jclouds 1.6 represents 7 months of refactoring to essentially “reset” the project 4 years after its founding. Most changes didn't affect user interfaces. The bulk of work included removing dependencies, reducing or removing threading, and refactoring to make jclouds do less magic and be easier to code and troubleshoot.
With this foundation in place, our move to the Apache Incubator will be easier on new developers, and allow us to move faster on feature requests moving forward.
NovaApi api = contextBuilder.buildApi(NovaApi.class);
Async
interfaces, jclouds will spawn far less, and in many cases no threads. Future releases will focus on “bring your own executor” design, allowing you to have complete control or forbid threading completely.openstack-cinder
rackspace-clouddns
rackspace-cloudloadbalancers
route53
sts
aws-route53
aws-sts
dynect
rackspace-cloudblockstorage-uk
rackspace-cloudblockstorage-us
rackspace-clouddns-uk
rackspace-clouddns-us
rackspace-cloudloadbalancers-uk
rackspace-cloudloadbalancers-us
ultradns-ws
cloudloadbalancers
- please use the rackspace-cloudloadbalancers
apideltacloud
- please use the ec2
apieucalyptus
- please use the ec2
apinova
- pre-diablo openstack no longer supportedwalrus
- please use the s3
apicloudloadbalancers-uk
- please use the rackspace-cloudloadbalancers-uk
apicloudloadbalancers-us
- please use the rackspace-cloudloadbalancers-us
apieucalyptus-partnercloud-ec2
- please use the ec2
apieucalyptus-partnercloud-s3
- please use the s3
apirimuhosting
- no longer supportedslicehost
- no longer supportedstratogen-vcloud-mycloud
- please use the vcloud
apisynaptic-storage
- please use the atmos
apitrystack-nova
- please use the openstack-nova
apiNovaApi
.RestContext
. This is replaced with ApiContext
, which doesn't have an async type. Note that you can use ContextBuilder.buildApi(YourApi.class)
instead of using contexts, as api interfaces are now closeable.Context.utils()
as many features there were only present to support the Async interfaces of jclouds. Code in jclouds will be easier to maintain when we needn't support utilities that are also present in tools such as guava and bouncycastle.jclouds will soon enter the Apache Incubator, please watch out for announcements as futher progress and releases of jclouds will occur from there.
Follow us on Twitter for updates.
To keep up with the latest on jclouds Version 1.6, please see issue 1564
jclouds would like to thank everyone who contributed time and effort in order to make the release of jclouds Version 1.6 happen. Check out who has been busy here.
Please see the test results for jclouds Version 1.6.