On Fri, Nov 09, 2012 at 08:04:44AM -0800, Christian wrote: > I have some questions in terms of how to use puppet of configuration > management for software patches. My previous approach was it to create a > puppet module for each patch ... Like Patch1 includes (FileA, FileB, > FileC), Patch2 includes (FileD, FileE)... So far so good and that works but > now i have to create a Patch3 with lets say FileF and FileA included. As > you can see there will be a puppet conflict as i can't deploy the same > files within different modules. What is the right architecture and method > to manage software patches? Is it to use rpms instead of? Or are there > other ideas how to manage that with puppet. >
Hi, If you should decompose them you can define them as different classes. That however as you know will lead to an explosion of different classes which can become pretty unmaintainable with time ... The question is if you *should* do it this way. I don't know so much about your system so I can't tell. We are mostly updating with proper package management and build our software for upgrades. Maybe if you tell us more about your system/setup, we can give you a better advice? Best, Nikola > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/YNceAdQNZr4J. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
