Bug 1057726 - Remove jetty.xml from ActiveMQ configuration
Merge pull request #293 from brenton/BZ1057726

Bug 1057726 - Remove jetty.xml from ActiveMQ configuration
<install> Remove the jetty and jetty realm configuration

- Add comment to tell users that they should enable authentication and
  set passwords if enabling jetty.xml
Merge pull request #295 from detiber/2.0-activemq-5.9.0

<install> Changes for activemq-5.9.0 update - enterprise 2.0
openshift.ks: Optionally register with RHN/RHSM

configure_rhn_channels, configure_rhsm_channels: Only register with RHN or
RHSM if credentials are provided.

configure_rhsm_channels: Only attach to a pool if a pool id is provided,
and skip any pools that are already attached.

validate_preflight: Allow the installation to proceed even if the rhn or
rhsm installation method is being used without any credentials provided,
as long as the host is already registered, and also allow installation
to proceed with the rhsm method even if no pool id is provided as long
as the required repositories are already available and credentials are
not provided (providing credentials would imply that we should register,
and re-registering would remove the existing repositories).

These changes allow the user to register with RHN or RHSM before running
the script and then use the rhn or rhsm installation method to have the
installation script configure channels, priorities, and excludes and
validate the configuration.

This commit fixes bug 1056906.
<install> note that broker auth must be synchronized
Merge pull request #297 from sosiouxme/enterprise-2.0

comments-only change so no QA needed
reset_deployment.rb: added "clean out" script

This script enables an administrator to quickly reset the
deployment back to zero after putting it through its paces.
https://lists.openshift.redhat.com/openshift-archives/dev/2014-January/msg00191.html
Merge pull request #277 from Miciah/openshift.ks-make-rhsm-rhn-registration-and-pool-attachment-optional

openshift.ks: Optionally register with RHN/RHSM
<install> Set default BIND key algorithm to MD5

Change the default settings for CONF_BIND_KEYALGORITHM and
CONF_BIND_KEYSIZE to HMAC-MD5 (instead of HMAC-SHA256) and 512 (instead of
256), respectively, so that the DNSSEC key generation, BIND configuration,
and dns-nsupdate plug-in configuration will use HMAC-MD5 (instead of
HMAC-SHA256) by default.

OpenShift Enterprise 2.0 only supports the HMAC-MD5 algorithm for nsupdate.

This commit fixes bug 1066171.
Merge pull request #299 from Miciah/bug-1066171-change-default-bind_keyalgorithm-setting-to-HMAC-MD5

<install> Set default BIND key algorithm to MD5