On Tuesday, September 18, 2012 1:36:53 PM UTC-5, Philip Brown wrote:
[yes, this is a reply to an OOOLD message. sorry :) I think it's still
useful]
This is regarding a construct that I suggested to the list back in May,
and still haven't found anything better for my purposes.
So, I'm
On Wed, Sep 19, 2012 at 7:36 AM, jcbollinger john.bollin...@stjude.org wrote:
On Tuesday, September 18, 2012 1:36:53 PM UTC-5, Philip Brown wrote:
...
...
I think that's just fine. Though no one would know from the responses you
received before, I think some people do pretty much what
[yes, this is a reply to an OOOLD message. sorry :) I think it's still
useful]
This is regarding a construct that I suggested to the list back in May, and
still haven't found anything better for my purposes.
So, I'm fleshing out the implementation details for people a bit more.
The idea:
Have
I vaguely recall some kind of reference mentioning that as a fallback,
puppet master would attempt to load host.fqdn.pp to find a node
definition. Is that a false memory?
In practice, it does not seem to do that.
Along those lines, is it possible to MAKE it do that?
I've tried
import
At the bottom of my site.pp I have:
import nodes/*
I haven't heard of this autoload thing, but then I'm newish.
On Wed, May 02, 2012 at 11:06:17AM -0700, Philip Brown wrote:
I vaguely recall some kind of reference mentioning that as a fallback,
puppet master would attempt to loadÂ
Hi,
load host.fqdn.pp to find a node
it will search hostname and fqdn but not hostname.fqdn.
This all sounds like a lot of work to me. How do you intend to manage changes
that effect 300 nodes?
What I do is that I create a custom that assigns a role to certain node types.
I then have a
