Hi,

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=192.168.0.201

The 2 networks are fixed IPs pools:

id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
1 10.0.0.0/24 None 10.0.0.2 8.8.4.4 None None None 3b22fce3-2a00-411e-9706-9c9150a92608 2 192.168.0.200/29 None 192.168.0.201 192.168.0.1 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=192.168.0.200/29 --bridge=br1 --dns1=192.168.0.1

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 192.168.0.200/29 pool, that's why the '--nic... v4-fixed-ip=' in the boot command above.

I also run a "management" network on 192.168.1.0/24 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 192.168.0.200/29 address is assigned to my instances.

Thanks.