Difference between revisions of "NSH SFC/Docs/Designs"
From fd.io
< NSH SFC
(Created page with "== Initial seed of repo == The following is simply a proposed way of completing the work alagalah@gmail.com has started in the VPP project's repo: [https://drive.google.com/...") |
(→Initial seed of repo) |
||
| Line 10: | Line 10: | ||
This is NOT intended to be a presumptive final architecture, merely some thoughts on how to achieve completing the PoC and moving the code. | This is NOT intended to be a presumptive final architecture, merely some thoughts on how to achieve completing the PoC and moving the code. | ||
| + | |||
| + | == Initial design of NSH-aware SFs == | ||
| + | |||
| + | The following is a proposal to enable NSH-aware SFs: | ||
| + | |||
| + | [https://docs.google.com/presentation/d/1n-dErGE5mCGncbTkXcXKFUZW2ZGEqgM6LUTDGDQzano/edit?usp=sharing=high level diagram for enabling NSH aware SFs] | ||
Revision as of 05:03, 29 November 2016
Initial seed of repo
The following is simply a proposed way of completing the work alagalah@gmail.com has started in the VPP project's repo:
Draw.io doc of simple high level design
The thinking is that this can be used to seed the NSH_SFC git repository, fixing bugs and completing intended PoC SFF / Classifier functionality, as well as kicking off the initial decoupling of VXLAN-GPE/GRE code and NSH code.
From there, we should definitely iterate on the actual design we would like NSH_SFC to have to support all the use cases etc as part of the project scope.
This is NOT intended to be a presumptive final architecture, merely some thoughts on how to achieve completing the PoC and moving the code.
Initial design of NSH-aware SFs
The following is a proposal to enable NSH-aware SFs:
