Re: [Netstack] Scalable agents

On Tue, 2012-07-10 at 18:51 +0300, Gary Kotton wrote: > Hi, > I have posted the first patch for this blueprint > (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms) > - https://review.openstack.org/#/c/9591. I have marked this as "Work > in progress". I have tested on Fedora with

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

t.com>>; netstack@lists.launchpad.net <mailto:netstack@lists.launchpad.net> *Sent:* Thursday, 10 May 2012, 18:38 *Subject:* Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms) Hi Gary, I appreciate the effort you'

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

gt;> From: Maru Newby >> To: gkot...@redhat.com >> Cc: Christopher Wright ; netstack@lists.launchpad.net >> Sent: Thursday, 10 May 2012, 18:38 >> Subject: Re: [Netstack] Scalable >> Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms) >>

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

n > > From: Maru Newby > To: gkot...@redhat.com > Cc: Christopher Wright ; netstack@lists.launchpad.net > Sent: Thursday, 10 May 2012, 18:38 > Subject: Re: [Netstack] Scalable > Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms) > > Hi Gary,

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

d.net >Sent: Thursday, 10 May 2012, 18:38 >Subject: Re: [Netstack] Scalable >Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms) > > >Hi Gary, > > >I appreciate the effort you've put into condensing the options. > > >I agree with y

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

On 05/10/2012 12:46 PM, Dan Wendlandt wrote: > > > On Thu, May 10, 2012 at 12:05 AM, Gary Kotton > wrote: > > On 05/10/2012 12:55 AM, Sumit Naiksatam (snaiksat) wrote: > > Hi Gary, > > Thanks for initiating this. A couple of comments/questions -

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

Hi Gary, I appreciate the effort you've put into condensing the options. I agree with your suggestion that option 1 is a good starting point. How will the agent discover changes to tap devices? Can an agent register for events from linux/kvm or xen, or would the agent just poll? For all I kn

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

On Thu, May 10, 2012 at 12:05 AM, Gary Kotton wrote: > On 05/10/2012 12:55 AM, Sumit Naiksatam (snaiksat) wrote: > >> 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

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

On Thu, May 10, 2012 at 5:23 AM, Robert Kukura wrote: > > > Hi Maru, > > I agree a REST interface could do the job. I misinterpreted your email > as arguing that the VIF driver should just create the tap device and the > agent should poll to discover the tap device, as is done now. > I'm not sur

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

Hi, Below is a table that lists a number of options, a short description, their advantages and disadvantages. Hopefully this can give an idea of the scope and complexity. *Option* *Description* *Advantages* *Disadvantages* 1 .Agent driving data retrieval from plugin Th

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

On 05/09/2012 11:23 PM, Maru Newby wrote: > 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 alre

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

On 05/09/2012 10: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. I'm less clear o

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

On 05/10/2012 03:05 AM, Gary Kotton wrote: >> 2. One model I was thinking of (which is kind of inline with the >> existing agent implementations), is where the agents are smart, and they >> know what to do in response to changes in the state of the logical >> Quantum resources. In such cases, the Q

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

On 05/10/2012 12:55 AM, Sumit Naiksatam (snaiksat) wrote: 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 n

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

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

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

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. > >

Re: [Netstack] Scalable Agents(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

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

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

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

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

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

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

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

Re: [Netstack] Scalable Agents (https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms)

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