Chapter 7. Getting Started with Boot from Volume

Size: px

Start display at page:

Download "Chapter 7. Getting Started with Boot from Volume"

Shannon Underwood
6 years ago
Views:

1 Chapter 7. Getting Started with Boot from Volume This chapter discusses creating a bootable volume from an existing minidisk, cloning a volume from an existing volume, and booting a virtual server instance from a volume. After creating a bootable volume, the volume is on a persistent disk. When the virtual server using that volume is deleted, by default the volume is not destroyed and can be used in subsequent virtual server instances. Note: Resizing/migration of volume-based instances is not supported. The following Linux distributions are supported for the boot from volume function: v RHEL 6 see Installing Red Hat Linux on page 97. v RHEL 7 see Installing Red Hat Linux on page 97. v SLES 11 see Installing SLES 11 on page 102. v SLES 12 see Installing SLES 12 on page 106. v Ubuntu see Installing Ubuntu on page 112. The steps for other versions/releases of RHEL, SLES, and Ubuntu may be different than what is documented here. Please consult you Linux documentation for instructions related to migrating a Linux system's root disk to a SCSI volume. Creating a Bootable Volume The process in this section creates a basic Linux system, but it will not contain any middleware that was part of the original Linux system. If your original Linux system had middleware installed on it, you can add the middleware to the system after migrating the system to a volume. Pre-Installation Tasks This section discusses the pre-installation tasks you must perform before creating a bootable volume. Note: On a CMA system, issue the command source $HOME/openrc to set OpenStack-related environment variables before you issue any OpenStack commands. 1. For Red Hat and SLES, locate an NFS server that will be accessible to the system you want to migrate from a minidisk to a volume. The NFS server must contain the Linux distribution media for the operating system being migrated. Subsequent steps will refer to the media being on an NFS server. For Ubuntu, subsequent steps show the media being on an FTP server, although downloading files using HTTP and HTTPS is also supported. 2. You must provision a virtual server with OpenStack that contains the Linux image which you intend to migrate to the bootable volume. This defines the system to OpenStack so that subsequent commands can utilize OpenStack functions to add a volume to the system. In this virtual server instance, the root volume resides on an ephemeral disk, ECKD or FBA minidisk. The target Linux system should follow the same requirements and restrictions which are imposed on a Linux system located on ECKD or FBA disks. See Image Requirements on page 69 for more information. Once the virtual server is known to OpenStack, you will need to obtain the OpenStack ID for that virtual server instance. Use the nova list command to get the ID: Copyright IBM Corp. 2014,

2 nova list ID Name Status Task State Power State Networks c-aaf9-42b759de2f3b hych0035 ACTIVE - Running mgt= Estimate the size of the disk you will need for the bootable volume. The size of the disk depends on the version of Linux you will run and on the packages you want to install on your system. A minimum of 3 GB is recommended. If the system you intend to create is similar in size to the one you are already using, determine the size of the disk that contains the root directory. You can use the Linux df -h filenode command to display total capacity as well as the used and available capacity. For example: df -h / Filesystem Size Used Avail Use% Mounted on /dev/dasda1 3.0G 1.6G 1.3G 58% / df -h /root Filesystem Size Used Avail Use% Mounted on /dev/dasda1 3.0G 1.6G 1.3G 58% / 4. For the bootable volume which will be created, on the target OpenStack virtual server, a persistent disk (volume) must be added with enough capacity to hold the Linux system. Locate or allocate a cinder volume with enough capacity to hold the Linux system that you want to use. Once you have located a suitable volume in cinder, you will need to know the volume ID for subsequent commands. You can issue the cinder list command to list the volumes in cinder and their IDs. For example: cinder list ID Status Display Name Size Volume Type Bootable Attached to fddccbf ad9b d3f431 available None 3 None false The Size column indicates the volume is 3 GB, and the ID will be used in the next step. 5. Attach the volume to the virtual server instance with the nova volume-attach command: nova volume-attach instance_id volume_id where: instance_id The instance identifier of the virtual server instance. volume_id The identifier of the volume. For example: nova volume-attach c-aaf9-42b759de2f3b fddccbf ad9b d3f Property Value device /dev/sdb id fddccbf ad9b d3f431 serverid c-aaf9-42b759de2f3b volumeid fddccbf ad9b d3f cinder list ID Status Display Name Size Volume Type Bootable Attached to fddccbf ad9b d3f431 in-use None 3 None false c-aaf9-42b759de2f3b z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

3 Note that the volume is now shown attached to the target system (see the "Attached to" column). 6. SSH into the Linux server and run the following command to obtain the FCP device, WWPN, and LUN. lszfcp -D The output from this command is similar to the following: 0.0.1fb2/0x /0x :0:4:34 The following values are shown in this example: FCP device 1fb2 WWPN LUN For RedHat, copy the kernel.img and initrd.img files into the Linux server location, and place the files in the /boot directory. The image files are located in the /images directory of the distribution media (for example, in /nfs/rhel6.5/dvd1/images/). For SLES, copy the initrd (with no file suffix) and vmrdr.ikr files into the Linux server location, and place the files in the /boot directory. The image files are located in the boot/s390x directory of the distribution media (for example, /nfs/sles11sp3gm/dvd1/boot/s390x/). For Ubuntu, copy the initrd.ubuntu and kernel.ubuntu files into the Linux server location, and place the files in the /boot directory. The image files are located in the /boot directory of the distribution media (for example, in /ftp/ubuntu16/dvd/boot/). 8. Run the zipl --dry-run command to gather information about the system, such as the name of the default Linux system. This command does not modify IPL records. It must be issued before making any modification to the /etc/zipl.conf file. (These modifications are shown in Step 9.) For example: zipl --dry-run Using config file /etc/zipl.conf Starting dry-run, target device contents will NOT be modified Building bootmap in /boot/ Building menu rh-automatic-menu Adding 1: IPL section linux el6.s390x (default) Preparing boot device: dasda (0100). Done. The entry linux el6.s390, which is the default Linux system, is determined by the [defaultboot] section. 9. Add the following configuration items to the /etc/zipl.conf file. For RedHat: [linux] image=/boot/kernel.img ramdisk=/boot/initrd.img parameters="root=/dev/ram0 rd_dasd= vnc ro ramdisk_size=40000" For SLES: [linux] image=/boot/vmrdr.ikr ramdisk=/boot/initrd target = /boot/zipl parameters="root=/dev/ram0 rd_dasd= vnc ro ramdisk_size=40000" For Ubuntu: Chapter 7. Getting Started with Boot from Volume 95

4 [linux] target = /boot image = /boot/kernel.ubuntu ramdisk = /boot/initrd.ubuntu parameters="root=/dev/ram0 rd_dasd= vnc ro ramdisk_size=40000" Add the [defaultboot] section (if it is not already present) and specify default=linux: [defaultboot] default=linux (The above command defines the default Linux system to be "linux". Previously, the default, as well as the original boot system, was "linux el6.s390". Issue the command /sbin/zipl to allow the new configuration to take effect: zipl Using config file /etc/zipl.conf Building bootmap in /boot/ Building menu rh-automatic-menu Adding 1: IPL section linux (default) Adding 2: IPL section linux e16.s390x Preparing boot device: dasda (0100). Done. Record the number in the menu associated with the original Linux system, and record the number of the boot device. They will be used in subsequent steps. In this example, the number of the original Linux is 2, and the number of the boot device is Before you can boot a new instance, you have to set the volume to be bootable using the cinder set-bootable command: cinder set-bootable volume_id true where: volume_id is the identifier of the volume. You can obtain this value by using the cinder list command. 11. Determine the IP configuration for the Linux system you are about to create on a volume. If you will use the same IP address as the system you are currently using, you can obtain its IP configuration information with the ifconfig command. To use a different IP address, contact your system administrator to get the IP address, subnet mask, gateway, DNS server and MAC address that you will be using. 12. Issue the Linux shutdown command to cause the target Linux server to gracefully shutdown: shutdown now Note: If the virtual server is periodically disconnected or powered off when you perform the next set of volume preparation steps, it may be because the compute service is doing periodic status synchronization work. If this is a problem, you can stop the compute service temporarily if necessary. Installing Linux This section provides an overview of installing Red Hat 6 Linux, Red Hat Linux 7, SUSE 11 Linux, SUSE 12 Linux, and Ubuntu Linux. For more detailed information on installing these releases and later Linux releases, refer to the following URLs or other appropriate Linux documentation: For Red Hat: z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

5 For SUSE: For Ubuntu: Installing Red Hat Linux 1> The instructions in this section apply to RHEL 6 and RHEL Log on to the z/vm virtual machine running the virtual server that you want to migrate. 2. Issue the following command: cp ipl 0100 where 0100 is the boot device shown in Step 9 on page Configure the Linux system network in order to make it accessible from a remote VNC client. Contact your network administrator to obtain the appropriate values. The following are properties you should specify: Layer mode must be layer2 (required) MAC must be a unique MAC address associated with this interface IPv4 must be an IPv4 address associated with this interface Netmask must be a netmask address associated with this interface Gateway must be a gateway IP address associated with this interface DNS server must be a DNS server IP address associated with this interface 4. On the z/vm console, issue the following command: cp term more 0 0 Without this command, the process will pause when the z/vm screen shows "More..." indicating that the system is waiting for you to manually clear the screen. In this case the VNC client will lose its connection and will not be able to establish a new connection until the process resumes. 5. Issue the following command on your SSH client to connect to the server as the "install" user to start the installation: ssh install@x.x.x.x where x.x.x.x is the IPv4 address you specified in Step 3. The installation process is similar to a typical Linux installation. In this example an NFS server is used the source of installation. On the "Installation Method" screen, select "NFS directory" as shown in Figure 32 on page 98. Chapter 7. Getting Started with Boot from Volume 97

Enterprise Linux directory" field. You can ignore the "NFS mount options" because these options are filled in by the command in most cases. Figure 33.

6 Figure 32. Installation Method Screen 6. On the "NFS Setup" screen, shown in Figure 33, specify the IP address of your NFS server in the "NFS server name" field, and specify the absolute path of the install directory in the "Red Hat Enterprise Linux directory" field. You can ignore the "NFS mount options" because these options are filled in by the command in most cases. Figure 33. NSF Setup Screen After system installer loads the necessary files from the NFS server, you will receive a message similar to the following: 03:33:57 Please manually connect your vnc client to :1 to begin the install. 03:33:57 Starting graphical installation. 7. Connect your VNC client to the server and continue the installation process. 8. The storage device which will contain the system must be specified to the FCP device which is attached to the server in Step 5 on page 94. Select "Specialized Storage Device" as shown in Figure 34 on page 99, and then select the "Next" button. 98 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

and then selecting "Add ZFCP LUN" followed by clicking on the "Add Drive" button." Figure 35.

7 Figure 34. Specifying the Storage Device a. Add the volume as a system storage device as shown in Figure 35 by selecting the "Add Advanced Target" button and then selecting "Add ZFCP LUN" followed by clicking on the "Add Drive" button." Figure 35. Adding the Volume as a System Storage Device b. Specify the volume information as shown in Figure 36 on page 100 and click on the "Add" button. Chapter 7. Getting Started with Boot from Volume 99

Figure 36. Specify the Volume Information c. Verify the volume was added by selecting the "Other SAN Devices" tab and checking that the added device is in the list.

8 Figure 36. Specify the Volume Information c. Verify the volume was added by selecting the "Other SAN Devices" tab and checking that the added device is in the list. Figure 37 on page 101 shows the that volume was successfully added. Then select the "Next" button to move to the next screen. 100 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

9 Figure 37. Results of Adding a Volume Successfully d. On the Type of Installation screen, which is shown in Figure 38 on page 102, check the "Review and modify partitioning layout" checkbox to use the standard partitioning layout. The "Create Storage" screen will appear. Select the "Standard Partition" button. Then select the "Next" button to move to the next screen. Chapter 7. Getting Started with Boot from Volume 101

Figure 38. Type of Installation Screen e. Make sure the volume uses standard partitioning layout by verifying that no LVM volume groups are listed for the device.

10 Figure 38. Type of Installation Screen e. Make sure the volume uses standard partitioning layout by verifying that no LVM volume groups are listed for the device. Installing SUSE Linux This section describes installing SLES 11 and SLES 12. Installing SLES 11: 1. Log on to the z/vm virtual machine running the virtual server that you want to migrate. 2. Issue the following command: cp ipl 0100 where 0100 is the boot device shown in Step 9 on page Configure the network to make it accessible from a remote VNC client. Contact your network administrator to obtain the appropriate values. The following are values you must specify: Source medium must be network Network protocol must be NFS OSA device must be Ethernet Physical medium must be Ethernet 102 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

11 Layer mode must be layer2 IPv4 address, IPv4 netmask, IPv4 gateway, and display type must be VNC. After you enter the correct values, the system installer will load the necessary files from your NFS server. You can then connect to the server with your VNC client. 4. Connect to the server with your VNC client to start the installation. The installation process is similar to a typical Linux installation. 5. On the Disk Activation screen, select "Configure ZFCP Disks" as shown in Figure 39. Then press the "Next" button to move to the next screen. Figure 39. Preparing the Volume 6. Specify the volume information as shown in Figure 40 on page 104 and select the "Next" button. Chapter 7. Getting Started with Boot from Volume 103

12 Figure 40. Specifying Volume information 7. On the subsequent screen, select the volume, shown as a SCSI disk, then press the "Next" button to move to the next screen. 8. On the Installation Settings screen, select the "Change" button to access the pulldown menu, and then select "Partitioning" to specify standard partitioning rather than LVM partitioning, as shown in Figure 41 on page 105. You will then see the screen shown in Figure 42 on page z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

13 Figure 41. Installation Settings Screen: Selecting the Change Partitioning Button 9. On the Preparing Hard Disk screen, verify that LVM partitioning is not selected in the "Proposal settings" section, as shown in Figure 42 on page 106. Then select the "Accept" button. Chapter 7. Getting Started with Boot from Volume 105

14 Figure 42. Verifying that LVM Partitioning is Not Selected 10. On the Installation Settings screen, shown in Figure 41 on page 105, select "Install". Installing SLES 12: 1. In Installing SLES 11 on page 102, follow Step 1 on page 102 through Step 7 on page On the Suggested Partitioning screen, shown in Figure 43 on page 107, select the Expert Partitioner button to customize the partition. 106 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

15 Figure 43. Suggested Partitioning Screen 3. You will then see Figure 44 on page 108. The SLES installer by default generates a recommended partitioning plan for you, which you can tailor as needed. Chapter 7. Getting Started with Boot from Volume 107

16 Figure 44. Expert Partitioner Screen with Sample Partitioning Plan 4. To edit a partition, select the partition name, as shown in Figure 45 on page 109. Then select the Edit button. 108 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

17 Figure 45. Editing a Partition 5. You will then see the Edit Partition screen, as shown in Figure 46 on page 110. Select the Fstab Options button. Chapter 7. Getting Started with Boot from Volume 109

18 Figure 46. Edit Partition Screen 6. You will then see the Fstab Options screen, as shown in Figure 47 on page 111. In the "Mount in /etc/fstab by" section, you must select the UUID radio button. Otherwise the system could fail to reboot after the installation. Then select OK. 110 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

19 Figure 47. Fstab Options Screen 7. Continue the installation process by selecting your time zone and setting an initial password. You will then see the Installation Settings screen, as shown in Figure 48 on page 112. Disable the firewall and Chapter 7. Getting Started with Boot from Volume 111

enable SSH, so that you can SSH onto the instance after the installation. Then select Install. Figure 48. Installation Settings Screen Installing Ubuntu 16.

Issue the following command on your SSH client to connect to the server as the "installer" user to start the installation: ssh installer@x.

20 enable SSH, so that you can SSH onto the instance after the installation. Then select Install. Figure 48. Installation Settings Screen Installing Ubuntu The instructions in this section apply to Ubuntu In Installing Red Hat Linux on page 97, follow Step 1 on page 97 through Step 4 on page Issue the following command on your SSH client to connect to the server as the "installer" user to start the installation: ssh installer@x.x.x.x where x.x.x.x is the IPv4 address you specified in Step 3 on page 97. You will see Figure 49. Select Start installer (expert mode) from the menu to begin the installation. Figure 49. Start Installation Screen 112 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

21 3. You will then see the Ubuntu installer main menu. Select "Choose language," as shown in Figure 50. Figure 50. Ubuntu Installer Main Menu Choose Language Follow the instructions on next set of screens to: v Select your language v Select your location (region) v Configure your locale. After making your selections you will return to the main menu. 4. From the main menu, select "Choose a mirror of the Ubuntu archive," as shown in Figure 51 on page 114, to choose an installation source. Chapter 7. Getting Started with Boot from Volume 113

You will then see Figure 53 on page 115.

22 Figure 51. Ubuntu Installer Main Menu Choose a Mirror 5. You will then see Figure 52. Select the method you want to use to download files. The steps that follow use FTP as the protocol; these steps vary slightly if you choose HTTP or HTTPS. Figure 52. Choose Protocol Screen 6. You will then see Figure 53 on page 115. In the "Ubuntu archive mirror hostname" field, specify the IP address or hostname from which the Ubuntu code will be downloaded. Then select Continue to move to the next screen. 114 z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

Figure 53. Choose Mirror Hostname Screen 7. You will then see Figure 54.

field. Then select Continue to move to the next screen. Figure 54.

If necessary, fill in the "FTP proxy information field.

23 Figure 53. Choose Mirror Hostname Screen 7. You will then see Figure 54. Specify the directory path of the Ubuntu archive in the Ubuntu archive mirror directory field. Then select Continue to move to the next screen. Figure 54. Choose Mirror Directory Screen 8. You will then see Figure 55. If necessary, fill in the "FTP proxy information field. You can ignore this field if you don t need a proxy. Then select Continue to return to the main menu. Figure 55. Specify FTP Proxy Screen Chapter 7. Getting Started with Boot from Volume 115

9. From the main menu, select "Download installer components," as shown in Figure 56. Figure 56. Ubuntu Installer Main Menu Download Installer Components The installer will download the necessary files.

24 9. From the main menu, select "Download installer components," as shown in Figure 56. Figure 56. Ubuntu Installer Main Menu Download Installer Components The installer will download the necessary files. This can take several minutes or more, depending on the capabilities of your network. When you see the list of components, select all the components that you want to load. Then select Continue. It can take several more minutes to load the additional components you selected. Then you will return to the main menu. 10. From the main menu, select "Set up users and passwords," as shown in Figure 57 on page z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

Figure 57. Ubuntu Installer Main Menu Set Up Users and Passwords Follow the instructions on next set of screens to: v Enable shadow passwords (recommended).

25 Figure 57. Ubuntu Installer Main Menu Set Up Users and Passwords Follow the instructions on next set of screens to: v Enable shadow passwords (recommended). v Enable the login as root capability (required in order for the instance to boot up). v Specify an account (consisting of the real name, user name, and password) for the user that will have "sudo as root" privilege. v Specify whether you want your home directory configured for encryption. After making your selections you will return to the main menu. 11. From the main menu, select "Configure the clock," as shown in Figure 58 on page 118 Chapter 7. Getting Started with Boot from Volume 117

Figure 58. Ubuntu Installer Main Menu Configure the Clock The installer will configure the clock based on your current location. If this is the time zone you want to use, select Yes.

26 Figure 58. Ubuntu Installer Main Menu Configure the Clock The installer will configure the clock based on your current location. If this is the time zone you want to use, select Yes. You will then return to the main menu. 12. For Ubuntu boot from volume, the target device must be an FCP. Skip the "Configure direct access storage devices (DASD)" choice in the main menu, and select "Activate FCP devices for installation," as shown in Figure 59 on page z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

27 Figure 59. Ubuntu Installer Main Menu Activate FCP Devices Follow the instructions on next set of screens to: v Select the FCP devices you want to activate from a list of available devices. v Select the LUNs that are available, or select "Add LUN" to add one or more LUNs. v Specify the world wide port name (WWPN) of the target port and the LUN to attach to a SCSI disk. When you are done, select "Finish" to return to the main menu. 13. Skip the "Detect disks" choice in the main menu and select "Partition disks," as shown in Figure 60 on page 120 Chapter 7. Getting Started with Boot from Volume 119

Figure 60. Ubuntu Installer Main Menu Partition Disks Follow the instructions on next set of screens to: v Select guided partitioning (recommended) or manual partitioning.

28 Figure 60. Ubuntu Installer Main Menu Partition Disks Follow the instructions on next set of screens to: v Select guided partitioning (recommended) or manual partitioning. In most cases, you should select "Guided - use entire disk." v Select the disk to be partitioned, and confirm your selection. Do not set up a logical volume manager (LVM) during this step. Setting up an LVM can prevent the virtual server instance from booting up. When you are done making selections, you will return to the main menu. 14. From the main menu, select "Install the system," as shown in Figure 61 on page z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

29 Figure 61. Ubuntu Installer Main Menu Install the System Most installations can use the default installation options. Follow the instructions on the next set of screens to: v Select a "normal" installation. v Select a "linux-generic" kernel. v Select "generic: include all available drivers" to use a generic initrd. When you are done making selections, you will return to the main menu. 15. In order for the system to boot up, you must install the ZIPL boot loader. From the main menu, select "Install the ZIPL boot loader on a hard disk," as shown in Figure 62 on page 122 Chapter 7. Getting Started with Boot from Volume 121

30 Figure 62. Ubuntu Installer Main Menu Install the ZIPL Loader After the ZIPL loader installs, you will return to the main menu. 16. From the main menu, select "Finish the installation," as shown in Figure 63 on page z/vm V6.4 Enabling z/vm for OpenStack (Support for OpenStack Newton Release)

Figure 63. Ubuntu Installer Main Menu Finish the Installation Post-Installation Tasks This section discusses the tasks you must perform after you install a Red Hat or SLES system.

31 Figure 63. Ubuntu Installer Main Menu Finish the Installation Post-Installation Tasks This section discusses the tasks you must perform after you install a Red Hat or SLES system. Note: On a CMA system, issue the command source $HOME/openrc to set OpenStack-related environment variables before you issue any OpenStack commands. 1. Depending on the Linux distribution you are using, the installation process could reboot the system automatically for you after the installation completes successfully. In this case you can skip this step and go to Step 2 on page 124. Otherwise, log on to the zvm virtual machine in which the target Linux system is running, and issue the CP SET LOADDEV command to reboot the newly installed system: CP SET LOADDEV PORTNAME wwpn LUN lun where: Chapter 7. Getting Started with Boot from Volume 123

Building Customized Linux Kernels A live demonstration. Mark Post August 17, 2004 Session # 9280

Building Customized Linux Kernels A live demonstration Mark Post August 17, 2004 Session # 9280 Documentation The Linux Documentation Project http://www.tldp.org/ Look for the Kernel HOWTO http://www.tldp.org/howto/kernel-howto/