|
|
UpgradeNotes
Steps required to upgrade a cluster to newer versions of Ganeti
Introduction
This page details the steps needed to upgrade a cluster to newer versions of Ganeti.
As a general rule, after each software update, the node daemons need to be restarted; if using the provided example init.d script, this means running on all nodes:
# /etc/init.d/ganeti restart
1.2 releases
1.2.3 to 1.2.4
No changes needed. Note that going back from 1.2.4 to 1.2.3 will require manual edit of the configuration file (since we added some HVM-related new attributes).
1.2.2 to 1.2.3
No changes needed. Note that the drbd7-to-8 upgrade tool does a disk format change for the drbd metadata, so in theory this might be risky. It is advised to have (good) backups before doing the upgrade.
1.2.1 to 1.2.2
No changes needed.
1.2.0 to 1.2.1
No changes needed. Only some bugfixes and new additions that don't affect existing clusters.
beta 3 to 1.2.0
No changes needed.
beta 2 to beta 3
No changes needed. A new version of the debian-etch-instance OS (0.3) has been released, but upgrading it is not required.
beta 1 to beta 2
Beta 2 switched the config file format to JSON. Steps to upgrade:
- shutdown the daemons (/etc/init.d/ganeti stop) on all nodes
- disable the cron job (default is /etc/cron.d/ganeti)
- install the new version
- make a backup copy of the config file
- upgrade the config file using the following: /usr/share/ganeti/cfgupgrade --verbose /var/lib/ganeti/config.data
- start the daemons and run gnt-cluster info, gnt-node list, gnt-instance list to check if the upgrade process went successfully
Also, the OS definition needs to be upgraded. There is a new version of the debian-etch-instance OS (0.2) that goes along with beta 2.
Sign in to add a comment