We probably have the quintessential setup for using node inheritance.
We now have about 1000 nodes in a HPC cluster with CentOS 5.x. About 950
nodes are identical, and the naming scheme is simplistic (vmp). The
remaining nodes are gateways that users log into to launch jobs,
or infrastructure
ENC + include/require = no need for inheritance.
Classify roles for your servers, assign classes and parameters to the roles.
On Wed, Aug 10, 2011 at 4:33 PM, Darrell Fuhriman wrote:
> [Following up a little late]
>
> Is anyone using node inheritance and happy with how it works? If so, can
> yo
[Following up a little late]
> Is anyone using node inheritance and happy with how it works? If so, can you
> describe your setup briefly?
I make very limited use of node inheritance. I use
node basenode {
include $operatingsystem
[other stuff I want absolutely everywhere]
}
node default i
vagn scott:
> I think one could make a case for getting rid of global variables
> entirely.
Functionally, this is common advice for avoiding the pitfalls of
puppet's peculiar dynamic scope. Newcomers are often advised to use
$::foo::bar::baz to avoid picking up data from unexpected places in the
On Fri, Aug 05, 2011 at 06:33:12AM -0700, Nigel Kersten wrote:
> We have a bunch of problems people regularly run into with node inheritance,
> and it's something we'd like to find a better solution for.
>
> Is anyone using node inheritance and happy with how it works? If so, can you
> describe yo
On 08/05/2011 10:21 AM, R.I.Pienaar wrote:
But also now I think $foo should be considered a top level variable in 2.7
when its not, making node variables more or less useless.
I like it that node variables are local and private.
node default {
$foo = "$backupdir/${hostname}"
- Original Message -
> On 08/05/2011 09:33 AM, Nigel Kersten wrote:
> > We have a bunch of problems people regularly run into with node
> > inheritance, and it's something we'd like to find a better solution
> > for.
> >
> Let me guess:
>
> - nodes are not classes
> - n
On 08/05/2011 09:33 AM, Nigel Kersten wrote:
We have a bunch of problems people regularly run into with node
inheritance, and it's something we'd like to find a better solution for.
Let me guess:
- nodes are not classes
- node scope is not global scope
Is there something else
We have a bunch of problems people regularly run into with node inheritance,
and it's something we'd like to find a better solution for.
Is anyone using node inheritance and happy with how it works? If so, can you
describe your setup briefly?
--
Nigel Kersten
Product Manager, Puppet Labs
*Join
