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

IronicStandalone really needs init-Pod(ipa-downloader)? #40

Open
matthewei opened this issue May 29, 2024 · 7 comments
Open

IronicStandalone really needs init-Pod(ipa-downloader)? #40

matthewei opened this issue May 29, 2024 · 7 comments
Assignees
Labels
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

Some times we can build a http server out of cluster and we can also ues it to be as a image-server. And we can upload kernal and ramdisk into it. So I think we may don't need the init-Pod in Ironic's Pod.

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label May 29, 2024
@matthewei
Copy link
Author

It is a required option in our project. So I think we should provide users with a configurable item.

@dtantsur
Copy link
Member

/triage accepted

I concur. We also don't use IPA-downloader in OpenShift. I'm not sure what the best API for that is, maybe as simple as a cacheAgentImage boolean flag.

@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
@matthewei
Copy link
Author

In fact I would like to update official-docs to tell user. You should get and upload IPA to the HTTP server. But if one want to use it. we can define a acheAgentImage boolean flag.

@matthewei
Copy link
Author

@dtantsur could you assign it to me? I want to realize it.

@matthewei
Copy link
Author

/assign

@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 5, 2024
@Rozzii
Copy link
Member

Rozzii commented Sep 11, 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 Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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