search

metal3-io / baremetal-operator

Bare metal host provisioning integration for Kubernetes
Apache License 2.0
587 stars 254 forks source link

One BMO controls multiple Ironic #1667

Open matthewei opened 7 months ago

matthewei commented 7 months ago

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

dtantsur commented 6 months ago

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 commented 6 months ago

/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" .

matthewei commented 6 months ago

/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 commented 6 months ago

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

metal3-io-bot commented 3 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 3 months ago

/remove-lifecycle stale

metal3-io-bot commented 6 days 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 5 days ago

/remove-lifecycle stale /lifecycle frozen