search

kadalu / rfcs

RFCs for changes to Kadalu https://kadalu.io/rfcs
4 stars 3 forks source link

New RFC: External Control Plane for Gluster #14

Closed aravindavk closed 4 years ago

aravindavk commented 4 years ago

Signed-off-by: Aravinda Vishwanathapura aravinda@kadalu.io

sankarshanmukhopadhyay commented 4 years ago

LGTM

In a future iteration we should solicit inputs on how authorization and access of users can be integrated with existing IAM pieces. Traditionally, Gluster has not documented any specific ways instead, leaving that to the directory services or, IAM frameworks to decide.

howels commented 4 years ago

Suggestion for increased adoption - would it be possible to migrate KIS PVs from being Heketi-managed to being Kadalu-managed? If a migration route was possible this would make it feasible for users with running workloads to contemplate a switch. Not always possible to remove and re-add the storage.

aravindavk commented 4 years ago

Suggestion for increased adoption - would it be possible to migrate KIS PVs from being Heketi-managed to being Kadalu-managed? If a migration route was possible this would make it feasible for users with running workloads to contemplate a switch. Not always possible to remove and re-add the storage.

Existing Gluster Cluster can be migrated to use this External Control plane without changing the Filesystem. This solution is for non-Kubernetes use cases. For the Kubernetes use case, Kadalu already supports using external Gluster Volumes(Heketi or independently managed Gluster Cluster). See here: https://kadalu.io/docs/k8s-storage/latest/external-gluster-storage

howels commented 4 years ago

Suggestion for increased adoption - would it be possible to migrate KIS PVs from being Heketi-managed to being Kadalu-managed? If a migration route was possible this would make it feasible for users with running workloads to contemplate a switch. Not always possible to remove and re-add the storage.

Existing Gluster Cluster can be migrated to use this External Control plane without changing the Filesystem. This solution is for non-Kubernetes use cases. For the Kubernetes use case, Kadalu already supports using external Gluster Volumes(Heketi or independently managed Gluster Cluster). See here: https://kadalu.io/docs/k8s-storage/latest/external-gluster-storage

Thanks. We have a mix of Kubernetes and non-Kubernetes volumes in our GlusterFS clusters.

Out of interest why do you recommend sharing Gluster volumes for multiple PV? We have some errors with metadata filling up in our Gluster-backed PV and blocking writes at present and would be anxious about a similar issue stopping multiple PVs at once.