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 3.0 to major release 3.1. This upgrade involves major changes to the product, product offer, and billing systems of Flexiant Cloud Orchestrator; Licensees may wish to verify there are no issues with the upgrade before distributing it to billing entities and customers.

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

The billing cycle will not run for one hour after the upgrade. For this reason we suggest that the upgrade is performed when the platform is not in use by customers.

This release contains major database changes. All that is necessary is that Jade is restarted which will be achieved simply by installing a new version. The significance of databases changes is simply that the install cannot be rolled back to a previous point version once Jade has been started other than by restoring from backup.

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 3.0 release. If not, follow procedure to update between minor releases. If you are running version 2.0, you will have to upgrade to version 3.0 first: see Upgrading from Major Release 2.0 to Major Release 3.0 for details.

    Upgrades from versions prior to 3.0.8 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.

  6. Make sure you have only one active Disk I/O product offer per billing entity. The Disk I/O charge will be combined with each server product offer.
  7. Make sure VAT Rate is set on all billing entities (as opposed to being left blank). On 3.0 a billing entity with a blank VAT rate will bill VAT at 20%. On 3.1, a billing entity with a blank value with bill VAT at 0%.


B. Upgrading the Operating System of each management stack

FCO v.3.0 and FCO v3.1 both Ubuntu Precise 12.04 LTS. However, now is a good time to upgrade to the latest security releases. 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. Upgrade your operating system using the abbreviated procedure set out below:

    aptitude update && aptitude safe-upgrade


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

C. Upgrading the installation on each management stack

To upgrade the FCO software, follow the following procedure:

  1. Edit /etc/apt/sources.list


    deb [arch=amd64] extility main


    deb [arch=amd64] extility main

  2. Run:

    aptitude update && aptitude safe-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. Rebuild the configuration:

    build-config -a


  6. Ensure services are restarted:

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


  7. Check all services are running correctly.

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

D. Upgrading each node

Node upgrading must be performed for each node on KVM and Xen platforms. On VMware and Hyper-V platforms, only router nodes must be upgraded.

Node software can also be upgraded when managing nodes on KVM and Xen platforms. This method does not require virtual machines to be migrated from the node whilst the upgrade is performed. For more information, see Managing Nodes.

FCO v3.1 uses a new node image. Therefore, you must reboot each appropriate node. Nodes can be rebooted without disruption to running virtual machines by using the procedure set out below.

For each appropriate node, perform the following steps:

  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.