if you specify an different address (for example .3 using the --gateway parameter) it will give that to the network node. (note that you should probably also mark that address reserved in the db so nova doesn't try to give it out -- update fixed_ips set reserved=1 where address='XXX.XXX.XXX.3')
Another option is to create the network with multi_host=True and each compute/network node should get a different address and it will leave .1 and .2 unused. Note that in this version you need to run nova-network on every compute node. Vish On Nov 2, 2012, at 9:37 AM, Joe Warren-Meeks <[email protected]> wrote: > Hi guys > > I'm struggling with VLAN Manager in Nova. > > I want to have 3 VLANs, one for each project. These ranges have been created > in my network and the tagged ports are connected to my server. > > I want to create VMs that just take an IP from these networks and get bridged > on to the network. > > The problem I keep finding is that using nova-manage to create the network > ends up with the compute node using the .1 address, which is actually > configured on the router. > > I don't want nova to do anything clever, just create the instance, inject the > IP and bridge the instance on to the VLAN. > > Any pointers on how I can do that? > > Kind regards > > -- joe. > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
