World Wide Cloud:The UltimateHybrid Cloud

Mirantis, 2014

About MirantisMirantis is the number one pure play OpenStack Company. We deliver all the technology, integration, training and support required for companies to succeed with production-grade open source cloud. More customers rely on Mirantis than any other company to scale out OpenStack without the compromises of vendor lock-in. Our bench of 400+ open source infrastructure experts helped make us one of top 5 contributors to OpenStack’s upstream codebase.

Introduction

About Nicholas ChaseNick Chase has 20+ years of experience as a developer and author. He has written several books and hundreds of articles as an IBM developerworks Certified Master Author, founded NoTooMi.com and has done web application development for companies such as Alcatel-Lucent, Sun Microsystems, Oracle, and the Tampa Bay Buccaneers. He is currently Mirantis' Technology Marketing Manager, and the Editor of OpenStack:Now.

Agenda

● What is Hybrid Cloud?● Levels of Hybridization● OpenStack as the New Web, or Why Hybrid Cloud

is Important● Creating the World Wide Cloud● Technical Hurdles● What the Community Needs to Do● Where We Go From Here

Agenda

What Is Hybrid Cloud?

Hybrid Cloud is...

● Multiple clouds...● Different systems...● Different platforms...● Different locations...● Talking to each other

What Is Hybrid Cloud?

We usually hear about Hybrid Cloud for...

● Dev/Test● Scaling up/cloudbursting● Better resource allocation

But what other use cases have we not even thought of yet?

Use cases

The Stages of Hybrid Cloud

● Isolated● Homogeneous● Heterogeneous ● World Wide Cloud (Cloud of Everything)

The Stages of Hybrid Cloud

● Isolated clouds: Any clouds are handled individually; jobs are assigned to clouds manually.

The Stages of Hybrid Cloud

● Isolated clouds: Any clouds are handled individually; jobs are assigned to clouds manually.

● Homogeneous clouds: All clouds are the same type; client software assigns jobs automatically.

The Stages of Hybrid Cloud

● Isolated clouds: Any clouds are handled individually; jobs are assigned to clouds manually.

● Homogeneous clouds: All clouds are the same type; client software assigns jobs automatically.

● Heterogeneous clouds: Multiple components and system types, with jobs managed by a single client.

The Stages of Hybrid Cloud

● Isolated clouds: Any clouds are handled individually; jobs are assigned to clouds manually.

● Homogeneous clouds: All clouds are the same type; client software assigns jobs automatically.

● Heterogeneous clouds: Multiple components and system types, with jobs managed by a single client.

● World Wide Cloud (Cloud of Everything): Heterogeneous clouds with a single (OpenStack) management grid, joinable by anyone.

The Stages of Hybrid Cloud

OpenStack as the New Web, or Why

Hybrid Cloud is Important

Why Hybrid Cloud is Important

Current use cases:● Dev/Test● Cloudbursting● Resource management

These are mostly corporate use cases. What about individuals?

Future use cases have yet to emerge.

Why Hybrid Cloud is Important

We ask

"Is OpenStack the new Linux?"

What if we're wrong? What if the question is

"Is OpenStack the new Web?"

OpenStack as the new Web

The Web gave us:● Democratization of content production/use● New ways to communicate● New use cases never dreamed of by its

founders● Based on open "standards" -- anybody could

do it

OpenStack as the new Web

OpenStack can give us us:● Democratization of resource production/use● New ways to process data● New use cases never dreamed of by its

founders● Based on open "standards" -- anybody could

do it

Creating the World Wide Cloud

Creating the World Wide Cloud

Step 1:

1. One cloud, private or public, controlled by API (not AWS)2. Choosing where to put your resources manually3. Resources on the same network4. Resources have to hit Keystone5. Resources need to access MySQL

Creating the world Wide Cloud

Step 2:

1. Multiple clouds -- by availability zone?2. MySQL replaced by distributed hashtable-ish method3. Clouds can be connected or not4. Multiple contributors5. Each cloud has its own resource policies

Creating the world Wide Cloud

Step 3:

1. Clouds have additional services such as Sahara, or Murano Application Catalog.

2. Each cloud can have its own policies, and its own catalog.3. A single cloud can allow apps from multiple catalogs.

Technical Challenges

Technical Hurdles

Networking● Do all resources need to be on the same

network?● Can we use a virtual mesh with something

like OpenVPN?● Do new SDN's/NFV's come into play

(Neutron)?

Technical Hurdles

Trust● Users need to know the level of trust for each

resource● Resource owners need to know what's on

their systems -- or do they?● Nova flavors, Cinder volume types● Additional metadata (Graffiti)?

Technical Hurdles

Billing● Users need to be able to pay for what they use

(Ceilometer)● Contributors need to be able to get paid for

what they contribute● Cryptocurrencies

Technical Hurdles

Coordination among services● Does the underlying machinery matter?● Jumpgate, Cisco● Apache vs Nginx -- who cares?

Technical Hurdles

Traceability● Users might want to maintain anonymity● Anonymous DMCA request repositories● Harder to go after thousands of individuals● Harder for individuals to fight

spying/subpoenas

What the Community Needs

To Do

What the Community Needs To do

Basic security issues around strangers joining your cloud:

● Multiple levels?● One-way credentials?● Federated identity?

What the Community Needs To do

Better cloud-to-cloud communication

● Ability to move workloads between clusters● Resource sharing from multiple clusters

What the Community Needs To do

And also ...

● Standardize the OpenStack API● Develop relationships with projects such as

Jumpgate, which use OpenStack APIs to manipulate other systems

Where We Go From Here