Puppet users - Feb 2009 - puppet 0.20.1 (debian etch) and recipe LDAPClientNSSwitch

Hello,

Still trying to make auto configuration of my debian with nssldap and
puppet.

I have the following manifest :

---//---
# Puppet / Debian LDAP NSS Classe
#
# http://reductivelabs.com/trac/puppet/wiki/Recipes/LDAPClientNSSwitch
#
# Inspired of :p
class ldap-client {
  package { ldap-utils:
    ensure => installed
  }

  package { nscd:
    ensure => installed
  }

  service { nscd:
    ensure => running,
    require => Package["nscd"],
    provider => init;
  }

  package { openssh-server:
    ensure => installed
  }
  service { ssh:
    ensure => running,
    require => Package["openssh-server"],
    provider => init;
  }

  file { etc-ldap-dir:
    path => "/etc/ldap",
    ensure => directory,
    owner => root, group => root, mode => 755
  }

  file { ldap-conf:
    path => "/etc/ldap/ldap.conf",
    owner => root, group => root, mode => 444,
    source => "puppet://puppet/dist/ldap/ldap.conf",
    require => File[etc-ldap-dir]
  }

  file { libnss-ldap-preseed:
    path => "/var/cache/debconf/libnss-ldap.preseed",
    owner => root, group => root, mode => 400,
    source => "puppet://puppet/dist/ldap/libnss-ldap.preseed"
  }

  package { libnss-ldap:
    ensure => installed,
    require => File[libnss-ldap-preseed],
    responsefile => "/var/cache/debconf/libnss-ldap.preseed";
  }

  file { libnss-ldap-conf:
    path => "/etc/libnss-ldap.conf",
    mode => 444,
    require => Package[libnss-ldap],
    source => "puppet://puppet/dist/ldap/libnss-ldap.conf"
  }

  file { libnss-ldap-secret:
    path => "/etc/libnss-ldap.secret",
    mode => 400,
    require => Package[libnss-ldap],
    source => "puppet://puppet/dist/ldap/libnss-ldap.secret"
  }

  file { nscd-conf:
    path => "/etc/nscd.conf",
    owner => root, group => root, mode => 444,
    source => "puppet://puppet/dist/ldap/nscd.conf",
    notify => Service["nscd"];
  }

  file { libpam-ldap-preseed:
    path => "/var/cache/debconf/libpam-ldap.preseed",
    owner => root, group => root, mode => 400,
    source => "puppet://puppet/dist/ldap/libpam-ldap.preseed"
  }

  package { libpam-ldap:
    ensure => installed,
    responsefile => "/var/cache/debconf/libpam-ldap.preseed",
    require => File[libpam-ldap-preseed]
  }

  file { libpam-ldap-conf:
    path => "/etc/pam_ldap.conf",
    mode => 444,
    require => Package[libpam-ldap],
    source => "puppet://puppet/dist/ldap/pam_ldap.conf"
  }

  file { libpam-ldap-secret:
    path => "/etc/pam_ldap.secret",
    mode => 400,
    require => Package[libpam-ldap],
    source => "puppet://puppet/dist/ldap/pam_ldap.secret"
  }

  # configuration de pam pour ldap
  file { libpam-ldap-common-account:
    path => "/etc/pam.d/common-account",
    mode => 444,
    require => Package[libpam-ldap],
    source => "puppet://puppet/dist/ldap/common-account"
  }

  file { libpam-ldap-common-auth:
    path => "/etc/pam.d/common-auth",
    mode => 444,
    require => Package[libpam-ldap],
    source => "puppet://puppet/dist/ldap/common-auth"
  }

  file { libpam-ldap-common-password:
    path => "/etc/pam.d/common-password",
    mode => 444,
    require => Package[libpam-ldap],
    source => "puppet://puppet/dist/ldap/common-password"
  }

  file { libpam-ldap-common-session:
    path => "/etc/pam.d/common-session",
    mode => 444,
    require => Package[libpam-ldap],
    source => "puppet://puppet/dist/ldap/common-session"
  }

  # OpenSSH
  file { sshd-pam:
    path => "/etc/pam.d/ssh",
    mode => 444,
    source => "puppet://puppet/dist/ldap/ssh",
    notify => Service["ssh"];
  }

  file { nsswitch-conf:
    path => "/etc/nsswitch.conf",
    source => "puppet://puppet/dist/ldap/nsswitch.conf",
    notify => Service["nscd"];
  }
}

---//---


But when I try to test the client, I hve this kind of error :

~# puppetd --test
info: Caching configuration at /etc/puppet/localconfig.yaml
notice: Starting configuration run
err:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/package=libpam-ldap/ensure:
change from absent to present failed: Could not set present on ensure:
can''t
convert nil into String in file
/usr/local/etc/puppet/manifests/classes/ldap.pp at line 87
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam_ldap.conf:
Dependency package[libpam-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam_ldap.conf:
Skipping because of failed dependencies
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-password:
Dependency package[libpam-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-password:
Skipping because of failed dependencies
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-account:
Dependency package[libpam-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-account:
Skipping because of failed dependencies
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-session:
Dependency package[libpam-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-session:
Skipping because of failed dependencies
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam_ldap.secret:
Dependency package[libpam-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam_ldap.secret:
Skipping because of failed dependencies
err:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/package=libnss-ldap/ensure:
change from absent to present failed: Could not set present on ensure:
can''t
convert nil into String in file
/usr/local/etc/puppet/manifests/classes/ldap.pp at line 54
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/libnss-ldap.secret:
Dependency package[libnss-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/libnss-ldap.secret:
Skipping because of failed dependencies
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/libnss-ldap.conf:
Dependency package[libnss-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/libnss-ldap.conf:
Skipping because of failed dependencies
notice:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-auth:
Dependency package[libpam-ldap] has 1 failures
warning:
Class[main]/Node[virtual-nl3]/Class[ldap-client]/file=/etc/pam.d/common-auth:
Skipping because of failed dependencies
info:
Class[main]/Node[virtual-nl3]/Class[linuxbasics]/Class[resolvconf]/file=/etc/resolv.conf:
Removing old backup of type file
notice:
Class[main]/Node[virtual-nl3]/Class[linuxbasics]/Class[resolvconf]/file=/etc/resolv.conf/content:
synced
notice: Finished configuration run in 4.29 seconds

As I see the problems sees to be on :

  package { libnss-ldap:
    ensure => installed,
    require => File[libnss-ldap-preseed],
    responsefile => "/var/cache/debconf/libnss-ldap.preseed";
  }
and
  package { libpam-ldap:
    ensure => installed,
    responsefile => "/var/cache/debconf/libpam-ldap.preseed",
    require => File[libpam-ldap-preseed]
  }

I am running puppet client on a Debian Etch with the following :

ii  puppet
0.20.1-1                             centralised configuration management
for net


Any hints ?

/Xavier

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

I don''t know if it''s the root cause of your problem, but
responsefile
only made it into Puppet at 0.22. You may want to get the 0.24.5 version 
from testing or unstable.

http://packages.debian.org/lenny/puppet

-- 
Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi Mike,

2009/2/2 Mike Renfro <renfro@tntech.edu>
>
> I don''t know if it''s the root cause of your problem, but
responsefile
> only made it into Puppet at 0.22. You may want to get the 0.24.5 version
> from testing or unstable.
>
> http://packages.debian.org/lenny/puppet
>
>
Ok I see. So I will update to lenny''s version ...

/Xavier

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

> 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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Zach,

Chris Moates did an interesting presentation on Puppet during CPOSC a
few months back. I was actually looking at his slides for a refresher
the other day. You might find something useful in there as far as
reasons to use Puppet. He lists quite a few and why its beneficial.

You can grab a PDF of his presentation here:

http://wiki.cposc.org/_media/2008:cposc2008-moates-scalableadmin.pdf

Hope this helps!


--
Ryan Duff
web: http://www.ryanduff.net
aim: ryancduff
twitter: ryancduff




Zach Buckholz 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
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

2009/2/2 Zach Buckholz <zach.buckholz@apollogrp.edu>
>
> 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.
>
>

If you are consistent in your use of puppet you can use puppet as a
documentation resource.
Need to know how a particular server is configured? Look at the puppetcode!

With puppet you can move servers with ease!
you write generic classes or modules. Need to move a particular service?
Just include it somewhere else!

For consistency it''s really easy to apply the same configuration to a
lot of
hosts.  Need to add a host? Well, just add it to the host group, and puppet
takes care of it!

As for administration overhead. Puppet will give you less work to do! How?
You just make a puppet manifest/module/class/whatever suites you that takes
care of a certain thing. You know it works! You don''t have to remember
how.
Next time, just apply it to a host! And Done!

If you need scripts to work on multiple platforms, Puppet does this really
well. Just add eg a case statement selecting what to apply based on
operating system.

Puppet scales well. Having server being puppetmaster set up with
nginx/mongrel/puppet we can restart puppet 100 nodes at the same time having
no troubles at all. The server being a dual quadcore with 16 gb of ram is
serving approx 200 nodes and is not sweating a bit. Could easly serve the
double.

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Steve Traugott (http://www.infrastructures.org/) compares the problem
to building cars by hand, vs the production line.  It''s a nice
metaphor to use when you''re trying to demonstrate what a significant
change it can be.

We still do stuff by hand in IT even though you can demonstrate that
the error rate of doing it is far too high.  I think IT workers end up
far too often like the poor bloke on the clock in Metropolis. :)

J.


2009/2/3 Bjørn Dyre Dyresen <bjorn@dyresen.net>:
>
>
> 2009/2/2 Zach Buckholz <zach.buckholz@apollogrp.edu>
>>
>> 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.
>>
>
>
>
> If you are consistent in your use of puppet you can use puppet as a
> documentation resource.
> Need to know how a particular server is configured? Look at the puppetcode!
>
> With puppet you can move servers with ease!
> you write generic classes or modules. Need to move a particular service?
> Just include it somewhere else!
>
> For consistency it''s really easy to apply the same configuration
to a lot of
> hosts.  Need to add a host? Well, just add it to the host group, and puppet
> takes care of it!
>
> As for administration overhead. Puppet will give you less work to do! How?
> You just make a puppet manifest/module/class/whatever suites you that takes
> care of a certain thing. You know it works! You don''t have to
remember how.
> Next time, just apply it to a host! And Done!
>
> If you need scripts to work on multiple platforms, Puppet does this really
> well. Just add eg a case statement selecting what to apply based on
> operating system.
>
> Puppet scales well. Having server being puppetmaster set up with
> nginx/mongrel/puppet we can restart puppet 100 nodes at the same time
having
> no troubles at all. The server being a dual quadcore with 16 gb of ram is
> serving approx 200 nodes and is not sweating a bit. Could easly serve the
> double.
>
>
>
> >
>


-- 
Julian Simpson
Software Build and Deployment
http://www.build-doctor.com

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Zach,

Some thoughts inline:

On Mon, Feb 2, 2009 at 12:53 PM, Zach Buckholz
<zach.buckholz@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?
What problems do you want to solve?

Seriously, if you don''t have a solid answer to this question in your
head, I bet you will have trouble making Puppet work for you. What
frustrates you about doing things the old "ssh + loop over hosts"
ad-hoc shell scripting way? What fires do you spend most of your time
putting out? What things do you find yourself doing over and over and
over again? Answer these questions and you''ll be a good way towards
pitching your proposal.
> This is what I have come up with so far; (I wish the reductive labs site
had
> a wiki page for this)
Add one! That''s what wikis are all about!
>     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?
I think you''ve covered enough ground here to make a solid argument, as
long as you remember to tie it all back to costs. Like this:

Unknown configurations: Whenever a machine has a problem, I spend XX%
of my time re-learning how that machine is set up before I can even
consider what is causing the problem. If the configuration were
consistent and self-documenting, it would free up XX hours of my time
($XX amount of money) to apply towards more important/revenue-driving
tasks.

That sort of thing gets managerial types fired up. Give them a dream
of an Operations team that is involved in producing revenue rather
than being a cost sink.

My .02

--Paul

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Zach,

(Sorry in advance if this is a re-post and for not replying to the
original message. I replied, deleted and it never went through. On top
of that, the link to this message on Google Groups goes to another!)

Anyway... my original reply:


Chris Moates did an interesting presentation on Puppet during CPOSC a
few months back. I was actually looking at his slides for a refresher
the other day. You might find something useful in there as far as
reasons to use Puppet. He lists quite a few and why its beneficial.

You can grab a PDF of his presentation here:

http://wiki.cposc.org/_media/2008:cposc2008-moates-scalableadmin.pdf

Hope this helps!


--
Ryan Duff
web: http://www.ryanduff.net
aim: ryancduff
twitter: ryancduff



Paul Lathrop wrote:
> Zach,
> 
> Some thoughts inline:
> 
> On Mon, Feb 2, 2009 at 12:53 PM, Zach Buckholz
> <zach.buckholz@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?
> 
> What problems do you want to solve?
> 
> Seriously, if you don''t have a solid answer to this question in
your
> head, I bet you will have trouble making Puppet work for you. What
> frustrates you about doing things the old "ssh + loop over hosts"
> ad-hoc shell scripting way? What fires do you spend most of your time
> putting out? What things do you find yourself doing over and over and
> over again? Answer these questions and you''ll be a good way
towards
> pitching your proposal.
> 
>> This is what I have come up with so far; (I wish the reductive labs
site had
>> a wiki page for this)
> 
> Add one! That''s what wikis are all about!
> 
>>     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?
> 
> I think you''ve covered enough ground here to make a solid
argument, as
> long as you remember to tie it all back to costs. Like this:
> 
> Unknown configurations: Whenever a machine has a problem, I spend XX%
> of my time re-learning how that machine is set up before I can even
> consider what is causing the problem. If the configuration were
> consistent and self-documenting, it would free up XX hours of my time
> ($XX amount of money) to apply towards more important/revenue-driving
> tasks.
> 
> That sort of thing gets managerial types fired up. Give them a dream
> of an Operations team that is involved in producing revenue rather
> than being a cost sink.
> 
> My .02
> 
> --Paul
> 
> > 
> 

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

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.buckholz@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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Zach,

Chris Moates did an interesting presentation on Puppet during CPOSC a
few months back. I was actually looking at his slides for a refresher
the other day. You might find something useful in there as far as
reasons to use Puppet. He lists quite a few and why its beneficial.

You can grab a PDF of his presentation here:

http://wiki.cposc.org/_media/2008:cposc2008-moates-scalableadmin.pdf

Hope this helps!


--
Ryan Duff
web: http://www.ryanduff.net
aim: ryancduff
twitter: ryancduff




Zach Buckholz 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

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---