Interfaces/images binding

[open-cloud]

Interfaces/images binding

[llpeterson]

Is this about being able to auto-detect interfaces after a VM boots... thereby allowing us to add networks after a set of VMs have been created.

[andybavier]

Right now the OpenCloud images bring up eth0 and eth1. In order for boot to succeed, one must be connected to a private network running the metadata server, and one must be connected to a public network (dedicated IP or NAT) so the user can login.

If the VM is connected to more than two networks at boot time, only two will come up at boot and there is a chance that the above constraints may be violated. We should make the process more flexible and robust, e.g., by using cloud-init to bring up all N interfaces.

We can also support adding networks to running VMs if Neutron supports it. We will need to test.

[andybavier]

One solution: use netplugd

http://getcloudify.org/2015/05/18/openstack-neutron-nova-cloud-vm-networking-network-automation-orchestration.html

[sisrael]

I don't know whether this is the right forum to post my question. Please direct me to correct forum if this is not the appropriate place to post this question.

I have used the ansible script https://github.com/andybavier/opencloud-cluster-setup to setup a private cloud with one controller node and one compute. I can create a VM instance on the compute node successfully with public IP address 172.16.0.19 and private IP address 10.0.11.15. But, I cannot ping or ssh into the newly created VM instance. The interface names on the compute node is em1, em2, etc instead of eth0, eth1. I dont' know whether that could cause any problem in accessing the VM instance. Any help to troubleshoot this problem would be greatly appreciated. Thanks in advance.