Dan,
it is much easier to manage puppet with a simple puppet class.
what I do, is to include a class which configures puppet it self.
in that class (which is also applied to the puppetmaster) you can define
everything you want (from config files to puppet version etc).
the only problem you need
Most of the machines that we are working with are already installed, so we
cant rely on preconfig.
I am just proposing the wrapper script to control which order config tasks
execute in. Using tags to create PRECONFIG calls
seems like an appealing solution to get around the need to constantly
decla
On 2/2/2009 4:36 AM, Xavier Beaudouin wrote:
> Do I use debconf-get-selections and keep only lines about libnss-ldap ? or
> is there any better way to get this file ?
That's what I've always done. Something like:
debconf-get-selections | grep '^libnss-ldap '
should work.
--
Mike Renfro /
Hi Mike,
2009/2/2 Mike Renfro
>
> 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 ve
Hi all I'm getting this same error with the Puppet RPMs from EPEL.
I have installed:
puppet-0.24.7-4.el4
ruby-augeas-0.2.0-3.el4
augeas-0.3.5-2.el4
augeas-libs-0.3.5-2.el4
facter-1.5.2-1.el4
on a 64 bit CentOS 4.7.
but I'm getting this error with this code:
augeas { "augeas-sshd_config":
con
> 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
Hello puppeteers. I discovered a problem with newer versions of yum.
When puppet checks the repository for later versions it uses the
following command:
/usr/bin/yum -d 0 -e 0 list available package
Earlier versions of yum printed nothing and exited 0 if no new
packages were available.
Unfortun
This seems much better to me. Specify what you want directly.
Is there ever going to be more than one file that could collide? You
probably only need the $bbVersion in the source param that way you can use
one name and get rid of the path.
On Sun, Feb 1, 2009 at 11:02 PM, chakkerz wrote:
>
Hi
> Hello puppeteers. I discovered a problem with newer versions of yum.
> When puppet checks the repository for later versions it uses the
> following command:
>
> /usr/bin/yum -d 0 -e 0 list available package
>
> Earlier versions of yum printed nothing and exited 0 if no new
> packages were
Hi,
I am putting together a solution to allow puppet to manage its agents
The following things need to be managed:
1. Ensure that the puppet agent version is the same as the server version
(and that we upgrade if there is a version mismatch)
2. Ensure that all facts are imported (easy enough with
Hello all,
I have set up a public svn repository with some facts that we have
written over time:
https://svn.ikw.uni-osnabrueck.de/dav/ikwadmin/public/puppet/facts/
(yes, it is svn).
Now, I was wondering where to document this on the puppet-wiki (or
should it rather be the facter-wiki)
http
Moving existing unmanaged system under Puppet has it's own set of issues,
but what Ohad said is going to work. Let Puppet manage Puppet, the version
and puppet.conf.
Why do you want to use an Initialize tag? Wouldn't you at least want to know
if not have Puppet fix it if the state anything you me
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:
Sorry about the noise I found how to get such files...
debconf-get-selections | grep libnss-ldap > libnss-ldap.preseed
/Xavier
PS: maybe this can be updated on the wiki ?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
On 29 jan, 21:56, Luke Kanies wrote:
> I'd say the answer depends on how often you have consistent groupings.
It's more about inconsistencies :-)
> If the list of mounts that a given service or host uses is relatively
> arbitrary, then there's no real way to get away from the 'realize'
> ca
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 / Te
Hello,
I am trying to use the recipe
http://reductivelabs.com/trac/puppet/wiki/Recipes/LDAPClientNSSwitch, but I
am bloqued about special debian thing.
The extract is :
file { libnss-ldap-preseed:
path => "/var/cache/debconf/libnss-ldap.preseed",
owner => root, group => root, mode => 4
On Mon, 2009-02-02 at 13:08 -0800, Jeff wrote:
> Hello puppeteers. I discovered a problem with newer versions of yum.
> When puppet checks the repository for later versions it uses the
> following command:
>
> /usr/bin/yum -d 0 -e 0 list available package
>
> Earlier versions of yum printed noth
On Jan 13, 3:00 am, Rodney Quillo wrote:
> Hi Blake and others,
>
> I got it running with the following gems:
>
> actionmailer (2.0.2)
> actionpack (2.0.2)
> activerecord (2.0.2)
> activeresource (2.0.2)
> activesupport (2.0.2)
> daemons (1.0.10)
> gem_plugin (0.2.3)
> hobofields (0.7.5)
> hobo
Yeah, looks like it works a treat.
The collision occurs on the container (the directory) not the files. I
guess if there is a file collision, then the second file will win,
because of the require =>s
It took a while for the source param bit to get through, but that's a
good idea ... reduces typos
On Mon, 2009-02-02 at 12:51 -0800, Larry Ludwig wrote:
> Hi all I'm getting this same error with the Puppet RPMs from EPEL.
>
> I have installed:
> puppet-0.24.7-4.el4
> ruby-augeas-0.2.0-3.el4
> augeas-0.3.5-2.el4
> augeas-libs-0.3.5-2.el4
> facter-1.5.2-1.el4
>
> on a 64 bit CentOS 4.7.
>
> b
21 matches
Mail list logo
