Skip to content

Configuring a multi-host deployment

For the complete list of installation instructions, see Installing Resource Manager.

Adding a delegate host through an SSH connection

Use this procedure to add a delegate host to a resource pool through an SSH connection. Repeat this procedure on each delegate in your Resource Manager deployment.

To succeed, the following statements about the login account used to perform this procedure must be true:

  • The account exists on both the master host and on the delegate host.
  • The account has serviced CLI privileges.
  • The account has either public key authentication or password authentication enabled on the master host and on the delegate host.

Follow these steps:

  1. Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote shell utility such as PuTTY.
  2. Start a command-line session as root or as a user with superuser privileges.

    1. In the Appliance Administration menu, select Root Shell.

    2. Select Run, and then press Enter. The menu is replaced by a command prompt similar to the following example:

      [root@hostname ~]#
      
  3. Add a delegate host to a resource pool.

    • If the master and delegate host are configured for key-based access, the following command does not prompt you to add the delegate to the list of known hosts or to provide the password of the remote user account.
    • Use the hostname or IP address to identify a Control Center host. If you use a hostname, all Control Center hosts must be able to resolve it, either through an entry in /etc/hosts or through a nameserver on the network. In the following example, replace Hostname-Or-IP with the hostname or IP address of a delegate host, and replace Resource-Pool with the name of a resource pool.
    • If the host is behind a router or firewall for network address translation (NAT), include the option --nat-address to specify the NAT device's hostname or IP address and port of the delegate host.
    serviced host add --register Hostname-Or-IP:4979 Resource-Pool --nat-address==NAT-Hostname-Or-IP:NAT-Port
    

Adding a delegate host using a file

Use this procedure to add a delegate host to a resource pool by using a key bundle file. Repeat this procedure on each delegate in your Resource Manager deployment.

  1. Gain access to the Control Center host, through the console interface of your hypervisor, or through a remote shell utility such as PuTTY.
  2. Start a command-line session as root or as a user with superuser privileges.

    1. In the Appliance Administration menu, select Root Shell.

    2. Select Run, and then press Enter. The menu is replaced by a command prompt similar to the following example:

      [root@hostname ~]#
      
  3. Add a delegate host to a resource pool.

    • Use the hostname or IP address to identify a Control Center host. If you use a hostname, all Control Center hosts must be able to resolve it, either through an entry in /etc/hosts or through a nameserver on the network.
    • In the following example, replace Hostname-Or-IP with the hostname or IP address of a delegate host, and replace Resource-Pool with the name of a resource pool.
    • If the host is behind a router or firewall for network address translation (NAT), include the option --nat-address to specify the NAT device's hostname or IP address and port of the delegate host.
    serviced host add Hostname-Or-IP:4979 Resource-Pool --nat-address==NAT-Hostname-Or-IP:NAT-Port
    

    The command creates a unique key bundle file in the local directory.

  4. Use a file transfer utility such as scp to copy the key bundle file to the delegate host.

    After you copy it to the delegate host, you can delete the key bundle file from the master host.

  5. Log in to the Control Center delegate host as a user with serviced CLI privileges.

  6. Install the key bundle.

    Replace Key-Bundle-Path with the pathname of the key bundle file:

    serviced host register Key-Bundle-Path
    
  7. Delete the key bundle file.

    The file is no longer needed on the delegate host.

    Replace Key-Bundle-Path with the pathname of the key bundle file:

    rm Key-Bundle-Path