IBM s Perspective on Image Management

Transcription

1 Boas Betzler, IBM Senior Technical Staff, Leader Image Center IBM Public and Private Cloud IBM s Perspective on Image Management November, 2010

2 What is Cloud Computing? A user experience and a business model Cloud computing is an emerging style of IT delivery in which applications, data, and IT resources are rapidly provisioned and provided as standardized offerings to users over the web in a flexible pricing model. An infrastructure management and services delivery methodology Cloud computing is a way of managing large numbers of highly virtualized resources such that, from a management perspective, they resemble a single large resource. This can then be used to deliver services with elastic scaling. Monitor & Manage Services & Resources Datacenter Infrastructure Access Services Service Consumers Cloud Administrator IT Cloud Service Catalog, Component Library Component Vendors/ Software Publishers Publish & Update Components, Images, Service Templates 2

3 Architectural Model for Cloud Computing Service Request & Operations Service Provider Service Creation End Users, Operators Cloud Services Service Planning Application/Business, Process, Assembly and Information Services Service Role-based Access Service Catalog Standards Based Interfaces Software Platform Services Infrastructure Services Cloud Management Platform Business Support Systems(BSS) Definition Tools Service Publishing Tools Operational Console Service Delivery Platform Operational Support Systems (OSS) Service Reporting & Analytics 3

4 Architectural Model for Cloud Computing Service Request & Operations IT Infrastructure & Application Provider Service Creation & Deployment End User Requests & Operators Service Management User Request Management/Self Service Portal Service Lifecycle Management Virtual Image Management Image Lifecycle Management Provisioning Security: Identity, Access, Integrity, Isolation, Audit & Compliance Performance Management Usage Accounting Availability/Backup/ Restore License Management Design & Build Service Catalog Request UI Operational UI Service Oriented Architecture Information Architecture Optimized Middleware (image deployment, integrated security, workload mgmt., high-availability) Virtualized Infrastructure Virtual Resources & Aggregations SMP Servers Server Virt. Storage Virt. Network Virt. Blades System Resources Storage Servers Storage Network Hardware Image Library (Store) Deployment Operational Lifecycle of Images 4 4

5 Taxonomy Image and Instance Image Provider controls Content and Quality User/Operator controls Content and Quality End User request instance Uses machine, Installs SW request image to be saved request instance Uses machine Cloud UI / API Cloud UI / API Master Image Catalog instantiate Serialize and save Private images instantiate Master Image Virtual Machine Instance 1 Modified Customer Image Virtual Machine Instance 2 Image Provider Repository Taxonomy: Image Instance Repository Image Library or Catalog Repository 5

6 Architecture - Spectrum between pre-build and bottom up install Pre-build Image Bottom-up install WAS JVM WAS WAS DB2 DB2 DB2 JVM WAS DB2 GCC Httpd JVM Linux Kernel Image Binary GCC httpd JVM Linux Kernel Image Binary GCC Httpd Linux Kernel Image Binary GCC Httpd Linux Kernel Image Binary Stack Stack Stack Stack Pre-build, integrated, Tested, cloned Image Cloned Image and Added layer Post initial boot Selection-List Approach with some Pre-integration and some testing post initial boot Roll-your-own Selection-List Installation post initial boot Composite Image Catalog Vendor: qredhat qnovel Select: q64bit q32bit Kernel Version q q Compiler: qgcc 4.1 qgcc 3.6 Web Server: qapache qthttpd JVM qsun qibm Database qmysql qdb2 Application Server qwebsphere qjboss 6

7 What is an image- Specifically a virtual image? It contains binary data that can be used to boot a virtual machine or LPAR when available to the CPU via storage or network connection. This also includes some metadata for information, configuration, instantiation and startup. E.g. X86.vmdk VMware virtual disk image file on a file system..vhd Xen and Hyper-V virtual disk image file on a file system. Partition on a Storage Device (e.g. Hard Disk) attached directly or via network. POWER Partition on a Storage Device (e.g. Hard Disk) attached directly or via network. mksysb.vdi POWER virtual disk image file on a file system. 7 System z Partition on a Storage Device (e.g. Hard Disk) attached directly or via network. There are other formats. 7 7

8 OVF Package.OVF XML metadata descriptor Includes details about each file in package, descrip on of virtual hardware, & license informa on What s not in OVF? The specifica on does not include service offering specifica ons..mf (optional) Manifest file, used for signi ng, contains the SHA-1 digetst It does not have any opera onal management protocol, API, et..cert (optional) Cer ficate file, used for signing It does not state how to build the image. Lamp.OVA Example Single File TAR format OVA recommended extension Order of the files in the OVA package specified by spec Resources (optional) Files String resource bundles, used for interna onal iza on.vmdk.iso.gzip Virtual Disks Compiles the list of Virtual Disks required for the Virtual Machine(s) OVF supports any Virtual Disk format with a publicly-disclosed specification Supporting Files ISO and other files Can be compressed and chunked 8 part1.vmd k

9 OVF, Image Activation & Capture Technology overview What s the big deal about applications in images? 4Applications keep instance configuration data in private configuration file. E.g. WAS image: IP address, DB2 connector config DB address, other admin passwords, performance settings, cluster settings. These settings are different for each instance. When master image gets converted to instance image, these needs to be set before application bootup. (to prevent e.g. a test image from momentarily connecting to production DB) 4OVF standard ( DMTF ) set up to describe image content and provide instance parameters. Does define XML schema Has support for single and multiple virtual machines ( virtual machine collection) Has support for configuration parameters definition & VM startup sequence. Does recommend using virtual CD as passing mechanism. Does not define component start-up sequence. 9

10 How does image activation take place? Master image is built with Activation engine inside 4A scripting engine that starts at boot-up before application services 4Reads the virtual CD with OVF xml for configuration 4Calls application specific scripts that set points of variability in application 4Releases startup to applications Other uses of activation engine 4Get additional assets 4Attach state based data/config for stateless images 10 10

11 Industry wide change to Image Management Images fast becoming the core object for deployment in datacenters bypasses installation problems, provides faster time to value, better availability, disaster recovery. Easy way to boot, store, distribute, copy software- OS & Applications Installation is as simple as a copy operation. (Configuration still needed) Fundamental mechanism for deploying cloud services (e.g. IBM Public Cloud, Amazon) Other companies beginning to ship images to solve installation problems. Customer Pain and New IT Challenges (Image Sprawl) Proliferation of virtual images in environments (just copy a file). Customer need a way or organizing, securing, managing deploying these images to the various virtualized platforms in a scalable manner. Customers need a way of managing the virtual instance once they are deployed. This includes monitoring, updating, tracking changes, auditing etc. Dormant/catalog images need maintenance too. (E.g. security patches) Customers need to manage the virtual images created by them in addition to any vendor offering images. Customers needs to integrate their images that are deployed with their processes and management tools

12 Image Management use cases Enterprise # of unique master images # of instances and private images Heterogeneous Geo. dispersed Key Personas Virtualized infrastructure ~ approx (= # of apps ) ~5,000 10,000 Yes Yes Operations Admin Dev/test Private Cloud < 200 ~1,000 approx No Yes Tester Extending to Service Provider # of unique master images # of instances and private images Heterogeneous Geo. dispersed? Key Personas IaaS PaaS SaaS < 50 base OS images * 100,000 No Possible Developer < 20 10,000 No Possible Developer < 10 10,000** No Possible Application user 12 * Customer application addition can increase this to ~ 3000 (e.g. AMIs) ** salesforce.com has about 55,000 instances ( estimate )

13 What is Image Lifecycle Management? Vendor built ISV Built Customer Built Capture and re-master Application images Capture OS image Images Designing Service using virtual images (Model Driven) Change Management of images Security of Images Update and patch images Deploy using network and SAN Customize and create VM instances for deployment Building Images and Metadata (creation or P-V,V-V) Store images in the Data center Repository Build virtual images based on model Catalog & Index images across many repositories. Manage replication of images Composite Service deployment using images 13

14 Image Lifecycle Management Design Build Manage Store Deploy Manage Tooling to design the stack of OS and applications in a virtual image. This can be done by modifying existing system image or by creating a new image structure. Images can represent single system or group of images can represent a composite application. Other discussion points Tooling to build virtual images and associate metadata with them. This can be done by capturing existing system or by creating a new image structure. Images can represent single system or composite application. Store the images in a repository. Manage multiple image repositories using a Library. They also need to be accessible from a deployment system. It includes offline operations capability including query and search. Repositories can be distributed and replicated for scale. 4 Standards : Open Virtualization Format Specification (OVF) 4 Governance : Control of images across the lifecycle steps 4 Storage media : Impact of Storage hardware on Image Management 4 *Security (including integrity, signing and access control) of images Deployment requires platform specific tools to take images from Store and use the appropriate mechanism (network or storage) to create an instance of the image for booting the system ( VM or LPAR) and attaching data images where needed. This includes customization of image for deployed instance. Use information from the build and deployment stage to better manage the deployed service. Management system needs to monitor, patch and update the deployed system. It also needs to include capture of a running system. The captured image can be modified for deployment in other locations or simply restored in its original location. 14

15 Enterprise Image Management End to end automation orchestrated Design Tools can also update image. Add software, patch. Graphically build application images. Output a model. Federated Image library manages composite images across hypervisors, locations, Build the binary image and OVF Promote image to envelope using the operational / preproduction test model. repository. Start tracking operational state. P-V and V-V tooling for consolidation. Application specific Images generally golden master Each capture. Hypervisor has its own filesystem and kept on shared repository where the storage, close to the Operational Tools can deployment takes servers. update image. Add place. Configuration software, is patch. done by OVF. Change tracking in CMDB. 15

16 Image Management Example: IBM Smart Business Development and Test on the IBM Cloud Our solution provides the following: Choice of seven virtual server configurations Option to add persistent storage Network bandwidth charged per GB transmitted Choice of over 50 pre-configured software images IBM Rational Application Lifecycle Management software IBM Lotus, WebSphere, DB2 and Informix stacks Complete Asset Management Solution for private images Payment options: Pay-as-you-go option (per virtual machine hour charge) Reserved capacity option Six reservation choice (small, medium, large for 6 or 12 months) Reserved capacity with discounted usage rates 16

17 With rapid, automated setup through a self-service portal that is designed for ease of use, you can deploy a service within minutes. You can have your development and test environment running in minutes on the IBM Cloud. Click and choose the service you need Choose the hardware and usage configuration Application provisioned and ready to run Step 1 Step 2 Step 3 17

18 Thank you! 18