Chapter 11. Testing an OpenShift Enterprise Deployment

This chapter provides information on how to test an OpenShift Enterprise deployment, and information on how to diagnose some problems.

11.1. Testing the MCollective Configuration

Important

Do not run the ruby193-mcollective daemon on the broker. The ruby193-mcollective daemon runs on node hosts and the broker runs the ruby193-mcollective client to contact node hosts. If the ruby193-mcollective daemon is run on the broker, the broker will respond to the oo-mco ping command and behave as both a broker and a node. This results in problems when creating applications, unless you have also run the node configuration on the broker host.
Run the following command on each node host to verify that the ruby193-mcollective service is running: 
# service ruby193-mcollective status
If the service is not running, use the following command to start it: 
# service ruby193-mcollective start
The command-line interface to MCollective is provided by the oo-mco command. This command can be used to perform diagnostics concerning communication between the broker and node hosts. Get a list of available commands with the following command: 
# oo-mco help
Use the oo-mco ping command to display all node hosts the current broker is aware of. An output similar to the following example is displayed: 
node.example.com                         time=100.02 ms

---- ping statistics ----
1 replies max: 100.02 min: 100.02 avg: 100.02
Use the oo-mco help command to see the full list of MCollective command line options.