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

One BMO controls multiple Ironic #1667

Open
matthewei opened this issue Apr 13, 2024 · 8 comments
Open

One BMO controls multiple Ironic #1667

matthewei opened this issue Apr 13, 2024 · 8 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

@matthewei
Copy link

User Story
We have many data centers scattered across the country, and we want to create a BMO on the central cloud to manage the ironic of each data center, to achieve the creation of bare metal k8s clusters.

Detailed Description

[A clear and concise description of what you want to happen.]
One BMO can manage several Ironic.

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/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 Apr 13, 2024
@dtantsur
Copy link
Member

This is an interesting request, but it's going to be tricky. For instance: how does BMO know, which Ironic to talk to for each specific BareMetalHost? What should BMO do what only some of the Ironics are available? Should we support migrating hosts between Ironics (if yes, how?)?

On a related note, make sure conductor groups don't solve your problems.

@Rozzii
Copy link
Member

Rozzii commented Apr 24, 2024

/triage accepted
This is a legit feature request but it will be a long design process as far as I can tell, as part of the written proposal we would need to hear about some good justifications of "why multiple Ironic instances can be deployed but not multiple BMOs" .

@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 Apr 24, 2024
@matthewei
Copy link
Author

/triage accepted This is a legit feature request but it will be a long design process as far as I can tell, as part of the written proposal we would need to hear about some good justifications of "why multiple Ironic instances can be deployed but not multiple BMOs" .

I would like to write an article to explain it.

@matthewei
Copy link
Author

One BMO controls multiple Ironic.pdf
@Rozzii @dtantsur Please check the attachment.

@Rozzii Rozzii moved this to BMO WIP 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 6, 2024
@Rozzii
Copy link
Member

Rozzii commented Aug 6, 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 6, 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 4, 2024
@Rozzii
Copy link
Member

Rozzii commented Nov 5, 2024

/remove-lifecycle stale
/lifecycle frozen

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 5, 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: BMO WIP
Development

No branches or pull requests

4 participants