Here, I will explain how FlatDHCPManager works with single-host networking. It is perhaps easier to understand; it also happens to be the default mode you get when installing OpenStack using one of the easy ways (by using the Puppet recipes).
Question #148714 “FlatDHCPManager makes the wrong bridge and ...
Mar 11, 2011 · Are you by any chance using the -- flat -interface option when using FlatDHCPManager ? If so then I think FlatDHCPManager will try to bridge into that interface (this involves moving the IP of that interface to the br100 bridge). Perhaps you can use -- flat -interface=eth1 or use another unused interface (besides using eth0)? -- Just some ideas.
The nova.network.manager Module — nova 13.1.5.dev1 documentation
FlatDHCPManager will start up one dhcp server to give out addresses. It never injects network settings into the guest. It also manages bridges. Otherwise it behaves like FlatManager . Do any initialization that needs to be run if this is a standalone service. Bases: nova.network.manager.NetworkManager. Basic network where no vlans are used.
How to correctly configure nova-compute to use FlatDHCPManager
Feb 25, 2015 · I am trying to deploy Openstack using FlatDHCPManager . I am using MAAS+Juju to deploy all of my nodes (HP Moonshot) running trusty. I want eth1 to be the public interface. Here are the relevant ...
Mar 1, 2017 · Here, I will explain how FlatDHCPManager works with single-host networking. It is perhaps easier to understand; it also happens to be the default mode you get when installing OpenStack using one of the easy ways (by using the Puppet recipes).
Usage or not of neutron-gateway v (s FlatDHCPManager)
Sep 24, 2020 · In the charm “openstack-base” by default it do FlatDHCPManager (option in nova-cloud-controller). What is the good choice for a fresh install in production ? What is the advantage of FlatDHCPManager vs Neutron (via neutron-gateway) ? (I want to use private networks, loadballancer, routers) Regards, thank you in advance for your answers Robin
Apr 10, 2021 · In FlatDHCPManager mode, all instances use one 64-bit global routing prefix. This configuration was tested with virtual machine images that have an IPv6 stateless address auto-configuration capability.