Deploying Resource Manager

Use this procedure to install the Resource Manager template and then deploy the application.
  1. Use the virtual hostname (HA-Virtual-Name) or virtual IP address (HA-Virtual-IP) of the high-availability cluster to start a Bash shell on the Control Center master host as root, or as a user with superuser privileges.
  2. Display the public hostname of the current node.
    uname -n
    The result is either Primary-Public-Name or Secondary-Public-Name.
  3. Place the other node in standby mode.
    This step avoids potential conflicts and errors in the event of an unexpected serviced shutdown during the initial deployment.
    Replace Other-Node-Hostname with the public hostname of the other node:
    pcs cluster standby Other-Node-Hostname
  4. Add the Resource Manager application template to Control Center.
    serviced template add /opt/serviced/templates/zenoss*.json
    On success, the serviced command returns the template ID.
  5. Identify the resource pool to which the master host belongs.
    serviced host list
  6. Deploy the application.
    • Replace Template-ID with the identified Resource Manager template.
    • Replace Pool with the name of the resource pool to which the master host belongs (single-host system) or to which the delegate hosts belong (multi-host system).
    • Replace Deployment with a name for this deployment (for example, Test or Production).
    serviced template deploy Template-ID Pool Deployment
    Control Center tags the Resource Manager images.
  7. Restore the cluster.

    Replace Standby-Node-Hostname with the public hostname of the node that is in standby mode:

    pcs cluster unstandby Standby-Node-Hostname
Resource Manager is ready to be configured for your environment. For more information, refer to the Zenoss Resource Manager Configuration Guide.