Getting Ready › Release Notes › Installation Considerations › Upgrade and Migration

Upgrade and Migration

This section describes the upgrade and migration considerations for CA AppLogic 3.8.

This section contains the following topics:

CentOS 5.8 and BFC 3.8 Upgrade

Upgrading Existing Grids

Update Appliance Boot Volume

CentOS 5.8 and BFC 3.8 Upgrade

If you want to do a fresh install of the BFC 3.8, you must confirm that CentOS 5.8 is installed on your system.

Note: If you plan to use the BFC Bare Metal Installation feature, the CentOS 5.8 installation is done automatically as part of the Bare Metal Installation process.

If you want to upgrade the BFC from 3.5.0 or earlier to 3.8, you must upgrade to CentOS 5.8. Use the following process to upgrade from CentOS 5.5 to CentOS 5.8.

Follow these steps to upgrade CentOS with a locally configured yum repository:

1. Download the CentOS 5.8 images from www.centos.org. The download should contain two DVD iso files (DVD1 and DVD2). Copy the downloaded files to the BFC machine.
2. Shut down the BFC service (service bfc stop)
3. On the BFC machine where you want to upgrade CentOS from 5.5 to 5.8, run the following command to verify that CentOS 5.5 is installed and ready for upgrade:

   rpm -import /mnt/CentOS/5.5/RPM-GPG-KEY-CentOS-5
   

   Note: This step assumes your current CentOS 5.5 yum configuration points to /mnt/CentOS/5.5/ as the yum repository.

4. On the BFC machine, mount the 2 DVD iso files separately on two directories:

   # mount -r -o loop CentOS5.8-DVD1.iso <dir1>
   

   # mount -r -o loop CentOS5.8-DVD2.iso <dir2>
   

5. Create a directory /mnt/centos58/ and copy the contents of the two directories (dir1 and dir2) to /mnt/centos58/.
6. Update the "baseurl=" parameter of the /etc/yum.conf:

   baseurl=file:///mnt/centos58/
   

7. Run the following YUM command:

   yum update
   

8. Reboot the BFC node for the updated packages (e.g. the kernel package) to get persistent.
9. Run the following YUM command to list the CentOS 5.8 packages:

   yum list.
   

Follow these steps to upgrade CentOS with the online yum repository

1. Verify that /etc/yum.repos.d/ directory exists.
2. Check whether the BFC machine has internet access (use the wget command to get any file from internet).
3. Run yum update to update the current installed CentOS 5.5 packages to CentOS 5.8 version).
4. Reboot the BFC node for the updated packages (e.g. the kernel package) to get persistent.
5. Run yum list to list the CentOS 5.8 packages.

   Note: For further details refer to your CentOS manuals for yum configuration.

Upgrading Existing Grids

Upgrades from existing CA AppLogic Version 3.0, 3.1, 3.5, and 3.7 grids to this release (3.8) are fully supported for Xen-based grids. For ESX-based grids, upgrade from CA AppLogic 3.0, 3.1, 3.5, and 3.7 to this release is not supported.

Upgrades are not supported from any CA AppLogic release prior to 3.0, such as 2.9 and 2.8. To migrate your older CA AppLogic grid to the latest release, you must install CA AppLogic 3.8 and migrate your custom applications and catalogs from your old grid to your new 3.8 grid.

Note: To upgrade Xen-based 3.x grids, refer to the BFC documentation.

CA AppLogic 3.8 does support appliances and applications that were created with older CA AppLogic releases. Depending upon the type of appliance and the kind of hypervisor that is needed, you may need to update the appliance before using it on a 3.8 grid.

Note: Solaris-based appliances are no longer supported in CA AppLogic 3.8.

Update Appliance Boot Volume

Follow these steps to update an appliance's boot volume (Linux-based) to work on Xen servers within a 3.x grid.

1. Ensure your appliance is using the updated 3.x ADL descriptor format.
2. Ensure the following statements are true about the appliance being converted:
   • The appliance has grub installed.
   • If grub uses /boot/grub/menu.lst for its configuration (this is the case with Ubuntu and Debian), then grub should not be updated after running this procedure as it reverts to the default grub configuration which makes the appliance unbootable. CentOS-based appliances are not affected.
3. Import the appliance into the 3.x grid using the class import command (or import your custom catalogs or applications as needed). Import anything that contains appliances that you want to update.
4. If the appliance is not a singleton, create a new application, drag an instance of your appliance into the application, and branch the appliance. If the appliance is a singleton, edit the application in the infrastructure editor.
5. Create an empty partitioned boot volume. The size should be roughly set to the size of the existing boot volume (unless a different size is needed) plus the size needed for a new kernel (usually about 50MB).
   • vol create my-app:boot_vol par1.size=150M
6. Copy the old boot volume's data to the partitioned volume that was created in the previous step.
   • vol copy my-app:LUX5.boot my-app:boot_vol%par1 --fscpy
7. Replace the old boot volume with the new partitioned volume.
   • vol copy my-app:boot_vol my-app:LUX5.boot --overwrite --force
   • vol destroy my-app:boot_vol -f
8. Manage the boot volume.
   • vol manage _GLOBAL_RO:apk_linux my-app:LUX5.boot -rw
9. Execute the following commands in the filer vol manage console to install a CentOS5 32-bit kernel (the same one that the Linux Filer uses). If you want a different kernel, copy it instead and update the grub configuration with the proper names. The boot volume is mounted under /mnt/vol2/par1.
   • cp -a /boot/{initrd-2.6.18-238.9.1.el5PAE.img,vmlinuz-2.6.18-238.9.1.el5PAE} /mnt/vol2/par1/boot/
   • cp -a /lib/modules/2.6.18-238.9.1.el5PAE /mnt/vol2/par1/lib/modules/
   • sed -i -e 's#/dev/hda2#/dev/hdb#'  -e 's#/dev/hda3#/dev/hdc#' -e 's#/dev/hda4#/dev/hdd#'  /mnt/vol2/par1/etc/fstab
   • tar -xvf /mnt/vol/apk-2.0.36-linux-rh.tar.gz -C /mnt/vol2/par1 (replace with the APK for your distro; verify you have the latest APK from the CA AppLogic 3.x release)
   • cd  /mnt/vol2/par1
   • tmp/apk-install
   • sed -i -e 's/tty1/console/' /mnt/vol2/par1/etc/inittab

     cat << EOF > /mnt/vol2/par1/boot/grub/grub.conf
     default 0
     timeout 1
     
     title CA AppLogic Appliance
             root    (hd0,0)
             kernel  /boot/vmlinuz-2.6.18-238.9.1.el5PAE root=/dev/hda1 ro console=tty0 console=ttyS0,38400n8
             initrd  /boot/initrd-2.6.18-238.9.1.el5PAE.img
     EOF
     
     fs=$(grep "^/dev/sdc1" /proc/mounts 2>/dev/null|awk '{print $3}')
     [ "$fs" == "ext3" -o "$fs" == "ext2" ] && fs=e2fs
     
     out=$(grub --batch --no-floppy 2>&1 <<EOF   
     device (hd0) /dev/sdc
     root (hd0,0)
     embed /boot/grub/${fs}_stage1_5 (hd0)
     EOF
     )
     
     sectors=$(grep 'sectors are embedded' <<< "$out" |grep -Eo '[[:digit:]]+')
     
     grub --batch --no-floppy <<EOF   
     device (hd0) /dev/sdc
     root (hd0,0)
     install --stage2=/mnt/vol2/par1/boot/grub/stage2 /boot/grub/stage1 (hd0) (hd0)1+${sectors} p (hd0,0)/boot/grub/stage2 (hd0,0)/boot/grub/grub.conf
     quit
     EOF
     

     Important! When vol managing the boot volume, update the fstab (/mnt/vol2/par1/etc/fstab) to mark any read-only volumes as read only. If this is not done, the appliance will fail to boot.

10. Exit the filer console
11. In the infrastructure editor, edit the class and change the following:
    1. Change the device schema for your appliance to use /dev/hdX.
    2. Update the device names for the volumes as follows:
       • /dev/hda1 to /dev/hda
       • /dev/hda2 to /dev/hdb
       • /dev/hda3 to /dev/hdc
       • /dev/hda4 to /dev/hdd
12. Save the application.
13. Start the appliance to verify that it is operational.
14. If the appliance was from a catalog, move the appliance back into the catalog.

    The appliance is now updated to boot on Xen servers within a CA AppLogic grid.