Jira (FACT-718) Allow for disabling certain facts within Facter

[Robin Bowes (JIRA)]

Robin Bowes commented on FACT-718

Re: Allow for disabling certain facts within Facter Additionally, I'd like to disable specific ec2 facts. For example, ec2_iam* should not be reported as facts, and ec2_network_interface_macs* are just clutter in an environment with an high turnover of nodes. Add Comment

This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)

[Rob Reynolds (JIRA)]

Rob Reynolds commented on FACT-718

Re: Allow for disabling certain facts within Facter

Peter Huene Paul just pointed this out... is this on the radar at all? cc stack72

Add Comment

[Peter Huene (JIRA)]

Peter Huene commented on FACT-718

Re: Allow for disabling certain facts within Facter

This wasn't on the radar for Facter 3 at least. We should look into the best way of filtering out undesirable facts that just clutter things up.

Add Comment

[Kylo Ginsberg (JIRA)]

Kylo Ginsberg assigned an issue to Unassigned

Facter / FACT-718

Allow for disabling certain facts within Facter

Change By: Kylo Ginsberg Assignee: Eric Sorenson Scrum Team: Client Platform

Add Comment

[Kylo Ginsberg (JIRA)]

Kylo Ginsberg commented on FACT-718

Re: Allow for disabling certain facts within Facter This needs some design/requirements work, but marking as "Ready for Engineering" so it shows up on our scrum boards

Add Comment

[stack72 (JIRA)]

stack72 commented on FACT-718

Re: Allow for disabling certain facts within Facter

Thanks for getting in touch about this. By solving this issue, we would avoid situations like this: https://t.co/9oEwsMuMKG By collecting all these facts (that I am personally not interested in), my puppetdb is working harder than it should be. This is a great article on why I started looking into this topic https://t.co/DahIH9VeX6

Add Comment

[Jon Bidinger (JIRA)]

Jon Bidinger commented on FACT-718

Re: Allow for disabling certain facts within Facter

In addition to the large set of returned values, this can take a long time to complete. fact='partitions', resolution='<anonymous>': 54852.08ms

Add Comment

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

[Jon McKenzie (JIRA)]

Jon McKenzie commented on FACT-718

Re: Allow for disabling certain facts within Facter

I'm also having ENC issues due to the shear number of dynamically generate facts. In my specific case, it's EC2 interface facts (about 10 per mac address). With lots of interfaces and instances, this is causing some slowdowns

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[Arnaud Morin (JIRA)]

Arnaud Morin commented on FACT-718

Re: Allow for disabling certain facts within Facter

Hi, I have exactly the same issue, I definitely need a way to filter facts!

Add Comment

[Adam Bottchen (JIRA)]

Adam Bottchen updated an issue

Facter / FACT-718

Allow for disabling certain facts within Facter

Change By: Adam Bottchen CS Priority: Needs Priority

Add Comment

[Kylo Ginsberg (JIRA)]

Kylo Ginsberg commented on FACT-718

Re: Allow for disabling certain facts within Facter Hello watchers of this ticket, This has come up more often of late, both in this ticket and anecdotally, so there's clearly a general need. There's also some need for discussion to make sure we come up with something usable and maintainable. So please do chime in with any design thoughts here. For starters I want to test three assertions: there's value to reducing what facts are collected in at least two arenas: a) resource consumption on the agent, and b) resource consumption on the master (pdb, etc). I'm calling this out to highlight that a solution where, say, we collected all the facts but blacklisted what we report, would not be a good solution. We want to not even collect unwanted facts. we'd prefer a blacklist to a whitelist (all comments here have been for a blacklist, but one idea on the puppet-users thread mentioned a whitelist/blacklist hybrid). we could blacklist top-level structured facts (e.g. ec2, partitions, blockdevices) and don't need more fine-grained blacklisting (and a top-level structured fact being blacklisted should imply that any associated legacy flat facts are also blacklisted). I think this will be more practical to implement, esp if we want to honor the use case that we keep resource consumption on the agent low.

Add Comment

[Jon Bidinger (JIRA)]

Jon Bidinger commented on FACT-718

Re: Allow for disabling certain facts within Facter

For my use cases, I can agree with all three assertions.

Add Comment

[Charlie Sharpsteen (JIRA)]

Charlie Sharpsteen updated an issue

Facter / FACT-718

Allow for disabling certain facts within Facter

Change By: Charlie Sharpsteen CS Priority: Needs Priority Reviewed CS Impact: In Facter 2.x, core facts could be disabled globally by removing the relevant .rb files. However, with Facter 3.x, this is no longer possible. Additionally, there are facts, such as network drives, which may be expensive to run on certain systems. The ability to conditionally disable core and custom facts would provide a workaround to both problems.

Add Comment

[Michael Smith (JIRA)]

Michael Smith updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Michael Smith Sprint: Client Triage

Add Comment

[Steve Barlow (JIRA)]

Steve Barlow assigned an issue to Eric Sorenson

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Steve Barlow Assignee: Eric Sorenson

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Eric Sorenson Fix Version/s: FACT 3.2.0

Add Comment

[Kylo Ginsberg (JIRA)]

Kylo Ginsberg updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Kylo Ginsberg Sprint: Client Triage

Add Comment

[Michael Smith (JIRA)]

Michael Smith updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Michael Smith Discussed here: https://groups.google.com/forum/#!topic/puppet-users/SCfVE1kpTpk With version 1.7 facts were added for each mounted volume.  When run on a server attached to a SAN with say 1,000 volumes mounted, end up with over 3,000 facts (and chocking our ENC). Would like the ability to disable these facts via a configuration file. ---- A temporary work-around for this in Facter 3 (structured facts) is to declare a custom fact with the same name, which will mask default facts. I'm not sure how to apply that for dynamically-named facts.

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

[Corey Hickey (JIRA)]

Corey Hickey commented on FACT-718

Re: Allow for disabling certain facts within Facter I agree as well. I found out about this ticket when tracking down "suspicious" connection attempts to 169.254.169.254 that turned out to be caused by EC2 detection. Being able to disable known-unwanted functionality would be useful. Thanks, Corey

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson commented on FACT-718

Re: Allow for disabling certain facts within Facter

There's an ongoing thread on the puppet-dev list about this: https://groups.google.com/d/topic/puppet-dev/bebmBUyRETg/discussion Could the watchers on this ticket take a minute to read through that and chime in if there's anything that seems wrong and/or crazy there? Alternately, a +1 with info about your must-have use cases would be super helpful.

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-718

Allow for disabling certain facts within Facter

Change By: Branan Riley Story Points: 5

Add Comment

[Branan Riley (JIRA)]

Branan Riley assigned an issue to Unassigned

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Branan Riley Assignee: Eric Sorenson

Add Comment

[Steve Barlow (JIRA)]

Steve Barlow updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Steve Barlow Sprint: Client 2016-08-10

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Branan Riley Sprint: Client 2016-08- 10 24

Add Comment

[David Kramer (JIRA)]

David Kramer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: David Kramer Fix Version/s: FACT 3.4.0

Add Comment

[Branan Riley (JIRA)]

Branan Riley updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Branan Riley Fix Version/s: FACT 3.5.0

Add Comment

[Steve Barlow (JIRA)]

Steve Barlow updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Steve Barlow Sprint: Client 2016- 08 09 - 24 07

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Maggie Dreyer Sprint: Client 2016- 09 08 - 07 24

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer assigned an issue to Maggie Dreyer

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Maggie Dreyer Assignee: Maggie Dreyer

Add Comment

[Phong Ly (JIRA)]

Phong Ly updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Phong Ly QA Risk Assessment: High QA Status: Reviewed

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Maggie Dreyer Sprint: Client 2016-08-24

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Maggie Dreyer Sprint: Client 2016-09-07

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Geoff Nichols Team: Agent & Platform Support

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[David Kramer (JIRA)]

David Kramer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: David Kramer Sprint: Client 2016-09-07 , Client 2016-09-21

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Geoff Nichols Sprint: Client 2016-09-07,  Client  APS  2016-09-21

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti assigned an issue to Glenn Sarti

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Glenn Sarti Assignee: Glenn Sarti

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti commented on FACT-718

Re: Allow for disabling certain facts within Facter PR Review: Adhoc build started at; https://jenkins.puppetlabs.com/view/puppet-agent/view/ad%20hoc/job/platform_puppet-agent_init-van-int_suite-manual-ad-hoc/324/

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti commented on FACT-718

Re: Allow for disabling certain facts within Facter

Merged into master at; https://github.com/puppetlabs/facter/commit/72e0260341a4ca52831d6520cd5f123d441e24ea

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti commented on FACT-718

Re: Allow for disabling certain facts within Facter

FACT-1507 has been raised to address acceptance tests.

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti commented on FACT-718

Re: Allow for disabling certain facts within Facter

Build started at; https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/facter/job/platform_facter_init-van-component_master/103/

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti commented on FACT-718

Re: Allow for disabling certain facts within Facter

Build completed with success https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/facter/job/platform_facter_pkg-van-promote_master/84/

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti assigned an issue to qa

Facter / FACT-718

Allow for disabling certain facts within Facter

Change By: Glenn Sarti Status: Ready for  CI  Test Assignee: Glenn Sarti qa

Add Comment

[Glenn Sarti (JIRA)]

Glenn Sarti assigned an issue to Stan Duffy

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Glenn Sarti Assignee: qa Stan Duffy

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Some facts are blockable in groups, as described in the fact schema. Adding one of these groups to the config file list element `blocklist` will not be resolved the next time Facter is run. This is useful to block facts that are very expensive to resolve, or even completely broken, if they are not needed by the user. Example: facts : { blocklist : [ "EC2", "file system" ] } If this block is present in the config file, EC2 facts and file system facts (e.g. mountpoints, partitions) will not be resolved. This feature is currently enabled for only a small subset of facts. If a fact has a `blockgroup` listed in its description, it can be blocked with this feature, along with all the other facts in that group. Blocking only subsets of groups is not supported. Change By: Maggie Dreyer Release Notes Summary: This allows the user to specify in the config file a list of fact groups that will be prevented from resolving the next time Facter runs. Release Notes: New Feature

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Maggie Dreyer Comment: Some facts can now be blocked via a list in the config file:

facts : {     blocklist : [ "EC2", "file system" ] }

The above block would prevent the EC2 facts and the file system facts (e.g. mountpoints, partitions) from being resolved the next time Facter runs. This is useful for blocking facts which are either expensive to collect, or whose collection causes issues on a given system, if the user does not need to use the fact values. This feature is not enabled for all facts. If a fact has a `blockgroup` field in its schema description, it can be blocked using the above list, along with all the other facts in that group. Blocking subsets of groups is not supported.

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Some facts can now be blocked via a list in the config file:

facts : { blocklist : [ "EC2", "file system" ] } The above block would prevent the EC2 facts and the file system facts (e.g. mountpoints, partitions) from being resolved the next time Facter runs. This is useful for blocking facts which are either expensive to collect, or whose collection causes issues on a given system, if the user does not need to use the fact values. This feature is not enabled for all facts. If a fact has a `blockgroup` field in its schema description, it can be blocked using the above list, along with all the other facts in that group. Blocking subsets of groups is not supported.

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Maggie Dreyer Comment: Some facts are blockable in groups, as described in the fact schema. Adding one of these groups to the config file list element `blocklist` will not be resolved the next time Facter is run. This is useful to block facts that are very expensive to resolve, or even completely broken, if they are not needed by the user. Example:

facts : {     blocklist : [ "EC2", "file system" ] }

If this block is present in the config file, EC2 facts and file system facts (e.g. mountpoints, partitions) will not be resolved. This feature is currently enabled for only a small subset of facts. If a fact has a `blockgroup` listed in its description, it can be blocked with this feature, along with all the other facts in that group. Blocking only subsets of groups is not supported.

Add Comment

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Maggie Dreyer Release Notes Summary: This allows Some facts are blockable in groups, as described in  the  user  fact schema. Adding one of these groups  to  specify in  the config file  a  list  of fact groups that  element `blocklist`  will  not  be  prevented from resolving  resolved  the next time Facter  runs  is run .  This is useful to block facts that are very expensive to resolve, or even completely broken, if they are not needed by the user.

Example: facts : { blocklist : [ "EC2", "file system" ] } If this block is present in the config file, EC2 facts and file system facts (e.g. mountpoints, partitions) will not be resolved. This feature is currently enabled for only a small subset of facts. If a fact has a `blockgroup` listed in its description, it can be blocked with this feature, along with all the other facts in that group. Blocking only subsets of groups is not supported.

Add Comment

[Geoff Nichols (JIRA)]

Geoff Nichols updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Geoff Nichols Component/s: DOCS

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

Facter / FACT-718 Allow for disabling certain facts within Facter

Change By: Claudia Petty Labels: new-feature redmine

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)