> So to report back after running it for >2 weeks: 0 problems so far and I
> don't really feel a difference to 1.7
>
>
> Thanks for trying it out! Is there a performance difference if you
> change server's "compile-mode" option? I'm mostly curious about running
> with JIT compilation on.
On Mon, Sep 18, 2017 at 4:33 AM, Peter Meier wrote:
> On 08/31/2017 01:21 AM, Peter Meier wrote:
>
> So to report back after running it for >2 weeks: 0 problems so far and I
> don't really feel a difference to 1.7
>
Thanks for trying it out! Is there a performance difference if you change
server
On 08/31/2017 01:21 AM, Peter Meier wrote:
>> Our current
>> Ruby versions are EOL'ed, so we're moving to MRI Ruby 2.4 on the agent
>> and (opt-in) jruby9k on the server.
>
> So what's the current status on that opt-in?
>
> I'm running into a nasty bug with Jruby 1.7 [1] and while I read the
> co
> Our current
> Ruby versions are EOL'ed, so we're moving to MRI Ruby 2.4 on the agent
> and (opt-in) jruby9k on the server.
So what's the current status on that opt-in?
I'm running into a nasty bug with Jruby 1.7 [1] and while I read the
configure guide [2] I'm still a bit unsure whether I shoul
On Fri, Jun 30, 2017, at 18:01, Erik Dalén wrote:
> On Fri, 30 Jun 2017 at 07:47 R.I. Pienaar wrote:
>
> >
> > On 30 Jun 2017, at 01:22, Eric Sorenson wrote:
> >
> > On Jun 28, 2017, at 9:28 AM, R.I.Pienaar wrote:
> >
> > People upgrading should note the PuppetDB dependency is now postgres
>
On Fri, 30 Jun 2017 at 07:47 R.I. Pienaar wrote:
>
> On 30 Jun 2017, at 01:22, Eric Sorenson wrote:
>
> On Jun 28, 2017, at 9:28 AM, R.I.Pienaar wrote:
>
> People upgrading should note the PuppetDB dependency is now postgres
> postgresql96, this is not stated on the package dependency metadata
>> On 30 Jun 2017, at 01:22, Eric Sorenson wrote:
>>
>> On Jun 28, 2017, at 9:28 AM, R.I.Pienaar wrote:
>>
>> People upgrading should note the PuppetDB dependency is now postgres
>> postgresql96, this is not stated on the package dependency metadata so
>> upgrade works fine but puppetdb fails
On Jun 28, 2017, at 9:28 AM, R.I.Pienaar wrote:
> People upgrading should note the PuppetDB dependency is now postgres
> postgresql96, this is not stated on the package dependency metadata so
> upgrade works fine but puppetdb fails to start until you update
Hm, as I understand it there isn't a p
Also if you are a mcollective user it might be worth waiting a bit. Many
deprecation warnings will show on your client and server logs which are really
annoying
I made PRs to fix them so maybe next release
---
R.I.Pienaar
> On 28 Jun 2017, at 16:28, R.I.Pienaar wrote:
>
> People upgrading s
I'm seeing a lot of Warning: Defining "data_provider": "hiera" in
metadata.json is deprecated. How do we successfully support both Puppet 4.7
(LTS) and Puppet 5 (Today) without this garbage popping up at every run?
I don't want to kill any *real* deprecation warnings, just ones that
conflict betwe
People upgrading should note the PuppetDB dependency is now postgres
postgresql96, this is not stated on the package dependency metadata so
upgrade works fine but puppetdb fails to start until you update
On Wed, Jun 28, 2017, at 15:40, Trevor Vaughan wrote:
> Awesome! We'll start working on testin
Awesome! We'll start working on testing with this as soon as we can.
First issue found: When using rspec-puppet, we need to test with
'server_facts' but now can no longer set those since they are 'reserved'
but appear to be unset by default. Any idea how to get around this?
On Tue, Jun 27, 2017 a
I have run out of superlatives to try to express how excited I am for this
release: the Puppet 5 Platform is available for download now.
The primary goals of this release are to harmonize numbering across the major
components (Puppet Agent, PuppetDB, Puppet Server) to "5", as a first step
towar
13 matches
Mail list logo
