Japan CloudStack Day (Mar 6 2014)

Sheng Liang

CTO, Cloud Platforms Group

A brief history

• Sept 2008 – Development started

• May 2010 – Released under GPL v3

• July 2011 – Acquired by Citrix

• April 2012 – Contributed to Apache Software Foundation

• November 2012 – First release (4.0.0-incubating) under ASF

• March 2013 – Apache CloudStack became a top level project

• Jan 2014 – 4.2.1 released

• Mar 2014 – 4.3 released!

Source: https://www.ohloh.net/orgs/apache/projects

Where in the world is Apache CloudStack?

Source: CloudStack Community Repository

Top 10: USA, Netherlands, UK, Japan, China, Taiwan, India, Canada, Brazil, France

108 Countries

2009-2011: build a cloud

2012-2013: operate a

cloud

2014-2015: profit from

a cloud

Functionality / Innovation: • Hyper-V Phase I • Dynamic Compute Offering • Remote-access VPN for VPC • Site-to-Site VPN (VR – VR) for VPC

Partner Integrations: • NetApp VSC • Juniper Contrail SDN Cost and Manageability: • Monitoring of System VMs • DB HA

Resiliency : • Rolling Upgrade

CloudStack 4.3

Features

7

Public Cloud Services CAGR (2012-2017) By Segment

16.9%

10.8%

14.9%

20.2%

23.5%

24.0%

37.3%

0% 5% 10% 15% 20% 25% 30% 35% 40%

Public Cloud Services Total

Cloud Business Process Services (BPaaS)

Cloud Advertising

Cloud Application Services (SaaS)

Cloud Management and Security Services

Cloud Application Infrastructure Services (PaaS)

Cloud System Infrastructure Services (IaaS)

CAGR (2012-2017)

Source: Gartner, Public Cloud Services Forecast, September 2013 (G00248730)

Bare metal server integration

• CloudStack makes physical servers and virtual machines appear the same to developers

• CloudStack manages any servers that support IPMI and PXE boot

• CloudStack can supply DHCP/PXE server or use existing DHCP/PXE servers

• CloudStack programs TOR switches to expose the right VLAN for each server

CloudStack Management

Server

CloudStack

API

XenServer/vSphere

OS OS OS …

DHCP

PXE

OS OS OS …

Overlay network can span multiple zones

(CloudStack 4.4)

Host 1

Host 3

Host 2

Host 4

CloudStack Virtual Router supports variety of network services

But VR becomes a single point of failure and a bottleneck for inter-network routing

VM 1

VM 2

VM 3 VR

Public Network

Network Services • DNS & DHCP • NAT • LB • ACL • VPN

VM 4

OpenFlow vSwitch OpenFlow vSwitch

OpenFlow vSwitch OpenFlow vSwitch

Availability Zone 1

Availability Zone 2

Distributed routing and ACL (CloudStack 4.4

and beyond)

Host 1

Host 3

Host 2

Host 4

OpenFlow vRouter becomes the first and last hop in routing

OpenFlow routing works over full mesh of tunnels

Backup VR in a separate zone

VM 1

VM 2

VM 3 VR

Public Network

Network Services • DNS & DHCP • NAT • LB • ACL • VPN

VM 4

OpenFlow vRouter OpenFlow vRouter

OpenFlow vRouter OpenFlow vRouter

Availability Zone 1

Availability Zone 2

Backup VR

Public Network

Future operational improvements

• Resiliency ᵒ Crash behavior

ᵒ Idempotency

ᵒ Design for failure

• Admin intervention ᵒ When to try to recover and when to hand control over to admin

ᵒ Integrated monitoring

ᵒ Visibility to long-running operations

Delayering

Compute

Hypervisor

Operating system

App development

Cloud-optimized infrastructure

Container, Docker, CoreOS, etc.

IT operations

DevOps

Storage

Networking

Can we make CloudStack install as

simple as Apache HTTP server?

yum install httpd

vi /etc/httpd/conf/httpd.conf

chkconfig httpd on

service httpd start

Rise of cloud-optimized infrastructure

Build working cloud service using legacy

infrastructure

Optimize infrastructure

for cloud service

Cloud optimized infrastructure becomes the

industry norm

Past Future Present

Work better. Live better.