bringing clouds together : the future of cloud services

Remember this ?

Bringing the Clouds Together

THE FUTURE OF CLOUD SERVICES

Bringing the Clouds Together

VIVEK JUNEJA

COFOUNDER

CLOUD GUY USER GROUP BANGALORE

developer / evangelist / blogger

#bcb12

@vivekjuneja

What you gonna walk away with ?

+ challenges of integrating multiple cloud services

+ current solutions – tools, technologies, patterns

~ agenda ~

+ not that long ago+ the rise of the *.*+ the 6 commandments

~ agenda ~

+ not that long ago+ the rise of the *.*+ the 6 commandments

+ not that long ago

…’02...’04....’06...

+ not that long ago

...’06...’07....’08...

the problem withfew

+ the problem with few

Fear of lock-in

+ the problem with few

Lack of choice

+ the problem with few

One choice does not fit All

Lack of standards

+ the problem with few

Lack of maturity in cloud implementation

+ the problem with few

~ agenda ~

+ not that long ago+ the rise of the *.*+ the 6 commandments

+ the rise of *.*

as a Service

+ the rise of *.*

why do you need*.*

+ why do you need *.*

Outages and Downtime

+ why do you need *.*

Need to look beyond AWS as default

+ why do you need *.*

Cloud provider nearest to the consumer

+ why do you need *.*

Boost Fault tolerance and High Availability

+ why do you need *.*

Right Cloud for the right Job

+ why do you need *.*

Insulate against pricing changes

the problem with *.*

+ the problem with *.*

Redundant Data across multiple providers

+ the problem with *.*

Integration is point to point

+ the problem with *.*

Lack of standards in cloud interoperability

+ the problem with *.*

When to use what syndrome

+ the problem with *.*

How to insulate locking in with a provider

~ agenda ~

+ not that long ago+ the rise of the *.*+ the 6 commandments

Before we start.....

XYZ Systems

Local Data Center

App Front End

Caching

Business Objects

Database / FS Legacy 1 Legacy 2IAM / ADS

Periodic spikes in Usage

XYZ Systems

Internal infrastructure insufficient

XYZ Systems

Infrastructure for periodic spikes not feasible

XYZ Systems

Legacy infrastructure cannot be outsourced

XYZ Systems

Need to use local IAM

XYZ Systems

Integrate with external cloud services

XYZ Systems

+ commandment

Integrating Cloud

1

Providers

Integrating Cloud providers

+ commandment

Workload Import

2

& Export

VM Import / Export

+ commandment

Use of Platform

2

agnostic P A A S

Use of Platform agnostic PAAS

appscale

+ commandment 3Automate

Deployment and

Configuration

Automate Deployment and Configuration

+ commandment 4Standardize

Sizing

+ commandment 4

Small Instance (Default) 1.7 GB of memory1 EC2 Compute Unit (1 virtual core with 1 EC2 Compute Unit)160 GB of local instance storage32-bit or 64-bit platform

+ commandment 4

+ commandment 4Standardize

Sizing?

+ commandment 4

+ commandment 4

1 2 3 40

300

600

900

AMZ_SMALL

AMZ_SMALL

1 2 3 40

300

600

900

1200

RKSPC_SMALL

RKSPC_SMALL

* The X axis represents the Iterations for the test. The Y axis represents the UNIXBench Indices

+ commandment 5API unification

+ commandment 5

client = DeltaCloud.new( api_name, api_password, api_url )

# switch the client to use EC2 driverec2 = client.with_config(:driver => :ec2)

# switch the client to use OpenStack driveropenstack = client.with_config(:driver => :openstack)

+ commandment 5

// Amazon EC2java -jar target/compute-basics-jar-with-dependencies.jar aws-ec2 accesskey secretkey mygroup add

// HP Public Cloudjava -jar target/compute-basics-jar-with-dependencies.jar hpcloud-compute tenantId:accesskey secretkey mygroup add

+ commandment 6Think Global, Act Local

Think Global, Act Local

Think Global, Act Local

?questions