Igor, See inline. - Louis
From: Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com] Sent: Monday, February 13, 2017 11:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [networking-sfc] What resources can and can't be reused Hi networking-sfc, As part of my work regarding SFC Encapsulation and SFC Graphs, I exercised the API to understand exactly what resources can be reused, to possibly relax a few of the constraints when a chain is encapsulated end-to-end. I'm requesting that the leaders and cores take a look at the list below, and reply if you see something that doesn't look quite right (or have any other comment/question). Thanks! 1. Every flow-classifier must have a logical source port. LF: - this is only true for OVS drivers. 2. The flow-classifier must be unique in its (full) definition. LF: correct 3. A port-chain can have multiple flow-classifiers associated with exactly the same definition BUT different logical source ports. LF: correct 4. The port-chains can be ambiguous, i.e. match on the same classification criteria, if and only if there are 0 flow classifiers associated. LF: If a port-chain has no classifier, then there is no classification so no traffic flows through it. 5. The flow classifiers can only be used once, by a single port-chain. LF: correct. 6. Different port-chains cannot be associated to different flow classifiers that specify the same classification criteria BUT different logical source ports (this is https://bugs.launchpad.net/networking-sfc/+bug/1638421). LF: correct 7. A port-pair's ingress cannot be in use by another port-pair's ingress. LF: correct a SF port can only be the ingress port of one port pair. 8. A port-pair's egress cannot be in use by another port-pair's egress. LF: correct a SF port can only be the egress port of one port pair. 9. A port-pair can be associated to another port-pair's ingress and egress ports BUT swapped (i1=e2, e1=i2). LF: correct. 10. The port-pairs become "in use" when a port-pair-group associates them, so they can't be reused across port-pair-groups. LF: correct, a port-pair can only be in one port-pair group. 11. A port-chain can include port-pair-groups already associated to other port-chains, as long as not the exact same sequence as another port-chain (e.g. pc1: [ppg1,ppg2]; pc2: [ppg1] - is fine). LF: correct. Best regards, Igor.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
