On Fri, Jul 31, 2015 at 01:14:44PM -0400, Russell Bryant wrote:
> Introduce a new logical port type called "localnet". A logical port
> with this type also has an option called "network_name". A "localnet"
> logical port represents a connection to a locally accessible network.
> ovn-controller will use the ovn-bridge-mappings configuration to
> figure out which patch port on br-int should be used for this port.
>
> Signed-off-by: Russell Bryant <rbry...@redhat.com>
Since this reserves a new register for OVN, we should remove that
register from the logical pipeline symbol table (see the loop near the
beginning of symtab_init() in pipeline.c) so that logical flows can't
screw with it.
Maybe the new field should be declared in pipeline.h with the others (my
tunnel key series adds MFF_LOG_DATAPATH here too). It's not really a
logical pipeline field, but it might still make sense to group these
together.
"sparse" spotted that these "be64"s in physical_run() should be "be32"s:
struct ofpact_set_field *sf =
ofpact_put_SET_FIELD(&ln_flow->ofpacts);
sf->field = mf_from_id(MFF_OVN_FLAGS);
sf->value.be64 = htonl(OVN_FLAG_LOCALNET);
sf->mask.be64 = OVS_BE64_MAX;
I'm not sure I correctly understand the model for using these. Maybe
you can flesh out an example to help me. Suppose I have a pair of
hypervisors A and B, and each HV has two VMs (A1 and A2, B1 and B2), and
all four of the VMs are connected to the same Neutron provider network.
How many OVN Logical_Switches would I have and what would their
membership look like? On each HV, what interfaces would be attached to
br-int?
Thanks a lot,
Ben.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
