Thanks Igor! Anil and I can help test out real NSH support when we have the
networking-odl driver finished. That would be a good way to exercise that side
of networking-sfc code. Will look at these patches.
Tim Rozet
Red Hat SDN Team
----- Original Message -----
From: "Duarte Cardoso, Igor" <igor.duarte.card...@intel.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>, "Cathy Zhang" <cathy.h.zh...@huawei.com>
Sent: Wednesday, October 5, 2016 6:06:02 AM
Subject: Re: [openstack-dev] [tacker] [networking-sfc] Removing required
port-id from classifier
Hi Tim,
Just about the second part of your email:
> how are IETF SFC/NSH related API/plugin changes going?
I'm essentially finished with NSH encap support [1], just have to fix a few
bugs and write the tests. Then I will work on connecting port-chains together
so we can have SFC graphs, kind of like IETF's branching/reclassification "SFC
Encapsulation" chains (described with higher detail in the NSH draft).
> Can we expect to have attributes like path-id, encap type soon?
The NSH patch I mentioned above will allow NSH encap to be specified for both
port-chains and port-pairs and, if port-pairs do not support the port-chain's
encapsulation, it's up to the driver to SFC-Proxy the traffic accordingly (OVS
will install SFC-proxy flows, just like it does today by default, for MPLS).
Regarding the path-id, I was working on a patch to facilitate that [2], but we
ended up merging one focused only on enabling the path-id ("chain_id") [3]. So
we have both attributes now.
[1] https://review.openstack.org/#/c/373465
[2] https://review.openstack.org/#/c/346175
[3] https://review.openstack.org/#/c/355336
Best regards,
Igor.
-----Original Message-----
From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Tuesday, October 4, 2016 6:07 PM
To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev@lists.openstack.org>; Cathy Zhang <cathy.h.zh...@huawei.com>
Subject: [openstack-dev] [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. 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?
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
__________________________________________________________________________
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
__________________________________________________________________________
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
