| commit | c5f6633c529a01a0549e38dd1e43737de225e1c7 | [log] [tgz] |
|---|---|---|
| author | Adrian Cole <adrian@jclouds.org> | Tue May 01 10:18:16 2012 -0700 |
| committer | Adrian Cole <adrian@jclouds.org> | Tue May 01 10:18:16 2012 -0700 |
| tree | 6fb6352c39a81b21d918987794b9772f332d1be1 | |
| parent | be7a30593a332a3b0c88879d71d51bd3ab2c2be4 [diff] | |
| parent | 2d8f5ec807747e0cdaf95ef7431cbbdda575bbef [diff] |
Merge branch 'master' of github.com:jclouds/jclouds into 1.5.x * 'master' of github.com:jclouds/jclouds: (62 commits) modernized cloudwatch always display some error content added tests Follow up to f06d273 that addresses pull request comments. Follow up to e58d91e that addresses pull request comments. Upgrade to Guava 12.0 Do not set member until we completely validate it Prefer unsynchronized StringBuilder Adding links to openstack-keystone admin API documentation Adding openstack-keystone to labs pom Fixing javadocs Renaming the service client (user operations) ServiceClient to better match up to Keystone documentation Fixing javadocs Renaming the service client (user operations) ServiceClient to better match up to Keystone documentation Renaming 'ServiceClient's AuthenticationClients to save confusion with user-accessible ServiceClient in keystone 2.0 Adding unit tests for keystone 2.0 AdminURL supplier Adding openstack-keystone to expose additional methods available on keystone api Adding AdminURL supplier for keystone 2.0 Optimize clearContainer for large folders Extended support to apis/cloudwatch for getting metrics. ...
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:
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.
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"))
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!
Copyright (C) 2009-2012 jclouds, Inc.
Licensed under the Apache License, Version 2.0