Public bug reported:
EC2 metatdata service is supported by nova metadata service that is
running in the management network. Cloud-init running in the instance
normally accesses the service at 169.254.169.254. Cloud-init can be
configured with metadata_urls other than the default
http://169.254.169.254 to access the service. But such configuration is
not currently supported by openstack. In order for the instance to
access the nova metadata service, neutron provides proxy service that
terminates http://169.254.169.254 and forwards the request to the nova
metadata service. Apparently, this works only when IPv4 is available in
the tenant network. For an IPv6 only tenant work, to continue the
support of this service, the instance has to access it at an IPv6
address. This requires enhancement in Neutron to support it.
A few options have been discussed so far:
-- define a well-known ipv6 link-local address to access the metadata
service.
-- enhance IPv6 RA to advertise the metadata service endpoint to instances.
This would require standards work and enhance cloud-init to support it.
-- define a well-known name for the metadata service and configure
metadata_urls to use the name. The name will be resolved to a datacenter
specific IP address. The corresponding DNS record should be pre-provisioned in
the datacenter DNS server for the instance to resolve the name.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: rfe
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1460177
Title:
Support metadata service with IPv6 only tenant network
Status in OpenStack Neutron (virtual network service):
New
Bug description:
EC2 metatdata service is supported by nova metadata service that is
running in the management network. Cloud-init running in the instance
normally accesses the service at 169.254.169.254. Cloud-init can be
configured with metadata_urls other than the default
http://169.254.169.254 to access the service. But such configuration
is not currently supported by openstack. In order for the instance to
access the nova metadata service, neutron provides proxy service that
terminates http://169.254.169.254 and forwards the request to the nova
metadata service. Apparently, this works only when IPv4 is available
in the tenant network. For an IPv6 only tenant work, to continue the
support of this service, the instance has to access it at an IPv6
address. This requires enhancement in Neutron to support it.
A few options have been discussed so far:
-- define a well-known ipv6 link-local address to access the metadata
service.
-- enhance IPv6 RA to advertise the metadata service endpoint to
instances. This would require standards work and enhance cloud-init to support
it.
-- define a well-known name for the metadata service and configure
metadata_urls to use the name. The name will be resolved to a datacenter
specific IP address. The corresponding DNS record should be pre-provisioned in
the datacenter DNS server for the instance to resolve the name.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1460177/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
