Nigel,
It frightens me a bit that I think the "correct" solution, will be to
replicate what the distros are doing in Puppetforge. Basically turning
puppetforge into a massive cross distro metadata repo, with very strict
contribution standards and rules. This would involve strong rules for
curated
I just wanted to post to this thread to primarily encourage you all to keep
brainstorming, and to make it clear that I'm paying close attention. :)
--
Nigel Kersten
Product Manager, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
Tried the same puppet setup in my homelab, no problems after upgrading.
Looking at the diffs, one of them was a kernel difference;
- test environment RHEL57 2.6.18-274.12.1.el5
- homelabRHEL57 2.6.18-274.17.1.el5
Remembered this bug; http://projects.puppetlabs.com/issues/10418, it
was
One more thing to keep in mind, the more templates you are compiling
also adds to time.
On Sat, Jan 28, 2012 at 11:11 AM, Antidot SAS wrote:
> Thx for answering, I really appreciated your investment, you gave some
> serious lead to search, I'll see on Monday and let you know if something
> comes
Thx for answering, I really appreciated your investment, you gave some
serious lead to search, I'll see on Monday and let you know if something
comes up. As far as swapping, no sign on the server.
On Fri, Jan 27, 2012 at 11:40 PM, jcbollinger wrote:
>
>
> On Jan 27, 11:10 am, Antidot SAS wrot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been mulling this over and wanted to get opinions on an, ugly, but
completely functional approach.
We've been talking about people supplying metadata to describe inter-class
dependencies (inter-module dependencies really, but hear me out). With
