On Tue, Oct 9, 2012 at 10:36 AM, R.I.Pienaar <r...@devco.net> wrote: > > > ----- Original Message ----- >> From: "Andrei-Florian Staicu" <andrei.sta...@gmail.com> >> To: puppet-users@googlegroups.com >> Sent: Tuesday, October 9, 2012 8:29:41 AM >> Subject: Re: [Puppet Users] mcollective tcp port >> >> On Tue, Oct 9, 2012 at 10:21 AM, R.I.Pienaar <r...@devco.net> wrote: >> > >> > >> > ----- Original Message ----- >> >> From: "Andrei-Florian Staicu" <andrei.sta...@gmail.com> >> >> To: puppet-users@googlegroups.com >> >> Sent: Tuesday, October 9, 2012 7:28:25 AM >> >> Subject: [Puppet Users] mcollective tcp port >> >> >> >> Hi all, >> >> >> >> I'm trying to prepare a common config for the DMZ hosts, and also >> >> to >> >> account for future infrastructure upgrades. >> >> Right now, I'm using only the puppet agent, triggered via SSH. >> >> This mean an open port 8140, from the client to the puppetmaster >> >> (is >> >> it required also the other way around?). >> >> I would like in the future to move to mcollective. >> >> Do you know what tcp port i should allow? The direction should be >> >> from >> >> the puppetmaster to the client. Do I need it also the other way >> >> around? >> > >> > >> > Like puppet its from managed node -> puppet master, usually port >> > 61613 >> > though you can pick any >> >> So there's no push involved? Only the client polls the servers? > > a persistant connection is made from managed node to the middleware > broker and comms over that TCP connection is bi-directional >
Excellent. Thanks a lot for your explanation. -- 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.
