Everything on here is good and like Paul said it is probably just as important to figure out what pains you are trying to solve, but I'd like to add a point.
Once you have Puppetized the infrastructure, you can reliably rebuild it. This has a huge impact on scenarios where you want/need to move datacenters, build in clouds or recover from disasters. Might be worth a slide in a presentation... On Mon, Feb 2, 2009 at 1:53 PM, Zach Buckholz <zach.buckh...@apollogrp.edu>wrote: > > This may sound like a confusing / trick question, so please bare with me. > > What problem(s) will puppet solve? Why would I use it? > > I am trying to pitch the use of puppet in our environment and need to > follow a formal proposal model. Which means I need to start with a problem > to solve or situation to improve. > > The concept of what puppet will do needs to be explained to non-technical > business leaders. > > This is what I have come up with so far; (I wish the reductive labs site > had a wiki page for this) > > What is the problem? > Unknown configurations > Environment is not dynamic > Messy > No central model > Hard to change > No consistency > Administration overhead > Reactive instead of proactive > Unorganized > Need scripts to work with linux and solaris > Hard to scale > > Can anyone add (non-technical explanations) to the above list? > > > Zach > > This message is private and confidential. If you have received it in > error, please notify the sender and remove it from your system. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
