diff options
| author |   Bin Hu <bh526r@att.com> | 2016-01-09 22:56:36 -0800 |
|---|---|---|
| committer | Bin Hu <bh526r@att.com> | 2016-01-09 22:56:36 -0800 |
| commit | 65838a2c8bf59035136bc7be7256d90ba22f05e8 (patch) | |
| tree | 7574d0078ca419546327e0e437a7c608353371e4 /docs/gapanalysis | |
| parent | f890f738bba19aaeb1db1ef4023e802072ca3414 (diff) | |
JIRA:IPVSIX-29
Change-Id: Ia161fab3f2f5127228596860d8a7e86f2697d016
Signed-off-by: Bin Hu <bh526r@att.com>
Diffstat (limited to 'docs/gapanalysis')
| -rw-r--r-- | docs/gapanalysis/gap-analysis-odl-lithium.rst | 7 | ||||
| -rw-r--r-- | docs/gapanalysis/gap-analysis-openstack-kilo.rst | 8 |
2 files changed, 7 insertions, 8 deletions
diff --git a/docs/gapanalysis/gap-analysis-odl-lithium.rst b/docs/gapanalysis/gap-analysis-odl-lithium.rst index 5178d51..56e86cf 100644 --- a/docs/gapanalysis/gap-analysis-odl-lithium.rst +++ b/docs/gapanalysis/gap-analysis-odl-lithium.rst @@ -20,9 +20,9 @@ requirements of VIM-agnostic IPv6 functionality, including infrastructure layer | | |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. | +| | |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>`_,| @@ -35,7 +35,6 @@ requirements of VIM-agnostic IPv6 functionality, including infrastructure layer |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. | | | diff --git a/docs/gapanalysis/gap-analysis-openstack-kilo.rst b/docs/gapanalysis/gap-analysis-openstack-kilo.rst index 745841d..bad7060 100644 --- a/docs/gapanalysis/gap-analysis-openstack-kilo.rst +++ b/docs/gapanalysis/gap-analysis-openstack-kilo.rst @@ -58,10 +58,10 @@ requirements of VIM-agnostic IPv6 functionality, including infrastructure layer |CLI) as well as via Horizon, including combination of | |https://review.openstack.org/#/c/139731/ for discussion. | |IPv6/IPv4 and IPv4/IPv6 floating IPs if implemented. | | | +-----------------------------------------------------------+-------------------------+--------------------------------------------------------------------+ -|Provide IPv6/IPv4 feature parity in support for |**Roadmap** |The L3 configuration should be transparent for the SR-IOV | +|Provide IPv6/IPv4 feature parity in support for |**To-Do** |The L3 configuration should be transparent for the SR-IOV | |pass-through capabilities (e.g., SR-IOV). | |implementation. SR-IOV networking support introduced in Juno based | | | |on the ``sriovnicswitch`` ML2 driver is expected to work with IPv4 | -| | |and IPv6 enabled VMs. | +| | |and IPv6 enabled VMs. We need to verify if it works or not | +-----------------------------------------------------------+-------------------------+--------------------------------------------------------------------+ |Additional IPv6 extensions, for example: IPSEC, IPv6 |**No** |It does not appear to be considered yet (lack of clear requirements)| |Anycast, Multicast | | | @@ -100,11 +100,11 @@ requirements of VIM-agnostic IPv6 functionality, including infrastructure layer |Ability for a VM to support a mix of multiple IPv4 and IPv6|Yes | | |networks, including multiples of the same type. | | | +-----------------------------------------------------------+-------------------------+--------------------------------------------------------------------+ -|Support for IPv6 Prefix Delegation. |**Roadmap** |Planned for Liberty | +|Support for IPv6 Prefix Delegation. |**Roadmap** |Some partial support is available in Liberty release | +-----------------------------------------------------------+-------------------------+--------------------------------------------------------------------+ |Distributed Virtual Routing (DVR) support for IPv6 |**No** |Blueprint proposed upstream, pending discussion. | +-----------------------------------------------------------+-------------------------+--------------------------------------------------------------------+ -|IPv6 First-Hop Security, IPv6 ND spoofing. |**Roadmap** |Blueprint proposed upstream. Some patches are under review. | +|IPv6 First-Hop Security, IPv6 ND spoofing. |**Roadmap** |Supported in Liberty release | +-----------------------------------------------------------+-------------------------+--------------------------------------------------------------------+ |IPv6 support in Neutron Layer3 High Availability |Yes | | |(keepalived+VRRP). | | | |