-
Language:
English
-
Language:
English
Chapter 4. Configuring a single node RHHI for Virtualization deployment
4.1. Configuring Red Hat Gluster Storage on a single node
Ensure that disks specified as part of this deployment process do not have any partitions or labels.
Log into the Cockpit UI
Browse to the Cockpit management interface of the first virtualization host, for example, https://node1.example.com:9090/, and log in with the credentials you created in Chapter 3, Install the virtualization host.
Start the deployment wizard
Click Virtualization → Hosted Engine and click Start underneath Hyperconverged.
The Gluster Configuration window opens.
Click the Run Gluster Wizard button.
The Gluster Deployment window opens in single node mode.
Specify storage host
Specify the back-end FQDN on the storage network of the virtualization host and click Next.
Specify volumes
Specify the volumes to create.
- Name
- Specify the name of the volume to be created.
- Volume Type
Specify a Distribute volume type. Only distributed volumes are supported for single node deployments.
ImportantThis step is affected by a known issue, BZ#1641483. It is not currently possible to select Distribute. Instead, select Replicated. The volume created is a single-brick distributed volume, which is correct for single-node RHHI for Virtualization deployments.
- Brick Dirs
- The directory that contains this volume’s bricks.
Specify bricks
Specify the bricks to create.
- RAID
- Specify the RAID configuration to use. This should match the RAID configuration of your host. Supported values are raid5, raid6, and jbod. Setting this option ensures that your storage is correctly tuned for your RAID configuration.
- Stripe Size
- Specify the RAID stripe size in KB. Do not enter units, only the number. This can be ignored for jbod configurations.
- Disk Count
- Specify the number of data disks in a RAID volume. This can be ignored for jbod configurations.
- LV Name
- Specify the name of the logical volume to be created.
- Device
- Specify the raw device you want to use. Red Hat recommends an unpartitioned device.
- Size
- Specify the size of the logical volume to create in GB. Do not enter units, only the number.
- Mount Point
- Specify the mount point for the logical volume. This should be inside the brick directory that you specified on the previous page of the wizard.
- Thinp
- Specify whether to provision the volume thinly or not. Note that thick provisioning is recommended for the engine volume. Do not use Enable Dedupe & Compression at the same time as this option.
- Enable Dedupe & Compression
- Specify whether to provision the volume using VDO for compression and deduplication at deployment time. Do not use Thinp at the same time as this option.
- Logical Size (GB)
- Specify the logical size of the VDO volume. This can be up to 10 times the size of the physical volume, with an absolute maximum logical size of 4 PB.
Review and edit configuration
Review the contents of the generated configuration file and click Edit to modify the file, and Save to keep your changes.
Click Deploy when you are satisfied with the configuration file.
Wait for deployment to complete
You can watch the deployment process in the text field as the gdeploy process runs using the generated configuration file.
The window displays Successfully deployed gluster when complete.
Click Continue to Hosted Engine Deployment and continue the deployment process with the instructions in Section 4.2, “Deploy the Hosted Engine on a single node using the Cockpit UI”.
If deployment fails, click the Redeploy button. This returns you to the Review and edit configuration tab so that you can correct any issues in the generated configuration file before reattempting deployment.
It may be necessary to clean up previous deployment attempts before you try again. Follow the steps in Appendix A, Cleaning up automated Red Hat Gluster Storage deployment errors to clean up previous deployment attempts.
4.2. Deploy the Hosted Engine on a single node using the Cockpit UI
This section shows you how to deploy the Hosted Engine on a single node using the Cockpit UI. Following this process results in Red Hat Virtualization Manager running in a virtual machine on your node, and managing that virtual machine. It also configures a Default cluster consisting only of that node, and enables Red Hat Gluster Storage functionality and the virtual-host tuned performance profile for the cluster of one.
Prerequisites
- This procedure assumes you have continued directly from the end of Configure Red Hat Gluster Storage for Hosted Engine using the Cockpit UI
Gather the information you need for Hosted Engine deployment
Have the following information ready before you start the deployment process.
- IP address for a pingable gateway to the virtualization host
- IP address of the front-end management network
- Fully-qualified domain name (FQDN) for the Hosted Engine virtual machine
- MAC address that resolves to the static FQDN and IP address of the Hosted Engine
Procedure
Specify virtual machine details
Enter the following details:
- Engine VM FQDN
- The fully qualified domain name to be used for the Hosted Engine virtual machine.
- MAC Address
- The MAC address associated with the FQDN to be used for the Hosted Engine virtual machine.
- Root password
- The root password to be used for the Hosted Engine virtual machine.
- Click Next.
Specify virtualization management details
Enter the password to be used by the
admin
account in Red Hat Virtualization Manager. You can also specify notification behaviour here.- Click Next.
Review virtual machine configuration
Ensure that the details listed on this tab are correct. Click Back to correct any incorrect information.
Click Prepare VM.
Wait for virtual machine preparation to complete.
If preparation does not occur successfully, see Viewing Hosted Engine deployment errors.
- Click Next.
Specify storage for the Hosted Engine virtual machine
Specify the back-end address and location of the
engine
volume.- Click Next.
Finalize Hosted Engine deployment
Review your deployment details and verify that they are correct.
NoteThe responses you provided during configuration are saved to an answer file to help you reinstall the hosted engine if necessary. The answer file is created at
/etc/ovirt-hosted-engine/answers.conf
by default. This file should not be modified manually without assistance from Red Hat Support.- Click Finish Deployment.
Wait for deployment to complete
This takes up to 30 minutes.
The window displays the following when complete.
ImportantIf deployment does not complete successfully, see Viewing Hosted Engine deployment errors.
Click Close.
Verify hosted engine deployment
Browse to the engine user interface (for example, http://engine.example.com/ovirt-engine) and verify that you can log in using the administrative credentials you configured earlier. Click Dashboard and look for your hosts, storage domains, and virtual machines.