Thanks Justin. I have posted the questions there as well, but since most of the
questions are related to OVS I thought people here can also help me understand
its functionality.
Thanks,
Salman
> Subject: Re: [ovs-discuss] OpenStack Quantum plugins
> From: jpet...@nicira.com
> Date: Thu, 26 Apr 2012 14:24:46 -0700
> CC: discuss@openvswitch.org
> To: salma...@live.com
>
> Hi, Salman. There are a few OpenStack/Quantum people on this list, but I
> suspect you'll have better luck on the main OpenStack list:
>
> openst...@lists.launchpad.net
>
> --Justin
>
>
> On Apr 26, 2012, at 2:07 PM, Salman Malik wrote:
>
> >
> > Hi All,
> >
> > I am trying to learn the functionality of Quantum plugins used in
> > OpenStack. I have read through the Quantum Admin Guide and had few
> > basic/quick question about quantum and OVS interaction with it :
> >
> >
> > 1) OVS can have ports in which vNICS can be plugged, so why does it need to
> > use an integration bridge for connecting all VMs on the same node to a
> > network?
> >
> > 2) The OVS quantum plugin seems to implement the core API functions and
> > (viewing the code) I concluded that it just makes maintains the logical
> > mappings e.g. b/w net IDs and VLAN IDs in a database. So how is this
> > mapping implemented on the actual ports of OVS? Is it the OVS quantum agent
> > responsible for directing the packets to correct input/output ports based
> > on the updates that it gets from the database?
> >
> > 3) The quantum admin guide says that the nova client will be the main user
> > of quantum and will interact with it via REST API, so it would be nice if
> > someone can point me to the code (file path name etc.) where this happens.
> >
> > Thanks,
> > Salman
> >
> > PS: What is the purpose of Quantum Manager in this architecture and where
> > should I look for its code?
> > ___
> > discuss mailing list
> > discuss@openvswitch.org
> > http://openvswitch.org/mailman/listinfo/discuss
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss