support set volume protected
Currently, glance have supported store in cinder. When glance image store in cinder, the image will be stored as a volume. So, cinder list can find the volume. The user can delete it easily. So, cinder should provide a mechanism that protects the safety of image data. The user can not delete the volume to store image. So I think, the cinder can support a api interface: cinder deactive volume_id or cinder disable volume_id and cinder enable volume_id. When volume is deactived, the volume cannot be deleted.
Blueprint information
- Status:
- Not started
- Approver:
- Sean McGinnis
- Priority:
- Undefined
- Drafter:
- YaoZheng_ZTE
- Direction:
- Needs approval
- Assignee:
- YaoZheng_ZTE
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I think this may need a spec written up to explain the use case and the mechanism proposed. I don't think "deactivate" is the write phrasing for this. Maybe more like "protected".
@Sean, I aggree with you. the 'protected' is much better. I will submit spec as soon as possible.
