Well, I'll tell you that for now some kind of configuration is difficult to be done with puppet. At least I couldn't find a way to do it. Ex: controlling a /etc/passwd file but partially with a libnss compat syntax. This means entries of local users are no controlled but entries beginning with a '+' are. As I couldn't find a way to do it, for now it is not being controlled by puppet.
Em sexta-feira, 3 de maio de 2013 15h02min18s UTC-3, Martin Langhoff escreveu: > > While I prep my scripts and tool up for a large infra, I want to > revisit a question that I ask myself regularly: what do people not > manage with Puppet (or wish they weren't)? > > In my situation (a RH-style world), initial base system install, inc > disk layout and initial networking is handled with kickstart > > For example: Do you exclude mountpoints? Network/SAN mountpoints? > Advanced network configs? > > What are the reasons to exclude a particular item? How do you manage it > instead? > > cheers, > > > > m > -- > [email protected] <javascript:> > - ask interesting questions > - don't get distracted with shiny stuff - working code first > ~ http://docs.moodle.org/en/User:Martin_Langhoff > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
