Deploy Self-Hosted Engine Using Cockpit

If your hosts do not have a direct internet connection, are behind a proxy, or you clicked Close in Cockpit after deploying Gluster, you must use the command line to deploy the self- hosted engine.

To deploy the self-hosted engine using the Cockpit web interface immediately after deploying Gluster, you should have clicked Continue to Hosted Engine Deployment in the last step of the Gluster deployment instructions.

Complete the following steps using the Hosted Engine Deployment wizard.

  1. On the VM screen, fill in the following VM settings information:
    • In the Engine VM FQDN field, enter the Engine virtual machine FQDN, which must be resolvable by a DNS search. Do not use the FQDN of the host.
    • In the MAC Address field, enter a MAC address for the Engine virtual machine only if you do not want to use the auto-generated address.
    • From the Network Configuration list, select either DHCP or Static.
      • To use DHCP, you must have a DHCP reservation (a pre-set IP address on the DHCP server) for the Engine virtual machine.
      • To use Static, enter the virtual machine IP, the netmask and gateway addresses, and DNS server. The IP address must belong to the same subnet as the host.
    • From the Bridge Interface list, select the physical network interface to configure the bridge on.
    • Enter and confirm the virtual machine’s Root Password.
    • Specify whether to allow Root SSH Access.
    • Enter the Number of Virtual CPUs for the virtual machine.
    • Enter the Memory Size (MiB). The available memory is displayed next to the field.
  2. (Optional) Click Advanced to provide any of the following information.
    • Enter a Root SSH Public Key to use for root access to the Engine virtual machine.
    • Select the Edit Hosts File check box if you want to add entries for the Engine virtual machine and the base host to the virtual machine’s /etc/hosts file. You must ensure that the host names are resolvable.
    • Change the management Bridge Name, or accept the default of ovirtmgmt.
    • Enter the Gateway Address for the management bridge.
    • Enter the Host FQDN of the first host to add to the Engine. This is the FQDN of the host you are using for the deployment.
  3. Click Next.
  4. On the Engine screen, enter a password for the Admin user in the Admin Portal Password field. Do not change any other fields.
  5. Click Next.

  6. Review the options in the Prepare VM screen. Click Prepare VM to continue or the Back if you need to change any options.

  7. When the Prepare VM completes successfully, click Next.

  8. On the Storage screen, select Gluster as the Storage Type. The Storage Connection should have the deployment node as the primary connection and other nodes as backup mount servers.

    Do not change any other fields.

  9. Click Next.

  10. On the Finish screen, review the mount information and click Finish Deployment.

    This process

    • transfers the Hosted Engine virtual disk to the Gluster engine volume
    • creates a VM named Hostedengine
    • configures services to start this instance automatically when the hyperconverged hosts boots
    • configures the deployment host as a KVM host in the Administration Portal
  11. Add the remaining hyperconverged nodes as KVM hosts. See Add Hyperconverged Hosts to Cluster for instructions.