Re: [openstack-dev] [Neutron] cloud-init IPv6 support

, Kevin M's message of 2015-09-08 14:44:35 -0700: > > How does that work with neutron private networks? > > > > Thanks, > > Kevin > > > > From: Clint Byrum [cl...@fewbar.com] > > Sent: Tuesday, September 08, 2015

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron] cloud-init IPv6 support Neutron already offers a DNS server (within the DHCP namespace, I think). It does forward on non-local queries to an external DNS server, but it already serves local

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Excerpts from Nir Yechiel's message of 2014-07-07 09:15:09 -0700: > AFAIK, the cloud-init metadata service can currently be accessed only by > sending a request to http://169.254.169.254, and no IPv6 equivalent is > currently implemented. Does anyone working on this or tried to address this >

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

How does that work with neutron private networks? Thanks, Kevin From: Clint Byrum [cl...@fewbar.com] Sent: Tuesday, September 08, 2015 1:35 PM To: openstack-dev Subject: Re: [openstack-dev] [Neutron] cloud-init IPv6 support Excerpts from Nir Yechiel's

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

m: Clint Byrum [cl...@fewbar.com] > Sent: Tuesday, September 08, 2015 1:35 PM > To: openstack-dev > Subject: Re: [openstack-dev] [Neutron] cloud-init IPv6 support > > Excerpts from Nir Yechiel's message of 2014-07-07 09:15:09 -0700: > > AFAIK, the cloud-init metadata service can cur

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

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 wrote: > I think that's different than what is being asked here. That patch appears to > just add

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Thanks for pointing that out. I like the DNS option too. That has to be done carefully though to make sure it's not easy for an attacker to get the name of the DNS entry that the instance tries to look up. On Fri, Sep 4, 2015 at 10:53 AM, Henry Gessau wrote: > Some thought has

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

questions) Subject: Re: [openstack-dev] [Neutron] cloud-init IPv6 support Thanks for pointing that out. I like the DNS option too. That has to be done carefully though to make sure it's not easy for an attacker to get the name of the DNS entry that the instance tries to look up. On Fri, Sep 4

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

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

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

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

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

I'm pretty sure this got implemented :) http://bazaar.launchpad.net/~cloud-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

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

- Original Message - > From: "Kevin Benton" > > 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

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

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

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

at 12:10 PM > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, > "CARVER, PAUL" <pc2...@att.com<mailto:pc2...@att.com>> > Subject: Re: [openstack-dev]

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On Mon, Jul 07, 2014 at 03:29:31PM EDT, Scott Moser wrote: I think it's also important to realize that the metadata service isn't OpenStack invented, it's an AWS API. Which means I don't think we really Thats incorrect. The metadata service that lives at http://169.254.169.254/ and

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On 14 July 2014 12:57, Collins, Sean sean_colli...@cable.comcast.com wrote: The URL structure and schema of data within may be 100% openstack invented, but the idea of having a link local address that takes HTTP requests and returns metadata was (to my knowledge) an Amazon EC2 idea from the

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

A bit more... I have OpenStack IceHouse with Trusty up and running, *almost* in an IPv6-Only environment, *there is only one place* that I'm still using IPv4, which is: 1- For Metadata Network. This means that, soon as OpenStack enables Metadata over IPv6, I'll kiss goodbye IPv4. For real, I

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

- Original Message - A bit more... I have OpenStack IceHouse with Trusty up and running, *almost* in an IPv6-Only environment, *there is only one place* that I'm still using IPv4, which is: 1- For Metadata Network. This means that, soon as OpenStack enables Metadata

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

I haven’t heard of anyone addressing this, but it seems useful. Vish On Jul 7, 2014, at 9:15 AM, Nir Yechiel nyech...@redhat.com wrote: AFAIK, the cloud-init metadata service can currently be accessed only by sending a request to http://169.254.169.254, and no IPv6 equivalent is currently

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

What's the use case for an IPv6 endpoint? This service is just for instance metadata, so as long as a requirement to support IPv4 is in place, using solely an IPv4 endpoint avoids a number of complexities: - Which one to try first? - Which one is authoritative? - Are both required to be present?

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On 7 July 2014 10:43, Andrew Mann and...@divvycloud.com wrote: What's the use case for an IPv6 endpoint? This service is just for instance metadata, so as long as a requirement to support IPv4 is in place, using solely an IPv4 endpoint avoids a number of complexities: - Which one to try

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Andrew Mann wrote: What's the use case for an IPv6 endpoint? This service is just for instance metadata, so as long as a requirement to support IPv4 is in place, using solely an IPv4 endpoint avoids a number of complexities: The obvious use case would be deprecation of IPv4, but the question

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On 07/07/2014 02:31 PM, Ian Wells wrote: On 7 July 2014 10:43, Andrew Mann and...@divvycloud.com mailto:and...@divvycloud.com wrote: What's the use case for an IPv6 endpoint? This service is just for instance metadata, so as long as a requirement to support IPv4 is in place,

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On 7 July 2014 11:37, Sean Dague s...@dague.net wrote: When it's on a router, it's simpler: use the nexthop, get that metadata server. Right, but that assumes router control. It does, but then that's the current status quo - these things go on Neutron routers (and, by extension, are

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

:26 AM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron] cloud-init IPv6 support Andrew Mann wrote: What's the use case for an IPv6 endpoint? This service is just

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

@lists.openstack.orgmailto:openstack-dev@lists.openstack.org, CARVER, PAUL pc2...@att.commailto:pc2...@att.com Subject: Re: [openstack-dev] [Neutron] cloud-init IPv6 support It wouldn’t be sufficient for OpenStack to support an IPv6 metadata address as long as most tenants are likely to be using

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On Mon, 7 Jul 2014, CARVER, PAUL wrote: Andrew Mann wrote: What's the use case for an IPv6 endpoint? This service is just for instance metadata, so as long as a requirement to support IPv4 is in place, using solely an IPv4 endpoint avoids a number of complexities: The obvious use case

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On Mon, 7 Jul 2014, Sean Dague wrote: Right, but that assumes router control. In general, anyone doing singlestack v6 at the moment relies on config-drive to make it work. This works fine but it depends what cloud-init support your application has. I think it's also important to

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

On 7 July 2014 12:29, Scott Moser smo...@ubuntu.com wrote: I'd honestly love to see us just deprecate the metadata server. If I had to deprecate one or the other, I'd deprecate config drive. I do realize that its simplicity is favorable, but not if it is insufficient. The question of