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.

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

Automate switch provisioning for each test case #12

Open
ccascone opened this issue Jan 22, 2021 · 0 comments · May be fixed by #13
Open

Automate switch provisioning for each test case #12

ccascone opened this issue Jan 22, 2021 · 0 comments · May be fixed by #13

Comments

@ccascone
Copy link
Member

ccascone commented Jan 22, 2021

Like we do for PTF tests, different test cases might require different P4 programs (fabric profile) and entries. For now, we rely on a manual process, which is time-consuming and error-prone. Instead, we should make it possible to script switch provisioning.

A few options:

  1. Provide p4runtime library like we do for fabric-tna's PTF tests (could be p4runtime-shell)
  2. Provide stratum p4rt_write.log for each test case (hard to modify by hand) and invoke stratum-replay
  3. Use STC to automate ONOS bring up and configuration (CPU/memory heavy, can only be used to program tables for which we have app logic)

Option 1 seems the best for our needs.

@Yi-Tseng Yi-Tseng linked a pull request Jan 26, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant