spec
spec copied to clipboard
Support for reverting a snapshot
Here at NetApp we make heavy use of the CSI standards in order to implement the NetApp Trident CSI for our storage products. We are investigating how to support snapshot revert
in order to provide near-instantaneous revert for applications that use volumes backed by NetApp storage. We would like to participate in getting those standards added to this spec.
What is the process for proposing new RPC interfaces and state transitions for reverting snapshots?
Is there a KEP that describes how k8s might consume this feature from CSI? Or some other CO?
Adding CSI RPCs without a clear plan for CO consumption is something we try to avoid.
On Fri, Jan 14, 2022, 9:48 AM Adam Haid @.***> wrote:
Here at NetApp we make heavy use of the CSI standards in order to implement the NetApp Trident CSI for our storage products. We are investigating how to support snapshot revert in order to provide near-instantaneous revert for applications that use volumes backed by NetApp storage. We would like to participate in getting those standards added to this spec.
What is the process for proposing new RPC interfaces and state transitions for reverting snapshots?
— Reply to this email directly, view it on GitHub https://github.com/container-storage-interface/spec/issues/498, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAR5KLCWMSMQUCLGLKULWC3UWAZTNANCNFSM5L67TDVA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
I will reach out to sig storage and socialize this idea. Then I'll write up a KEP and see how far we get.