Fixes NetworkManager Installation Error

Previously, the puppet agent installation was failing due to the
NetworkManager-Wait-online service not being installed:

Error: Could not enable NetworkManager-wait-online: Execution of
'/sbin/chkconfig NetworkManager-wait-online on' returned 1: error
reading information on service NetworkManager-wait-online:
No such file or directory

This service appears to be unneeded for Fedora 19.
Ensures rubygem-bundler on Fedora

Previously, Ruby bundler commands would fail because the
rubygem-bundler package was not being installed (as required) on
Fedora systems.
Fixes and Optimizes the Apache Configuration

Previously, the Apache servername.conf files existed in different
classes for Brokers and Nodes.  Furthermore, the broker class did
not contain a dependency on the httpd service.  Therefore, httpd
would not be enabled and running after the puppet agent run.
Adds Support for Configuring NTP Servers

Previously, the ntp servers used by an OpenShift deployment were
hard coded to:

['time.apple.com iburst', 'pool.ntp.org iburst', 'clock.redhat.com iburst']

This causes problems for deployments that do not allow ntp clock
synchronization with outside entities.  This patch adds the
$ntp_servers parameter for configuring an array of NTP servers and
uses the above mentioned array of servers to maintain backwards
compatibility.
Fixes Cartridge Installations

Previously, only the mysql and mariadb cartridges would install
and appear in the oo-admin-cartridge list.  Since the oo-admin
command is no longer needed, only a refresh of mcollective is
being done for the cartridges to appear correctly.
Fixes Mcollective Server Dependencies

Previously, the mcollective service would be in an "up" state
upon the successful deployment of a node.  Although, the service
would be "up", the broker would be unable to mco ping the
node.  This was due to the following reasons:

1. The service not being restarted after the associated config
files were changed by puppet.

2. DNS registration and resolution being configured after the
openshift_origin::mcollective_server class.  The node could not
resolve the broker's name, causing the mcollective service to
function inproperly until the service was restarted.
Add Support for Example Top Level Manifests

Previously, a user would need to manually create the top-level
manifest (configure_origin.pp).  This patch creates 2 sample
top-level manifests in the root DIR of the project and will help
reduce user error during deployments.
Fixes Startup of Node Services

Previously, several node services such as oddjobd and
opeshift-node-web-proxy would be in a "down" state after the
successful completion of a puppet agent run.

This patch creates the proper dependencies between configuration
files and services to ensure proper service management.