Bug 1335964 - [RFE] IPv6 enablement in Ironic
Summary: [RFE] IPv6 enablement in Ironic
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M2
: 12.0 (Pike)
Assignee: Derek Higgins
QA Contact: Dan Yasny
URL:
Whiteboard:
Depends On: 1298313 1443139 1513945
Blocks: 1307054 1442136 1473541
TreeView+ depends on / blocked
 
Reported: 2016-05-13 16:20 UTC by Keith Basil
Modified: 2018-02-05 19:02 UTC (History)
13 users (show)

Fixed In Version: openstack-ironic-8.0.1-0.20170511110442.623eaa0.el7ost
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 20:41:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 458506 0 None MERGED Update auto-addresses on MAC change 2020-09-09 13:15:29 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Keith Basil 2016-05-13 16:20:00 UTC
The BZ is to track IPv6 enablement of the Ironic services.  Ironic is one of the OpenStack services with limited IPv6 support.  But there are some things we can do to get IPv6 enabled:

1. Run the Ironic API with Apache + mod_wsgi sounds like we should support it, see: http://docs.openstack.org/developer/ironic/deploy/install-guide.html#configuring-ironic-api-behind-mod-wsgi

2. Lucas has written up an early vision document here:
https://wiki.openstack.org/wiki/Ironic/IPv6

The only part in the code that required a change is already merged (see the neutron bits in the wiki page). Now the rest depends on the hardware capabilities and configuration of external components such as TFTP with IPv6, UEFI for PXE with IPv6 and the BMC should support IPv6.

Comment 2 Lucas Alvares Gomes 2016-05-16 09:43:36 UTC
Thanks for this BZ Basil,

As stated in the bug description, I believe the only thing we need to do now is test it. Code-wise this change seems completed.

Comment 3 Lucas Alvares Gomes 2016-09-13 10:55:47 UTC
(In reply to Lucas Alvares Gomes from comment #2)
> Thanks for this BZ Basil,
> 
> As stated in the bug description, I believe the only thing we need to do now
> is test it. Code-wise this change seems completed.

To clarify this comment, what I mean here is that the code _in Ironic_ should be completed. We still need to deal with enabling support for IPv6 in iPXE if it's not enabled (by default upstream it's disabled), TFTP configuration, and maybe other things.

I've tried to list some possible stuff here: https://wiki.openstack.org/wiki/Ironic/IPv6

Comment 5 Dmitry Tantsur 2016-12-06 15:04:02 UTC
This seems to be implemented, and should be just tested.

Comment 8 Dmitry Tantsur 2017-01-11 12:02:18 UTC
Even though we might figure out ironic bits relatively soon, we still have problems with dnsmasq, so deferring this RFE till Pike.

Comment 12 Derek Higgins 2017-03-06 12:32:39 UTC
The current status is that IPv6 deployments with ironic work. the problem is how we setup dhcpv6 in neutron. dnsmasq has checks that don't allow certain IDs to change during the provisioning.

described here
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2017q1/011267.html

I'm hoping to patch dnsmasq if it looks like a patch would be acceptable.

Comment 16 Ramon Acedo 2017-04-18 09:33:19 UTC
Adding https://review.openstack.org/#/c/447538/ as it's a requirement to bypass the dnsmasq issue described in comment #12

Comment 17 Derek Higgins 2017-04-25 14:20:00 UTC
patch was reverted,   OpenStack gerrit 458506 is take 2

Comment 24 Dan Yasny 2017-11-24 16:38:39 UTC
Tested manually and all TCs passed

Comment 27 errata-xmlrpc 2017-12-13 20:41:55 UTC
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/RHEA-2017:3462


Note You need to log in before you can comment on or make changes to this bug.