Red Hat Enterprise Linux on IBM System z. Management and Provisioning Best Practices

Transcription

1 Red Hat Enterprise Linux on IBM System z Management and Provisioning Best Practices Thorsten Scherf Principal Consultant Red Hat Global Professional Services Filipe Miranda <fmiranda@redhat.com> Global lead for Red Hat Technologies for IBM System z and POWER Systems

2 Red Hat Enterprise Linux on IBM System z Management and Provisioning Best Practices

3 Linux Deployment on Z Cloning based profiling Pros: Easy to understand for z sysadmins Well documented Cons: Patching becomes difficult as platform grows Architecture dependent LNX001 WORK GOLD0 GOLD1 LNX002 LNX101 LNX102 3

4 Linux Deployment on Z Installation template based profiling (kickstart) Pros: Fast Easy to understand Flexible Well documented Architecture independent Fits with configuration management Easy to update Cons: Flashcopy based clone is faster ks0 LNX001 LNX002 LNX101 Repository ks1 LNX102 4

5 Application Lifecycle Management Red Red Hat Hat Network Network RHEL Devel Channel RHEL Devel Channel RHEL Test Channel RHEL Test Channel RHN Devel Devel Clients Systems LNX001 RHN RHN Test Clients Test Test Clients Systems RHEL Production Channel RHEL Production Channel RHN RHN Prod Clients Prod Prod Clients RHN Prod Systems RHN Prod Clients RHN Clients Prod Prod Clients Systems Repository ks0 ks1 LNX002 LNX101 LNX102 Rollback to previous versions available 5

6 Configuration Management Red Red Hat Hat Network Network Base Base Config Channel Config Channel cfg Push new config version LNX001 cfg LNX002 Workload 1 Workload 1 Config Channel Config Channel LNX001 cfg Workload 2 Workload 2 Config Channel Config Channel LNX101 LNX102 Repository ks0 ks1 LNX002 LNX101 LNX102 Rollback to previous versions available 6

7 MultiOrg: Delegation Main Org Admin Main Org Admin Organization A Organization B Org Admin Org Admin Org Admin Org Admin System Admin System Admin Channel Admin Channel Admin System Admin System Admin Channel Admin Channel Admin RHN Clients RHN Clients System Group(s) Channels System Group(s) Channels Trusted Shares 7

8 Cobbler: Provisioning Integration Red Red Hat Hat Network Network Satellite Satellite profiles Cobbler Cobbler Dynamic profile customization - variables - snippets - templates Upon IPL: - Install new profile - Reinstall profile LNX001 snippets snippets ks0 LNX002 ks1 LNX101 LNX001 LNX102 LNX002 Repository ks0 ks1 LNX101 LNX102 8

9 PXE Deployment on Z zpxe Pros: Same configuration file on all guests Disk 191 not needed for each guest All changes in management server Flexible Same known principle as PXE Fits with configuration management tools (cobbler) Easy to update Cons: New approach Limited support 9

10 In Brad's words... Next, it's time to add a system to Cobbler. Unlike traditional PXE, where unknown clients are identified by MAC address, zpxe uses the z/vm user ID to distinguish systems. For example, to add a system with z/vm user ID z01: cobbler system add --name z01 \ --hostname=z01.example.com --ip= subnet= netmask= \ --name-servers= name-servers-search=example.com:example2.com \ --gateway= kopts="layer2=0 NETTYPE=qeth PORTNO=0 cms=none \ HOSTNAME=z01.example.com IPADDR= SUBCHANNELS= , , \ MTU=1500 BROADCAST= SEARCHDNS=example.com:example2.com \ NETMASK= DNS= PORTNAME=UNASSIGNED \ DASD= ,200 GATEWAY= NETWORK= " Most of the options to cobbler system add are self explanatory network parameters. They are fully explained in the cobbler man page (see man cobbler). The --kopts option is used to specify System z specific kernel options needed by the installer. These are the same parameters found in the PARM or CONF file of a traditional installation, and in fact will be placed into a PARM file used by zpxe. For any parameters not specified with --kopts, the installer will prompt you during kickstart in the 3270 console. For a truly non-interactive installation, make sure to specify at least the parameters listed above. Now that you've added a system to Cobbler, it's time to configure zpxe, the Cobbler-specific System z PXE emulator client, which ships with Cobbler. zpxe is designed to replace PROFILE EXEC for a System z guest. Alternatively, you can simply call ZPXE EXEC from your existing PROFILE EXEC. The following example assumes the z/vm FTP server is running; however, you can also FTP from z/vm to the cobbler server. Transfer zpxe.rexx to z/vm: # cd /var/lib/cobbler # ftp zvm.example.com ==> ascii ==> put zpxe.rexx zpxe.exec ==> bye Next, logon to z/vm, and backup the current PROFILE EXEC and rename ZPXE EXEC: ==> rename profile exec a = execback = ==> rename zpxe exec a profile = = Finally, you need to create a ZPXE CONF to specify the cobbler server hostname, as well as the default disk to IPL. Use xedit to create this file. It has only two lines. ==> xedit zpxe conf a * * * Top of File * * * HOST example.server.com IPLDISK * * * End of File * * * zpxe is now configured. The client will attempt to contact the server at each logon. If there is a system record available, and it is set to be reinstalled, zpxe will download the necessary files and begin the kickstart. To schedule an install, run the following command on the cobbler server: cobbler system edit --name z01 --netboot-enabled 1 --profile RHEL-5-Server-U1-s390x 10

11 How zpxe works Simple, yet smart REXX script 1. Copy zpxe.exec from cobbler server (RHN Satellite) 2. Rename zpxe.exec to profile.exec 3. Edit new profile.exec to customize provisioning server 4. Enable distribution as s390 architecture in provisioning server 5. Add system profile in provisioning server 6. Enable network boot in provisioning server 7. Synchronize cobbler server with Satellite 11

12 How zpxe works 1.Copy zpxe.exec from cobbler server (RHN Satellite) # cd /var/lib/cobbler/loaders # ftp zvm-training.s390.bos.redhat.com ==> ascii ==> put zpxe.rexx zpxe.exec ==> bye 12

13 How zpxe works 2. Rename zpxe.exec to profile.exec Logon to z/vm, and backup the current PROFILE EXEC and rename ZPXE EXEC: ==> rename profile exec a = execback = ==> rename zpxe exec a profile = = 13

14 How zpxe works 3. Edit new zpxe conf to customize provisioning server ==> xedit zpxe conf a * * * Top of File * * * HOST satellite-sme.s390.bos.redhat.com IPLDISK * * * End of File * * * 14

15 How zpxe works 4. Enable distribution as s390 architecture in provisioning server Check for distros not having the right architecture # cobbler distro list # cobbler distro report (...) Name : ks-rhel-s390x-server-6-63 Architecture : i386 (...) Change distro to right architecture # cobbler distro edit --name ks-rhel-s390x-server arch s390 # cobbler distro report --name ks-rhel-s390x-server-6-63 Name : ks-rhel-s390x-server-6-63 Architecture : s390 (...) 15

16 How zpxe works 5. Add system profile in provisioning server cobbler system add --name train10 --hostname=train10.s390.bos.redhat.com --ip= subnet= name-servers= , name-servers-search=s390.bos.redhat.com,redhat.com --gateway= kopts="layer2=0 NETTYPE=qeth PORTNO=0 cms=none VSWITCH=1 HOSTNAME=train10.s390.bos.redhat.com IPADDR= SUBCHANNELS= , , MTU=8192 BROAD CAST= SEARCHDNS=s390.bos.redhat.com:redhat.com NETMASK= DNS= : PORTNAME=UNASSIGNED DASD= GATEWAY= " --profile rhel6u3-s390x:1:redhat 16

17 How zpxe works 6. Enable network boot in provisioning server cobbler system edit --name train10 --profile rhel6u4- s390x:1:redhat --network-enabled 1 7. Synchronize cobbler server with Satellite cobbler sync 17

18 Thank you Q&A 18