On Mon, Sep 22, 2014 at 10:07 AM, Britt Gresham
wrote:
> Hello,
>
> We are interested in collecting puppet profile data from the puppet master
> in the real world. This data will be used to help us find a direction to go
> to increase the throughput of the puppet master master.
>
>
I would be inc
On Fri, Sep 26, 2014 at 1:30 PM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 09/26/2014 09:45 PM, Rob Reynolds wrote:
> >
> > Java just on server side. Native is moving towards C++.
>
> No wait, what, really?
>
>
Felix, if your "what?" is about Java (the language), that was a mistak
On Tue, Sep 23, 2014 at 1:30 PM, Matt Zagrabelny wrote:
> On Tue, Sep 23, 2014 at 2:03 PM, Gabriel Filion
> wrote:
> > On 23/09/14 12:11 PM, Nate Wolfe wrote:
> >> We are thrilled to announce the preview release of Puppet Server, our
> >> newest open source project.
> >> Puppet Server is a next-
On Mon, Sep 22, 2014 at 12:10 PM, Tristan Smith
wrote:
> One more, mostly just a 'wouldn't it be nice if this were clearly
> handled?' Having a comma at the end of an assignment like the below appears
> to cause confusion; mostly at this point my gripe is that the error line is
> reported as the
Puppet 3.7.1 is a backward-compatible bugfix release in the Puppet 3
series. This release fixes several regressions and other issues.
* PUP-3222: Windows service provider references a non-existent
class
* PUP-3190: "each" no longer supported in Puppet 3.7.0
* PUP-3191: Syml
On Wed, Sep 10, 2014 at 12:55 PM, Juan Andres Ramirez wrote:
> Hello,
>I have data in machine.yaml :
>
> sitedefinition:
> - website: "site.one.com"
> ipadress: "192.168.0.2"
> protocol: "http"
> port: "80"
> - website : "site.two.com"
> ipadress : "192
On Wed, Jul 23, 2014 at 11:40 AM, Danny Roberts <
dannyroberts.perso...@googlemail.com> wrote:
> Thanks that certainly sorts out the authentication problem.
>
> Turns out I'm using the wrong API call for what I require though. I'm
> after the equivalent of running "puppet cert list" and not "puppe
On Wed, Jul 23, 2014 at 7:02 AM, Cristian Falcas
wrote:
> Hello,
>
> When are the exported resources exported and by whom? Are they send by the
> agent at the end of the run or are written by the server after catalog
> compilation?
>
>
The exported resources are created as part of the catalog com
On Thu, May 29, 2014 at 8:30 AM, Kylo Ginsberg wrote:
> On Wed, May 28, 2014 at 1:53 PM, Andy Parker wrote:
>
>> On Tue, May 27, 2014 at 11:33 AM, Kylo Ginsberg
>> wrote:
>>
>>> On Tue, May 27, 2014 at 7:16 AM, Chuck wrote:
>>>
>>>> The
On Tue, May 27, 2014 at 11:33 AM, Kylo Ginsberg wrote:
> On Tue, May 27, 2014 at 7:16 AM, Chuck wrote:
>
>> The ability to turn off the deprecation messages would be great. The
>> only things these messages provide are a drain on logging resources, noise
>> in the logs, and confusion from end u
On Tuesday, May 27, 2014 5:53:29 AM UTC-7, Konrad Scherer wrote:
>
> On 14-05-22 03:21 PM, Daniele Sluijters wrote:
> > The environment caching is already there, use the environment_timeout
> > setting. Mine is set to unlimited and I reload at deploy time by
> > touching tmp/restart.txt. This so
On Friday, April 18, 2014 8:42:28 AM UTC-7, Atom Powers wrote:
>
> Since updating to 3.5.1 resource defaults don't seem to work any more. I
> didn't see anything in the release notes that look
> relevant.
>
>
It looks like it is a bug in the new evaluator that is part of the
experimental future
On Tue, Mar 25, 2014 at 3:57 PM, David Mesler wrote:
> Currently I use the common import "nodes/*" method. With that I've always
> had to restart the puppet master processes in order to process new node
> files. Will that still be necessary with the new manifest directory
> behavior?
>
> Hi David,
On Thu, Mar 21, 2013 at 5:46 AM, llowder wrote:
>
>
> On Wednesday, March 20, 2013 5:37:14 PM UTC-5, Andy Parker wrote:
>
>> On Tue, Mar 19, 2013 at 2:30 PM, Larry Fast wrote:
>>
>>> My Hiera tree is turning into a chaotic mess. I'm guessing that my tree
&
On Tue, Mar 19, 2013 at 2:30 PM, Larry Fast wrote:
> My Hiera tree is turning into a chaotic mess. I'm guessing that my tree
> structure is one problem source. So I'm wondering how other real users have
> setup hiera. Here are the core problems that are giving me headaches.
I'd be interested i
On Wed, Jan 2, 2013 at 8:26 AM, jcbollinger wrote:
>
>
> On Friday, December 28, 2012 9:46:01 AM UTC-6, Ygor wrote:
>>
>> Puppet 3.0.2
>>
>> I define a virtual user resource (@users::useraccount) with tags and then
>> try to realize them with a resource collector (spaceship operator)
>>
>> Here's
On Tue, Nov 20, 2012 at 8:13 AM, Mohit Chawla wrote:
> Hello Jeff,
>
> Thanks for the reply.
>
> > A new ticket to collect this information is the best tool we have at
> > this time.
>
> This is on 2.7.19. Added ticket
> http://projects.puppetlabs.com/issues/17747.
>
>
I believe this is related t
On Thu, Oct 4, 2012 at 7:24 AM, jcbollinger wrote:
>
>
> Puppet's guts have code for setting a custom environment for commands, but
> the 'command' and 'commands' functions don't provide an interface to it.
> I'm working from the code here, not actual experience, but it looks like you
> can use th
I encountered this issue yesterday when trying to reproduce another
issue. I discovered that you need to be using activerecord 3.0.11.
Later versions don't seem to work (error with a "stack too deep") and
earlier versions don't seem to work (error with "uninitialized
constant ActiveRecord").
On Th
On Tue, Oct 2, 2012 at 11:06 AM, Corby Wilson wrote:
> I use the command "puppet kick" to do remote triggers of a 60 node cluster.
> In the new release (3.0) it deprecated the command and the command fails
> with:
> Error: Host lcms-dn1.aws.tie.noklab.net failed: Error 400 on SERVER: Could
> not f
This is a heads up to anyone who has written code that calls custom
functions. We are making a change in Puppet 3.0 that will make the
calls reject incorrect calls (see bug #15756). Calling functions from
ruby code (either other functions or erb templates) was always
supposed to be done by placing
In an effort to streamline and consolidate how code gets submitted to
puppet, we've updated the contributing guidelines. The changes were
along three fronts:
1. Clarify what to target when submitting patches.
2. Reflect the reality that we take code submissions as github pull requests.
3. Simplify
22 matches
Mail list logo
