Puppet Developers Google Group

Re: Announce: Puppet 3.2.1 Available

2013-05-23T10:32:12Z

I like the new features in 3.2.1 very much.

My suggestion for the lambda syntax is:

*# Alternative 1: Parameters are inside the lambda block. [1,2,3].each {

Then it's more like Ruby.

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-23T18:08:29Z

Thanks for tracking it down to that. Charlie and I traced it a bit further
and found that inside webrick it loads webrick/config.rb which sets up a
hash that contains the servername that is determined by calling
WEBrick::Util.getservername which does these reverse lookups. That explains
the mystery of simply loading some code causing a DNS lookup to occur.

Re: Announce: Puppet 3.2.1 Available

2013-05-23T00:08:42Z

I neglected to mention in the announcement email, to support the
"Future" parser, we have added dependencies on ruby-rgen to our puppet
packages that support dependency resolution (gem, deb, rpm). It is
available as a gem
on rubygems.org and packaged as a library in our apt and yum
dependencies repos.

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-22T23:56:56Z

On Wed, May 22, 2013 at 10:10 AM, Charlie Sharpsteen

Regardless of which state /etc/hosts is in, it always returns the
short name: "coolair".

Wil

Re: [Puppet Users] Re: Announce: Puppet 3.2.1 Available

2013-05-22T23:30:48Z

Matt,
What platform are you on? Are you using a cache of some sort in front
of apt? We haven't been able to reproduce this problem.

--
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
[link]
Register now and take advantage of the Early Bird discount - save 25%!

Announce: PuppetDB 1.3.1 Available

2013-05-22T23:23:54Z

PuppetDB 1.3.1 is now available for download! This is a bug-fix release
for the 1.3 series of PuppetDB.

=============
=============

Available in native package format at:
[link] and [link]

Puppet module:
[link]

Announce: Puppet 3.2.1 Available

2013-05-22T19:54:00Z

Puppet 3.2.1 is a bugfix release for the 3.x series of Puppet.

This release addresses two major issues that were uncovered in 3.2.0
and caused us to pull that release (#20726 and #20742). It also
includes a fix for Solaris support (#19760).

Downloads are available at:
* Source [link]

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-22T17:10:44Z

Thanks a bunch for the info Wil! One additional question: What is the
hostname that Ruby is using to perform the lookup? I.E., what is the return
value of:
ruby -rsocket -e 'puts Socket.gethostname'
-Charlie

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-22T16:53:49Z

I agree this should be restricted to code paths that actually use webrick

In the case of the windows-specific monkey patches for openssl, there is no
difference putting them in lib/puppet/util/monkey_patches .rb or
lib/puppet/util/windows.rb, as both are always loaded via require 'puppet'.

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-22T13:28:29Z

[snip]

Yes, I concur that it's a bad thing to load webrick on a command-line
puppet (or even the agent if it doesn't listen). Those monkey patches
should be splitted depending on the puppet use case.

I suggest you file a redmine ticket about this issue (and I'm sure
you'll certainly won't be the first to be hit by this dns resolution

Re: [Puppet-dev] Is Puppet::Provider::Package#query required?

2013-05-22T00:49:26Z

Ah! Thanks. I'd missed that query call. (After a fair amount of looking,
too! But, for that file, only with eyeballs, not grep. Ah well.)

-Fritz

Re: [Puppet-dev] Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-21T22:03:28Z

On Tue, May 21, 2013 at 9:53 AM, Charlie Sharpsteen

Sure; in my /etc/hosts I had the following for my host-only vbox net:

192.168.56.1 coolair.local coolair

With that in place:

$ time ruby -rsocket -e "Socket.gethostbyname(Socket.g ethostname)"
real 0m10.013s

And when I change it to:

Re: [Puppet-dev] Is Puppet::Provider::Package#query required?

2013-05-21T17:38:41Z

It looks like PackageProvider#query is being called in the #properties
method at (
[link]).
I deleted that method and ran the specs to see what blows up:

1) Package provider gem should be able to get a list of existing packages

Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-21T16:53:46Z

Hi Wil,
Could you provide a bit more information on what the entry in your
/etc/hosts file looked like? It would be interesting to reproduce this
behavior and see if everything is functioning as intended.
Thanks!
-Charlie

Re: Performance regression between 3.2.1-rc1 and 3.1.1?

2013-05-21T06:21:48Z

After realizing that even 'puppet --version' took ~10s, I ran the ruby
profiler, noticed there were differences in the number of calls, extracted
& diff'd those, noticed the addition of Socket#gethostbyname and
Socket#gethostname. Eventually I noticed that my /etc/hosts had
myhostname.local instead of just myhostname which (I presume) was causing a