Planning  Your  Cloud  Strategy  

S.Uthaiyashankar  VP  Engineering,  WSO2  shankar@wso2.com  

Why  We  Need  Cloud  Strategy?    

Picture  Credit  :  h=p://dilbert.com/strip/2009-­‐11-­‐18  

Cloud  Strategy  

•  Using  Cloud  Services  •  FederaLon  of  Cloud  IdenLLes  •  Development  in  Cloud  •  Running  Your  ApplicaLon  in  Cloud  

Cloud  Services  

•  Tons  of  Useful  Services  •  Standing  on  the  Shoulders  of  Giants  •  You/Your  Customers  might  already  

using  some  of  these  services  

Cloud  Iden::es  

•  Increased  numbers  of  Social  IdenLLes  

•  Gartner  predicts,  by  the  end  of  2015,  50%  of  all  new  retail  customer  idenLLes  will  be  based  on  social  network  idenLLes  

•  Your  users/employees  already  have  one  or  more  social  idenLLes  

Applica:on  Development  

•  Agile  •  API  Driven  •  Polyglot  (language,  technology,  data)  •  Requires  Quick  Releases  •  Supports  Long  Tail  of  Apps  

Applica:on  Run:me  

•  Microservices  Architecture  •  Unpredictable  Load  •  Varied  scalability  between  components  

Relationship with IT

8  

2 days to create a

user

½ day to reset a

password

3 days to create a database

1 week to provision

a VMruntime policies

devops policies

Picture  Credit  :  h=p://web.zizinya.com/blog/  

This  oAen  leads  to  Shadow  IT…  

What  You  Need?    

•  Self  Service  •  Heterogeneous  RunLmes  •  Polyglot  Programming  Model  •  Workflow  Driven  •  API  Driven  •  Accept  CreaLve  ExperimentaLon  •  Low  Cost  Development,  RunLme  Environments  

Rise of the Containers

Enterprise Docker, Adrien BLIND, Aurelien GABET, Arnaud MAZIN

And  the  Fancy  Cousins…  

nodes. They also make sure that the correct numbers of thesethings are running at all times.

A node usually runs three important processes:

1. Kubelet—A special background process (daemon that runs oneach node whose job is to respond to commands from the mas‐ter to create, destroy, and monitor the containers on that host.

2. Proxy—This is a simple network proxy that’s used to separatethe IP address of a target container from the name of the serviceit provides. (I’ll cover this in depth a little later.)

3. cAdvisor (optional)—http://bit.ly/1izYGLi[Container Advisor(cAdvisor)] is a special daemon that collects, aggregates, pro‐cesses, and exports information about running containers. Thisinformation includes information about resource isolation, his‐torical usage, and key network statistics.

These various parts can be distributed across different machines forscale or all run on the same host for simplicity. The key differencebetween a master and a node comes down to who’s running whichset of processes.

Figure 2-2. The Expanded Kubernetes Layout

If you’ve read ahead in the Kubernetes documentation, you might betempted to point out that I glossed over some bits—particularly onthe master. You’re right, I did. That was on purpose. Right now, theimportant thing is to get you up to speed on the basics. I’ll fill insome of the finer details a little later.

The Master and Its Minions | 9

Picture  Credit  :  Kubernetes  :  Scheduling  the  Future  at  Cloud  Scale  

And  the  Madness  Con:nues…  

Urbernetes Control Plane

Kubernetes Cluster 1

GCE

Kubernetes Cluster 2

AWs

Kubernetes Cluster n

Private

Standard Kubernetes API

Urbernetes API Policy Engine

Auth

Desired Federation

State

MigraLon  Controllers  

https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/federation.md

How  WSO2  Helps?  

WSO2  API  Manager  

•  Controlling  which  cloud  APIs  can  be  used  by  the  applicaLons  

•  IdenLfying  which  applicaLons  are  using  what  APIs  and  how  much  they  are  using  

WSO2  ESB  and  Connectors  

•  IntegraLon  with  cloud  services  •  Cloud  to  Cloud  and  Cloud  to  Enterprise  

IntegraLons  •  ESB  Connector  Store  :  hKps://store.wso2.com  

WSO2  Integra:on  Cloud  

•  Managers  and  executes  integraLon  templates  

WSO2  Iden:ty  Server  •  SSO  and  IdenLty  FederaLon  

WSO2  Iden:ty  Server  •  IdenLty  Provisioning  

Running  WSO2  Products  on  Kubernetes  

Pod 1 Pod 2

Manager Cluster Service

Pod 3 Pod 4 Pod n

Worker Cluster Services

Manager Replication Controller

Worker Replication Controller

Client

Gov Reg

Conf Reg

User Store

WSO2  Private  PaaS  

IaaS Provider 1

Kubernetes Cluster 1

Load Balancer

1

Load Balancer

2

Load Balancer

n

Central Load Balancer

N1 N2 N3 Nn M

Kubernetes Cluster 2

N1 N2 N3 Nn M

Kubernetes Cluster n

N1 N2 N3 Nn M

IaaS Provider n

Client

WSO2  App  Factory  

WSO2  Cloud  (hKp://wso2.com/cloud)  

Thank  You