Neutron Static IP

asked 2014-06-17 12:04:58 -0600

marcantonio gravatar image

It occurs to me that, using a provider network and a physical NIC on each compute node, I can statically assign IP's to my instances and forget about DHCP and L3 agent.

Does anyone see a problem with this? Am I losing any of OpenStack's functionality by doing things this way (aside from everything that L3 agent provides)? WIll migrations still work properly?

Will neutron still let me assign virtual NICs to instances if the network they attach to is created with --disable-dhcp?

Thanks, Marc

edit retag flag offensive close merge delete


Any special config needed to run DHCP agent on the compute nodes?

marcantonio gravatar imagemarcantonio ( 2014-06-18 06:09:14 -0600 )edit

nope, but you will need enable_isolated_metadata = True in the dhcp_agent.ini and run the metadata agent on the nodes that run the dhcp agent.

darragh-oreilly gravatar imagedarragh-oreilly ( 2014-06-19 01:26:28 -0600 )edit

I tried this. My VMs get DHCP addresses but I seem to get no response from

marcantonio gravatar imagemarcantonio ( 2014-06-21 14:55:20 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2014-06-18 01:57:47 -0600

darragh-oreilly gravatar image

updated 2014-06-18 02:02:00 -0600

yeah, if you map a neutron network to a physical network that is routed to the outside world, then there is no need for neutron routers/ l3-agents/network nodes. Neutron will still allocate IPs, and do security groups, metadata so I would keep the dhcp stuff. But you don't need a network node to run the dhcp-agents - just run them on the compute nodes. More than one dhcp-agent can serve a network for redundancy.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-06-17 12:04:58 -0600

Seen: 200 times

Last updated: Jun 17 '14