jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-780) Remove vcloud and vcloud-director from jclouds
Date Mon, 17 Nov 2014 16:19:34 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214791#comment-14214791
] 

ASF subversion and git services commented on JCLOUDS-780:
---------------------------------------------------------

Commit 6f974f34b51d02960196cc2868d79e703634d7e8 in jclouds's branch refs/heads/master from
[~adrian.f.cole@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=6f974f3 ]

JCLOUDS-780 Remove vcloud.


> Remove vcloud and vcloud-director from jclouds
> ----------------------------------------------
>
>                 Key: JCLOUDS-780
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-780
>             Project: jclouds
>          Issue Type: Task
>          Components: jclouds-core
>            Reporter: Adrian Cole
>            Assignee: Adrian Cole
>             Fix For: 1.9.0
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message