diff options
| author |   Guo Ruijing <ruijing.guo@intel.com> | 2018-11-08 16:52:30 +0800 |
|---|---|---|
| committer | Ruijing Guo <ruijing.guo@intel.com> | 2018-11-08 03:12:35 +0000 |
| commit | 97f02fd3d2168135d9837926c0515b3d5b8de6ad (patch) | |
| tree | 8a5c9d5f01539ac316ae3b67fe938228e4591a5d /docs/release/userguide/virlet.rst | |
| parent | 1fa07ef952a6b0e12487901919cec52b9d9b9739 (diff) | |
add scenarior for virlet and kata
Change-Id: I24eaa36693b05343f67a3a777d04b7841dca9884
Signed-off-by: Guo Ruijing <ruijing.guo@intel.com>
(cherry picked from commit 554a84f03e586252c5f0fc320acd046a2ae93439)
Diffstat (limited to 'docs/release/userguide/virlet.rst')
| -rw-r--r-- | docs/release/userguide/virlet.rst | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/docs/release/userguide/virlet.rst b/docs/release/userguide/virlet.rst deleted file mode 100644 index 60902db..0000000 --- a/docs/release/userguide/virlet.rst +++ /dev/null @@ -1,13 +0,0 @@ -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. |