Ask Your Question
0

Issue with spawing vm on public network

asked 2017-11-12 23:48:15 -0600

akarki gravatar image

updated 2017-11-12 23:48:35 -0600

Hi, We have installed openstack -pike via kolla-ansible.It is a 2 node node setup where node1 acts as controller,network and compute and node2 just as compute.

While spawing vm in a public network we saw an issue that all vm were being scheduled at node1 and when we tried to spawn vm at node 2 we saw "No valid host found issue".In logs it showed "port binding failed"

there was no issue however in spawning vm in node2 at private network

After adding br-ex in compute node ie node2 the vm in public network started spawning at compute node as well. we came across a bug which removed br-ex from compute node in ocata release.

bug : https://review.openstack.org/#/c/460645/

However in doing so the openstack installation becomes incapable of launching vm in public network . Is there something i am missing.can the vm be spawned at public netwok without br-ex in compute node.

Please help.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-11-13 07:39:30 -0600

Bernd Bausch gravatar image

updated 2017-11-13 07:42:24 -0600

To be connected to a provider network (the external network is a special type of provider network), an instance must run on a node that is connected to that network. See https://docs.openstack.org/neutron/la..., where the bridge is called br-provider instead of br-ex.

How to achieve that in Kolla, though, I can't say.

edit flag offensive delete link more

Comments

Thanks for the answer however according to me even though the compute node is not connect to the external network via br-ex the vm should spawn(not spawning in my case without adding br-ex) but possibly the vm may not have connectivity to external network.Is it not?

akarki gravatar imageakarki ( 2017-11-13 22:03:03 -0600 )edit

The launch fails because the port can't be bound. The port can't be bound because the network connection can't be established. Try launching the instance with --nic none, i.e. without network. It should work.

Bernd Bausch gravatar imageBernd Bausch ( 2017-11-14 02:33:34 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-11-12 23:48:15 -0600

Seen: 21 times

Last updated: Nov 13