| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Make the metadata service available over the IPv6 link-local |
| 5 |
address ``fe80::a9fe:a9fe``. Metadata over IPv6 works on both |
| 6 |
isolated networks and networks with an IPv6 subnet connected |
| 7 |
to a Neutron router as well as on dual-stack and on IPv6-only |
| 8 |
networks. There are no new config options. The usual config |
| 9 |
options (``enable_isolated_metadata``, ``force_metadata``, |
| 10 |
``enable_metadata_proxy``) now control the metadata service over |
| 11 |
both IPv4 and IPv6. This change only affects the guests' access to |
| 12 |
the metadata service over tenant networks. This feature changes |
| 13 |
nothing about how the metadata-agent talks to Nova's metadata service. |
| 14 |
The guest OS is expected to pick up routes from Router Advertisements |
| 15 |
for this feature to work on networks connected to a router. |
| 16 |
At least the following IPv6 subnet modes work: |
| 17 |
|
| 18 |
* ``--ipv6-ra-mode slaac --ipv6-address-mode slaac`` |
| 19 |
* ``--ipv6-ra-mode dhcpv6-stateless --ipv6-address-mode dhcpv6-stateless`` |
| 20 |
* ``--ipv6-ra-mode dhcpv6-stateful --ipv6-address-mode dhcpv6-stateful`` |
| 21 |
|
| 22 |
Please note that the metadata IPv6 address (being link-local) |
| 23 |
is not complete without a zone identifier (in a Linux guest |
| 24 |
that is usually the interface name concatenated after a percent |
| 25 |
sign). Please also note that in URLs you should URL-encode |
| 26 |
the percent sign itself. For example, assuming that the primary |
| 27 |
network interface in the guest is ``eth0`` the base metadata URL is |
| 28 |
``http://[fe80::a9fe:a9fe%25eth0]:80/``. |
| 29 |
upgrade: |
| 30 |
- | |
| 31 |
The metadata over IPv6 feature makes each dhcp-agent restart |
| 32 |
trigger a quick restart of dhcp-agent-controlled metadata-proxies, |
| 33 |
so they can pick up their new config making them also bind to |
| 34 |
``fe80::a9fe:a9fe``. These restarts make the metadata service |
| 35 |
transiently unavailable. This is done in order to enable the metadata |
| 36 |
service on pre-existing isolated networks during an upgrade. Please |
| 37 |
also note that pre-existing instances may need to re-acquire all |
| 38 |
information acquired over Router Discovery and/or DHCP for this |
| 39 |
feature to start working. |