Not sure If I read it right, does this mean VCloud support will be removed
in 1.8.x onward?

This will be big dent for Jcloud users.



On Sun, Nov 16, 2014 at 11:26 PM, Adrian Cole <adrian.f.c...@gmail.com>
wrote:

> TL;DR;
>
> jclouds will stop maintaining vcloud in 1.8.x. We will remove vcloud
> (and the vcloud-director labs provider) in version 1.9.0.
>
> Our vcloud codebase is old, unsupported by cloud providers and a
> crippling maintenance debt on the project. If we want jclouds to
> endure, we have to make difficult decisions such as this.
>
> The removal of vcloud is being tracked in the following jira
> https://issues.apache.org/jira/browse/JCLOUDS-780
>
> Best,
> -A
>
> Here's a copy of the description of JCLOUDS-780
>
> For over a month, we've discussed the fate of vcloud [1]. For example,
> we've already removed all vcloud providers as they no longer work with
> version 1.0 [2]. Also users who contact us either run custom forks
> [3], or also find features they need missing [4].
>
> Eventhough the replacement code was supposed to be vcloud-director, it
> has never left labs, and has too much technical debt to continue
> attempting to support [5].
>
> A couple stakeholders have offered they may be able to help [6], or
> encourage vmware to add a new api to cover modern products [7].
>
> Good wishes aside, the facts remain that we have 2 aging apis, that
> are unsupportable in current form. Keeping vcloud and vcloud-director
> codebases limits the project's ability to move forward, so we must
> drop them.
>
> Users who wish to continue on either codebase will need to maintain
> their own fork.
>
> When it comes time to start vcloud products again, we'll want to start
> very small, with at least 2 champions, and some means to keep tests
> passing. If we don't, we'll surely repeat history again.
>
> [1] http://markmail.org/thread/4p22wkbrd4mncmss
> [2] https://issues.apache.org/jira/browse/JCLOUDS-743
> [3] http://markmail.org/message/gxcl37zq2pnn22sf
> [4] http://markmail.org/thread/ligd5sbkmvoo7vdi
> [5] http://markmail.org/thread/s5i6i4nr6f5k5wew
> [6] http://markmail.org/thread/5fav2wa6ylxbqpdy
> [7] http://markmail.org/thread/q4otznoqoygrz64b
>

Reply via email to