ipv6_opnfv_project:ipv6_gap_odl
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ipv6_opnfv_project:ipv6_gap_odl [2016/02/22 17:17] Bin Hu |
ipv6_opnfv_project:ipv6_gap_odl [2016/02/22 19:37] (current) Bin Hu [IPv6 Gap Analysis with Open Daylight] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== IPv6 Gap Analysis with Open Daylight ===== | ===== IPv6 Gap Analysis with Open Daylight ===== | ||
| - | Here is the gap analysis with Open Daylight: | + | Here is the gap analysis with Open Daylight Beryllium Release: |
| + | |||
| + | ^ Use Case / Requirement ^ Supported in ODL Beryllium Release? ^ 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 Beryllium 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\\ 1. Communication between VMs on same compute node\\ 2. Communication between VMs on different compute nodes (east-west)\\ 3. External routing (north-south) | No | ODL net-virt provider in Beryllium release only supports IPv4 Router.\\ In the meantime, if IPv6 Routing is necessary, we can use ODL for L2 connectivity and Neutron L3 agent for IPv4/v6 routing. | | ||
| + | | IPAM: Support for IPv6 Address assignment modes.\\ 1. SLAAC\\ 2. DHCPv6 Stateless\\ 3. DHCPv6 Stateful\\ | 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 Advertisements based on the IPv6 addressing mode.\\ Router Advertisement is also necessary for VMs to configure the default route. | | ||
| + | | When using ODL for L2 forwarding/tunneling, is it compatible with IPv6. | Yes | | | ||
| + | | Full support for IPv6 matching (i.e., IPv6, ICMPv6, TCP, UDP) 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. | No | Security Groups for IPv6 is a work in progress. | | ||
| + | | 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. | | ||
| + | |||
| + | |||
| + | |||
| - | **IPv6 ToDo in Beryllium:** https://trello.com/c/IlLJcL1x/26-ipv6\\ **IPAM/DHCP:** https://trello.com/c/fBL9uD8G/25-l3-dhcp-ipam | ||
| - | ^ Use Case / Requirement ^ Supported in ODL Lithium SR1 Release? ^ 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\\ 1. Communication between VMs on same compute node\\ 2. Communication between VMs on different compute nodes (east-west)\\ 3. External routing (north-south) | No | ODL net-virt provider in Lithium release only supports IPv4 Router.\\ Support for IPv6 Router is planned using [[https://wiki.opendaylight.org/view/IPv4/IPv6_Dual_stack|Routing Manager]] as part of Beryllium Release.\\ In the meantime, if IPv6 Routing is necessary, we can use ODL for L2 connectivity and Neutron L3 agent for IPv4/v6 routing.\\ Note: In Lithium SR1 release, we have the following [[http://fpaste.org/275362|issue]], which is fixed upstream and back-ported to [[https://git.opendaylight.org/gerrit/#/c/26284|stable/lithium (expected in SR2 release)]]. | | ||
| - | | IPAM: Support for IPv6 Address assignment modes.\\ 1. SLAAC\\ 2. DHCPv6 Stateless\\ 3. DHCPv6 Stateful\\ | 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 Advertisements based on the IPv6 addressing mode.\\ Router Advertisement is also necessary for VMs to configure the default route\\ This could be part of Routing Manager in Beryllium release. | | ||
| - | | When using ODL for L2 forwarding/tunneling, is it compatible with IPv6. | Yes | | | ||
| - | | Full support for IPv6 matching (i.e., IPv6, ICMPv6, TCP, UDP) 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. | No | Security Groups for IPv6 are currently not supported. | | ||
| - | | 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. | | ||
| ==== Prior Version of Gap Analysis ==== | ==== Prior Version of Gap Analysis ==== | ||
ipv6_opnfv_project/ipv6_gap_odl.1456161469.txt.gz · Last modified: 2016/02/22 17:17 by Bin Hu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
