-
Notifications
You must be signed in to change notification settings - Fork 143
Open
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.
Description
The BMO e2e tests have been designed to work also on real hardware. We should check that it actually works, and document how to do it. I think this could fit well in the user-guide, targeted at contributors, but perhaps also as a way for users to check that BMO works with their hardware. A conformance test if you like.
From a high perspective, the process should look something like this:
- Write kustomize overlays for Ironic and BMO (or deploy them manually). The e2e overlays we use in CI gives an example for how this could look like. See this and this.
- Set up a Kubernetes cluster (e.g. using kind or minikube). The test framework can do this automatically, but it is likely that some special configuration is needed, in which case it is better to do it manually.
- Write config file to adapt the e2e suite to the specific environment.
- Run the tests!
Metadata
Metadata
Assignees
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue is ready to be actively worked on.Indicates an issue is ready to be actively worked on.
Type
Projects
Status
Todo