cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Suich (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-4774) Provide Option to Quiesce VMs While Taking Snapshots
Date Fri, 10 Jan 2014 05:01:52 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Suich closed CLOUDSTACK-4774.
-----------------------------------


> Provide Option to Quiesce VMs While Taking Snapshots
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-4774
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4774
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Chris Suich
>
> CloudStack currently snapshots vm disks by taking hypervisor snapshots. However, when
implementing the storage subsystem API interface takeSnapshot(), the VM associated with the
requested volume is not quiesced since a hypervisor snapshot is not necessarily taken. When
creating a storage level snapshot, there are ways around this and 'quiescing' the vm without
actually quiescing it (through hypervisor APIs). I would like to propose that there be an
option to quiesce VMs when taking snapshots both manually and through recurring snapshot policies.
One issue I see with this is that this option is not always applicable. If the default storage
provider is used, a hypervisor snapshot will be taken and therefore the VM will always be
quiesced. Some storage providers may not respect the user's request to quiesce. Because of
this, I suggest that the option be shown to the user as 'Quiesce VM (if applicable)'. This
indicates to the user that the option will be passed to the management server and respected
if possible.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message