Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 0 additions & 4 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,5 +1 @@
.envrc.local
infra/local/.vagrant/
infra/local/kubeconfig
infra/kind/kubeconfig.yaml
redfish-mockup-clients
11 changes: 5 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,17 +13,16 @@ The `tests` directory contains a suite of tests based on [chainsaw](https://kyve
* A metal-operator installation and BMC to run tests against. This repository usually uses the locally virtualised [metal-lab](https://github.com/simontesar/metal-lab) to develop or verify functionality of the actual tests. You can use the lab setup as a reference.

### Usage
The server to run a test against is configured by passing a values file to chainsaw via `VALUES`. There is no default, tests fail unless `VALUES` is set. To just see the suite run, use `infra/kind/values-basic-go.yaml`, which points to a Redfish mock setup in the [`kind` environment](environments.md).
The server to run a test against is configured by passing a values file to chainsaw via `VALUES`. To try the tests without using your own BMC, clone the [`metal-lab`](https://github.com/simontesar/metal-lab) repository and refer to its `README` to bring it up.

```bash
# Examples
make test VALUES=infra/kind/values-basic-go.yaml # Run all tests
make test/01-bmc-registration VALUES=infra/kind/values-basic-go.yaml # Run a specific test
make test/03-power-annotation VALUES=/path/to/metal-lab/values-containerlab-node1.yaml # Run against a specific BMC
export KUBECONFIG=/path/to/metal-lab/kubeconfig.yaml
make test VALUES=/path/to/metal-lab/values-containerlab-node1.yaml # Run all tests
make test/01-bmc-registration VALUES=/path/to/metal-lab/values-containerlab-node1.yaml # Run a specific test
make test/03-power-annotation VALUES=/path/to/your-bmc.yaml # Run against your own BMC
```

The [`metal-lab`](https://github.com/simontesar/metal-lab) repository provides a standalone containerlab-based environment and ships its own `VALUES` `values-containerlab-node1.yaml` / `values-containerlab-node2.yaml`. Clone the metal-lab repository and refer to its `README` to try the suite of tests without your own BMC.

### Bring your own BMC
To run tests against your own BMC, copy these values into a new file:
```yaml
Expand Down
56 changes: 0 additions & 56 deletions config/metal-operator/ignition-template.yaml

This file was deleted.

28 changes: 0 additions & 28 deletions config/metal-operator/kustomization.yaml

This file was deleted.

9 changes: 0 additions & 9 deletions config/metal-operator/macdb-secret.yaml

This file was deleted.

42 changes: 0 additions & 42 deletions config/metal-operator/manager_patch.yaml

This file was deleted.

11 changes: 0 additions & 11 deletions config/metal-operator/metaldata_patch.yaml

This file was deleted.

14 changes: 0 additions & 14 deletions config/metal-operator/registry_service.yaml

This file was deleted.

51 changes: 0 additions & 51 deletions config/metalprobe-mock-controller/clusterrole.yaml

This file was deleted.

15 changes: 0 additions & 15 deletions config/metalprobe-mock-controller/clusterrolebinding.yaml

This file was deleted.

62 changes: 0 additions & 62 deletions config/metalprobe-mock-controller/deployment.yaml

This file was deleted.

15 changes: 0 additions & 15 deletions config/metalprobe-mock-controller/kustomization.yaml

This file was deleted.

7 changes: 0 additions & 7 deletions config/metalprobe-mock-controller/serviceaccount.yaml

This file was deleted.

20 changes: 0 additions & 20 deletions config/redfish-mockups/components/go-mockup/bmc.yaml

This file was deleted.

10 changes: 0 additions & 10 deletions config/redfish-mockups/components/go-mockup/bmcsecret.yaml

This file was deleted.

Loading
Loading