[openstack-dev] Change in openstack/neutron-specs[master]: Neutron API for Service Chaining

Cathy Zhang Cathy.H.Zhang at huawei.com
Wed Jun 17 18:24:15 UTC 2015


Hi Nicolas,

Thanks for your suggestion. Yes, we can add Application ID to the parameter of the flow classifier/filter. The next updated version will reflect this. Actually in its existing design, the parameter field of the flow classifier can be extended in the future to include more flow descriptors for more granular differentiation of flows.

Per earlier suggestion from Isaku etc., we can also add a “context” field to the service chain API. The context field will include information such as “the encapsulation mechanism” used by the service functions in the chain, which can be NSH, VLAN, none etc. so that the Service Function Forwarder (the vSwcitch) knows whether it should act as a SFC proxy or not and if acting as a Proxy, what is the chain correlation mechanism between the Service Function Forwarder and the Service Function.

Any comments/questions/suggestions?

Thanks,
Cathy

From: Nicolas BOUTHORS [mailto:Nicolas.BOUTHORS at qosmos.com]
Sent: Wednesday, June 17, 2015 12:03 AM
To: Armando Migliaccio; Henry Fourie
Cc: Isaku Yamahata; Gal Sagie; vishwanath jayaraman; Swaminathan Vasudevan; Ila Palanisamy; Adolfo Duarte; Ritesh Anand; Lynn Li; Bob Melander; Berezovsky Irena; Subrahmanyam Ongole; Cathy Zhang; Moshe Levi; Joe D'Andrea; Ryan Tidwell; Vikram Choudhary; Ruijing; Yatin Kumbhare; Miguel Angel Ajo; Numan Siddique; Yuriy Babenko; YujiAzama
Subject: RE: Change in openstack/neutron-specs[master]: Neutron API for Service Chaining


In IETF SFC draft-penno-sfc-appid-00 proposed a notion of ApplicationId, a generic attribute that can be included in NSH metadata.  This reflects also on  ODL SFC wich has introduced the Application Id as a parameter that can be used by the Classifier to steer traffic into a chain.



I suggest we include this parameter in the Flow Filter resource, so that application aware service chaining can be done.



ApplicationId is typically encoded in a 32 bit field.



   Application Identification Data Format



The following table displays the Selector ID default length for the  different Classification Engine IDs.



        Classification               Selector ID default

        Engine ID Name               length (in bytes)



        IANA-L3                      1



        PANA-L3                      1



        IANA-L4                      2



        PANA-L4                      2



        USER-Defined                 3



        PANA-L2                      5



        PANA-L7                      3



        ETHERTYPE                    2



        LLC                          1



        PANA-L7-PEN                  3 (*)



                0                   1                   2                   3

      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      |Class. Eng. ID |zero-valued upper-bits ... Selector ID         |

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+





Nicolas



-----Original Message-----
From: Jenkins (Code Review) [mailto:review at openstack.org]
Sent: mercredi 17 juin 2015 08:46
To: Armando Migliaccio; Louis Fourie
Cc: Isaku Yamahata; Gal Sagie; vishwanath jayaraman; Swaminathan Vasudevan; Ila Palanisamy; Adolfo Duarte; Ritesh Anand; Lynn Li; Bob Melander; Berezovsky Irena; Subrahmanyam Ongole; cathy; Moshe Levi; Joe D'Andrea; Ryan Tidwell; vikram.choudhary; Ruijing; Yatin Kumbhare; Miguel Angel Ajo; Numan Siddique; Yuriy Babenko; YujiAzama
Subject: Change in openstack/neutron-specs[master]: Neutron API for Service Chaining



Jenkins has posted comments on this change.



Change subject: Neutron API for Service Chaining ......................................................................





Patch Set 8: Verified+1



Build succeeded (check pipeline).



- gate-neutron-specs-docs http://docs-draft.openstack.org/46/177946/8/check/gate-neutron-specs-docs/6955f62//doc/build/html/<http://docs-draft.openstack.org/46/177946/8/check/gate-neutron-specs-docs/6955f62/doc/build/html/> : SUCCESS in 3m 51s

- gate-neutron-specs-python27 http://logs.openstack.org/46/177946/8/check/gate-neutron-specs-python27/271ef19/ : SUCCESS in 2m 31s



--

To view, visit https://review.openstack.org/177946

To unsubscribe, visit https://review.openstack.org/settings



Gerrit-MessageType: comment

Gerrit-Change-Id: Ic0df6070fefd9ead6589fa2da6c49824d7ae3941

Gerrit-PatchSet: 8

Gerrit-Project: openstack/neutron-specs

Gerrit-Branch: master

Gerrit-Owner: Louis Fourie <louis.fourie at huawei.com<mailto:louis.fourie at huawei.com>>

Gerrit-Reviewer: Adolfo Duarte <adolfo.duarte at hp.com<mailto:adolfo.duarte at hp.com>>

Gerrit-Reviewer: Armando Migliaccio <armamig at gmail.com<mailto:armamig at gmail.com>>

Gerrit-Reviewer: Berezovsky Irena <irenab.dev at gmail.com<mailto:irenab.dev at gmail.com>>

Gerrit-Reviewer: Bob Melander <bob.melander at gmail.com<mailto:bob.melander at gmail.com>>

Gerrit-Reviewer: Gal Sagie <gal.sagie at huawei.com<mailto:gal.sagie at huawei.com>>

Gerrit-Reviewer: Ila Palanisamy <ilavajuthy.palanisamy at hp.com<mailto:ilavajuthy.palanisamy at hp.com>>

Gerrit-Reviewer: Isaku Yamahata <yamahata.review at gmail.com<mailto:yamahata.review at gmail.com>>

Gerrit-Reviewer: Jenkins

Gerrit-Reviewer: Joe D'Andrea <jdandrea at research.att.com<mailto:jdandrea at research.att.com>>

Gerrit-Reviewer: Louis Fourie <louis.fourie at huawei.com<mailto:louis.fourie at huawei.com>>

Gerrit-Reviewer: Lynn Li <lynn.li at hp.com<mailto:lynn.li at hp.com>>

Gerrit-Reviewer: Miguel Angel Ajo <mangelajo at redhat.com<mailto:mangelajo at redhat.com>>

Gerrit-Reviewer: Moshe Levi <moshele at mellanox.com<mailto:moshele at mellanox.com>>

Gerrit-Reviewer: Numan Siddique <nusiddiq at redhat.com<mailto:nusiddiq at redhat.com>>

Gerrit-Reviewer: Ritesh Anand <ritesh.anand at hp.com<mailto:ritesh.anand at hp.com>>

Gerrit-Reviewer: Ruijing <ruijing.guo at intel.com<mailto:ruijing.guo at intel.com>>

Gerrit-Reviewer: Ryan Tidwell <rktidwell85 at gmail.com<mailto:rktidwell85 at gmail.com>>

Gerrit-Reviewer: Subrahmanyam Ongole <songole at oneconvergence.com<mailto:songole at oneconvergence.com>>

Gerrit-Reviewer: Swaminathan Vasudevan <swaminathan.vasudevan at hp.com<mailto:swaminathan.vasudevan at hp.com>>

Gerrit-Reviewer: Yatin Kumbhare <yatinkumbhare at gmail.com<mailto:yatinkumbhare at gmail.com>>

Gerrit-Reviewer: YujiAzama <yuj-azama at rc.jp.nec.com<mailto:yuj-azama at rc.jp.nec.com>>

Gerrit-Reviewer: Yuriy Babenko <ybabenko3 at gmail.com<mailto:ybabenko3 at gmail.com>>

Gerrit-Reviewer: cathy <cathy.h.zhang at huawei.com<mailto:cathy.h.zhang at huawei.com>>

Gerrit-Reviewer: vikram.choudhary <vikram.choudhary at huawei.com<mailto:vikram.choudhary at huawei.com>>

Gerrit-Reviewer: vishwanath jayaraman <vishwanathj at hotmail.com<mailto:vishwanathj at hotmail.com>>

Gerrit-HasComments: No

This message and any attachments (the "message") are confidential, intended solely for the addressees. If you are not the intended recipient, please notify the sender immediately by e-mail and delete this message from your system. In this case, you are not authorized to use, copy this message and/or disclose the content to any other person. E-mails are susceptible to alteration. Neither Qosmos nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

Ce message et toutes ses pièces jointes (ci-après le "message")sont confidentiels et établis à l'intention exclusive de ses destinataires. Si vous avez reçu ce message par erreur, merci d’en informer immédiatement son émetteur par courrier électronique et d’effacer ce message de votre système. Dans cette hypothèse, vous n’êtes pas autorisé à utiliser, copier ce message et/ou en divulguer le contenu à un tiers. Tout message électronique est susceptible d'altération. Qosmos et ses filiales déclinent toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150617/4d5ab7ad/attachment.html>


More information about the OpenStack-dev mailing list