Zun

Support 'delete_on_termination' with mounts

Bug #1780673 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zun
Triaged
Medium
Kien Nguyen

Bug Description

Zun supports create/run containers with Cinder volume bind-mounts. In CLI, this is achieved by:

  $ zun run --mount source=<cinder_volume_id>,destination=<path_in_container> ...

or

  $ zun run --mount size=<cinder_volume_size>,destination=<path_in_container> ...

The first command mount an existing cinder volume to the container. The second command create a cinder volume with specified size and mount it to container.

This bug proposes to add an option to control how to circulate the volume if the container is deleted. For example:

  $ zun run --mount source=<cinder_volume_id>,destination=<path_in_container>,delete-on-termination=<True_or_False> ...

  $ zun run --mount size=<cinder_volume_size>,destination=<path_in_container>,delete-on-termination=<True_or_False> ...

If True, the cinder volume is deleted. If False, it is not deleted. The default should be False.

hongbin (hongbin034)
description: updated
Changed in zun:
status: New → Triaged
importance: Undecided → Medium
Kien Nguyen (kiennt2609)
Changed in zun:
assignee: nobody → Kien Nguyen (kiennt2609)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.