Markup corrections to the Kubernetes gap analyzis

[openretriever.git] / docs / development / gapanalysis / gap-analysis-kubernetes-v1.5.rst

diff --git a/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst b/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst
index bff5372..f8fb85a 100644 (file)
--- a/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst
+++ b/docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst
@@ -14,11 +14,32 @@ 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                 |Kubernetes only manage containers. For this part, we need to setup a|
-  |                                                           |                   |platform to manage containers and virtual machine together          |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
-  |TBD                                                        |                   |                                                                    |
-  +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+
+  |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                                                     |
+  +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+