Hi Tim,

Please see inline.

Thanks,
Cathy

-----Original Message-----
From: Tim Rozet [mailto:tro...@redhat.com] 
Sent: Tuesday, October 04, 2016 10:07 AM
To: OpenStack Development Mailing List (not for usage questions); Cathy Zhang
Cc: Sridhar Ramaswamy; Sripriya Seetharam
Subject: [tacker] [networking-sfc] Removing required port-id from classifier

Hi Cathy,
I recall a while back discussing removing the required neutron port-id from the 
classifier.  

Cathy> Do you mean logical source port here?


We just finished up implementing VNFFG in Tacker and are hitting this while 
testing.  What is the plan to remove this requirement?  Also, how are IETF 
SFC/NSH related API/plugin changes going?  Can we expect to have attributes 
like path-id, encap type soon?  

Cathy> The API already provides a way for specifying "path-id" and encap type 
(currently only MPLS encap type is supported since OVS does not support NSH 
yet). As to NSH support, the code patch is being worked on, not completed yet. 
We are also tracking the NSH work in OVS and hope OVS will support NSH soon so 
that when networking-sfc integrates with that new version of OVS, NSH can be 
supported properly.  




Thanks,

Tim Rozet
Red Hat SDN Team
__________________________________________________________________________
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

Reply via email to