[ovs-build] Fixed: ovn-org/ovn#318 (branch-20.06 - 0db5cbf)
builds at travis-ci.org
Tue Jun 30 12:40:50 UTC 2020
Build Update for ovn-org/ovn
Duration: 20 mins and 25 secs
Commit: 0db5cbf (branch-20.06)
Author: Dumitru Ceara
Message: Split SB Port_Group per datapath.
In order to avoid ovn-controller reinstalling all logical flows that
refer a port_group when some ports are added/removed from the port group
we now change the way ovn-northd populates the Southbound DB Port_Group
Instead of copying NB.Port_Group.name to SB.Port_Group.name we now
create one SB.Port_Group record for every datapath that has ports
referenced by the NB.Port_Group.ports field. In order to maintain the
SB.Port_Group.name uniqueness constraint, ovn-northd populates the field
with the value: <SB.Logical_Datapath.tunnel_key>_<NB.Port_Group.name>.
In specific scenarios we see significant improvements in time to
install/remove all logical flows to/from OVS. One such scenario, in the
BZ referenced below has:
$ ovn-nbctl acl-list pg
from-lport 1001 (inport == @pg && ip) drop
to-lport 1001 (outport == @pg && ip) drop
Then, incrementally, creates new logical ports on different logical
switches, binds them to OVS interfaces and adds them to the port_group.
Measuring the total time to perform the above steps 500 times (for 500
new ports attached to 100 switches, 5 per switch) on a test setup
we observe an improvement of 50% in time it takes to install all
openflow rules when port_groups are split in the SB database.
Suggested-by: Numan Siddique <numans at ovn.org>
Reported-by: Venkata Anil <anilvenkata at redhat.com>
Signed-off-by: Dumitru Ceara <dceara at redhat.com>
Acked-by: Numan Siddique <numans at ovn.org>
Signed-off-by: Mark Michelson <mmichels at redhat.com>
View the changeset: https://github.com/ovn-org/ovn/compare/bad3cc972ed1...0db5cbf65283
View the full build log and details: https://travis-ci.org/github/ovn-org/ovn/builds/703498453?utm_medium=notification&utm_source=email
You can unsubscribe from build emails from the ovn-org/ovn repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=24187664&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the build