diff options
author | Bin Hu <bh526r@att.com> | 2016-02-04 15:56:33 -0800 |
---|---|---|
committer | Bin Hu <bh526r@att.com> | 2016-02-04 15:56:33 -0800 |
commit | 962ab4fc723ec32a9dc7109f6b1a6c8191bd49be (patch) | |
tree | 6a3378c905797b53d403ba5bdff6407204da1040 | |
parent | 3c4f23e2afc974fc41dce5ca817594ceb3fef46f (diff) |
JIRA:IPVSIX-29
Change-Id: I4b79b8b317b58c475d22da7a0e3a919f266e8da2
Signed-off-by: Bin Hu <bh526r@att.com>
-rw-r--r-- | docs/gapanalysis/gap-analysis-odl-lithium.rst | 91 |
1 files changed, 45 insertions, 46 deletions
diff --git a/docs/gapanalysis/gap-analysis-odl-lithium.rst b/docs/gapanalysis/gap-analysis-odl-lithium.rst index e55778d..269ef16 100644 --- a/docs/gapanalysis/gap-analysis-odl-lithium.rst +++ b/docs/gapanalysis/gap-analysis-odl-lithium.rst @@ -10,49 +10,48 @@ requirements of VIM-agnostic IPv6 functionality, including infrastructure layer .. table:: :class: longtable -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|Use Case / Requirement |Supported in ODL Lithium|Notes | -+=============================================================+========================+================================================================================+ -|REST API support for IPv6 subnet creation in ODL |Yes |Yes, it is possible to create IPv6 subnets in ODL using Neutron REST API. | -| | | | -| | |For a network which has both IPv4 and IPv6 subnets, ODL mechanism driver | -| | |will send the port information which includes IPv4/v6 addresses to ODL | -| | |Neutron northbound API. When port information is queried it displays IPv4 | -| | |and IPv6 addresses. However, in Lithium release, ODL net-virt provider | -| | |does not support IPv6 features (i.e., the actual functionality is missing | -| | |and would be available only in the later releases of ODL). | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|IPv6 Router support in ODL |**No** |ODL net-virt provider in Lithium release only supports IPv4 Router. | -| | |Support for IPv6 Router is planned in later releases using ``Routing Manager``. | -|1. Communication between VMs on same compute node | |In the meantime, if IPv6 Routing is necessary, we can use ODL for L2 | -|2. Communication between VMs on different compute nodes | |connectivity and Neutron L3 agent for IPv4/v6 routing. | -| (east-west) | | | -|3. External routing (north-south) | |**Note**: In Lithium SR3 release, we have the following `issue | -| | |<http://lists.opendaylight.org/pipermail/ovsdb-dev/2015-November/002288.html>`_,| -| | |which is fixed `upstream <http://git.opendaylight.org/gerrit/#/c/30253/4>`_ | -| | |and `back-ported <http://git.opendaylight.org/gerrit/#/c/30474>`_ to | -| | |``stable/lithium`` branch on December 15th, 2015. | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|IPAM: Support for IPv6 Address assignment modes. |**No** |Although it is possible to create different types of IPv6 subnets in ODL, | -| | |ODL_L3 would have to implement the IPv6 Router that can send out Router | -|1. SLAAC | |Advertisements based on the IPv6 addressing mode. Router Advertisement | -|2. DHCPv6 Stateless | |is also necessary for VMs to configure the default route. | -|3. DHCPv6 Stateful | | | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|When using ODL for L2 forwarding/tunneling, is it compatible |Yes | | -|with IPv6. | | | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|Full support for IPv6 matching (i.e., IPv6, ICMPv6, TCP, UDP)|**No** |Security Groups for IPv6 are currently not supported. | -|in security groups. Ability to control and manage all IPv6 | | | -|security group capabilities via Neutron/Nova API (REST and | | | -|CLI) as well as via Horizon. | | | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|Shared Networks support |**No** |ODL currently assumes a single tenant to network mapping and does not | -| | |support shared networks among tenants. | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|IPv6 external L2 VLAN directly attached to a VM. |**ToDo** | | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ -|ODL on an IPv6 only Infrastructure. |**ToDo** |Deploying OpenStack with ODL on an IPv6 only infrastructure where the API | -| | |endpoints are all IPv6 addresses. | -+-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ - + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |Use Case / Requirement |Supported in ODL Lithium|Notes | + +=============================================================+========================+================================================================================+ + |REST API support for IPv6 subnet creation in ODL |Yes |Yes, it is possible to create IPv6 subnets in ODL using Neutron REST API. | + | | | | + | | |For a network which has both IPv4 and IPv6 subnets, ODL mechanism driver | + | | |will send the port information which includes IPv4/v6 addresses to ODL | + | | |Neutron northbound API. When port information is queried it displays IPv4 | + | | |and IPv6 addresses. However, in Lithium release, ODL net-virt provider | + | | |does not support IPv6 features (i.e., the actual functionality is missing | + | | |and would be available only in the later releases of ODL). | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |IPv6 Router support in ODL |**No** |ODL net-virt provider in Lithium release only supports IPv4 Router. | + | | |Support for IPv6 Router is planned in later releases using ``Routing Manager``. | + |1. Communication between VMs on same compute node | |In the meantime, if IPv6 Routing is necessary, we can use ODL for L2 | + |2. Communication between VMs on different compute nodes | |connectivity and Neutron L3 agent for IPv4/v6 routing. | + | (east-west) | | | + |3. External routing (north-south) | |**Note**: In Lithium SR3 release, we have the following `issue | + | | |<http://lists.opendaylight.org/pipermail/ovsdb-dev/2015-November/002288.html>`_,| + | | |which is fixed `upstream <http://git.opendaylight.org/gerrit/#/c/30253/4>`_ | + | | |and `back-ported <http://git.opendaylight.org/gerrit/#/c/30474>`_ to | + | | |``stable/lithium`` branch on December 15th, 2015. | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |IPAM: Support for IPv6 Address assignment modes. |**No** |Although it is possible to create different types of IPv6 subnets in ODL, | + | | |ODL_L3 would have to implement the IPv6 Router that can send out Router | + |1. SLAAC | |Advertisements based on the IPv6 addressing mode. Router Advertisement | + |2. DHCPv6 Stateless | |is also necessary for VMs to configure the default route. | + |3. DHCPv6 Stateful | | | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |When using ODL for L2 forwarding/tunneling, is it compatible |Yes | | + |with IPv6. | | | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |Full support for IPv6 matching (i.e., IPv6, ICMPv6, TCP, UDP)|**No** |Security Groups for IPv6 are currently not supported. | + |in security groups. Ability to control and manage all IPv6 | | | + |security group capabilities via Neutron/Nova API (REST and | | | + |CLI) as well as via Horizon. | | | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |Shared Networks support |**No** |ODL currently assumes a single tenant to network mapping and does not | + | | |support shared networks among tenants. | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |IPv6 external L2 VLAN directly attached to a VM. |**ToDo** | | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ + |ODL on an IPv6 only Infrastructure. |**ToDo** |Deploying OpenStack with ODL on an IPv6 only infrastructure where the API | + | | |endpoints are all IPv6 addresses. | + +-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+ |