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

Add operators to suport allocating empty bare-metal. #649

Open
sailorvii opened this issue Jun 22, 2022 · 11 comments
Open

Add operators to suport allocating empty bare-metal. #649

sailorvii opened this issue Jun 22, 2022 · 11 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

@sailorvii
Copy link
Contributor

sailorvii commented Jun 22, 2022

User Story

As developers, we are developing a feature to support a bare-metal platform. I'm not sure if it's useful for others.

Detailed Description

In our scenario, some customers like to acquire an empty bare-metal host or a group of hosts.
Furthermore, users hope that host could pre-install the customized application.
It's a pure bare-metal management platform without guest Kubernetes.

Anything else you would like to add:
A machine operator, a machine-deployment operator.

[Miscellaneous information that will assist in solving the issue.]
The user could specify the machine with some conditions:

  1. Image to be installed.
  2. Host label to be chosen.
  3. User data specified by the customer such as "what application I want to install at the start time".

A machine deployment will define a group of machines with the same configuration. It will define the number of replicas. It could scale up/down.

/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 Jun 22, 2022
@Rozzii
Copy link
Member

Rozzii commented Jun 22, 2022

The community is willing to continue the discussion if you provide a design document PR in metal3-docs repository.
Based on the design document the community will decide whether it is OK to continue with the implementation or not.

Also please not that using the "machine" word has issues in our community because it refers to the Machine object in Metal3 context so please refrain from using it if you are not specifically mean the Machine object.
Please note that at the moment we don't have resources to implement this feature so if it is accept you have to do the implementation.
/triage accepted

@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 Jun 22, 2022
@sailorvii
Copy link
Contributor Author

I'll provide the design document soon.

@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 Sep 21, 2022
@furkatgofurov7
Copy link
Member

/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 Sep 21, 2022
@sailorvii
Copy link
Contributor Author

sailorvii commented Oct 8, 2022

Is there anybody who could help to review the proposal metal3-io/metal3-docs#268? Thanks.

@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 Jan 6, 2023
@Rozzii
Copy link
Member

Rozzii commented Feb 1, 2023

/remove-lifecycle stale

1 similar comment
@furkatgofurov7
Copy link
Member

/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 Feb 1, 2023
@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 May 2, 2023
@Rozzii
Copy link
Member

Rozzii commented Sep 20, 2023

I think in principle we should support this use-case

@Rozzii Rozzii reopened this Sep 20, 2023
@Rozzii
Copy link
Member

Rozzii commented Sep 20, 2023

/life-cycle-frozen

@Rozzii Rozzii 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 Oct 11, 2023
@Rozzii Rozzii moved this to BMO on hold / blocked in Metal3 - Roadmap Jun 28, 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 on hold / blocked
Development

No branches or pull requests

4 participants