Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-15 Thread David Schmitt
On 14.11.2012 22:37, Luke Kanies wrote: On Nov 14, 2012, at 10:20 AM, Patrick Carlisle mailto:patr...@puppetlabs.com>> wrote: On Wed, Nov 14, 2012 at 9:24 AM, Luke Kanies mailto:l...@puppetlabs.com>> wrote: If you're using JSON instead of YAML, then you shouldn't see a lot of time

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-14 Thread Luke Kanies
On Nov 14, 2012, at 10:20 AM, Patrick Carlisle wrote: > > > On Wed, Nov 14, 2012 at 9:24 AM, Luke Kanies wrote: > > > If you're using JSON instead of YAML, then you shouldn't see a lot of time in > the converting to and from. I can't remember if this is a configurable > option in 3.0, or

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-14 Thread Patrick Carlisle
On Wed, Nov 14, 2012 at 9:24 AM, Luke Kanies wrote: > > > If you're using JSON instead of YAML, then you shouldn't see a lot of time > in the converting to and from. I can't remember if this is a configurable > option in 3.0, or if it defaults to JSON, but if it still defaults to YAML, > that co

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-14 Thread Luke Kanies
On Nov 14, 2012, at 8:53 AM, Brice Figureau wrote: > Hi, > > On Wed, 2012-11-14 at 13:43 +0100, David Schmitt wrote: >> On Tue, 13 Nov 2012 11:08:57 -0800, Luke Kanies >> wrote: The run with 2.7.19 takes around ten minutes wallclock time. 3.0.1 >> takes around nine minutes wallclock

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-14 Thread Brice Figureau
Hi, On Wed, 2012-11-14 at 13:43 +0100, David Schmitt wrote: > On Tue, 13 Nov 2012 11:08:57 -0800, Luke Kanies > wrote: > >> The run with 2.7.19 takes around ten minutes wallclock time. 3.0.1 > takes > >> around nine minutes wallclock for a complete "puppet agent --test". > The > >> difference is

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-14 Thread David Schmitt
On Tue, 13 Nov 2012 11:08:57 -0800, Luke Kanies wrote: >> The run with 2.7.19 takes around ten minutes wallclock time. 3.0.1 takes >> around nine minutes wallclock for a complete "puppet agent --test". The >> difference is approximately the time saved on master compiling the >> catalog. I'm not co

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-13 Thread Luke Kanies
On Nov 13, 2012, at 7:35 AM, David Schmitt wrote: > On 12.11.2012 14:34, Brice Figureau wrote: >> On Mon, 2012-11-12 at 13:06 +0100, David Schmitt wrote: >>> Hi, >>> >>> I've just upgraded my local test master to 3.0 and wanted to share the ups >>> and downs. >>> >>> * The upgrade went as smo

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-13 Thread David Schmitt
On 12.11.2012 14:34, Brice Figureau wrote: On Mon, 2012-11-12 at 13:06 +0100, David Schmitt wrote: Hi, I've just upgraded my local test master to 3.0 and wanted to share the ups and downs. * The upgrade went as smooth as could be expected: config.ru migration tripped me up, but was document

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-12 Thread Brice Figureau
On Mon, 2012-11-12 at 13:06 +0100, David Schmitt wrote: > Hi, > > I've just upgraded my local test master to 3.0 and wanted to share the ups > and downs. > > * The upgrade went as smooth as could be expected: config.ru migration > tripped me up, but was documented. > * There were still unexpe

Re: [Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-12 Thread R.I.Pienaar
- Original Message - > From: "David Schmitt" > To: "Puppet dev" > Sent: Monday, November 12, 2012 12:06:17 PM > Subject: [Puppet-dev] Reports from the puppet 3.0 migration front > > Hi, > > I've just upgraded my local test master

[Puppet-dev] Reports from the puppet 3.0 migration front

2012-11-12 Thread David Schmitt
Hi, I've just upgraded my local test master to 3.0 and wanted to share the ups and downs. * The upgrade went as smooth as could be expected: config.ru migration tripped me up, but was documented. * There were still unexpected differences in behaviour which were not warned by 2.7. In my case I