On 12/01/2010 04:04 PM, Trevor Hemsley wrote:
> On 01/12/2010 14:53, Martijn Grendelman wrote:
>> Hi Trevor,
>>> More likely just adding
>>>
>>> usecacheonfailure = false
>>>
>>> to the [puppetd] stanza in /etc/puppet/puppet.conf will help.
>> I am yet unfamiliar with that option, but just as a r
Hi list,
for those interested: I've created a homebrew package provider for puppet.
You can get it from https://github.com/jedi4ever/puppet-homebrew
enjoy :)
Patrick
P.S. You need a newer version of puppet as it uses the new module structure
--
You received this message because you are subsc
On Nov 22, 3:06 am, Ramon van Alteren wrote:
> Hi All,
>
> We're trying to get a hudson build working for our puppet modules by using
> manitest.
>
> So far we've had good progress but right now we're stumped.
> We have a set of manifest/template combinations where the
> manifest code uses the hos
Hello List,
I have a Problem with classes wich uses augeas. if augeas is not installed,
The complete catalog will not compile. So I can not install augeas with a
different class. I have to switch off all classes wich uses augeas, until
augeas is installed. I solved this Problem by introducing t
Thank you. It real help for me/
now I use
user { $username:
ensure => present,
home=> "$home/$username",
shell => "/bin/bash",
gid => $username,
groups => ['wheel','users'],
comment => "$uname",
password => "$hash";
}
Sorry fo
Thank you! Thank you! I did not knew what is important.
On Nov 19, 9:28 pm, Felix Frank
wrote:
> On 11/17/2010 07:01 PM, Nan Liu wrote:
>
> > On Wed, Nov 17, 2010 at 4:00 AM, Leonko wrote:
> >> Hello, I have problem with creating user under centos:
>
> >> part of my class:
>
> >> user {jboss:
On Dec 8, 2010, at 1:22 AM, Hubert Krause wrote:
> Hello List,
>
> I have a Problem with classes wich uses augeas. if augeas is not installed,
> The complete catalog will not compile. So I can not install augeas with a
> different class. I have to switch off all classes wich uses augeas, until
Hello,
Anybody know how I can make checking file for verify for size/md5sum
and if it not equal my value rewrite it from server.
There may vriant than simple: file { /my/file: ensure => present,
checksum => true,source => "puppet:///files/file"}
?
Thanks
--
You received this message because yo
Hello,
Am Wednesday 08 December 2010 11:00:11 schrieb Patrick:
> The best answer is usually, "install Augeas when you install Puppet". If
> that's not possible, I know of two options: 1) Custom fact wrapper
> 2) Use a bootstrap enviroment and don't have your client leave it without
> Augeas.
Do
On 08-12-10 11:19, Leonko wrote:
> Hello,
> Anybody know how I can make checking file for verify for size/md5sum
> and if it not equal my value rewrite it from server.
> There may vriant than simple: file { /my/file: ensure => present,
> checksum => true,source => "puppet:///files/file"}
> ?
Isn
On 12/03/2010 09:48 PM, Don Jackson wrote:
>
> So here is a scenario:
>
> I have a directory:
>
> ./foo
> ./foo/file1
> ./foo/file2
> ./foo/file3
> …
> ./foo/fileN
>
> I populate this directory on a configured machine via a recursive file
> resource.
>
> Wh
On 12/05/2010 07:23 PM, cyrus wrote:
> I have the following setup
>
> http://pastebin.com/bWANRpsP
>
> And was wondering if anyone could comment on whether my philosophy is
> correct. The issue I am having is this. 99% of my systems need to be
> configured identically. However every now and then
On 12/06/2010 01:12 AM, Chris C wrote:
> Hi folks,
> Is anyone noticing an issue with the length of a class name? If I call
> the class syslogng the class fails. If I call the class slng the class
> works. Strangely a class named all_hosts works.
I remember a weird occurence when a class was ou
Hi,
We have several situations where it is desireable to do catalog runs on
demand. We have 'puppetrun' for that, but it can -and does- happen, that a
catalog run is already in progress when we trigger a run by hand. In that
case, the triggered run is skipped.
I would like to have the possibility
On 12/06/2010 09:13 PM, Kikanny wrote:
> Whenever I try to connect to the master from the client, I get the
> following error:
>
> Could not retrieve catalog from remote server: SSL_connect returned=1
> errno=0 state=SSLv3 read server certificate B: certificate verify
> failed
>
> I tried google
So there is something wrong with the date of the certificate. When I
do "openssl x509 -text -in -noout /etc/puppet/ssl/certs/client.pem |
grep -A2 Validity", I get:
Validity
Not Before: Dec 7 14:08:10 2010 GMT
Not After : Dec 6 14:08:10 2015 GMT
However, the current date of the client is Dec 8 wh
On Wed, Dec 8, 2010 at 3:10 PM, Martijn Grendelman wrote:
> Hi,
>
> We have several situations where it is desireable to do catalog runs on
> demand. We have 'puppetrun' for that, but it can -and does- happen, that a
> catalog run is already in progress when we trigger a run by hand. In that
> cas
Hello,
sorry it took me so long to reply.
Thank you for the answer. That has helped me a lot and I think I'm on
the correct path now. It is just a lot more verbose than I had hoped
:)
> A custom function that expands the array would be a bit more
> universal, but you can still do this with puppe
On Wed, Dec 8, 2010 at 6:20 AM, Kikanny wrote:
> So there is something wrong with the date of the certificate. When I
> do "openssl x509 -text -in -noout /etc/puppet/ssl/certs/client.pem |
> grep -A2 Validity", I get:
>
> Validity
> Not Before: Dec 7 14:08:10 2010 GMT
> Not After : Dec 6 14:08:10
Was this resolved? I'm using 2.6.4 and still can't declare packages
with the same package name:
package { legacy_chunk:
name => 'facter',
provider => 'rpm',
ensure => absent,
}
package { gem_chunk:
name => 'facter',
provider => 'gem',
ensure => latest
}
Thank you.
--
You received this me
Hi Nan
Thanks for your response. I tried that. But it says that everything is
okay. I get "verify return 1" instead of saying why there is a
verification error
On Dec 8, 10:54 am, Nan Liu wrote:
> On Wed, Dec 8, 2010 at 6:20 AM, Kikanny wrote:
> > So there is something wrong with the date o
I am currently looking into rebuilding my puppet server and possibly
switching to new hardware. I am looking for any input that users may
have with this process.
1. ) Any one done this before?
2. ) Any gotcha's I need to be aware of?
3. ) Any advice in general ;)
--
You received this message bec
Morning chaps,
>From my understanding the puppet master must have a hostname of
"puppet". Is this correct? I'd like to be able to call this box
whatever I like. I think that I can do that within
/etc/puppet/puppet.conf.
--
John Maclean
MSc (DIC)
Enterprise Linux Systems Engineer
--
You rece
I think it is a call from the facter API that let's you define the
code to use to get the value for that certain fact you are defining.
>From what I know, it let's you use just ruby code. But from that you
can call bash code too.
For example, you would like a new fact that gives you back your
curr
Hi!
I'm trying to make puppet execute classes in a certain order for a
particular node.
So this is my test config:
class one {
exec { "echoone":
command => "/bin/echo $var1",
}
}
class two {
exec { "echotwo":
command => "/bin/echo $var2",
}
}
class three {
e
Hello everybody,
Is there a way when installing a package like this :
package { "rubygems":
ensure => installed,
}
to pass -t parameter to apt-get in order to use a specific apt
source ? EG : apt-get install -t lenny-backports rubygems
Ideally I would not use exec ...
I am
You can name it whatever you like. 'puppet' is the default. In your client's
puppet.conf files, add the line:
server = puppetmaster_hostname
under the [agent] section if running version 2.6 and [main] section if running
version 0.25. It also doesn't hurt to add this line to your puppetmaster
On 12/08, Martijn Grendelman wrote:
> I would like to have the possibility to tell Puppet to queue the trigger,
> and when the currently running catalog run is finished, process it and do
> another run.
>
> Does this sound like a good idea?
I thought so, and proposed a similar feature a while bac
Puppet will, by design, apply classes in a random order. To specify the order,
you want to use the "require" parameter.
exec { "echoone":
command => "/bin/echo $var1",
}
exec { "echotwo":
command => "/bin/echo $var2",
require => Exec['echoone'],
}
exec { "e
On Dec 8, 2010, at 2:32 AM, Hubert Krause wrote:
> Hello,
>
> Am Wednesday 08 December 2010 11:00:11 schrieb Patrick:
>> The best answer is usually, "install Augeas when you install Puppet". If
>> that's not possible, I know of two options: 1) Custom fact wrapper
>> 2) Use a bootstrap enviromen
(Patrick's Homebrew provider lit a fire under me to finish this.)
I've written a provider for Python's pip package management frontend.
It's (theoretically) the standard for the future, being more capable
and less shit than easy_install.
https://github.com/rcrowley/puppet-pip
As noted in the REA
Sadly, no. I very much missed the feature. We ended up using the apt
preferences file to implement that behaviour
If I was doing it over I would use a define that added the package resource
and also used concat to automatically build up the preferences entry.
Regards, Daniel.
On 09/12/2010 6:03 A
On Dec 8, 2010, at 6:38 PM, Daniel Pittman wrote:
> Sadly, no. I very much missed the feature. We ended up using the apt
> preferences file to implement that behaviour
>
> If I was doing it over I would use a define that added the package resource
> and also used concat to automatically build
On 12/09/2010 05:13 AM, Patrick wrote:
>
> On Dec 8, 2010, at 6:38 PM, Daniel Pittman wrote:
>
>> Sadly, no. I very much missed the feature. We ended up using the apt
>> preferences file to implement that behaviour
>>
>> If I was doing it over I would use a define that added the package
>> resour
34 matches
Mail list logo
