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?
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/8776a661a9 189cbc0c4437562 bcd3b6c27f81854 /cloudinit/ sources/ DataSourceEc2. py#L66
[2] https:/ /github. com/canonical/ cloud-init/ blob/919e22dc1d 779f58f03dfd1cf de5ad9dc33a60d1 /cloudinit/ sources/ DataSourceOpenS tack.py# L21