Installation
|
Host Installation
|
A) Install Red Hat Enterprise Linux on a physical server
B) Install required additional packages for RHV
subscription-manager register
subscription-manager list --available
Attach required poolid from available repositories listed by previous command:
subscription-manager attach --pool=poolid
Make sure all requires repositories are attached:
subscription-manager list --consumed
yum repolist
subscription-manager repos --disable=*
subscription-manager repos \
--enable=rhel-7-server-rpms \
--enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
--enable=rhel-7-server-satellite-tools-6.5-rpms
yum update
Note: Reboot the machine if any kernel related packages have been updated.
C) Using cockpit for installation
yum install cockpit-ovirt-dashboard
systemctl enable cockpit.socket
systemctl start cockpit.socket
D) Add to the Manager
1. From the Administration Portal, click Compute → Hosts.
2. Click New.
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.
5-1. Enter the root user’s password to use password authentication.
652. Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.
6. Click the Advanced Parameters button to expand the advanced host settings.
6-1. Optionally disable automatic firewall configuration.
6-2. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
7. 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.
8. Click OK.
|
Self-Hosted Engine Installation
|
A) Install Red Hat Enterprise Linux on a physical server
B) Install required additional packages for RHV
subscription-manager register
subscription-manager list --available
Attach required poolid from available repositories listed by previous command:
subscription-manager attach --pool=poolid
Make sure all requires repositories are attached:
subscription-manager list --consumed
yum repolist
subscription-manager repos --disable="*"
subscription-manager repos \
--enable rhel-7-server-rpms \
--enable rhel-7-server-rhv-4-tools-rpms \
--enable rhel-7-server-rhv-4-mgmt-agent-rpms \
--enable rhel-7-server-optional-rpms \
--enable rhel-7-server-ansible-2.8-rpms \
--enable rhel-7-server-satellite-tools-6.5-rpms
yum update
Note: Reboot the machine if any kernel related packages have been updated.
C) Install the deployment tool
yum install ovirt-hosted-engine-setup
D) Install screen
Note: Red Hat recommends using the screen window manager to run the script to avoid losing the session in case of network or terminal disruption. Install and start screen:
yum install screen
screen
Note: In the event of session timeout or connection disruption, run screen -d -r to recover the deployment session.
E) Start the deployment script
hosted-engine --deploy
Note: To escape the script at any time, use the Ctrl+D keyboard combination to abort deployment.
1. Select Yes to begin the deployment:
Continuing will configure this host for serving as hypervisor and create a local VM with a running engine.
The locally running engine will be used to configure a storage domain and create a VM there.
At the end the disk of the local VM will be moved to the shared storage.
2. Are you sure you want to continue? (Yes, No)[Yes]:
3. Configure the network.
The script detects possible NICs to use as a management bridge for the environment.
3-1. Please indicate a pingable gateway IP address [X.X.X.X]:
3-2. Please indicate a nic to set ovirtmgmt bridge on: (eth1, eth0) [eth1]:
3-3. If you want to use a custom appliance for the virtual machine installation, enter the path to the OVA archive. Otherwise, leave this field empty to use the RHV-M Appliance.
3-4. If you want to deploy with a custom engine appliance image,
3-4-1. Please specify the path to the OVA archive you would like to use
(leave it empty to skip, the setup will use rhvm-appliance rpm installing it if missing):
4. Specify the FQDN for the Manager virtual machine:
4-1. Please provide the FQDN you would like to use for the engine appliance.
Note: This will be the FQDN of the engine VM you are now going to launch,
it should not point to the base host or to any other existing machine.
4-2. Engine VM FQDN: manager.example.com
4-3. Please provide the domain name you would like to use for the engine appliance.
4-4. Engine VM domain: [example.com]
5. Enter the root password for the Manager:
5-1. Enter root password that will be used for the engine appliance:
5-2. Confirm appliance root password:
6. Enter an SSH public key that will allow you to log in to the Manager as the root user, and specify whether to enable SSH access for the root user:
6-1. Enter ssh public key for the root user that will be used for the engine appliance (leave it empty to skip):
6-2. Do you want to enable ssh access for the root user (yes, no, without-password) [yes]:
7. Enter the virtual machine’s CPU and memory configuration:
7-1. Please specify the number of virtual CPUs for the VM (Defaults to appliance OVF value): [4]:
7-2. Please specify the memory size of the VM in MB (Defaults to maximum available): [7267]:
8. Enter a MAC address for the Manager virtual machine, or accept a randomly generated one. If you want to provide the Manager virtual machine with an IP address via DHCP, ensure that you have a valid DHCP reservation for this MAC address. The deployment script will not configure the DHCP server for you.
8-1. You may specify a unicast MAC address for the VM or accept a randomly generated default [00:16:3e:3d:34:47]:
9. Enter the virtual machine’s networking details:
9-1. How should the engine VM network be configured (DHCP, Static)[DHCP]?
9-2. If you specified Static, enter the IP address of the Manager:
Important: The static IP address must belong to the same subnet as the host. For example, if the host is in 10.1.1.0/24, the Manager virtual machine’s IP must be in the same subnet range (10.1.1.1-254/24).
9-3. Please enter the IP address to be used for the engine VM [x.x.x.x]:
9-4. Please provide a comma-separated list (max 3) of IP addresses of domain name servers for the engine VM
9-5. Engine VM DNS (leave it empty to skip):
10. Specify whether to add entries for the Manager virtual machine and the base host to the virtual machine’s /etc/hosts file. You must ensure that the host names are resolvable.
10-1. Add lines for the appliance itself and for this host to /etc/hosts on the engine VM?
Note: ensuring that this host could resolve the engine VM hostname is still up to you (Yes, No)[No]
11. Provide the name and TCP port number of the SMTP server, the email address used to send email notifications, and a comma-separated list of email addresses to receive these notifications:
11-1. Please provide the name of the SMTP server through which we will send notifications [localhost]:
11-2. Please provide the TCP port number of the SMTP server [25]:
11-3. Please provide the email address from which notifications will be sent [root@localhost]:
11-4. Please provide a comma-separated list of email addresses which will get notifications [root@localhost]:
12. Enter a password for the admin@internal user to access the Administration Portal:
12-1. Enter engine admin password:
12-2. Confirm engine admin password:
- The script creates the virtual machine. This can take some time if it needs to install the RHV-M Appliance.
13. Select the type of storage to use:
- Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]:
13-1. For NFS, enter the version, full address and path to the storage, and any mount options:
13-1-1. Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]:
13-1-2. Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs
13-1-3. If needed, specify additional mount options for the connection to the hosted-engine storage domain []:
13-2. For iSCSI, enter the portalails and select a target and LUN from the auto-detected lists. You cany select one iSCSI target during the deployment, but multipathing is ported to connect all portals of the same portal group.
Note: To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. See Red Hat Enterprise Linux DM Multipath for details. There is also a Multipath Helper tool that generates a script to install and configure multipath with different options.
13-2-1. Please specify the iSCSI portal IP address:
13-2-2. Please specify the iSCSI portal port [3260]:
13-2-3. Please specify the iSCSI discover user:
13-2-4. Please specify the iSCSI discover password:
13-2-5. Please specify the iSCSI portal login user:
13-2-6. Please specify the iSCSI portal login password:
13-2-6-1. The following targets have been found:
[1] iqn.2017-10.com.redhat.example:he
TPGT: 1, portals:
192.168.1.xxx:3260
192.168.2.xxx:3260
192.168.3.xxx:3260
13-2-6-2. Please select a target (1) [1]: 1
13-2-6-3. The following luns have been found on the requested target:
[1] 360003ff44dc75adcb5046390a16b4beb 199GiB MSFT Virtual HD
status: free, paths: 1 active
13-2-6-3. Please select the destination LUN (1) [1]:
13-3. For Gluster storage, enter the full address and path to the storage, and any mount options:
Important: Only replica 3 Gluster storage is supported. Ensure you have the following configuration:
13-3-1. In the /etc/glusterfs/glusterd.vol file on all three Gluster servers, set rpc-auth-allow-insecure to on.
13-3-1-1. option rpc-auth-allow-insecure on
13-3-2. Configure the volume as follows:
13-3-2-1. gluster volume set _volume_ cluster.quorum-type auto
13-3-2-2. gluster volume set _volume_ network.ping-timeout 10
13-3-2-3. gluster volume set _volume_ auth.allow \*
13-3-2-4. gluster volume set _volume_ group virt
13-3-2-5. gluster volume set _volume_ storage.owner-uid 36
13-3-2-6. gluster volume set _volume_ storage.owner-gid 36
13-3-2-7. gluster volume set _volume_ server.allow-insecure on
13-3-3. Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/gluster_volume
If needed, specify additional mount options for the connection to the hosted-engine storage domain []:
13-4. For Fibre Channel, select a LUN from the auto-detected list. The host bus adapters must be configured and connected, and the deployment script will auto-detect the LUNs available, and the LUN must not contain any existing data. To reuse an existing LUN, see Reusing LUNs in the Administration Guide.
13-4-1. The following luns have been found on the requested target:
[1] 3514f0c5447600351 30GiB XtremIO XtremApp
status: used, paths: 2 active
[2] 3514f0c5447600352 30GiB XtremIO XtremApp
status: used, paths: 2 active
Please select the destination LUN (1, 2) [1]:
14. Enter the Manager disk size:
14-1. Please specify the size of the VM disk in GB: [50]:
When the deployment completes successfully, one data center, cluster, host, storage domain, and the Manager virtual machine are already running. You can log in to the Administration Portal to add any other resources.
F) Login to the Manager
- Enable the required repositories on the Manager virtual machine. See Enabling the Red Hat Virtualization Manager Repositories in the Installation Guide.
subscription-manager repos --disable="*"
subscription-manager repos \
--enable rhel-7-server-rhv-4-tools-rpms \
--enable rhel-7-server-rhv-4-mgmt-agent-rpms \
--enable rhel-7-server-rpms \
--enable rhel-7-server-optional-rpms \
--enable rhel-7-server-ansible-2.8-rpms \
--enable rhel-7-server-satellite-tools-6.5-rpms
yum -y install \
katello-host-tools \
katello-host-tools-tracer \
katello-agent \
- Optionally, add a directory server using the ovirt-engine-extension-aaa-ldap-setup interactive setup script so you can add additional users to the environment. For more information, see Configuring an External LDAP Provider in the Administration Guide.
G) The Manager virtual machine, the host running it, and the self-hosted engine storage domain are flagged with a gold crown in the Administration Portal.
|
Engine / Manager Installation (RHVM)
|
A) Install RHEL on a physical server, a Virtual Machine, or a Cloud-based Instance
B) Install required additional packages
subscription-manager register
subscription-manager list --available
subscription-manager attach --pool=pool_id
yum repolist
subscription-manager repos --disable="*"
subscription-manager repos \
--enable=rhel-7-server-rpms \
--enable=rhel-7-server-supplementary-rpms \
--enable=rhel-7-server-rhv-4.2-manager-rpms \
--enable=rhel-7-server-rhv-4-manager-tools-rpms \
--enable=jb-eap-7-for-rhel-7-server-rpms \
yum update
Note: Reboot the machine if any kernel related packages have been updated.
yum install rhvm
C) Configuring the Red Hat Virtualization Manager
Run the engine-setup command to begin configuration of the Red Hat Virtualization Manager:
engine-setup
1. Press Enter to configure the Manager:
1-1. Configure Engine on this host (Yes, No) [Yes]:
2. Optionally allow engine-setup to configure the Image I/O Proxy (ovirt-imageio-proxy) to allow the Manager to upload virtual disks into storage domains.
Configure Image I/O Proxy on this host? (Yes, No) [Yes]:
3. Optionally allow engine-setup to configure a websocket proxy server for allowing users to connect to virtual machines via the noVNC or HTML 5 consoles:
Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:
To configure the websocket proxy on a separate machine, select No and refer to Appendix F, Installing a Websocket Proxy on a Separate Machine for configuration instructions.
4. Choose whether to configure Data Warehouse on the Manager machine.
Note: Data Warehouse is required for the engine. If you choose to not configure it on this host, you have to configure it on a remote host, and then configure the engine on this host so that it can access the database of the remote Data Warehouse host.
4-1. Configure Data Warehouse on this host (Yes, No) [Yes]:
4-2. To configure Data Warehouse on a separate machine, select No and see Installing and Configuring Data Warehouse on a Separate Machine in the Data Warehouse Guide for installation and configuration instructions.
5. Optionally allow access to a virtual machines’s serial console from the command line.
5-1. Configure VM Console Proxy on this host (Yes, No) [Yes]:
5-2. Additional configuration is required on the client machine to use this feature. See Opening a Serial Console to a Virtual Machine in the Virtual Machine Management Guide.
6. Optionally install Open Virtual Network (OVN). Selecting Yes will install an OVN central server on the Manager machine, and add it to Red Hat Virtualization as an external network provider. The default cluster will use OVN as its default network provider, and hosts added to the default cluster will automatically be configured to communicate with OVN.
6-1. Configure ovirt-provider-ovn (Yes, No) [Yes]:
6-2. For more information on using OVN networks in Red Hat Virtualization, see Adding Open Virtual Network (OVN) as an External Network Provider in Red Hat Administration Guide.
7. Press Enter to accept the automatically detected host name, or enter an alternative host name and press Enter. Note that the automatically detected host name may be incorrect if you are using virtual hosts.
7-1. Host fully qualified DNS name of this server [autodetected host name]:
8. The engine-setup command checks your firewall configuration and offers to modify that configuration to open the ports used by the Manager for external communication such as TCP ports 80 and 443. If you do not allow engine-setup to modify your firewall configuration, then you must manually open the ports used by the Manager. Firewalld will be configured as the firewall manager because iptables have been deprecated.
Setup can automatically configure the firewall on this system.
Note 1: automatic configuration of the firewall may overwrite current settings.
Note 2: iptables is deprecated and will be removed in future releases
8-1. Do you want Setup to configure the firewall? (Yes, No) [Yes]:
8-2. If you choose to automatically configure the firewall, and no firewall managers are active, you are prompted to select your chosen firewall manager from a list of supported options. Type the name of the firewall manager and press Enter. This applies even in cases where only one option is listed.
9. Choose to use either a local or remote PostgreSQL database as the Data Warehouse database:
9-1. Where is the DWH database located? (Local, Remote) [Local]:
9-1-1. If you select Local, the engine-setup command can configure your database automatically (including adding a user and a database), or it can connect to a preconfigured local database:
9-1-1-1. Setup can configure the local postgresql server automatically for the DWH to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and create DWH database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
9-1-1-1-1. If you select Automatic by pressing Enter, no further action is required here.
9-1-1-1-2. If you select Manual, input the following values for the manually-configured local database:
9-1-1-1-2-1. DWH database secured connection (Yes, No) [No]:
9-1-1-1-2-2. DWH database name [ovirt_engine_history]:
9-1-1-1-2-3. DWH database user [ovirt_engine_history]:
9-1-1-1-2-4. DWH database password:
Note: engine-setup requests these values after the Manager database is configured in the next step.
9-1-2. If you select Remote, input the following values for the preconfigured remote database host:
9-1-2-1. DWH database host [localhost]:
9-1-2-2. DWH database port [5432]:
9-1-2-3. DWH database secured connection (Yes, No) [No]:
9-1-2-4. DWH database name [ovirt_engine_history]:
9-1-2-5. DWH database user [ovirt_engine_history]:
9-1-2-6. DWH database password:
Note: engine-setup requests these values after the Manager database is configured in the next step.
10. Choose to use either a local or remote PostgreSQL database as the Manager database:
10-1. Where is the Engine database located? (Local, Remote) [Local]:
10-1-1. If you select Local, the engine-setup command can configure your database automatically (including adding a user and a database), or it can connect to a preconfigured local database:
10-1-1-1. Setup can configure the local postgresql server automatically for the engine to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql and create Engine database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
10-1-1-1-1. If you select Automatic by pressing Enter, no further action is required here.
10-1-1-1-1. If you select Manual, input the following values for the manually-configured local database:
10-1-1-1-2-1. Engine database secured connection (Yes, No) [No]:
10-1-1-1-2-2. Engine database name [engine]:
10-1-1-1-2-3. Engine database user [engine]:
10-1-1-1-2-4. Engine database password:
10-1-2. If you select Remote, input the following values for the preconfigured remote database host:
10-1-2-1. Engine database host [localhost]:
10-1-2-2. Engine database port [5432]:
10-1-2-3. Engine database secured connection (Yes, No) [No]:
10-1-2-4. Engine database name [engine]:
10-1-2-5. Engine database user [engine]:
10-1-2-6. Engine database password:
11. Set a password for the automatically created administrative user of the Red Hat Virtualization Manager:
11-1. Engine admin password:
11-1. Confirm engine admin password:
12. Select Gluster, Virt, or Both:
12-1. Application mode (Both, Virt, Gluster) [Both]:
12-1-1. Both offers the greatest flexibility. In most cases, select Both. Virt application mode allows you to run virtual machines in the environment; Gluster application mode only allows you to manage GlusterFS from the Administration Portal.
13. If you installed the OVN provider, you can choose to use the default credentials, or specify an alternative.
13-1. Use default credentials (admin@internal) for ovirt-provider-ovn (Yes, No) [Yes]:
13-1-1. oVirt OVN provider user[admin@internal]:
13-1-2. oVirt OVN provider password:
14. Set the default value for the wipe_after_delete flag, which wipes the blocks of a virtual disk when the disk is deleted.
14-1. Default SAN wipe after delete (Yes, No) [No]:
15. The Manager uses certificates to communicate securely with its hosts. This certificate can also optionally be used to secure HTTPS communications with the Manager. Provide the organization name for the certificate:
15-1. Organization name for certificate [autodetected domain-based name]:
16. Optionally allow engine-setup to make the landing page of the Manager the default page presented by the Apache web server:
16-1. Setup can configure the default page of the web server to present the application home page. This may conflict with existing applications.
16-1-1. Do you wish to set the application as the default web page of the server? (Yes, No) [Yes]:
17. By default, external SSL (HTTPS) communication with the Manager is secured with the self-signed certificate created earlier in the configuration to securely communicate with hosts. Alternatively, choose another certificate for external HTTPS connections; this does not affect how the Manager communicates with hosts:
17-1. Setup can configure apache to use SSL using a certificate issued from the internal CA.
17-1-1. Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
17-2. Choose how long Data Warehouse will retain collected data:
Note: This step is skipped if you chose not to configure Data Warehouse on the Manager machine.
17-2-1. Please choose Data Warehouse sampling scale:
(1) Basic
(2) Full
(1, 2)[1]:
17-2-1-1. Full uses the default values for the data storage settings listed in the Data Warehouse Guide (recommended when Data Warehouse is installed on a remote host).
17-2-1-2. Basic reduces the values of DWH_TABLES_KEEP_HOURLY to 720 and DWH_TABLES_KEEP_DAILY to 0, easing the load on the Manager machine (recommended when the Manager and Data Warehouse are installed on the same machine).
18. Review the installation settings, and press Enter to accept the values and proceed with the installation:
18-1. Please confirm installation settings (OK, Cancel) [OK]:
18-1-1. When your environment has been configured, engine-setup displays details about how to access your environment. If you chose to manually configure the firewall, engine-setup provides a custom list of ports that need to be opened, based on the options selected during setup. The engine-setup command also saves your answers to a file that can be used to reconfigure the Manager using the same values, and outputs the location of the log file for the Red Hat Virtualization Manager configuration process.
19. If you intend to link your Red Hat Virtualization environment with a directory server, configure the date and time to synchronize with the system clock used by the directory server to avoid unexpected account expiry issues. See Synchronizing the System Clock with a Remote Server in the Red Hat Enterprise Linux System Administrator’s Guide for more information.
20. Install the certificate authority according to the instructions provided by your browser. You can get the certificate authority’s certificate by navigating to `http://your-manager-fqdn/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA`, replacing your-manager-fqdn with the fully qualified domain name (FQDN) that you provided during the installation.
D) Connecting to the Admin Portal
1. In a web browser, navigate to https://your-manager-fqdn/ovirt-engine, replacing your-manager-fqdn with the fully qualified domain name that you provided during installation.
Note: You can access the Administration Portal using alternate host names or IP addresses. To do so, you need to add a configuration file under /etc/ovirt-engine/engine.conf.d/. For example:
vi /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf
SSO_ALTERNATE_ENGINE_FQDNS="alias1.example.com alias2.example.com"
The list of alternate host names needs to be separated by spaces. You can also add the IP address of the Manager to the list, but using IP addresses instead of DNS-resolvable host names is not recommended.
2. Click Administration Portal. An SSO login page displays. SSO login enables you to log in to the Administration and VM Portal at the same time.
3. Enter your User Name and Password. If you are logging in for the first time, use the user name admin in conjunction with the password that you specified during installation.
4. Select the domain against which to authenticate from the Domain list. If you are logging in using the internal admin user name, select the internal domain.
5. Click Log In.
6. You can view the Administration Portal in multiple languages. The default selection will be chosen based on the locale settings of your web browser. If you would like to view the Administration Portal in a language other than the default, select your preferred language from the drop-down list on the welcome page.
|
Adding New Hosts
|
A) Install Red Hat Enterprise Linux on a physical server
B) Install required additional packages for RHV
subscription-manager register
subscription-manager list --available
Attach required poolid from available repositories listed by previous command:
subscription-manager attach --pool=poolid
Make sure all requires repositories are attached:
subscription-manager list --consumed
yum repolist
subscription-manager repos --disable=*
subscription-manager repos \
--enable=rhel-7-server-rpms \
--enable=rhel-7-server-rhv-4-mgmt-agent-rpms \
--enable=rhel-7-server-satellite-tools-6.5-rpms
yum update
Note: Reboot the machine if any kernel related packages have been updated.
C) Add to the Manager
1. From the Administration Portal, click Compute → Hosts.
2. Click New.
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.
5-1. Enter the root user’s password to use password authentication.
5-2. Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.
6. Click the Advanced Parameters button to expand the advanced host settings.
6-1. Optionally disable automatic firewall configuration.
6-2. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
7. 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.
8. Click OK.
D) Deploy a Self-Hosted Engine
1. Click Compute → Hosts and select the host.
2. Click Management → Maintenance and click OK.
3. Click Installation → Reinstall.
4. Click the Hosted Engine tab and select DEPLOY from the drop-down list.
5. Click OK.
|