Correlation should be unique per Port Pair Group

Bug #1692536 reported by Igor D.C.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-sfc
Fix Released
Undecided
Igor D.C.

Bug Description

When creating Port Pair Groups, the associated Port Pairs should all share the same correlation type. If not, the instances of each group will require different processing and will not be able to provide the same set of features at the respective hop of the chain, e.g. not able to fully encapsulate the packets (which could lead to chain packet leakage) or not able to transport metadata, amongst other reasons. Ideally, it should be possible to clearly state what is supported, and how, per each hop of a chain (independently of what instances are associated to that hop/PPG).

Currently, the OVS driver works around this by falling back to having no correlation at the next hops, if at least one of the PPs/next hops doesn't support the correlation required by the Port Chain.

Tags: rfe
Igor D.C. (igordcard)
Changed in networking-sfc:
assignee: nobody → Igor Duarte Cardoso (igordcard)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-sfc (master)

Fix proposed to branch: master
Review: https://review.openstack.org/466777

Changed in networking-sfc:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-sfc (master)

Reviewed: https://review.openstack.org/466777
Committed: https://git.openstack.org/cgit/openstack/networking-sfc/commit/?id=fa27b9bf8463f113e5cdb9d9b2a0b2d592db3150
Submitter: Jenkins
Branch: master

commit fa27b9bf8463f113e5cdb9d9b2a0b2d592db3150
Author: Igor Duarte Cardoso <email address hidden>
Date: Mon May 22 14:14:09 2017 +0000

    Require Port Pairs to share same correlation type

    When creating Port Pair Groups, validation of each Port Pair's
    correlation type will now occur.
    Every Port Pair needs to share the same correlation type
    when they get attached to a specific Port Pair Group.
    This guarantees homogeneity in the composition of a Port Pair Group
    and clarifies the definition and feature set of each hop of a chain.

    Creating and Updating Port Pair Groups now verifies whether all PPs are
    consistent with regards to the correlation type selected.

    The workaround to achieve "homogeneous" next-hops in the OVS driver
    introduced by Iebdfca5467ca33cfd9d93d55f47d6b57b79dffbe
    has been removed, so were a couple of related tests.

    Documentation has been updated.

    Closes-Bug: #1692536

    Change-Id: I80714f2661340c639a38162f3bfc22ab3e01a3c7

Changed in networking-sfc:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-sfc 5.0.0.0b2

This issue was fixed in the openstack/networking-sfc 5.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.