Personally I kinda hope that Puppet can change the versioning system. So
that it is easier to know which version is major and which minor.
As far as how far back support should go, I would say that client/server
should be at least 1 major version behind.
---
On Nov 25, 11:14 am, Terry wrote:
> Hi,,,
>
> I have a strange problem when installing puppet client 2.6.3 on a
> node.
> I have installed facter-1.3.8-4 and ruby-1.8.6-8.
>
> When I start puppetd as a normal user everything behaves normally.
> A .puppet directory is installed under $HOME and s
On Nov 24, 3:50 pm, Nigel Kersten wrote:
> I mentioned this in an earlier thread, but here's a dedicated one.
>
> We made a big change between 0.24.x and 0.25.x where we moved from
> XMLRPC to REST.
>
> How do people feel about us dropping all XMLRPC support from 2.7.x,
> such that it only support
Lars Francke wrote:
> Awesome! I didn't even know there was an official syntax file. I've
> been using the one from vim.org from 2007(?). Thanks for maintaining
> this.
>
>> https://github.com/puppetlabs/puppet/tree/master/ext/vim/
>>
>> We should remove the one on puppetlabs.com.
>
> It would be
Awesome! I didn't even know there was an official syntax file. I've
been using the one from vim.org from 2007(?). Thanks for maintaining
this.
> https://github.com/puppetlabs/puppet/tree/master/ext/vim/
>
> We should remove the one on puppetlabs.com.
It would be really great if you could either a
I don't understand how I'd convert the definitions from my original
mail into virtual resources.
Simplified:
$disks = ['/a', '/b']
define foo() {
file { "${name}/foo": }
}
foo { $disks: }
define bar($path) {
file { "${name}/foo/${path}":
require => Foo[$name],
}
}
bar { $disks:
path
Douglas Garstang wrote:
> I don't know if this is a known, documented bug, but in v2.6.1, the
> puppetd daemon will just completely shut down if it isn't able to
> connect to the puppetmaster. Rather annoying. Is this fixed in a newer
> release? If not, I'll have to write a wrapper script, or put i
I don't know if this is a known, documented bug, but in v2.6.1, the puppetd
daemon will just completely shut down if it isn't able to connect to the
puppetmaster. Rather annoying. Is this fixed in a newer release? If not,
I'll have to write a wrapper script, or put it into cron.
Doug.
--
You rec
On Thu, Nov 25, 2010 at 5:48 AM, thbe wrote:
> On 28 Okt., 15:09, Kikanny wrote:
>> Hmmm...I've made some progress. There seemed to be some problems with
>> Ruby 1.9.1. So I reverted back to Ruby 1.8.7 and followed the steps
>> again as outlined
>> inhttp://projects.puppetlabs.com/projects/1/wik
On Thu, Nov 25, 2010 at 7:34 AM, Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
>
> Am Do den 25. Nov 2010 um 15:04 schrieb Thomas Bendler:
>> 2010/11/25 Klaus Ethgen >
>>
>> > [...]
>> > There are many distributions out there providing 0.24 version only. And
>> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Do den 25. Nov 2010 um 15:04 schrieb Thomas Bendler:
> 2010/11/25 Klaus Ethgen >
>
> > [...]
> > There are many distributions out there providing 0.24 version only. And
> > as the use of puppet is to manage many distributions, even the
> > a
On Wed, Nov 24, 2010 at 10:15 PM, Paul Nasrat wrote:
> On 20 November 2010 16:42, Nigel Kersten wrote:
>> On Fri, Nov 19, 2010 at 12:56 PM, Steve Atwell wrote:
>>> I need to write a custom fact that depends on the value of another
>>> custom fact in a different file. For example:
>>>
>>> # foo.
2010/11/25 Klaus Ethgen >
> [...]
> There are many distributions out there providing 0.24 version only. And
> as the use of puppet is to manage many distributions, even the
> antiquated »enterprise« distributions, I think that dropping support for
> version lower than 0.25 is not that good idea.
>
On 28 Okt., 15:09, Kikanny wrote:
> Hmmm...I've made some progress. There seemed to be some problems with
> Ruby 1.9.1. So I reverted back to Ruby 1.8.7 and followed the steps
> again as outlined
> inhttp://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows.
> Installed an additional gem call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
Am Do den 25. Nov 2010 um 0:50 schrieb Nigel Kersten:
> We made a big change between 0.24.x and 0.25.x where we moved from
> XMLRPC to REST.
>
> How do people feel about us dropping all XMLRPC support from 2.7.x,
> such that it only support
Hi,,,
I have a strange problem when installing puppet client 2.6.3 on a
node.
I have installed facter-1.3.8-4 and ruby-1.8.6-8.
When I start puppetd as a normal user everything behaves normally.
A .puppet directory is installed under $HOME and ssl key is installed
under $HOME/.puppet/ssl.. I si
Hi people.
After some reading, I think I have some sort of coherent thought about how to
handle users and groups, being a first time Puppet user though I figured I'd
ask for some criticism before I go ahead.
I'll use the /modules/user module as per the BP-doc, and store all the users
and groups
On Wed, Nov 24, 2010 at 7:35 PM, Daniel Pittman wrote:
>> One of the bits of feedback I have had from various folks out in the wider
> world is that (right or wrong) they already feel that Puppet has a pretty fast
> upgrade cycle and a very poor backward compatibility story.
>
>> My firm would be
Thank you Paul, and thank you everyone else for your replies.
Presumably fact values can be broken down into two categories:
a) those values which exist in Factor's code base somewhere
b) those values which are obtained from elsewhere
Those in a) can be deduced just by looking at the Factor co
On Thu, 25 Nov 2010 00:50:30 +0100, Nigel Kersten
wrote:
I mentioned this in an earlier thread, but here's a dedicated one.
We made a big change between 0.24.x and 0.25.x where we moved from
XMLRPC to REST.
How do people feel about us dropping all XMLRPC support from 2.7.x,
such that it onl
On Wed, 24 Nov 2010 21:13:37 +0100
Stefan Schulte wrote:
Hi all,
I think I get it...
class File default was:
File {
ensure => prsent,
mode=> 644,
owner => root,
group => root,
}
notice prsent... and not present.
^
> I dont think its working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> [...]
>> How do people feel about us dropping all XMLRPC support from 2.7.x,
>> such that it only supported Puppet clients 0.25.x and higher?
>> [...]
>>
>
> Will it be possible to run two puppet server instances (2.6.x and 2.7.x) on
> the same hos
2010/11/25 Nigel Kersten
> [...]
> How do people feel about us dropping all XMLRPC support from 2.7.x,
> such that it only supported Puppet clients 0.25.x and higher?
> [...]
>
Will it be possible to run two puppet server instances (2.6.x and 2.7.x) on
the same host on different ports? If yes, g
23 matches
Mail list logo
