Setting Up the IBM Cloud Manager with OpenStack Cloud Manager Appliance (CMA) on z/vm

Size: px

Start display at page:

Download "Setting Up the IBM Cloud Manager with OpenStack Cloud Manager Appliance (CMA) on z/vm"

Brooke Lee
6 years ago
Views:

1 Setting Up the IBM Cloud Manager with OpenStack Cloud Manager Appliance (CMA) on z/vm This document can be found on the web at Version Date: May 5, 2015 Mike Bonett IBM Americas zgrowth Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 1

2 IBM Cloud Manager with OpenStack (ICM) supports the deployment of cloud environments using OpenStack technology. The ICM infrastructure consists of a deployment server, an OpenStack controller node (which provides the user interface) and one or more OpenStack compute nodes (which connect to the managed hypervisors). IBM Cloud Manager with OpenStack runs on various platforms, including z/vm, and can manage cloud environments on various hypervisors, including z/vm. On z/vm ICM is part of z/vm 6.3, where it is called the z/vm Cloud Manager Appliance (CMA). The CMA runs in the Extreme Cloud Administration Tool (xcat) Management Node z/vm guest. xcat is a component of z/vm 6.3 and is the interface used by IBM OpenStack based products to provision Linux guests in a z/vm LPAR. When ICM runs on a distributed platform, the OpenStack controller and compute node functions connect to XCAT. When the CMA is used, the controller and compute node functions run on z/vm. The following picture compares the basic architecture for each option, when managing a z/vm LPAR: With version , the CMA can manage z/vm as well as other hypervisor platforms (VMware, KVM, Hyper-V, Power). It can be activated and used as a trial without charge until licensing for support purposes is desired. Setting up ICM to run on the z System platform differs from the setup on distributed platform, and consists of activating and customizing the CMA. The major steps that must be performed: 1. Ensure that the environment is at the required level of maintenance. 2. Enable the directory maintenance facility (DIRMAINT) and Systems Management Application Programming Interface (SMAPI). Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 2

3 3. Obtain the CMA fixpack components (ECKD/FBA volume image and IBM Cloud Manager deployer). 4. Enable the CMA. 5. Execute the IBM Cloud Manager deployer. This technote provides guidance for accomplishing these steps. 1. Ensure that the environment is at the required level of maintenance xcat and SMAPI must be at current maintenance levels. URL on the IBM z/vm website lists the required PTFs that must be installed before proceeding with the next steps. Note that the PTFs are across multiple components. APAR VM65675 ( is the PTF that provides the CMA. Installing the PTF for that APAR( UM34565) creates the file CMA42 FILE on the MAINT 400 disk. This file contains detailed installation instructions to enable the CMA (see steps 4 and 5 below for more details). Subsequent PTFs have been released to correct errors found in APAR VM65676; these are also identified on the above IBM z/vm website URL. In addition, The latest RSU should be installed before installing the required PTFs. 2. Enable the directory maintenance facility (DIRMAINT) and Systems Management Application Programming Interface (SMAPI) SMAPI and DIRMAINT must be enabled and active. Instructions on enabling DIRMAINT are documented in z/vm: Directory Maintenance Facility Tailoring and Administration Guide ( Instructions for enabling SMAPI are documented in the Setting up and Configuring the Server Environment chapter in z/vm: Systems Management Application Programming ( The IBM Redbook The Virtualization Cookbook for IBM z/vm 6.3, RHEL 6.4, and SLES 11 SP3 ( contains an appendix with a step-by-step walkthrough of setting up DIRMAINT and SMAPI. This is useful for quickly getting these functions running in a non-production environment. 3. Obtain the CMA fixpack components (FBA/ECKD and IBM Cloud Manager Deployer). The components can be found as follows: Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 3

4 1. Log onto IBM Support: Fix Central ( 2. On the Find Product tab, make the following selections: a. Product Selector: IBM Cloud Manager with OpenStack b. Installed Version: c. Platform: z/vm After the selections, the tab contents should display as follows: 3. Press Continue to display the components: Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 4

5 4. Only 2 of the three components are needed: a. Select either IBM-CMWO-zVM_FBA_DASD or IBM-CMWOzVM_ECKD_DASD, depending on the volume type the file will be restored to. b. Select IBM-CMWO-zVM_CMA_Installer, as this is the ICM Deployer code 5. Once selected, follow the FixCentral prompts and procedures to download the files to the local workstation or server. 4. Enable the CMA with the fixpack Detailed instructions on the process are contained in CMA42 FILE on the MAINT 400 disk. This file should be reviewed in its entirety before proceeding. The following highlight key aspects of the process: If you are not migrating from the ICM 4.1 CMO appliance, skip to the GENERAL INSTALLATION INSTRUCTIONS section of the document. The XCAT guest comes defined with 2G memory size as a default. To support the CMA function it must be increased to a minimum of 8G. 3 additional minidisks of 3338 cylinders (ECKD) or blocks (FBA) each have to be allocated. Two will be allocated to MAINT630, one to XCAT The general process of using the new minidisks (details are in CMA42 FILE): Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 5

6 o Allocate the new volumes to the appropriate virtual machines o Upload and unpack the *ECKD_DASD or *FBA_DASD file using the 2 new MAINT630 volumes o Restore the unpacked ECKD file to the new XCAT volume Before uploading and executing the ICM deployed code, the CMA must be active. Details on how to customize and bring up CMA are documented in the OpenStack Configuration chapter of Enabling z/vm for OpenStack (Support for OpenStack Juno Release), available at Some highlights and considerations: o Do NOT force xcat to restart it; instead, force and xautolog VSMGUARD. o The parameter for the CMA are set by editing the DMSSICNF COPY and DMSSICMO COPY files on the MAINT 193 disk: DMSSICNF COPY contains the XCAT parameters for its two guest machines (XCAT and ZHCP) DMSSICMO contains the ICM and OpenStack parameters. This includes whether this CMA will be a controller node (user functions as well as a compute node) or a compute node only (managed by another ICM controller node). In addition, volumes that are used to create a LVM filesystem mounted at /data are defined here; ensure there is enough space to allow for the installation of the ICM deployer in the next step (a minimum of 50GB free space, in reality make this larger as it is used for various purposes). Create a network diagram matching your desired configuration before configuring these files. Example configuration diagrams are provided in the Network Configurations section of this chapter. o Be sure to edit these files from the MAINT630 ID using the LOCALMOD procedure; otherwise, when service is applied changes to these files will be overlaid. o If XCAT was previously configured and running, and the CMA controller or compute node function is now being added, any information previously store in XCAT (such as node definitions and source and deployed images) will be erased. There is no migration path from standalone XCAT to the CMA appliance. o The first few times the xcat virtual machines (XCAT and ZHCP) are started, it is helpful to use the z/vm CP command SET SECUSER, so that their console output can be viewed on another logged on guest (e.g. SET SECUSER XCAT MAINT). This allows one to view the console messages as they are produced, which can aid any debugging required. If this is an Operations Manager for z/vm environment, Operations Manager for z/vm should be the secondary user to allow viewing of the console. Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 6

7 o z/vm supplies an installation verification program (IVP) within the CMA that will check for configuration problems. Do not proceed further until all warnings have been addressed (the IVP returns no warnings). 5. Upload and execute the IBM Cloud Manager (ICM) deployer The ICM deployer is contained in the.tar file downloaded from Fix Central. Follow the instructions in CMA42 FILE for uploading it to the CMA and executing the ICM deployer. Expect the ICM deployer to take at least 10 minutes to finish. The deployer produces only a handful of console messages, and only after the OpenStack services restart after the deployment completes. Results When the above steps are completed successfully, the following components will be running in the XCAT virtual machine: o xcat user interface and functions for capturing images and deploying images into Linux instances. o For a controller node: o ICM user interface, including both administrative and self-service catalog functions o OpenStack Nova, Neutron, Cinder, Glance, Keystone functions used to manage instance, network, storage, image, and security functions o OpenStack Horizon interface for dashboard management of the OpenStack environment, and deploying instances and Heat Orchestration stacks (patterns). o Chef server and client, which can be used for storing and deploying chef cookbooks and recipes o Files to support deploying instances onto other platforms (e.g. chef rpms for power and x86) o For a compute node: o OpenStack Nova and Neutron functions All ICM documentation is available in the IBM Cloud Manager for OpenStack Knowledge Center at The key documents are: IBM Cloud Manager for OpenStack Administrators Guide: provides details on administrating the CMA environment, such as managing users, projects, and managed cloud environments. Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 7

8 IBM Cloud Manager for OpenStack Users Guide: provides details on using the self-service portal. John Arwe has published a summary of common installation and deployment issues, and security and usage hints and tips on the IBM developerworks IBM Cloud Manager with OpenStack wiki. The URL is _9626_24cbbb86fbb9/page/zVM%20Cloud%20Manager%20Appliance%20%28CMA%29%20deployment %20information Acknowledgements Special thanks to the following individuals who provided review and content guidance and assistance: John Arwe, IBM Mike Baskey, IBM Mike Sine, IBM Setting up the IBM Cloud Manager with OpenStack CMA on z/vm 8

IBM Cloud Manager with OpenStack: z/vm Integration Considerations

IBM Cloud Manager with OpenStack: z/vm Integration Considerations May 2016 IBM zgrowth Team Cloud & Smarter Infrastructure Mike Bonett Executive I/T Specialist Special Notices This document reflects the