On 04/19/2013 07:06 PM, Ken Coar wrote:
> Simplicity. Keeping everything in the puppet milieu, which is already
> set up. Don't want to introduce new mechanisms and dependencies
> rather than making use of what's already there.
I'm not so sure about that.
I do believe that you could do what you have in mind, but you'd need an
additional master, not an agent node "somehow serving files".
Assuming you do setup a master of your own, and setup the manifest so
that the new server will be used like
file { "foo":
source => "puppet://local.puppet.master/modules/foomod/foo"
}
Even then, your local master would need to share the SSL certificate of
the original master, since you likely cannot make your agent use
different certificates per master.
So in the end, setting up an additional puppet fileserver may imply the
opposite of simplicity. But if you *can* setup an NFS share, rsync
target, svn checkout etc. without much hassle, as David suggests, that
may make things very simple indeed.
Cheers,
Felix
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
