[ovs-build] Failed: ovsrobot/ovn#102 (series_127677 - fec5d0f)

Travis CI builds at travis-ci.com
Wed Aug 28 04:12:38 UTC 2019


Build Update for ovsrobot/ovn
-------------------------------------

Build: #102
Status: Failed

Duration: 49 mins and 8 secs
Commit: fec5d0f (series_127677)
Author: Ankur Sharma
Message: OVN: Vlan backed DVR N-S, redirect packet via localnet port

Background:
With c0974331b7a19a87ab8f1f2cec8fbe366af92fa2, we have added
support for E-W workflow for vlan backed DVRs.

This series enables N-S workflow for vlan backed DVRs.

Key difference between E-W and N-S traffic flow is that
N-S flow requires a gateway chassis. A gateway chassis
will be respondible for following:
a. Doing Network Address Translation (NAT).
b. Becoming entry and exit point for North->South
   and South->North traffic respectively.

OVN by default always uses overlay encapsulation to redirect
the packet to gateway chassis. This series will enable
the redirection to gateway chassis in the absence of encapsulation.

This patch:
Achieves the vlan backed redirection by doing following:

Sender Side:
------------
a. For a remote port of type "chassisredirect" and if it
   has redirect type as "vlan", then do not add tunnel
   based redirection flow in table=32.

b. In table=33, add a flow with priority=100, that would do following:
   i. Change the metadata to that of gateway logical switch
      (i.e logical switch attached to gateway logical router port).
  ii. Change REG15 to point to localnet port of gateway logical switch.
 iii. send to packet to table=15.

c. In Table=65, packet will hit the existing priority=150 flow to send
   the packet to physical bridge, while attaching vlan header and
   changing source mac to chassis mac.

Receiver Side:
--------------
a. No changes needed

OVERALL PACKET FLOW:
Sender Side:
-----------
a. logical flow in lr_in_gw_redirect stage will ensure that
   outport of the packet is chassisredirect port.
   For example:
   table=12(lr_in_gw_redirect  ), priority=50   , match=(outport == "router-to-underlay"), action=(outport = "cr-router-to-underlay"; next;)

b. After ingress pipeline, packet will enter the table=32, followed by table=33

c. Table=33, will send the packet to table=65.

d. Table=65, will send the packet to uplink bridge
   with destination mac of chassisredirect port and vlan
   id of peer logical switch.

Receiver Side:
-------------
a. Packet is received by the pipeline of peer logical switch.
b. Since destination mac is that of router port, hence packet will
   enter the logical router pipeline.
c. Now, packet will go through regular logical router pipeline
   (both ingress and egress).

One caveat with the approach is that ttl will be decremented twice,
since the packets are going through logical router ingress pipeline
twice (once on sender chassis and again on gateway chassis).

No changes needed for the reverse path.

Signed-off-by: Ankur Sharma <ankur.sharma at nutanix.com>
Signed-off-by: 0-day Robot <robot at bytheb.org>

View the changeset: https://github.com/ovsrobot/ovn/compare/b69ace6543a6...fec5d0f77311

View the full build log and details: https://travis-ci.com/ovsrobot/ovn/builds/124841985?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the ovsrobot/ovn repository going to https://travis-ci.com/account/preferences/unsubscribe?repository=9136199&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.com/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/20190828/e10207fc/attachment-0001.html>


More information about the build mailing list