Jira (BOLT-398) Lookup/Hiera spike
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-398 Lookup/Hiera spike Change By: David Kramer Sprint: Bolt Ready for Grooming 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 (BOLT-398) Lookup/Hiera spike
Title: Message Title Henrik Lindberg commented on BOLT-398 Re: Lookup/Hiera spike Yes - there is no cache invalidation/eviction except if the input used to form the hierarchy changed. For regular compiles the "change" is really if a variable goes from non existing to being assigned since all variables are immutable. 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 (BOLT-398) Lookup/Hiera spike
Title: Message Title Alex Dreyer commented on BOLT-398 Re: Lookup/Hiera spike Henrik Lindberg I'm guessing there is no invalidation of that cache since a catalog compile is in essence an atomic operation from a snapshot while during a plan the state of a node is likely to meaningfully change. 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 (BOLT-398) Lookup/Hiera spike
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-398 Lookup/Hiera spike Change By: Alex Dreyer I want to connect to a node based on configuration without knowing about the node in inventory a priori. Accept arbitrary targets, look up facts from puppetdb/discovery for them. use lookup to determine connection information based on the facts before connecting.I have a task with 'configuration params' for example ha-proxy socket location that may vary between nodes. I want to look up these parameters from hiera and pass them to run_task for a single target.We should explore how feasible it is use hiera for this by writing a function that can lookup a value in the context of a targets vars and facts and an arbiratry hiera.yaml file- How long does it take to loop over 200 with a more or less full complement of facter facts.- How much memory does it take to store a puppet scope an instance of the hierarchy for each target- What if any pal/lookup functions would make this easier. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-398) Lookup/Hiera spike
Title: Message Title Henrik Lindberg commented on BOLT-398 Re: Lookup/Hiera spike It is important to consider that hiera5 uses caching to be performant - if variables used in the hiera.conf changes so that the input to a function changes (for example an interpolation into a path that is given to it) the cache will be invalidated. Thus, if execution of plan logic iterates over target nodes and looks things up then each node switch will incur the cost of an invalidated cache. I suspect that it is not possible to ensure that all lookups for one target node are done before doing them for another node. That suggests that it would be best if it was possible to have multiple instances of "the hierarchy"; one per target node, and that it is fast to switch between them. We did some work on making it possible to have disjunct configurations, but not sure how suitable that API is for one separate instance per node. It is difficult to speculate what the worst case performance scenario cost - probably need to set up and measure - as it depends greatly on the volume of data and repetition of key lookup. 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 (BOLT-398) Lookup/Hiera spike
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-398 Lookup/Hiera spike Issue Type: Task Assignee: Unassigned Created: 2018/03/20 9:00 AM Priority: Normal Reporter: Alex Dreyer I want to connect to a node based on configuration without knowing about the node in inventory a priori. Accept arbitrary targets, look up facts from puppetdb/discovery for them. use lookup to determine connection information based on the facts before connecting. I have a task with 'configuration params' for example ha-proxy socket location that may vary between nodes. I want to look up these parameters from hiera and pass them to run_task for a single target. We should explore how feasible it is use hiera for this by writing a function that can lookup a value in the context of a targets vars and facts and an arbiratry hiera.yaml file How long does it take to loop over 200 with a more or less full complement of facter facts. How much memory does it take to store a puppet scope for each target What if any pal/lookup functions would make this easier. Add Comment
