The Java Multi-Cloud Toolkit
Go to file
Matt Stephenson f1b5faf007 Fail the build on duplicate resources or classes on the classpath 2012-04-25 19:47:58 -07:00
all updated current version to 1.5.0-SNAPSHOT 2012-02-04 11:06:07 -08:00
allblobstore Issue 879:keystone v2 hpcloud-objectstorage provider 2012-03-22 21:45:25 -07:00
allcompute added openstack-nova-ec2 to allcompute 2012-04-03 10:49:49 -07:00
allloadbalancer missing cloudloadbalancer instance 2012-02-27 09:47:01 +02:00
antcontrib wrapper -> view 2012-04-23 19:14:36 -07:00
apis Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
archetypes refactor PropertiesBuilder and related types into ApiMetadata and ProviderMetadata, and update all usage 2012-04-11 19:47:09 -06:00
assemblies updated current version to 1.5.0-SNAPSHOT 2012-02-04 11:06:07 -08:00
blobstore switched to buildView 2012-04-24 12:26:37 -07:00
common Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
compute Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
core Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
demos Using the public rather than the internal address to trigger tweet storage in Cloud Foundry TweetStore while we figure out if it's possible to use the internal address (see http://support.cloudfoundry.com/requests/102117) 2012-04-13 17:05:48 -04:00
drivers Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
labs Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
loadbalancer Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
project Fail the build on duplicate resources or classes on the classpath 2012-04-25 19:47:58 -07:00
providers Remove IPSocket class, replace with Guava's HostAndPort class. 2012-04-25 17:52:01 -07:00
resources Issue 847:version updates 2012-02-23 15:11:05 +02:00
sandbox-apis implemented image extension 2012-04-18 09:37:44 +01:00
sandbox-drivers/asynchttpclient [842] Added required import packages to cloudfiles api bundle. Improved import packages in all bundles. 2012-02-17 00:49:39 +02:00
sandbox-providers removed ContextBuilder subclasses; added unwrap; undid generic params 2012-04-16 00:44:20 -07:00
scriptbuilder created base Context class with ProviderMetadata and Identity 2012-04-23 16:16:51 -07:00
skeletons wrapper -> view 2012-04-23 19:14:36 -07:00
.gitignore issue 384: network support refactored 2012-03-01 17:29:18 +00:00
README.md README.md - improved 2012-03-28 21:59:16 +01:00
README.txt Issue 895:add openstack-nova-ec2 api 2012-04-03 00:06:00 -07:00
pom.xml Using the Javadoc plugin's 'aggregate-jar' goal instead of 'aggregate' for the jclouds-multi Javadoc build, so the Javadocs are actually attached and deployed 2012-04-23 12:00:25 -04:00

README.md

jclouds

jclouds is an open source library that helps you get started in the cloud and reuse your java and clojure development skills. Our api allows you freedom to use portable abstractions or cloud-specific features. We test support of 30 cloud providers and cloud software stacks, including Amazon, GoGrid, Ninefold, vCloud, OpenStack, and Azure. We offer several API abstractions as java and clojure libraries. The following are the most mature:

Features

Even if you don't need the portable apis we provide, or could roll it your own, programming against cloud environments can be challenging. We focus on the following areas so that you can focus on using the cloud, rather than troubleshooting it!

  • SIMPLE INTERFACE Instead of creating new object types, we reuse concepts like maps so that the programming model is familiar. In this way, you can get started without dealing with REST-like apis or WS.

  • RUNTIME PORTABILITY We have drivers that allow you to operate in restricted environments like Google App Engine. We have very few required dependencies, so we are unlikely to clash with your app.

  • DEAL WITH WEB COMPLEXITY Network based computing introduces issues such as transient failures and redirects. We handle this for you.

  • UNIT TESTABILITY Writing tests for cloud endpoints is difficult. We provide you with Stub connections that simulate a cloud without creating network connections. In this way, you can write your unit tests without mocking complexity or the brittleness of remote connections.

  • PERFORMANCE Writing tests for cloud endpoints is difficult. We provide you with Stub connections that simulate a cloud without creating network connections. In this way, you can write your unit tests without mocking complexity or the brittleness of remote connections.

  • LOCATION All of our abstractions are location-aware. For example, you can get ISO-3166 codes to tell which country or province a cloud runs in.

  • QUALITY We test every provider with live scenarios before each release. If it doesn't pass, the provider goes into the sandbox.

BlobStore

Simplifies dealing with key-value providers such as Amazon S3. For example, BlobStore can give you a simple Map view of a container.

BlobStore Example (Java):

// init
context = new BlobStoreContextFactory().createContext(
"aws-s3",
accesskeyid,
secretaccesskey);
blobStore = context.getBlobStore();

// create container
blobStore.createContainerInLocation(null, "mycontainer");

// add blob
blob = blobStore.blobBuilder("test").payload("testdata").build();
blobStore.putBlob("mycontainer", blob);

BlobStore Example (Clojure):

(use 'org.jclouds.blobstore2)
(def *blobstore* (blobstore "azureblob" account encodedkey))
(create-container *blobstore* "mycontainer")
(put-blob *blobstore* "mycontainer" (blob "test" :payload "testdata"))

ComputeService

Simplifies the task of managing machines in the cloud. For example, you can use ComputeService to start 5 machines and install your software on them.

Compute Example (Java):

// init
context = new ComputeServiceContextFactory().createContext(
"aws-ec2",
accesskeyid,
secretaccesskey,
ImmutableSet.of(new Log4JLoggingModule(), new SshjSshClientModule()));

client = context.getComputeService();

// define the requirements of your node
template = client.templateBuilder().osFamily(UBUNTU).smallest().build();

// setup a boot user which is the same as your login
template.getOptions().runScript(AdminAccess.standard());

// these nodes will be accessible via ssh when the call returns
nodes = client.createNodesInGroup("mycluster", 2, template);

// you can now run ad-hoc commands on the nodes based on predicates
responses = client.runScriptOnNodesMatching(inGroup("mycluster"), "uptime", wrapInInitScript(false));

Compute Example (Clojure):

(use 'org.jclouds.compute2)

; create a compute service using sshj and log4j extensions
(def compute (*compute* "trmk`-ecloud" "user" "password" :sshj :log4j))

; launch a couple nodes with the default operating system, installing your user.
(create-nodes *compute* "mycluster" 2
(TemplateOptions$Builder/runScript (AdminAccess/standard)))

; run a command on that group 
(run-script-on-nodes-matching *compute* (in-group? "mycluster") "uptime" 
(RunScriptOptions$Builder/wrapInInitScript false))

Check out https://github.com/jclouds/jclouds-examples for more examples!

Downloads

Resources

License

Copyright (C) 2009-2012 jclouds, Inc.

Licensed under the Apache License, Version 2.0