Several additional changes are provided with this APAR.

Transcription

1 /*********************************************************************/ /* COPYRIGHT - */ /* Licensed Materials - Property of IBM */ /* This product contains "Restricted Materials of IBM" */ /* 5741-A7 (C) Copyright IBM Corp */ /* All rights reserved. */ /* US Government Users Restricted Rights - */ /* Use, duplication or disclosure restricted by GSA ADP Schedule */ /* Contract with IBM Corp. */ /* See IBM Copyright Instructions. */ /*********************************************************************/ /* File Name: CMA42 FILE */ /* Description: Cloud Manager Appliance information */ /* Status: z/vm Version 6, Release 3. */ /* Function: Contains information on obtaining and installing */ /* Cloud Manager Appliance (CMA) for z/vm. */ /* Change Activity: */ /* VM CMA support */ /*********************************************************************/ NOTE: IBM recommends running xcat with an initial storage value of least 8 Gigabytes (8G) of virtual storage. The XCAT user ID is shipped with a default virtual storage of 2 Gigabytes (2G). The CP directory entry for the XCAT user ID should be changed to a minimum of 8G before restarting the XCAT virtual machine VM Support for z/vm Cloud Manager Appliance (CMA) In order to provide an easy method to deploy an OpenStack controller or compute node with z/vm support and to provide an entry level IBM Cloud Manager with OpenStack for z Systems, the z/vm Cloud Manager Appliance (CMA) is provided with this APAR. Introducing the z/vm Cloud Manager Appliance (CMA) which replaces the Cloud Manager with Openstack for z/vm Several additional changes are provided with this APAR. * Networking netmask and gateway values can now be specified in the DMSSICNF COPY file for the ZHCP service machine. * The xcatconf4z script which is installed on a virtual server prior to its capture by OpenStack products has been updated. The script is shipped with the xcat MN. The OpenStack z/vm plug-in at the Juno level utilizes the new support in xcatconf4z. For this reason, it is recommended that images be recreated with the latest version of xcatconf4z after updating xcat or the CMA controller with this new service. Chapter 6 of the Enabling z/vm for OpenStack book guides the user in creating an image and installing xcatconf4z on an image. The APAR VM65676 TARBIN should only be applied to the CMO appliance if you are migrating from CMO to CMA For this migration, proceed to "Migrating from CMO 4.1 (Icehouse) to CMA 4.2

2 (Juno)" below. If you are installing CMA without migrating from CMO , continue with at "GENERAL INSTALLATION INSTRUCTIONS" below Migrating from CMO 4.1 (Icehouse) to CMA 4.2 (Juno) If you are installing Cloud Manager Appliance (CMA) for the first time, start with the instructions under "GENERAL INSTALLATION INSTRUCTIONS" below. If you are upgrading CMO 4.1 to CMA 4.2, continue with the instructions here and in the "GENERAL SERVICE INSTRUCTIONS" below. Before restoring the new CMA DDR image, be aware that: 1. You need to apply all CMA Icehouse APARs before migrating to the CMA Juno version. The latest list of CMA Icehouse APARs can be found at: 2. For controller role, all configuration files, all OpenStack database and other data are kept in LVM disks which are built with disks defined in cmo_data_disk in DMSSICMO COPY file. 3. For compute role, there is no LVM disk. All configuration files are kept on its root disk (MDISK 11). If you have put any file on the compute node, you should back them up to your workstation before restoring the new image. GENERAL SERVICE INSTRUCTIONS Log into the xcat GUI on the CMA as ADMIN and go to "Run script" panel for the xcat node: Enter the following commands to bring 4 disk online, find the device the DASD is on and mount it: Bring online with chccwdev -e 4 Setting device..4 online Done Find the device name associated with the 4 disk: cat /proc/dasd/devices..11(eckd) at ( 94: ) is dasda : active at blocksize: 496,..2(ECKD) at ( 94: 4) is dasdb : active at blocksize: 496,..21(ECKD) at ( 94: 8) is dasdc : active at blocksize: 496,..22(ECKD) at ( 94: 12) is dasdd : active at blocksize: 496,..193(ECKD) at ( 94: 16) is dasde : active at blocksize: 496,..191(ECKD) at ( 94: 2) is dasdf : active at blocksize: 496,..4(ECKD) at ( 94: 24) is dasdg : active at blocksize: 496,

3 Mount the device. Find the..4 reference in the previous output. In the example above, the name to use is dasdg. modprobe fuse cmsfs-fuse /dev/dasdg /mnt Now we need to install the rpm file(s) with the CMORPM.SH command. We need an executable version of this script. cd / cmsfscp -d /dev/dasdg -a CMORPM.SH /tmp/cmorpm.sh chmod +x /tmp/cmorpm.sh /tmp/cmorpm.sh /mnt/<aparnum>.tarbin where <aparnum> is the APAR number of the change you are installing For example, /mnt/vm65652.tarbin (there may be more than one rpm installed) Preparing... ########################################### [1%] 1:<rpmname> ########################################### [1%]... The cmorpm.sh script will unmount the 4 device when finished. Delete the cmorpm.sh rm /tmp/cmorpm.sh After the rpm is installed, you need to CP FORCE and CP XAUTOLOG VSMGUARD to bring the changes online. NOTE: If you are migrating from CMO 4.1 to CMA 4.2, continue with the following instructions: Once the appliance is running again, ssh to the appliance, log on using mnadmin userid and issue: sudo /usr/bin/perl /usr/local/bin/premigration.pl or sudo perl /usr/local/bin/premigration.pl This is sample output: Found CMA Icehouse version, prepare to migrate to Juno version Setting device..c online Done Setting device..d online Done Pre-migration done

4 You then need to follow the instructions in the "Initial Setup" section to restore new CMA image. GENERAL INSTALLATION INSTRUCTIONS DASD Requirements: CMA can be installed and run from either ECKD or FBA DASD. To complete the installation you will need to choose one of the following based on your system's DASD availability. ECKD (339) minidisks, each with 3338 cylinders 1 to hold the CMA appliance (XCAT 11) This minidisk becomes the CMOAPP volume 1 to hold the packed copy of CMA CKD (MAINT63 12) 1 to hold the unpacked copy of CMA CKD (MAINT63 13) FBA (SCSI) 3 FBA minidisks, each with 4,86,72 blocks 1 to hold the CMA appliance (XCAT 11) This minidisk becomes the CMOAPP volume 1 to hold the packed copy of CMA FBA (MAINT63 12) 1 to hold the unpacked copy of CMA FBA (MAINT63 13) If you are upgrading CMO 4.1 to CMA 4.2, contiue with "Download the CMA file" section below Initial set up You must define a new minidisk to the XCAT user ID on your z/vm 6.3. system. This new minidisk is where the CMA resides. Note: If you had installed an earlier copy of CMO or CMA and you are replacing that copy, you can reuse the minidisk used for that earlier copy. LOGON MAINT63 on your z/vm 6.3. system. If you are using a CP directory management tool, such as DirMaint, you should use the appropriate directory management tool commands to add this minidisk. If you are not using a directory management tool, you should use XEDIT to change your CP user directory using your local change management procedures. If you are using ECKD DASD on your system, add the following minidisk statement to the XCAT user ID on your system. If you are running in a multiple member SSI, you should add the MDISK statement to the XCAT subconfig entry for the member where you will run the XCAT user ID. If you will be running the appliance on multiple members of an SSI cluster, each member must have its own minidisk defined. For ECKD DASD, add this statement to the XCAT user ID MDISK cccc 3338 xxxxxx MR ALL WRITE MULTIPLE For FBA (SCSI) DASD, add this statement to the XCAT user ID MDISK 11 FB-512 bbbb xxxxx MR ALL WRITE MULTIPLE

5 where cccc bbbb xxxxxx the starting cylinder number on the real ECKD DASD defined at the CMOAPP volume id. Do not define this minidisk at cylinder of the real ECKD DASD because restoring the CMA will replace the volume label and cause the system to not be able to find this ECKD device later. the starting block number on the real FBA DASD defined at the CMOAPP volume id. Do not define this minidisk before block 132 of the real FBA (SCSI) DASD because restoring the CMA will replace the volume label and cause the system to not be able to find this FBA device later. the volume id label of the real device where the minidisk resides You should still be logged on to the MAINT63 user ID. You need to define two more minidisks to hold the restorable CMA image (virtual device addresses: 12 and 13). These two minidisks will be owned by the MAINT63 user ID and should be defined as the sizes listed above in the DASD Requirements section. If you are using a CP directory management tool, such as DirMaint, you should use the appropriate directory management tool commands to add this minidisk. If you are not using a directory management tool, you should use XEDIT to change your CP user directory using your local change management procedures. These two minidisks will contain copies of the CMA image from the IBM Fix Central repository. These copies only need to exist on your z/vm 6.3. system until the CMA is restored and running. If you are in a multimember SSI, these two minidisks can be shared across the MAINT63 members in the SSI cluster. After defining these minidisks to the MAINT63 user ID, you need to make them accessible to MAINT63. Issue the following commands: 1. CP LINK * MR 2. CP LINK * MR 3. FORMAT 12 T when prompted, respond 1 when prompted again, respond MNT12 4. FORMAT 13 U when prompted, respond 1 when prompted again, respond MNT13 If you prefer, you can use SFS to hold these files. Your SFS filepool must be large enough to contain the download file and the unpacked copy of that file. Refer to the file sizes below for the amount of free space needed in your SFS filepool. Using SFS can help reduce the total amount of disk space consumed by the CMA image files. To use SFS directories, you need to create two directories using the commands 1. CREATE DIR fpool:maint63.cmapack 2. CREATE DIR fpool:maint63.cmaunpack 3. ACCESS fpool:maint63.cmapack T 4. ACCESS fpool:maint63.cmaunpack U

6 where "fpool" is the name of your SFS filepool, e.g. VMSYSU. You should now issue the command CP DETACH 12 to relinquish this minidisk for use by the FTP step described below. The FTP server requires write access to this minidisk and this command allows that to happen Download the CMA file The CMA file is located on the IBM Fix Central server. Point your favorite browser at the url You must be a registered user of IBM Fix Central. To register, click on "Register" in the upper right corner of the web page and follow the registration instructions. Once on the IBM Fix Central page, 1. click the "Select Product" tab 2. in the "Product Group" drop down, select "Other Software" 3. in the "Product Selector" drop down, enter IBM Cloud Manager with OpenStack 4. in the "Installed Version" drop down, select in the "Platform" drop down, select z/vm 6. click the Continue button 7. on the next page, select the IMAGE file for the DASD type of your CMA. Select either IBM-CMWO-zVM_ECKD_DASD IBM-CMWO-zVM_FBA_DASD 8. select one of the download methods listed on the next page and bring the IMAGE file down to your workstation. The files downloaded to your workstation will be either CMA422.ECKD CMA422.FBA Once the download to your workstation completes, you must bring the file up to your z/vm 6.3. system. If using FTP to move the file from your workstation to z/vm, you must transfer the file in a binary, fixed-format method with a logical record length of 124. From your workstation command prompt: FTP ipaddr_vm_system USER MAINT63 password BIN QUOTE SITE FIXRECFM 124 CD MAINT63.12 PUT CMA422.ECKD CMA422.ECKD

7 PUT CMA422.FBA CMA422.FBA QUIT The copy of the CMA image you have moved to your z/vm 6.3. system is in a packed format. You must unpack it before you can proceed to the next step. While still logged on the MAINT63 user ID, you unpack the file by issuing the commands 1. CP LINK * MR 2. ACCESS 12 T 3. COPYFILE CMA422 ECKD T CMA422 ECKD U ( UNPACK OLDDATE COPYFILE CMA422 FBA T CMA422 FBA U ( UNPACK OLDDATE Restore the CMA file Now that the CMA image file is on your z/vm 6.3. system, you must restore the image file to the XCAT 11 minidisk. While still logged on to MAINT63, do the following: 1. LINK XCAT MR 2. ACCESS 193 T 3. ACCESS 13 U 4. DDRREST 11 CMA422 ECKD U DDRREST 11 CMA422 FBA U The DDRREST command will display something similar to the following z/vm DASD DUMP/RESTORE PROGRAM HCPDDR698I DATA DUMPED FROM CMOAPP TO BE RESTORED HCPDDR697I NO VOL1 LABEL FOUND RESTORING CMOAPP DATA DUMPED mm/dd/yy AT hh.mm.ss GMT FROM CMOAPP RESTORED INPUT CYLINDER EXTENTS OUTPUT CYLINDER EXTENTS START STOP START STOP END OF RESTORE BYTES RESTORED END OF JOB After restoring the CMA to the XCAT 11 minidisk issue a DETACH 11 to relinquish control of the minidisk. You now must do your local configuration for the CMA. Refer to the publication z/vm V6.3 Enabling z/vm for OpenStack (Support for OpenStack Juno Release) SC for information on configuring and starting your new CMA appliance Download the ICM deployer installer files. The ICM 4.2 FP2 installer files are located on the IBM Fix Central

8 server. Point your favorite browser at the url You must be a registered user of IBM Fix Central. To register, click on "Register" in the upper right corner of the web page and follow the registration instructions. Once on the IBM Fix Central page, 1. click the "Select Product" tab 2. in the "Product Group" drop down, select "Other Software" 3. in the "Select from Other Software" drop down, select IBM Cloud Manager with OpenStack 4. in the "Installed Version" drop down, select in the "Platform" drop down, select z/vm 6. click the Continue button 7. on the next page, select the installer files, you need to select the file cmwo42_cma_install.tar 8. select one of the download methods listed on the next page and bring the installer file down to your workstation. Please Note: The installer file size is nearly 5G. Your workstation will need at least 5G of free space to hold the installer file. The files downloaded to your workstation will be cmwo42_cma_install.tar 4.9G Once the download to your workstation completes, you must bring the files up to your CMA. Before that, you need to check whether there is enough disk space on CMA to keep and install ICM deployer, 2G of free disk space is needed. From your workstation, use the SSH client tool to login to CMA with your mnadmin username and password. Once you login to CMA, issue the command df -h /dev/mapper/cmo-data Following is sample output: Ã root@cmademo~â # df -h /dev/mapper/cmo-data Filesystem Size Used Avail Use% Mounted on /dev/mapper/cmo-data 21G 1G 2G 5% /data You can determine how much disk space is available from the "Avail" column. If there is not enough disk space, you need to follow the instructions in Chapter 5 in the "Enabling z/vm for OpenStack", to modify DMSSICMO COPY file to add more disks using the cmo_data_disk variable. You can use an sftp client tool, such as scp, to bring all the ICM deployer installer files to CMA. Login username and password is the same as the CMA mnadmin username and password. All installer files should be stored in the mnadmin home directory Install ICM deployer Once you move the ICM deployer installer file to CMA, you should ssh to CMA and issue the command

9 tar xvf INSTALLER_PATH/cmwo42_cma_install.tar where INSTALLER_PATH is the file path of the installer tar file. Then issue the command sudo /usr/local/bin/cmoinstaller.sh -r CMO_INSTALLER_BIN \ -directory INSTALLER_DIR where CMO_INSTALLER_BIN is the name of your cmo installer bin file INSTALLER_DIR is the absolute path of location directory of the cmo installer bin file You will see following message when ICM deployer is installed successfully. Install CMWO installer completed successfully