On May 14, 8:52 am, Simon J Mudd sjm...@pobox.com wrote:
sjm...@pobox.com (Simon J Mudd) writes:
john.bollin...@stjude.org (jcbollinger) writes:
In fact, Puppet Labs's own recently updated style guide recommends
against using extlookup(), though that position is controversial.
I
john.bollin...@stjude.org (jcbollinger) writes:
On May 14, 8:52 am, Simon J Mudd sjm...@pobox.com wrote:
However, from the discussion a few things strike me:
1. the use of parameterised classes is recommended heavily. I've just
found out about this new feature inspite of using puppet
- Original Message -
john.bollin...@stjude.org (jcbollinger) writes:
Perhaps. To some extend my non-parameterised classes are _very_ similar
in many ways except for various parameters (creation of logical volumes
and filesystems, version of mysql to use, creation of certain cron
Hi John,
john.bollin...@stjude.org (jcbollinger) writes:
...
Let's not cast things in terms of correctness, except insomuch as
whether they reliably produce the desired effect on clients.
Indeed. As always there is more than one way to solve a problem.
Depending on what you're trying to do
r...@devco.net (R.I.Pienaar) writes:
- Original Message -
john.bollin...@stjude.org (jcbollinger) writes:
Perhaps. To some extend my non-parameterised classes are _very_ similar
in many ways except for various parameters (creation of logical volumes
and filesystems, version of
- Original Message -
r...@devco.net (R.I.Pienaar) writes:
- Original Message -
john.bollin...@stjude.org (jcbollinger) writes:
Perhaps. To some extend my non-parameterised classes are _very_
similar
in many ways except for various parameters (creation of
Hi John,
While you obviously disagree with me, thanks for taking the time to
reply. I may be looking at the problem the wrong way which is why
I'm trying to figure out if that's the case and why.
john.bollin...@stjude.org (jcbollinger) writes:
On May 13, 8:07 am, jcbollinger
r...@devco.net (R.I.Pienaar) writes:
Let me not be taken as an extlookup() zealot. I do like the design
as it is, but that doesn't mean it is ideal -- or even good -- for every
purpose. One of the advantages of Puppet, however, is that it is
fairly easy to modify and extend. If you
On May 14, 2011, at 12:55 AM, Simon J Mudd wrote:
Hi John,
While you obviously disagree with me, thanks for taking the time to
reply. I may be looking at the problem the wrong way which is why
I'm trying to figure out if that's the case and why.
john.bollin...@stjude.org (jcbollinger)
kc7...@gmail.com (Patrick) writes:
On May 14, 2011, at 12:55 AM, Simon J Mudd wrote:
...
Not if they are part of the primary key. That's part of the point.
Any modern database can sustain thousands of queries a second doing this.
However, you are right small sites may not want to go this
john.bollin...@stjude.org (jcbollinger) writes:
In fact, Puppet Labs's own recently updated style guide recommends
against using extlookup(), though that position is controversial.
I found the URL: http://docs.puppetlabs.com/guides/style_guide.html
The extlookup() Function
Modules should
sjm...@pobox.com (Simon J Mudd) writes:
john.bollin...@stjude.org (jcbollinger) writes:
In fact, Puppet Labs's own recently updated style guide recommends
against using extlookup(), though that position is controversial.
I found the URL:
On May 13, 1:25 am, Simon J Mudd sjm...@pobox.com wrote:
Hi,
I have been trying to improve the coding of some of
my puppet recipes and had some trouble so wrote
this:http://blog.wl0.org/2011/05/thoughts-about-extlookup-in-puppet/
Comments on the web seem to indicate that extlookup()
- Original Message -
Let me not be taken as an extlookup() zealot. I do like the design
as it is, but that doesn't mean it is ideal -- or even good -- for every
purpose. One of the advantages of Puppet, however, is that it is
fairly easy to modify and extend. If you would like
14 matches
Mail list logo
