Creating images independent from existing volumes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
You cannot delete the snapshot because a volume depends on it. This happens when a volume is created from a snapshot. Because they share blocks on the backend storage, you can't delete the parent snapshot without deleting volumes that depend on it.
The way to create a volume from a snapshot that is independent of the snapshot is:
- Create a snapshot of the source volume
- Create a volume from the snapshot
- Create an image of the new volume
- Create a new volume from the image
The resulting image will be independent of the source snapshot.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named; start by locating the documentation section covering volumes, snapshots, and images, then check its navigation and formatting conventions. Document the independent-image workflow described in the issue, and consider the work done when readers can follow the steps without needing the source snapshot afterward.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100