On Feb 1, 2012, at 8:06 PM, Nan Liu wrote:
> On Wed, Feb 1, 2012 at 4:40 PM, Dustin Little wrote:
>> Hoping to get some insight from the community. Can puppet/mcollective/
>> facter collect/store facts about hosts that are not actually running
>> puppet? I see that custom facts can be gathered v
On Wed, Feb 1, 2012 at 4:40 PM, Dustin Little wrote:
> Hoping to get some insight from the community. Can puppet/mcollective/
> facter collect/store facts about hosts that are not actually running
> puppet? I see that custom facts can be gathered via shell scripts.
> Might this be used to build ho
So,
You can run Facter independently of Puppet, yes. You can have Facter
export a file to YAML by doing `facter --yaml > file.yaml` and then use
that file with MCollective (MCollective would use that YAML file full of
fact data to respond to queries that are filtered according to fact
information
Hoping to get some insight from the community. Can puppet/mcollective/
facter collect/store facts about hosts that are not actually running
puppet? I see that custom facts can be gathered via shell scripts.
Might this be used to build host resources and obtain facts? Also how
well do puppet/mcollec
Hi guys,
I've got a few questions regarding Puppet. We're currently investigating it
for deployment at the ISP where I work.
Here's some questions that have been raised;
Why the pull architecture?
How can this be achieved using a push, what are the limitations?
What are the implications of usi
