Cloud on z Systems Solution Overview: IBM Cloud Manager with OpenStack

Transcription

1 Cloud on z Systems Solution Overview: IBM Cloud Manager with OpenStack June 1, 2015 IBM Systems Nisha Bonda Client Technical Specilist Mike Bonett zgrowth Team North America

2 Table of Contents ACKNOWLEDGEMENTS 3 INTRODUCTION 4 WHY CLOUD ON Z SYSTEMS? 4 IBM CLOUD MANAGER WITH OPENSTACK OVERVIEW 5 COMPLEMENTARY USAGE WITH IISZ PRODUCTS 7 Cloud on z Systems Solutions IBM

3 Acknowledgements This white paper was produced by the IBM zchampions Cloud Work Group. Authors: Nisha Bonda, Mike Bonett Contributors/Reviewers: Mike Baskey, Tony Liu Please provide any feedback and comments to Nisha Bonda at or Mike Bonett at Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. For a complete list of IBM Trademarks, see AIX, DB2, developerworks, IBM, IBM (logo), ibm.com, MVS, NetView, OMEGAMON, Parallel Sysplex, PR/SM, pseries, RACF System z, Tivoli, VTAM, WebSphere, z/os, z/vm, zenterprise, zseries, z Systems The following are trademarks or registered trademarks of other companies. Other company, product, and service names may be trademarks or service marks of others. Java and all Java-based trademarks are trademarks of Oracle Corporation, in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. OpenStack is a registered trademark of The OpenStack Foundation in the United States, other countries, or both. Cloud on z Systems Solutions IBM

4 Introduction Cloud is fast becoming the new infrastructure model. A cloud can offer a better way for IT organizations to build and manage development and test environments for new applications. Developers can obtain resources on demand and then release the resources when they are not needed anymore, which can greatly improve productivity and speed up each new application s time-to-market. Organizations are now moving beyond virtualization to higher stages of Cloud Computing. IBM Cloud Computing solutions focus on eased service consumption and management of an infrastructure, and z Systems delivers resiliency, availability, security and scalability for the most demanding workloads and environment. Deploying your cloud on z Systems can dramatically improve efficiency and economics, up to 32% lower total cost of ownership than x86 private cloud, all while delivering the trust and confidence of unmatched security and reliability on z System i. Why Cloud on z Systems? Cloud environments require the following characteristics: On-Demand Self Service -pick services you need, when you need them Broad Network Access -available over network through thin or thick clients Resource Pooling -resources are shared, serving multiple consumers Rapid Elasticity -capabilities provisioned, in some cases automatically Measured Service -pay only for what you use Multi-Tenancy multiple, isolated users and groups All of these characteristics must be provided in an authenticated and secure manner. The hypervisor on z Systems supports these characteristics by managing all platform computing resources efficiently with isolation, allowing multiple environments to co-exist while providing performance, reliability and availability. Its unique workload management capabilities enables high utilization with mixed workloads, allowing hundreds of mixed workloads to be run in parallel on Linux on z Systems. One of the top challenges in moving to a public or private cloud is security concern. z Systems makes security for the cloud a priority. z Systems architecture can provide organizations with the assurance and confidence to run many different applications containing confidential data on one z Systems, divided into partitions that keep each application s data secure and isolated from the others. This combination of security and multi-tenancy allows organizations to run various sized Cloud on z Systems Solutions IBM

5 workloads in parallel while allowing multiple users accessing the same application, running on the same operating system, on the same hardware. Cloud Computing must be supported on a reliable and highly available platform. Built-in hardware redundancy and fewer points of failure allow z Systems to provide those key factors to both private and public clouds hosted on its platform. The mainframe s dedicated processors for I/O operations, workloads with high I/O demand, such as transaction processing, can run more efficiently. Resources can be dynamically scaled without affecting ongoing operations. Each component is built to be resilient with support for non-disruptive configuration changes and dynamic replacement capabilities. Amongst security, reliability, performance and availability, organizations seek cost reduction for a cloud solution adoption. There is a variety of cloud pricing models; however most include either a consumption-based model or a subscription-based model. A mainframe-based private cloud can cost less overall than a cloud built on other platforms. A recent IBM study found that the three-year total cost of ownership (TCO) for a z Systems mainframe cloud can be 66% less than a thirdparty provider s public cloud and as much as 32% less than an x86-based private cloud ii. A variety of workloads can be consolidated and virtualized on a smaller footprint resulting in lower overall software costs when compared to other solutions. z Systems smaller footprint can lower costs of labor, electricity, and floor space. Case Study: 123 Workloads (219 VMs) 24,000,000 20,000, ,000,000 12,000,000 8,000,000 Labor, Power & Space Middleware Infrastructure 4,000,000 0 Public Cloud Private Cloud on x86 Cloud on z13 IBM Cloud Manager with OpenStack Overview IBM offers an integrated family of cloud technologies for quickly building public, private, and hybrid clouds. IBM Cloud Manager with OpenStack (ICM) is a solution Cloud on z Systems Solutions IBM

6 that is part of z/vm as the Cloud Manager Appliance that can be used towards setting up a cloud environment. IBM Cloud Manager with OpenStack is a simple, entry-level cloud management stack that can be used as a turn-key solution that cost-effectively delivers basic cloud capabilities across all supported IBM platforms. ICM is part of the z/vm 6.3 operating system and can run on z Systems, or can run on distributed x and p platforms. ICM provides heterogeneous cloud management across Power Systems, PureFlex/Flex Systems, System x, and Linux on z Systems environments along with multiple hypervisor support including VMware, PowerVM, KVM, Hyper-v, and z/vm. ICM has pattern support that are Chef-based patterns (recipes) that can work with the OpenStack Heat pattern engine (along with UrbanCode Deploy w/patterns). Cloud Manager allows simple workload deployment based on these (or custom) patterns, which speeds delivery of new services. Patterns with IBM Cloud Manager with OpenStack Pattern is an abstract concept that combines virtualized operating system images, hardware resources, and software configurations to create a customized instance for a particular purpose. A pattern can consist of a base image, middleware, and application instances integrated for a repeatable topology delivery to end-users. It can contain multiple images that can each be uniquely customized. An example of a pattern is a database server, web application server(s), HTTP server(s), and load balancer. Chef is an open-source integration and management framework that makes it easy to deploy servers and applications to any physical, virtual, or cloud location, regardless of infrastructure size ( infrastructure as code ). Chef allows software configuration via its recipes (procedures to install infrastructure components) and cookbooks (groups of recipes). Heat is an OpenStack component that integrates hardware and software deployments to create an infrastructure topology. Heat templates are text files where server, storage, network, and software components are defined and can be ordered via dependencies and patterns to support the desired topology sequence. IBM Cloud Manager with OpenStack supports Chef and Heat technology that allows association between hardware and software topology. For customers that prefer a graphical interface for interaction with Heat, UrbanCode Deploy with Patterns can be used to create templates for deploying into a z Systems Cloud. UrbanCode Deploy with Patterns allows a user to graphically create Heat templates via drag-and-drop methodology, using an optional Urban Code deploy server as the source of the software components. One can directly deploy Heat Cloud on z Systems Solutions IBM

7 template from UrbanCode Deploy with Patterns to an OpenStack Cloud through ICO and ICM. The primary use of IBM Cloud Manager with OpenStack is to allow end users to deploy Linux instances onto z/vm (from previous created source images) ICM supports patterns that depend on Chef cookbooks/recipes, or Heat templates deployed by Chef, which are built outside of the product. ICM provides a Chef infrastructure (server and client support) that can be used to create custom patterns. ICM provides both an admin (Horizon) console as well as a self-service UI along with a service catalog to deploy services (VMs) from. Complementary Usage with IISz Products IBM Cloud Manager with OpenStack can complement the products that are part of the IBM Infrastructure Suite for z/vm and Linux on z Systems (IISz), which can be used to administer, monitor, automate, and backup the z/vm cloud environment into which IBM Cloud Manager with OpenStack deploys guests. IBM Wave for z/vm is used by z/vm system programmers to administrate z/vm real and virtual resources for ICM cloud platforms. It also provides system programmer productivity tools to simply and improve the efficiency of this administration. IBM OMEGAMON XE for z/vm and Linux provides in-depth performance monitoring and reflex automation for z/vm and Linux on z Systems resources. IBM Cloud Manager with OpenStack can install the agent for Linux into deployed instances so that they can immediately connect to the IBM Tivoli Monitoring infrastructure. IBM Operations Manager for z/vm can apply automation polices to z/vm and Linux instances. For example, it can monitor the z/vm consoles of deployed guests and take automated actions based on messages that appear on the console. IBM Backup and Recovery Manager for z/vm provides z/vm system and volume backups to support fast recovery from problems. This supports backup of the z/vm cloud environment as a whole. IBM Tivoli Storage Manager allows users to back up, restore, and archive user and application data residing on Linux guests. IBM Cloud Manager with OpenStack can install the Tivoli Storage Manager into deployed instances so that the instance can immediately connect to a Tivoli Storage Manager server and immediately make use of these functions. Cloud on z Systems Solutions IBM

8 i The New Mainframe Cloud, IBM Systems Magazine, Fehmina Merchant, Ph.D. ii The New Mainframe Cloud, IBM Systems Magazine, Fehmina Merchant, Ph.D. Cloud on z Systems Solutions IBM