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 support for UEFI HTTP boot #1822

Open
elfosardo opened this issue Jul 10, 2024 · 4 comments
Open

Add support for UEFI HTTP boot #1822

elfosardo opened this issue Jul 10, 2024 · 4 comments
Assignees
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

@elfosardo
Copy link
Member

User Story

As an operator I would like to use the UEFI HTTP boot feature to be able to deploy bare metal hosts with boot over HTTP(s)

Detailed Description

HTTP boot is available since at least 9 years, it was standardized in UEFI version 2.5, and it's considered as a natural valid replacement for PXE boot.
It addresses PXE issues for security, relying on HTTPs and using a reliable TCP connection, and scalability and performance, for example with the possibility of using HTTP load balancers.
In general HTTP boot grants a faster, more reliable and more secure way to obtain operating system images and EFI executables during a network boot process.

Anything else you would like to add:

The ironic implementation is already done so we just need to add a new hardware driver to BMO to support it.

/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 Jul 10, 2024
@elfosardo
Copy link
Member Author

design proposal metal3-io/metal3-docs#459

@elfosardo elfosardo self-assigned this Jul 10, 2024
@dtantsur
Copy link
Member

/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 Jul 24, 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 Oct 22, 2024
@Rozzii
Copy link
Member

Rozzii commented Oct 23, 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 Oct 23, 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. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: BMO WIP
Development

No branches or pull requests

4 participants