The Java Multi-Cloud Toolkit
Go to file
Andrew Gaul 5330699fe7 Improve XML compatibility with trace-level logging
Some providers, notably Azure, include a byte-order mark in their XML
responses.  ParseSax.apply buffers these responses in a String when
users enable trace-level logging to include the response in any thrown
exceptions.  InputSource(InputStream) skips these byte-order marks
while InputSource(Reader) does not, yielding a SAXParseException.
2014-09-05 17:56:11 -07:00
all [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
allblobstore [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
allcompute [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
allloadbalancer [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
apis Set Content-MD5 only if ETag has correct format 2014-08-28 21:51:51 -07:00
blobstore Throw ContainerNotFoundException from removeBlob 2014-08-28 18:26:59 -07:00
common JCLOUDS-656: Parse Swift authentication headers case-insensitively 2014-08-08 20:34:03 -04:00
compute JCLOUDS-661: Adding a test for single-port firewall rules 2014-08-14 14:43:41 -06:00
core Improve XML compatibility with trace-level logging 2014-09-05 17:56:11 -07:00
drivers [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
loadbalancer [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
project [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
providers fix ASF copyright headers on SoftLayer 2014-08-18 19:04:49 -06:00
resources Backport https://github.com/jclouds/jclouds/pull/472 2014-08-18 19:13:27 -06:00
scriptbuilder [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
skeletons [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00
.dir-locals.el JCLOUDS-26. Adding .dir-locals.el for Emacs tab-width setting 2013-05-10 14:52:52 -07:00
.gitignore added support for vbox 4.2.6; 2012-12-31 01:33:43 +01:00
.mailmap .mailmap updates 2013-10-08 22:14:07 -07:00
CONTRIBUTING.md Added the CONTRIBUTING file 2014-07-02 16:48:14 +02:00
README.md Updated links to the user and dev mailing lists 2014-04-14 14:41:52 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2014-07-29 16:50:39 -04:00

README.md

jclouds

jclouds allows provisioning and control of cloud resources, including blobstore and compute, from Java and Clojure. Our API 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 Get started without dealing with REST-like APIs or WebServices. Instead of creating new object types, jclouds reuses concepts like maps so that the programming model is familiar.

  • RUNTIME PORTABILITY jclouds drivers enable you to operate in restricted environments like Google App Engine. There are very few required dependencies, so jclouds is unlikely to clash with your app.

  • DEAL WITH WEB COMPLEXITY jclouds handles issues such as transient failures and redirects that traditional network based computing introduces.

  • UNIT TESTABILITY Write your unit tests without mocking complexity or the brittleness of remote connections. Writing tests for cloud endpoints is difficult. jclouds provides you with Stub connections that simulate a cloud without creating network connections.

  • PERFORMANCE Customize configuration to match your performance needs. jclouds provides you with asynchronous commands, tunable http, date, and encryption modules.

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

  • QUALITY Every provider is tested with live scenarios before each release. If the provider doesn't pass, it goes back 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 ^:dynamic *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-2013 The Apache Software Foundation

Licensed under the Apache License, Version 2.0