Hi Eric,
On 06 Mar 2015, at 05:30, Eric Sorenson wrote:
> […]
> Similarly, on the network stack, we want to consolidate on the
> jetty/puppet-server/jruby stack as the single way to run Puppet masters, so
> the built-in webrick support and Rack support layer will ride off into the
> sunset.
This.
On 2015-03-06 03:42, Adrien Thebo wrote:
To me, following the principle of least astonishment indicates that
caching be disabled by default; it'll work correctly for new users and
has no hidden gotchas. When people want to do performance tuning they're
probably fairly sophisticated users a
Hi all, this may seem a bit far-out since we haven't pushed Puppet 4 completely
out of the nest, but I wanted to talk about some plans for the next cycle of
breaking changes/deprecations that are headed for Puppet 5.
There are two main areas of change, both related to continuing to move
server-
+1 to this suggestion.
-Eric
--
Eric Shamow
Sent with Airmail
On March 5, 2015 at 6:42:32 PM, Adrien Thebo (adr...@puppetlabs.com) wrote:
To me, following the principle of least astonishment indicates that caching be
disabled by default; it'll work correctly for new users and has no hidden
g
To me, following the principle of least astonishment indicates that caching
be disabled by default; it'll work correctly for new users and has no
hidden gotchas. When people want to do performance tuning they're probably
fairly sophisticated users and can deal with weird cache invalidation
issues;
Oh...in that case I vote for unlimited *if and only if*, I don't have to
hack-fu my own script to clear the environment via an API call.
'puppet environment refresh' would be my recommendation.
Thanks,
Trevor
On Thu, Mar 5, 2015 at 8:19 PM, Owen Rodabaugh wrote:
> To clarify, I am asking for
To clarify, I am asking for opinions on whether the default
environment_timeout should be 0 or unlimited in future releases of puppet.
The current plan is to default to unlimited.
I'm concerned that shipping with this default assumes prior experience and
will be another hurdle to getting star
Will the Puppet 4.0 release be available through a dist-upgrade on
apt.puppetlabs.com or a through a normal upgrade?
On Fri, Feb 27, 2015, at 09:31 PM, Kylo Ginsberg wrote:
>
> Priorities
> * Puppet Agent 1.0.0
> * Puppet Server 2.0.0
> * Puppet Server 1.1.0
> * Puppet 4.0.0 / 3.8.0
Can you use inotify to invalidate the cache via the API call when selected
files in your infrastructure change?
It looks like you could do this directly from the core
https://launchpad.net/inotify-java. You'll just want to queue them up a bit
to not go crazy. 10 seconds should probably do it, but
We've been discussing what the default environment_timeout setting should
be. There is general agreement that the current 3 minutes is not great.
It's both baffling to new users and does not bring in the full performance
benefits.
Two main perspectives on this:
1. Performance should be the pri
"probably"
The code is written to standard operating system APIs, and we are very
aggressive with our compiler warnings (which helps avoid
undefined/architecture-specific behavior). I would expect it to work, but
as always with C++ sometimes things get weird.
Depending on the architecture* we wou
On Thu, Mar 5, 2015 at 1:25 PM, Roy Nielsen wrote:
> Curious - will this be able to be compiled and used on Arm or other
> architectures (cross platform compatibility)?
>
>
> I have been toying with ARM chips at home to get this working. (Not
official from Puppet Labs). Thus far I haven't got it
Curious - will this be able to be compiled and used on Arm or other
architectures (cross platform compatibility)?
Thank you,
-Roy
On Wed, Mar 4, 2015 at 4:45 PM, Kylo Ginsberg wrote:
> As some of you know, we have been working on a native reimplementation of
> facter in C++11 in the https://git
Ah! You have an invite now :).
On Wednesday, 4 March 2015 20:12:42 UTC+1, Hunter Haugen wrote:
>
> No merge access?
>
>
>
> -Hunter
>
> On Tue, Mar 3, 2015 at 9:27 AM, Daniele Sluijters > wrote:
>
>> Ahem, why u no
>> https://github.com/puppet-community/community-triage/tree/master/modules/notes
14 matches
Mail list logo
