Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Most of the cloud images are configured with only 1 NIC in cloud-int. So, when a VM boots, it comes up with only 1 NIC irrespective of the number of networks you attach to the VM.

So, the common way people get around this limitation is to create a snapshot of VM with multiple NICs and upload to glance.

Please check the below link to create snapshot of multi NIC image.

[https://leadwithoutatitle.wordpress.com/2017/07/06/how-to-create-a-multi-nic-ubuntu-cloud-image/]

As far as default route is concerned, let's say you have 2 networks and you've set gateway for one of the networks and you attach the 2 networks to VM while launching, the VM will the default route as the gateway set for first network.

Most of the cloud images are configured with only 1 NIC in cloud-int. cloud-init. So, when a VM boots, it comes up with only 1 NIC irrespective of the number of networks you attach to the VM.

So, the common way people get around this limitation is to create a snapshot of VM with multiple NICs and NICs, upload to glance.glance and use this to launch VMs.

Please check the below link to create snapshot of multi NIC image.

[https://leadwithoutatitle.wordpress.com/2017/07/06/how-to-create-a-multi-nic-ubuntu-cloud-image/]

As far as default route is concerned, let's say you have 2 networks and you've set gateway for one of the networks and you attach the 2 networks to VM while launching, the VM will have the default route as the gateway set for first network.