GitHub user syed reopened a pull request:
https://github.com/apache/cloudstack/pull/1600
Support Backup of Snapshots for Managed Storage
This PR adds an ability to Pass a new parameter, locationType,
to the âcreateSnapshotâ API command. Depending on the locationType,
we decide where the snapshot should go in case of managed storage.
There are two possible values for the locationType param
1) `Standard`: The standard operation for managed storage is to
keep the snapshot on the device. For non-managed storage, this will
be to upload it to secondary storage. This option will be the
default.
2) `Archive`: Applicable only to managed storage. This will
keep the snapshot on the secondary storage. For non-managed
storage, this will result in an error.
The reason for implementing this feature is to avoid a single
point of failure for primary storage. Right now in case of managed
storage, if the primary storage goes down, there is no easy way
to recover data as all snapshots are also stored on the primary.
This features allows us to mitigate that risk.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/syed/cloudstack snapshot-archive-pr
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1600.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1600
----
commit 252942f29c5c485b7d60b6ae8be33165db1b0cfb
Author: Syed <[email protected]>
Date: 2016-06-30T17:37:33Z
Support Backup of Snapshots for Managed Storage
This PR adds an ability to Pass a new parameter, locationType,
to the âcreateSnapshotâ API command. Depending on the locationType,
we decide where the snapshot should go in case of managed storage.
There are two possible values for the locationType param
1) `Standard`: The standard operation for managed storage is to
keep the snapshot on the device. For non-managed storage, this will
be to upload it to secondary storage. This option will be the
default.
2) `Archive`: Applicable only to managed storage. This will
keep the snapshot on the secondary storage. For non-managed
storage, this will result in an error.
The reason for implementing this feature is to avoid a single
point of failure for primary storage. Right now in case of managed
storage, if the primary storage goes down, there is no easy way
to recover data as all snapshots are also stored on the primary.
This features allows us to mitigate that risk.
commit 374944a3e2670f78ebdcdffe065a64ee89e3ac96
Author: Syed <[email protected]>
Date: 2016-07-05T17:21:56Z
Detach from hypervisor after copy to secondary storage
commit 3d30645baca863b31f2e10e68def606de25666b1
Author: Mike Tutkowski <[email protected]>
Date: 2016-07-13T19:35:43Z
A couple Marvin changes and new/updated Marvin tests
commit 50d0b17ae86476a3ef6b17fd3f8e2a6e311ceff5
Author: Syed Mushtaq Ahmed <[email protected]>
Date: 2016-07-13T23:53:00Z
Merge pull request #5 from mike-tutkowski/snapshot-archive-pr
A couple Marvin changes and new/updated Marvin tests
commit a96519970d09c22be5470422c6f208f6812f7c90
Author: Mike Tutkowski <[email protected]>
Date: 2016-07-14T16:35:13Z
Changing locationType to PRIMARY and SECONDARY
commit 6baa19635e074923e797d748c0bb6b7efdf24a4f
Author: Syed <[email protected]>
Date: 2016-09-01T21:38:46Z
Fix review comments
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
