On Thu, May 10, 2012 at 6:44 AM, Daniel Sauble <djsau...@puppetlabs.com> wrote: > Hey all, > > I've been designing a new feature for Puppet, and wanted to get some > kick-back from the community to see if you think this is needed or not. The > feature is called Puppet Sites, and meets some specific goals by means of a > few tasks. > > Securely add nodes to your deployment without manually signing certificates > on the CA... > > ...so that you can have the advantages of autosigning without its security > problems. > > Get a list of all the nodes in your deployment... > > ...so that a single command can give you what previously you had to trawl > multiple services (ENCs, CAs, etc...) on each Puppet master in your > deployment to retrieve. > > Store connection information for Puppet services in a central location > (accessible from manifests, puppet.conf, and defaults.rb)... > > ...so that you don't have to manage puppet.conf files on each node in your > population > ...so that agent/master/CA configuration stays consistent across your > deployment > ...so that you can update your config and fetch a new catalog in a single > operation. > > Thanks in advance for the feedback! > - Daniel
Hi Daniel, thanks for dropping a note to get some feedback on this. While these features sound very nice I personally would find it interesting and might have more to add if you went into a bit of detail about how you plan to implement these features. Thanks, -- Romeo -- 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.
