-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start migrating kernel-forwarder to new style xconnect NS #2
Comments
@edwarnicke I'd be happy to try taking a crack at this. |
@rktidwell I'd be happy to review and assist you with that if needed 👍 |
rktidwell
pushed a commit
to rktidwell/sdk-kernel
that referenced
this issue
Jan 23, 2020
This change introduces basic utilities for managing interfaces, routes, and namespaces. See networkservicemesh#2 Signed-off-by: Ryan Tidwell <[email protected]>
rktidwell
pushed a commit
to rktidwell/sdk-kernel
that referenced
this issue
Feb 4, 2020
This change introduces basic utilities for managing interfaces, routes, and namespaces. See networkservicemesh#2 Signed-off-by: Ryan Tidwell <[email protected]>
@rdimitrov @rktidwell Hi, We moved issue from In Progress into To Do stuff, please update status if anything is changed. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Start writing the kernel-forwarder network service SDK in a style similar to the
sdk-vppagent.
You can crib in terms of how things are done from:
https://github.com/networkservicemesh/networkservicemesh/tree/master/forwarder/kernel-forwarder
The text was updated successfully, but these errors were encountered: