Failure on restore -> allow to "fix" OMAP
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 132
- Forks
- 69
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 47
Description
In the case where there is a configuration in the OMAP that cannot be applied after restore we currently fail the daemon/SPDK process, so there is no way to fix any configuration errors in the OMAP (at least for a single GW). An example is if the host IPs changed and there is still a listener configuration in the OMAP for the old IP.
To remedy this situation we could introduce an admin mode for the GW daemon that allows to do changes to the OMAP without applying them to SPDK, e.g. --config-change-only. We can restrict to only allow certain operations in this mode, e.g. only delete so we don't run into issues where a SPDK response is required.
Contributor 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.
Research direction
Start by locating the gateway daemon's restore path and OMAP configuration operations, then trace where SPDK application failures currently terminate the process. The proposed outcome is a config-change-only admin mode, such as --config-change-only, that permits only safe OMAP changes such as deletion without applying them to SPDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100