Bug 894839 - Change Quantum DHCP agent to use RPC rather than notifications
Summary: Change Quantum DHCP agent to use RPC rather than notifications
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-quantum
Version: 2.0 (Folsom)
Hardware: All
OS: Linux
medium
medium
Target Milestone: snapshot1
: 3.0
Assignee: Gary Kotton
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-13 20:12 UTC by Perry Myers
Modified: 2016-04-26 14:37 UTC (History)
4 users (show)

Fixed In Version: openstack-quantum-2013.1.1-2.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-29 15:04:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0878 0 normal SHIPPED_LIVE Red Hat OpenStack 3.0 ("Grizzly") Preview bug fix and enhancement update 2013-05-29 19:01:24 UTC

Description Perry Myers 2013-01-13 20:12:41 UTC 
Change Quantum DHCP agent to use RPC rather than notifications
Comment 1 Gary Kotton 2013-05-14 08:43:23 UTC 
This is part of the Grizzly release.
Comment 4 Rami Vaknin 2013-05-23 19:58:50 UTC 
Could you please specify what should be tested here? Does basic DHCP functionality imply that RPC works well?
Comment 5 Perry Myers 2013-05-26 14:29:27 UTC 
(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.
Comment 6 Gary Kotton 2013-05-26 16:31:48 UTC 
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.
Comment 7 Rami Vaknin 2013-05-28 09:32:46 UTC 
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.
Comment 9 errata-xmlrpc 2013-05-29 15:04:01 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2013-0878.html
Note You need to log in before you can comment on or make changes to this bug.