Jira (PUP-7129) Use systemd service provider for Debian 9 (Stretch)
Title: Message Title Florian Klink updated an issue Puppet / PUP-7129 Use systemd service provider for Debian 9 (Stretch) Change By: Florian Klink Summary: Use systemd service provider for Debian 9 ( Strech Stretch ) 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-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title Nacho Barrientos commented on PUP-7302 Re: Puppet HTTP Node API: make fact_merge optional Something like this: https://github.com/puppetlabs/puppet/pull/5689 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-7303) Improve performance of hiera config stability check
Title: Message Title Thomas Hallgren commented on PUP-7303 Re: Improve performance of hiera config stability check Kenn Hussey, Henrik Lindberg, the PR for this ticket will give a measurable performance improvement for cases where the hiera.yaml file contains a large number of global interpolations. It would be great if it made it to 4.9.4 but I don't think it is critical. 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-7303) Improve performance of hiera config stability check
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7303 Improve performance of hiera config stability check Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7303) Improve performance of hiera config stability check
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7303 Improve performance of hiera config stability check Issue Type: Improvement Affects Versions: PUP 4.9.3 Assignee: Thomas Hallgren Created: 2017/03/04 6:05 AM Fix Versions: PUP 4.9.4 Priority: Normal Reporter: Thomas Hallgren The check to assert that a hiera configuration is stable with respect to interpolated values, does not take into account that a global variable (a variable that starts with '::') is immutable once set. The performance of this check will be greatly improved for use-cases that have a hiera.yaml files similar to this example file from a comment in PUP-7294 if such variables are exempt from the check. Add Comment
Jira (FACT-1574) Add acceptance tests for supported agent fact directories
Title: Message Title Geoff Nichols commented on FACT-1574 Re: Add acceptance tests for supported agent fact directories PR merged to facter#LTS-1.7 at https://github.com/puppetlabs/facter/commit/a2d8fb275ca3348bb4ce217ad50104d82a565431. 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-7271) performance regression in puppet 4.9
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7271 performance regression in puppet 4.9 Change By: Kenn Hussey Flagged: Impediment 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-7301) Avoid excessive type inference when checking instance_of?
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7301 Avoid excessive type inference when checking instance_of? Change By: Kenn Hussey Flagged: Impediment 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-7301) Avoid excessive type inference when checking instance_of?
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7301 Avoid excessive type inference when checking instance_of? Change By: Kenn Hussey Priority: Normal Critical 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-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title
Nacho Barrientos updated an issue
Puppet / PUP-7302
Puppet HTTP Node API: make fact_merge optional
Change By:
Nacho Barrientos
Hi,In a Puppet installation with PuppetDB available, each call of the agents to the [/node entrypoint|https://docs.puppet.com/puppet/latest/http_api/http_node.html] of the Puppet HTTP API generates a call to PuppetDB's _/vX/nodes/foo.example.com/facts_ if the list of facts is not cached on the master. This is very likely in our case because we have plenty of masters serving our agents and also because the TTL is 30 ~20 minutes, which is lower than our default Puppet run interval.This generates queries to PuppetDB which, unless I was missing something, are not necessary in our deployment and we'd rather to use those CPU cycles for something else. I fail to see how getting the list of last known facts as parameters are useful to the agent when calling _/node_ (first request during a Puppet run). OTOH, we do need variables coming from the ENC like the environment, of course.We managed to avoid those queries in a development master by doing this hack:{noformat}--- routes.yaml.orig2017-03-04 11:19:52.164820233 +0100+++ routes.yaml 2017-03-04 11:12:18.021435083 +0100@@ -6,6 +6,6 @@ ---master: facts: - terminus: puppetdb+ terminus: yaml cache: yaml{noformat}The Puppet agent run went fine, however this configuration prevents later on the masters from sending commands to PuppetDB to replace facts which is something we'd like to keep.Would you take into consideration a patch to, behind a setting, make [this behaviour|https://github.com/puppetlabs/puppet/blob/ebd96213cab43bb2a8071b7ac0206c3ed0be8e58/lib/puppet/node.rb#L116] optional?Thank you!
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title Nacho Barrientos created an issue Puppet / PUP-7302 Puppet HTTP Node API: make fact_merge optional Issue Type: Bug Assignee: Unassigned Created: 2017/03/04 3:31 AM Priority: Normal Reporter: Nacho Barrientos Hi, In a Puppet installation with PuppetDB available, each call of the agents to the /node entrypoint of the Puppet HTTP API generates a call to PuppetDB's /vX/nodes/foo.example.com/facts if the list of facts is not cached on the master. This is very likely in our case because we have plenty of masters serving our agents and also because the TTL is 30 minutes, which is lower than our default Puppet run interval. This generates queries to PuppetDB which, unless I was missing something, are not necessary in our deployment and we'd rather to use those CPU cycles for something else. I fail to see how getting the list of last known facts as parameters are useful to the agent when calling /node (first request during a Puppet run). OTOH, we do need variables coming from the ENC like the environment, of course. We managed to avoid those queries in a development master by doing this hack: --- routes.yaml.orig2017-03-04 11:19:52.164820233 +0100 +++ routes.yaml
Jira (PUP-7301) Avoid excessive type inference when checking instance_of?
Title: Message Title Thomas Hallgren commented on PUP-7301 Re: Avoid excessive type inference when checking instance_of? Kenn Hussey, Henrik Lindberg, in my opinion, it is imperative this ticket is included in 4.9.4. It makes a huge performance difference for large data sets in Hiera. 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-7301) Avoid excessive type inference when checking instance_of?
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7301 Avoid excessive type inference when checking instance_of? Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-7291) no hiera class parameter lookup debug information
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7291 no hiera class parameter lookup debug information Change By: Henrik Lindberg Release Notes Summary: The (very limited) debug output from Automatic Parameter Lookup (APL) was removed in Puppet 4.9.0 with the intention of replacing it with the full lookup --explain output, but the explain output ended up not being enabled for APL. This is now fixed making debugging of APL much easier. Release Notes: Bug Fix 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-7301) Avoid excessive type inference when checking instance_of?
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-7301 Avoid excessive type inference when checking instance_of? Issue Type: Bug Affects Versions: PUP 4.9.3 Assignee: Unassigned Created: 2017/03/04 12:31 AM Fix Versions: PUP 4.9.4 Priority: Normal Reporter: Thomas Hallgren The type of an instance is often inferred when checking if it is instance of a Pcore type. I.e: t.instance_of?(o) can be written as:
Jira (PUP-7301) Avoid excessive type inference when checking instance_of?
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7301 Avoid excessive type inference when checking instance_of? Change By: Thomas Hallgren Assignee: Thomas Hallgren 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.
