-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support pure IPv6 environments (no IPv4) #770
Comments
That's not entirely true - just configure the VMs not to ask for IPv4 addresses. |
I'm not sure it will be enough. |
Indeed, it would be best to use 3 VMs with only IPv6 addresses, just like the customer wants. However, I think it would be a good enough first step to "cheat" a bit, by preparing both ipv4 and ipv6 on the VMs, but using only the IPv6 ones in our code. It may miss a bug or two, but would make sure that all our own fields and arguments support ipv6. It also make it possible to develop the suite before (or in parallel) we fix this Lago issue. |
Currently IPv6 addresses for hosts are supported only appending a fixed prefix to the IPv4 addresses assigned by libvirt DHCP.
See: https://github.com/lago-project/lago/blob/master/lago/providers/libvirt/network.py#L223
Please support also pure IPv6 environments without IPv4 addresses.
The text was updated successfully, but these errors were encountered: