oo-install: premature restart_services

Remove unneeded RESTART_REQUIRED=true; do not want to start services
before they are configured.

Bug 1122297 - premature restart_services blocks oo-install
https://bugzilla.redhat.com/show_bug.cgi?id=1122297
Merge pull request #420 from sosiouxme/bug1122297

oo-install: premature restart_services
openshift.ks, configure_activemq: Mark vars local

Declare networkConnectors and authenticationUser_amq as local variables.
openshift.ks: Improve descriptions for replication

Clarify that ports may be specified for CONF_DATASTORE_REPLICANTS and must
not be specified for CONF_ACTIVEMQ_REPLICANTS.
openshift.ks: Fix replication for routing plug-in

Fix configure_routing_plugin to configure the routing plug-in with all
ActiveMQ replicants instead of only the first.

This commit fixes bug 1109052.
openshift.ks: Configure ActiveMQ redelivery

Modify configure_activemq to configure redelivery for the routinginfo
queue, which may be used by the ActiveMQ routing plug-in.

This commit fixes bug 1132208.
openshift.ks: Always set routing_plugin_user/pass

In set_defaults, set the routing_plugin_user and routing_plugin_pass
variables when installing the "broker" or "activemq" component instead of
setting them only when installing the "broker" component.  These variables
are used when configuring ActiveMQ and so may be used even if the "broker"
component is not being configured

This commit fixes bug 1110680.
Merge pull request #432 from Miciah/bug-1109052-fix-replication-for-routing-plugin-bug-1132208-configure-activemq-redelivery-bug-1132209-always-set-routing_plugin_user-and-_pass

Bug 1109052 fix replication for routing plugin bug 1132208 configure activemq redelivery bug 1132209 always set routing plugin user and  pass
installer: set better mcollective timeouts

Bug 1122872 - "oo-mco" does not timeout when no ActiveMQ available
https://bugzilla.redhat.com/show_bug.cgi?id=1122872

Bug 1065048 - broker does not handle activemq outages gracefully
https://bugzilla.redhat.com/show_bug.cgi?id=1065048

When ActiveMQ is down or unreachable, with the previous default settings,
broker tools that operate via mcollective simply hang indefinitely.
With these defaults, mcollective queries will fail with useful error
after 6.3 seconds of retries, and a link is given to display options if
an administrator would like to adjust the behavior.

Additionally, the node interval for retrying a connection to ActiveMQ
was decreased to 4 seconds instead of the default 30. This way, nodes
will be visible faster after ActiveMQ returns.
Merge pull request #440 from sosiouxme/bz1122872

installer: set better mcollective timeouts