Difference between revisions of "NSH SFC/Meeting"
Last updated 7 years ago

Revision as of 00:21, 7 February 2017

Meeting Details

Weekly on Monday, 60min, from 16:00 - 17:00 PDT.

Join Skype Meeting

Join by phone +1(916)356-2663 (or your local bridge access #) Choose bridge 5. (Global) English (United States)

Conference ID: 133570463

Find a local number

IRC
- #fdio-nsh room on freenode
- Web-based IRC client: https://webchat.freenode.net/

Agenda

The next NSH_SFC meeting is scheduled for Monday 6th Feb, 2017

1) NSH_SFC 17.01 release and package for other Linux foundation projects (e.g. ODL and Open-O) to use

2) NSH_SFC 17.04 feature discussion and status

 2.1) Co-locate NSH_SFC and VPP in as same box

 2.2) Plan for the MD type 2 support and iOAM support based on discussion between Hongjun and Prasad.

Information From Past Meetings

[Expand]

2017-02-06

1) NSH_SFC 17.01 release and package for other Linux foundation projects (e.g. ODL and Open-O) to use

       1.1) Two issues (next node and endian) founded during integration tests, so it is very important to enable CSIT automation

       1.2) Packaging VPP and NSH_SFC for ODL and Open-O

       1.2.1)Docker image for ODL SFC 104

　　　　　1.2.2)KVM/Qemu image for Open-O Murcury release enabling EPA

2) NSH_SFC 17.04 feature discussion and status 

       2.1) Co-locate NSH_SFC and VPP in a same box, blocked on a issue on handling packets returned from SNAT node to NSH_SFC plugin, prefer solution is to connect them to a L2 bridge instead of SNAT directly transmit the packet to wire. Hongjun is working on this

       2.2) Plan for the MD type 2 support and iOAM support based on discussion between Hongjun and Prasad

       2.2.1) Generic TLV routines in NSH_SFC, initial patches to send out for review this week

       2.2.2) iOAM plugin by Prasad to reuse those routines for NSH based iOAM implementation

       2.2.3) Move TLV generic routines to VPP if needed (e.g. other graph nodes need to use those routines)

[Expand]

2017-01-24

[Expand]

2017-01-09

1) NSH_SFC build failure tracked by https://jira.fd.io/browse/NSHSFC-18, which caused by recent build infrastructure change. Hongjun is working with Damjan to resolve this, seems it only need to add the missed file to the file src/vpp-api/java/Makefile.am. Nobody knows how to publish NSH_SFC artifacts for NSH_SFC rc1.

AR: Danny to drop email to help desk to ask how to publish NSH_SFC artifacts.

2) 0.5 dedicated resource is working on including NSH_SFC to the FD.io CSIT tests to cover both feature and performance automation tests. Goals are:

  * Can configure the NSH_SFC to act as SFF/Classifier/Proxy via Postman
  * Enable a Jeinkins job that drives TREX to send traffics in different size to NSH_SFC and
  measure/report the NSH_SFC performance when it acts different roles.

Test plan is underdeveloped, and the initial version is supposedly to be ready by the end of this week. Target is that the CSIT infrastructure for NSH_SFC to hit 17.04 release. All the new patches to be submitted in the future will benefit from this automation performance tests, to understand the performance impact the patch will be introducing.

3) A separated meeting is schedule with Prasad to discuss the TLV support for NSH MD Type 2. Prasad and his team is doing the in-band IOAM for VxLAN-GPE at this point which enables a framework to handle TLV. Target is to ensure common TLV parser in VPP could be used by various VPP plugin for different purpose. Keith is going to raise this in the VPP weekly meeting.

[Expand]

2017-01-02

1) 17.01 Release

1.a Patches for NSH Proxy and NSH Classifier have been merged to both NSH_SFC and HC, after performing unit test. Integration with ODL SFC ongoing.

1.b Get some request from FD.io STV team about what tests need to be performed for NSH_SFC 17.01 release, will ask them to do integration test below:

    * Develops some CSIT test cases to test the dataplane and VPP CLI of NSH SFF, 
      NSH-Proxy and NSH Classifier.
    * Integrates  Honeycomb, VPP and NSH_SFC to test the HC NB API of NSH SFF, NSH-Proxy 
      and NSH Classifier.

1.c Hongjun is working on creating a Docker image that includes VPP 17.01 and NSH_SFC 17.01 as well as virtio_user PMD (based on DPDK 16.11) to enable easy-to-deploy NSH SFC ingredients (Classifier, SFF, Proxy, etc). In the future, the ODL and NSH-aware VNFs (co-locating Proxy and SFs) will be packaged the same way to enable an all-in-one setup, which includes a Vagrant image within several Docker images to create a SFC setup that has all ingredients specified in RFC 7665.

2) 17.04 release discussion

Targeted new features for 17.04 release:

    * Co-locate Proxy with SF 
    * Basic MD Type 2 support, such as encap/decap NSH within MD Type 2

3) Planned new features for 17.07 release

    * Release NSH-aware SFs being able to consume context header embedded in the NSH via 
      per-packet metadata
    * Enable match-action for MD Type 2 NSH

4) Open: P4 for VPP and NSH_SFC

Idea is to develop a "compiler" that dynamically generate graph nodes from P4 program' HLIR, each node on the P4' parse graph will be mapped to a graph node of VPP and the graph node is responsible for extracting header defined in P4 and determine next graph nodes. This way, supporting new protocols such as VxLAN-GPE and NSH will be much easier. In addition, a "compiler" for ODL will be introduced to convert P4 program to Yang model for NETCONF SB plugin and HC to consume, so ODL could control VPP based P4 switch via RPC. Note: there is no need to support Openflow and OVSDB for this case.

Will add this to JIRA and no resources are assigned for this story.

[Expand]

2016-12-12

[Expand]

2016-12-05

1) NSH_SFC 1701 release plan updated on this wiki. The milestones will be one week post VPP' milestones.

2) NSH Proxy and NSH Classifier those two features are in good shape. Features implementation done after initial test, there is no dependency on VPP' API change, but it still needs to depend on Yang model change in HC to ensure they can be integrated with ODL SFC. HC API freeze is Dec 14th, and Hongjun is working to ensure the Yang model and API changes will be accepted before HC API freeze.

3) ODL SFC in Carbon release will support above two features, and the SFC 104 test will enable a working demo.

4) NSH-aware VNFs in current proposal could be treated as NSH Proxy collocates with SF, there are two issues problems raised by Joel need to address in the near future:

   a. We need SFs to be natively NSH-aware, meaning they can manipulate metadata inside the NSH. 
      Current implementation looks like NSH Proxy co-locate with SFs but SFs can only 
      see the original frames.
   b. How to handle NAT like or TCP Proxy like SFs after they change the headers 
      of the inner headers which are typically used as key to determine which 
      next graph node is?  The initial thought is to add some information to 
      per-packet metadata before packets go into the SF, and the metadata can 
      be used to determine if it needs to be re-encapsulated by NSH_SFC graph node.

AR: Hongjun to investigate how to support NAT and TCP Proxy sort of SFs by leveraging per-packet metadata. Also, think about the framework and libraries to enable SF being able to manipulate NSH metadata.

[Expand]

2016-11-28

[Expand]

2016-08-29

The following list of gerrit patches do the integration work:

(1).VPP:

https://gerrit.fd.io/r/#/c/2118/ jvpp support for nsh.

(2).Honeycomb:

https://gerrit.fd.io/r/#/c/2527/ HONEYCOMB-46: Add Nsh Map in Honeycomb

which depends on this patch:

https://gerrit.fd.io/r/#/c/2481/9 HONEYCOMB-46: Add Nsh Entry in Honeycomb

(3).ODL SFC:

https://git.opendaylight.org/gerrit/#/c/42699/ Add VPP Renderer

Actually, there are only two issues remained, but I think they won’t block the integration test.

(4).The building failure due to “mvn” commands are not supported in Jenkins.

       We have discussed this issue on weekly meeting, and Ed Warnicke will fix it.

(5). HC Plugin could not reuse the VxlanGpeCustomizer within the HC code base.

      I have sent an email to discuss this issue with Maros and Marek.

      The details are as follows:

In nsh-map Yang model, there is an augmentation:

 augment /vpp-nsh/nsh-maps/nsh-map {

   ext:augment-identifier vxlan-gpe-encap-augment;

   when "/encap-type = 'vpp-nsh:vxlan-gpe-encap-type' ";

   uses v3po:vxlan-gpe-base-attributes;

How can I reuse the VxlanGpeCustomizer within the HC code base?

I tried to register VxlanGpeCustomizer into VppNshWriterFactory, but it failed.

[Expand]

2016-07-18

[Expand]

2016-06-20

[Expand]

2016-06-06

[Expand]

2016-05-23

[Expand]

2016-05-16

[Expand]

2016-05-09

[Expand]

2016-04-25

[Expand]

2016-04-11

Difference between revisions of "NSH SFC/Meeting"
Last updated 7 years ago

Revision as of 00:21, 7 February 2017

Meeting Details

Agenda

Information From Past Meetings

Navigation menu

Personal tools

Namespaces

Variants

Views

Actions

Search

Navigation

Tools

@@ Line 34: / Line 34: @@
 <div class="mw-collapsible-content">
 ) NSH_SFC 17.01 release and package for other Linux foundation projects (e.g. ODL and Open-O) to use
-      1.1) Two issues (next node and endian) founded during integration tests, so it is very important to enable CSIT automation
+.1) Two issues (next node and endian) founded during integration tests, so it is very important to enable CSIT automation
-      1.2) Packaging VPP and NSH_SFC for ODL and Open-O
+.2) Packaging VPP and NSH_SFC for ODL and Open-O
 .2.1)Docker image for ODL SFC 104

Difference between revisions of "NSH SFC/Meeting"Last updated 7 years ago

Revision as of 00:21, 7 February 2017

Meeting Details

Agenda

Information From Past Meetings

Navigation menu

Search

Difference between revisions of "NSH SFC/Meeting"
Last updated 7 years ago