diff options
| -rw-r--r-- | INFO | 5 | ||||
| -rw-r--r-- | docs/development/gapanalysis/gap-analysis-kubernetes-v1.5.rst | 37 | ||||
| -rw-r--r-- | docs/development/gapanalysis/gap-analysis-openstack-mitaka.rst | 30 | ||||
| -rw-r--r-- | docs/development/gapanalysis/gap-analysis-openstack.rst | 71 | ||||
| -rw-r--r-- | docs/development/gapanalysis/index.rst | 4 |
5 files changed, 106 insertions, 41 deletions
@@ -20,6 +20,9 @@ wassim.haddad@ericsson.com heikki.mahkonen@ericsson.com akapadia@aarnanetworks.com srupanagunta@gmail.com +ruijing.guo@gmail.com Link to TSC approval of the project: http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-12-13-14.59.html -Link(s) to approval of additional committers: http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-04-11-13.59.html +Link(s) to approval of additional committers: +http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-04-11-13.59.html +https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-June/016505.html 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 --- 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 | + +-----------------------------------------------------------+-------------------+-----------------------------------------------------------------------------------------------------+ diff --git a/docs/development/gapanalysis/gap-analysis-openstack-mitaka.rst b/docs/development/gapanalysis/gap-analysis-openstack-mitaka.rst deleted file mode 100644 index 9fa906b..0000000 --- a/docs/development/gapanalysis/gap-analysis-openstack-mitaka.rst +++ /dev/null @@ -1,30 +0,0 @@ -.. 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) - -================================================ -OpenRetriever Gap Analysis with OpenStack Mitaka -================================================ -This section provides users with OpenRetriever gap analysis regarding feature -requirement with Openstack Mitaka Official Release. The following table lists -the use cases / feature requirements of container integrated functionality, and -its gap analysis with Openstack Mitaka Official Release. - -.. table:: - :class: longtable - - +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ - |Use Case / Requirement |Supported in Mitaka|Notes | - +===========================================================+===================+====================================================================+ - |Manage conainter and virtual machine in the same platform. |No |Magnum could provide container environment, but it can't manage | - | | |container application. We need a tool to manage applications, no | - | | |matter where it is running on container or virutal machine. | - +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ - |Container private registry store container images. |No |Container images need to store in container private registry. The | - | | |image could be stored in Openstack Cinder or single virtual machine.| - | | |No matter what, it can fetech container images in this container | - | | |environment. | - +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ - |Kuryr need to support MACVLAN and IPVLAN |No |MACVLAN and IPVLAN could get better network performance. In Ocata, | - | | |it will support. | - +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+ diff --git a/docs/development/gapanalysis/gap-analysis-openstack.rst b/docs/development/gapanalysis/gap-analysis-openstack.rst new file mode 100644 index 0000000..a7357aa --- /dev/null +++ b/docs/development/gapanalysis/gap-analysis-openstack.rst @@ -0,0 +1,71 @@ +.. 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), Gergely Csatari (Nokia) + +========================================= +OpenRetriever Gap Analysis with OpenStack +========================================= +This section provides a gap analyzis between the targets of OpenRetriever for +release Euphrates (E) or later and the features provided by OpenStack in release +Ocata. As the OPNFV and OpenStack releases tend to change over time this +analyzis is planned to be countinously updated. +During the analyzis all OpenStack projects considered. + +(**Editors note:** Maybe we should define a scope of OpenStack projects which is +considered. All OpenStack projects can mean anything.) + +The following table lists the use cases / feature requirements of container +integrated functionality, and its gap analysis with OpenStack. + +.. table:: + :class: longtable + + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+----------------+ + |Use Case / Requirement |Related OpenStack |Notes |Status | + | |project | | | + +===========================================================+===================+====================================================================+================+ + |Manage container and virtual machine lifecycle with the |Zun_ or nova-docker|Magnum_ can deploy a Container Orchestration Engine (COE), but does |Open | + |same NB API |driver |not provide any lifecycle management operations to the containers | | + | | |deployed in the COE. | | + | | |Zun_ provides lifecycle management support for the containers | | + | | |deployed in the COE via Nova API, but not all COE API operations are| | + | | |supported. | | + | | |nova-docker driver provided support for container lifecycle | | + | | |management without a COE (and Magnum), but it was deprecated due to | | + | | |lack of community support. A fork of the original nova-docker driver| | + | | |is maintained by the Zun team to provide support for the sandbox | | + | | |containers. | | + | | |**Note:** Support for this is not targeted in OPNFV release E. | | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+----------------+ + |Container private registry to store container images |Swift_, Cinder_, |Container images need a storage backed from where the COE can serve |Open | + | |Glance_, Glare_ |the registry. This backend should be accessible and should be | | + | | |supported by the COE. | | + | | |As a workaround it is possible to install a registry backend to a VM| | + | | |, but it is more optimal to use the possible backends already | | + | | |available in OpenStack, like Swift_, Cinder_, Glance_ or Glare_. | | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+----------------+ + |Kuryr_ needs to support MACVLAN and IPVLAN |Kuryr_ |Using MACVLAN or IPVLAN could provide better network performance. |Open | + | | |It is planned for Ocata. | | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+----------------+ + |Kuryr_ Kubernetes_ integration is needed |Kuryr_ |It is done in the frame of OpenRetriever. |Targeted to | + | | | |OPNFV release E | + | | | |/OpenStack Ocata| + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+----------------+ + |HA support for Kuryr_ |Kuryr_ | |Targeted to | + | | | |OPNFV release E | + | | | |/OpenStack Ocata| + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+----------------+ + |HA support for Zun_ |Zun_ | |Open | + | | | | | + | | | | | + +-----------------------------------------------------------+-------------------+--------------------------------------------------------------------+----------------+ + + +.. _Zun: https://wiki.openstack.org/wiki/Zun +.. _Magnum: https://wiki.openstack.org/wiki/Magnum +.. _Swift: https://wiki.openstack.org/wiki/Swift +.. _Cinder: https://wiki.openstack.org/wiki/Cinder +.. _Kuryr: https://wiki.openstack.org/wiki/Kuryr +.. _Glance: https://wiki.openstack.org/wiki/Glance +.. _Glare: https://github.com/openstack/glare +.. _Kubernetes: https://kubernetes.io/ diff --git a/docs/development/gapanalysis/index.rst b/docs/development/gapanalysis/index.rst index 339b154..08b0925 100644 --- a/docs/development/gapanalysis/index.rst +++ b/docs/development/gapanalysis/index.rst @@ -1,6 +1,6 @@ .. 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) +.. (c) Xuan Jia (China Mobile), Gergely Csatari (Nokia) ========================== OpenRetriever Gap Analysis @@ -18,5 +18,5 @@ OpenRetriever Gap Analysis .. toctree:: maxdepth:2 gap-analysis-opnfv-installer.rst - gap-analysis-openstack-mitaka.rst + gap-analysis-openstack.rst gap-analysis-kubernetes-v1.5.rst |