summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBin Hu <bh526r@att.com>2016-01-06 16:36:03 -0800
committerBin Hu <bh526r@att.com>2016-01-07 00:52:07 +0000
commit757e0513c71b6dd883d4f960421fde93fff9f693 (patch)
tree30361efd889e943d8acbda9a056efbe2ebefeab0
parentc1f22085089d9be36b51ddc44179da48d52739f1 (diff)
JIRA:IPVSIX-29
Fixed broken URL/reference link in docs/gapanalysis/gap-analysis-odl-lithium.rst Change-Id: I444001d09d417af969b1a04a927e4f25ef10605d Signed-off-by: Bin Hu <bh526r@att.com> (cherry picked from commit 1d0d7b0d1a9eeaa3d6c9f17aec1d1907e8fe6bff)
-rw-r--r--docs/gapanalysis/gap-analysis-odl-lithium.rst90
1 files changed, 46 insertions, 44 deletions
diff --git a/docs/gapanalysis/gap-analysis-odl-lithium.rst b/docs/gapanalysis/gap-analysis-odl-lithium.rst
index faa260b..5178d51 100644
--- a/docs/gapanalysis/gap-analysis-odl-lithium.rst
+++ b/docs/gapanalysis/gap-analysis-odl-lithium.rst
@@ -7,47 +7,49 @@ Open Daylight Lithium Official Release. The following table lists the use cases
requirements of VIM-agnostic IPv6 functionality, including infrastructure layer and VNF
(VM) layer, and its gap analysis with Open Daylight Lithium Official Release.
-+-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
-|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 using ``Routing Manager`` as part of |
-|1. Communication between VMs on same compute node | |Beryllium Release. In the meantime, if IPv6 Routing is necessary, we can |
-|2. Communication between VMs on different compute nodes | |use ODL for L2 connectivity and Neutron L3 agent for IPv4/v6 routing. |
-| (east-west) | | |
-|3. External routing (north-south) | |**Note**: In Lithium SR1 release, we have the following `issue |
-| | |<http://fpaste.org/275362>`_, which is fixed upstream and back-ported to |
-| | |``stable/lithium``. |
-+-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
-|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 | | |
-| | |This could be part of ``Routing Manager`` in ``Beryllium`` release. |
-+-------------------------------------------------------------+------------------------+-------------------------------------------------------------------------+
-|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 using ``Routing Manager`` as part of |
+|1. Communication between VMs on same compute node | |Beryllium Release. In the meantime, if IPv6 Routing is necessary, we can |
+|2. Communication between VMs on different compute nodes | |use ODL for L2 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 | | |
+| | |This could be part of ``Routing Manager`` in ``Beryllium`` release. |
++-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+
+|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. |
++-------------------------------------------------------------+------------------------+--------------------------------------------------------------------------------+