Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use API instead of vppctl to interact with VPP #4

Open
fepan opened this issue Mar 14, 2018 · 6 comments
Open

Use API instead of vppctl to interact with VPP #4

fepan opened this issue Mar 14, 2018 · 6 comments
Labels
enhancement

Comments

@fepan
Copy link

fepan commented Mar 14, 2018

Instead of using vppctl, we should use either python or go API to configure VPP.
@rkamudhan
Copy link
Contributor

Hi Feng,

Interesting, We did this as inital PoC. Welcome your PR on this.

@rkamudhan
Copy link
Contributor

Plus all features are tested with VPP 17.01, Welcome the PR for the latest VPP

@rkamudhan
Copy link
Contributor

@fepan Updated README.md for more understanding.

@fepan
Copy link
Author

fepan commented Mar 16, 2018

Excellent, the documentation helps a lot. One thing I'm wondering, do we need to maintain support for VPP 17.01 as well as latest version, or is it OK to just add support for latest version. With latest VPP version, there could be some API changes as well as vhostuser/virtio-user incompatibility, so I'm wondering if we should use 17.01 as a reference.

@rkamudhan
Copy link
Contributor

@fepan I am highly inclined to go for the latest version and also for the API changes.

@fepan
Copy link
Author

fepan commented Mar 16, 2018

@rkamudhan sounds good, I'll test with latest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fepan @rkamudhan