mcollective module - hiera integration

117 views
Skip to first unread message

Mike Reed

unread,
Sep 11, 2014, 2:48:23 PM9/11/14
to puppet...@googlegroups.com
Hello all,

I have a quick question regarding the puppet-forge mcollective module and it's integration with hiera.  I'd like to abstract some values into hiera instead of using site.pp to define parameter values for the mcollective class.  I've got hiera and the mcollective module already working with the following two parameters (i've moved the $middleware hosts parameter for the sake of this post, from it's original location in init.pp):

class mcollective (
  # which subcomponents to install here
  $server                  = hiera('::mcollective::server'),
  $client                   = hiera('::mcollective::client'),
  $middleware_hosts = hiera('::mcollective::middleware_hosts'),

My hiera source looks like this:
---
classes: mcollective
mcollective::middleware: true
mcollective::server: true
mcollective::middleware_hosts:
  - server-01.local

So far everything is working fine but now I'd like to add the $middleware parameter and assign it to my hiera config (I've already added 'middleware' per the above definition).  The documentation states that I'd simply add the below 'middleware' parameter to my node definition:

node 'broker1.example.com' {
  class { '::mcollective':
    middleware         => true,

The problem is that I can't find that value anywhere in the module to replace the default 'false' with my hiera directive.  I've been combing through the module and I can't seem to find it. My understanding is that I need to replace the 'middleware' parameter just like I did above with $server/$client. 

Can anybody point me in the right direction on where I would change this value?  I'm still getting used to hiera and these module structures and, I do have to say that the mcollective module is probably the most complicated I've worked with so far.

Thanks you in advance for your help.

Cheers,

Mike

Matthew Hyclak

unread,
Sep 11, 2014, 3:16:18 PM9/11/14
to puppet...@googlegroups.com
That option was removed in the latest version of the module[1]. You'll have to roll back a version to do it that way, but the way forward appears to be using an external option to configure the middleware for you. For now, I just pinned version 1.1.6 until I can get time to implement the middleware module as well.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d7b52df3-aeaa-4cba-bc49-8743c0a89371%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mike Reed

unread,
Sep 11, 2014, 4:33:03 PM9/11/14
to puppet...@googlegroups.com
Oops, I suppose if I would have read the module changelog, I could have avoided this entire post.  Thank you for the help and info...much appreciated.

Cheers,

m. 
Reply all
Reply to author
Forward
0 new messages