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

Installation, Upgrade, and Migration

This section describes how to install, upgrade, and migrate CA AppLogic® 3.5.

This section contains the following topics:

CentOS 5.8 and BFC 3.5.2 Upgrade

Upgrade From 3.0 or 3.1 - Check Version Download Location

BFC Replaces ALD

Upgrading Existing Grids

Upgrading New Windows APK

CentOS 5.8 and BFC 3.5.2 Upgrade

If you want to do a fresh install of the BFC 3.5.2, 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.5.2, 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.

Upgrade From 3.0 or 3.1 - Check Version Download Location

The following note only applies to users upgrading from version 3.0 or 3.1 to 3.5.

Before you upgrade CA AppLogic® 3.0 or 3.1 to CA AppLogic® 3.5, confirm that your version download directory is not set to /opt/bfc. The uninstaller that is provided with version 3.0 and 3.1 removes all files from the BFC install directory. If the 3.5 upgrade does not succeed for some reason and you use the 3.0/3.1 fallback to recover, all files in opt/bfc are removed.

This is not an issue if you do not use opt/bfc as your version download directory, and is not an issue for new 3.5 installations. Follow these steps to check your version download location.

1. Start the BFC, open the Administration page, and click the Versions tab.
2. Check the CA AppLogic® Version Downloads Directory field. If the directory path includes /opt/bfc, change it to another location. The directory must have read/write permissions for the bfcadmin user.
3. Move the current version download files to the new directory location. For example, enter the following command on the BFC machine to move downloaded files from /opt/bfc/downloads to /var/applogic/downloads:

   mv /opt/bfc/downloads /var/applogic/downloads 
   

BFC Replaces ALD

ALD is no longer used to install and upgrade grids. Taking the place of ALD is the Backbone Fabric Controller (BFC). BFC contains a simple-to-use web-based GUI application that you use to create and manage all of your CA AppLogic® grids within a single backbone. BFC automatically downloads the latest CA AppLogic® releases and hotfixes.

The BFC documentation includes information about how to download/install BFC and how to use it to manage your CA AppLogic® grids.

Upgrading Existing Grids

This section contains the following topics:

Determine Changes for Your Applications

Update Appliance Descriptors

Update Appliance Boot Volume

Upgrades from existing CA AppLogic® Version 3.0, 3.1, 3.5, and 3.7 grids to this release (3.5) 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.5 and migrate your custom applications and catalogs from your old grid to your new 3.5 grid.

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

CA AppLogic® 3.5 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.5 grid.

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

Determine Changes for Your Applications

Follow the guidelines below to determine what kind of modifications (if any) are needed to make your applications run on a 3.5 grid:

• If you move appliances from a 3.0/3.1/3.5 grid to a 3.5 grid (Xen or ESX-based), everything works as-is without any modifications.
• If moving appliances from a 2.9 grid (or prior version) to a 3.5 Xen-based grid, everything will work as-is w/o any modifications
• If you move Windows-based appliances from a 2.9 grid (or prior) to a 3.5 ESX-based grid, the descriptors need to be updated to the new 3.x format (see below), the latest APK (Appliance Kit) needs to be re-installed in the appliance and vmware-tools should be installed in the appliance too (vmware-tools can be downloaded from VMware's website)
• If you move Linux-based appliances from a 2.9 grid (or prior) to a 3.5 ESX-based grid, the descriptors need to be updated to the new 3.x format (see below) and the boot disk needs to be updated to support ESX (see below)
• If any appliance has more than 10 terminals and the intent is to run the appliance on an ESX-based grid, the descriptors need to be updated to use the new 3.x format (see below) and the latest APK (Appliance Kit) needs to be re-installed in the appliance

Update Appliance Descriptors

Follow these steps to update an appliance descriptor to use the new 3.x format.

Note: Perform this procedure if you have appliances from older CA AppLogic® releases that you want to run on the ESX hypervisor.

Follow these steps:

1. 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 to use the new 3.x ADL descriptor format.
2. 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.
3. Modify the appliance class and under the Advanced section of the General tab, select the appropriate virtualization modes based on the hypervisors are compatible with the appliance (more than one mode may be selected as long as the appliance supports all of the selected modes).
4. Select the Options button next to the virtualization modes and do the following:
   1. Select the VMware virtualization mode.
   2. In the options field, add a new setting named esx_os_name where the value is one of the following:
      • Microsoft Windows Server 2003, Datacenter Edition (64-bit): winNetDatacenter-64
      • Microsoft Windows Server 2003, Enterprise Edition (64-bit): winNetEnterprise-64
      • Microsoft Windows Server 2003, Standard Edition (64-bit): winNetStandard-64
      • Microsoft Windows Server 2003, Datacenter Edition (32-bit): winNetDatacenter
      • Microsoft Windows Server 2003, Enterprise Edition (32-bit): winNetEnterprise
      • Microsoft Windows Server 2003, Standard Edition (32-bit): winNetStandard
      • Microsoft Windows Server 2003, Web Edition: winNetWeb
      • Microsoft Windows Server 2008 R2 (64-bit): windows7srv-64
      • Microsoft Windows Server 2008 (32-bit): longhorn
      • Microsoft Windows 7 (32-bit): windows7
      • Microsoft Windows 8 (32-bit/64-bit): windows7
      • Microsoft Windows 7 (64-bit): windows7-64
      • Linux (32-bit): rhel6
      • Linux (64-bit): rhel6-64
      • Other (32-bit): other
      • Other (64-bit): other-64

      For example, if the appliance is based on Microsoft Windows Server 2008 (32-bit), update the options field with the setting: esx_os_name=longhorn.

5. Save the application.
6. Start the appliance to verify that it is operational.
7. If the appliance was from a catalog, move the appliance back into the catalog.

   The appliance is now updated to use the new 3.x ADL descriptor format.

Update Appliance Boot Volume

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

1. Ensure your appliance is using the updated 3.x ADL descriptor format as specified in the previous section above.
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 will revert to the default grub configuration which will make 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) + 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 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.

1. Exit the filer console
2. 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 -> /dev/hda
      • /dev/hda2 -> /dev/hdb
      • /dev/hda3 -> /dev/hdc
      • /dev/hda4 -> /dev/hdd
3. Save the application.
4. Start the appliance to verify that it is operational.
5. If the appliance was from a catalog, move the appliance back into the catalog.

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

Note: The entire catalog and all applications that are included with CA AppLogic® 3.x have been updated to work on either Xen or ESX. You may choose to re-base your custom appliances on the CA AppLogic® 3.x appliances to obtain the ability to run them on either Xen or ESX. In this case there is no need to follow the instructions above.

Upgrading New Windows APK

If you participated in the beta, you can upgrade the new Windows APK from the version included with beta (APK version 3.5.4) to version included with GA (APK version 3.5.14).

To upgrade the Windows_APK.*.msi, remove the following directory links before installing the GA version:

• /lib/applogic
• /etc/sysconfig
• /var/run/applogic