Upgrading a Federation

This version of OpenNebula introduces some changes in the federation data model. You need to coordinate the upgrade across zones and upgrade them at the same time.

Step 1. Check Federation Status

Check that federation is in sync and all zones are at the same index (FED_INDEX):

onezone list
C   ID NAME                                         ENDPOINT                                      FED_INDEX
   101 S-US-CA                                      http://192.168.150.3:2633/RPC2                715438
   100 S-EU-GE                                      http://192.168.150.2:2633/RPC2                715438
*    0 M-EU-FR                                      http://192.168.150.1:2633/RPC2                715438

It is a good idea to prevent any API access to the master zone during this step (e.g. by filtering out access to API).

Step 2. Stop All Zones

Stop OpenNebula and any other related services you may have running: OneFlow, EC2, and Sunstone, in all zones. Preferably use the system tools, like systemctl or service as root in order to stop the services.

Step 4. Backup federated tables

Once master zone has been updated, you need to export federated tables:

onedb backup -v --federated

Step 5. Restore federated backup in slave zones

The backup that has been generated needs to be restored in all slave zones:

onedb restore <backup_file> -v --federated

Step 6. Upgrade Slave Zones

You can upgrade now the slave zones:

You will restart OpenNebula in each zone as part of the upgrade. Once you finish upgrading your master remove any access restriction to the API imposed in Step 1.