Red Hat Bugzilla – Bug 894839
Change Quantum DHCP agent to use RPC rather than notifications
Last modified: 2016-04-26 10:37:41 EDT
This is part of the Grizzly release.
Could you please specify what should be tested here? Does basic DHCP functionality imply that RPC works well?
(In reply to Rami Vaknin from comment #4)
> Could you please specify what should be tested here? Does basic DHCP
> functionality imply that RPC works well?
I'll have to defer to the Quantum devs to answer that question.
The basic functionality of the DHCP service needs to be verified.
In Folsom when a subnet was created a notification would be sent and any DHCP agent could pick up the notification.
In Grizzly the agents are registered with the plugin and the communication is done directly with the agent via the standard RPC channels.
Verified on Grizzly installed on RHEL6.4, openstack-quantum-2013.1.1-8.el6ost.
The dnsmasq process has started successfully (after removing libvirt's dnsmasq process) and an instance got his ip.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.