Chapter 3. Administering the Environment

1. Click Compute Clusters and select the cluster containing the self-hosted engine nodes.
2. Click Edit.
3. Click the Scheduling Policy tab.
4. Click + and select HeSparesCount.
5. Enter the number of additional self-hosted engine nodes that will reserve enough free memory to start the Manager virtual machine.
6. Click OK.

Procedure

1. In the Administration Portal, click Compute Hosts.

2. Click New.

   For information on additional host settings, see Explanation of Settings and Controls in the New Host and Edit Host Windows in the Administration Guide.

3. Use the drop-down list to select the Data Center and Host Cluster for the new host.
4. Enter the Name and the Address of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field.

5. Select an authentication method to use for the Manager to access the host.

   • Enter the root user’s password to use password authentication.
   • Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.
6. Optionally, configure power management, where the host has a supported power management card. For information on power management configuration, see Host Power Management Settings Explained in the Administration Guide.
7. Click the Hosted Engine tab.
8. Select Deploy.
9. Click OK.

Procedure

1. Click Compute Hosts and select the host.
2. Click Management Maintenance and OK.
3. Click Installation Reinstall.
4. Click the Hosted Engine tab and select DEPLOY from the drop-down list.
5. Click OK.

1. Connect to one of the hosted-engine nodes:

   $ ssh root@host_address

2. Put the self-hosted engine in global maintenance mode:

   # hosted-engine --set-maintenance --mode=global

3. Check if there is already a running instance of the Manager virtual machine:

   # hosted-engine --vm-status

   If a Manager virtual machine instance is running, connect to its host:

   # ssh root@host_address

4. Shut down the virtual machine:

   # hosted-engine --vm-shutdown

   Note

   If the virtual machine does not shut down, execute the following command:

   # hosted-engine --vm-poweroff

5. Start the Manager virtual machine in pause mode:

   hosted-engine --vm-start-paused

6. Set a temporary VNC password:

   hosted-engine --add-console-password

   The command outputs the necessary information you need to log in to the Manger virtual machine with VNC.

7. Log in to the Manager virtual machine with VNC. The Manager virtual machine is still paused, so it appears to be frozen.

8. Resume the Manager virtual machine with the following command on its host:

   Warning

   After running the following command, the boot loader menu appears. You need to enter into rescue mode before the boot loader proceeds with the normal boot process. Read the next step about entering into rescue mode before proceeding with this command.

   # /usr/bin/virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf resume HostedEngine

9. Boot the Manager virtual machine in rescue mode.

10. Disable global maintenance mode

    # hosted-engine --set-maintenance --mode=none

Procedure

1. In the Administration Portal, click Compute Hosts and select the self-hosted engine node.
2. Click Management Maintenance and OK.
3. Click Installation Reinstall.
4. Click the Hosted Engine tab and select UNDEPLOY from the drop-down list. This action stops the ovirt-ha-agent and ovirt-ha-broker services and removes the self-hosted engine configuration file.
5. Click OK.
6. Optionally, click Remove. This opens the Remove Host(s) confirmation window.
7. Click OK.

Procedure

1. Log in to one of the self-hosted engine nodes and enable global maintenance mode:

   # hosted-engine --set-maintenance --mode=global

2. Confirm that the environment is in global maintenance mode before proceeding:

   # hosted-engine --vm-status

   You should see a message indicating that the cluster is in global maintenance mode.

Procedure

1. On the Manager machine, check if updated packages are available:

   # engine-upgrade-check

2. Update the setup packages:

   # yum update ovirt\*setup\* rh\*vm-setup-plugins

3. Update the Red Hat Virtualization Manager with the engine-setup script. The engine-setup script prompts you with some configuration questions, then stops the ovirt-engine service, downloads and installs the updated packages, backs up and updates the database, performs post-installation configuration, and starts the ovirt-engine service.

   # engine-setup

   When the script completes successfully, the following message appears:

   Execution of setup completed successfully

   Note

   The engine-setup script is also used during the Red Hat Virtualization Manager installation process, and it stores the configuration values supplied. During an update, the stored values are displayed when previewing the configuration, and might not be up to date if engine-config was used to update configuration after installation. For example, if engine-config was used to update SANWipeAfterDelete to true after installation, engine-setup will output "Default SAN wipe after delete: False" in the configuration preview. However, the updated values will not be overwritten by engine-setup.

   Important

   The update process might take some time. Do not stop the process before it completes.

4. Update the base operating system and any optional packages installed on the Manager:

   # yum update --nobest

   Important

   If you encounter a required Ansible package conflict during the update, see Cannot perform yum update on my RHV manager (ansible conflict).

   Important

   If any kernel packages were updated:

   1. Disable global maintenance mode
   2. Reboot the machine to complete the update.

Procedure

1. Log in to the Manager virtual machine and shut it down.

2. Log in to one of the self-hosted engine nodes and disable global maintenance mode:

   # hosted-engine --set-maintenance --mode=none

   When you exit global maintenance mode, ovirt-ha-agent starts the Manager virtual machine, and then the Manager automatically starts. It can take up to ten minutes for the Manager to start.

3. Confirm that the environment is running:

   # hosted-engine --vm-status

   The listed information includes Engine Status. The value for Engine status should be:

   {"health": "good", "vm": "up", "detail": "Up"}

   Note

   When the virtual machine is still booting and the Manager hasn’t started yet, the Engine status is:

   {"reason": "bad vm status", "health": "bad", "vm": "up", "detail": "Powering up"}

   If this happens, wait a few minutes and try again.