~~Restore SFM VM State Through Omnia HA Automation~~ **CANCELLED — SFM 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
- 3/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- infrastructure
Research direction
There is no implementation to start: the issue cancels the SFM VM bring-up, recovery, and high-availability automation, and says SFM lifecycle stays externally managed. Do not start a patch. Check whether the related BR-22381 scope, which covers only guest delivery for non-OIM functional groups, needs any follow-up. Done means the issue is closed or confirmed as cancelled.
Written by the indexing model from the issue text.
Description
Restore SFM VM State Through Omnia HA Automation
Status
Cancelled
Cancellation Decision
SFM is a non-Omnia appliance. Omnia will not trigger SFM VM bring-up, restart, recovery, backup, restore, fencing, or high availability. Those operations remain externally managed by the appliance and virtualization owners.
BR-22381 does not supersede this capability; it now covers only VM guest delivery for Omnia-controlled non-OIM functional groups.
Resulting Ownership Boundary
- SFM application and VM recovery remain external.
- Omnia network integrations may consume an available SFM service but do not control its VM lifecycle.
- No OIM Pacemaker or Proxmox workflow is introduced for SFM recovery.
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Nixtla/mlforecast#823 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/ML-For-Beginners#1061 ·
-
bot-found documentation priority: P3
Difficulty 2/5 Under an hour Newbie friendliness 82/100
madenvel/KalinkaPlayer#503 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
EleutherAI/lm-evaluation-harness#4508 ·
Maintainers usually reply within 1 day