| commit | 8b5091bea66e1f24338a1674ac22348f741db8fa | [log] [tgz] |
|---|---|---|
| author | Adrian Cole <adrian@jclouds.org> | Sun Sep 09 11:59:23 2012 -0700 |
| committer | Adrian Cole <adrian@jclouds.org> | Sun Sep 09 11:59:23 2012 -0700 |
| tree | 8f91577973757bb2436f96481e9fc9983f1b7223 | |
| parent | fef7bab24ea4cef65445aca8410d1ba59ce1a2e4 [diff] | |
| parent | b0a12bf3030616ce460baea34d7bf45724d569c7 [diff] |
Merge branch 'master' of https://github.com/jclouds/jclouds into 1.5.x * 'master' of https://github.com/jclouds/jclouds: (25 commits) Moved HP Storage Container Metadata parsing to Swift since it's a standard Swift feature. Moved HP Storage createContainer(String, CreateContainerOptions) to CommonSwiftClient since it's a standard Swift feature. Added support for setting Swift Container Metadata. Added support for deleting Swift Container Metadata. Added copy object feature to Swift. Removed unnecessary TODO comment. Changed DeleteContainerMetadataOptions to just be a List. Changed CopyObjectOptions to be just be a String. Changed CommonSwiftClient.setContainerMetadata() to use just a Map for metadata. Added ExpectTests. Changed setContainerMetadata() to use Iterable instead of List for more generic type goodness. Changed copyObject() to use 4 String params instead of 2 String params to be similar to other such methods in jclouds. issue 830: added systemadmin package; more tests fixed CDMI: adding support for 1) query parameters 2) non-cdmi content data object operations Javadoc update for CloudStack Template.getStatus() CloudStack template status parsing update merge azure management base implementation Update parsing of Status in CloudStack Template default region endpoint for rackspace legacy apis issue 830: fixed VAppTemplateApiLiveTest.deleteVAppTemplate Issue 1075:switch to use jetty for java install/web service tests nslookup on CentOS 6.2 doesn't set error code when failing, so grep expected output instead review addressed issue 830: keypair Added test descriptions and dependencies to basic Nova live tests Configure duplicates plugin to ignore .gitattributes decrufted metadataapi configure .gitattributes to not convert shell scripts to CRLF on Windows Correct typo issue 830: more LiveTests fixed on query, vapp, vapptemplate and vdc features ...
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
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