Bug 1042400

Summary: [RFE][neutron]: Quantum Multi-host DHCP and L3
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/quantum-multihost
Whiteboard: upstream_milestone_next upstream_status_needs-code-review upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:18:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 22:09:06 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/quantum-multihost.

Description:

Goal here is to have a DHCP implementation that provides the same properties as nova-network's "multi_host" functionality, where the DHCP server for a particular VM runs directly on the same hypervisor as the VM itself (with the exception of when a VM migrates). 

The main goal of this approach is that you don't need to worry about providing HA for a centralized DHCP agent. 

Note: the downside of this approach is that each DHCP instance consumes an IP, meaning it can reduce the number of available IPs on a subnet (i.e., it probably makes sense to double or triple the size of the subnet when using multi_host, assuming subnets are using "free" RFC 1918 space). 

Specification URL (additional information):

https://docs.google.com/document/d/1Y41g-POd3DLmtFnD6JfKFDvZJikbUvsL0wIi8LFD35U/edit?usp=sharing