Comment 0 for bug 1719806
Revision history for this message
| Vivekanandan Narasimhan (vivekanandan-narasimhan) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
On both stable/pike and stable/ocata, we performed the following steps:
1. Create a network
2. Create an IPv6 subnet in SLAAC Mode (both RA mode and Address mode)
3. Create a router
4. Attach the IPv6 subnet to the router
3. Now boot VMs with the network-id.
4. Make sure VMs are up and able to communicate via their Global and Link-Local IPv6 addresses.
5. Create an IPv4 subnet on the same network.
After step 5, you will notice that the booted VM neutron ports fixed-ips are not updated with IPv4 subnets automatically.
The user has to manually update the VM Neutron ports via port-update command with the IPv4 subnet-id and then go back to the VM and recycle eth0 after which only the VMs will get the IPv4 address.
If the above set of steps are followed just by swapping the order where we create IPv4 subnets first, then boot VMs, create an IPv6 subnet on the same network, the VM Neutron Ports fixed-ips get updated automatically with the new assigned IPv6 Global addresses on the IPv6 subnet.