search

metal3-io / metal3-dev-env

Metal³ Development Environment
Apache License 2.0
113 stars 118 forks source link

Add periodic tests for local ironic scenario #1418

Open tuminoid opened 5 months ago

tuminoid commented 5 months ago

After https://github.com/metal3-io/metal3-dev-env/pull/1404 merges and we move Ubuntu to default to Minikube ephemeral cluster, we don't test local (non-k8s) ironic installation anymore. We still plan to keep it around, so we need a periodic test at a minimum to keep it around. Otherwise it will rot and break fast.

Rozzii commented 5 months ago

/triage accepted

Rozzii commented 5 months ago

/help

metal3-io-bot commented 5 months ago

@Rozzii: This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/metal3-io/metal3-dev-env/issues/1418): >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dtantsur commented 5 months ago

Thinking aloud: once ironic-standalone-operator matures, maybe we can add an additional Go binary to it that will run Ironic locally. This way, we can keep configuration in sync. Or maybe I'm overthinking it?

metal3-io-bot commented 2 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Rozzii commented 2 months ago

/remove-lifecycle stale