7.5. Host Tasks

7.5.1. Adding a Red Hat Enterprise Linux Host

Summary
A Red Hat Enterprise Linux host is based on a standard "basic" installation of Red Hat Enterprise Linux, with specific entitlements enabled. The physical host must be set up before you can add it to the Red Hat Enterprise Virtualization environment.

Important

Make sure that virtualization is enabled in your host's BIOS settings. For information on changing your host's BIOS settings, refer to your host's hardware documentation.

Procedure 7.1. Adding a Red Hat Enterprise Linux Host

  1. Click the Hosts resource tab to list the hosts in the results list.
  2. Click New to open the New Host window.
  3. Use the drop-down menus to select the Data Center and Host Cluster for the new host.
  4. Enter the Name, Address, and SSH Port of the new host.
  5. Select an authentication method to use with the host.
    • Enter the root user's password to use password authentication.
    • Copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.
  6. You have now completed the mandatory steps to add a Red Hat Enterprise Linux host. Click the Advanced Parameters button to expand the advanced host settings.
    1. Optionally disable automatic firewall configuration.
    2. Optionally disable use of JSON protocol.

      Note

      With Red Hat Enterprise Virtualization 3.5, the communication model between the Manager and VDSM now uses JSON protocol, which reduces parsing time. As a result, the communication message format has changed from XML format to JSON format. Web requests have changed from synchronous HTTP requests to asynchronous TCP requests.
    3. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
  7. You can configure the Power Management and SPM using the applicable tabs now; however, as these are not fundamental to adding a Red Hat Enterprise Linux host, they are not covered in this procedure.
  8. Click OK.
Result
The new host displays in the list of hosts with a status of Installing, and you can view the progress of the installation in the details pane. After installation is complete, the status updates to Reboot. The host must be activated for the status to change to Up.

7.5.2. Adding a Foreman Host Provider Host

Summary
The process for adding a Foreman host provider host is almost identical to that of adding a Red Hat Enterprise Linux host except for the method by which the host is identified in the Manager. The following procedure outlines how to add a host provided by a Foreman host provider.

Procedure 7.2. Adding a Foreman Host Provider Host

  1. Click the Hosts resource tab to list the hosts in the results list.
  2. Click New to open the New Host window.
  3. Use the drop-down menus to select the Data Center and Host Cluster for the new host.
  4. Select the Use Foreman Hosts Providers check box to display the options for adding a Foreman host provider host and select the provider from which the host is to be added.
  5. Select either Discovered Hosts or Provisioned Hosts.
    • Discovered Hosts (default option): Select the host, host group, and compute resources from the drop-down lists.
    • Provisioned Hosts: Select a host from the Providers Hosts drop-down list.
    Any details regarding the host that can be retrieved from the external provider are automatically set, and can be edited as desired.
  6. Enter the Name, Address, and SSH Port (Provisioned Hosts only) of the new host.
  7. Select an authentication method to use with the host.
    • Enter the root user's password to use password authentication.
    • Copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_hosts on the host to use public key authentication (Provisioned Hosts only).
  8. You have now completed the mandatory steps to add a Red Hat Enterprise Linux host. Click the Advanced Parameters drop-down button to show the advanced host settings.
    1. Optionally disable automatic firewall configuration.
    2. Optionally disable the use of JSON protocol.
    3. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
  9. You can configure the Power Management, SPM, Console, and Network Provider using the applicable tabs now; however, as these are not fundamental to adding a Red Hat Enterprise Linux host, they are not covered in this procedure.
  10. Click OK to add the host and close the window.
Result
The new host displays in the list of hosts with a status of Installing, and you can view the progress of the installation in the details pane. After installation is complete, the status will update to Reboot. The host must be activated for the status to change to Up.

7.5.3. Approving a Registered Hypervisor

Approve a Hypervisor that has been registered using the details of the Manager.

Procedure 7.3. Approving a Registered Hypervisor

  1. From the Administration Portal, click the Hosts tab, and then click the host to be approved. The host is currently listed with the status of Pending Approval.
  2. Click Approve to open the Edit and Approve Hosts window. You can use the window to specify a name for the Hypervisor, fetch its SSH fingerprint before approving it, and configure power management. For information on power management configuration, refer to Section 7.5.4.2, “Host Power Management Settings Explained”.
  3. Click OK. If you have not configured power management, you are prompted to confirm whether to proceed without doing so; click OK.

7.5.4. Explanation of Settings and Controls in the New Host and Edit Host Windows

7.5.4.1. Host General Settings Explained

These settings apply when editing the details of a host or adding new Red Hat Enterprise Linux hosts and Foreman host provider hosts.
The General settings table contains the information required on the General tab of the New Host or Edit Host window.

Table 7.1. General settings

Field Name
Description
Data Center
The data center to which the host belongs. Red Hat Enterprise Virtualization Hypervisor hosts cannot be added to Gluster-enabled clusters.
Host Cluster
The cluster to which the host belongs.
Use Foreman Hosts Providers
Select or clear this check box to view or hide options for adding hosts provided by Foreman hosts providers. The following options are also available:
Discovered Hosts
  • Discovered Hosts - A drop-down list that is populated with the name of Foreman hosts discovered by the engine.
  • Host Groups -A drop-down list of host groups available.
  • Compute Resources - A drop-down list of hypervisors to provide compute resources.
Provisioned Hosts
  • Providers Hosts - A drop-down list that is populated with the name of hosts provided by the selected external provider. The entries in this list are filtered in accordance with any search queries that have been input in the Provider search filter.
  • Provider search filter - A text field that allows you to search for hosts provided by the selected external provider. This option is provider-specific; see provider documentation for details on forming search queries for specific providers. Leave this field blank to view all available hosts.
Name
The name of the cluster. This text field has a 40-character limit and must be a unique name with any combination of uppercase and lowercase letters, numbers, hyphens, and underscores.
Comment
A field for adding plain text, human-readable comments regarding the host.
Address
The IP address, or resolvable hostname of the host.
Password
The password of the host's root user. This can only be given when you add the host; it cannot be edited afterwards.
SSH PublicKey
Copy the contents in the text box to the /root/.known_hosts file on the host to use the Manager's ssh key instead of using a password to authenticate with the host.
Automatically configure host firewall
When adding a new host, the Manager can open the required ports on the host's firewall. This is enabled by default. This is an Advanced Parameter.
Use JSON protocol
This is enabled by default. This is an Advanced Parameter.
SSH Fingerprint
You can fetch the host's SSH fingerprint, and compare it with the fingerprint you expect the host to return, ensuring that they match. This is an Advanced Parameter.

7.5.4.2. Host Power Management Settings Explained

The Power Management settings table contains the information required on the Power Management tab of the New Host or Edit Host windows.

Table 7.2. Power Management Settings

Field Name
Description
Kdump integration
Prevents the host from fencing while performing a kernel crash dump, so that the crash dump is not interrupted. Kdump is available by default on new Red Hat Enterprise Linux 6.6 and 7.1 hosts and Hypervisors. If kdump is available on the host, but its configuration is not valid (the kdump service cannot be started), enabling Kdump integration will cause the host (re)installation to fail. If this is the case, see Section 7.7.4, “fence_kdump Advanced Configuration”.
Primary/ Secondary
Prior to Red Hat Enterprise Virtualization 3.2, a host with power management configured only recognized one fencing agent. Fencing agents configured on version 3.1 and earlier, and single agents, are treated as primary agents. The secondary option is valid when a second agent is defined.
Concurrent
Valid when there are two fencing agents, for example for dual power hosts in which each power switch has two agents connected to the same power switch.
  • If this check box is selected, both fencing agents are used concurrently when a host is fenced. This means that both fencing agents have to respond to the Stop command for the host to be stopped; if one agent responds to the Start command, the host will go up.
  • If this check box is not selected, the fencing agents are used sequentially. This means that to stop or start a host, the primary agent is used first, and if it fails, the secondary agent is used.
Address
The address to access your host's power management device. Either a resolvable hostname or an IP address.
User Name
User account with which to access the power management device. You can set up a user on the device, or use the default user.
Password
Password for the user accessing the power management device.
Type
The type of power management device in your host.
Choose one of the following:
  • apc - APC MasterSwitch network power switch. Not for use with APC 5.x power switch devices.
  • apc_snmp - Use with APC 5.x power switch devices.
  • bladecenter - IBM Bladecenter Remote Supervisor Adapter.
  • cisco_ucs - Cisco Unified Computing System.
  • drac5 - Dell Remote Access Controller for Dell computers.
  • drac7 - Dell Remote Access Controller for Dell computers.
  • eps - ePowerSwitch 8M+ network power switch.
  • hpblade - HP BladeSystem.
  • ilo, ilo2, ilo3, ilo4 - HP Integrated Lights-Out.
  • ipmilan - Intelligent Platform Management Interface and Sun Integrated Lights Out Management devices.
  • rsa - IBM Remote Supervisor Adapter.
  • rsb - Fujitsu-Siemens RSB management interface.
  • wti - WTI Network Power Switch.
Port
The port number used by the power management device to communicate with the host.
Options
Power management device specific options. Enter these as 'key=value' or 'key'. See the documentation of your host's power management device for the options available.
For Red Hat Enterprise Linux 7 hosts, if you are using cisco_ucs as the power management device, you also need to append ssl_insecure=1 to the Options field.
Secure
Select this check box to allow the power management device to connect securely to the host. This can be done via ssh, ssl, or other authentication protocols depending on and supported by the power management agent.
Source
Specifies whether the host will search within its cluster or data center for a fencing proxy. Use the Up and Down buttons to change the sequence in which the resources are used.
Disable policy control of power management
Power management is controlled by the Cluster Policy of the host's cluster. If power management is enabled and the defined low utilization value is reached, the Manager will power down the host machine, and restart it again when load balancing requires or there are not enough free hosts in the cluster. Select this check box to disable policy control.

7.5.4.3. SPM Priority Settings Explained

The SPM settings table details the information required on the SPM tab of the New Host or Edit Host window.

Table 7.3. SPM settings

Field Name
Description
SPM Priority
Defines the likelihood that the host will be given the role of Storage Pool Manager (SPM). The options are Low, Normal, and High priority. Low priority means that there is a reduced likelihood of the host being assigned the role of SPM, and High priority means there is an increased likelihood. The default setting is Normal.

7.5.4.4. Host Console Settings Explained

The Console settings table details the information required on the Console tab of the New Host or Edit Host window.

Table 7.4. Console settings

Field Name
Description
Override display address
Select this check box to override the display addresses of the host. This feature is useful in a case where the hosts are defined by internal IP and are behind a NAT firewall. When a user connects to a virtual machine from outside of the internal network, instead of returning the private address of the host on which the virtual machine is running, the machine returns a public IP or FQDN (which is resolved in the external network to the public IP).
Display address
The display address specified here will be used for all virtual machines running on this host. The address must be in the format of a fully qualified domain name or IP.

7.5.5. Configuring Host Power Management Settings

Summary
Configure your host power management device settings to perform host life-cycle operations (stop, start, restart) from the Administration Portal.
It is necessary to configure host power management in order to utilize host high availability and virtual machine high availability.

Important

Ensure that your host is in maintenance mode before configuring power management settings. Otherwise, all running virtual machines on that host will be stopped ungracefully upon restarting the host, which can cause disruptions in production environments. A warning dialog will appear if you have not correctly set your host to maintenance mode.

Procedure 7.4. Configuring Power Management Settings

  1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
  2. Click Edit to open the Edit Host window.
  3. Click the Power Management tab to display the Power Management settings.
  4. Select the Enable Power Management check box to enable the fields.
  5. Select the Kdump integration check box to prevent the host from fencing while performing a kernel crash dump.

    Important

    When you enable Kdump integration on an existing host, the host must be reinstalled for kdump to be configured. See Section 7.5.12, “Reinstalling Virtualization Hosts”.
  6. The Primary option is selected by default if you are configuring a new power management device. If you are adding a new device, set it to Secondary.
  7. Select the Concurrent check box to enable multiple fence agents to be used concurrently.
  8. Enter the Address, User Name, and Password of the power management device into the appropriate fields.
  9. Use the drop-down menu to select the Type of power management device.
  10. Enter the Port number used by the power management device to communicate with the host.
  11. Enter the Options for the power management device. Use a comma-separated list of 'key=value' or 'key'.
  12. Select the Secure check box to enable the power management device to connect securely to the host.
  13. Click Test to ensure the settings are correct.
  14. Click OK to save your settings and close the window.
Result
You have configured the power management settings for the host. The Power Management drop-down menu is now enabled in the Administration Portal.

Note

Power management is controlled by the Cluster Policy of the host's cluster. If power management is enabled and the defined low utilization value is reached, the Manager will power down the host machine, and restart it again when load balancing requires or there are not enough free hosts in the cluster. Tick the Disable policy control of power management check box if you do not wish for your host to automatically perform these functions.

7.5.6. Configuring Host Storage Pool Manager Settings

Summary
The Storage Pool Manager (SPM) is a management role given to one of the hosts in a data center to maintain access control over the storage domains. The SPM must always be available, and the SPM role will be assigned to another host if the SPM host becomes unavailable. As the SPM role uses some of the host's available resources, it is important to prioritize hosts that can afford the resources.
The Storage Pool Manager (SPM) priority setting of a host alters the likelihood of the host being assigned the SPM role: a host with high SPM priority will be assigned the SPM role before a host with low SPM priority.

Procedure 7.5. Configuring SPM settings

  1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
  2. Click Edit to open the Edit Host window.
  3. Click the SPM tab to display the SPM Priority settings.
  4. Use the radio buttons to select the appropriate SPM priority for the host.
  5. Click OK to save the settings and close the window.
Result
You have configured the SPM priority of the host.

7.5.7. Editing a Resource

Summary
Edit the properties of a resource.

Procedure 7.6. Editing a Resource

  1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
  2. Click Edit to open the Edit window.
  3. Change the necessary properties and click OK.
Result
The new properties are saved to the resource. The Edit window will not close if a property field is invalid.

7.5.8. Approving Newly Added Red Hat Enterprise Virtualization Hypervisor Hosts

Summary
You have to install your Red Hat Enterprise Virtualization Hypervisor hosts before you can approve them in the Red Hat Enterprise Virtualization Manager. Read about installing Red Hat Enterprise Virtualization Hypervisors in the Red Hat Enterprise Virtualization Installation Guide.
Once installed, the Red Hat Enterprise Virtualization Hypervisor host is visible in the Administration Portal but not active. Approve it so that it can host virtual machines.

Procedure 7.7. Approving newly added Red Hat Enterprise Virtualization Hypervisor hosts

  1. In the Hosts tab, select the host you recently installed using the Red Hat Enterprise Virtualization Hypervisor host installation media. This host shows a status of Pending Approval.
  2. Click the Approve button.
Result
The host's status changes to Up and it can be used to run virtual machines.

Note

You can also add this host using the procedure in Section 7.5.1, “Adding a Red Hat Enterprise Linux Host”, which utilizes the Red Hat Enterprise Virtualization Hypervisor host's IP address and the password that was set on the RHEV-M screen.

7.5.9. Moving a Host to Maintenance Mode

Summary
Many common maintenance tasks, including network configuration and deployment of software updates, require that hosts be placed into maintenance mode. When a host is placed into maintenance mode the Red Hat Enterprise Virtualization Manager attempts to migrate all running virtual machines to alternative hosts.
The normal prerequisites for live migration apply, in particular there must be at least one active host in the cluster with capacity to run the migrated virtual machines.

Procedure 7.8. Moving a Host to Maintenance Mode

  1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
  2. Click Maintenance to open the Maintenance Host(s) confirmation window.
  3. Click OK to initiate maintenance mode.
Result:
All running virtual machines are migrated to alternative hosts. The Status field of the host changes to Preparing for Maintenance, and finally Maintenance when the operation completes successfully.

7.5.10. Activating a Host from Maintenance Mode

Summary
A host that has been placed into maintenance mode, or recently added to the environment, must be activated before it can be used.

Procedure 7.9. Activating a Host from Maintenance Mode

  1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
  2. Click Activate.
Result
The host status changes to Unassigned, and finally Up when the operation is complete. Virtual machines can now run on the host.

7.5.11. Removing a Host

Remove a host from your virtualized environment.

Procedure 7.10. Removing a host

  1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
  2. Place the host into maintenance mode.
  3. Click Remove to open the Remove Host(s) confirmation window.
  4. Select the Force Remove check box if the host is part of a Red Hat Gluster Storage cluster and has volume bricks on it, or if the host is non-responsive.
  5. Click OK.
Your host has been removed from the environment and is no longer visible in the Hosts tab.

7.5.12. Reinstalling Virtualization Hosts

Reinstall Red Hat Enterprise Virtualization Hypervisors and Red Hat Enterprise Linux hosts from the Administration Portal. Use this procedure to reinstall Hypervisors from the same version of the Hypervisor ISO image from which it is currently installed; the procedure reinstalls VDSM on Red Hat Enterprise Linux Hosts. This includes stopping and restarting the Hypervisor. If migration is enabled at cluster level, virtual machines are automatically migrated to another host in the cluster; as a result, it is recommended that host reinstalls are performed at a time when the Hypervisor's usage is relatively low.
The cluster to which the Hypervisor belongs must have sufficient memory reserve in order for its hosts to perform maintenance. Moving a host with live virtual machines to maintenance in a cluster that lacks sufficient memory causes the virtual machine migration operation to hang and then fail. You can reduce the memory usage of this operation by shutting down some or all virtual machines before moving the host to maintenance.

Important

Ensure that the cluster contains more than one host before performing a reinstall. Do not attempt to reinstall all the hosts at the same time, as one host must remain available to perform Storage Pool Manager (SPM) tasks.

Procedure 7.11. Reinstalling Red Hat Enterprise Virtualization Hypervisors and Red Hat Enterprise Linux Hosts

  1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
  2. Click Maintenance. If migration is enabled at cluster level, any virtual machines running on the host are migrated to other hosts. If the host is the SPM, this function is moved to another host. The status of the host changes as it enters maintenance mode.
  3. Click Reinstall to open the Install Host window.
  4. Click OK to reinstall the host.
Once successfully reinstalled, the host displays a status of Up. Any virtual machines that were migrated off the host, are at this point able to be migrated back to it.

Important

After a Red Hat Enterprise Virtualization Hypervisor is successfully registered to the Red Hat Enterprise Virtualization Manager and then reinstalled, it may erroneously appear in the Administration Portal with the status of Install Failed. Click Activate, and the Hypervisor will change to an Up status and be ready for use.

7.5.13. Customizing Hosts with Tags

Summary
You can use tags to store information about your hosts. You can then search for hosts based on tags.

Procedure 7.12. Customizing hosts with tags

  1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
  2. Click Assign Tags to open the Assign Tags window.
    Assign Tags Window

    Figure 7.1. Assign Tags Window

  3. The Assign Tags window lists all available tags. Select the check boxes of applicable tags.
  4. Click OK to assign the tags and close the window.
Result
You have added extra, searchable information about your host as tags.

7.5.14. Changing the IP Address of a Red Hat Enterprise Virtualization Hypervisor (RHEV-H)

Procedure 7.13. 

  1. Place the Hypervisor into maintenance mode so the virtual machines are live migrated to another Hypervisor. See Section 7.5.9, “Moving a Host to Maintenance Mode” for more information. Alternatively, manually shut down or migrate all the virtual machines to another Hypervisor. See Manually Migrating Virtual Machines for more information.
  2. Click Remove, and click OK to remove the host from the Administration Portal.
  3. Log in to your Hypervisor as the admin user.
  4. Press F2, select OK, and press Enter to enter the rescue shell.
  5. Modify the IP address by editing the /etc/sysconfig/network-scripts/ifcfg-rhevm file. For example:
    # vi /etc/sysconfig/network-scripts/ifcfg-rhevm
    ...
    BOOTPROTO=none	
    IPADDR=10.x.x.x
    PREFIX=24
    ...
  6. Restart the network service and verify that the IP address has been updated.
    • For Red Hat Enterprise Linux 6:
      # service network restart
      # ifconfig rhevm
    • For Red Hat Enterprise Linux 7:
      # systemctl restart network.service
      # ip addr show rhevm
  7. Type exit to exit the rescue shell and return to the text user interface.
  8. Re-register the host with the Manager. See Installation Guide, Manually Adding a Hypervisor from the Administration Portal for more information.

7.5.15. Changing the FQDN of a Host

Use the following procedure to change the fully qualified domain name of hypervisor hosts.

Procedure 7.14. Updating the FQDN of a Hypervisor Host

  1. Place the Hypervisor into maintenance mode so the virtual machines are live migrated to another Hypervisor. See Section 7.5.9, “Moving a Host to Maintenance Mode” for more information. Alternatively, manually shut down or migrate all the virtual machines to another Hypervisor. See Manually Migrating Virtual Machines for more information.
  2. Click Remove, and click OK to remove the host from the Administration Portal.
    • For RHEL-based hosts:
      • For Red Hat Enterprise Linux 6:
        Edit the /etc/sysconfig/network file, update the host name, and save.
        # vi /etc/sysconfig/network
        HOSTNAME=NEW_FQDN
      • For Red Hat Enterprise Linux 7:
        Use the hostnamectl tool to update the host name. For more options, see Red Hat Enterprise Linux 7 Networking Guide, Configure Host Names.
        # hostnamectl set-hostname NEW_FQDN
    • For Red Hat Enterprise Virtualization Hypervisors (RHEV-H):
      In the text user interface, select the Network screen, press the right arrow key and enter a new host name in the Hostname field. Select <Save> and press Enter.
  3. Reboot the host.
  4. Re-register the host with the Manager. See Installation Guide, Manually Adding a Hypervisor from the Administration Portal for more information.