Installation Guide

Procedure 2.1. Checking if a Processor Supports the Required Flags

1. At the host's boot screen, press any key and select the Boot or Boot with serial console entry from the list.
2. Press Tab to edit the kernel parameters for the selected option.
3. Ensure there is a Space after the last kernel parameter listed, and append the rescue parameter.
4. Press Enter to boot into rescue mode.
5. At the prompt which appears, determine that your processor has the required extensions and that they are enabled by running this command:

   # grep -E 'svm|vmx' /proc/cpuinfo | grep nx

   If any output is shown, then the processor is hardware virtualization capable. If no output is shown, then it is still possible that your processor supports hardware virtualization. In some circumstances manufacturers disable the virtualization extensions in the BIOS. If you believe this to be the case, consult the system's BIOS and the motherboard manual provided by the manufacturer.

Procedure 5.1. Installing and Configuring Data Warehouse and Reports on the Red Hat Enterprise Virtualization Manager

1. Install the rhevm-dwh package and the rhevm-reports package on the system where the Red Hat Enterprise Virtualization Manager is installed:

   # yum install rhevm-dwh rhevm-reports

2. Run the engine-setup command to begin configuration of Data Warehouse and Reports on the machine:

   # engine-setup

3. Follow the prompts to configure Data Warehouse and Reports:

   Configure Data Warehouse on this host (Yes, No) [Yes]: 
   Configure Reports on this host (Yes, No) [Yes]:

4. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   Do you want Setup to configure the firewall? (Yes, No) [Yes]:

   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.
5. Answer the following questions about the Data Warehouse database and the Reports database:

   Where is the DWH database located? (Local, Remote) [Local]: 
   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]: 
   Where is the Reports database located? (Local, Remote) [Local]: 
   Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
   Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:

   Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about each remote database host.
6. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:

   Reports power users password:

   You are prompted to enter the password a second time to confirm it.
7. For the configuration to take effect, the ovirt-engine service must be restarted. The engine-setup command prompts you:

   During execution engine service will be stopped (OK, Cancel) [OK]:

   Press Enter to proceed. The ovirt-engine service restarts automatically later in the command.
8. Confirm your installation settings:

   Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.2. Installing and Configuring Data Warehouse and Reports Together on a Separate Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

4. Disable all existing repositories:

   # subscription-manager repos --disable=*

5. Enable the required repositories:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

6. Ensure that all packages currently installed are up to date:

   # yum update

7. Install the rhevm-dwh-setup and rhevm-reports-setup packages:

   # yum install rhevm-dwh-setup rhevm-reports-setup

8. Run the engine-setup command to begin configuration of Data Warehouse and Reports on the machine:

   # engine-setup

9. Follow the prompts to configure Data Warehouse and Reports:

   Configure Data Warehouse on this host (Yes, No) [Yes]: 
   Configure Reports on this host (Yes, No) [Yes]:

10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]:

    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.
11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

    Host fully qualified DNS name of this server [autodetected hostname]:

12. Enter the fully qualified domain name of the Manager machine, and then press Enter:

    Host fully qualified DNS name of the engine server []:

13. Answer the following questions about the Data Warehouse database and the Reports database:

    Where is the DWH database located? (Local, Remote) [Local]: 
    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]: 
    Where is the Reports database located? (Local, Remote) [Local]: 
    Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
    Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:

    Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about each remote database host.
14. Enter the fully qualified domain name and password for the Manager database machine. Press Enter to accept the default values in each other field:

    Engine database host []: engine-db-fqdn
    Engine database port [5432]: 
    Engine database secured connection (Yes, No) [No]: 
    Engine database name [engine]: 
    Engine database user [engine]: 
    Engine database password: password

15. Press Enter to allow setup to sign the Reports certificate and Apache certificate on the Manager via SSH:

    Setup will need to do some actions on the remote engine server. Either automatically, using ssh as root to access it, or you will be prompted to manually perform each such action.
    Please choose one of the following:
    1 - Access remote engine server using ssh as root
    2 - Perform each action manually, use files to copy content around
    (1, 2) [1]:

16. Press Enter to accept the default SSH port, or enter an alternative port number and then press Enter:

    ssh port on remote engine server [22]:

17. Enter the root password for the Manager machine:

    root password on remote engine server manager-fqdn.com:

18. Press Enter to allow automatic configuration of SSL on Apache:

    Setup can configure apache to use SSL using a certificate issued from the internal CA.
    Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

19. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:

    Reports power users password:

    You are prompted to enter the password a second time to confirm it.
20. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.3. Step 1: Installing and Configuring Data Warehouse on a Separate Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

4. Disable all existing repositories:

   # subscription-manager repos --disable=*

5. Enable the required repositories:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

6. Ensure that all packages currently installed are up to date:

   # yum update

7. Install the rhevm-dwh-setup package:

   # yum install rhevm-dwh-setup

8. Run the engine-setup command to begin configuration of Data Warehouse on the machine:

   # engine-setup

9. Press Enter to configure Data Warehouse:

   Configure Data Warehouse on this host (Yes, No) [Yes]:
   

10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]:

    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.
11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

    Host fully qualified DNS name of this server [autodetected host name]:

12. Answer the following questions about the Data Warehouse database:

    Where is the DWH database located? (Local, Remote) [Local]: 
    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]:
    

    Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about the remote database host.
13. Enter the fully qualified domain name and password for the Manager database machine. Press Enter to accept the default values in each other field:

    Engine database host []: engine-db-fqdn
    Engine database port [5432]: 
    Engine database secured connection (Yes, No) [No]: 
    Engine database name [engine]: 
    Engine database user [engine]: 
    Engine database password: password

14. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:
    

Procedure 5.4. Step 2: Installing and Configuring Reports on a Separate Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find subscription pools containing the repositories required to install Reports:

   # subscription-manager list --available | grep -A8 "Red Hat Enterprise Linux Server"
   # subscription-manager list --available | grep -A8 "Red Hat Enterprise Virtualization"

3. Use the pool identifiers located in the previous step to attach the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization entitlements to the system:

   # subscription-manager attach --pool=pool_id

4. Disable all existing repositories:

   # subscription-manager repos --disable=*

5. Enable the required repositories:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

6. Ensure that all packages currently installed are up to date:

   # yum update

7. Install the rhevm-reports-setup package:

   # yum install rhevm-reports-setup

8. Run the engine-setup command to begin configuration of Reports on the machine:

   # engine-setup

9. Press Enter to configure Reports:

   Configure Reports on this host (Yes, No) [Yes]:
   

10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]:

    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.
11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

    Host fully qualified DNS name of this server [autodetected host name]:

12. Enter the fully qualified domain name of the Manager machine, and then press Enter:

    Host fully qualified DNS name of the engine server []:

13. Answer the following questions about the Reports database:

    Where is the Reports database located? (Local, Remote) [Local]: 
    Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
    Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

    Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about the remote database host.
14. Enter the fully qualified domain name and password for your Data Warehouse database host. Press Enter to accept the default values in each other field:

    DWH database host []: dwh-db-fqdn
    DWH database port [5432]: 
    DWH database secured connection (Yes, No) [No]: 
    DWH database name [ovirt_engine_history]: 
    DWH database user [ovirt_engine_history]: 
    DWH database password: password

15. Press Enter to allow setup to sign the Reports certificate and Apache certificate on the Manager via SSH:

    Setup will need to do some actions on the remote engine server. Either automatically, using ssh as root to access it, or you will be prompted to manually perform each such action.
    Please choose one of the following:
    1 - Access remote engine server using ssh as root
    2 - Perform each action manually, use files to copy content around
    (1, 2) [1]:

16. Press Enter to accept the default SSH port, or enter an alternative port number and then press Enter:

    ssh port on remote engine server [22]:

17. Enter the root password for the Manager machine:

    root password on remote engine server manager-fqdn.com:

18. Press Enter to allow automatic configuration of SSL on Apache:

    Setup can configure apache to use SSL using a certificate issued from the internal CA.
    Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

19. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:

    Reports power users password:

    You are prompted to enter the password a second time to confirm it.
20. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.5. Step 1: Installing and Configuring Data Warehouse on the Manager Machine

1. Install the rhevm-dwh package:

   # yum install rhevm-dwh

2. Run the engine-setup command to begin configuration of Data Warehouse on the machine:

   # engine-setup

3. Press Enter to configure Data Warehouse:

   Configure Data Warehouse on this host (Yes, No) [Yes]:
   

4. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   Do you want Setup to configure the firewall? (Yes, No) [Yes]:

   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.
5. Answer the following questions about the Data Warehouse database:

   Where is the DWH database located? (Local, Remote) [Local]: 
   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]:
   

   Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about the remote database host.
6. For the configuration to take effect, the ovirt-engine service must be restarted. The engine-setup command prompts you:

   During execution engine service will be stopped (OK, Cancel) [OK]:

   Press Enter to proceed. The ovirt-engine service restarts automatically later in the command.
7. Confirm your installation settings:

   Please confirm installation settings (OK, Cancel) [OK]:
   

Procedure 5.6. Step 2: Installing and Configuring Reports on a Separate Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

4. Disable all existing repositories:

   # subscription-manager repos --disable=*

5. Enable the required channels:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

6. Ensure that all packages currently installed are up to date:

   # yum update

7. Install the rhevm-reports-setup package:

   # yum install rhevm-reports-setup

8. Run the engine-setup command to begin configuration of Reports on the machine:

   # engine-setup

9. Press Enter to configure Reports:

   Configure Reports on this host (Yes, No) [Yes]:
   

10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]:

    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.
11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

    Host fully qualified DNS name of this server [autodetected host name]:

12. Enter the fully qualified domain name of the Manager machine, and then press Enter:

    Host fully qualified DNS name of the engine server []:

13. Answer the following questions about the Reports database:

    Where is the Reports database located? (Local, Remote) [Local]: 
    Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
    Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

    Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about the remote database host.
14. Enter the fully qualified domain name and password for your Data Warehouse database host. Press Enter to accept the default values in each other field:

    DWH database host []: dwh-db-fqdn
    DWH database port [5432]: 
    DWH database secured connection (Yes, No) [No]: 
    DWH database name [ovirt_engine_history]: 
    DWH database user [ovirt_engine_history]: 
    DWH database password: password

15. Press Enter to allow setup to sign the Reports certificate and Apache certificate on the Manager via SSH:

    Setup will need to do some actions on the remote engine server. Either automatically, using ssh as root to access it, or you will be prompted to manually perform each such action.
    Please choose one of the following:
    1 - Access remote engine server using ssh as root
    2 - Perform each action manually, use files to copy content around
    (1, 2) [1]:

16. Press Enter to accept the default SSH port, or enter an alternative port number and then press Enter:

    ssh port on remote engine server [22]:

17. Enter the root password for the Manager machine:

    root password on remote engine server manager-fqdn.com:

18. Press Enter to allow automatic configuration of SSL on Apache:

    Setup can configure apache to use SSL using a certificate issued from the internal CA.
    Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

19. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:

    Reports power users password:

    You are prompted to enter the password a second time to confirm it.
20. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.7. Step 1: Installing and Configuring Data Warehouse on a Separate Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

4. Disable all existing repositories:

   # subscription-manager repos --disable=*

5. Enable the required channels:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

6. Ensure that all packages currently installed are up to date:

   # yum update

7. Install the rhevm-dwh-setup package:

   # yum install rhevm-dwh-setup

8. Run the engine-setup command to begin configuration of Data Warehouse on the machine:

   # engine-setup

9. Press Enter to configure Data Warehouse:

   Configure Data Warehouse on this host (Yes, No) [Yes]:
   

10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]:

    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.
11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

    Host fully qualified DNS name of this server [autodetected host name]:

12. Answer the following questions about the Data Warehouse database:

    Where is the DWH database located? (Local, Remote) [Local]: 
    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]:
    

    Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about the remote database host.
13. Enter the fully qualified domain name and password for the Manager database machine. Press Enter to accept the default values in each other field:

    Engine database host []: engine-db-fqdn
    Engine database port [5432]: 
    Engine database secured connection (Yes, No) [No]: 
    Engine database name [engine]: 
    Engine database user [engine]: 
    Engine database password: password

14. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:
    

Procedure 5.8. Step 2: Installing and Configuring Reports on the Manager Machine

1. Install the rhevm-reports package:

   # yum install rhevm-reports

2. Run the engine-setup command to begin configuration of Reports on the machine:

   # engine-setup

3. Press Enter to configure Reports:

   Configure Reports on this host (Yes, No) [Yes]:
   

4. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   Do you want Setup to configure the firewall? (Yes, No) [Yes]:

   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.
5. Answer the following questions about the Reports database:

   Where is the Reports database located? (Local, Remote) [Local]: 
   Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
   Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
   

   Press Enter to choose the highlighted defaults, or type your alternative preference and then press Enter. If you select Remote, you are prompted to provide details about the remote database host.
6. Enter the fully qualified domain name and password for your Data Warehouse database host. Press Enter to accept the default values in each other field:

   DWH database host []: dwh-db-fqdn
   DWH database port [5432]: 
   DWH database secured connection (Yes, No) [No]: 
   DWH database name [ovirt_engine_history]: 
   DWH database user [ovirt_engine_history]: 
   DWH database password: password

7. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:

   Reports power users password:

   You are prompted to enter the password a second time to confirm it.
8. For the configuration to take effect, the ovirt-engine service must be restarted. The engine-setup command prompts you:

   During execution engine service will be stopped (OK, Cancel) [OK]:

   Press Enter to proceed. The ovirt-engine service restarts automatically later in the command.
9. Confirm your installation settings:

   Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.9. Migrating the Data Warehouse Database to a Separate Machine

1. On the existing database machine, dump the ovirt_engine_history database into a SQL script file:

   # pg_dump ovirt_engine_history > ovirt_engine_history.sql

2. Copy the script file from the existing database machine to the new database machine.
3. Restore the ovirt_engine_history database on the new database machine:

   # psql -d ovirt_engine_history -f ovirt_engine_history.sql

   The command above assumes that the database on the new machine is also named ovirt_engine_history.

Procedure 5.10. Step 1: Setting up the New Data Warehouse Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

4. Disable all existing repositories:

   # subscription-manager repos --disable=*

5. Enable the required channels:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

6. Ensure that all packages currently installed are up to date:

   # yum update

7. Install the rhevm-dwh-setup package:

   # yum install rhevm-dwh-setup

Procedure 5.11. Step 2: Stopping the Data Warehouse Service on the Manager Machine

1. Stop the Data Warehouse service:

   # service ovirt-engine-dwhd stop

2. If the ovirt_engine_history database, the Manager database, or both are hosted on the Manager machine and were configured by a previous version (Red Hat Enterprise Virtualization 3.4 or prior) that was then upgraded, you must allow the new Data Warehouse machine to access them. Edit the /var/lib/pgsql/data/postgresql.conf file and modify the listen_addresses line so that it matches the following:

   listen_addresses = '*'

   If the line does not exist or has been commented out, add it manually.
   If one or both databases are hosted on a remote machine, you must manually grant access by editing the postgres.conf file on each machine, and adding the listen_addresses line, as above. If both databases are hosted on the Manager machine and were configured during a clean setup of Red Hat Enterprise Virtualization Manager 3.5, access is granted by default.
3. Restart the postgresql service:

   # service postgresql restart

Procedure 5.12. Step 3: Configuring the New Data Warehouse Machine

1. Run the engine-setup command to begin configuration of Data Warehouse on the machine:

   # engine-setup

2. Press Enter to configure Data Warehouse:

   Configure Data Warehouse on this host (Yes, No) [Yes]:
   

3. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   Do you want Setup to configure the firewall? (Yes, No) [Yes]:

   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.
4. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

   Host fully qualified DNS name of this server [autodetected host name]:

5. Answer the following question about the location of the ovirt_engine_history database:

   Where is the DWH database located? (Local, Remote) [Local]: Remote
   

   Type the alternative option as shown above and then press Enter.
6. Enter the fully qualified domain name and password for your ovirt_engine_history database host. Press Enter to accept the default values in each other field:

   DWH database host []: dwh-db-fqdn
   DWH database port [5432]: 
   DWH database secured connection (Yes, No) [No]: 
   DWH database name [ovirt_engine_history]: 
   DWH database user [ovirt_engine_history]: 
   DWH database password: password

7. Enter the fully qualified domain name and password for the Manager database machine. Press Enter to accept the default values in each other field:

   Engine database host []: engine-db-fqdn
   Engine database port [5432]: 
   Engine database secured connection (Yes, No) [No]: 
   Engine database name [engine]: 
   Engine database user [engine]: 
   Engine database password: password

8. Press Enter to create a backup of the existing Data Warehouse database:

   Would you like to backup the existing database before upgrading it? (Yes, No) [Yes]:

   The time and space required for the database backup depends on the size of the database. It may take several hours to complete. If you choose not to back up the database here, and engine-setup fails for any reason, you will not be able to restore the database or any of the data within it. The location of the backup file appears at the end of the setup script.
9. Confirm that you want to permanently disconnect the existing Data Warehouse service from the Manager:

   Do you want to permanently disconnect this DWH from the engine? (Yes, No) [No]:

10. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:
    

Procedure 5.13. Step 4: Removing the Data Warehouse Package from the Manager Machine

1. Remove the Data Warehouse package:

   # yum remove rhevm-dwh

   This step prevents the Data Warehouse service from attempting to automatically restart after an hour.
2. Remove the Data Warehouse files:

   # rm -rf /etc/ovirt-engine-dwh /var/lib/ovirt-engine-dwh

Procedure 5.14. Step 1: Configuring the New Reports Machine

1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

   # subscription-manager register

2. Find the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization subscription pools and note down the pool IDs.

   # subscription-manager list --available

3. Use the pool IDs located in the previous step to attach the entitlements to the system:

   # subscription-manager attach --pool=pool_id

4. Disable all existing repositories:

   # subscription-manager repos --disable=*

5. Enable the required channels:

   # subscription-manager repos --enable=rhel-6-server-rpms
   # subscription-manager repos --enable=rhel-6-server-supplementary-rpms
   # subscription-manager repos --enable=rhel-6-server-rhevm-3.6-rpms
   # subscription-manager repos --enable=jb-eap-6-for-rhel-6-server-rpms

6. Ensure that all packages currently installed are up to date:

   # yum update

7. Install the rhevm-reports-setup package:

   # yum install rhevm-reports-setup

8. Run the engine-setup command to begin configuration of Reports on the machine:

   # engine-setup

9. Press Enter to configure Reports:

   Configure Reports on this host (Yes, No) [Yes]:
   

10. Press Enter to automatically configure the firewall, or type No and press Enter to maintain existing settings:

    Setup can automatically configure the firewall on this system.
    Note: automatic configuration of the firewall may overwrite current settings.
    Do you want Setup to configure the firewall? (Yes, No) [Yes]:

    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.
11. Press Enter to accept the automatically detected hostname, or enter an alternative hostname and press Enter:

    Host fully qualified DNS name of this server [autodetected host name]:

12. Enter the fully qualified domain name of the Manager machine, and then press Enter:

    Host fully qualified DNS name of the engine server []:

13. Answer the following questions about the ovirt_engine_reports database. Press Enter to allow setup to create and configure a local database:

    Where is the Reports database located? (Local, Remote) [Local]:
    Setup can configure the local postgresql server automatically for the Reports to run. This may conflict with existing applications.
    Would you like Setup to automatically configure postgresql and create Reports database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

14. Enter the fully qualified domain name and password for your ovirt_engine_history database host. Press Enter to accept the default values in each other field:

    DWH database host []: dwh-db-fqdn
    DWH database port [5432]: 
    DWH database secured connection (Yes, No) [No]: 
    DWH database name [ovirt_engine_history]: 
    DWH database user [ovirt_engine_history]: 
    DWH database password: password

15. Press Enter to allow setup to sign the Reports certificate and Apache certificate on the Manager via SSH:

    Setup will need to do some actions on the remote engine server. Either automatically, using ssh as root to access it, or you will be prompted to manually perform each such action.
    Please choose one of the following:
    1 - Access remote engine server using ssh as root
    2 - Perform each action manually, use files to copy content around
    (1, 2) [1]:

16. Press Enter to accept the default SSH port, or enter an alternative port number and then press Enter:

    ssh port on remote engine server [22]:

17. Enter the root password for the Manager machine:

    root password on remote engine server manager-fqdn.com:

18. Press Enter to allow automatic configuration of SSL on Apache:

    Setup can configure apache to use SSL using a certificate issued from the internal CA.
    Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
    

19. Set a password for the Reports administrative users (admin and superuser). Note that the reports system maintains its own set of credentials that are separate to those used for the Manager:

    Reports power users password:

    You are prompted to enter the password a second time to confirm it.
20. Confirm your installation settings:

    Please confirm installation settings (OK, Cancel) [OK]:

Procedure 5.15. Step 2: Migrating Saved Reports to the New Reports Machine

1. On the Manager machine, run the ovirt-engine-reports-tool command:

   # ovirt-engine-reports-tool
   

2. Enter the number that corresponds to the export option, and press Enter:

   (2) Export Jasperreports saved reports to a zip file
   (1, 2, 3) []: 2
   

3. Enter the absolute path for the zip file to export saved reports to, and press Enter:

   Filename to export saved reports to: /tmp/saved-reports.zip

4. Copy the zip file to the new Reports machine:

   # scp /tmp/saved-reports.zip reports-machine-fqdn:/tmp/

5. On the new Reports machine, run the ovirt-engine-reports-tool command:

   # ovirt-engine-reports-tool
   

6. Enter the number that corresponds to the import option, and press Enter:

   (3) Import a saved reports zip file to Jasperreports
   (1, 2, 3) []: 3

7. Enter the absolute path of the zip file from which to import, and press Enter:

   Filename to import saved reports from: /tmp/saved-reports.zip

Procedure 5.16. Step 3: Removing the Reports Service from the Manager Machine

1. Stop the Reports service:

   # service ovirt-engine-reportsd stop

2. Remove the Reports package:

   # yum remove rhevm-reports

3. Remove the Reports files:

   # rm -rf /etc/ovirt-engine-reports /var/lib/ovirt-engine-reports

4. Remove the Reports database and user. The default name for both is ovirt_engine_reports:

   # su - postgres
   $ psql
   postgres=# drop database ovirt_engine_reports;
   postgres=# drop user ovirt_engine_reports;
   

Procedure 7.2. Installing the edit-node Tool

1. Log in to the system on which to modify the Red Hat Enterprise Virtualization Hypervisor ISO file.
2. Enable the required repository:
   • For Red Hat Enterprise Linux 6:

     # subscription-manager repos --enable=rhel-6-server-rhevh-rpms

   • For Red Hat Enterprise Linux 7:

     # subscription-manager repos --enable=rhel-7-server-rhevh-rpms

3. Install the ovirt-node-tools package:

   # yum install ovirt-node-tools

Procedure 7.4. Preparing USB Installation Media using dd on Linux Systems

1. Run the following command to ensure you have the latest version of the Red Hat Enterprise Virtualization Hypervisor disk image:
   • For Red Hat Enterprise Linux 6:

     # yum update rhev-hypervisor6

   • For Red Hat Enterprise Linux 7:

     # yum update rhev-hypervisor7

2. Use the dd utility to write the disk image to a USB storage device.

   Example 7.10. Use of dd

   This example uses a USB storage device named /dev/sdc.

   # dd if=/usr/share/rhev-hypervisor/rhev-hypervisor.iso of=/dev/sdc
   243712+0 records in
   243712+0 records out
   124780544 bytes (125 MB) copied, 56.3009 s, 2.2 MB/s
   

   Warning

   The dd utility will overwrite all data on the device specified by the of parameter. Ensure you have specified the correct device and that the device contains no valuable data before using the dd utility.

Procedure 7.5. Preparing USB Installation Media using dd on Windows Systems

1. Open http://www.redhat.com/services/custom/cygwin/ in a web browser and click 32-bit Cygwin to download the 32-bit version of Red Hat Cygwin, or 64-bit Cygwin to download the 64-bit version of Red Hat Cygwin.
2. Run the downloaded executable as a user with administrator privileges to open the Red Hat Cygwin installation program.
3. Follow the prompts to install Red Hat Cygwin. The Coreutils package in the Base package group provides the dd utility. This package is automatically selected for installation.
4. Copy the rhev-hypervisor.iso file downloaded from the Content Delivery Network to C:\rhev-hypervisor.iso.
5. Run the Red Hat Cygwin application from the desktop as a user with administrative privileges.

   Important

   On the Windows 7 and Windows Server 2008, you must right-click the Red Hat Cygwin icon and select the Run as Administrator option to ensure the application runs with the correct permissions.
6. In the terminal, run the following command to view the drives and partitions currently visible to the system:

   $ cat /proc/partitions

   Example 7.11. View of Disk Partitions Attached to System

   Administrator@test /
   $ cat /proc/partitions
   major minor  #blocks  name
       8     0  15728640 sda
       8     1    102400 sda1
       8     2  15624192 sda2

7. Attach the USB storage device to which the Red Hat Enterprise Virtualization Hypervisor disk image will be written to the system. Run the cat /proc/partitions command again and compare the output to that of the previous output. A new entry will appear that designates the USB storage device.

   Example 7.12. View of Disk Partitions Attached to System

   Administrator@test /
   $ cat /proc/partitions
   major minor  #blocks  name
       8     0  15728640 sda
       8     1    102400 sda1
       8     2  15624192 sda2
       8    16    524288 sdb
   

8. Use the dd utility to write the rhev-hypervisor.iso file to the USB storage device. The following example uses a USB storage device named /dev/sdb. Replace sdb with the correct device name for the USB storage device to be used.

   Example 7.13. Use of dd Utility Under Red Hat Cygwin

   Administrator@test /
   $ dd if=/cygdrive/c/rhev-hypervisor.iso of=/dev/sdb& pid=$!
   

   Warning

   The dd utility will overwrite all data on the device specified by the of parameter. Ensure you have specified the correct device and that the device contains no valuable data before using the dd utility.

   Note

   Writing disk images to USB storage devices with the version of the dd utility included with Red Hat Cygwin can take significantly longer than the equivalent on other platforms. You can run the following command to view the progress of the operation:

   $ kill -USR1 $pid

Procedure 7.6. Preparing Optical Hypervisor Installation Media

1. Install the wodim package and dependencies:

   # yum install wodim
   

2. Insert a blank CD-ROM or DVD into your CD or DVD writer.
3. Write the disk image to the disc:

   wodim dev=[device] [image]

   Note

   To find out the name of your writer device, run the following command:

   # less /proc/sys/dev/cdrom/info

   Example 7.14. Use of the wodim Utility

   This example uses the first CD-RW (/dev/sr0) device available and an example unified installer disk image location.

   # wodim dev=/dev/sr0 /usr/share/rhev-hypervisor/rhev-hypervisor.iso
   

1. The ovirt-early service sets storage, network and management parameters in the /etc/default/ovirt file. These parameters are determined from the kernel arguments passed to the Hypervisor during the boot sequence.
2. The /etc/init.d/ovirt-firstboot script determines the type of installation to perform based on the parameters set on the kernel command line or the TUI installation.

Procedure 7.7. Configuring the Host Name, DNS, and NTP

1. In the text user interface, select the Network screen, press the right arrow key and enter a new host name in the Hostname field.
2. Select the DNS Server 1 field and enter the IP address of the primary DNS server. Optionally set a secondary DNS server.
3. Select the NTP Server 1 field and enter the IP address or host name of the primary NTP server. Optionally set a secondary NTP server.
4. Select <Save> and press Enter to save the changes. You must save before you proceed to edit the network interfaces.

Procedure 7.8. Configuring Network Interfaces

1. Select a network interface from the list beneath Available System NICs and press Enter to configure that network interface.

   Note

   To identify the physical network interface card associated with the selected network interface, select <Flash Lights to Identify> and press Enter.
2. Choose to configure IPv4 or IPv6.
   • Configure a dynamic or static IP address for IPv4:
     • Select DHCP under IPv4 Settings and press the space bar to configure a dynamic IP address.
     • Select Static under IPv4 Settings, press the space bar, and input the IP Address, Netmask, and Gateway that the Hypervisor will use to configure a static IP address.

       Example 7.17. Static IPv4 Networking Configuration

       IPv4 Settings
       ( ) Disabled     ( ) DHCP     (*) Static
       IP Address: 192.168.122.100_  Netmask: 255.255.255.0___
       Gateway     192.168.1.1_____
       

   • Configure a stateless, dynamic, or static IP for IPv6:
     • Select Auto under IPv6 Settings and press the space bar to configure stateless auto configuration.
     • Select DHCP under IPv6 Settings and press the space bar to configure a dynamic IP address.
     • Select Static under IPv6 Settings, press the space bar, and input the IP Address, Prefix Length, and Gateway that the Hypervisor will use to configure a static IP address.

       Example 7.18. Static IPv6 Networking Configuration

       IPv6 Settings
       ( ) Disabled     ( ) Auto     ( ) DHCP     (*) Static
       IP Address: 2001:db8:1::ab9:C0A8:103_  Prefix Length: 64______
       Gateway     2001:db8:1::ab9:1________
       

3. Enter a VLAN identifier in the VLAN ID field to configure a VLAN for the device.
4. Select the <Save> button and press Enter to save the network configuration.

Procedure 7.9. Configuring Remote Storage

1. Enter an initiator name in the iSCSI Initiator Name field or the path to the NFS share in the NFSv4 Domain (example.redhat.com) field.

   Example 7.19. iSCSI Initiator Name

   iSCSI Initiator Name:
   iqn.1994-05.com.redhat:5189835eeb40_____

   Example 7.20. NFS Path

   NFSv4 Domain (example.redhat.com):
   example.redhat.com_____________________

2. Select <Save> and press Enter.

Procedure 7.10. Configuring a Hypervisor Management Server

• • Configure the Hypervisor Management Server using the address of the Manager.
    1. Enter the IP address or fully qualified domain name of the Manager in the Management Server field.
    2. Enter the management server port in the Management Server Port field. The default value is 443. If a different port was selected during Red Hat Enterprise Virtualization Manager installation, specify it here, replacing the default value.
    3. Leave the Password and Confirm Password fields blank. These fields are not required if the address of the management server is known.
    4. Select <Save & Register> and press Enter.
    After a few minutes, the Hypervisor is displayed under the Hosts tab in the Administration Portal. You must approve it to use the Hypervisor in your Red Hat Enterprise Virtualization environment. See Section 7.6, “Approving a Registered Hypervisor” for more information.
  • Configure the Hypervisor Management Server using a password.
    1. Enter a password in the Password field. Although the Hypervisor will accept a weak password, it is recommended that you use a strong password. Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words.
    2. Re-enter the password in the Confirm Password field.
    3. Leave the Management Server and Management Server Port fields blank. As long as a password is set, allowing the Hypervisor to be added to the Manager later, these fields are not required.
    4. Select <Save & Register> and press Enter.
    After the password is set, manually add the Hypervisor from the Administration Portal. See Section 9.4, “Manually Adding a Hypervisor from the Administration Portal” for more information.

Procedure 7.11. Registering the Hypervisor

1. Enter your Customer Portal user name in the Login field.
2. Enter your Customer Portal password in the Password field.
3. Enter a profile name to be used for the system in the Profile Name (optional) field. This is the name under which the system will appear when viewed in the Customer Portal.
4. Select the method by which to register the Hypervisor:

   • Red Hat Subscription Manager

     1. Select the RHSM option and press the space bar.
     2. You do not need to enter values in the URL and CA URL fields.
     3. Optionally enter an organization name in the Organization field.

     Example 7.21. Red Hat Subscription Manager Configuration

     (X) RHSM     ( ) Satellite     ( ) SAM
     URL:          _________________________________________________
     CA URL:       _________________________________________________
     Organization: Organization_Name________________________________

   • Red Hat Satellite 5

     1. Select the Satellite option and press the space bar.
     2. Enter the URL of the Satellite server in the URL field.
     3. Enter the URL of the certificate authority for the Satellite server in the CA URL field.
     4. Optionally enter an organization name in the Organization field.
     5. Optionally enter a life cycle environment name in the Environment field.

     Example 7.22. Satellite 5 Configuration

     ( ) RHSM     (X) Satellite     ( ) SAM
     URL:          https://sat.example.com____________________________
     CA URL:       http://sat.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT
     Organization: Organization_Name__________________________________
     Environment:  Library____________________________________________

   • Red Hat Satellite 6.0 or 6.1

     1. On the Satellite server, extract the certificate:

        # cd /tmp
        # rpm2cpio /var/www/html/pub/katello-ca-consumer-latest.noarch.rpm | cpio -idmv
        # cat etc/rhsm/ca/candlepin-local.pem etc/rhsm/ca/katello-server-ca.pem >> /var/www/html/pub/katello-server-ca.crt
        # restorecon -Rv /var/www/html/pub/katello-server-ca.crt
        # chmod 644 /var/www/html/pub/katello-server-ca.crt

     2. On the Hypervisor, select the Satellite option and press the space bar.
     3. Enter the URL of the Satellite server in the URL field.
     4. Enter the URL of the certificate authority for the Satellite server in the CA URL field.
     5. Enter an organization name in the Organization field.
     6. Enter a life cycle environment name in the Environment field.

     Example 7.23. Satellite 6 Configuration

     ( ) RHSM     (X) Satellite     ( ) SAM
     URL:          https://sat.example.com____________________________
     CA URL:       http://sat.example.com/pub/katello-server-ca.crt___
     Organization: Organization_Name__________________________________
     Environment:  Library____________________________________________

   • Red Hat Satellite 6.2

     1. Select the Satellite option and press the space bar.
     2. Enter the URL of the Satellite server in the URL field.
     3. Enter the URL of the certificate authority for the Satellite server in the CA URL field.
     4. Enter an organization name in the Organization field.
     5. Enter a life cycle environment name in the Environment field.

     Example 7.24. Satellite 6 Configuration

     ( ) RHSM     (X) Satellite     ( ) SAM
     URL:          https://sat.example.com____________________________
     CA URL:       http://sat.example.com/pub/katello-server-ca.crt___
     Organization: Organization_Name__________________________________
     Environment:  Library____________________________________________

   • Subscription Asset Manager

     1. Select the SAM option and press the space bar.
     2. Enter the URL of the Subscription Asset Manager server in the URL field.
     3. Enter the URL of the certificate authority for the Subscription Asset Manager server in the CA URL field.
     4. Optionally enter an organization name in the Organization field.

     Example 7.25. Subscription Asset Manager Configuration

     ( ) RHSM     ( ) Satellite     (X) SAM
     URL:          https://sam.example.com____________________________
     CA URL:       http://sam.example.com/sam/candlepin-local.pem_____
     Organization: Your_Organization__________________________________

5. If you are using a proxy server, you must also specify the details of that server:
   1. Select <HTTP Proxy Configuration> and press Enter.
   2. Enter the IP address or fully qualified domain name of the proxy server in the Server field.
   3. Enter the port by which to attempt a connection to the proxy server in the Port field.
   4. Enter the user name by which to attempt a connection to the proxy server in the Username field.
   5. Enter the password by which to authenticate the user name specified above in the Password field.
   6. Select <Save> and press Enter to save the configuration and return to the RHSM Registration screen.
6. Select <Save> and press Enter.

Procedure 7.12. Configuring Security-Related Tasks

1. To enable SSH authentication, select the Enable SSH password authentication option and press the space bar. SSH authentication can also be enabled in the RHEV-M screen. Leave the option disabled if the function is not required.
2. AES-NI encryption is enabled by default.
   • If you need to disable it, select the Disable AES-NI option and press the space bar.
   • If AES-NI encryption is enabled, you can optionally set the number of bytes by which to pad blocks in AES-NI encryption
3. Enter a new password for the admin user in the Password field and Confirm Password to change the password used to log into the Hypervisor console.
4. Select <Save> and press Enter.

Procedure 7.13. Configuring the Hypervisor Keyboard Layout

1. Select a keyboard layout from the list provided.

   Keyboard Layout Selection
   	
   Choose the Keyboard Layout you would like to apply to this system.
   
   Current Active Keyboard Layout: U.S. English
   Available Keyboard Layouts
   Swiss German (latin1)
   Turkish
   U.S. English
   U.S. International
   Ukranian
   ...
   
   <Save>

2. Select <Save> and press Enter to save the selection.

Procedure 7.14. Enabling the SNMP Agent on the Hypervisor

1. Select the Enable SNMP option and press the space bar to enable SNMP.
2. Enter a password in the Password and Confirm Password fields.
3. Select <Save> and press Enter.

Procedure 7.15. Enabling CIM Monitoring Connections on the Hypervisor

1. Select the Enable CIM option and press the space bar to enable CIM.

   Enable CIM     [ ]

2. Enter a password in the Password field and Confirm Password field.
3. Select <Save> and press Enter.

Procedure 7.16. Configuring Logging using the Logging Screen

1. In the Logrotate Max Log Size field, enter the maximum size in kilobytes that log files can reach before they are rotated by logrotate. The default value is 1024.
2. Select an Interval to configure logrotate to run Daily, Weekly, or Monthly. The default value is Daily.
3. Optionally configure rsyslog to transmit log files to a remote syslog daemon:
   1. Enter the remote rsyslog server address in the Server Address field.
   2. Enter the remote rsyslog server port in the Server Port field. The default port is 514.
4. Optionally configure netconsole to transmit kernel messages to a remote destination:
   1. Enter the Server Address.
   2. Enter the Server Port. The default port is 6666.
5. Select <Save> and press Enter.

Procedure 7.17. Configuring Kernel Dumps

1. Select an option for storing kernel dumps:

   • Disable

     To disable kernel dumps, select Disable, and press the space bar.

   • Local

     Select the Local option and press the space bar to store kernel dumps on the local system. This is the default option.

   • SSH

     1. Select the SSH option and press the space bar to export kernel dumps via SSH.
     2. Enter the location in which kernel dumps will be stored in the SSH Location (root@example.com) field.
     3. Enter an SSH Key URL (optional).

   • NFS

     1. Select the NFS option and press the space bar to export kernel dumps to an NFS share.
     2. Enter the location in which kernel dumps will be stored in the NFS Location (example.com:/var/crash) field.
2. Select <Save> and press Enter.

Procedure 8.2. Automating Deployment using PXE and Kickstart

1. Download the RHVH ISO image from the Customer Portal:
   1. Log in to the Customer Portal at https://access.redhat.com.
   2. Click Downloads in the menu bar.
   3. Click Red Hat Virtualization, scroll up, and click Download Latest to access the product download page.
   4. Choose the appropriate hypervisor image and click Download Now.
2. Make the RHVH ISO image available over the network using the instructions in Installation Source on a Network.
3. Configure the PXE server using the instructions in Preparing for a Network Installation.
   The following requirements apply in order to boot RHVH from the PXE server:
   • Ensure that you copy the RHVH boot images to the tftp/ root directory.

     # cp URL/to/RHVH-ISO/images/pxeboot/{vmlinuz,initrd.img} /var/lib/tftpboot/pxelinux/

   • The boot loader configuration file must include a RHVH label that specifies the RHVH boot images.

     KERNEL URL/to/vmlinuz
     APPEND initrd=URL/to/initrd.img inst.stage2=URL/to/RHVH-ISO

4. Create a Kickstart file and make it available over the network using the instructions in Kickstart Installations.
   The following constraints apply to RHVH Kickstart files:
   • The %packages section is not required for RHVH. Instead, use the liveimg option and specify the squashfs.img file from the RHVH ISO image.

     liveimg --url=URL/to/squashfs.img

   • The autopart command is highly recommended. Thin provisioning must be used.

     autopart --type=thinp

     If your installation requires manual partitioning instead, see Section 8.2.1, “Custom Partitioning” for a list of limitations that apply to partitions.
     The following example demonstrates how to configure manual partitioning.

     clearpart --all
     part /boot --fstype xfs --size=1000 --ondisk=sda
     part pv.01 --size=42000 --grow
     volgroup HostVG pv.01
     logvol swap --vgname=HostVG --name=swap --fstype=swap --recommended
     logvol none --vgname=HostVG --name=HostPool --thinpool --size=40000 --grow
     logvol / --vgname=HostVG --name=root --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=6000 --grow
     logvol /var --vgname=HostVG --name=var --thin --fstype=ext4 --poolname=HostPool
     --fsoptions="defaults,discard" --size=15000
     logvol /var/log --vgname=HostVG --name=var_log --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=8000
     logvol /var/log/audit --vgname=HostVG --name=var_audit --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=2000
     logvol /home --vgname=HostVG --name=home --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=1000
     logvol /tmp --vgname=HostVG --name=tmp --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=1000
     

   • A %post section that calls the nodectl init command is required.

     %post
     nodectl init
     %end

   To fully automate the installation process, you can add this Kickstart file to the boot loader configuration file on the PXE server. Specify the Kickstart location by adding inst.ks= to the APPEND line:

   APPEND initrd=URL/to/initrd.img inst.stage2=URL/to/RHVH-ISO inst.ks=URL/to/RHVH-ks.cfg

   Example 8.1. Red Hat Virtualization Host Kickstart File

   The following is an example of a Kickstart file used to deploy Red Hat Virtualization Host. You can include additional commands and options as required.

   liveimg --url=http://1.2.3.4/path/to/squashfs.img
   clearpart --all
   autopart --type=thinp
   rootpw --plaintext ovirt
   timezone --utc America/Phoenix
   zerombr
   text
   
   reboot
   
   %post --erroronfail
   nodectl init
   %end

5. Install RHVH using the instructions in Booting the Installation on AMD64 and Intel 64 Systems from the Network Using PXE.