On Fri, Oct 26, 2018 at 01:39:43AM +0000, Ankur Sharma wrote: > As a part of proposal for distributed virtual routing > for VLAN networks through OVN, this series has code changes > for Layer 2. > > [1] https://mail.openvswitch.org/pipermail/ovs-dev/2018-October/353066.html > [2] > https://docs.google.com/document/d/1uoQH478wM1OZ16HrxzbOUvk5LvFnfNEWbkPT6Zmm9OU/edit?usp=sharing > > This Series: > a. Changes in OVN NB Schema to introduce a logical switch type. > b. Changes in ovn-nbctl to configure a logical switch type. > c. Changes in ovn-northd to process and save a logical switch type. > > Adding a logical switch type would be helpful in following: > a. Debugging, since VLAN backed logical switch is dependent on > localnet ports, hence basic validations like localnet port > configured or not etc., can be done with ease. > > b. Helps with Layer 3 implementation > (https://mail.openvswitch.org/pipermail/ovs-dev/2018-October/353179.html). > > This Patch: > a. By default set network_type as overlay during ls_add handling. > > b. Add a new ovn-nbctl command to set network type of a logical > switch. > ovn-nbctl ls-set-network-type LS_NAME vlan|overlay > > c. Display network type along with logical switch, for example: > # ovn-nbctl ls-list > d94d7531-128b-43a2-bff0-56f2aa2ea878 (bar) (type: overlay) > 531e6f24-f6ae-4ea3-856d-ac986f900770 (foo) (type: vlan) > > d. Unit tests to validate this command > > Signed-off-by: Ankur Sharma <ankur.sha...@nutanix.com>
Usually I'd expect that the network type would be fixed for a given logical network, rather than changing after it is created. Thus, I'd recommend adding an option to ls-add to specify the network type, rather than a new command. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
