Automating the Creation and Management of Cloud Workloads

Transcription

1 Automating the Creation and Management of Cloud Workloads Rick Ashford Don Vosburg Cameron Seader Technical Specialist Technical Specialist Technical Specialist

2 Introduction

3 A Conversation Before Cloud Computing We need faster rollout of services That ll cost you How much? I can t say Isn t there unused capacity on systems we paid for? Possibly, but it s all part of a virtual pool of servers Not going to happen 3 IT Manager Business Executive I d rather pay by user

4 Promise of Private Cloud Computing 4 Lower Costs Increased Agility Greater Control and Security

5 A Conversation After Cloud Computing We need faster rollout of services. Is later today OK? How much? $1.50/hour. What if I have to expand or shrink the user base? No problem. You're in control. Not going to happen. 5 Cloud IT Manager Provider Business Executive I love you!

6 Why SUSE Cloud? 6

7 SUSE Cloud 2.0 7

8 Image Creation

9 How do I build it? There are 3 ways to create SUSE Linux Enterprise images: The hard way The not quite as hard way The easy way 9

10 How do I build it? The hard way... Manual build process Tedious Labor-intensive 1:1 ratio between target disk size and image size Be sure to stretch out your scroll-button finger before starting I'm not going to show you how to do this. It makes my head hurt. 10

11 How do I build it? The not quite as hard way... Kiwi open source project Developed and hosted by opensuse Portal page: Can create for multiple architectures Can create for multiple distributions Can be deployed to physical, virtual and cloud 11 vmdk, qcow2, vhd, ovf, raw, lxc Very flexible With flexibility comes complexity

12 How do I build it? The easy way... SUSE Studio Two ways to get it: 1. SUSE Studio Onsite 2. SUSE Studio Online Provides a simplified, web-based user interface for Kiwi 12

13 It's SHOWTIME! Thank you. 13

14 Deployment

15 How do I deploy it? There are 3 ways to deploy SUSE images in the cloud: The easy way The not quite as easy way The hard up-front, but totally easier in the end way 15

16 How do I deploy it? The easy way... Manual deployment process Log into the dashboard for SUSE Cloud Go to the images section Select your image and launch it Configure networking and storage as necessary Very quick and easy... If you're doing it once 16

17 How do I deploy it? The not quite as easy way... Use the API Python libraries Script out the manipulation of compute, network, and storage Labor intensive up front, but scales easily to large deployments Not terribly friendly to all potential cloud users 17

18 How do I deploy it? The hard up-front, but totally easier in the end way OpenStack Heat Project Incubated project for Grizzly Technical Preview in SUSE Cloud 2.0 Heat is a service to orchestrate multiple composite cloud applications 18

19 How do I deploy it? The hard up-front, but totally easier in the end way Heat is a service to orchestrate multiple composite cloud applications using the AWS Cloud Formation template format, through both an OpenStack-native ReST API and a CloudFormation-compatible Query API. 19

20 How do I deploy it? The hard up-front, but totally easier in the end way Heat is a service to orchestrate multiple composite cloud applications using the AWS Cloud Formation template format, through both an OpenStack-native ReST API and a CloudFormation-compatible Query API. Um... what? 20

21 How do I deploy it? The hard up-front, but totally easier in the end way Heat allows you to pre-define a set of compute, network, and storage requirements to provide a specific service, and deploy the whole thing automagically. 21

22 It's SHOWTIME! Thank you. 22

23 Management

24 How do I manage it? There are 3 ways to manage SUSE images in the cloud: The cross your fingers way The hard way The easy way 24

25 How do I manage it? The cross your fingers way... How to: Just let it sit and ignore it Pros: No initial labor costs and scales easily to large deployments Cons: Time and unapplied security patch releases will make your instance unsupportable and/or insecure 25

26 How do I manage it? The cross your fingers way... Rounding up, approximately 100% of cloud workloads run unpatched The Guy I Ran Into at the OpenStack Summit 26

27 How do I manage it? The hard way... Design your own custom-built mechanisms to manage everything 27 Very tailored to a specific environment, rarely flexible Must be managed as its own project, on top of the management you're trying to get done in the first place Training the new guy takes forever Highly susceptible to hit by a bus complications

28 How do I manage it? The easy way... SUSE Manager 28 Manage both SUSE and Red Hat servers Provides automated... Software management System provisioning Configuration Auditing Monitoring

29 How do I manage it? The easy way... Examples of automation opportunities Auto-registration Integration with SUSE Studio Tailor custom groups, packages, configurations Maintenance 29 Schedule patching/configuration changes to fall in specified maintenance windows In-place Service Pack upgrades Automated major-version upgrades

30 It's SHOWTIME! Thank you. 30

31

32 Unpublished Work of SUSE. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.