Jira (FACT-348) Facter should provide a convenient way to cache values

2 views
Skip to first unread message

Steve Traylen (JIRA)

unread,
Apr 24, 2015, 7:33:00 AM4/24/15
to puppe...@googlegroups.com
Steve Traylen commented on New Feature FACT-348
 
Re: Facter should provide a convenient way to cache values

This would be useful. For instance the ec2 facts which poll our nova master quite a bit.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Atlassian logo

Eric Sorenson (JIRA)

unread,
Mar 8, 2016, 8:26:03 PM3/8/16
to puppe...@googlegroups.com
Eric Sorenson updated an issue
 
Facter / New Feature FACT-348
Change By: Eric Sorenson
Fix Version/s: FACT 3.2.0
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Atlassian logo

Eric Sorenson (JIRA)

unread,
Mar 8, 2016, 8:27:04 PM3/8/16
to puppe...@googlegroups.com
Eric Sorenson commented on New Feature FACT-348
 
Re: Facter should provide a convenient way to cache values

Bringing this in to consideration for Facter 3.2.0.

Trey Dockendorf (JIRA)

unread,
May 3, 2016, 9:25:03 AM5/3/16
to puppe...@googlegroups.com
Trey Dockendorf assigned an issue to Trey Dockendorf
 
Change By: Trey Dockendorf
Assignee: Eric Sorenson Trey Dockendorf
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Atlassian logo

Trey Dockendorf (JIRA)

unread,
May 3, 2016, 9:26:02 AM5/3/16
to puppe...@googlegroups.com
Trey Dockendorf assigned an issue to Eric Sorenson
Change By: Trey Dockendorf
Assignee: Trey Dockendorf Eric Sorenson

Kenn Hussey (JIRA)

unread,
Jun 27, 2016, 1:37:04 PM6/27/16
to puppe...@googlegroups.com
Kenn Hussey commented on New Feature FACT-348
 
Re: Facter should provide a convenient way to cache values

Eric Sorenson do you have an update on whether/when we should be pursuing this?

Eric Sorenson (JIRA)

unread,
Jun 28, 2016, 2:27:06 AM6/28/16
to puppe...@googlegroups.com
Eric Sorenson commented on New Feature FACT-348

Kenn Hussey Yes we should - I'm working on a Puppet RFC for a facter.conf file, which includes TTLs as a feature.

Eric Sorenson (JIRA)

unread,
Jul 15, 2016, 7:42:04 PM7/15/16
to puppe...@googlegroups.com
Eric Sorenson updated an issue
Change By: Eric Sorenson
Scrum Team: Client Platform

Steve Barlow (JIRA)

unread,
Jul 18, 2016, 1:08:11 PM7/18/16
to puppe...@googlegroups.com
Steve Barlow updated an issue
Change By: Steve Barlow
Sprint: Client 2016-08-10

Kylo Ginsberg (JIRA)

unread,
Jul 20, 2016, 12:17:04 PM7/20/16
to puppe...@googlegroups.com
Kylo Ginsberg updated an issue
Change By: Kylo Ginsberg
Fix Version/s: FACT 3.4.0
Fix Version/s: FACT 3.5.0

Branan Riley (JIRA)

unread,
Jul 27, 2016, 12:33:07 PM7/27/16
to puppe...@googlegroups.com
Branan Riley updated an issue
Change By: Branan Riley
Sprint: Client 2016-08- 10 24

David Kramer (JIRA)

unread,
Aug 3, 2016, 12:19:04 PM8/3/16
to puppe...@googlegroups.com

Steve Barlow (JIRA)

unread,
Aug 10, 2016, 12:28:09 PM8/10/16
to puppe...@googlegroups.com
Steve Barlow updated an issue
Change By: Steve Barlow
Sprint: Client 2016- 08 09 - 24 07

David Kramer (JIRA)

unread,
Aug 24, 2016, 12:22:05 PM8/24/16
to puppe...@googlegroups.com
David Kramer updated an issue
Change By: David Kramer
Sprint: Client 2016-09- 07 21

Geoff Nichols (JIRA)

unread,
Sep 6, 2016, 8:57:04 PM9/6/16
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Team: Agent & Platform Support
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Geoff Nichols (JIRA)

unread,
Sep 7, 2016, 12:48:03 AM9/7/16
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Client APS  2016-09-21

Maggie Dreyer (JIRA)

unread,
Sep 8, 2016, 2:16:09 PM9/8/16
to puppe...@googlegroups.com
Maggie Dreyer assigned an issue to Unassigned
Change By: Maggie Dreyer
Assignee: Eric Sorenson

Maggie Dreyer (JIRA)

unread,
Sep 14, 2016, 4:25:04 PM9/14/16
to puppe...@googlegroups.com

Glenn Sarti (JIRA)

unread,
Sep 19, 2016, 12:58:03 AM9/19/16
to puppe...@googlegroups.com

Glenn Sarti (JIRA)

unread,
Sep 19, 2016, 6:46:07 PM9/19/16
to puppe...@googlegroups.com
Glenn Sarti assigned an issue to Maggie Dreyer
Change By: Glenn Sarti
Assignee: Glenn Sarti Maggie Dreyer

Geoff Nichols (JIRA)

unread,
Sep 21, 2016, 1:15:06 PM9/21/16
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Windows 2016-09-21, AP 2016-09-21

Geoff Nichols (JIRA)

unread,
Sep 21, 2016, 1:42:05 PM9/21/16
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Windows AP  2016- 09 10 - 21 05 , AP 2016-09-21

Glenn Sarti (JIRA)

unread,
Sep 30, 2016, 12:14:07 PM9/30/16
to puppe...@googlegroups.com

Glenn Sarti (JIRA)

unread,
Oct 3, 2016, 12:34:06 PM10/3/16
to puppe...@googlegroups.com

Maggie Dreyer (JIRA)

unread,
Oct 3, 2016, 1:13:06 PM10/3/16
to puppe...@googlegroups.com
Maggie Dreyer updated an issue
 
Change By: Maggie Dreyer
Release Notes Summary: This adds the ability to cache groups of facts for a specified length of time. Adding the name of a fact group along with a duration to the `ttls` section of the config file will cause Facter to only resolve that group of facts once, until the cache expires.

Example:

facts : { ttls : [ { "kernel" : 30 days }, { "file system" : 1 hour } ] }

will cause kernel and file system facts to be cached for 30 days and 1 hour, respectively. The names of cacheable fact groups can be found using the `--list-cache-groups` command line option.

The location of the cache is `/opt/puppetlabs/facter/cache/cached_facts/` on Unix and `C:\ProgramData\PuppetLabs\facter\cache\cached_fact\` on Windows.
Release Notes: New Feature

Glenn Sarti (JIRA)

unread,
Oct 3, 2016, 3:50:07 PM10/3/16
to puppe...@googlegroups.com

Glenn Sarti (JIRA)

unread,
Oct 3, 2016, 4:05:05 PM10/3/16
to puppe...@googlegroups.com
Glenn Sarti assigned an issue to Maggie Dreyer
 

Moved back to reviewing to track the promotion job of Facter goes all the way through the puppet-agent pipelines.

Change By: Glenn Sarti
Assignee: Maggie Dreyer

Maggie Dreyer (JIRA)

unread,
Oct 5, 2016, 11:53:03 AM10/5/16
to puppe...@googlegroups.com

Geoff Nichols (JIRA)

unread,
Oct 22, 2016, 12:03:06 AM10/22/16
to puppe...@googlegroups.com

Erik Dalén (JIRA)

unread,
Dec 13, 2016, 11:33:04 AM12/13/16
to puppe...@googlegroups.com
Erik Dalén commented on New Feature FACT-348
 
Re: Facter should provide a convenient way to cache values

Is there any way to set the cache group on a custom fact?
This would really be most useful for those as the builtin ones are pretty fast anyway.

Maggie Dreyer (JIRA)

unread,
Dec 13, 2016, 11:56:03 AM12/13/16
to puppe...@googlegroups.com
Maggie Dreyer commented on New Feature FACT-348

There is not currently a way to do that. On some people's systems, some of the built-in facts are quite slow, and caching them was straightforward, which is why we started there. Could you describe in a little more detail what your use case is and what sort of user experience you'd like to see for caching custom facts? That would help us design a good solution.

Tyler Pace (JIRA)

unread,
Dec 13, 2016, 1:44:04 PM12/13/16
to puppe...@googlegroups.com
Tyler Pace commented on New Feature FACT-348

Erik Dalén and I had a brief chat on Slack that I'll copy here for context.

https://puppetcommunity.slack.com/archives/puppet/p1481653413001521

tyler.pace [10:23 AM]
@dalen @mjolnir40k Do you have any other examples of custom facts that you would like to cache? And, how long would they be cached?

dalen [10:33 AM]
@tyler.pace a bunch of stuff from the `lshw` tool (that takes ~12 seconds to run on our hardware)
@tyler.pace 1 day cache time seems reasonable for that
@tyler.pace also some Dell Poweredge bios stuff that takes a while to read, firmware versions etc

tyler.pace [10:37 AM]
@dalen Would you want to add those facts to an existing cache group or perhaps be able to create your own custom cache group(s)?

dalen [10:38 AM]
@tyler.pace probably create our own would be best

Maggie Dreyer (JIRA)

unread,
Dec 13, 2016, 2:01:11 PM12/13/16
to puppe...@googlegroups.com
Maggie Dreyer commented on New Feature FACT-348

I haven't really put much thought into how to implement this yet, but it seems like the custom fact cache group/key would be something you would set in the fact itself, then use in the config file. If that group name was the same as a built-in group, all the built-in facts in that group would get cached along with the custom fact. If it was unique, only the custom fact(s) with that group would be cached.

Claudia Petty (Jira)

unread,
Jun 21, 2023, 8:44:04 AM6/21/23
to puppe...@googlegroups.com
Claudia Petty updated an issue
 
Change By: Claudia Petty
Labels: new-feature redmine
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages