The integration test for NSH_SFC rc2 has been done and a small issue on NSH Proxy is found and fixed in a merged patch https://gerrit.fd.io/r/#/c/4829/, hence a new tag v17.01-rc3 has been placed and re-performed integration test shows it works well.

We will officially release NSH_SFC 17.01 tomorrow, and supply jar files for hc2vpp project to use.

As mentioned by Hongjun, starting from NSH_SFC 17.04 release cycle, the jar files will be created along with RCs for other dependent projects like hc2vpp.

OK. We will releasee nsh_sfc RC jar versions in future.

Have commented on patch 4781.

Thanks a lot,

Hongjun

Ok, so we will try to release hc2vpp RC2 as soon as we solve our infra problems,

but we will of course wait for nsh release before releasing hc2vpp.

For future nsh release please consider releasing nsh_sfc RC jar versions – it would help us a lot.

Could you please comment on

https://gerrit.fd.io/r/#/c/4781/

regarding snapshot dependency.

Thanks,

Marek

Nsh_sfc did not change the jar version for rc1 and rc2, which both are 1701-snapshot.

so I think it is ok if hc2vpp RC2 debs and rpms include nsh_sfc 1701-snapshot.

When nsh_sfc 1701 formally release, we will change it to 17.01.

At that time, hc2vpp will need to change it accordingly.

NSH_SFC RC1 has a bug which has been fixed in RC2, so RC2 jar is expected to be included.

How about RC1 then?

Or you are ok if hc2vpp RC2 debs and rpms include nsh_sfc snapshot?

Regards,

Marek

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

OK. We will releasee nsh_sfc RC jar versions in future.

Have commented on patch 4781.

Thanks a lot,

Hongjun

Ok, so we will try to release hc2vpp RC2 as soon as we solve our infra problems,

but we will of course wait for nsh release before releasing hc2vpp.

For future nsh release please consider releasing nsh_sfc RC jar versions – it would help us a lot.

Could you please comment on

https://gerrit.fd.io/r/#/c/4781/

regarding snapshot dependency.

Thanks,

Marek

Nsh_sfc did not change the jar version for rc1 and rc2, which both are 1701-snapshot.

so I think it is ok if hc2vpp RC2 debs and rpms include nsh_sfc 1701-snapshot.

When nsh_sfc 1701 formally release, we will change it to 17.01.

At that time, hc2vpp will need to change it accordingly.

NSH_SFC RC1 has a bug which has been fixed in RC2, so RC2 jar is expected to be included.

How about RC1 then?

Or you are ok if hc2vpp RC2 debs and rpms include nsh_sfc snapshot?

Regards,

Marek

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

OK. We will releasee nsh_sfc RC jar versions in future.

Have commented on patch 4781.

Thanks a lot,

Hongjun

Ok, so we will try to release hc2vpp RC2 as soon as we solve our infra problems,

but we will of course wait for nsh release before releasing hc2vpp.

For future nsh release please consider releasing nsh_sfc RC jar versions – it would help us a lot.

Could you please comment on

https://gerrit.fd.io/r/#/c/4781/

regarding snapshot dependency.

Thanks,

Marek

Nsh_sfc did not change the jar version for rc1 and rc2, which both are 1701-snapshot.

so I think it is ok if hc2vpp RC2 debs and rpms include nsh_sfc 1701-snapshot.

When nsh_sfc 1701 formally release, we will change it to 17.01.

At that time, hc2vpp will need to change it accordingly.

NSH_SFC RC1 has a bug which has been fixed in RC2, so RC2 jar is expected to be included.

How about RC1 then?

Or you are ok if hc2vpp RC2 debs and rpms include nsh_sfc snapshot?

Regards,

Marek

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

Ok, so we will try to release hc2vpp RC2 as soon as we solve our infra problems,

but we will of course wait for nsh release before releasing hc2vpp.

For future nsh release please consider releasing nsh_sfc RC jar versions – it would help us a lot.

Could you please comment on

https://gerrit.fd.io/r/#/c/4781/

regarding snapshot dependency.

Thanks,

Marek

Nsh_sfc did not change the jar version for rc1 and rc2, which both are 1701-snapshot.

so I think it is ok if hc2vpp RC2 debs and rpms include nsh_sfc 1701-snapshot.

When nsh_sfc 1701 formally release, we will change it to 17.01.

At that time, hc2vpp will need to change it accordingly.

NSH_SFC RC1 has a bug which has been fixed in RC2, so RC2 jar is expected to be included.

How about RC1 then?

Or you are ok if hc2vpp RC2 debs and rpms include nsh_sfc snapshot?

Regards,

Marek

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

Nsh_sfc did not change the jar version for rc1 and rc2, which both are 1701-snapshot.

so I think it is ok if hc2vpp RC2 debs and rpms include nsh_sfc 1701-snapshot.

When nsh_sfc 1701 formally release, we will change it to 17.01.

At that time, hc2vpp will need to change it accordingly.

NSH_SFC RC1 has a bug which has been fixed in RC2, so RC2 jar is expected to be included.

How about RC1 then?

Or you are ok if hc2vpp RC2 debs and rpms include nsh_sfc snapshot?

Regards,

Marek

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

NSH_SFC RC1 has a bug which has been fixed in RC2, so RC2 jar is expected to be included.

How about RC1 then?

Or you are ok if hc2vpp RC2 debs and rpms include nsh_sfc snapshot?

Regards,

Marek

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

How about RC1 then?

Or you are ok if hc2vpp RC2 debs and rpms include nsh_sfc snapshot?

Regards,

Marek

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

Yes, we will be releasing RC2 jars once NSH_SFC RC2 integration test passed today or tomorrow.

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

Hi,

since nsh_sfc final release is postponed, would it be possible to release RC1 or RC2 jars?

It would help releasing hc2vpp RC2 – we delayed it partially because we don’t want to depend on nsh snapshots.

Regards,

Marek

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny

One correction, since currently HC only has the RC1 label in Gerrit so our NSH_SFC RC2 integration test be use it until HC RC2 label is ready to use.

Meeting Minutes for today as below:

l  A small patch https://gerrit.fd.io/r/#/c/4745/ applied to NSH_SFC RC1, hence NSH_SFC RC2 tag is created. NSH_SFC RC2 integration test with VPP 17.01 and Honeycomb RC2 (https://gerrit.fd.io/r/#/c/4781/) is ongoing, blocked on environment configuration. Expect to release NSH_SFC 17.01 by Jan 27^th , once integration test passed, and Honeycomb 17.01 depends on NSH_SFC 17.01.

l  Shared preliminary NSH_SFC performance using RC2 to cover SFF, Proxy and Classifier use cases by feeding small packets. See details at https://wiki.fd.io/view/NSH_SFC/Docs/Performance

ü  The comprehensive performance report will be shared once CSIT team fully integrate it to CSIT automation test environment.

ü  NSH Proxy (1core, 1thread) performance drops from 16.09’ 5.8Mpps to 4.25Mpps for 128B small packet, might due to decoupling of VxLAN-GPE and NSH, will be analyzing it further post 17.04 release after MD Type 2 is supported.

ü  2 to 3 dedicated cores could achieve 10G line rate for small packet for all NSH_SFC use cases, assuming performance scales linearly.

Proposed agenda as below, feel free to propose new agenda items.

* Open

* NSH_SFC 17.01 release: RC1 and RC2 difference, integration test result review with VPP 17.01 and HC RC2.

* Preliminary NSH_SFC performance review and discussion for SFF, Classifier and Proxy functionalities.

-Danny