On Mar 19, 1:45 pm, Douglas Garstang <doug.garst...@gmail.com> wrote: > I've always found the mcollective docs > athttp://docs.puppetlabs.com/mcollective/reference/basic/gettingstarted... > very confusing. > > What _exactly_ goes on the client (i.e. the remote system)? The docs > talk about editing both the server.cfg and the client.cfg files. The > server.cfg file is part of the collective package and the client.cfg > file is part of the client.cfg package. However, I though the client > package was installed on the single querying system? As you can see, > it's all quite confusing and the documentation doesn't clearly explain > it. > > Doug
I had the same issue trying to comprehend the notion of which was client and server. After I bit of friendly explanation, it made more sense. The explanation was as follows, MCollective's notion of server/client "is based on which is actually the TCP/IP server, e.g. the one that accepts the connection request." Meaning, each of your puppet "clients" runs an MCollective "server" and your central MCollective "client", that is the one that runs mco, initiates a connection to each MCollective "server" for any command you may run. So your server.cfg should go out to all servers and the client.cfg should only be on one (or a handful of) server(s). Hope that helps, -Matt -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
