blob: 367237d9c712c82cd8a6cff63eb99fdcd730d2ac (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.http://creativecommons.org/licenses/by/4.0
.. (c) Xuan Jia (China Mobile)
================================================
Container4NFV Gap Analysis with Kubernetes v1.5
================================================
This section provides users with Container4NFV gap analysis regarding feature
requirement with Kubernetes Official Release. The following table lists the use
cases / feature requirements of container integrated functionality, and its gap
analysis with Kubernetes Official Release.
.. table::
:class: longtable
+-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
|Use Case / Requirement |Supported in v1.5 |Notes |
+===========================================================+===================+=====================================================================================================+
|Manage conainter and virtual machine in the same platform. |No | There are some ways how Kubernetes could manage VM-s: |
| | | |
| | | 1. `Kubevirt <https://github.com/kubevirt/kubevirt>`_ |
| | | 2. Kubernetes can start rkt and with |
| | | `rkt it is possible to start VM-s <https://coreos.com/rkt/docs/latest/running-kvm-stage1.html>`_ |
| | | 3. `Virtlet <https://github.com/Mirantis/virtlet>`_ |
| | | 4. `Hypercontainer <https://github.com/kubernetes/frakti>`_ |
+-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
|Kubernetes support multiple networks. |No | As VNF needs at least three interfaces. Management,control plane, data plane. `CNI |
| | | <https://github.com/containernetworking/cni/blob/master/SPEC.md>`_ already supports multiple |
| | | interfaces in the API definition. |
| | | |
| | | 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/>`_ |
+-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
|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 |
+-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
|
