sign in sign up
<<
Home , Docker (software), Ganeti, OpenStack, OVirt, Platform as a service

A Complete Open Storage, Virt, IaaS, PaaS

Dave Neary Open Source and Standards,

1 Agenda

1. Traditional 2. The move to IaaS 3. Storage 4. PaaS, application encapsulation and orchestration 5. Cloud monitoring, service brokerage

2 Agenda

1. Traditional virtualization 2. The move to IaaS 3. Storage 4. PaaS, application encapsulation and orchestration 5. Cloud monitoring, service brokerage

3 Virtualization

After

Before

4 Virtualization

● Consolidation of hardware – fewer, bigger servers

● Workload management – over-subscribed services get more hardware

● Protect your apps – fault tolerance, high availability, , Network, disk, compute, memory Quality of Service

● Ability to scale up – add more hardware and modify resources allocated to VM on the fly

● No change to legacy apps

5 Open Source virtualization

KVM management application Open Source alternative to vSphere

Widely deployed Hosted by Foundation since April 2013

Developed by to manage clusters Manages KVM and nodes

6 Agenda

1. Traditional virtualization 2. The move to IaaS 3. Storage 4. PaaS, application encapsulation and orchestration 5. Cloud monitoring, service brokerage

7 Infrastructure

● Self-service provision

● Many identical servers

● Stateless services

● Scale-out easily – load balancing, public IPs, as service

● Move to

8 Pets vs Cattle (yes, again)

Scale Up Scale Out - Servers are like pets. - Servers are like cattle. Pets are given names, are unique, Cattle are given numbers and lovingly hand raised and cared for. are almost identical to each When they get ill, you nurse them other. When they get ill, you get back to health another one.

“Future application architectures should use Cattle but Pets with strong configuration management are viable and still needed” - Tim Bell, CERN

9“ OpenStack architecture

● Modular architecture

● Designed to easily scale out

● Based on (growing) set of core services

10 Instance types

XL XL 16 cores 30 GB memory

M L L L M

Server 19234 19235 32 cores 32 cores 60GB memory 60GB memory

11 Sample cloud application

6. Shared storage 4. Load balanced

1. Load balancer 5. Replicated with public IP 2. Load balanced database web servers 3. Load balancer

Web service

12 Sample cloud application

● Stateless – no side-effects in instance, memory only

● Persistent storage requires block storage or object storage service, or shared filesystem

● Requires rearchitecture of legacy applications

13 Agenda

1. Traditional virtualization 2. The move to IaaS 3. Storage 4. PaaS, application encapsulation and orchestration 5. Cloud monitoring, service brokerage

14 Storage

● Clouds needs scale-out storage

● Disk drives fail. All the time

● Image, block, and object storage, and/or shared filesystem

● Scale-out storage on commodity hardware - GlusterFS, , RiakCS, Swift

● Virtualization aware, tight integration with virtualization and Infrastructure as a Service desirable

15 Scale-out storage

16 Scale-out storage

17 Agenda

1. Traditional virtualization 2. The move to IaaS 3. Storage 4. PaaS, application encapsulation and orchestration 5. Cloud monitoring, service brokerage

18 PaaS =

A Cloud Application Platform

Code Deploy Enjoy

Push- Save Time and Money Code your app button Deploy, and your App is running in the Cloud!

19 Consolidated B-24 Liberator

Incredibly sophisticated. ~500k parts, assembled by unskilled labor.

No manufacturing process. Parts were cast in rubber molds, so every part was slightly different.

Assembled in the heat of San Diego, which warped the metal and required whole assemblies to be adjusted.

Ford Motor Co. brought a manufacturing process … ●unit production went from 250 planes a year to 650 planes a month.

THIS IS OUR CHALLENGE TODAY

20 Physical Virtualized With PaaS

How to Build an App: How to Build an App: How to Build an App: 1. Have Idea 1. Have Idea 1. Have Idea 2. Get Budget 2. Get Budget 2. Get Budget 3. Submit hardware acquisition request 3. Submit VM Request request 3. Code 4. Wait 4. Wait 4. Test 5. Get Hardware 5. Deploy framework/appserver 5. Launch 6. Rack and Stack Hardware 6. Deploy testing tools 6. Automatically Scale 7. Install 7. Test testing tools 8. Install Operating System 8. Code Patches/Fix-Packs 9. Configure Prod VMs 9. Create user Accounts 10. Push to Prod 10. Deploy framework/appserver 11. Launch 11. Deploy testing tools 12. Request More Prod VMs to 12. Test testing tools meet demand 13. Code 13. Wait 14. Configure Prod servers (and buy 14. Deploy app to new VMs them if needed) 15. Etc. 15. Push to Prod 16. Launch “The use of Platform-as-a-Service technologies will 17. Order more servers to meet demand 18. Wait… enable IT organizations to become more agile and more 19. Deploy new servers responsive to the business needs.” –Gartner* 20. Etc.

21 Control vs automation IaaS PaaS SaaS

APPLICATION

APPLICATION PLATFORM (JBOSS, PHP, RUBY, ETC) OPERATING SYSTEM (RHEL) VIRTUALIZATION (KVM) HARDWARE (x86) STORAGE (GlusterFS)

Managed and Controlled by Customer (IT, Dev, or Increased Control User) Automated and Managed Increased Automation by the Public or Private Cloud Offering

22 OpenShift Origin

Multi-language, Auto-Scaling, Self-service, Elastic, Cloud Application Platform

23 CloudFoundry

24

25 Orchestration and deployment

● Containerization – Docker, OpenShift cartridges

● Orchestration templates – Heat, CloudFormations

● Configuration management – , Puppet, , , CFEngine...

26 Agenda

1. Traditional virtualization 2. The move to IaaS 3. Storage 4. PaaS, application encapsulation and orchestration 5. Cloud monitoring, service brokerage

27 Industry Trend – Hybrid Cloud Existing IT + Private Cloud + Public Cloud = “Hybrid Cloud” Private Cloud

Physical IT Virtual IT Private Cloud Hybrid Cloud

Public Cloud

It's all coming together!!!

28 One Ring to Rule them All

● Cloud management software

● “Single pane of glass” to allow management of traditional Virt and private and public IaaS

● Enables policy enforcement ● Facilitates service migration ● Frees you from vendor lock-in ● CloudForms Management Engine

29 Open Hybrid Cloud

Legacy virtualization Private Public (VMware, cloud cloud oVirt/RHEV) (eg. OpenStack) (AWS, GCE)

30 Open Hybrid Cloud

Cloud services broker, Cloud management

Legacy virtualization Private Public (VMware, cloud cloud oVirt/RHEV) (eg. OpenStack) (AWS, GCE)

31 Open Hybrid Cloud

Developer environment Guest instances Platform as a Service

Cloud services broker, Cloud management

Legacy virtualization Private Public (VMware, cloud cloud oVirt/RHEV) (eg. OpenStack) (AWS, GCE)

32 Open Hybrid Cloud

Developer environment Guest

g instances n i Platform as a Service k r o w t

e Cloud services broker, Cloud management N

d e n i

f Legacy e Private Public

D virtualization cloud cloud e

r (VMware, a oVirt/RHEV) (eg. OpenStack) (AWS, GCE) w t f o S Shared storage (object, block)

33 Open Hybrid Cloud

Developer environment n o i Guest t a r t g instances s n i Platform as a Service e k h r c o r o w

t , t e Cloud services broker, Cloud management n N

e

d m e y n o i l

f Legacy p e

Private Public e

D virtualization d

cloud cloud , e t

r (VMware, n

a (eg. OpenStack) (AWS, GCE)

oVirt/RHEV) e w t m f p o o S l e v

Shared storage (object, block) e D

34 Open Hybrid Cloud needs Open Source

participate integrate stabilize

35 THANK YOU! QUESTIONS?

Dave Neary [email protected] @nearyd

36