On Wed, Feb 9, 2011 at 3:07 AM, prayther <prayt...@gmail.com> wrote: > > I am specifically trying to eliminate the need for puppet master for 2 > reasons (i am just scratching the surface on what puppet can do and > how it works. nooby). 1 simplicity to others to use an open systems > management process that has red hat satellite server at the center > (all i want them to NEED to understand is satellite and channels) of > it and 2 so i can use the satellite's disconnected feature to be able > to deliver a complete solution to disconnected networks. > > i am packaging puppet content in an RPM's and delivering it that way. > i also believe i have it figured out how to deliver content for > security, application and host in separate RPM's > > so i too have been looking for a concise, this is what you loose and a > brief description of what that means in a "mature" enterprise > installation.
There's quite a bit of functionality in Puppet Master so this is not a comprehensive list. Puppet Master provides a centralized location for: managing manifests, modules, and environments syncing custom facts and types/providers reports puppet:/// file service certificates filebucket backup collecting facts from clients (future inventory service) You can achieve some these functionality without a puppet master, but you would still have the same hurdles for disconnected networks. Jordan's slides list several differences so I won't reiterate them here. Another key difference is the agent only receives a catalog in master/agent mode. In masterless mode you must provide the puppet manifest/templates to each client system. The catalog is system specific and does not contain any configuration information about other systems, the manifests and templates would have all the configuration data for all systems. It would be non trivial to keep the configuration data isolated in masterless mode if you have a desire to segment and isolate configuration data by system, or even system roles (i.e. my website database system should not contain puppet manifest with my financial database password). The rest of the features are mainly trade off between a central service vs. distributed service, and the ability to isolate access (i.e. if you use an ENC, puppet master is the only system that needs access to the LDAP/CMDB/database, if you implement something similar in a masterless environment, every agent needs an account and access to that central source of information). Thanks, Nan -- 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.
