Public and private Cloud Computing with openqrm. by Matt Rechenburg Project Manager of openqrm (Images from wikimedia)

Transcription

1 Public and private Cloud Computing with openqrm by Matt Rechenburg Project Manager of openqrm (Images from wikimedia)

2 Agenda for this workshop Theory OpenQRM: Concepts, Architecure, Features, Mechanisms and Installation The openqrm Cloud Practical Installing, building and updating openqrm Enabling features via plugins Creating a resource pool Preparing server-templates from the image-shelf Cloud setup and configuration Administration of Clouds / Cloud-Security

3

4 Grid Computing Automated deployment Cloud Computing? SAAS Utility Computing Distributed computing Virtualization

5 Wikipedia: Cloud computing is Internet ("cloud") based development and use of computer technology ("computing"). It is a business information management style of computing in which typically real-time scalable resources are provided as a service over the Internet to users who need not have knowledge of, expertise in, or control over the technology infrastructure ("in the cloud") that supports them.

6 Software as a Service vs. Automated Provisioning

7 Why open-source is important for Cloud Computing?

8 Its mostly based on existing open-source Components It consists of many integrated technologies Let's not re-invent the wheel OSS-projects are good at what they are doing The challenge is Integration CC needs an open API to be extensible for existing third-party utilities

9 Features Complete separation of physical hardware and server appliances Automated network-management Support for multiple virtualization technologies Single management console Integrated storage-management for rapid-deployment Ready-made server-images Automated system- and service monitoring High-Availability with N-to-1 failover Completely Plug-able No vendor locking Cloning and deploying server from golden-images in seconds

10 How do we install our servers?

11 The servers gets ordered The server gets delieverd The server got physically setup The server gets connected to the network The OS is being installed on the harddisks The server gets its appliaction installed The server gets its final configurtion The server gets monitoring configured The server gets backup configured...

12 What is the weakest part of your hardware?

13 The concept of an appliance What is linux? A kernel file An initrd file Some kernel module files A root-filesystem (files) We should treat linux-servers like files!

14

15 ... think of booting your servers from gmailfs :) Root-filesystems can be anywhere Storage-plugins providing new types Plugin is responsible to mount the rootfs Local-disk/NFS/Iscsi/Aoe/Netapp... Storage-server can clone server-images

16 Rapid deployment Linux-Kernel Kernel Modules Root-filesystem (NAS/SAN/local/*) Hardware (dump) + Software your Service Storage

17 Virtualization support? Hypervisors are JUST resource-providers!

18 Plug-able Virtualization! Virtualization plugins provide resource types Responsible to map Hypervisor-commands (create/start/stop/remove/configure etc.) Virtual Machines boot via PXE Generic provisioning deploys to any VM-type Management is the same as for physical systems

19 ... continued automation Automated monitoring Automated network management Automated storage management Automated resource planning Single place of updates/backup/restore

20 GREEN IT

21 ... some fun with high-availability N to 1 fail-over Task : Get 10 custom physical servers high-available Usually : Take another 10 servers as separated hot-standby Requirements : 20 physical systems openqrm option 1: Use 1 idle hot-standby for all 10 physical servers Requirements : 11 physical systems

22 ... you even can save the one physical hot-standby fail-over, physical to virtual openqrm option 2: Use virtual machines as hot-standby's Requirements : just the 10 physical systems Fail-over by rapid re-deployment Server-images are not connected to hardware! Fail-over from physical to virtual from any type Server-images are not connected to resource types! OpenQRM keeps your data-center running

23 golden-images from the shelf Server-images are just root-filesystems Ready-made images from the image-shelf Server-image gets downloaded to storage-server Kernel is created from the image root-filesystem Image gets deployed from storage-server Storage-servers can clone server-images Concept of golden-images Deployment of server snapshots

24 Cloud Computing! Fully automated provisioning cycle External User portal for cloud-requests Manual or automatic approval Deployment to physical- or virtual machines Sends mail in case of cloud-events Integrate with Puppet

25 $ $ $$ $ $ The billing mechanism in the Cloud $ $ $ $ $ $ User registers to the Cloud User buys Cloud Computing Units (CCU's) User requests Systems from the Cloud CCU's are charged on the Users account CCU's are a generic currency for compute resources

26

27 On our roadmap... Integration with more Virtualization technologies Adding a kernel-shelf Database configuration via GUI Integrating more useful data-center tool... and we are looking for sponsors!

28 Time for the live demo

29 Time for your questions

30 Many thanks for joining this presentation! Enjoy OSDC 2009 on behalf of the openqrm team Matt Rechenburg