Jira (PDB-5644) Puppet db export does not include unchanged resources in exported reports.
Title: Message Title Joshua Partlow created an issue PuppetDB / PDB-5644 Puppet db export does not include unchanged resources in exported reports. Issue Type: Bug Affects Versions: PDB 8.0.0, PDB 7.13.0 Assignee: Unassigned Components: PuppetDB Created: 2023/05/11 5:06 PM Priority: Normal Reporter: Joshua Partlow Running 'puppet db export' for reports that have unchanged resources (in in the reports.resources blob), produces a report with an empty resources array. (If there are resource_events, then the array will have just those resources that had resource_event). The expectation is that export would round trip the resources. Add Comment
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob in reports.logs )** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob in reports.metrics )** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path stored as a blob ( corresponds to depth of resource in catalog graph reports.resources )** events array ( but changed resource properties stored as in resource_events ) *** most variable old_value new_value message*** so each resource events array has one event per resource property change, (file content, owner, mode, for instance would be three events), but typically just one containment_path (corresponds to depth of resource in catalog graph) most variable* old_value* new_value* message Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11852) 11. Update Public-facing Puppet docs to remove fake_platform
Title: Message Title Aria Li created an issue Puppet / PUP-11852 11. Update Public-facing Puppet docs to remove fake_platform Issue Type: Task Assignee: Unassigned Created: 2023/05/11 1:59 PM Labels: os Priority: Normal Reporter: Aria Li Update Public-facing Puppet docs with removal of this platform Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11852) 11. Update Public-facing Puppet docs to remove fake_platform
Title: Message Title Aria Li updated an issue Puppet / PUP-11852 11. Update Public-facing Puppet docs to remove fake_platform Change By: Aria Li Epic Link: PA-5458 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.485529.1683838764000.12670.1683838800172%40Atlassian.JIRA.
Jira (PUP-11851) 11. Update Public-facing Puppet docs to remove fake_platform
Title: Message Title Aria Li created an issue Puppet / PUP-11851 11. Update Public-facing Puppet docs to remove fake_platform Issue Type: Task Assignee: Unassigned Created: 2023/05/11 1:34 PM Labels: os Priority: Normal Reporter: Aria Li Update Public-facing Puppet docs with removal of this platform Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11851) 11. Update Public-facing Puppet docs to remove fake_platform
Title: Message Title Aria Li updated an issue Puppet / PUP-11851 11. Update Public-facing Puppet docs to remove fake_platform Change By: Aria Li Epic Link: PA-5445 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.485507.168383724.12654.1683837300112%40Atlassian.JIRA.
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5593 Generating report data Change By: Joshua Partlow * logs (stored as a blob)** variable*** tags array*** message** plugin lines** could have debug lines* metrics (stored as a blob)** elements are simple structure (hash of name, value, category)** count of metrics somewhat variable based on type?* resources** containment_path (corresponds to depth of resource in catalog graph)** events array (stored as resource_events)*** most variable old_value new_value message*** ever more than 1 one event ? per resource property change, (file content, owner, mode, for instance would be three events), but typically just one Probably simplest to generate reports from the generated catalogs since that provides us with resources and structure already. Also makes the sample dataset more cohesive.How many variations to build per catalog? Since a report is a snapshot of change in time, could build several variants. Need to check and see how benchmark varies reports.Also need to think about unchanged resources. Does generate deal with that, or should benchmark mutate reports with that flag on or off? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (FACT-3202) Incorrect is_virtual and virtual facts on crio container runtime
Title: Message Title Jesse Hathaway created an issue Facter / FACT-3202 Incorrect is_virtual and virtual facts on crio container runtime Issue Type: Bug Assignee: Unassigned Created: 2023/05/11 1:02 PM Priority: Normal Reporter: Jesse Hathaway When using the crio container runtime facter reports the following incorrect information: $ facter is_virtual false $ facter virtual physical
Jira (FACT-3202) Incorrect is_virtual and virtual facts on crio container runtime
Title: Message Title Jesse Hathaway updated an issue Facter / FACT-3202 Incorrect is_virtual and virtual facts on crio container runtime Change By: Jesse Hathaway Affects Version/s: FACT 4.3.1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.485493.1683835348000.12649.1683835380100%40Atlassian.JIRA.
Jira (PUP-11850) 11. Update Public-facing Puppet docs to remove fake_platform 1.0
Title: Message Title Aria Li updated an issue Puppet / PUP-11850 11. Update Public-facing Puppet docs to remove fake_platform 1.0 Change By: Aria Li Epic Link: PA-5431 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.485475.1683831548000.12618.1683831600239%40Atlassian.JIRA.
Jira (PUP-11850) 11. Update Public-facing Puppet docs to remove fake_platform 1.0
Title: Message Title Aria Li created an issue Puppet / PUP-11850 11. Update Public-facing Puppet docs to remove fake_platform 1.0 Issue Type: Task Assignee: Unassigned Created: 2023/05/11 11:59 AM Labels: os Priority: Normal Reporter: Aria Li Update Public-facing Puppet docs with removal of this platform Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
