>
> All I want to be able to do is set a variable on a per node basis that
> defines a functional grouping, ie a class of server, and query that with
> mcollective. Should not be difficult to do.
>
It isn't and it seems to me that you already know how to do it, just do not
try to assign that variable as a custom facts (it that doesn't show up in
the scope lookup) and set it in puppet manifests (or in the ENC), then set
factsource = yaml in mcollective config file and populate it with something
like:
file {"/etc/mcollective/facts.yaml":
owner => root,
group => root,
mode => 400,
loglevel => debug, # this is needed to avoid it being logged and
reported on every run
# avoid including highly-dynamic facts as they will cause
unnecessary template writes
content => inline_template("<%= scope.to_hash.reject { |k,v| k.to_s
=~ /(uptime.*|path|timestamp|free|.*password.*|.*psk.*|.*key)/ }.to_yaml
%>"),
require => Package["mcollective"],
}
I generally use this, in mcollective for custom variables like $role and
$role_group that are assigned on role classes that are included by nodes
(one node, one role).
The $role_group is useful, for me, to group all the machines (of different
roles) that cuncur to provide a service for users (they have all to work for
the service to be usable).
And trust me, when you can check in few seconds, whatever is relevant to a
site or a service offered to your users with something like:
mc-puppi check -F role_group=appstore
you are happy, but that's another story.
My2c
al
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/f8SYI1w3xiEJ.
To post to this group, send email to puppet-users@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.
