Service doesn't start in runlevel 2 by default
Updated to connect to new hubs

We have 4 new hubs and want all of rpc on the new hubs. So datacenter
is hard coded to rpc
Script added to help Support with the installation process

This script was created to allow support to have a single installation
process for RabbitMQ, Chef-Server, and the Chef cookbooks.
Merge pull request #28 from cloudnull/support-chef

Script added to help Support with the installation process
Merge pull request #26 from mattt416/fix_script

Service doesn't start in runlevel 2 by default
added chef-server.rb option for host and rabbit env
Make a DATACENTER environment variable

so it can be overridden at run time
use default value if set
Merge pull request #29 from JCallicoat/master

Make a DATACENTER environment variable
updated chef-install to allow the version to be configurable
Merge pull request #32 from cloudnull/heartbleed_update

updated chef-install to allow the version to be configurable
Change file check order

The `/etc/lsb-release` file exists on CentOS 6.5, too. Switching the order of this check allows for both Ubuntu and CentOS's Chef Server installation to succeed since `/etc/system-release-cpe` is exclusive to the latter.
Merge pull request #33 from jpmontez/patch-1

Change file check order
added RabbitMQ URI override
Merge pull request #34 from cloudnull/master

added RabbitMQ URI override
Merge remote-tracking branch 'upstream/master'