Bug 1089447
| Summary: | [RFE][neutron]: support multiple ipv6 prefixes for ipv6 network | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
| Component: | openstack-neutron | Assignee: | Sridhar Gaddam <sgaddam> |
| Status: | CLOSED ERRATA | QA Contact: | Eran Kuris <ekuris> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | chrisw, ihrachys, markmc, mlopes, nyechiel, oblaut, rbiba, sgaddam, tfreger, yeylon |
| Target Milestone: | z2 | Keywords: | FutureFeature, ZStream |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/neutron/+spec/multiple-ipv6-prefixes | ||
| Whiteboard: | upstream_milestone_kilo-rc1 upstream_definition_approved upstream_status_implemented | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
This enhancement adds support for configuring multiple IPv6 prefixes and addresses on a single interface.
As a result, OpenStack Networking (neutron) considers the type of IPv6 subnets that form part of the network, and automatically associates ports with addresses from all the SLAAC-enabled subnets within the ports network.
There is no change to the REST API, but port-create/port-update responses automatically include the SLAAC addresses in the list of 'fixed_ips'.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-08 12:07:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1228176 | ||
| Bug Blocks: | 1232677 | ||
|
Description
RHOS Integration
2014-04-19 04:05:26 UTC
Hi Sridhar , I finished to write the test plan and I attached it to "External Trackers". Please take a look for final review and tell me if you have any comments . thanks you very much . Hello Eran, I've emailed you the comments. Please take a look and update the document accordingly. Thanks, --Sridhar. This RFE cannot be tested because of blocker bug https://bugzilla.redhat.com/show_bug.cgi?id=1228176 in launchpad : https://bugs.launchpad.net/neutron/+bug/1456206?comments=all Tried to test it on :OSP 7 build 2015-06-02.1 on rhel 7.1 # rpm -qa |grep neutron python-neutron-2015.1.0-1.el7ost.noarch openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch python-neutronclient-2.4.0-1.el7ost.noarch openstack-neutron-2015.1.0-1.el7ost.noarch openstack-neutron-ml2-2015.1.0-1.el7ost.noarch openstack-neutron-lbaas-2015.1.0-3.el7ost.noarch python-neutron-fwaas-2015.1.0-3.el7ost.noarch openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch openstack-neutron-common-2015.1.0-1.el7ost.noarch python-neutron-lbaas-2015.1.0-3.el7ost.noarch test run : https://tcms.engineering.redhat.com/run/248773/ The blocker Bug reported for this issue is resolved by using dnsmasq 2.67 as well as the neutron patch which is merged upstream [1] and a stable/kilo patch under review [2]. [1] https://review.openstack.org/#/c/185066/ [2] https://review.openstack.org/#/c/197469/ I believe it's included in >= openstack-neutron-2015.1.1-1.el7ost. If so, please mark as MODIFIED. Yes @Ihar, stable/kilo patch is merged upstream and is available in >= openstack-neutron-2015.1.1-1.el7ost Hi Ihar, We can't close this bug because of the original one that still reproduces for us. Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1228176 The latest build still works with dnsmasq-2.66-13.el7_1.src.rpm The bug Toni refers to is in VERIFIED. Verified on the latest kilo puddle
[root@dell-c6220-11 ~(keystone_admin)]# rpm -qa |grep dnsmasq
dnsmasq-2.66-14.el7_1.x86_64
dnsmasq-utils-2.66-14.el7_1.x86_64
[root@dell-c6220-11 ~(keystone_admin)]# rpm -qa |grep neutron
openstack-neutron-common-2015.1.1-6.el7ost.noarch
openstack-neutron-2015.1.1-6.el7ost.noarch
openstack-neutron-ml2-2015.1.1-6.el7ost.noarch
python-neutronclient-2.4.0-2.el7ost.noarch
openstack-neutron-lbaas-2015.1.1-1.el7ost.noarch
python-neutron-2015.1.1-6.el7ost.noarch
openstack-neutron-fwaas-2015.1.1-1.el7ost.noarch
python-neutron-lbaas-2015.1.1-1.el7ost.noarch
openstack-neutron-openvswitch-2015.1.1-6.el7ost.noarch
python-neutron-fwaas-2015.1.1-1.el7ost.noarch
VM nic for example:
[root@host-192-168-1-4 ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1400
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2003:db3::f816:3eff:fe01:971d prefixlen 64 scopeid 0x0<global>
inet6 2002:db2::f816:3eff:fe01:971d prefixlen 64 scopeid 0x0<global>
inet6 2001:db1::f816:3eff:fe01:971d prefixlen 64 scopeid 0x0<global>
inet6 fe80::f816:3eff:fe01:971d prefixlen 64 scopeid 0x20<link>
ether fa:16:3e:01:97:1d txqueuelen 1000 (Ethernet)
RX packets 531 bytes 50089 (48.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 319 bytes 30000 (29.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
https://tcms.engineering.redhat.com/run/255169/
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:1866 |