On Wednesday, January 21, 2015 at 11:36:25 AM UTC-6, Alessandro Franceschi
wrote:
Given that:
- I've used nodes inheritance with profit for years, in the past
- Now I mostly prefer a nodeless setup (with or without ENC)
let me spam the list with a fragment of my book Extending Puppet on
On Thursday, January 22, 2015 at 9:09:37 AM UTC-6, jcbollinger wrote:
[...] With that approach you can create an insanely complex, multi-level
node inheritance tree [...].
Clarification: though you safely *can* do that, you shouldn't.
John
--
You received this message because you
On Thursday, January 22, 2015 at 4:09:37 PM UTC+1, jcbollinger wrote:
On Wednesday, January 21, 2015 at 11:36:25 AM UTC-6, Alessandro Franceschi
wrote:
Given that:
- I've used nodes inheritance with profit for years, in the past
- Now I mostly prefer a nodeless setup (with or without
Given that:
- I've used nodes inheritance with profit for years, in the past
- Now I mostly prefer a nodeless setup (with or without ENC)
let me spam the list with a fragment of my book Extending Puppet on the
topic, as it contains some (controversial?) points of view I'm curious to
hear
Note that you can also just put the standard classes (and variables)
directly in the top scope. No real need to encapsulate them inside a node
scope (unless you are overriding the value of facts in the manifest, but
that seems like a pretty bad idea anyway).
A minor difference is also that
On Friday, January 9, 2015 at 3:34:41 PM UTC-6, RIlindo Foster wrote:
It seems you are using this as a way to classify nodes. Your best option
is to use an ENC (Foreman or Hiera) to classify your nodes, ideally using
the roles and profiles pattern to abstract your modules.
I strongly
This could work. I'll play with that to see what I can do.
Thanks for the replies!
Jason
On Fri, Jan 9, 2015 at 3:23 PM, Peter Bukowinski pmb...@gmail.com wrote:
On Jan 9, 2015, at 2:52 PM, Jason Price japr...@gmail.com wrote:
This doesn't make me happy, but fine. Major versions let you
On Jan 9, 2015, at 2:52 PM, Jason Price japr...@gmail.com wrote:
This doesn't make me happy, but fine. Major versions let you have breaking
changes.
My question is this: What do I replace it with?
My use case is as follows:
node default {
This doesn't make me happy, but fine. Major versions let you have breaking
changes.
My question is this: What do I replace it with?
My use case is as follows:
node default {
class{ 'ntp': }
class{ 'dns': }
class{ 'monitoring': }
class{
Clarification Request: NODE inheritance only, right ?
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin
Hobbes)
On Jan 09, 2015, at 02:52 PM, Jason Price japr...@gmail.com wrote:
It seems you are using this as a way to classify nodes. Your best option is to
use an ENC (Foreman or Hiera) to classify your nodes, ideally using the roles
and profiles pattern to abstract your modules.
On Jan 9, 2015, at 1:52 PM, Jason Price japr...@gmail.com wrote:
This doesn't make me
11 matches
Mail list logo
