Skip to content
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

Add proposal for snapshot support #802

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

afritzler
Copy link
Member

Proposed Changes

  • Introduce Snapshot and SnapshotClass resources to allow users to take point-in-time snapshots of the content of a Volume
  • Enhance the Volume resource to include a dataSource field for restoring data from a snapshot
  • Improve data protection and disaster recovery capabilities
  • Provide support for different types of snapshots based on VolumePool capabilities
  • The proposal does not modify existing VolumePool resources
  • The Snapshot resource is not designed to provide a complete backup or archival solution for Volumes
  • The actual creation and readiness of a snapshot can depend on various factors such as Volume size, VolumePool capabilities, and infrastructure performance
  • The Snapshot resource and restoration path are meant to be additional tools in the data protection toolbox, not to replace existing comprehensive disaster recovery and data protection solutions

Fixes #801

- Introduce `Snapshot` and `SnapshotClass` resources to allow users to take point-in-time snapshots of the content of a `Volume`
- Enhance the `Volume` resource to include a `dataSource` field for restoring data from a snapshot
- Improve data protection and disaster recovery capabilities
- Provide support for different types of snapshots based on `VolumePool` capabilities
- The proposal does not modify existing `VolumePool` resources
- The `Snapshot` resource is not designed to provide a complete backup or archival solution for `Volumes`
- The actual creation and readiness of a snapshot can depend on various factors such as `Volume` size, `VolumePool` capabilities, and infrastructure performance
- The `Snapshot` resource and restoration path are meant to be additional tools in the data protection toolbox, not to replace existing comprehensive disaster recovery and data protection solutions

Signed-off-by: Andreas Fritzler <[email protected]>
@afritzler afritzler requested a review from a team as a code owner July 24, 2023 08:53
@github-actions github-actions bot added size/L documentation Improvements or additions to documentation enhancement New feature or request labels Jul 24, 2023
@balpert89
Copy link
Contributor

We have discussed the PR internally and do not see a problem with going forward as-is. We do not recommend going forward with the mentioned alternatives as its either off-loading significant portions to the user (3rd party provider), complicate interaction (storage provider APIs) or restrict flexibility (adding to Volume).

volumeRef:
name: example-volume
snapshotClassRef:
name: example-snapshotclass
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we also have encryption support for Snapshot as Volume encryption support is there?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would expect a transitive behavior here. If the volume is encrypted, the snapshot should be encrypted as well. Plus, the option to encrypt the snapshot explicitly.

@afritzler afritzler requested a review from a team as a code owner May 16, 2024 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request size/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Request for Proposal: Snapshot Support
3 participants