I agree on not including labs providers in jclouds releases anymore and just publishing the snapshots. If anyone is interested in promoting a provider, pull requests are welcome to have them moved to the main repository!
On Fri, Dec 17, 2021 at 11:40 AM Ignasi Barrera <ignasi.barr...@gmail.com> wrote: > > +1 > > On Fri, Dec 17, 2021 at 7:46 AM Andrew Gaul <g...@apache.org> wrote: > > > > I opened https://github.com/apache/jclouds/pull/127 to move the glacier > > provider to main repo. I propose removing all the labs integration from > > the release process which means the following will only publish as > > SNAPSHOTs: > > > > jclouds-labs: > > abiquo > > aliyun-ecs > > cdmi > > cloudsigma2 > > cloudsigma2-hnl > > cloudsigma2-lvs > > cloudsigma2-mia > > cloudsigma2-sjc > > cloudsigma2-wdc > > cloudsigma2-zrh > > dimensiondata > > joyentcloud > > joyent-cloudapi > > oneandone > > profitbricks-rest > > vagrant > > vsphere > > > > jclouds-labs-aws: > > aws-elb > > aws-iam > > aws-rds > > elb > > iam > > jclouds > > rds > > > > jclouds-labs-openstack: > > openstack-glance > > openstack-heat > > openstack-marconi > > openstack-poppy > > openstack-trove > > rackspace-autoscale > > rackspace-autoscale-uk > > rackspace-autoscale-us > > rackspace-cdn-uk > > rackspace-cdn-us > > rackspace-cloudbigdata > > rackspace-cloudbigdata-us > > rackspace-clouddatabases-uk > > rackspace-clouddatabases-us > > rackspace-cloudqueues-uk > > rackspace-cloudqueues-us > > rackspace-orchestration-uk > > rackspace-orchestration-us > > > > Does want to keep any of these and migrate them to the main repo? We > > have a promotion guide: > > > > https://cwiki.apache.org/confluence/display/JCLOUDS/How+to+Promote+a+Provider > > > > On Sun, Sep 19, 2021 at 11:12:50AM +0900, Andrew Gaul wrote: > > > One of the frictions during jclouds releases is the presence of multiple > > > jclouds-labs repositories. The intent of labs was to provide a nursery > > > for new providers before moving into the main repo but instead has > > > become an old-age home. Could we move the handful of providers that > > > users care about into the main repo? We can either delete the labs > > > providers or just stop releasing them. > > > > > > Here are the top providers by downloads last month: > > > > > > $ sort -r -t'"' -k4 -n Downloads/stats_slices.csv | head > > > "oauth","2513","0.11768286675214767" > > > "googlecloud","2424","0.11351503431797028" > > > "google-compute-engine","2371","0.11103305965662003" > > > "openstack-glance","1997","0.09351877868175507" > > > "openstack-neutron","1920","0.08991289883852005" > > > "openstack-marconi","614","0.02875339426100254" > > > "rackspace-cloudfiles","435","0.02037089131772518" > > > "glacier","409","0.01915331929922104" > > > "rackspace-cloudfiles-us","386","0.01807623915374279" > > > "docker","348","0.016296712681651115" > > > > > > oauth, googlecloud, and google-compute-engine moved to the main repo in > > > 2.0.0 and 2/3 of the downloads for openstack-glance and > > > openstack-neutron are for 1.8.1! Compare with over 50,000 downloads per > > > month of jclouds-core which suggests these labs providers are largely > > > unused. > > > > -- > > Andrew Gaul > > http://gaul.org/
