This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
Currently, Volume Snapshots in Cloudstack take a considerable amount of time to complete thereby blocking other operations on the VM. This is because, the volume snapshot operation involves 2 steps - creating a snapshot of the volume on primary storage and then backing it up on secondary storage. This feature will separate the creation of the snapshot on primary and its copying onto secondary.
This is a functional specification of the feature "Separate creation and backup operations for a volume snapshot".
|First Revision||May 2nd, 2017|
This feature will only improve the experience with volume snapshots.
A separate thread pool will be maintained for backup task.
An additional param will be added to CreateSnapshotCmd, on whose value the decision of, if to separate the snapshot and copy operations or if to continue with the existing one is decided.
A checkbox will be added to the "Create Volume Snapshot" dialog box, which when checked, snapshot and copy operations will be separated and if left unchecked the existing flow continues.
Parallel operations that can happen during backing up of snapshot
All the other VM/Volume operations not listed above are not supported.