On Tue, Jun 5, 2012 at 9:57 PM, Irena Berezovsky <ire...@mellanox.com>wrote:
> Rami,Dan**** > > Seems that this question may be relevant to nova guys. It’s a question of > design in first place. Is it correct to expose networking operation > details to the nova-compute or it should be fully encapsulated inside > nova-network?**** > > Dan, how is it going to be managed in Folsom where QuantumManager will be > dropped and nova parity will be achieved by using Quantum Client to call > Quantum APIs? > Hi Irena, Once our changes for Folsom are complete, nova-compute will leverage the quantum client code to call Quantum APIs directly. Dan > **** > > ** ** > > Irena**** > > ** ** > > ** ** > > *From:* Rami Cohen [mailto:ramic.h...@gmail.com] > *Sent:* Tuesday, June 05, 2012 11:47 PM > *To:* Dan Wendlandt > *Cc:* Irena Berezovsky; netstack@lists.launchpad.net > *Subject:* Re: [Netstack] Nova & Quantum integration**** > > ** ** > > Dan, > Thanks for your quick and detailed response. > While I understand that the agent is used for enhanced services while the > driver is just for VM provisioning/destroying/restarting, I still think > that reflecting the values returned by quantum API to the Quantum driver > may be beneficial and it requires minimum effort (just returns the > parameters by Nova network to the Nova compute. In particular, it may save > a lot of (development and QA) effort when the agent is not needed. > What do you think? > > RamiC > > **** > > On Tue, Jun 5, 2012 at 9:30 PM, Dan Wendlandt <d...@nicira.com> wrote:**** > > Rami,**** > > ** ** > > A quantum agent configuring the vswitch can get very complex (especially > when adding things like security groups, QoS policies, etc. etc.). We do > not want to complicate Nova by having it perform all operations on the > vswitch. **** > > ** ** > > Also, the Quantum agent may need to reconfigure the vswitch at any point, > resulting from a change made to the quantum API (e.g., putting a quantum > port in 'admin-down' state). Nova really only does anything network > related when a VM is created, destroyed, or restarted. Thus, we have nova > only do the absolute simplest networking step of creating the device > presenting the vNIC, and informing the vswitch about it (and the > corresponding tear-down). **** > > ** ** > > The OVS + Linux Bridge plugins have agents that you could use as a model. > **** > > ** ** > > Dan**** > > ** ** > > On Tue, Jun 5, 2012 at 10:22 AM, Rami Cohen <ramic.h...@gmail.com> wrote:* > *** > > Irena, > In current Quantum/Nova Implementation and openvswitch plugin the VIF > driver performs the actual vif connectivity to the vswitch (using > 'ovs-vsctl'). This make sense since it reuse existing Nova messaging > mechanism and the fact that the Nova compute is already deployed on each > node (so why to deploy, maintain and communicate with additional agent?). I > would think that the best way is to enable quantum to pass parameters to > the VIF driver. > What do you think?**** > > ** ** > > **** > > > RamiC > > the Nova compute is already deployed on each host) the fact that the > parameters of quantum does not sent back to the driver **** > > ** ** > > On Tue, Jun 5, 2012 at 2:35 PM, Irena Berezovsky <ire...@mellanox.com> > wrote:**** > > Rami,**** > > Following the recent discussions on the mailing list regarding the > responsibility of the VIF driver, seems that it should be very thin and > network provisioning should be handled by Quantum Plugin Agent as in > OpenvSwitch and LinuxBridge plugins.**** > > I have similar need to get attributes for the attached network/ port and > seems that the way to do it is via API extension.**** > > You can see the details in the following mailing thread: **** > > https://lists.launchpad.net/openstack/msg12716.html**** > > **** > > Hope this helps,**** > > Irena**** > > *From:* netstack-bounces+irenab=mellanox....@lists.launchpad.net [mailto: > netstack-bounces+irenab=mellanox....@lists.launchpad.net] *On Behalf Of *Rami > Cohen > *Sent:* Tuesday, June 05, 2012 1:14 PM > *To:* netstack@lists.launchpad.net > *Subject:* [Netstack] Nova & Quantum integration**** > > **** > > Hi, > Is there any mechanism to pass some parameters from Quantum Manager to the > Quantum VIF driver (that is part of the Nova compute)? > In particular, I saw that when Nova network calls Quantum API (create and > attach ports) it ignores the return values sent from the quantum manager, > so there is no formal way to reflect them back to the Nova compute. > > Thanks, > RamiC**** > > > > **** > > -- > RamiC™**** > > ** ** > > -- > Mailing list: https://launchpad.net/~netstack > Post to : netstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~netstack > More help : https://help.launchpad.net/ListHelp**** > > > > **** > > ** ** > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Dan Wendlandt **** > > Nicira, Inc: www.nicira.com**** > > twitter: danwendlandt > ~~~~~~~~~~~~~~~~~~~~~~~~~~~**** > > ** ** > > > > > -- > RamiC™**** > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
