DHCP server running on the "public" network interface

In OpenStack, Can I have a DHCP server running on the “public” network interface?

I am having this problem with my Openstack test deployment using Fuel. I am planning to deploy in the following configuration:

  1. Two network interfaces per node.
  2. Several compute nodes, one or more controllers, one Fuel instance.
    • eth0 is connected to my hosting provider’s public network over which I have no control and no access to the upstream router. This network provides internet connectivity to each machine.
    • eth1 is connected to a private LAN.

I have configured all the networks to sit on eth1 except for “public” , which i’ve configured on eth0. But Fuel fails when I ‘verify networks’, because, my provider has a DHCP server on the public network - eth0 - and Fuel finds it during the verification process.

Is there a way for me to allow my configuration to work?

Hey Nikunj, I am not quite sure about Fuel, but you should look at the below options:

1 - Flat DHCP mode:
docs.openstack.org/grizzly/opens … rking.html

2 - VLAN mode:
docs.openstack.org/grizzly/opens … rking.html

In both the above cases you can create subnets from which the DHCP server (dnsmaq) will assign IP addresses.