Deploying Resource Manager
- 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.
Display the public hostname of the current node.
uname -nThe result is either Primary-Public-Name or Secondary-Public-Name.
Place the other node in standby mode.
This 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
Add the Resource Manager application
template to Control Center.
serviced template add /opt/serviced/templates/zenoss*.jsonOn success, the serviced command returns the template ID.
Identify the resource pool to which the master host belongs.
serviced host list
Deploy the application.
- Replace Template-ID with the identifier 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 DeploymentControl Center tags the Resource Manager images.
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