Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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

Run BMO e2e with Kubevirt backed BareMetalHosts #1736

Open
lentzi90 opened this issue May 20, 2024 · 7 comments
Open

Run BMO e2e with Kubevirt backed BareMetalHosts #1736

lentzi90 opened this issue May 20, 2024 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@lentzi90
Copy link
Member

User Story

As a developer I would like to use kubevirt as "backend" for the BareMetalHosts in the e2e tests since it would greatly simplify the setup and reduce the requirements.

Detailed Description

Kubevirt has accepted a proposal for BMC support. Once it is implemented, we could make use of kubevirt in our e2e tests (and for development with tilt etc.).
To make this happen, we should help out with the implementation (see the implementation phases in the proposal).
Related issue: starbops/kubevirtbmc#1

/kind feature

@metal3-io-bot metal3-io-bot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels May 20, 2024
@dtantsur
Copy link
Member

I'm for it, but here is a caveat: I don't know how many features they're going to implement. Sushy-tools also supports virtual media and firmware settings, for instance. There is a WIP effort to make it support (emulate, of course) firmware updates.

@Rozzii
Copy link
Member

Rozzii commented May 29, 2024

/triage accepted
On the 2024.29.5 Community meeting we have agreed to accept this, but let's first implement the Kube-Virt support for IPMI and let's see how that behaves.

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels May 29, 2024
@Rozzii Rozzii moved this to Backlog in Metal3 - Roadmap Jun 28, 2024
@metal3-io-bot
Copy link
Contributor

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

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 27, 2024
@Rozzii
Copy link
Member

Rozzii commented Aug 28, 2024

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 28, 2024
@metal3-io-bot
Copy link
Contributor

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

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 26, 2024
@lentzi90
Copy link
Member Author

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 27, 2024
@Rozzii
Copy link
Member

Rozzii commented Nov 29, 2024

/lifecycle frozen

@metal3-io-bot metal3-io-bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: Backlog
Development

No branches or pull requests

4 participants