Why are VMs assigned a FIXED IP from every available network? [closed]

asked 2014-07-23 18:12:49 -0600

jfarschman gravatar image

I have a working Grizzly with nova-network (flat DHCP mode) that we use for our development labs and it works great with a single FIXED network. However, it's time to expand. My plan is to have one controller, that can spin up VM in either the old dev lab or on new compute nodes that will use a second FIXED network.

When I add the second network and start a VM in the WebUI (Horizon) the VM grabs an IP from both fixed networks:

nova-manage network create --multi_host='T' 10.17.64.0/24 --num_networks 1 --network_size 256 --fixed_range_v4=10.17.64.0/24 --fixed_cidr=10.17.64.0/24 --bridge_interface=br64 --bridge=br64 --dns1=8.8.8.8 --dns2=8.8.4.4

I tried using the --project_id= argument, but that didn't work.

Is this just a problem with Horizon not allowing me to select a network. It seems that when you don't specify a network when creating a VM it will automatically assign a private IP address from each available nova-network.

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by rbowen
close date 2016-12-07 15:55:35.034095

Comments

This question is about a version of OpenStack which has been EOL'ed. Closing.

rbowen gravatar imagerbowen ( 2016-12-07 15:55:31 -0600 )edit