Jira (PUP-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Rob Braden updated an issue Puppet / PUP-8636 Don't prefetch if every resource using a provider is noop'd or no scheduled Change By: Rob Braden Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8636 Don't prefetch if every resource using a provider is noop'd or no scheduled Change By: Owen Rodabaugh CS Priority: Needs Priority Minor CS Impact: Some resources such as selinux or mounts can be very expensive to run, taking minutes to run in some cases. Today this happens on every run even if that resource is only schedule to run a small portion of the time.This would be a nice feature for customers who have expensive resources being prefetched, potentially saving them up to minutes per puppet run. That said the schedule resource is not very commonly used. Metaparameters/filters such as schedule and tag based filtering would be suitable for this optimizationNoop still needs to prefetch check everything to determine what it will change and so would not work with this new feature. CS Severity: 2 - Annoyance CS Business Value: 2 - $$$ CS Frequency: 1 - 1-5% of Customers Add Comment
Jira (PUP-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8636 Don't prefetch if every resource using a provider is noop'd or no scheduled Change By: Owen Rodabaugh Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Charlie Sharpsteen commented on PUP-8636 Re: Don't prefetch if every resource using a provider is noop'd or no scheduled We still have to prefectch for noop as the noop'd resource has to report what change would have been made — which requires fetching the current state of the resource. Skipping prefetches when no resources of a given type are scheduled (or selected by something like a tag filter) does seem like a useful optimization. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title
Martin Ewings updated an issue
Puppet / PUP-8636
Don't prefetch if every resource using a provider is noop'd or no scheduled
Change By:
Martin Ewings
When a Particular Resource provider is defaulting to No-op or is part of a schedule which is not active, Puppet shouldn't prefetch any data relating to that provider in order to speed up compilation, for example: {code:java} schedule { 'narrow': range => '1:01 - 1:02', }Package <| provider == 'pkgutil' |> { schedule => 'narrow', } {code} this works in that the packages are skipped, the background provider tasks are still being completed:{code:java} Prefetching pkgutil resources for packageDebug: Executing: '/opt/csw/bin/pkgutil -a'Debug: Executing: '/opt/csw/bin/pkgutil -c'Debug: /Package[sudo]: Not scheduledDebug: /Package[sudo]: Resource is being skipped, unscheduling all eventsDebug: /Package[name]: Not scheduledDebug: /Package[name]: Resource is being skipped, unscheduling all events{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title Martin Ewings updated an issue Puppet / PUP-8636 Don't prefetch if every resource using a provider is noop'd or no scheduled Change By: Martin Ewings CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8636) Don't prefetch if every resource using a provider is noop'd or no scheduled
Title: Message Title
Martin Ewings created an issue
Puppet / PUP-8636
Don't prefetch if every resource using a provider is noop'd or no scheduled
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/04/06 7:16 AM
Priority:
Normal
Reporter:
Martin Ewings
When a Particular Resource provider is defaulting to No-op or is part of a schedule which is not active, Puppet shouldn't prefetch any data relating to that provider in order to speed up compilation, for example:
schedule { 'narrow':
range => '1:01 - 1:02',
}
Package <| provider == 'pkgutil' |> {
schedule => 'narrow',
