Hello.
I'm a about 2 months into a puppet poc. I've got the low hanging
fruit taken care of and have the standard manifests which apply to
every host of a given operating system. Basically just schlepping
lot's of standard files out to every host of a given OS type. No real
decision making or logic required.
j
Now I'm starting to branch out into node specific configurations
and would appreciate any input if the following is seen as a common
method to applying host specific configurations. As we progress
through our POC I want to have decent/common practices in place as I
teach the rest of the team.
In the following example I created class to support constructing
raidz(2) zpools.
class zfs::zpool {
zpool { "$my_zpool_name":
ensure => 'present',
raid_parity => "$my_zpool_parity",
raidz => [ "$my_zpool_disks" ]
}
}
Then for any node which will have zpools I include the class and
define the variables like this
node headbone {
# Define my zpool variables
$my_zpool_name = "localdisks"
$my_zpool_parity = "raidz2"
$my_zpool_disks = "c0t2d0 c0t3d0 c0t4d0 c0t5d0
c0t6d0 c0t7d0"
include zfs::zpool
}
Down the road as my needs get more complex and my experience with
puppet grows will I regret this method of node specific
configurations? Anyhoo just looking for any possible gotchas I
haven't taken into consideration.
TIA. Derek.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
