On Thu, Oct 28, 2010 at 3:15 PM, Forrie wrote:
> Thanks for posting the code snippet.
>
> We haven't been building RPMs for internal use; so, I certainly could
> work on that. I think we might be able to do a filesystem tree copy
> -- for example, track the files that get installed on the maste
Thanks for posting the code snippet.
We haven't been building RPMs for internal use; so, I certainly could
work on that. I think we might be able to do a filesystem tree copy
-- for example, track the files that get installed on the master
server, then copy those to the files repository under pu
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!
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
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 upgrades work. We've gone through up, and down, grades
>
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 upgrades work. We've gone through up, and down, grades
of multiple versions of .24, .25, and 2.6. In every case t
On Fri, Oct 8, 2010 at 4:56 PM, Forrie wrote:
> That's more of what we're looking to do. I think it would be a bad
> idea to have puppet automatically updating clients. This would need
> to be a one-off, scheduled item you would trigger from the puppet
> master server, under the default {} node,
That's more of what we're looking to do. I think it would be a bad
idea to have puppet automatically updating clients. This would need
to be a one-off, scheduled item you would trigger from the puppet
master server, under the default {} node, I would presume;
Perhaps having the puppet (and facte
