First, Émile, your performance plots are awesome! Thank you so much for taking
the time to put these together. They will help us tremendously as we
investigate and kill off these issues.
Second, we recognized the performance drop prior to this thread and Max and
Carl had already been doing out
On Thu May 10 01:07:31 UTC 2012 pull request #752 was closed.
(#14391) Fix inaccurate message from Hiera data lookups requested by (kelseyhightower)
The pull request was merged by: daniel-pittman
--
You received this message because you are subscribed to the Google G
Please review pull request #201: (#14366) is_virtual/virtual should be triggered by EC2 opened by (kjoconnor)
Description:
Uses the built-in EC2 checks that populate the ec2_* facts to see
if we're running on EC2 and populate the is_virtual/virtual facts
appropriately.
T
Please review pull request #752: (#14391) Fix inaccurate message from Hiera data lookups opened by (kelseyhightower)
Description:
When the Hiera gem is missing the error message now reads:
"Hiera terminus not supported without hiera library"
Opened: Thu May 1
On Thu May 10 00:23:11 UTC 2012 pull request #207 was closed.
(maint) move EnvSetup to before we actually try to install requested by (justinstoller)
The pull request was merged by: djm68
--
You received this message because you are subscribed to the Google Groups "P
On Thu May 10 00:22:08 UTC 2012 pull request #173 was closed.
(maint) Give the Test Harness an idiomatic Ruby layout requested by (justinstoller)
--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group
Please review pull request #206: Add --modules command line option to test modules opened by (jeffmccune)
Description:
Without this patch the git acceptance type has no way to install
arbitrary Puppet modules. We need this functionality to properly test
the Registry pupp
On Wed May 09 23:47:25 UTC 2012 pull request #749 was closed.
Remove deprecated standalone executables requested by (pcarlisle)
--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group, send email to pu
Please review pull request #751: (#3909) Strip trailing dot from default FQDN opened by (hkenney)
Description:
In Facter pull request 200 the default domian can no longer end
with a trailing '.'. This modifies Puppet's defaults to mirror
that change.
Opened: W
Please review pull request #200: (#3909) Strip trailing dots from domain fact opened by (hkenney)
Description:
Prior to this commit, the domain could end in '.' or could not.
Now, normalizing to no trailing '.' in domain fact. This also
works properly for top level domain
Jeff came over and asked Daniel and I about this. He might be able to give his
understanding, as well. My response is below.
On May 9, 2012, at 2:26 PM, Kelsey Hightower wrote:
> On Tuesday, May 8, 2012 7:17:33 PM UTC-4, Andy Parker wrote:
> I'll chime in on this now, I suppose.
>
> You are rig
On Wed May 09 23:21:54 UTC 2012 pull request #205 was closed.
(maint) Add Hiera install option requested by (djm68)
The pull request was merged by: cprice-puppet
--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
T
Please review pull request #205: (maint) Add Hiera install option opened by (djm68)
Description:
Add -h and --hiera + URI to install Hiera. Creates a default
hiera.yaml file as well.
TODO: add Windows install option as well.
Opened: Wed May 09 23:09:11 UTC 20
> But meanwhile, I have no template, so Im' still wondering where I put my
> type and resource provider files in this thing :-}
> "puppet module build" just seemed to create a "pkg" directory, and a
> tarfile.
> Without some output like the "generate" stuff, I still have been given no
> clue where
On Wednesday, May 9, 2012 2:23:46 PM UTC-7, Ken Barber wrote:
>
> >
> > As a suggestion.. if you guys INSIST on overloading the term "module",
> to
> > cover both user-level code, and back-end code, then I would recommend
> you
> > add an additional, separate subcommand to puppet-module, tha
>> > And IMO, that's as it should be. Back end ruby language code should be
>> > held
>> > separate from regular "puppet language code" stuff.
>>
>> I'm still not convinced, but I'm open to being convinced :-).
>>
>
> Here's the important factor, which you guys @puppetlabs simply cannot see,
> beca
On Wednesday, May 9, 2012 at 2:21 PM, Philip Brown wrote:
>
> ookay.. lots of questions, so you get lots of answers :)
>
I figured it would save us both time if none of my questions are helpful. :)
>
> I need a top level validate, not one under a newparam(). I need to ensure
> that multiple pa
On Wednesday, May 9, 2012 2:23:46 PM UTC-7, Ken Barber wrote:
>
> >
> > And IMO, that's as it should be. Back end ruby language code should be
> held
> > separate from regular "puppet language code" stuff.
>
> I'm still not convinced, but I'm open to being convinced :-).
>
>
Here's the import
On Wed May 09 21:16:05 UTC 2012 pull request #741 was closed.
(#13341) nested exceptions requested by (pcarlisle)
The pull request was merged by: cprice-puppet
--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To
On Tuesday, May 8, 2012 7:17:33 PM UTC-4, Andy Parker wrote:
>
> I'll chime in on this now, I suppose.
>
> You are right that both read and write operations are good for
> abstraction. The problem comes that comes into play is that read and write
> operations usually end up with completely differ
> Once again, I hit a "documentation is lacking" problem.
>
> The above command generates a whole BUNCH of files:
> ./tests/init.pp
> ./README
> ./Modulefile
> ./spec/spec.opts
> ./spec/spec_helper.rb
> ./metadata.json
> ./manifests/init.pp
Yeah - my bad, I'm sorry - try 'puppet module build' afte
On Wednesday, May 9, 2012 2:00:01 PM UTC-7, Nick Lewis wrote:
>
> On Wednesday, May 9, 2012 at 1:55 PM, Philip Brown wrote:
>
> I'm interested in the pattern of
>
> if provider.respond_to?()
>
>
> In particular,
>
> provider.validate if provider.respond_to?(:validate)
>
> I have
>
> def validat
On Wednesday, May 9, 2012 at 1:55 PM, Philip Brown wrote:
> I'm interested in the pattern of
>
> if provider.respond_to?()
>
>
> In particular,
>
> provider.validate if provider.respond_to?(:validate)
>
> I have
>
> def validate
> blah blah
>
> in my provider, but that does not seem to b
I'm interested in the pattern of
if provider.respond_to?()
In particular,
provider.validate if provider.respond_to?(:validate)
I have
def validate
blah blah
in my provider, but that does not seem to be enough.
--
You received this message because you are subscribed to the Google Groups
On Thu, May 3, 2012 at 2:25 PM, Trevor Vaughan wrote:
> All,
>
> I've noticed an understandable correlation between catalog size and
> config retrieval time. However, I'm a bit lost as to why it seems so
> slow.
>
> For an example 1.5M catalog:
>
> 24 seconds compile time
> Almost instantaneous tr
Please review pull request #749: Remove deprecated standalone executables opened by (pcarlisle)
Description:
This removes the standalone filebucket, pi, puppetdoc, and ralsh commands.
Opened: Wed May 09 20:31:28 UTC 2012
Based on: puppetlabs:master (13
Please review pull request #748: Move rubygems require to executable entry points to Puppet opened by (pcarlisle)
Description:
We were trying to load rubygems in lib/puppet.rb so that we could load other
libraries installed as gems, but this isn't anywhere near the first
On Wed, May 9, 2012 at 2:15 AM, Peter Meier wrote:
>> Otherwise i work on Puppet optimizations and i have seen some strange
>> things too. I work on big catalog (more than 1000 resources) and i want to
>> reduce the application time (around 20 sec).
>> I have seen two kind of things:
>> - First,
This is a maintenance release candidate of Puppet Dashboard.
It includes contributions from Daniel Sauble, Danijel Ilisin, and Patrick
Carlisle.
This release is available for download at:
http://downloads.puppetlabs.com/dashboard/
We have included Debian and RPM packages, as well as a tarball.
S
On Wed May 09 17:49:56 UTC 2012 pull request #97 was closed.
Update contributors in readme requested by (haus)
The pull request was merged by: lifton
--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to th
It's interesting this problem has come up because all of a sudden I'm
plagued
by incredibly slow config retrieval:
Changes:
Total: 2
Events:
Success: 2
Total: 2
Resources:
Changed: 2
Out of sync: 2
Total: 390
Skipped: 6
Time:
Please review pull request #97: Update contributors in readme opened by (haus)
Description:
It's been a long time since the contributors listed in the README.markdown were
updated, so this updates the contributors list based on the current git
history.
Opened:
Please review pull request #199: (#7484) Domain Fact should handle TLD opened by (hkenney)
Description:
The domain fact executed "hostname" on all platforms,
however the default on Linux is that "hostname" does not return FQDN.
This causes problems when the machine only h
Also... my earlier assumption seems to be correct. In principle, at least.
Just looking at the "best practices layout" autogenerated there... this
seems to be primarily geared towards *classes*, and end user "modules".
Not back end "here's a whole new resource type" code.
A module is more than j
On Sunday, May 6, 2012 2:09:20 PM UTC-7, Ken Barber wrote:
>
>
> >> Do you really think its hard? I was under the impression it was
> >> relatively easy these days.
> >
> >
> > huh. I dunno, lets just say that it did not seem that way at
> >
> https://github.com/puppetlabs/puppet-module-too
On Wed May 09 16:45:07 UTC 2012 pull request #198 was closed.
Ticket/1.6.x/7484 domain fact should handle tld requested by (hkenney)
--
You received this message because you are subscribed to the Google Groups "Puppet Developers" group.
To post to this group, send email
On 09.05.2012 11:15, Peter Meier wrote:
But anyway I remember that caching the catalog (read serializing it as
yaml to disk) has been very slow for years and also known. It usually
makes the agent look like it's hanging. This especially happens on huge
catalogs - I have catalogs with up to 10k re
Otherwise i work on Puppet optimizations and i have seen some
strange things too. I work on big catalog (more than 1000 resources)
and i want to reduce the application time (around 20 sec).
I have seen two kind of things:
- First, recent Puppet versions are slowest (see PuppetVersions.png
in
Hi,
Trevor Vaughan a écrit :
All,
I've noticed an understandable correlation between catalog size and
config retrieval time. However, I'm a bit lost as to why it seems so
slow.
For an example 1.5M catalog:
24 seconds compile time
Almost instantaneous transfer time (localhost)
40 seconds regis
Hi,
Trevor Vaughan a écrit :
All,
I've noticed an understandable correlation between catalog size and
config retrieval time. However, I'm a bit lost as to why it seems so
slow.
For an example 1.5M catalog:
24 seconds compile time
Almost instantaneous transfer time (localhost)
40 seconds regis
40 matches
Mail list logo
