add scenarior for virlet and kata

Change-Id: I24eaa36693b05343f67a3a777d04b7841dca9884
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
(cherry picked from commit 554a84f03e586252c5f0fc320acd046a2ae93439)

2 files changed, 31 insertions, 0 deletions

diff --git a/docs/release/scenarios/k8-nosdn-virtlet-noha/index.rst b/docs/release/scenarios/k8-nosdn-virtlet-noha/index.rst
new file mode 100644
index 0000000..ba7c54e
--- /dev/null
+++ b/docs/release/scenarios/k8-nosdn-virtlet-noha/index.rst
@@ -0,0 +1,18 @@
+.. _k8-nosdn-virtlet-noha:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+=========================================
+k8-nosdn-virtlet-noha overview and description
+=========================================
+.. This document will be used to provide a description of the scenario for an end user.
+.. You should explain the purpose of the scenario, the types of capabilities provided and
+..  the unique components that make up the scenario including how they are used.
+
+.. toctree::
+   :maxdepth: 3
+
+   ./scenario.description.rst
+
diff --git a/docs/release/scenarios/k8-nosdn-virtlet-noha/scenario.description.rst b/docs/release/scenarios/k8-nosdn-virtlet-noha/scenario.description.rst
new file mode 100644
index 0000000..60902db
--- /dev/null
+++ b/docs/release/scenarios/k8-nosdn-virtlet-noha/scenario.description.rst
@@ -0,0 +1,13 @@
+Virlet implementation for OPNFV
+=================================
+
+This quickstart shows you how to easily install a Kubernetes cluster on VMs running with Vagrant. The installation uses a tool called kubeadm which is part of Kubernetes.
+
+kubeadm assumes you have a set of machines (virtual or bare metal) that are up and running. In this way we can get a cluster with one master node and 2 workers (default). If you want to increase the number of workers nodes, please check the Vagrantfile inside the project.
+
+About Virlet
+------------
+
+(Virlet)[https://github.com/Mirantis/virtlet] is a Kubernetes runtime server / (CRI)[http://blog.kubernetes.io/2016/12/container-runtime-interface-cri-in-kubernetes.html] that enables you to run VM workloads based on QCOW2 images. (CRI is what enables Kubernetes to run non-Docker flavors of containers, such as Rkt.) 
+
+Virlet gives NFV a new direction. Virtlet itself runs as a DaemonSet, essentially acting as a hypervisor and making the CRI proxy available to run the actual VMs. This way, it’s possible to have both Docker and non-Docker pods run on the same node.