From b69d5697e35bb9d536f9215435bad77626268fb8 Mon Sep 17 00:00:00 2001 From: Xuan Jia Date: Mon, 12 Jun 2017 11:46:44 +0800 Subject: Update gap analysis for Kubernetes Change-Id: Ib4b95923f31e2f4626069d5e229bd850f3ac9e3a Signed-off-by: Xuan Jia --- .../gapanalysis/gap-analysis-kubernetes-v1.5.rst | 30 +++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) diff --git a/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst b/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst index bff5372..2d4039c 100644 --- a/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst +++ b/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst @@ -17,8 +17,32 @@ analysis with Kubernetes Official Release. +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ |Use Case / Requirement |Supported in v1.5 |Notes | +===========================================================+===================+====================================================================+ - |Manage conainter and virtual machine in the same platform. |No |Kubernetes only manage containers. For this part, we need to setup a| - | | |platform to manage containers and virtual machine together | + |Manage conainter and virtual machine in the same platform. |No | There are some ways how Kubernetes could manage VM-s: | + | | | 1) Kubevirt [1] | + | | | 2) Kubernetes can start rkt and with rkt it is possible to start | + | | | VM-s [2] | + | | | 3) Virtlet [3] | + | | | 4) Hypercontainer [4] | + | | | [1] https://github.com/kubevirt/kubevirt | + | | | [2] https://coreos.com/rkt/docs/latest/running-kvm-stage1.html | + | | | [3] https://github.com/Mirantis/virtlet | + | | | [4] https://github.com/kubernetes/frakti | +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ - |TBD | | | + |Kubernetes support multiple networks. |No | As VNF needs at least three interfaces. Management,control plane, | + | | |data plane. | + | | | (1) Multus https://github.com/Intel-Corp/multus-cni | + | | | (2) CNI-Genie https://github.com/Huawei-PaaS/CNI-Genie | + | | | (3) A solution built into Kubernetes | + | | | https://docs.google.com/document/d/1TW3P4c8auWwYy-w_5afIPDcGNLK3LZf0m14943eVfVg/ | + | | | (4) CNI | + | | | https://github.com/containernetworking/cni/blob/master/SPEC.md | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ + |Kubernetes support NAT-less connections to a container |No | SIP/SDP and SCTP are not working with NAT-ed networks | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ + |Kubernetes scheduling support CPU binding，NUMA features |No |The kubernetes schedular don't support these features | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ + |DPDK need to support CNI |No |DPDK is the technology to accelerate the data plane. Container need | + | | |support it, the same with virtual machine. | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ + |SR-IOV can support CNI (Optional) |No |SR-IOV could let container get high performance | +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ -- cgit 1.2.3-korg