Flexiant Cloud Orchestrator Documentation v5.0.15
Page tree
Skip to end of metadata
Go to start of metadata

This page sets out the procedure to update a version with minor release 2.0 to major release 3.0.

You may wish to consider using our professional services department to carry out this upgrade.

Do not commence this upgrade procedure until you have read through the entire procedure, and are confident that you have the appropriate skills to carry it out.

A. Preparatory work

  1. Ensure you are running the latest 2.0 release. If not, follow procedure to update between minor releases.

    Upgrades from versions prior to 2.0.4 will not work

  2. Ensure you have a complete system backup prior to the upgrade.

  3. Your system management stack will not run during the upgrade process; ensure you provide an appropriate maintenance window.

  4. Ensure local.cfg and all branding files are backed up prior to upgrade.

  5. Ensure all system backups are up to date.

B. Upgrading the Operating System of each management stack

FCO v2.0 uses Ubuntu Lucid 10.04 LTS. FCO v.3.0 requires Ubuntu Precise 12.04 LTS. Therefore as a preliminary step, you must upgrade the operating system on each management stack.

  1. Stop all FCO services

    run-parts -a stop --regex '^(extility|apache)' /etc/init.d

    Ensure you are logged in via ssh or at the console to perform the above operation. VARs with remote-support access to their clients should not use the above command.



  2. Follow Ubuntu's procedure to upgrade the from Lucid to Precise. You can either read the procedure here (remembering you have a server not a desktop install) or follow the abbreviated procedure set out below:

    1. Ensure your OS has an up-to-date version of Lucid before starting

      aptitude update && aptitude upgrade

    2. Install update-manager-core if it is not already installed:

      aptitude install update-manager-core

    3. Work around a bug in Ubuntu that can (without this line) cause bind9 to use 100% CPU on an upgrade from Lucid to Precise.

      chmod 755 /var/cache/bind && chown root.bind /var/cache/bind && service bind9 restart

    4. Edit /etc/update-manager/release-upgrades and ensure it contains the line Prompt=lts

       

    5. Start the upgrade manager:

      do-release-upgrade

    6. If the upgrade manager complains that no new release is found, use the following command:

      do-release-upgrade -d

    7. Follow the on-screen prompts, carefully noting down the instructions given about upgrading Postgres. Remove all packages it suggests removing. Answer the default (no) to all questions to keep the current versions of the files. Allow it to remove the obsolete packages

       

  3. Upgrading the operating system will install postgres-9.1. This will by default install a blank cluster (the postgres term for a database). It is thus necessary for you to upgrade your Postgres cluster after the upgrade to bring the original data back. You should follow the instructions you noted above. Use these in preference to what is set out below. If for some reason you have lost them, the normal route is:

    su postgres
pg_dropcluster --stop 9.1 main    
pg_upgradecluster 8.4 main

Note that to complete the operating system upgrade, you will need to reboot the management stack

C. Upgrading the installation on each management stack

To upgrade the installed FCO software, use the following procedure:

  1. Edit /etc/apt/sources.list

    Replace:

    deb http://repo.flexiant.com/fco extility main

    With:

    deb [arch=amd64] http://repo.flexiant.com/fco3 extility main


  2. Run

    aptitude update && aptitude upgrade
  3. Check all services are running correctly.

  4. Ensure that the appropriate packages are installed

    1. For a cluster and control plane server.

      aptitude install extility-all

    2. For a control plane server.

      aptitude install extility-controlplane

    3. For a cluster.

      aptitude install extility-cluster

  5. Remove and purge xvpadmin

    aptitude remove extility-xvpadmin

aptitude purge extility-xvpadmin

  6. Rebuild the configuration:

    build-config -a

  7. Ensure services are restarted

    run-parts -a start --regex '^(extility|apache)' /etc/init.d
  8. Check all services are running correctly.

  9. You may wish to reboot the management stack to ensure all services start after a reboot. This step is optional.

D. Upgrading each node

FCO v2.0 uses node images running Ubuntu Lucid 10.04 LTS. FCO v.3.0 requires Ubuntu Precise 12.04 LTS, and the kernel that goes with it. Therefore you must reboot each node. This can be done without disruption to running virtual machines by using the procedure set out below for each node:

  1. Put the node into maintenance mode using the system control panel
     
  2. Live migrate all virtual machines from the node
     
  3. Wait until the node shows no VMs are running.
     
  4. Log into the node using the sshe command, and type reboot.

  5. Wait for the node to reboot.

  6. Mark the node as in running state using the system control panel.