| 1 |
--- |
| 2 |
issues: |
| 3 |
- | |
| 4 |
The high availability of metadata service on isolated networks is limited |
| 5 |
or non-existent. IPv4 metadata is redundant when the DHCP agent managing |
| 6 |
it is redundant, but recovery is tied to the renewal of the DHCP lease, |
| 7 |
making most recoveries very slow. IPv6 metadata is not redundant at all |
| 8 |
as the IPv6 metadata address can only be configured in a single place at |
| 9 |
a time as it is link-local. Multiple agents trying to configure it will |
| 10 |
generate an IPv6 duplicate address detection failure. |
| 11 |
|
| 12 |
Administrators may observe the IPv6 metadata address in "dadfailed" state |
| 13 |
in the DHCP namespace for this reason, which is only an indication it is |
| 14 |
not highly available. Until a redesign is made to the isolated metadata |
| 15 |
service there is not a better deployment option. See `bug 1953165 |
| 16 |
<https://bugs.launchpad.net/neutron/+bug/1953165>`_ for information. |