-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(snapshot,restore): support for local snapshot #53
Conversation
Signed-off-by: mayank <[email protected]>
Signed-off-by: mayank <[email protected]>
Signed-off-by: mayank <[email protected]>
Signed-off-by: mayank <[email protected]>
Signed-off-by: mayank <[email protected]>
…openebs Signed-off-by: mayank <[email protected]>
README.md
Outdated
@@ -62,6 +62,17 @@ spec: | |||
provider: <GCP_OR_AWS> | |||
region: <AWS_REGION> | |||
``` | |||
|
|||
For local snapshot of CStor volume through velero, Refere `example/06-local-volumesnapshotlocation.yaml` to configure `VolumeSnapshotLocation`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to be consistent with 'cloud backup', should we call this as 'local backup'? before changing, lets get opinion from @kmova as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That may create confusion with local copy of the snapshot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For creating local backup using cStor Volume snapshot feature, refer example/06-local-volumesnapshotlocation.yaml
to configure VolumeSnapshotLocation
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few things like adding comments, testcases are required. Overall flow looks to be good, however one more round of review need to be done.
APIs are changed however backup compatibility is maintained.
This involves good amount of changes with respect to approach as well. Now, storage classes with 'WatiForFirstConsumer' may not work. So, its better to get into the early cycles of testing.
Approving this in order to get into early cycles of testing.
Signed-off-by: mayank <[email protected]>
Signed-off-by: mayank <[email protected]>
Created an issue to track test-cases #54. |
Signed-off-by: mayank <[email protected]>
README.md
Outdated
@@ -50,7 +50,7 @@ Run the following command to install development image of OpenEBS velero-plugin | |||
This command will add an init container to Velero deployment to install the OpenEBS velero-plugin. | |||
|
|||
## Configuring snapshot location | |||
To take a backup of CStor volume through Velero, configure `VolumeSnapshotLocation` with provider `openebs.io/cstor-blockstore`. Sample YAML file for volumesnapshotlocation can be found at `example/06-volumesnapshotlocation.yaml`. | |||
To take a cloud backup of CStor volume through Velero, configure `VolumeSnapshotLocation` with provider `openebs.io/cstor-blockstore`. Sample YAML file for volumesnapshotlocation can be found at `example/06-volumesnapshotlocation.yaml`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To take remote backup of cStor volume snapshot to cloud or S3 compatible storage, configure VolumeSnapshotLocation
with provider openebs.io/cstor-blockstore
.
Can you provide samples for popular use cases like:
- Minio
- AWS S3
- GCP buckets.
They could be different commented out YAMLs in the same snapshotlocation example yaml.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Throughout this document - mention remote/cloud backup and local backup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
apiVersion: velero.io/v1 | ||
kind: VolumeSnapshotLocation | ||
metadata: | ||
name: <LOCATION_NAME> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a comment above on example valid location name string.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
spec: | ||
provider: openebs.io/cstor-blockstore | ||
config: | ||
namespace: <OPENEBS_NAMESPACE> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is ok to repeat the comment here on what the namespace means.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
@@ -24,6 +24,6 @@ spec: | |||
bucket: <YOUR_BUCKET> | |||
prefix: <PREFIX_FOR_BACKUP_NAME> | |||
backupPathPrefix: <PREFIX_FOR_BACKUP_PATH> | |||
provider: <GCP_OR_AWS> | |||
provider: <gcp_OR_aws> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there are any know gotchas around permissions or how the buckets are created, please add them as comments in this YAML.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
Gave some minor comments @mynktl - also can you confirm if a test for local backup and restore can be added in this PR or planned for another PR? |
Signed-off-by: mayank <[email protected]>
Ref: openebs/openebs#2844
Changes:
Sample volumeSnapshotLocation: