On Tue, Dec 11, 2012 at 6:52 PM, Jakov Sosic jso...@srce.hr wrote:
On 12/09/2012 04:39 PM, Stefan Goethals wrote:
Serving facts to nodes via puppet...
That means you already know those facts in puppet so you don't need to
serve them to the nodes anymore :-)
Yeah kinda beats the purpose of
Serving facts to nodes via puppet...
That means you already know those facts in puppet so you don't need to
serve them to the nodes anymore :-)
On Sun, Dec 9, 2012 at 1:31 AM, Jakov Sosic jso...@srce.hr wrote:
On 12/06/2012 06:44 PM, Stefan Goethals wrote:
Hi,
You could use facter-dot-d to
On 12/06/2012 06:44 PM, Stefan Goethals wrote:
Hi,
You could use facter-dot-d to set a fact on those servers specifying the
name of a storagegroup or a webcluster
and then use that fact in your hiera hierarchy
so you could have
/etc/facter/facts.d/servertype.yaml with content
Thank you, I
Hi.
I'm currently using hiera in a very rudimentary way, using only perhost
and common.
Now, I'm trying to group my hosts a little bit, so for example web
servers could have their own yaml with data. Problem is I don't have an
idea how to group hosts? How can I say to puppet that for example
Hi,
You could use facter-dot-d to set a fact on those servers specifying the
name of a storagegroup or a webcluster
and then use that fact in your hiera hierarchy
so you could have
/etc/facter/facts.d/servertype.yaml with content
servertype: storage_node ( or web_node )
Have in
Hello,
I do this using facter-dot-d.
For my environment, I group by physical location, so I have a text file
/etc/facter/facts.d/location.txt with contents of:
location=foobar
Then facter -p location will output the location of the node.
Then throughout my manifests, I use the meta-parameter
