24
1 Cloud, 2 Clouds, 3 Clouds, Tons... DevOps Days 2017

1 cloud, 2 clouds, 3 clouds, tons

Embed Size (px)

Citation preview

Page 1: 1 cloud, 2 clouds, 3 clouds, tons

1 Cloud, 2 Clouds, 3 Clouds, Tons...

DevOps Days 2017

Page 2: 1 cloud, 2 clouds, 3 clouds, tons

Defining Multi-Cloud

Cloud BurstingMulti-Cloud

APPLICATION

CLOUD A CLOUD BON-PREMISE

CLOUD PUBLIC CLOUD

100%CAPACITY

STANDARDWORKLOAD

PEAKWORKLOAD

Future Proofing & Migration

PRODUCTION CLOUD

FUTURE CLOUD

Application Portability

CLOUD A CLOUD B

Page 3: 1 cloud, 2 clouds, 3 clouds, tons

The Multi-Cloud Reality - Not Just AWS

Page 4: 1 cloud, 2 clouds, 3 clouds, tons

Continues to introduce new players

Focus on bare-metal cloud

Dominant in Asia

Salesforce - niche cloud

Page 5: 1 cloud, 2 clouds, 3 clouds, tons

Private vs. Public Cloud Isn’t What it Used to Be..

Azure Stack Amazon VPC

Page 6: 1 cloud, 2 clouds, 3 clouds, tons

Private Cloud Moves to Public Cloud

Page 7: 1 cloud, 2 clouds, 3 clouds, tons

Cloud is Getting Closer to the Edge

Page 8: 1 cloud, 2 clouds, 3 clouds, tons

What’s Changed?

Innovation VSAdoption

Page 9: 1 cloud, 2 clouds, 3 clouds, tons

The Challenge

Operational Chaos:● Who’s running what?

Where?● How much does it cost?● Who is running ON what?

Automation, cost, and performance optimization are bound to a specific platform

Page 10: 1 cloud, 2 clouds, 3 clouds, tons

Approaches to Multi-Cloud Management

Cloud Management Platform Application Platform (PaaS) Automation / Orchestration Platform (PaaS)

Page 11: 1 cloud, 2 clouds, 3 clouds, tons

Cloud Management Platform - Infrastructure firstPros:

● Single Pane of Glass● Cost analysis and control

Cons

● Limited application awareness

● Doesn’t fit well with devops processes

● Limited cloud services (Least

Common Denominator)

Page 12: 1 cloud, 2 clouds, 3 clouds, tons

PaaS - Application First ApproachPros:

● Kubernetes and containers are supported by all major clouds

● Application / Micro Services centric

Cons

● Suits mostly for Green Field● Lack of interoperability with

the rest of the world..

Page 13: 1 cloud, 2 clouds, 3 clouds, tons

Multi-Cloud Orchestration - Automation First Pros:

● Works across a wide variety of public / private clouds

● Can support any cloud service or application

● Highly customizable

Cons

● Requires customization per application / cloud

Page 14: 1 cloud, 2 clouds, 3 clouds, tons

Too Many Options?

14

Your apps sucks, rewrite!

No More VMware!

Docker is awesome dude!

Private Cloud is Dead!

We’ll Solve all Your

problems..

Page 15: 1 cloud, 2 clouds, 3 clouds, tons

Take the Pragmatic Approach to Multi-Cloud

● The only constant is change!● There ain’t a single solution

that fits all● Keep your options open - Avoid

locking into a single platform

Page 16: 1 cloud, 2 clouds, 3 clouds, tons

Take the Pragmatic Approach to Multi-Cloud ● Let’s be more specific ..

○ Use Containers where possible ○ Kubernetes simplify the multi cloud challenge

(Supported by all major clouds) ○ Use Automation Framework to allow

integration and interoperability between the various clouds and platform

○ Use a declarative approach to abstract the demand (application), from the supply (infrastructure resources)

Page 17: 1 cloud, 2 clouds, 3 clouds, tons

Example: A Pragmatic Approach to Multi-Cloud

ONAP Operation Manager (OOM)

● New linux Foundation Project● Comprised out of Dozen

Micro Services using Docker/Kubernetes

● Multi-Stack/ Multi Cloud

Page 18: 1 cloud, 2 clouds, 3 clouds, tons

Example: A Pragmatic Approach to Multi-CloudManage Kubernetes Infrastructure On Multi Cloud

● Create VM/Baremetal machine

● Configure the network/Storage, Security, Monitoring ..

● Seamless integration (Using the Kubernetes Provider plugin)

● Auto-Scale, Heal workflow (or manual)

Kubernetes Nodes

Kubernetes Master

Network Setup

Kubernetes Multi Cloud Cluster Blueprint

Page 19: 1 cloud, 2 clouds, 3 clouds, tons

Example: A Pragmatic Approach to Multi CloudManage ONAP Microservices on Kubernetes

● Templatize the standard Kubernetes template (in-line or by reference) ..

● Dependency and discovery between services.

● Allow execution of workflow

Deployment

Blueprint

Plugin

Page 20: 1 cloud, 2 clouds, 3 clouds, tons

Example: A Pragmatic Approach to Multi CloudSupport Hybrid Stack..

● Support a combination of Kubernetes services alongside standard VM’s , BigData applications, Lamda Services, Legacy Application under the same automation/orchestration template

Deployment

Blueprint

Plugin

Page 21: 1 cloud, 2 clouds, 3 clouds, tons

Example: A Pragmatic Approach to Multi-CloudMulti Site / Environment..

● Managing Multiple Kubernetes clusters

○ Cross site deployment○ Dev, QA, Production ○ Multi-Cloud

Private

Public

Bare-metal

Page 22: 1 cloud, 2 clouds, 3 clouds, tons

Live Demo..

● Define a new service into a deployment template

● Deploy the service into an existing Kubernetes cluster.

Page 23: 1 cloud, 2 clouds, 3 clouds, tons

Summary● Hybrid cloud is a reality you can’t avoid● Kubernetes provides a good abstraction

for managing application on multi-cloud● Standard modeling such as TOSCA

makes the interoperability of Kubernetes with the outside world possible

Page 24: 1 cloud, 2 clouds, 3 clouds, tons

Thank You