Ask Your Question

nova boot dashboard

asked 2013-06-10 18:58:42 -0500

smkr gravatar image

updated 2013-06-11 10:24:39 -0500

fifieldt gravatar image


I can start the VMs from the command line with:

[root@nova ~]# nova boot ostack-vm1 --flavor 3 --image 35f414c9-ad5b-4f95-ba5e-63b8c4a77e60 --nic net-id=3b22fce3-2a00-411e-9706-9c9150a92608 --nic net-id=c6f65c5d-88d5-4984-98a9-6209137ccd55,v4-fixed-ip=

The 2 networks are fixed IPs pools:

id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
1 None None None None 3b22fce3-2a00-411e-9706-9c9150a92608 2 None None None None c6f65c5d-88d5-4984-98a9-6209137ccd55

where the network #2 was created with:

[root@nova ~]# nova-manage network create --label=local-vm --fixed_range_v4= --bridge=br1 --dns1=

so the bridge br1 takes care of routing traffic to the "public" network. I don't want Nova to pick a random/available address from the pool, that's why the '--nic... v4-fixed-ip=' in the boot command above.

I also run a "management" network on that allows me to SSH into the Nova node.

Is there a way to configure Horizon to execute the same command when I create the instance from the Dashboard? It appears that all it does is call 'nova boot' without any networking options. That way I have no control over what address is assigned to my instances.


edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-06-11 04:46:06 -0500

jpichon gravatar image

At this time I don't believe it's possible to decide which fixed ip is assigned to your instance, when booting a new instance from Horizon.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-06-10 18:58:42 -0500

Seen: 690 times

Last updated: Jun 11 '13