Hello all.
We're running Puppet to manage our linux-servers, but as of now we don't really have a good setup for dealing with different environments (production, qass, and so forth). The puppet manifests have been added to Subversion. Our current apporach for staging for example a puppet class, we create one class for each environment (appending "_prod", "_qass", and so forth to the class name), and make changes to the class contents accordingly. I'm sure there are better ways of doing this kind of thing. So what we need is a structured way of staging puppet manifests, but in two slightly different aspects: 1. Manifests that are exactly equal in all environments (for example linux hardening) 2. Manifests that have different parameters in the different environments (for example DNS setup) I suspect using modules is the way to go. I'm not too experienced with version control yet, but I'm sure this type of tool may get us far. But before we start restructuring our puppet setup I'd like to hear from other puppet users on how they use Puppet and Subversion to manage manifest staging and so forth. Best regards, Kenneth Holter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
