Jira (PUP-6519) Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-6519 Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk Change By: Nicholas Fagerlund Labels: tcse triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6519) Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk
Title: Message Title Nicholas Fagerlund commented on PUP-6519 Re: Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk Hey Nick Walker, we're triaging and I think we're gonna close this. I don't think anyone would disagree that the cron job thing is bogus, but investing in Mco improvements to things that aren't strictly broken doesn't seem likely at the moment. Maybe re-open if we're going to start re-investing in mco? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6519) Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk
Title: Message Title Charlie Sharpsteen commented on PUP-6519 Re: Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk Something close to this has actually been possible for a while by setting the facts cache terminus to "yaml" in /etc/puppetlabs/puppet/routes.yaml agent: facts: cache: yaml That will cause the agent to update $clientyamldir/facts/$certname.yaml each time Facts are loaded. The problem is that MCollective expects facts to be in a slightly different format, it just wants the fact values and not the surrounding metadata. That's why the cron job contains: facts_y = facts.values.to_yaml So, this would probably also require an update to MCollective so that it can load Puppet fact sets directly, instead of demanding its own separate format. Add Comment
Jira (PUP-6519) Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk
Title: Message Title Nick Walker created an issue Puppet / PUP-6519 Allow The Initial Facter Run in an Agent Run To Log its Output To a File on Disk Issue Type: Improvement Assignee: Unassigned Created: 2016/07/18 5:31 PM Labels: tcse Priority: Normal Reporter: Nick Walker The Specific Problem When you source facts from disk for mcollective as is such in Puppet Enterprise you need to have an ability to update the facts on disk. Why setup a cron job to run facter every so often when the puppet agent is already running facter every 30 mins by default? The Proposed Solution Puppet agent should allow you to log the output of it's initial facter run to a file on disk. In the mcollective case I could configure it to log the output to the file mcollective reads facts from and then I'd have an automated way to update my facts for mcollective ( assuming I'm okay when them only updating every runinterval). Other Use Cases I can imagine some other use case when facter is slow to run and you want to use some facter output for something outside of puppet. Assuming the output you want is not time-sensitive it would be nice to be able to grab it from a file on disk instead of needing to invoke facter.
