Support for metadata over IPv6

[Slawek Kaplonski]

OpenStack Neutron recently added support to Metadata over IPv6. See spec https://specs.openstack.org/openstack/neutron-specs/specs/ussuri/metadata-add-ipv6-support.html

It would be great if cloud-init would add support for that too. I'm not cloud-init expert at all and I have no idea how it could be implemented but I think it's good to at least propose that here so maybe someone will want to work on that.

[Lucas Albuquerque Medeiros de Moura (lamoura)]

Thanks for filling this feature request

[Maximilian Stinsky (mstinsky)]

Greetings,

I just stumbled upon this feature request, as we upgraded our openstack setup to a version which supports metadata over ipv6. While testing it we found that cloud-init does not support this without manually setting the metadata_url over user-data.

Maybe I am too naive, but this does not look to be the hardest implementation if it would be done like in ec2 with a metadata url list which is just tested one by one [1].

Could this be done the same way in openstack where we change [2] to be a list of possible metadata addresses?

Any opinions on this?

[1] https://github.com/canonical/cloud-init/blob/8776a661a9189cbc0c4437562bcd3b6c27f81854/cloudinit/sources/DataSourceEc2.py#L66

[2] https://github.com/canonical/cloud-init/blob/919e22dc1d779f58f03dfd1cfde5ad9dc33a60d1/cloudinit/sources/DataSourceOpenStack.py#L21

[James Falcon (falcojr)]

Yes, given that we recently completed our first dual-stack implementation, it should not be hard to add another.

[Slawek Kaplonski (slaweq)]

It seems to be fixed with https://github.com/canonical/cloud-init/pull/1805 now. Thx a lot

[Alberto Contreras (aciba)]

This bug is believed to be fixed in cloud-init in version 23.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3816