On Feb 1, 2011 11:56 PM, "KC Braunschweig" <[email protected]> wrote:
> On Thu, Jan 27, 2011 at 7:54 AM, Rob McBroom <[email protected]>
wrote:
> > On Jan 26, 2011, at 9:15 AM, Howard Jones wrote:
> >
> >> I have a couple of applications (backup, Cacti, Asset Tracking) where I
want a node to have some package and config installed, and once that is
done, some config to be done on another system to register the client with a
central server. Is there a standard way to do this, short of having some
kind of web service accessible from all the client systems?
>
> If you're using mcollective also, this might help:
>
> http://docs.puppetlabs.com/mcollective/reference/plugins/registration.html
>
> If you go this or the exported resources route, let us know how it
> worked out for you. I haven't implemented either yet but both are in
> the plan for the coming months.
For what it is worth, my recommendation was rooted firmly in practical
experience; we exported a number of exec operations with "unless" clauses
that did this remote registration to tools that were too hostile to more
stable changes.
Regards,
Daniel
--
Puppet Labs Developer –http://puppetlabs.com
Daniel Pittman <[email protected]>
Contact me via gtalk, email, or phone: +1 (877) 575-9775
Sent from a mobile device. Please forgive me if this is briefer than usual.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
