Nigel Kersten a écrit :
All puppet changes are applied with explicit and manual "puppetd -t"
All interactions with puppet are manual and CLI based. Admin should manual
valid that changes that are being applied are ok.
This is the kind of use of puppet that I think it rarely speak about here ;)
Many many many people run like this.
I'm happy to see that, but my feeling was different.
I rarely see topics about this kind of use and I'm mostly seeing
improvement (in puppet-dev) related to puppet as a daemon, and no CLI one.
2 examples:
. puppetd --test
This will output a log of lines with fancy colors :)
This really looks like (and in fact, it is) a log mode which is directly
output to console. For admins, expecially new ones you never use Puppet
before, this output is really difficult to understand.
. object selection
When you've got a lot of object not up to date, you deciced that you can
safely apply 'file:/foo' but you do not know why package 'bar' should be
uninstalled and you will asked your collegue John about that. So you
say: I only apply file 'foo' changes.
This can only be done using tags, but 'tags' is not strict, their is not
to say: "only a file named 'foo'"
This is two examples, but we had success for other patches :)
Here is :)
What was the "not a success" aspect of your tickets?
Patch was not finished and landed or feature could not have been
developped (either by puppetlabs or us)
Thank you to hake a look to all of this :)
Aurélien
--
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.
