Skip to content

Support using an Ironic object to fetch the necessary information on start-up #2101

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.

Sign up for GitHub

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

Jump to bottom
Open
dtantsur opened this issue Dec 5, 2024 · 4 comments
Open

Support using an Ironic object to fetch the necessary information on start-up #2101

dtantsur opened this issue Dec 5, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@dtantsur
Copy link
Member

dtantsur commented Dec 5, 2024

With the introduction of ironic-standalone-operator and its Ironic resource, BMO can potentially fetch most information it needs on start-up (Ironic location, networking and credentials) from such an object. Together with #2100, it may make the existence of deploy.sh/deploy-cli unnecessary. The installation then will boil down to something like

make install deploy IRONIC_NAME=my-ironic

/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 Dec 5, 2024
@dtantsur dtantsur mentioned this issue Dec 5, 2024
Open
@Rozzii
Copy link
Member

Rozzii commented Dec 18, 2024

/triagge accepted

@Rozzii
Copy link
Member

Rozzii commented Dec 18, 2024

/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 Dec 18, 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 Mar 18, 2025
@Rozzii
Copy link
Member

Rozzii commented Mar 19, 2025

/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 Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dtantsur @Rozzii @metal3-io-bot