Thanks for taking care of the first item.
For the second, it depends and has two uses i could think of:
1) For port security, as discussed in another thread we will need to add
the mac-ip pairs, but this of course
can be resolved by adding this to the port_security field.
2) To construct the L3 pipeline, you will need to understand to which
chassis/port to send a L3 traffic somehow.
and for that you will need the mapping between the lport and ip
(Of course that depends on the L3 design, but i really wonder how to do
it otherwise)
On Wed, Jul 15, 2015 at 12:52 AM, Ben Pfaff <b...@nicira.com> wrote:
> On Wed, Jul 08, 2015 at 04:23:09PM +0300, Gal Sagie wrote:
> > First, i think everyone would love to hear if there are any plans or any
> > first ideas
> > regarding the L3 design.
> >
> > Second, i would like to talk about what currently is available in the
> > schema and how it differs
> > from Openstack Neutron.
> >
> > 1. The logical router port has no interface IP, from the description i
> > understand that the
> > 'network' is meant to describe the entire subnet range but we still
> > need an IP that is used
> > as the default gateway of the logical switch (or network in terms of
> > neutron)
> > (This IP is configurable in Neutron)
>
> This does seem like an omission. I'll send a patch.
>
> > 2. Currently there is no IP information for logical ports in the NB
> schema
>
> Is it useful?
>
--
Best Regards ,
The G.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
