[ovs-build] Still Failing: dceara/ovn#79 (copp-rfc-v1 - 3457f15)

Travis CI builds at travis-ci.org
Thu Oct 10 08:35:14 UTC 2019


Build Update for dceara/ovn
-------------------------------------

Build: #79
Status: Still Failing

Duration: 20 mins and 40 secs
Commit: 3457f15 (copp-rfc-v1)
Author: Dumitru Ceara
Message: Add CoPP (Control Plane Protection).

Add new 'Copp' (Control plane protection) table to OVN Northbound DB:
- this stores mappings between control plane protocol names and meters
  that should be used to rate limit controller-destined traffic for
  those protocols.

Add new 'copp' columns to the following OVN Northbound DB tables:
- Logical_Switch
- Logical_Switch_Port
- Logical_Router
- Logical_Router_Port

This allows defining control plane policies with different
granularities. For example a user can decide to enforce a general
policy for the logical switch but at the same time configure a
different policy on some of the ports of the logical switch.
Control plane protocol policies applied to a logical port take
precedence over the ones defined at logical switch level. For
logical routers and logical router ports we take the same approach.

Add a new 'controller_meter' column to OVN Southbound Logical_Flow
table. This stores an optional string which should correspond to
the Meter that must be used for rate limiting controller actions
generated by packets hitting the flow.

Add CLI commands in 'ovn-nbctl' to allow the user to manage Control
Plane Protection Policies at different levels (logical switch,
logical router, logical port).

Add a new 'ctrl_meter_id' field to 'struct ovn_flow' to be used for
applying meters to flows that trigger controller actions.

Add a new 'ofctrl_add_flow_meter' function to create a new 'ovn_flow'
with an attached controller meter.

Change ofctrl_check_and_add_flow to allow specifying a meter ID for
packets that are punted to controller.

Change consider_logical_flow to parse controller_meter from the logical
flow and use it when building openflow entries.

Add a new 'ctrl_meter_id' field to 'struct ovnact_encode_params' to be
used when encoding controller actions from logical flow actions.

Change the ovn-northd implementation to set the new 'controller_meter'
field for flows that need to punt packets to ovn-controller. For some
protocols (ARP/ND/DNS) install two sets of flows:
- one flow with a lower priority for the whole datapath using the
  per-datapath CoPP policy.
- one flow per port with a higher priority than the per-datapath one if
  there is a per-port CoPP defined for the given port.

Post-RFC remaining items:
- add autotests for CoPP

Signed-off-by: Dumitru Ceara <dceara at redhat.com>
CC: Han Zhou <hzhou8 at ebay.com>
CC: Numan Siddique <nusiddiq at redhat.com>

View the changeset: https://github.com/dceara/ovn/compare/0abc3ceb6d30...3457f1529f32

View the full build log and details: https://travis-ci.org/dceara/ovn/builds/595989319?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the dceara/ovn repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=25507942&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...
URL: <http://mail.openvswitch.org/pipermail/ovs-build/attachments/20191010/fe68a8e6/attachment-0001.html>


More information about the build mailing list