External-storage: Break up this repo into individual kubernetes-sigs/sig-storage* ones

Created on 18 Dec 2018 · 16Comments · Source: kubernetes-retired/external-storage

There is a nice and quick process for getting a repo in kubernetes-sigs/ now. We already have https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner and https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner.

Track the work for the rest here.

areawefs arecepcephfs areceprbd aredigitalocean areflex areglusteblock areglusteglusterfs areglustesubvol areiscstargetd arelocal-volume arenfs arenfs-client areopenebs lifecyclrotten

Source

wongma7

Most helpful comment

I'm going to break out ceph (cephfs & rbd) provisioner.

cofyc on 19 Dec 2018

👍2

All 16 comments

I'm going to break out ceph (cephfs & rbd) provisioner.

cofyc on 19 Dec 2018

👍2

Submitted a request https://github.com/kubernetes/org/issues/324

cofyc on 24 Dec 2018

Can anyone contribute to this, or..? If so, I would like to volunteer for extracting the nfs provisioner.

alcohol on 16 Jan 2019

I also would like to take part in this action. I can take care of AWS provisioner.

Zyqsempai on 23 Jan 2019

Thanks for interest, migration work after I've copy/pasted the provisioner's directory from here into the root of the new repo might be to: setup dependencies (vendor), make sure it builds, find/replace broken links. But before then I need to request the repos.

About the nfs provisioner: what should it be called? This is an opportunity to differentiate it from nfs-client. I am leaning toward 'nfs-ganesha-provisioner' to make it clear that it is running a ganesha server.

wongma7 on 24 Jan 2019

Are you exporting with history btw? It would be very nice to preserve git commit history for the files being exported.

https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/

alcohol on 25 Jan 2019

bout the nfs provisioner: what should it be called? This is an opportunity to differentiate it from nfs-client. I am leaning toward 'nfs-ganesha-provisioner' to make it clear that it is running a ganesha server.

While I agree that it would make sense to differentiate it more clearly from the nfs-client provisioner, I am not sure if making the specific daemon implementation part of the repository name is a good idea long term. Then again, some other provisioners also include vendor names. So I definitely have no objections to your suggestion. Alternatively I would suggest nfs-daemon or nfs-userspace-daemon. I'll leave the decision making up to you :-)

alcohol on 25 Jan 2019

FYI: The Digitalocean provisioner is deprecated and should be removed at some point (1.14 maybe?).

klausenbusk on 9 Feb 2019

openebs is moving towards CSI. Once that is available, will raise an PR to deprecate it here.

kmova on 13 Mar 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 11 Jun 2019

/remove-lifecycle stale

tsmetana on 11 Jun 2019

I attempted for some more comprehensive overview of what is still relevant in this repo:

EFS provisioner: deprecated by CSI: https://github.com/aws/aws-efs-csi-driver
CephFS provisioner: deprecated by CSI: https://github.com/ceph/ceph-csi
DigitalOcean provisioner: deprecated by CSI:https://github.com/digitalocean/csi-digitalocean
Flex: deprecated by CSI (?), there even exists a CSI adapter: https://github.com/kubernetes-csi/drivers/tree/master/pkg/flexadapter
GlusterFS provisioner: deprecated by CSI https://github.com/gluster/gluster-csi-driver
Gluster Block provisioner: deprecated by CSI https://github.com/gluster/gluster-csi-driver
iSCSI targetd provisioner: no CSI equivalent I'd know of
Local volume static provisioner: deprecated some time ago already, new upstream at https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner
NFS client / NFS provisioner: no CSI equivalent (there is a CSI driver for statically provisioned NFS volumes only)
OpenEBS: no CSI equivalent found (there is some work undergoing though: see the comment above)
Snapshots: deprecated by CSI -- part of the spec, some drivers already include snapshotting support.

Looks like only iSCSI, NFS and OpenEBS are still relevant. The rest probably deserves a deprecation notice.

tsmetana on 11 Jun 2019

👍1

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 9 Sep 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 9 Oct 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 8 Nov 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.