7.5. Host Tasks
- 7.5.1. Adding a Red Hat Enterprise Linux Host
- 7.5.2. Adding a Foreman Host Provider Host
- 7.5.3. Approving a Registered Hypervisor
- 7.5.4. Explanation of Settings and Controls in the New Host and Edit Host Windows
- 7.5.5. Configuring Host Power Management Settings
- 7.5.6. Configuring Host Storage Pool Manager Settings
- 7.5.7. Editing a Resource
- 7.5.8. Approving Newly Added Red Hat Enterprise Virtualization Hypervisor Hosts
- 7.5.9. Moving a Host to Maintenance Mode
- 7.5.10. Activating a Host from Maintenance Mode
- 7.5.11. Removing a Host
- 7.5.12. Reinstalling Virtualization Hosts
- 7.5.13. Customizing Hosts with Tags
- 7.5.14. Changing the IP Address of a Red Hat Enterprise Virtualization Hypervisor (RHEV-H)
- 7.5.15. Changing the FQDN of a Host
7.5.1. Adding a Red Hat Enterprise Linux Host
Important
Procedure 7.1. Adding a Red Hat Enterprise Linux Host
- Click the Hosts resource tab to list the hosts in the results list.
- Click to open the New Host window.
- Use the drop-down menus to select the Data Center and Host Cluster for the new host.
- Enter the Name, Address, and SSH Port of the new host.
- 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_keyson the host to use public key authentication.
- You have now completed the mandatory steps to add a Red Hat Enterprise Linux host. Click the button to expand the advanced host settings.
- Optionally disable automatic firewall configuration.
- 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. - Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
- 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.
- Click .
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
Procedure 7.2. Adding a Foreman Host Provider Host
- Click the Hosts resource tab to list the hosts in the results list.
- Click to open the New Host window.
- Use the drop-down menus to select the Data Center and Host Cluster for the new host.
- 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.
- 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. - Enter the Name, Address, and SSH Port (Provisioned Hosts only) of the new host.
- 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_hostson the host to use public key authentication (Provisioned Hosts only).
- You have now completed the mandatory steps to add a Red Hat Enterprise Linux host. Click the drop-down button to show the advanced host settings.
- Optionally disable automatic firewall configuration.
- Optionally disable the use of JSON protocol.
- Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
- 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.
- Click to add the host and close the window.
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
Procedure 7.3. Approving a Registered Hypervisor
- 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.
- 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”.
- Click . If you have not configured power management, you are prompted to confirm whether to proceed without doing so; click .
7.5.4. Explanation of Settings and Controls in the New Host and Edit Host Windows
7.5.4.1. Host General Settings Explained
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
Provisioned 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 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
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.
|
|
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:
|
|
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 and 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
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
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
Important
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
- Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
- Click to open the Edit Host window.
- Click the Power Management tab to display the Power Management settings.
- Select the Enable Power Management check box to enable the fields.
- 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”. - 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.
- Select the Concurrent check box to enable multiple fence agents to be used concurrently.
- Enter the Address, User Name, and Password of the power management device into the appropriate fields.
- Use the drop-down menu to select the Type of power management device.
- Enter the Port number used by the power management device to communicate with the host.
- Enter the Options for the power management device. Use a comma-separated list of 'key=value' or 'key'.
- Select the Secure check box to enable the power management device to connect securely to the host.
- Click to ensure the settings are correct.
- Click to save your settings and close the window.
Note
7.5.6. Configuring Host Storage Pool Manager Settings
Procedure 7.5. Configuring SPM settings
- Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
- Click to open the Edit Host window.
- Click the SPM tab to display the SPM Priority settings.
- Use the radio buttons to select the appropriate SPM priority for the host.
- Click to save the settings and close the window.
7.5.7. Editing a Resource
Procedure 7.6. Editing a Resource
- Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
- Click to open the Edit window.
- Change the necessary properties and click .
7.5.8. Approving Newly Added Red Hat Enterprise Virtualization Hypervisor Hosts
Procedure 7.7. Approving newly added Red Hat Enterprise Virtualization Hypervisor hosts
- 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. - Click the button.
Up and it can be used to run virtual machines.
Note
7.5.9. Moving a Host to Maintenance Mode
Procedure 7.8. Moving a Host to Maintenance Mode
- Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
- Click to open the Maintenance Host(s) confirmation window.
- Click to initiate maintenance mode.
Preparing for Maintenance, and finally Maintenance when the operation completes successfully.
7.5.10. Activating a Host from Maintenance Mode
Procedure 7.9. Activating a Host from Maintenance Mode
- Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
- Click .
Unassigned, and finally Up when the operation is complete. Virtual machines can now run on the host.
7.5.11. Removing a Host
Procedure 7.10. Removing a host
- Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
- Place the host into maintenance mode.
- Click to open the Remove Host(s) confirmation window.
- 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.
- Click .
7.5.12. Reinstalling Virtualization Hosts
Important
Procedure 7.11. Reinstalling Red Hat Enterprise Virtualization Hypervisors and Red Hat Enterprise Linux Hosts
- Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
- Click . 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.
- Click Reinstall to open the Install Host window.
- Click to reinstall the host.
Important
7.5.13. Customizing Hosts with Tags
Procedure 7.12. Customizing hosts with tags
- Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
- Click to open the Assign Tags window.
- The Assign Tags window lists all available tags. Select the check boxes of applicable tags.
- Click to assign the tags and close the window.
7.5.14. Changing the IP Address of a Red Hat Enterprise Virtualization Hypervisor (RHEV-H)
Procedure 7.13.
- 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.
- Click , and click to remove the host from the Administration Portal.
- Log in to your Hypervisor as the
adminuser. - Press F2, select , and press Enter to enter the rescue shell.
- Modify the IP address by editing the
/etc/sysconfig/network-scripts/ifcfg-rhevmfile. For example:# vi /etc/sysconfig/network-scripts/ifcfg-rhevm ... BOOTPROTO=none IPADDR=10.x.x.x PREFIX=24 ...
- 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
- Type
exitto exit the rescue shell and return to the text user interface. - 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
Procedure 7.14. Updating the FQDN of a Hypervisor Host
- 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.
- Click , and click to remove the host from the Administration Portal.
- For RHEL-based hosts:
- For Red Hat Enterprise Linux 6:Edit the
/etc/sysconfig/networkfile, 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 and press Enter.
- Reboot the host.
- Re-register the host with the Manager. See Installation Guide, Manually Adding a Hypervisor from the Administration Portal for more information.
