On 10/10/2010 06:28 PM, Patrick wrote:
>
> On Oct 10, 2010, at 3:29 AM, donavan wrote:
>
>> On Oct 8, 1:18 pm, Disconnect wrote:
>>> We just use packages:
>>> package { "puppet": ensure => latest }
>>
>> Seconded, mostly. We target specific versions, and test in a lab
>> first, but self upgrade
Thought I'd just post some manifest code for what people have already
described to give you some ideas.
The following is a parameterised class where you can either use the
site default, or pass in any version of Puppet you want:
class puppet($request_version = "") {
#everything needs common!
Thanks Jacob.. I'll try this out. I was also thinking about hosting
our own apt repo and then we could use "apt" instead of "dpkg"
On Oct 8, 7:26 pm, Jacob Helwig wrote:
> On Fri, 08 Oct 2010 16:20:39 -0700, Jacob Helwig wrote:
> > Date: Fri, 8 Oct 2010 16:20:39 -0700
> > From: Jacob Helwig
>
You really want to do that. It's much easier to maintain.
Here's a tutorial for a really simple repository if you want it:
http://nerdica.com/?p=43
On Oct 11, 2010, at 7:58 AM, Tim C wrote:
> Thanks Jacob.. I'll try this out. I was also thinking about hosting
> our own apt repo and then we co
Chuck a écrit :
I have migrated my EL5 servers from 0.25.5 to 2.6.2 and have no issues
now. I did have some issues with 2.6.1 which are now fixed. I would
like to see 2.6.2 in the official EPEL repository.
I'd like to now if you are using some 'Exec' ?
And if yes, do you explictly set the 'pat
I've been poking around the web docs, and dont see an answer to this
yet:
Is there any pre-existing functionality in puppet, to allow limiting
parallelism?
Example:
Lets say that I want all machines to run some sort of job, that
updates a central database with information about the state of each
On Mon, Oct 11, 2010 at 02:09:54PM -0700, Philip Brown wrote:
>
> Example:
> Lets say that I want all machines to run some sort of job, that
> updates a central database with information about the state of each
> puppet client.
>
> Lets also say, that I have 1000 machines, so if all of them decid
yes I do use some, no I do not use the "path" option.
On Oct 11, 12:23 pm, Aurelien Degremont
wrote:
> Chuck a crit :
>
> > I have migrated my EL5 servers from 0.25.5 to 2.6.2 and have no issues
> > now. I did have some issues with 2.6.1 which are now fixed. I would
> > like to see 2.6.2 in the
Philip
There are a couple of ways:
If your clients run puppetd in daemon mode, then look in the client
configuration file at:
splay = true
splaylimit = 1800
We run our puppet clients as a wrapper from cron and make use of the
function which randomises a number based on fqdn (and other op
One word: Idempotence.
If you have to do what you are asking, ur doin' it wrong.
On Mon, Oct 11, 2010 at 2:09 PM, Philip Brown
wrote:
> I've been poking around the web docs, and dont see an answer to this
> yet:
>
> Is there any pre-existing functionality in puppet, to allow limiting
> paralleli
On Oct 11, 5:45 pm, Scott Smith wrote:
> One word: Idempotence.
>
> If you have to do what you are asking, ur doin' it wrong.
Weeel,,not neccessarily.
It can still be "Idempotent".
The 'state' we wish to maintain, can be,
"machine has a self-generated/updated entry in central database, that
is
Take a look at mcollective. You can query your facter facts on all your
systems. You can also use puppetcommanderd, an mcollective add on, that will
schedule runs of your clients matching a filter (filter on facts or classes)
spread out over a specified time period.
On Oct 11, 2010, at 8:44 P
12 matches
Mail list logo
