docs: middle ware parameter [how to connect mcollective with a middleware]
gl00ten opened this issue · 15 comments
node puppet {
class { '::mcollective':
client => true,
middleware => true,
middleware_hosts => ['puppet.domain1.net'],
}
}using this on puppet master to install mcollective and it's not working because it says "middleware" parameter is not valid?
Invalid parameter middleware on Class[Mcollective] at /etc/puppet/manifests/site.pp:6 on node puppet.salesseek.net
well, it's not entirely wrong, https://github.com/puppet-community/puppet-mcollective/blob/master/manifests/init.pp#L28-L41
so we should fix our docs
Was reading that just now :P
So the readme is outdated. What kind of manifest do I need to set up a puppetmaster with the middleware and an agent?
node puppet {
class { '::mcollective': middleware_hosts => ['puppet'], }
}
node puppetagent {
# class { '::mcollective':
# client => true,
# middleware_hosts => ['puppet'],
# }
}This is what I got so far, but getting dependency errors, so I'm thinking it's not enough?
I am also stuck on this issue ,
can anybody explain how to solve it?
Full disclosure, I've never used or hacked this module.
Still, I just went hunting for your missing parameter, and it turns out we don't support middleware management anymore since 9be4fed.
To setup your queue manager, you should pick an ActiveMQ or RabbitMQ module and add it to the respective profile(s).
I never tried either option, and cannot supply any second hand knowledge either. Sorry.
@fullmooninu depends on your scale, i guess.
for a small (we're running <500 machines) setup, ActiveMQ serves us quite well.
ty ty both. I ended up manually installing rabbitmq followed by mcollective, using someone's written instructions.
Oh nooo 😧
And thus we fail...
[silent sobbing]
pats
there there
Reopening so that this won't fall under the rug.
We desperately need to update the docs. This is a pretty serious issue from my point of view.
Hello:
Is this still needed?
I'll try and clean this up.