Making open source more inclusive

1. Place the cluster into Global Maintenance mode

   1. Log in to the Web Console.
   2. Click Virtualization Hosted Engine.
   3. Click Put this cluster into global maintenance.

2. Upgrade Red Hat Virtualization Manager.

   1. Log in to the Hosted Engine virtual machine.

   2. Upgrade the setup packages:

      # yum update ovirt-engine\*setup\* rh\*vm-setup-plugin

   3. Run engine-setup and follow the prompts to upgrade the Manager.

      This process can take a while and cannot be aborted, so Red Hat recommends running it inside a screen session. See How to use the screen command for more information about this function.

   4. Upgrade all other packages.

      # yum update

   5. Reboot the Hosted Engine virtual machine to ensure all updates are applied.

      # reboot

3. Restart the Hosted Engine virtual machine.

   1. Log in to any hyperconverged host.

   2. Start the Hosted Engine virtual machine.

      # hosted-engine --vm-start

   3. Verify the status of the Hosted Engine virtual machine.

      # hosted-engine --vm-status

4. Remove the cluster from Global Maintenance mode.

   1. Log in to the Web Console.
   2. Click Virtualization Hosted Engine.
   3. Click Remove this cluster from global maintenance.

1. Upgrade one host at a time

   Perform the following steps to upgrade each hyperconverged host.

   1. Disable self-healing on each hosted volume.

      Run the following commands to disable self-healing for each volume on this hyperconverged host.

      # gluster volume set <volname> cluster.self-heal-daemon off

      For example:

      # gluster volume set engine cluster.self-heal-daemon off
      # gluster volume set vmstore cluster.self-heal-daemon off
      # gluster volume set data cluster.self-heal-daemon off

   2. Upgrade the hyperconverged host.

      1. In the Manager, click Compute Hosts and select a node.
      2. Click Installation Upgrade.

      3. Click OK to confirm the upgrade.

         Wait for the upgrade to complete, and for the host to become available again.

   3. Enable self-healing on each hosted volume.

      Run the following commands to enable self-healing for each volume on this hyperconverged host.

      # gluster volume set <volname> cluster.self-heal-daemon on

      For example:

      # gluster volume set engine cluster.self-heal-daemon on
      # gluster volume set vmstore cluster.self-heal-daemon on
      # gluster volume set data cluster.self-heal-daemon on

   4. Verify self-healing is complete before upgrading the next host.

      1. Click the name of the host.
      2. Click the Bricks tab.

      3. Verify that the Self-Heal Info column of all bricks is listed as OK before upgrading the next host.

         If self-heal does not complete, there could be a Gluster file ID (GFID) mismatch. See the Self-heal does not complete section in Maintaining Red Hat Hyperconverged Infrastructure for Virtualization for assistance resolving this issue.

2. Update cluster compatibility

   When all hosts are upgraded, update cluster compatibility setting.

   1. In the Manager, click Cluster and select the cluster (Default).
   2. Click Edit.
   3. Update the value of Cluster compatibility to 4.3 and save.

3. Update cluster operating version

   When all hosts are upgraded, run the following command on any host to update the operating version of all volumes in the cluster.

   # gluster volume set all cluster.op-version 70200

   1. Restart all virtual machines

      This ensures that the new cluster compatibility setting takes effect.

      1. Click Compute Virtual Machines and select a running virtual machine.
      2. Click Reboot.

      3. Click OK in the Reboot Virtual Machine(s) confirmation window.

         The Status of the virtual machine changes to Reboot In Progress before returning to Up.

Procedure

1. Log in to the Web Console.
2. Click Virtualization Hosted Engine and then click Manage Gluster.

3. Click Create Volume. The Create Volume window opens.

   1. On the Hosts tab, select three different hyperconverged hosts with unused disks and click Next.

      

   2. On the Volumes tab, specify the details of the volume you want to create and click Next.

      

   3. On the Bricks tab, specify the details of the disks to be used to create the volume and click Next.

      

   4. On the Review tab, check the generated configuration file for any incorrect information. When you are satisfied, click Deploy.

      

      Successfully created volume is displayed when deployment completes successfully.

Procedure

1. In the Administration Portal, click the Storage tab and then click New Domain.
2. Ensure that the new storage domain is in the same data center as the existing storage domain.
3. Provide a Name for the domain, for example, vmstore2.
4. Set the Domain function to Data.
5. Set the Storage Type to GlusterFS.
6. Check the Use managed gluster volume option.
7. Set the Gluster dropdown to the new volume.
8. Click OK.

Procedure

1. In the Administration Portal, click Storage > Domains and click the name of the old storage domain.
2. Click the Disks tab.
3. Select the disks that you want to move and click Move.
4. From the Target list, select the storage domain to which the disks will move.
5. Optionally, from the Disk Profile list, select a profile.

6. Click OK.

   The virtual disks are moved to the target storage domain. During the move procedure, the Status column displays Locked and a progress bar indicating the progress of the move operation.