⁠4.5. Migrating to a Self-Hosted Environment

Summary
Deploy a hosted-engine environment and migrate an existing instance of Red Hat Enterprise Virtualization. The hosted-engine deployment script is provided to assist with this task. The script asks you a series of questions, and configures your environment based on your answers. When the required values have been provided, the updated configuration is applied and the Red Hat Enterprise Virtualization Manager services are started.
The hosted-engine deployment script guides you through several distinct configuration stages. The script suggests possible configuration defaults in square brackets. Where these default values are acceptable, no additional input is required.
This procedure requires a new Red Hat Enterprise Linux 6.5 host with the ovirt-hosted-engine-setup package installed. This host is referred to as 'Host-HE1', with a fully qualified domain name (FQDN) of Host-HE1.example.com in this procedure.
Your original Red Hat Enterprise Virtualization Manager is referred to as 'BareMetal-Manager', with an FQDN of Host-HE1.example.com, in this procedure. You will be required to access and make changes on BareMetal-Manager during this procedure.
The hosted engine, the virtual machine created during configuration of Host-HE1 and used to manage the environment, is referred to as 'HostedEngine-VM' in this procedure. You will be prompted by the hosted-engine deployment script to access this virtual machine multiple times to install an operating system and to configure the engine.
All steps in this procedure are to be conducted as the root user for the specified machine.

Important

The engine running on BareMetal-Manager must be the same version as will be installed on HostedEngine-VM. As the hosted engine feature is only available on Red Hat Enterprise Virtualization version 3.3.0 and later, any previous version of Red Hat Enterprise Virtualization running on BareMetal-Manager must be upgraded. Upgrade the engine version on BareMetal-Manager before creating the backup with the engine-backup command.
⁠

Procedure 4.3. Migrating to a Self-Hosted Environment

  1. Initiating Hosted Engine Deployment

    Begin configuration of the self-hosted environment by deploying the hosted-engine customization script on Host_HE1. To escape the script at any time, use the CTRL+D keyboard combination to abort deployment. 
    # hosted-engine --deploy

  2. Configuring Storage

    Select the version of NFS and specify the full address, using either the FQDN or IP address, and path name of the shared storage domain. Choose the storage domain and storage data center names to be used in the environment. 
    During customization use CTRL-D to abort.
Please specify the storage you would like to use (nfs3, nfs4)[nfs3]: 
Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs
[ INFO  ] Installing on first host
Please provide storage domain name. [hosted_storage]: 
Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.Please enter local datacenter name [hosted_datacenter]:

  3. Configuring the Network

    The script detects possible network interface controllers (NICs) to use as a management bridge for the environment. It then checks your firewall configuration and offers to modify it for console (SPICE or VNC) access HostedEngine-VM. Provide a pingable gateway IP address, to be used by the ovirt-ha-agent to help determine a host's suitability for running HostedEngine-VM. 
    Please indicate a nic to set rhevm bridge on: (eth1, eth0) [eth1]:
iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: 
Please indicate a pingable gateway IP address [X.X.X.X]:

  4. Configuring the Virtual Machine

    The script creates a virtual machine to be configured as the Red Hat Enterprise Virtualization Manager, the hosted engine referred to in this procedure as HostedEngine-VM. Specify the boot device and, if applicable, the path name of the installation media, the CPU type, the number of virtual CPUs, and the disk size. Specify a MAC address for the HostedEngine-VM, or accept a randomly generated one. The MAC address can be used to update your DHCP server prior to installing the operating system on the virtual machine. Specify memory size and console connection type for the creation of HostedEngine-VM. 
    Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: 
The following CPU types are supported by this host:
          - model_Penryn: Intel Penryn Family
          - model_Conroe: Intel Conroe Family
Please specify the CPU type to be used by the VM [model_Penryn]: 
Please specify the number of virtual CPUs for the VM [Defaults to minimum requirement: 2]: 
Please specify the disk size of the VM in GB [Defaults to minimum requirement: 25]: 
You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]: 
Please specify the memory size of the VM in MB [Defaults to minimum requirement: 4096]: 
Please specify the console type you would like to use to connect to the VM (vnc, spice) [vnc]:

  5. Configuring the Hosted Engine

    Specify the name for Host-HE1 to be identified in the Red Hat Enterprise Virtualization environment, and the password for the admin@internal user to access the Administrator Portal. Provide the FQDN for HostedEngine-VM; this procedure uses the FQDN HostedEngine-VM.example.com. Finally, 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.

    Important

    The FQDN provided for the engine (HostedEngine-VM.example.com) must be the same FQDN provided when BareMetal-Manager was initially set up. 
    Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]: Host-HE1
Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: 
Confirm 'admin@internal' user password: 
Please provide the FQDN for the engine you would like to use. This needs to match the FQDN that you will use for the engine installation within the VM: BareMetal-Manager.example.com
Please provide the name of the SMTP server through which we will send notifications [localhost]: 
Please provide the TCP port number of the SMTP server [25]: 
Please provide the email address from which notifications will be sent [root@localhost]: 
Please provide a comma-separated list of email addresses which will get notifications [root@localhost]:

  6. Configuration Preview

    Before proceeding, the hosted-engine script displays the configuration values you have entered, and prompts for confirmation to proceed with these values. 
    Bridge interface                   : eth1
Engine FQDN                        : BareMetal-Manager.example.com
Bridge name                        : rhevm
SSH daemon port                    : 22
Firewall manager                   : iptables
Gateway address                    : X.X.X.X
Host name for web application      : Host-HE1
Host ID                            : 1
Image size GB                      : 25
Storage connection                 : storage.example.com:/hosted_engine/nfs
Console type                       : vnc
Memory size MB                     : 4096
MAC address                        : 00:16:3e:77:b2:a4
Boot type                          : pxe
Number of CPUs                     : 2
CPU Type                           : model_Penryn

Please confirm installation settings (Yes, No)[No]:

  7. Creating HostedEngine-VM

    The script creates the virtual machine that will be configured to be HostedEngine-VM and provides connection details. You will need to install an operating system on HostedEngine-VM before the hosted-engine script can proceed on Host-HE1. 
    [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
[ INFO  ] Stage: Transaction setup
[ INFO  ] Stage: Misc configuration
[ INFO  ] Stage: Package installation
[ INFO  ] Stage: Misc configuration
[ INFO  ] Configuring libvirt
[ INFO  ] Generating VDSM certificates
[ INFO  ] Configuring VDSM
[ INFO  ] Starting vdsmd
[ INFO  ] Waiting for VDSM hardware info
[ INFO  ] Creating Storage Domain
[ INFO  ] Creating Storage Pool
[ INFO  ] Connecting Storage Pool
[ INFO  ] Verifying sanlock lockspace initialization
[ INFO  ] Initializing sanlock lockspace
[ INFO  ] Initializing sanlock metadata
[ INFO  ] Creating VM Image
[ INFO  ] Disconnecting Storage Pool
[ INFO  ] Start monitoring domain
[ INFO  ] Configuring VM
[ INFO  ] Updating hosted-engine configuration
[ INFO  ] Stage: Transaction commit
[ INFO  ] Stage: Closing up
[ INFO  ] Creating VM
You can now connect to the VM with the following command:
	/usr/bin/remote-viewer vnc://localhost:5900
Use temporary password "5379skAb" to connect to vnc console.
Please note that in order to use remote-viewer you need to be able to run graphical applications.
This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
Otherwise you can run the command from a terminal in your preferred desktop environment.
If you cannot run graphical applications you can connect to the graphic console from another host or connect to the console using the following command:
virsh -c qemu+tls://Test/system console HostedEngine
If you need to reboot the VM you will need to start it manually using the command:
hosted-engine --vm-start
You can then set a temporary password using the command:
hosted-engine --add-console-password
The VM has been started.  Install the OS and shut down or reboot it.  To continue please make a selection:
         
          (1) Continue setup - VM installation is complete
          (2) Reboot the VM and restart installation
          (3) Abort setup
         
          (1, 2, 3)[1]:
    Using the naming convention of this procedure, you would connect to the virtual machine using VNC with the following command: 
    /usr/bin/remote-viewer vnc://Host-HE1.example.com:5900

  8. Installing the Virtual Machine Operating System

    Connect to HostedEngine-VM, the virtual machine created by the hosted-engine script, and install a Red Hat Enterprise Linux 6.5 operating system.

  9. Synchronizing the Host and the Virtual Machine

    Return to Host-HE1 and continue the hosted-engine deployment script by selecting option 1: 
    (1) Continue setup - VM installation is complete
     Waiting for VM to shut down...
[ INFO  ] Creating VM
You can now connect to the VM with the following command:
	/usr/bin/remote-viewer vnc://localhost:5900
Use temporary password "5379skAb" to connect to vnc console.
Please note that in order to use remote-viewer you need to be able to run graphical applications.
This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
Otherwise you can run the command from a terminal in your preferred desktop environment.
If you cannot run graphical applications you can connect to the graphic console from another host or connect to the console using the following command:
virsh -c qemu+tls://Test/system console HostedEngine
If you need to reboot the VM you will need to start it manually using the command:
hosted-engine --vm-start
You can then set a temporary password using the command:
hosted-engine --add-console-password
Please install and setup the engine in the VM.
You may also be interested in subscribing to "agent" RHN/Satellite channel and installing rhevm-guest-agent-common package in the VM.
To continue make a selection from the options below:
          (1) Continue setup - engine installation is complete
          (2) Power off and restart the VM
          (3) Abort setup

  10. Installing the Manager

    Connect to HostedEngine-VM, subscribe to the appropriate Red Hat Enterprise Virtualization Manager channels, ensure that the most up-to-date versions of all installed packages are in use, and install the rhevm packages. 
    # yum upgrade
    # yum install rhevm

  11. Disabling BareMetal-Manager

    Connect to BareMetal-Manager, the Manager of your established Red Hat Enterprise Virtualization environment, and stop the engine and prevent it from running. 
    # service ovirt-engine stop
# service ovirt-engine disable
# chkconfig ovirt-engine off

    Note

    Though stopping BareMetal-Manager from running is not obligatory, it is recommended as it ensures no changes will be made to the environment after the backup has been created. Additionally, it prevents BareMetal-Manager and HostedEngine-VM from simultaneously managing existing resources.

  12. Updating DNS

    Update your DNS so that the FQDN of the Red Hat Enterprise Virtualization environment correlates to the IP address of HostedEngine-VM and the FQDN previously provided when configuring the hosted-engine deployment script on Host-HE1. In this procedure that FQDN was set as BareMetal-Manager.example.com because in a migrated hosted-engine setup, the FQDN provided for the engine must be identical to that given in the engine setup of the original engine.

  13. Creating a Backup of BareMetal-Manager

    Connect to BareMetal-Manager and run the engine-backup command with the --mode=backup, --file=FILE, and --log=LogFILE parameters to specify the backup mode, the name of the backup file created and used for the backup, and the name of the log file to be created to store the backup log. 
    # engine-backup --mode=backup --file=FILE --log=LogFILE

  14. Copying the Backup File to HostedEngine-VM

    Still on BareMetal-Manager, secure copy the backup file to HostedEngine-VM. In the following example, HostedEngine-VM.example.com is the FQDN for HostedEngine-VM, and /backup/ is any designated folder or path. If the designated folder or path does not exist, you will need to connect to HostedEngine-VM and create it before secure copying the backup from BareMetal-Manager. 
    # scp -p backup1 HostedEngine-VM.example.com:/backup/

  15. Restoring the Backup File on HostedEngine-VM

    The engine-backup --mode=restore command does not create a database; you are required to create one on HostedEngine-VM before restoring the backup you created on BareMetal-Manager. Connect to HostedEngine-VM and create the database, as detailed in Section 3.7, “Preparing a PostgreSQL Database for Use with Red Hat Enterprise Virtualization Manager”.

    Note

    The procedure in Section 3.7, “Preparing a PostgreSQL Database for Use with Red Hat Enterprise Virtualization Manager” creates a database that is not empty, which will result in the following error when you attempt to restore the backup: 
    FATAL: Database is not empty
    Create an empty database using the following command in psql: 
    postgres=# create database [database name] owner [user name]
    After the empty database has been created, restore the BareMetal-Manager backup using the engine-backup command with the --mode=restore --file=FILE --log=Restore.log parameters to specify the restore mode, the name of the file to be used to restore the database, and the name of the logfile to store the restore log. This restores the files and the database but does not start the service.
    To specify a different database configuration, use the --change-db-credentials parameter to activate alternate credentials. Use the engine-backup --help command on the Manager for a list of credential parameters. 
    # engine-backup --mode=restore --file=FILE --log=Restore.log --change-db-credentials --db-host=X.X.X.X --db-user=engine --db-password=password --db-name=engine

  16. Configuring HostedEngine-VM

    Configure the engine on HostedEngine-VM. This will identify the existing files and database. 
    # engine-setup
    [ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140304075238.log
Version: otopi-1.1.2 (otopi-1.1.2-1.el6ev)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Yum Downloading: rhel-65-zstream/primary_db 2.8 M(70%)
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment setup
[ INFO  ] Stage: Environment customization
         
          --== PACKAGES ==--
         
[ INFO  ] Checking for product updates...
[ INFO  ] No product updates found
         
          --== NETWORK CONFIGURATION ==--
         
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]: 
[ INFO  ] iptables will be configured as firewall manager.
         
          --== DATABASE CONFIGURATION ==--
         
         
          --== OVIRT ENGINE CONFIGURATION ==--
         
          Skipping storing options as database already prepared
         
          --== PKI CONFIGURATION ==--
         
          PKI is already configured
         
          --== APACHE CONFIGURATION ==--
         
         
          --== SYSTEM CONFIGURATION ==--
         
         
          --== END OF CONFIGURATION ==--
         
[ INFO  ] Stage: Setup validation
[WARNING] Less than 16384MB of memory is available
[ INFO  ] Cleaning stale zombie tasks
         
          --== CONFIGURATION PREVIEW ==--
         
          Database name                      : engine
          Database secured connection        : False
          Database host                      : X.X.X.X
          Database user name                 : engine
          Database host name validation      : False
          Database port                      : 5432
          NFS setup                          : True
          Firewall manager                   : iptables
          Update Firewall                    : True
          Configure WebSocket Proxy          : True
          Host FQDN                          : HostedEngine-VM.example.com
          NFS mount point                    : /var/lib/exports/iso
          Set application as default page    : True
          Configure Apache SSL               : True
         
          Please confirm installation settings (OK, Cancel) [OK]:
    Confirm the settings. Upon completion, the setup will provide an SSH fingerprint and an internal Certificate Authority hash.

  17. Synchronizing the Host and the Manager

    Return to Host-HE1 and continue the hosted-engine deployment script by selecting option 1: 
    (1) Continue setup - engine installation is complete
    [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
[ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] The VDSM Host is now operational
          Please shutdown the VM allowing the system to launch it as a monitored service.
          The system will wait until the VM is down.

  18. Shutting Down HostedEngine-VM

    Shutdown HostedEngine-VM. 
    # shutdown now

  19. Setup Confirmation

    Return to Host-HE1 to confirm it has detected that HostedEngine-VM is down. 
    [ INFO  ] Enabling and starting HA services
          Hosted Engine successfully set up
[ INFO  ] Stage: Clean up
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
Result
Your Red Hat Enterprise Virtualization engine has been migrated to a hosted-engine setup. The Manager is now operating on a virtual machine on Host-HE1, called HostedEngine-VM in the environment. As HostedEngine-VM is highly available, it will be migrated to other hosts in the environment when applicable.
Report a bug