Chris Wright wrote:
>> Its worth noting that I'm am not aware of any practical benefits or costs
>> to being a member of the quantum team on launchpad...
>
> That was my next question ;) I was not receiving any gerrit watch emails
> and someone suggested I needed to be on the team (I don't believ
Hi Bob,
On 2012-05-09, at 6:26 PM, Robert Kukura wrote:
>>
>> I'm less clear on the need to implement rpc communication between the vif
>> driver and quantum plugin, at least as part of this blueprint. Am I missing
>> a use-case that is not already handled by Quantum's rest interface?
>
> At
On 05/09/2012 03:50 PM, Maru Newby wrote:
> Hi Gary,
>
> +1 for adding a framework for plugin to agent communication via rpc.
>
> Regarding your list of shortcomings, the security of the database connection
> would be easily remedied, but the other arguments are compelling by
> themselves.
>
>
Hi Gary,
Thanks for initiating this. A couple of comments/questions -
1. Do we really need the VIF driver to communicate the agent's identity;
I am referring to the agent ID being sent by the VIF driver in the
message? In general, I am not sure if there is a need to have the VIF
driver send messa
* Dan Wendlandt (d...@nicira.com) wrote:
> Its funny, as just yesterday I was asking the same thing to Jay Pipes, as I
> find it annoying to get an email and have to click approve all the time
> (especially given the up-tick in membership requests). I had assumed all
> PTLs had to do this, but bas
Turns out flipping the bit was easy, once you know to look for it :)
Btw, some of these groups may be used to automatically notify people on
certain launchpad events (e.g., https://launchpad.net/~quantum-bugs), but
I'm not aware of any notifications for the plane "quantum" group,
particularly sinc
Its funny, as just yesterday I was asking the same thing to Jay Pipes, as I
find it annoying to get an email and have to click approve all the time
(especially given the up-tick in membership requests). I had assumed all
PTLs had to do this, but based on the list below, I suspect this is more of
a
Hi Gary,
+1 for adding a framework for plugin to agent communication via rpc.
Regarding your list of shortcomings, the security of the database connection
would be easily remedied, but the other arguments are compelling by themselves.
I'm less clear on the need to implement rpc communication be
Following up from yesterday's meeting on encouraging developers...
Launchpad team policy:
Nova: Open
Swift:Open
Glance: Open
Keystone: Open
Horizon: Open
Cinder: Open
Quantum: Moderated
Any reason for moderating team membership?
thanks,
-c
On 05/09/2012 09:12 AM, Gary Kotton wrote:
>
> On 05/09/2012 03:36 PM, Irena Berezovsky wrote:
>> 4. Agent ID can be generated by using host UUID.
> Thanks - this is certainly an option
Is there only one agent on a given host? I assume this is used to
target rpc messages to a specific agent.
In
Hi,
Please see my inline comments.
Thanks
Gary
On 05/09/2012 03:36 PM, Irena Berezovsky wrote:
Hi Gary,
Great work!
I also express my interest in this blueprint due to the reasons you mentioned.
I would like to address number of points in the proposal.
1. VIF Driver to Quantum Server RPC message
Hi Gary,
Great work!
I also express my interest in this blueprint due to the reasons you mentioned.
I would like to address number of points in the proposal.
1. VIF Driver to Quantum Server RPC messages: should it use existing APIs or
requires new APIs as code or extension?
2. VIF Un-Plug flow: H
Hi,
I have added a very high level description on how to address the issue.
This can be seen at:
https://docs.google.com/document/d/1MbcBA2Os4b98ybdgAw2qe_68R1NG6KMh8zdZKgOlpvg/edit
Comments will be greatly appreciated.
Questions:
1. Do we want agents to be backward compatible (that is, still m
Hi,
First and foremost I think that it was great chatting about the reviews
last night. A few days ago Maru opened a bug
https://bugs.launchpad.net/quantum/+bug/995283. This was addressed in
https://blueprints.launchpad.net/openstack/?searchtext=man-support (it
was based on the nova support).
14 matches
Mail list logo
