Using "latest" and controlling the repositories yourself is best practice I believe. On Nov 16, 2010 2:16 PM, "jcbollinger" <john.bollin...@stjude.org> wrote: > > On Nov 16, 11:03 am, Andy <andy....@gmail.com> wrote: >> Also, do you typically create your own mirrors of the repositories to >> control the repository contents? > > I don't know about Luke, but I do. That provides not only control > over the repository contents, but also (for me) much better > performance, as my queries and package retrievals do not have to leave > my internal network. I also get better availability because the > repository has fewer clients, and if it ever goes down I can fix it. > > Moreover, you then have the option to rely on your local repository > instead of Puppet for control of package versions. That is, maintain > in your repository only those software versions you want to use, and > let your Package resources all simply specify the "latest" version. > No more tweaking manifests when you qualify a new package version! > > > Cheers, > > John > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> . > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. >
-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
