The Java Multi-Cloud Toolkit
Go to file
Andrei Savu a3d421442a Issue 973. Performance problems with Synaptic's Atmos service and writing new blobs 2012-10-09 02:14:55 +03:00
all [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
allblobstore [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
allcompute [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
allloadbalancer [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
antcontrib [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
apis Issue 973. Performance problems with Synaptic's Atmos service and writing new blobs 2012-10-09 02:14:55 +03:00
archetypes [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
assemblies [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
blobstore [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
common [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
compute Made the polling period between updates for servers and images configurable when using the ComputeService. 2012-10-05 11:38:32 -07:00
core Made the polling period between updates for servers and images configurable when using the ComputeService. 2012-10-05 11:38:32 -07:00
demos Spelling corrections 2012-07-26 22:39:35 -07:00
drivers [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
labs [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
loadbalancer [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
project [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
providers Issue 973. Performance problems with Synaptic's Atmos service and writing new blobs 2012-10-09 02:14:55 +03:00
resources [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
sandbox-apis pulled SQS out of sandbox and into labs 2012-09-10 18:02:07 -07:00
sandbox-drivers/asynchttpclient Removed fragments and dynamic imports. Added centralized control of the maven-bundle-plugin. 2012-06-03 19:41:54 +03:00
sandbox-providers Spelling corrections 2012-07-26 22:39:35 -07:00
scriptbuilder [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
skeletons [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00
.gitignore Add support to apis/cloudwatch for listing stored metrics. 2012-04-26 19:14:30 -06:00
.mailmap Add .mailmap to clean up git shortlog 2012-08-20 11:00:44 -07:00
README.md Improve README blurb 2012-07-18 14:50:05 -07:00
pom.xml [maven-release-plugin] prepare for next development iteration 2012-09-27 11:00:25 -07:00

README.md

jclouds

jclouds allows provisioning and control of cloud resources, including blobstore and compute, from Java and Clojure. Our API gives allows developers to use both portable abstractions and cloud-specific features. We test support of 30 cloud providers and cloud software stacks, including Amazon, Azure, GoGrid, Ninefold, OpenStack, and vCloud. jclouds is licensed under the Apache License, Version 2.0

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