On 06/28/2012 12:12 AM, Willian Molinari wrote:
Hi folks,
I was discussing with Mark about it too.
Our ISC dhcp agent is using rabbitmq to get the server messages and would be
nice to use the RPC for it. The code for generic-firewall
(https://blueprints.launchpad.net/quantum/+spec/quantum-generic-firewall) will
use RPC as well.
Using RPC we remove this client dependency and avoid rework, so maybe worth
waiting. A lot of code should be done on the agents while RPC is not ready.
I have a number of comments regarding this.
1. The Quantum service is able to support the RPC service. This was made
possible by the integration of the common config code and the rebase
following the support of the global data structure for this (the RPC
code in common config uses the global data structure)
2. With the Quantum agents this is a bit more tricky. At the moment the
agents use an instance of the common config but do not make use of the
global data structure. This still needs to be addressed. It should not
be complicated.
3. A while ago I got the linux bridge up and running with the RPC. This
was using private versions of the common config. Once we are done with
F-2 I will merge this and push so that all can see the usage. My only
concern is #2 above. We just need an elegant way in doing this.
Just want to know your ideas about it.
--
Willian Molinari
(a.k.a PotHix)
________________________________________
From: netstack-bounces+willian.molinari=locaweb.com...@lists.launchpad.net
[netstack-bounces+willian.molinari=locaweb.com...@lists.launchpad.net] on
behalf of Mark McClain [mark.mccl...@dreamhost.com]
Sent: Wednesday, June 27, 2012 5:56 PM
To: netstack@lists.launchpad.net
Subject: [Netstack] DHCP agent review and the client lib requirement
All-
I've had the same conversation with several you about the DHCP agent and the
use of the client lib. I'd thought I move the discussion over here.
The current method It is definitely not my preferred way to solve this problem
long term. For F3, I want to add RPC support to Quantum. Messaging would help
improve the various agents we now have in the codebase. Specifically, it will
help the dhcp agent because it can be more efficient (i.e. won't have to
constantly poll for changes or use the client lib to create a port for
itself).the network.
The implementation posted today requires the client lib. It's how the DHCP
server gets a port for itself and it's why jenkins fails (there isn't a way to
specify a client lib that's not in pypi).
Thoughts?
mark
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
