~~Proxmox-Based VM Lifecycle Management for OME and SFM~~ **CANCELLED — appliance VM lifecycle remains externally managed**
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Under an hour
- Newbie friendliness
- 4/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- infrastructure
Research direction
This issue records a cancelled decision and asks for no code change, so there is no file, test or entry point to start from. Do not pick it up. If you want to contribute to the ownership boundary or BR-22381, confirm the scope with the maintainers first; no work is defined here.
Written by the indexing model from the issue text.
Description
Proxmox-Based VM Lifecycle Management for OME and SFM
Status
Cancelled
Cancellation Decision
Omnia will not own OME/Polaris or SFM VM instantiation, start, stop, restart, placement, migration, backup, restore, fencing, or high availability. These are non-Omnia appliances whose VM and application lifecycle remain externally managed.
BR-22381 no longer supersedes this appliance-lifecycle capability. BR-22381 is limited to hypervisor-neutral VM guest delivery for Omnia-controlled non-OIM functional groups.
Resulting Ownership Boundary
- Appliance and virtualization owners manage OME/Polaris and SFM VM lifecycle.
- Omnia may consume appliance services through separately defined integrations but does not operate their VMs.
- Provider-specific appliance automation is not part of the initial product scope.
- 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 82 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/sagemaker-python-sdk#6554 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
huggingface/diffusers#15170 ·
Maintainers usually reply within 1 day
-
[BUG] LLM conflict check ignores MNEMOSYNE_LLM_MAX_TOKENS, so reasoning models return empty repliesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mnemosyne-oss/mnemosyne#1325 ·
Maintainers usually reply within 1 day
-
enhancement meshtastic-2.8
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pskillen/meshflow-api#459 ·