Comment 3 for bug 2007938
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
So this is also a problem with IPv4, but this protocol doesn't have a mechanism to detect duplicated IP addresses. Let's keep for now the focus on the IPv6 problem.
If we detect a duplicated IPv6 address on this network, that means there is other metadata agent spawned (on other DHCP agent). In that case, we should skip the configuration of the metadata server. That means we won't have HA for metadata in this network. If the DHCP agent with the active metadata server does down, we need to be able to, in the other DHCP agents, configure the IPv6 address and spawn a metadata server.
This mechanism (I don't know now how to implement it) will periodically check the existence of this IPv6 metadata address on other interface. If that is not present, then configure it and spawn the metadata server.
Do you have other alternative? Because having multiple metadata IPs is not an option, I think. And having something like VRRP is, IMO, over-engineering.