On 11 November 2010 19:06, James Turnbull wrote:
> donavan wrote:
>> Pieter, It's not a solution today but it sounds like you're looking
>> for the Inventory Service[1]. The basic idea is to collect, and
>> export, the client facts using a REST interface from a central
>> service. There's a push t
On Sat, Nov 13, 2010 at 4:39 AM, Paul Nasrat wrote:
> On 11 November 2010 19:06, James Turnbull wrote:
>> donavan wrote:
>>> Pieter, It's not a solution today but it sounds like you're looking
>>> for the Inventory Service[1]. The basic idea is to collect, and
>>> export, the client facts using a
On Fri, Nov 12, 2010 at 7:54 AM, Peter Bonivart wrote:
> On Nov 3, 4:39 pm, Nigel Kersten wrote:
>> We really need community testing with this provider. There are some
>> questions Rudy has in the ticket log that we need to get answered.
>>
>> http://projects.puppetlabs.com/issues/4258
>
> Hi, I'
- "Nigel Kersten" wrote:
> We're working out a way to do decent screencasts of new and existing
> features.
>
> Would people be interested in tuning into such demos live? I
> understand we have a rather wide spread of timezones here, but it
> would be kind of cool if we could do live demos
On Thu, Nov 11, 2010 at 6:43 PM, donavan wrote:
> On Nov 11, 2:15 am, Daniel Pittman wrote:
>> Leonko writes:
>>
>> I think it is mentioned obliquely a few times, but there certainly isn't
>> anywhere super-obvious that explains this feature of manifest auto-loading.
>
> Yes, +1 to an issue for
On Fri, Nov 12, 2010 at 10:28 AM, Roberto Bouza wrote:
> Hello,
>
> Up to right now everything is working great with puppet. I just have
> one questions.
>
> Is there a way to tell a type (like file) not to fail if something
> specific happens.
>
> Let's say I have a directory which it needs to be
Hi all,
I'm a Puppet newbie and am struggling to get myself up and running on my
first Puppet install and am looking for some assistance.
To explain where I'm at I have done the following (all based on the Puppet
getting started guide):
1: sudo apt-get install puppet, installation completed but
On Fri, Nov 12, 2010 at 3:36 AM, tecneeq wrote:
> On 12 Nov., 02:42, Joel Merrick wrote:
>
>> > However, what if the selection of packages changes? Is there a more
>> > clever way to install tasks with tasksel, without listing each and
>> > every package the tasksel task is made of?
>
>> Have you
Hi all
As the last step in our GitHub migration the reductivelabs account has
been deleted.
Please now use the Puppet Labs account:
https://github.com/puppetlabs
Regards
James Turnbull
--
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571
--
You received this message because you are s
Paul Nasrat wrote:
> On 11 November 2010 19:06, James Turnbull wrote:
>> donavan wrote:
>>> Pieter, It's not a solution today but it sounds like you're looking
>>> for the Inventory Service[1]. The basic idea is to collect, and
>>> export, the client facts using a REST interface from a central
>>>
On Nov 13, 2010, at 4:53 AM, Edd Grant wrote:
> 2: Created /etc/puppet/manifests/site.pp which contains the following (taken
> from the Puppet getting started guide):
> # site.pp
> #Configure permissions on the sudoers file
> file { "/etc/sudoers":
> ownner => root, group => root, mode => 440
On 13 November 2010 16:35, R.I.Pienaar wrote:
>
> - "Nigel Kersten" wrote:
>
>> We're working out a way to do decent screencasts of new and existing
>> features.
>>
>> Would people be interested in tuning into such demos live? I
>> understand we have a rather wide spread of timezones here, bu
I am banging my head against the wall for recently built hosts that
are unable to verify the server's certs. The usual is not working.
on the puppet agent machine:
find /var/lib/puppet/ssl -type f -delete
on puppet master:
puppetca --clean
on agent:
puppetd --server puppet --waitforcert 2 -
First thing I would check is time, to make sure that your manager and host
are synched.
--
From: "David Birdsong"
Sent: Saturday, November 13, 2010 2:49 PM
To:
Subject: [Puppet Users] certificate verify failed
I am banging my head against the
further research on this:
I think the issue is with the certificates. Although I have no idea what.
I removed /var/lib/puppet/ssl directory and recreated it. When a client
tries to get catalog I get the following error:
[2010-11-13 19:31:22] ERROR OpenSSL::SSL::SSLError: tlsv1 alert unknown ca
On Nov 13, 2010, at 4:48 PM, Marek Dohojda wrote:
> further research on this:
> I think the issue is with the certificates. Although I have no idea what. I
> removed /var/lib/puppet/ssl directory and recreated it. When a client tries
> to get catalog I get the following error:
> [2010-11-13
Drat! you are right of course, I did remove the ssl from the client I am
testing but I forgot about all the other hosts which of course can't verify the
certificate. D'OH I been working on this far too long. Ok so this takes care
of this issue, I am back to the:
"Could not intern from pson: s
OK I figured this out. The issue appeared to be with one of the classes.
Somehow there was a bad character. What is amazing is that all I did is open
it and close it, so ahm yeah no clue how that fixed things, but it did.
From: Patrick
Sent: Saturday, November 13, 2010 6:31 PM
To: puppe
On Sat, Nov 13, 2010 at 3:19 PM, Marek Dohojda wrote:
> First thing I would check is time, to make sure that your manager and host
> are synched.
>
makes sense, i didn't think of this earlier, but alas i've synced them
(they were off by ~18 seconds) and still getting the exact same error.
err: Co
On Sat, Nov 13, 2010 at 7:56 PM, David Birdsong
wrote:
> On Sat, Nov 13, 2010 at 3:19 PM, Marek Dohojda wrote:
>> First thing I would check is time, to make sure that your manager and host
>> are synched.
>>
> makes sense, i didn't think of this earlier, but alas i've synced them
> (they were off
20 matches
Mail list logo
