oep(zfspv): ability to provision application utilizing zfs pool already running on the node via CSI. #2705
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pawanpraka1
changed the title
pawanpraka1
changed the title
pawanpraka1
changed the title
zfs pool already running on the node via CSI. Signed-off-by: Pawan <pawan@mayadata.io>
| We should be able to create and delete a volume in a kubernetes cluster | ||
| using CSI where the volume has to be created on the ZFS pool which is | ||
| already running on the node and the higher order applications should be | ||
| able to conume this volume. |
| ## Summary | ||
|
|
||
| This proposal describs how OpenEBS can support dynamic provisioning of | ||
| volumes via **CSI** using ZFS dataset that are running on local nodes. |
There was a problem hiding this comment.
Can we mention or rephrase that a ZFS dataset will represent a Kubernetes volume.
| #### Volume Creation Workflow | ||
| - CSI driver will handle CSI request for volume create | ||
| - CSI driver will read the request parameters and create following resources: | ||
| - ZfsVolumeCR _(Kubernetes custom resource)_ |
| When kubernetes schedules the application pod according the Topology mentioned in | ||
| the StorageClass, The CSI will get a NodePublish event. It will get all the volume | ||
| properties from ZfsVolumeCR custom resource and it will fire zfs create command | ||
| and creates the volume. It will get the pool name from the storage class and create |
There was a problem hiding this comment.
Let CSI take in all the values/config/properties from ZFSVolume object.
Let us avoid making use of StorageClass at this stage.
There was a problem hiding this comment.
corrected it. we are taking that from CR only.
| ### 1. CSI create volume | ||
| At CSI when we get a volume create request, we will create a PV object. | ||
| The actual volume will be create at the Node publish time. We will have | ||
| StorageClass at this point. We will create a ZfsVolumeCR with all the |
There was a problem hiding this comment.
It makes sense to publish the ZFSVolume schema in this doc.
There was a problem hiding this comment.
done, added the sample CR for now it may change in future..
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
kmova
approved these changes
Sep 25, 2019
pranjalvyaas
pushed a commit
to pranjalvyaas/openebs
that referenced
this pull request
Oct 1, 2019
…dy running on the node via CSI. (openebs#2705) Initial Design Proposal for supporting provisioning of Local PVs backed by ZFS using CSI Driver. Signed-off-by: Pawan <pawan@mayadata.io> Signed-off-by: pranjalv9 <pranjalvvyas@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposal describs how OpenEBS can support dynamic provisioning of
volumes via CSI using ZFS dataset that are running on local nodes.
Signed-off-by: Pawan pawan@mayadata.io