Automated BIOS Profile Management via Functional Groups
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 3/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- infrastructure
Research direction
This issue is cancelled and no code change is requested, so there is nothing to implement. Read the Cancellation Decision and Resulting Ownership Boundary sections to see which layers own BIOS settings. Done means no work is started here; a separate issue is needed if you want Omnia to validate a BIOS prerequisite.
Written by the indexing model from the issue text.
Description
Automated BIOS Profile Management via Functional Groups
Status
Cancelled — 2026-09-25
Cancellation Decision
BIOS settings remain managed through the accepted OME/Polaris settings experience, which applies changes through iDRAC to the physical BIOS. Omnia will not introduce another BIOS-policy abstraction between the administrator and those existing management layers.
The proposed capability would have created three successive management abstractions before the authoritative setting: Omnia policy → OME/Polaris → iDRAC → BIOS. This would increase drift, troubleshooting ambiguity, and ownership overlap without validated customer value.
Resulting Ownership Boundary
- OME/Polaris owns the administrator-facing BIOS settings workflow.
- iDRAC owns device-level BIOS configuration execution.
- Omnia may validate or report an unmet BIOS prerequisite but does not remediate BIOS settings through this cancelled capability.
- Slurm SPANK/plugstack integration is not a replacement BIOS-management path and does not provide a supported runtime BIOS-mutation use case.
Historical Scope
The cancelled proposal would have mapped editable BIOS profiles to Omnia functional groups, queried settings through Redfish, applied differences through iDRAC, and rebooted nodes before OS provisioning. This historical scope is retained for traceability only and is not scheduled for implementation.
Backlog Disposition
The capability is removed from the active priority sequence and retained in the cancelled backlog section.
- Dominant language
- Python
- Stars
- 9
- Forks
- 175
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 137
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dell/omnia
-
`src/telemetry/containers/build_images.sh` should have localcopy build_actionPossibly taken @priti-parate claimed this 24 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dell/omnia#5425 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Warning: SLURM_REPO_URL and SLURM_REPO_NAME must be provided.Possibly taken @priti-parate claimed this 24 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dell/omnia#5423 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
use `hostnamectl` instead of `hostname`Possibly taken @richardhenwood-dell claimed this 81 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Utility to create S3 format Image file from OCI format file hosted on a container image registryOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
URLValidator ignores an explicit empty scheme allowlistPossibly taken @IlyaKhalafi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
tortoise/tortoise-orm#2393 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
frappe/frappe_docker#2046 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
complete_box_iou_loss / complete_box_iou: NaN gradients for zero-height boxes, NaN for point boxesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
AXI SMU SPEC
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
tenstorrent/tt-oca-harness#3556 ·
Maintainers usually reply within 1 day