Rabbit repository management

If we are running on anything before trusty, we need to manually
manage the repository because the available version of rabbitmq
is not recent enough for our module. For trusty and later, the
available version is too recent for us to use, so we have to turn
off repo management.

This is volatile, and needs a more permanent solution.

Change-Id: I0db87d6c5cbecee8575d91e6f88ef43a947967ff

manifests/params.pp

@@ -27,8 +27,10 @@ class storyboard::params () {
     'Debian': {
       if $::operatingsystem == 'Ubuntu' and $::operatingsystemrelease >= 13.10 {
         $apache_version = '2.4'
+        $manage_rabbit_repo = false
       } else {
         $apache_version = '2.2'
+        $manage_rabbit_repo = true
       }
     }
     default: {

manifests/rabbit.pp

@@ -23,9 +23,12 @@ class storyboard::rabbit (
   $rabbitmq_user_password
 ) {
 
+  require storyboard::params
+
   class { 'rabbitmq':
     service_manage    => true,
-    delete_guest_user => true
+    delete_guest_user => true,
+    manage_repos      => $storyboard::params::manage_rabbit_repo,
   }
 
   rabbitmq_user { $rabbitmq_user: