[RFE] Allow an operator to block all future bios deployments
Bug #2068530 reported by
Julia Kreger
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
In Progress
|
Wishlist
|
Afonne-CID |
Bug Description
During the Baremetal SIG meeting at CERN in June 2024, one of the items suggested by the audience is a flag or setting which would prevent new deploy in bios mode, to allow operators to functionally block new deployments in an undesirable configuration of bios boot mode. We obviously would want to permit cleaning and recovery of the machine in whatever configured operating mode, but that final pre-deployment should return an error.
A possible option is to just raise an error on verification, which would stop some users but also enable advanced users to proceed.
summary: |
- Allow an operator to block all future bios deployments + [RFE] Allow an operator to block all future bios deployments |
Changed in ironic: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in ironic: | |
assignee: | nobody → Afonne-CID (cidelight) |
Changed in ironic: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
So after discussion, there are basically two separate knobs we need:
- One to block during enrollment / node updates in API --> you cannot set boot mode to bios
- One to prevent *deployment* of a node with boot mode set to BIOS, this would be useful for migrating away from BIOS-based boot or when you have to bootstrap machines via bios booting