docs: Add info about kubernetes support

1. Introduce the installer used to deploy kubernetes
2. Introduce XCI how to deploy the kubernetes

Change-Id: I052b4547d763d19b8d6136a48d4804443921b021
Signed-off-by: wutianwei <wutianwei1@huawei.com>

3 files changed, 112 insertions, 36 deletions

diff --git a/docs/images/arch-layout-k8s-ha.png b/docs/images/arch-layout-k8s-ha.png
new file mode 100644
index 00000000..e0870305
--- /dev/null
+++ b/docs/images/arch-layout-k8s-ha.png
diff --git a/docs/images/arch-layout-k8s-noha.png b/docs/images/arch-layout-k8s-noha.png
new file mode 100644
index 00000000..0ee8bceb
--- /dev/null
+++ b/docs/images/arch-layout-k8s-noha.png
diff --git a/docs/xci-user-guide.rst b/docs/xci-user-guide.rst
index 7a411257..8f506fc4 100644
--- a/docs/xci-user-guide.rst
+++ b/docs/xci-user-guide.rst
@@ -41,6 +41,7 @@ The sandbox provides
 * multiple OPNFV scenarios to install
 * ability to select different versions of upstream components to base the work on
 * ability to enable additional OpenStack services or disable others
+* ability to install kubernetes with different network plugins
 
 One last point to highlight here is that the XCI itself uses the sandbox for
 development and test purposes so it is continuously tested to ensure it works
@@ -50,10 +51,11 @@ purposes.
 Components of the Sandbox
 ===================================
 
-The sandbox uses OpenStack projects for VM node creation, provisioning
-and OpenStack installation. XCI Team provides playbooks, roles, and scripts
-to ensure the components utilized by the sandbox work in a way that serves
-the users in the best possible way.
+The sandbox uses OpenStack tools for VM node creation and provisioning.
+OpenStack and Kubernetes installations are done using the tools from corresponding
+upstream projects with no changes to them. XCI Team provides playbooks,
+roles, and scripts to ensure the components utilized by the sandbox
+work in a way that serves the users in the best possible way.
 
 * **openstack/bifrost:** Bifrost (pronounced bye-frost) is a set of Ansible
   playbooks that automates the task of deploying a base image onto a set
@@ -70,6 +72,13 @@ the users in the best possible way.
   More information about this project can be seen on
   `OpenStack Ansible documentation <https://docs.openstack.org/developer/openstack-ansible/>`_.
 
+* **kubernetes-incubator/kubespray:** Kubespray is a composition of Ansible playbooks,
+  inventory, provisioning tools, and domain knowledge for generic Kubernetes
+  clusters configuration management tasks. The aim of kubespray is deploying a
+  production ready Kubernetes cluster.
+  More information about this project can be seen on
+  `Kubespray documentation <https://kubernetes.io/docs/getting-started-guides/kubespray/>`_.
+
 * **opnfv/releng-xci:** OPNFV Releng Project provides additional scripts, Ansible
   playbooks and configuration options in order for developers to have an easy
   way of using openstack/bifrost and openstack/openstack-ansible by just
@@ -85,29 +94,29 @@ deployed using VM nodes.
 
 Available flavors are listed on the table below.
 
-+------------------+------------------------+---------------------+-------------------------+
-| Flavor           | Number of VM Nodes     | VM Specs Per Node   | Time Estimates          |
-+==================+========================+=====================+=========================+
-| All in One (aio) | | 1 VM Node            | | vCPUs: 8          | | Provisioning: 10 mins |
-|                  | | controller & compute | | RAM: 12GB         | | Deployment: 90 mins   |
-|                  | | on single/same node  | | Disk: 80GB        | | Total: 100 mins       |
-|                  | | 1 compute node       | | NICs: 1           | |                       |
-+------------------+------------------------+---------------------+-------------------------+
-| Mini             | | 3 VM Nodes           | | vCPUs: 6          | | Provisioning: 12 mins |
-|                  | | 1 deployment node    | | RAM: 12GB         | | Deployment: 65 mins   |
-|                  | | 1 controller node    | | Disk: 80GB        | | Total: 77 mins        |
-|                  | | 1 compute node       | | NICs: 1           | |                       |
-+------------------+------------------------+---------------------+-------------------------+
-| No HA            | | 4 VM Nodes           | | vCPUs: 6          | | Provisioning: 12 mins |
-|                  | | 1 deployment node    | | RAM: 12GB         | | Deployment: 70 mins   |
-|                  | | 1 controller node    | | Disk: 80GB        | | Total: 82 mins        |
-|                  | | 2 compute nodes      | | NICs: 1           | |                       |
-+------------------+------------------------+---------------------+-------------------------+
-| HA               | | 6 VM Nodes           | | vCPUs: 6          | | Provisioning: 15 mins |
-|                  | | 1 deployment node    | | RAM: 12GB         | | Deployment: 105 mins  |
-|                  | | 3 controller nodes   | | Disk: 80GB        | | Total: 120 mins       |
-|                  | | 2 compute nodes      | | NICs: 1           | |                       |
-+------------------+------------------------+---------------------+-------------------------+
++------------------+------------------------+---------------------+--------------------------+--------------------------+
+| Flavor           | Number of VM Nodes     | VM Specs Per Node   | Time Estimates Openstack | Time Estimates Kubernetes|
++==================+========================+=====================+==========================+==========================+
+| All in One (aio) | | 1 VM Node            | | vCPUs: 8          | | Provisioning: 10 mins  | | Provisioning: 10 mins  |
+|                  | | controller & compute | | RAM: 12GB         | | Deployment: 90 mins    | | Deployment: 30 mins    |
+|                  | | on single/same node  | | Disk: 80GB        | | Total: 100 mins        | | Total: 40 mins         |
+|                  | | 1 compute node       | | NICs: 1           | |                        | |                        |
++------------------+------------------------+---------------------+--------------------------+--------------------------+
+| Mini             | | 3 VM Nodes           | | vCPUs: 6          | | Provisioning: 12 mins  | | Provisioning: 12 mins  |
+|                  | | 1 deployment node    | | RAM: 12GB         | | Deployment: 65 mins    | | Deployment: 35 mins    |
+|                  | | 1 controller node    | | Disk: 80GB        | | Total: 77 mins         | | Total: 47 mins         |
+|                  | | 1 compute node       | | NICs: 1           | |                        | |                        |
++------------------+------------------------+---------------------+--------------------------+--------------------------+
+| No HA            | | 4 VM Nodes           | | vCPUs: 6          | | Provisioning: 12 mins  | | Provisioning: 12 mins  |
+|                  | | 1 deployment node    | | RAM: 12GB         | | Deployment: 70 mins    | | Deployment: 35 mins    |
+|                  | | 1 controller node    | | Disk: 80GB        | | Total: 82 mins         | | Total: 47 mins         |
+|                  | | 2 compute nodes      | | NICs: 1           | |                        | |                        |
++------------------+------------------------+---------------------+--------------------------+--------------------------+
+| HA               | | 6 VM Nodes           | | vCPUs: 6          | | Provisioning: 15 mins  | | Provisioning: 15 mins  |
+|                  | | 1 deployment node    | | RAM: 12GB         | | Deployment: 105 mins   | | Deployment: 40 mins    |
+|                  | | 3 controller nodes   | | Disk: 80GB        | | Total: 120 mins        | | Total: 55 mins         |
+|                  | | 2 compute nodes      | | NICs: 1           | |                        | |                        |
++------------------+------------------------+---------------------+--------------------------+--------------------------+
 
 
 The specs for VMs are configurable and the more vCPU/RAM the better.
@@ -122,8 +131,8 @@ depending on
 * installed/activated OpenStack services
 * internet connection bandwidth
 
-Flavor Layouts
---------------
+Flavor Layouts - OpenStack Based Deployments
+--------------------------------------------
 
 All flavors are created and deployed based on the upstream OpenStack Ansible (OSA)
 guidelines.
@@ -165,6 +174,44 @@ flavors.
 .. image:: images/arch-layout-test.png
    :scale: 75 %
 
+Flavor Layouts - Kubernetes Based Deployments
+---------------------------------------------
+
+All flavors are created and deployed based on the upstream kubespray guidelines.
+
+For network plugins, calico is used. flannel, weaver, contive, canal and cilium
+are supported currently
+
+The differences between the flavors are documented below.
+
+**All in One**
+
+As shown on the table in the previous section, this flavor consists of a single
+node. All the kubernetes services run on the same node, which acts as master
+and worker at the same time.
+
+**Mini/No HA/HA**
+
+These flavors consist of multiple nodes.
+
+* **opnfv**: This node is used for driving the installation towards target nodes
+  in order to ensure the deployment process is isolated from the physical host
+  and always done on a clean machine.
+* **master**:  provide the kubernetes cluster’s control plane.
+* **node**: a worker machine in Kubernetes, previously known as a minion.
+
+HA flavor has 3 master nodes and a load balancer is set up as part of the deployment process.
+The access to the Kubernetes cluster is done through the load balancer.
+
+Please see the diagrams below for the host and service layout for these
+flavors.
+
+.. image:: images/arch-layout-k8s-noha.png
+   :scale: 75 %
+
+.. image:: images/arch-layout-k8s-ha.png
+   :scale: 75 %
+
 User Guide
 ==========
 
@@ -200,7 +247,12 @@ How to Use
 
    | ``cd releng-xci/xci``
 
-4. Execute the sandbox script
+4. If you want to deploy Kubernetes based scenario, set the variables as below. Otherwise skip.
+
+   | ``export INSTALLER_TYPE=kubespray``
+   | ``export DEPLOY_SCENARIO=k8-nosdn-nofeature``
+
+5. Execute the sandbox script
 
    | ``./xci-deploy.sh``
 
@@ -241,8 +293,14 @@ default.
 
 5. Set the version to use for openstack-ansible
 
+   1) if deploying OpenStack based scenario
+
    | ``export OPENSTACK_OSA_VERSION=master``
 
+   2) if deploying Kubernetes based scenario
+
+   | ``export KUBESPRAY_VERSION=master``
+
 6. Set where the logs should be stored
 
    | ``export LOG_PATH=/home/jenkins/xcilogs``
@@ -256,7 +314,7 @@ behaviors, especially if it is changed to ``master``. If you are not
 sure about how good the version you intend to use is, it is advisable to
 use the pinned versions instead.
 
-**Verifying the Basic Operation**
+**Verifying the Openstack Basic Operation**
 
 You can verify the basic operation using the commands below.
 
@@ -276,6 +334,23 @@ You can also access the Horizon UI by using the URL, username, and
 the password displayed on your console upon the completion of the
 deployment.
 
+**Verifying the Kubernetes Basic Operation**
+
+You can verify the basic operation using the commands below.
+
+1. Login to opnfv host
+
+   | ``ssh root@192.168.122.2``
+
+2. Issue kubectl commands
+
+   | ``kubectl get nodes``
+
+You can also access the Kubernetes Dashboard UI by using the URL,
+username, and the password displayed on your console upon the
+completion of the deployment.
+
+
 **Debugging Tips**
 
 If ``xci-deploy.sh`` fails midway through and you happen to fix whatever
@@ -295,11 +370,12 @@ Here are steps that take place upon the execution of the sandbox script
 2. Installs ansible on the host where sandbox script is executed.
 3. Creates and provisions VM nodes based on the flavor chosen by the user.
 4. Configures the host where the sandbox script is executed.
-5. Configures the deployment host which the OpenStack installation will
-   be driven from.
-6. Configures the target hosts where OpenStack will be installed.
-7. Configures the target hosts as controller(s) and compute(s) nodes.
-8. Starts the OpenStack installation.
+5. Configures the deployment host which the OpenStack/Kubernetes
+   installation will be driven from.
+6. Configures the target hosts where OpenStack/Kubernetes will be installed.
+7. Configures the target hosts as controller(s)/compute(s) or master(s)/worker(s)
+   depending on the deployed scenario.
+8. Starts the OpenStack/Kubernetes installation.
 
 .. image:: images/xci-basic-flow.png
    :height: 640px