7.3. Installing Additional Hosts to a Restored Self-Hosted Engine Environment
- Prepare a physical host to be used as an additional self-hosted engine host. You can use a freshly installed Red Hat Enterprise Linux host or a self-hosted engine host from the backed up environment. If you are using a freshly installed host, subscribe the host to the required entitlements and install
ovirt-hosted-engine-setup. See Section 3.1, “Subscribing to the Required Entitlements”. If you are resuing a self-hosted engine host, remove the self-hosted engine configuration. See Section 6.4, “Removing a Host from a Self-Hosted Engine Environment”.
Procedure 7.7. Adding Additional Self-Hosted Engine Hosts
- Install the ovirt-hosted-engine-setup package.
# yum install ovirt-hosted-engine-setup
- Configure the host with the deployment command.
# hosted-engine --deployIf running the
hosted-enginedeployment script over a network, it is recommended to use the
screenwindow manager to avoid losing the session in case of network or terminal disruption. Install the screen package first if not installed.
# hosted-engine --deploy
Preparing for InitializationThe script begins by requesting confirmation to use the host as a hypervisor for use in a self-hosted engine environment.
Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]:
Configuring StorageSelect the type of storage to use.
During customization use CTRL-D to abort. Please specify the storage you would like to use (iscsi, nfs3, nfs4)[nfs3]:
- For NFS storage types, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.
Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs
- For iSCSI, specify the iSCSI portal IP address, port, user name and password, and select a target name from the auto-detected list:
Please specify the iSCSI portal IP address: Please specify the iSCSI portal port : Please specify the iSCSI portal user: Please specify the iSCSI portal password: Please specify the target name (auto-detected values) [default]:
Detecting the Self-Hosted EngineThe
hosted-enginescript detects that the shared storage is being used and asks if this is an additional host setup. You are then prompted for the host ID, which must be an integer not already assigned to a host in the environment.
The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? [ INFO ] Installing on additional host Please specify the Host ID [Must be integer, default: 2]:
Configuring the SystemThe
hosted-enginescript uses the answer file generated by the original hosted-engine setup. To achieve this, the script requires the FQDN or IP address and the password of the
rootuser of that host so as to access and secure-copy the answer file to the additional host.
[WARNING] A configuration file must be supplied to deploy Hosted Engine on an additional host. The answer file may be fetched from the first host using scp. If you do not want to download it automatically you can abort the setup answering no to the following question. Do you want to scp the answer file from the first host? (Yes, No)[Yes]: Please provide the FQDN or IP of the first host: Enter 'root' user password for host [hosted_engine_1.example.com]: [ INFO ] Answer file successfully downloaded
Configuring the Hosted EngineSpecify the name for the additional host to be identified in the Red Hat Enterprise Virtualization environment, and the password for the
admin@internaluser. The name must not already be in use by a host in the environment.
Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_2]: Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: Confirm 'admin@internal' user password:
Configuration PreviewBefore proceeding, the
hosted-enginescript displays the configuration values you have entered, and prompts for confirmation to proceed with these values.
Bridge interface : eth1 Engine FQDN : HostedEngine-VM.example.com Bridge name : rhevm SSH daemon port : 22 Firewall manager : iptables Gateway address : X.X.X.X Host name for web application : hosted_engine_2 Host ID : 2 Image size GB : 25 Storage connection : storage.example.com:/hosted_engine/nfs Console type : vnc Memory size MB : 4096 MAC address : 00:16:3e:05:95:50 Boot type : disk Number of CPUs : 2 CPU Type : model_Penryn Please confirm installation settings (Yes, No)[Yes]:
Confirming Engine Installation CompleteThe additional host will contact the Manager and
hosted_engine_1, after which the script will prompt for a selection. Continue by selection option 1.
[ INFO ] Stage: Closing up 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 (4) Destroy VM and abort setup (1, 2, 3, 4)
[ 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...At this point, the host will become visible in the Administration Portal with Installing and Initializing states before entering a Non Operational state. The host will continue to wait for VDSM host to become operational until it eventually times out.
[ INFO ] Still waiting for VDSM host to become operational... [ INFO ] Still waiting for VDSM host to become operational... [ ERROR ] Timed out while waiting for host to start. Please check the logs. [ ERROR ] Unable to add hosted_engine_1 to the manager [ INFO ] Enabling and starting HA services Hosted Engine successfully set up [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination
- Activate the host.
- Log in to the Administration Portal.
- Click the Hosts tab and select the host to activate.
- Click thebutton.