The Java Multi-Cloud Toolkit
Go to file
Andrew Gaul 3c7b9652f4 Work around failed CDN metadata lookups with HPCS
Previously BlobStore.list and thus BlobStore.clearContainer serialized
on synchronous and failed CDN lookups.  This effectively prevents
clearing any large container.  We cache a negative entry to work
around this.  When HP improves their CDN support we should remove this
workaround.
2012-10-29 15:31:03 -07:00
all bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
allblobstore bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
allcompute Added rackspace-cloudservers-uk to allcompute. 2012-10-25 09:51:10 -05:00
allloadbalancer bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
apis Merge pull request #907 from pandriani/master 2012-10-24 20:08:03 -07:00
archetypes bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
assemblies bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
blobstore Prefer immutable over empty collections 2012-10-20 15:35:29 -07:00
common Always add trailing brace to AWSError.tostring 2012-09-25 15:59:20 -07:00
compute Issue 1103: isolate polling of nodes into its own class 2012-10-20 11:05:18 -07:00
core Prefer immutable over empty collections 2012-10-20 15:35:29 -07:00
demos Issue 1113:Move perftest to new jclouds-perftest-s3 repository 2012-10-21 16:14:51 -07:00
drivers Prefer immutable over empty collections 2012-10-20 15:35:29 -07:00
labs Prefer Files.copy to copy streams 2012-10-24 17:44:05 -07:00
loadbalancer bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
project bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
providers Work around failed CDN metadata lookups with HPCS 2012-10-29 15:31:03 -07:00
resources updated remote-resources plugin version 2012-10-21 16:41:23 -07:00
sandbox-apis Prefer immutable over empty collections 2012-10-20 15:35:29 -07:00
sandbox-drivers/asynchttpclient bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -07:00
sandbox-providers Prefer immutable over empty collections 2012-10-20 15:35:29 -07:00
scriptbuilder Prefer immutable over empty collections 2012-10-20 15:35:29 -07:00
skeletons bumped to 1.6.0-SNAPSHOT 2012-09-17 01:43:52 -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 bumped to 1.5 2012-09-28 10:05:41 -07:00
pom.xml Issue 1112:Move antcontrib to new jclouds-ant repository 2012-10-21 15:07:18 -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 dozens of 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