Some thought has been given to this. See https://bugs.launchpad.net/neutron/+bug/1460177
I like the third option, a well-known name using DNS. On Thu, Sep 03, 2015, Kevin Benton <blak...@gmail.com> wrote: > I think that's different than what is being asked here. That patch appears to > just add IPv6 interface information if it's available in the metadata. This > thread is about getting cloud-init to connect to an IPv6 address instead of > 169.254.169.254 for pure IPv6 environments. > > On Thu, Sep 3, 2015 at 11:41 AM, Joshua Harlow <harlo...@outlook.com > <mailto:harlo...@outlook.com>> wrote: > > I'm pretty sure this got implemented :) > > http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/1042 > > <http://bazaar.launchpad.net/%7Ecloud-init-dev/cloud-init/trunk/revision/1042> > and https://bugs.launchpad.net/cloud-init/+bug/1391695 > > That's the RHEL support, since cloud-init translates a ubuntu style > networking style the ubuntu/debian style format should also work. > > > Steve Gordon wrote: > > ----- Original Message ----- > > From: "Kevin Benton"<blak...@gmail.com <mailto:blak...@gmail.com>> > > When we discussed this before on the neutron channel, I thought > it was > because cloud-init doesn't support IPv6. We had wasted quite a bit > of time > talking about adding support to our metadata service because I was > under > the impression that cloud-init already did support IPv6. > > IIRC, the argument against adding IPv6 support to cloud-init was > that it > might be incompatible with how AWS chooses to implement IPv6 > metadata, so > AWS would require a fork or other incompatible alternative to > cloud-init in > all of their images. > > Is that right? > > > That's certainly my understanding of the status quo, I was enquiring > primarily to check it was still accurate. > > -Steve > > On Thu, Sep 3, 2015 at 7:30 AM, Sean M. Collins<s...@coreitpro.com > <mailto:s...@coreitpro.com>> wrote: > > It's not a case of cloud-init supporting IPv6 - The Amazon EC2 > metadata > API defines transport level details about the API - and > currently only > defines a well known IPv4 link local address to connect to. No > well known > link local IPv6 address has been defined. > > I usually recommend config-drive for IPv6 enabled clouds due > to this. > -- > Sent from my Android device with K-9 Mail. Please excuse my > brevity. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > -- > Kevin Benton > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev