One of the big hurdles for an enterprise to move to the cloud is the fear of getting locked into a specific cloud implementation. This is one of the big reasons apart from security of data that keeps most of the enterprises out of the cloud space. Currently each vendor provides their unique set of API to interact with their Cloud services. This mandates a need to recode and refactor when moving from one cloud provider to the other. jClouds is a multi cloud framework which allows connection to multiple clouds such as Amazon, VMWare, Azure, and Rackspace. jClouds provides portable abstractions for cloud specific features, thus allowing the application to move from one cloud vendor to the other with relative ease. jClouds also had a simulators to operate in restricted environments like Google App Engine and Android. Unit testing and mocking is made easy through stub connections which simulate the cloud.

1. Getting Started With jClouds
Vikas Hazrati
Inphina Technologies
1

2. cloud is real !
2

3. enterprises like to be on cloud
3

4. reluctance due to lock-In
4

5. abstraction
5

6. changing the ecosystem
6

7. multi cloud frameworks
Fog
Dasein Cloud
Delta Cloud LibCloud
7

8. key value storage
global name space
key, value with metadata
http accessible Not the same!
sites on demand
unlimited scaling
8

9. other factors
File Size
Resumability
CDN
Replication
SLA Not the same!
Consistency Model
Authorization
API Complexity
9

10. http request
10

11. do you want to deal with this?
Errors
Concurrency
Cloud Complexity
11

12. 12

13. what is jClouds
OSS JAVA Framework for cloud enablement and inter cloud
communication
3/2009, 1.0-beta6, 105.4k lines, $1.4M
Support many clouds including Amazon, VMWare, Azure,
and Rackspace.
13

14. easy to start
Runtime portability
Simple interface
Open Source
Unit Testability
Deals with
Web Complexity
Performance
Feels like java
and clojure
14

15. simple interface
Basic
Advanced
15

16. simple interface
Expert
16

17. choose your complexity and weight
17

18. abstractions
Blobstore Compute
BlobStore ( atmos, azure, rackspace, s3 )
Compute ( vcloud, ec2, gogrid, ibmdev,rackspace,rimu)
18

19. blobstore
// init
context = new BlobStoreContextFactory().createContext(
"s3",accesskeyid,secretaccesskey);
blobStore = context.getBlobStore();
// create container
blobStore.createContainerInLocation(null, "mycontainer");
// add blob
blob = blobStore.newBlob("test");
blob.setPayload("testdata");
blobStore.putBlob(containerName, blob);
19

20. blobstore in detail
Managing key-value storage providers
Synchronous and Asynchronous APIs
Service
Blobstore
Container
Blob
20

21. <Blobstore Code Sample>
21

22. vfs support
22

23. compute: provisioning
provisioning (and re-provisioning) is cheap
APIs = automation
tools exist
forgetting to turn things off
licensing
erratic service quality
cloud apis are sometimes unreliable
apis are very different across clouds
features are very different across
clouds
accidental complexity
23

24. provisioning with jClouds
24

25. 95 + 5
25

26. projects using jClouds
I N F I N I S PAN
Android Integration
Gigaspaces
Elastic Search
26

27. alternatives
Roll-your-own
Jersey, RESTEasy
EC2-based cloud apis
typica, jets3t
Dasein Cloud API
Service provided SDKs
27

28. scepticism
api's are not that different to write a driver
open source cloud Ruby libraries (RightAws,
RightRackspace, RightGoGrid, etc.) not actually
that much work to abstract the API details away.
real benefit of standards - semantics of
resources like vlans, security groups,
reassignable IP addresses, network attached
block storage devices, etc
28

29. reluctance to lock-in? no
more ...
29

30. References:-
http://code.google.com/p/jclouds/
http://anyweight.blogspot.com/
http://www.slideshare.net/marakana/jclouds-at-san-francisco-java-user-group
http://www.youtube.com/watch?v=queixYPsIq0
30

31. vhazrati@inphina.com
http://www.inphina.com
http://thoughts.inphina.com
31