User login
Learn how to use Qlustar!

Qlustar Update Procedure

Updating a Qlustar cluster is a multi-step process. The detailed steps depend on whether the update involves a kernel update or not (the release notes will mention it, if a new kernel is part of the update) and what module versions you have selected for your images. We'll explain the differences below. Follow the steps in the following order.

Updating the head-node(s)

Apply the standard Debian procedure to update the head-node(s) installation. Execute as root:

  $ aptitude update
  $ aptitude dist-upgrade

This will update all packages. In most cases, if new versions of the Qlustar image module packages are available, this will also automatically rebuild the images defined in QluMan. We elaborate on this below.

If the kernel was updated by this process reboot the head-node(s) after executing the above commands, otherwise you're done with this step.

Updating the chroot(s)

This is also a standard Debian upgrade as explained in the First Steps Guide. If you have setup multiple chroots, you'll have to update all of them.

Updating the nodes

If the update contains a new kernel, reboot all nodes. In case you have some storage nodes that export a global file-system (e.g. NFS or Lustre), reboot them first, then all the other nodes.

If the update doesn't contain a new kernel, you have the choice of either rebooting the nodes like above or using the Qlustar online update mechanism (currently the online update has to be executed manually, future versions of QluMan will allow to do this from the GUI) as follows. Execute the following command on the head-node for each node (of course, this can be done in a shell for loop):

  $ qlustar-image-update -u <image name> <hostname>

where <image name> has to be the name of the image that is currently booted on the corresponding node. You also have the option to first check what exactly the update will change. To find out, execute the following for one sample node per image type:

  $ qlustar-image-update -c <image name> <hostname>

This will show the files that will be changed by this update.

  $ qlustar-image-update -s <image name> <hostname>

This will show all services (daemons) that need to be restarted as a result of this update.

When will images be updated/rebuilt?

There are a couple of cases to distinguish, depending on what version is selected for an image in QluMan (see also the corresponding section in the QluMan Guide).

  1. Selected image version is of type x.y.z,
    e.g. 8.1.1. In this case, the image will be rebuilt if and only if there is an update for the selected version (8.1.1) of the modules. Such updates will always be bug-/security-fixes.
  2. Selected image version is of type x.y,
    e.g. 8.1 with 8.1.1 being the most recent 8.1.z version before applying the update. In this case the image is rebuilt, if the update entails a new maintenance release (e.g. 8.1.2 which will then become the new real image version) or an update for the currently installed (8.1.1) modules.
  3. Selected image version is of type x,,
    e.g. 8 with 8.1 being the most recent 8.y and 8.1.1 being the most recent 8.1.z version before applying the update. In this case the image is rebuilt, if either the update entails a new feature release (e.g. 8.2, the latest 8.2.z will then become the new real image version) or a new maintenance release (e.g. 8.1.2 which will then become the new real image version) or an update for the currently installed (8.1.1) modules. With this option, manual intervention to obtain a new image version is only necessary when upgrading to a new major release (e.g. 9.y.z).
glqxz9283 sfy39587stf02 mnesdcuix8
sfy39587stf03
sfy39587p08