Open Stack

Yes. So we can define multiple logical switches per network and ovn keeps
vlan maps that ovs agent used to maintain and do the tunneling. My
confusion was from lport-add command that did not have host info, so if
there is no neutron, the cms has to maintain the host to lport association
and we can't query from NB-DB. Makes sense.

-Murali

On Fri, Oct 2, 2015 at 11:46 AM, Russell Bryant <rbryant at redhat.com> wrote:

> On 10/02/2015 02:26 PM, Murali R wrote:
> > Hi Russell,
> >
> > Thank you these are really good. Had a quick question. When you create a
> > logical switch in your first script (line 23) - at what point is it
> > associated with br-int ? Is it on line 45? So I can create any switch
> > and when I associated logical port it associates logical switch ? Or is
> > there a different way we can associate logical-phy switches? I was
> > looking to get the logical associations during startup initialization.
>
> To clarify, I believe you're talking about the first script from the
> tutorial [1], which is:
>
>
> https://github.com/openvswitch/ovs/blob/master/tutorial/ovn/env1/setup.sh
>
> Most of that script is all configuring logical topology.  OVN does
> nothing to the network until ovn-controller sees a port appear on br-int
> that maps to a logical port.  This mapping is done by setting the
> "iface-id" to the name of the logical port.
>
> Once ovn-controller has mapped a port on br-int to a logical port, it
> can configure the switch appropriately for that port.
>
> Does that make sense?
>
> [1]
> https://github.com/openvswitch/ovs/blob/master/tutorial/OVN-Tutorial.md
>
> --
> Russell Bryant
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151005/de3c9337/attachment.html>