Remove and promote DigitalOcean

[Ignasi Barrera <na...@apache.org>]

Hi!

The v1 of the DigitalOcean API will be turned off on November 9. I
plan to remove the digitalocean provider from master ASAP.

Our v2 provider has been around for a short time (since 1.9.1), but
despite being a young one I'll promote to promote it to the main repo:

* It implements all the available compute abstractions.
* The structure and workflows are the same from the v1 provider, and
that has proven to work pretty well.
* I've been using in production from my fork without major issues.
* Has a complete test suite and all live tests have been passing
consistently since it was created.
* It's already the version that will come with the latest version of
the Jenkins jclouds-plugin.


Anyone against the removal of v1 and promotion of v2?

Re: Remove and promote DigitalOcean

[Ignasi Barrera <ig...@gmail.com>]

> I would say go ahead, even if there are known issues. We should also plan for a release with it..

Agree. We should start planning the 2.0.0 release and focus on working
on what we want to be in it. Regarding compute, my must-have list is:

* Promote: Azure compute, Docker, Profitbricks and DigitalOcean2 (all
are finished and only need a bit more testing).
* Improve the image cache to eliminate the race conditions it presents
when using the ImageExtension. I have a branch where I've done ~half
the work.

Re: Remove and promote DigitalOcean

[Zack Shoylev <za...@RACKSPACE.COM>]

I would say go ahead, even if there are known issues. We should also plan for a release with it..

________________________________________
From: Ignasi Barrera <na...@apache.org>
Sent: Wednesday, October 28, 2015 5:03 PM
To: dev@jclouds.apache.org
Subject: Remove and promote DigitalOcean

Hi!

The v1 of the DigitalOcean API will be turned off on November 9. I
plan to remove the digitalocean provider from master ASAP.

Our v2 provider has been around for a short time (since 1.9.1), but
despite being a young one I'll promote to promote it to the main repo:

* It implements all the available compute abstractions.
* The structure and workflows are the same from the v1 provider, and
that has proven to work pretty well.
* I've been using in production from my fork without major issues.
* Has a complete test suite and all live tests have been passing
consistently since it was created.
* It's already the version that will come with the latest version of
the Jenkins jclouds-plugin.


Anyone against the removal of v1 and promotion of v2?