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

Require a Behavioral model and conformance tests #39

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Require a Behavioral model and conformance tests #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion OPI_RELEASE_APPROACH.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ are not meant to be used in production.**

The details of what this will look like are as follows:


* The protobuf files themselves
* Some language specific bindings for those files. For example, bindings for
C++, golang, python, and Rust
Expand All @@ -42,6 +43,8 @@ The details of what this will look like are as follows:
* sZTP code, including a custom client
* A Container Storage Interface (CSI) library, client and helpful
utilities called [goopicso](https://github.com/opiproject/goopicsi)
* A behavioral model representing a DPU/IPU, against which all APIs/code will
be implemented.

OPI is tracking work in the following specific areas, which will each contain
pieces of the above release artifacts:
Expand Down Expand Up @@ -84,7 +87,7 @@ platform for both developer testing as well as verification. Each time a new
API is added, the API will need to be implemented in the integration test
suite in the OPI PoC repository.

OPI will also produce a test plan, including a set of concrete tests, which
OPI will also produce a test plan, including a set of conformance tests, which
each vendor is recommended to run against their HW DPU or IPU devices
running the OPI APIs. The vendors will then be encouraged to upload those
test results to a webpage containing a table of all the vendor results.
Expand Down