summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGergely Csatari <gergely.csatari@nokia.com>2017-07-03 07:04:25 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-07-03 07:04:25 +0000
commit0f93186dcabb017dd80271af0e60d3eb37fcedcf (patch)
tree92fa73e3e825dd0fa8bc1d872df6013ae8427e81
parent319038683d45291c0348412e7b037b86bc8f49a4 (diff)
parentb69d5697e35bb9d536f9215435bad77626268fb8 (diff)
Merge "Update gap analysis for Kubernetes"
-rw-r--r--docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst30
1 files 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 |
+-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+