On Tue, Mar 1, 2016 at 11:03 PM, Justin Pettit <jpet...@ovn.org> wrote:
> > > On Mar 1, 2016, at 6:44 PM, Russell Bryant <russ...@ovn.org> wrote: > > > > FWIW, this is what I was trying to figure out with my questions as well. > > It does seem like there is something missing here. > > > > With localnet ports today, a single logical port maps to a physical port > on > > N chassis. It's not 1 to 1, which this model seems to assume. > > Is that true? I think the documentation implies that, but I'm not sure if > the implementation does. In the Logical_Port table, there can be zero or > one "phys_endpt". If someone doesn't populate "phys_endpt" (or sets "type" > to "vlan" and "ingress_encap" to the vlan id), then it should have the > behavior that you describe. I spoke with Darrell at some length today, and > I think he'll be sending out a revised version. > > I think the final version is supposed to behave like this: If > "phys_endpt" is empty or exists with only a vlan tag, then it will behave > just like it does now: the bindings will happen on any hypervisor with the > appropriate "external-ids:ovn-bridge-mappings" set. If "phys_endpt" > specifies a particular chassis, then it would only be instantiated there. > (I think this latter case could be useful when creating a software gateway.) > > I need to read the localnet implementation and Darrell's proposed changes > more carefully, but does the previous paragraph sound reasonable? I'll dig > into it more tomorrow, but please let me know if I'm way off course. > Yes, this sounds reasonable. Thanks for helping clarify! -- Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
