Merge pull request #51 from sosiouxme/enterprise-1.2

I got rid of plugins we're not using. Then, restructured the script such that the procedure operates in a way that will be a little more friendly to oo-installer. Specifically:

* The major sections are broken into bash functions (so they can be specifically run with CONF_ACTIONS) and delineated in the output so that progress can be tracked and partial re-run is possible.
* All of the subscription mgmt is done, then all of the package installing, then all of the configuring. This way you can re-run the package install (the most likely part to fail), without configuration having occurred that could break things (e.g. nameserver, sshd, etc.).
<openshift.ks> Added zerombr line for full automation of KS
Starting in anaconda-13.21.176-1 shipped with RHEL 6.3
The 'zerombr' line was necessary to have fully automated
kickstart. Documented in RHEL 6.3 technilate notes and
Red Hat Article 117513
Merge pull request #54 from kyle-benson/rebase_ksmod

<openshift.ks> Added zerombr line for full automation of KS
openshift.ks: Add CONF_DATASTORE_REPLICANTS

Add the CONF_DATASTORE_REPLICANTS setting, which specifies
a comma-separated list of hostnames that will be configured to constitute
a MongoDB replica set.  This setting defaults to the value of
CONF_DATASTORE_REPLICANTS.

If the number of replicants is 1 (which is the case with the default
value), then replication is not configured.

Add the CONF_MONGODB_KEY setting, which specifies the key that will be used
by replicants.  This setting defaults to 'OSEnterprise'.

Add the CONF_MONGODB_REPLSET setting, which specifies the name of the
replica set.  This setting defaults to 'ose'.

Factor the new execute_mongodb function out of configure_datastore.

Factor the new configure_datastore_add_users function out of
configure_datastore.

Add the configure_datastore_add_replicants function, which can be
invoked as an action on the host that is to be the primary.  Note that we
cannot perform this step during the initial installation because it will
fail if not all hosts in the replica set are up and running mongod.

Factor the new set_mongodb function out of configure_datastore.

Modify configure_datastore to configure user accounts only for
a non-replicated setup and otherwise to configure appropriate settings
(rest, journal, replSet, and keyFile) for a replicated setup and to
write out mongodb.key.

Modify configure_controller to set MONGO_HOST_PORT to the entire replica
set.

Modify set_defaults to accommodate the new settings and to append the port
specification :27017 to each hostname in the replica set that does not
already have a port specification.
openshift.ks: Add CONF_ACTIVEMQ_REPLICANTS

Add the CONF_ACTIVEMQ_REPLICANTS setting, which specifies a comma-separated
list of hostnames for ActiveMQ broker replicants.  This setting defaults
the value of CONF_ACTIVEMQ_HOSTNAME.

Add the CONF_ACTIVEMQ_AMQ_USER_PASSWORD setting, which specifies the
password to use for ActiveMQ's "amq" user (see below).

Modify configure_activemq so that if a list of replicants is specified
where that list includes hostnames other than the hostname of the host that
is currently being configured, configure_activemq will add appropriate
networkConnector entries to activemq.xml, add an "amq" user with the
password specified by the CONF_ACTIVEMQ_AMQ_USER_PASSWORD setting, and open
port 61616 (which replicants use to communicate using the OpenWire
protocol).  Also modify the policyEntries configuration to match Puppet
Labs' recommendations.

Add a new function generate_mcollective_pools_configuration, which
outputs the plugin.activemq.pool.* settings for the MCollective
configuration files using the new CONF_ACTIVEMQ_REPLICANTS setting.

Use this new generate_mcollective_pools_configuration function in
configure_mcollective_for_activemq_on_broker and
configure_mcollective_for_activemq_on_node so that a new broker or node
host is configured to use whatever replicants are specified by
CONF_ACTIVEMQ_REPLICANTS.
Factor configure_rhc out of install_rhc_pkg

For consistency with commit 48336e7e05ebf3d9d2d20d1975f4f005c9999928,
split configure_rhc out of install_rhc_pkg.
Merge pull request #52 from Miciah/openshift.ks-add-CONF_DATASTORE_REPLICANTS

openshift.ks: Add CONF_DATASTORE_REPLICANTS
Merge pull request #56 from Miciah/openshift.ks-factor-configure_rhc-out-of-install_rhc_pkg

Factor configure_rhc out of install_rhc_pkg
<install> don't always set the hostname

If the "hostname" specified is an IP, don't set that.
Also, if they don't want their hostname overwritten, there's an option
for that.
Also, superseding the hostname in the dhcp conf appeared to do nothing
(or be overwritten by sysconfig) so it's removed.
Add additional named host entries when using named component

* Provide a NAMED_ENTRIES argument to the script or export
  CONF_NAMED_ENTRIES environment variable with comma delimited
  host:ipaddress pairs (colon delimited host and ipaddress)
openshift.ks: Delete NAMED_ENTRIES

configure_named: Instead of setting NAMED_ENTRIES=${CONF_NAMED_ENTRIES}
and then using NAMED_ENTRIES, just use CONF_NAMED_ENTRIES directly.
<install> ability to not create host DNS entries
<install> separate host DNS out from app
<install> ability to skip jboss repos/carts

Conflicts:
	enterprise/install-scripts/amazon/openshift-amz.sh
	enterprise/install-scripts/generic/openshift.sh
	enterprise/install-scripts/openshift.ks
<install> register to RHN with --force; re-runnable
<install> introduce yum CDN base URL; refactor accordingly
<install> bind_key; preflight checks; docs

* added some preflight sanity checks like "is this RHEL 6?"
* compressed some verbose code defining yum repos
* after some research, discovered that the bind key is not half of a
keypair and can be set arbitrarily; re-enabled that ability.