Jira (PDB-88) Remove JDK 1.6 Support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Kenneth Barber Assignee: Kenneth Barber Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-88) Remove JDK 1.6 Support
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-88) Remove JDK 1.6 Support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-88 Remove JDK 1.6 Support Change By: Kenneth Barber This ticket tracks the final removal of JDK 1.6 support.* Remove the funky cipher manipulation stuff in jetty.clj* Look for code that dispatches on jvm version, audit it* Remove testing against 1.6 (.travis.yml needs changing) * For older debian based distros, we could add the JavaPackage manually built package to the controlfile for those distros so people have an option (albeit a manual built package is a pain, but better then nothing), we need to test this however: https://gist.github.com/kbarber/7775906* For older debian/ubuntu distros as well, if we decide to use JavaPackage then we should modify our acceptance tests somehow to support this - at the moment if we make this change these acceptance tests will begin to fail. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-343) (packaging) Remove Fedora 18 from default build targets
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-343 (packaging) Remove Fedora 18 from default build targets Change By: Kenneth Barber Sprint: 20140212 to 20140219 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer Change By: Kenneth Barber Component/s: Module Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-343) (packaging) Remove Fedora 18 from default build targets
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-343 (packaging) Remove Fedora 18 from default build targets Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Change By: Kenneth Barber Sprint: 20140212 to 20140219 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer Change By: Kenneth Barber Sprint: 20140212 to 20140219 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-460) PR (119): Adding option to disable management of the firewall - nibalizer
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-460 PR (119): Adding option to disable management of the firewall - nibalizer Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-7) Move puppetdb acceptance testing to use vsphere
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-7 Move puppetdb acceptance testing to use vsphere Change By: Kenneth Barber The current ec2 acceptance testing is both prone to failure and complicated to set up. Moving the puppetdb acceptance tests to use the local vsphere infrastructure will allow the s3 repo steps to be removed from the pipeline, which will simplify the workflow and will allow for more stability in testing. Further to this: there is still some decisions to be made about the future of EC2/Vsphere, so until we understand where the company really wants to go, we're not sure what to do with this ticket. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-171) Provide documentation for how to debug a crashed or frozen JVM
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-171 Provide documentation for how to debug a crashed or frozen JVM Change By: Kenneth Barber Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-182) Document backup and restoration advice
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-182 Document backup and restoration advice Change By: Kenneth Barber Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-215) Improve API documentation and examples for submitting commands
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-215 Improve API documentation and examples for submitting commands Change By: Kenneth Barber Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-333) Catalog wire format docs state aliases are required for resources
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-333 Catalog wire format docs state aliases are required for resources Change By: Kenneth Barber Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-187) Add formal docs for the CLI tools
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-187 Add formal docs for the CLI tools Change By: Kenneth Barber Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-444) Convert to using dynamic postgres instances for unit tests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-444 Convert to using dynamic postgres instances for unit tests Change By: Kenneth Barber Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-380) /reports/hash
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-380 /reports/hash Change By: Kenneth Barber Summary: / repors reports /hash Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-198) storeconfigs error caused by unclear documentation
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-198 storeconfigs error caused by unclear documentation Change By: Kenneth Barber Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-271) Retire JDK 1.6. in docs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-271 Retire JDK 1.6. in docs Change By: Kenneth Barber Affects Version/s: 1.6.0 Fix Version/s: 1.6.x Fix Version/s: 2.0.x Summary: Deprecate Retire JDK 1.6. in docs Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-234) Create v4 API
Title: Message Title Kenneth Barber commented on an issue Re: Create v4 API Okay, the PR is ready to go again: https://github.com/puppetlabs/puppetdb/pull/848 Add Comment PuppetDB / PDB-234 Create v4 API This involves creating the new /v4 end-point ready for new features and major changes. We should probably consider publishing this as /v4-experimental or /experimental/v4 or something like that, so we have some room to modify v4 before we commit to it as stable. This all depends on timing of course, as we may find v4 is read when we ship. Other ideas: ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-308) Drop 2.7.x support for puppetdb-terminus
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-308 Drop 2.7.x support for puppetdb-terminus Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-343) (packaging) Remove Fedora 18 from default build targets
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-343 (packaging) Remove Fedora 18 from default build targets Change By: Kenneth Barber Fix Version/s: 1.5.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-459) PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-459 PR (857): The order of (keys m) and (vals m) is not guaranteed to be the same - senior Change By: Kenneth Barber Affects Version/s: 2.0.x Affects Version/s: 1.6.0 Affects Version/s: 1.6.2 Fix Version/s: 1.6.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PDB-462) HTTP/2.0
Title: Message Title Kenneth Barber commented on an issue Re: HTTP/2.0 Christopher Price has already been working to switch us to Jetty 9 which introduces SPDY v3 support at least, what work is required to enable that is another thing: https://github.com/puppetlabs/puppetdb/pull/826. Of course SPDY 3.1 is out now, which Jetty doesn't seem to support yet (at least I can't see anything indicated so in 9.0 or 9.1 release notes). So really, we're beholden to Jetty and when the standard comes out, and we'll have to jump on that version that supports it. But for now at least we have the potential to support some of the features with the SPDY v3 protocol. So probably what is more immediately valuable would be a ticket to enable SPDY support, since we can probably do that once that PR I mentioned gets merged in. Christopher Price have you had any thoughts in this direction yet? Add Comment PuppetDB / PDB-462 HTTP/2.0 As a spec for HTTP/2.0 is starting to slowly emerge and people are starting to experiment with it I think it's a good time to bring up this issue. I'm sure some investigation will have to be done and the libraries that are used will have to be updated to support HTTP/2.0. Even though it's still early days it there should at least be an issue about it. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-463) Assertion failure for v1 resource queries after upgrading to 1.6.x
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-463 Assertion failure for v1 resource queries after upgrading to 1.6.x Change By: Kenneth Barber Fix Version/s: 1.6.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-463) Assertion failure for v1 resource queries after upgrading to 1.6.x
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-463 Assertion failure for v1 resource queries after upgrading to 1.6.x Change By: Kenneth Barber Sprint: 20140212 to 20140219 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-463) Assertion failure for v1 resource queries after upgrading to 1.6.x
Title: Message Title Kenneth Barber commented on an issue Re: Assertion failure for v1 resource queries after upgrading to 1.6.x PR is here: https://github.com/puppetlabs/puppetdb/pull/860 Add Comment PuppetDB / PDB-463 Assertion failure for v1 resource queries after upgrading to 1.6.x We just upgraded to 1.6.2 from 1.5.0. Our v1 resource queries stopped working with the following exception: java.lang.AssertionError: Assert failed: (and (integer? limit) (>= limit 0)) at com.puppetlabs.puppetdb.http.v1.resources$produce_body.invoke(resources.clj:86) at com.puppetlabs.puppetdb.http.v1.resources$routes$fn__6411$fn__64... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-461) PR (858): Remove redmine links - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-461 PR (858): Remove redmine links - kbarber Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-461) PR (858): Remove redmine links - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-461 PR (858): Remove redmine links - kbarber Change By: Kenneth Barber Fix Version/s: 1.5.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-461) PR (858): Remove redmine links - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-461 PR (858): Remove redmine links - kbarber Change By: Kenneth Barber Sprint: 20140212 to 20140219 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-463) Assertion failure for v1 resource queries after upgrading to 1.6.x
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-463 Assertion failure for v1 resource queries after upgrading to 1.6.x Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-463) Assertion failure for v1 resource queries after upgrading to 1.6.x
Title: Message Title Kenneth Barber commented on an issue Re: Assertion failure for v1 resource queries after upgrading to 1.6.x Imri Zvik this is fixed now with my latest commit. Add Comment PuppetDB / PDB-463 Assertion failure for v1 resource queries after upgrading to 1.6.x We just upgraded to 1.6.2 from 1.5.0. Our v1 resource queries stopped working with the following exception: java.lang.AssertionError: Assert failed: (and (integer? limit) (>= limit 0)) at com.puppetlabs.puppetdb.http.v1.resources$produce_body.invoke(resources.clj:86) at com.puppetlabs.puppetdb.http.v1.resources$routes$fn__6411$fn__64... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-379) /nodes//reports
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-379 /nodes//reports Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-378) Empty query on reports results in http 500
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-378 Empty query on reports results in http 500 Change By: Kenneth Barber Story Points: 2 Assignee: Deepak Giridharagopal Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-239) After a change causing a service to not restart, it takes two puppet run for Puppetdb's events API to get the proper status
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-239 After a change causing a service to not restart, it takes two puppet run for Puppetdb's events API to get the proper status Change By: Kenneth Barber Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-220) Titles containing numbers returned from functions will throw exceptions during report storage
Title: Message Title
Kenneth Barber updated an issue
PuppetDB / PDB-220
Titles containing numbers returned from functions will throw exceptions during report storage
Change By:
Kenneth Barber
During some testing, I saw this error: {code} 2013-06-07 17:30:53,124 ERROR [command-proc-45] [puppetdb.command] [97b7fe3f-775e-4ced-833c-6a031758aa47] [store report] Fatal error on attempt 0java.lang.IllegalArgumentException: ResourceEvent key :resource-title should be String, got 1459 at com.puppetlabs.validation$validate_against_model_BANG_.invoke(validation.clj:82) at com.puppetlabs.puppetdb.report$validate_BANG_.invoke(report.clj:42) at com.puppetlabs.puppetdb.command$eval3849$fn__3852$fn__3855.invoke(command.clj:363) at com.puppetlabs.puppetdb.command$eval3849$fn__3852.invoke(command.clj:362) at clojure.lang.MultiFn.invoke(MultiFn.java:167) at com.puppetlabs.puppetdb.command$produce_message_handler$fn__3944.invoke(command.clj:582) at com.puppetlabs.puppetdb.command$wrap_with_discard$fn__3895$fn__3898.invoke(command.clj:490) at com.puppetlabs.puppetdb.command.proxy$java.lang.Object$Callable$f8c5758f.call(Unknown Source) at com.yammer.metrics.core.Timer.time(Timer.java:91) at com.puppetlabs.puppetdb.command$wrap_with_discard$fn__3895.invoke(command.clj:489) at com.puppetlabs.puppetdb.command$wrap_with_exception_handling$fn__3880$fn__3881.invoke(command.clj:443) at com.puppetlabs.puppetdb.command.proxy$java.lang.Object$Callable$f8c5758f.call(Unknown Source) at com.yammer.metrics.core.Timer.time(Timer.java:91) at com.puppetlabs.puppetdb.command$wrap_with_exception_handling$fn__3880.invoke(command.clj:442) at com.puppetlabs.puppetdb.command$wrap_with_command_parser$fn__3890.invoke(command.clj:465) at com.puppetlabs.puppetdb.command$wrap_with_meter$fn__3871.invoke(command.clj:403) at com.puppetlabs.puppetdb.command$wrap_with_thread_name$fn__3903.invoke(command.clj:505) at clamq.jms$jms_consumer$fn__3141.invoke(jms.clj:38) at clamq.jms.proxy$java.lang.Object$MessageListener$ce893c05.onMessage(Unknown Source) at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560) at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498) at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325) at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947) at java.lang.Thread.run(Thread.java:722) {code} I was using notify during a load test, the code to replicate is simple: {code} $a = range('1','2') notify { $a: } {code} Even confirmed in future pa
Jira (PDB-220) Titles containing numbers returned from functions will throw exceptions during report storage
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-220 Titles containing numbers returned from functions will throw exceptions during report storage Change By: Kenneth Barber Labels: redmine trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-220) Titles containing numbers returned from functions will throw exceptions during report storage
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-220 Titles containing numbers returned from functions will throw exceptions during report storage Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-232) Create database migration size estimates and fail with insufficient disk space
Title: Message Title Kenneth Barber commented on an issue Re: Create database migration size estimates and fail with insufficient disk space I think this is non-trivial, so marking it as an 8. More because I can't see an extremely clean/efficient way of doing this without some effort. Add Comment PuppetDB / PDB-232 Create database migration size estimates and fail with insufficient disk space Some of our database migrations can require significant changes to disk usage, such as copying the contents of a large table to a new table that has additional columns or other structural changes. It would be nice to have something that estimates the potential impact of an upgrade and ensure that the user meets those guidelines before performing the upgr... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For
Jira (PDB-232) Create database migration size estimates and fail with insufficient disk space
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-232 Create database migration size estimates and fail with insufficient disk space Change By: Kenneth Barber Story Points: 8 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404
Title: Message Title Kenneth Barber commented on an issue Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 Seems PDB-88 is blocking this also, Ryan Senior and delivery have been working on this. Sorry Christopher Price. Add Comment PuppetDB / PDB-401 PR (826): Port to trapperkeeper 0.3.0 - cprice404 h2. Port to trapperkeeper 0.3.0 * Author: Chris Price <> * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826] * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files] h2. Pull Request Description This commit updates PuppetD... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-330) Scope 2.0 epics Round 1 - Environments
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-330 Scope 2.0 epics Round 1 - Environments Change By: Kenneth Barber Summary: Scope 2.0 epics Round 1 - Environments Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-335) Scope 2.0 epics Round 2 - HA
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 - HA Change By: Kenneth Barber Summary: Scope 2.0 epics Round 2 - HA Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-466) Scope 2.0 Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 Round 3 - Reporting and Structured Facts Change By: Kenneth Barber Sprint: 20140305 to 20140312 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-466) Scope 2.0 Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-466 Scope 2.0 Round 3 - Reporting and Structured Facts Issue Type: Task Assignee: Unassigned Created: 19/Feb/14 8:19 AM Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-466) Scope 2.0 epics Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 epics Round 3 - Reporting and Structured Facts Change By: Kenneth Barber Summary: Scope 2.0 epics Round 3 - Reporting and Structured Facts Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-466) Scope 2.0 epics Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 epics Round 3 - Reporting and Structured Facts Change By: Kenneth Barber Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-335) Scope 2.0 epics Round 2 - HA
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 - HA Change By: Kenneth Barber Fix Version/s: 2.0.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-467) Merge versioning tests for http testing into non-versioned files
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-467 Merge versioning tests for http testing into non-versioned files Issue Type: Improvement Assignee: Unassigned Created: 19/Feb/14 8:42 AM Fix Versions: 1.6.x Priority: Normal Reporter: Kenneth Barber We have done some work in merging the testing between versioning into single files but there is still some cleanup work to go on remaining end-points. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-467) Merge versioning tests for http testing into non-versioned files
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-467 Merge versioning tests for http testing into non-versioned files Change By: Kenneth Barber Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-221) puppetdb-export/import doesn't contain node facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-221 puppetdb-export/import doesn't contain node facts Change By: Kenneth Barber It would be good if puppetdb-export & import contained the facts of the nodes as well as the catalog and reports. A change to anonymize will probably have to occur as well, unless we can see a way for skipping it for now. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-221) puppetdb-export/import doesn't contain node facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-221 puppetdb-export/import doesn't contain node facts Change By: Kenneth Barber Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-378) Empty query on reports results in http 500
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-378 Empty query on reports results in http 500 Change By: Kenneth Barber Labels: trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-111) Switch message publishing from Strings to bytes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-111 Switch message publishing from Strings to bytes Change By: Kenneth Barber Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-110) Switch PuppetDB to use streams from the incoming command requests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-110 Switch PuppetDB to use streams from the incoming command requests Change By: Kenneth Barber Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-130) Provide human-friendly message if the infile specified to import/anonymzie doesn't exist
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-130 Provide human-friendly message if the infile specified to import/anonymzie doesn't exist Change By: Kenneth Barber Story Points: 1 Affects Version/s: 1.5.0 Affects Version/s: 1.6.2 Labels: redmine trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-130) Provide human-friendly message if the infile specified to import/anonymzie doesn't exist
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-130 Provide human-friendly message if the infile specified to import/anonymzie doesn't exist Change By: Kenneth Barber Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-136) Support for Oracle backend
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-136 Support for Oracle backend Change By: Kenneth Barber Story Points: 30 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-466) Scope 2.0 epics Round 3 - Reporting and Structured Facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-466 Scope 2.0 epics Round 3 - Reporting and Structured Facts Change By: Kenneth Barber Spend time scoping and creating tickets for the epics 'Reporting' and 'Structured Facts'. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-465) Add Trusty (Ubuntu 14.04) Support
Title: Message Title Kenneth Barber commented on an issue Re: Add Trusty (Ubuntu 14.04) Support We'll need an Ubuntu 14.04 image for EC2 before this can be done. Melissa Stone, I presume this ticket tracks the packaging work, do we need another to track this image creation and acceptance test work? Add Comment PuppetDB / PDB-465 Add Trusty (Ubuntu 14.04) Support This involves adding/updating spen and acceptance tests for trusty, and making sure the build_defaults has been updated accordingly This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)
Title: Message Title Kenneth Barber commented on an issue Re: puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) I just noticed PDB-468 actually makes in-roads to fixing this very issue. We probably just need to add JAVA_ARGS to the command line call instead of the templated version once PDB-468 is merged. Add Comment PuppetDB / PDB-142 puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) A user on IRC reported that when running puppetdb-foreground, it fell back to the default heap size of 192M even though he'd configured the heap to 4G in the puppetdb system defaults. We should verify this, and see how hard it would be to make the script respect the user's settings--it's far less useful of a tool if it doesn't do that. :) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For mo
Jira (PDB-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-142 puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-142) puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-142 puppetdb-foreground doesn't respect defaults (e.g. JAVA_ARGS) Change By: Kenneth Barber Labels: redmine trivial Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-470 Investigate setStatementsCacheSize for performance Issue Type: Improvement Assignee: Unassigned Created: 20/Feb/14 6:53 PM Fix Versions: 2.0.x Labels: trivial Priority: Normal Reporter: Kenneth Barber It seems the setting setStatementsCacheSize for BoneCPConfig will enable prepared statements cache. This seems to have a great effect on our insert time, especially at high load. So far I've tested this 3 times and found that the number of seconds spent doing inserts is almost halved. The patch I was working with is here: --- a/src/com/puppetlabs/jdbc.clj +++ b/src/com/puppetlabs/jdbc.clj @@ -300,6 +300,7 @@ (defn make-connection-pool (.setStatisticsEnabled stats) (.setIdleMaxAgeInMinutes (pl-time/to-minutes conn-max-age)) (.setIdleConnectionTestPeriodInMinutes (pl-time/to-minutes conn-keep-alive + (.setStatementsCacheSize 1000) ;; paste the URL back together from parts. (.setJdbcUrl (str "jdbc:" subprotocol ":" subname))
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate setStatementsCacheSize for performance Change By: Kenneth Barber Attachment: Screen Shot 2014-02-21 at 02.44.58.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate setStatementsCacheSize for performance Change By: Kenneth Barber Attachment: Screen Shot 2014-02-21 at 02.45.07.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title
Kenneth Barber commented on an issue
Re: Investigate setStatementsCacheSize for performance
Find attached a couple of screenshots for before/after patch results. Like I said, I've tried this 3 times and found similar results each time, so I'm sure its not by accident.
This appears to be a simple facility that provides hashes lookups of previously prepared statements so they can be re-used. Without this, prepared statements are being prepared then destroyed after a single use. By using prepared statements we avoid a hard-parse in postgresql and with multiple use Postgresql can avoid plan calculation after a while once it considers a plan stable. So big performance benefits it would seem.
The alternative is to look at doing our own prepared statements.
Add Comment
PuppetDB / PDB-470
Investigate setStatementsCacheSize for performance
It seems the setting setStatementsCacheSize for BoneCPConfig will enable prepared statements cache. This seems to have a great effect on our insert time, especially at high load. So far I've tested this 3 times and found that the number of seconds spent doing inserts is almost halved. The patch I was working with is here: {code} --- a/src/com...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-470) Investigate setStatementsCacheSize for performance
Title: Message Title
Kenneth Barber updated an issue
PuppetDB / PDB-470
Investigate setStatementsCacheSize for performance
Change By:
Kenneth Barber
It seems the setting setStatementsCacheSize for BoneCPConfig will enable prepared statements cache.This seems to have a great effect on our insert time, especially at high load.So far I've tested this 3 times and found that the number of seconds spent doing inserts is almost halved.The proposal is to implement this setting as a user configurable item and set it to a reasonable default perhaps. We should confirm the numbers I've seen here first, and also do some more research on the feature to understand its side-effects. We might also want to consider just doing our own prepared statement handling and the value of that versus this approach, although this might be a good phase 1 regardless.The patch I was working with is here:{code}--- a/src/com/puppetlabs/jdbc.clj+++ b/src/com/puppetlabs/jdbc.clj@@ -300,6 +300,7 @@ (defn make-connection-pool (.setStatisticsEnabled stats) (.setIdleMaxAgeInMinutes (pl-time/to-minutes conn-max-age)) (.setIdleConnectionTestPeriodInMinutes (pl-time/to-minutes conn-keep-alive+ (.setStatementsCacheSize 1000) ;; paste the URL back together from parts. (.setJdbcUrl (str "jdbc:" subprotocol ":" subname)){code}My test code for submitting a random catalog is here:{code}#!/usr/bin/env rubyrequire 'rubygems'require 'net/http'require 'uri'require 'json'require 'pp'def replace_catalog(catalog) uri = URI.parse("http://localhost:8080/v3/commands") http = Net::HTTP.new(uri.host, uri.port) request = Net::HTTP::Post.new(uri.request_uri) request.set_form_data({ "payload" => {"command" => "replace catalog","version" => 3,"payload" => catalog.to_json, }.to_json} ) response = http.request(request) puts response.bodyenddef random_string (0...50).map { ('a'..'z').to_a[rand(26)] }.joinenddef random_resource {"type" => "Class","title" => random_string,"exported" => false,"file" => "asdf","line" => 3,"tags" => ["asdf"],"parameters" => {} }endpayload1 = { "metadata" => { "api_version" => 1 }, "data" => {"name" => "host-0","version" => "3","transaction-uuid" => "foo","edges" => [ {"source" => { "type" => "Class", "title" => "foo",},"target" => { "type" => "File", "title" => "foo",},"relationship" => "contains", },],"resources" => [ {"type" => "Class","title" => "foo","exported" => false,"file" => "asdf","line" => 3,"tags" => ["asdf"],"parameters" => {}, }, {"type" => "File","title" => "foo","exported" => false,"file" => "asdf","line" => 3,"tags" => ["asdf"],"parameters" => {}, },] }}1.times do payload1["data"]["resources"].push random_resourceend#pp payload1replace_catalog(payload1){code}
Jira (PDB-470) Investigate and implement setStatementsCacheSize for repetitive SQL performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate and implement setStatementsCacheSize for repetitive SQL performance Change By: Kenneth Barber Summary: Investigate and implement setStatementsCacheSize for repeat repetitive SQL performance Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate and implement setStatementsCacheSize for repeat SQL performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate and implement setStatementsCacheSize for repeat SQL performance Change By: Kenneth Barber Summary: Investigate and implement setStatementsCacheSize for repeat SQL performance Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-471) Reports with "status=failure" aren't stored in PuppetDB
Title: Message Title Kenneth Barber commented on an issue Re: Reports with "status=failure" aren't stored in PuppetDB Urban Kujo I can't reproduce it, you'll need to provide more exact instructions on how to reproduce this state, like I've shown above. Add Comment PuppetDB / PDB-471 Reports with "status=failure" aren't stored in PuppetDB Hi, First of all: I'm running the Puppetmaster and PuppetDB on 2 separate machines. I'm trying to get information about reports with "status=fail" with: curl -G 'http://prdlnx42.genua.de:8080/v3/events' --data-urlencode 'query=["=","status","failure"]' --> What I get is: [] --> 1) I intentionally triggered reports with "status=fail" 2) The report... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt
Jira (PDB-471) Reports with "status=failure" aren't stored in PuppetDB
Title: Message Title
Kenneth Barber commented on an issue
Re: Reports with "status=failure" aren't stored in PuppetDB
Actually, my mistake its not the same thing. Regardless I can't duplicate it:
# cat /etc/puppet/manifests/site.pp
service { "foobarbaz": ensure => stopped}
# puppet agent -t
Info: Retrieving plugin
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in /etc/puppet/modules/postgresql/lib/facter/postgres_default_version.rb
Info: Loading facts in /etc/puppet/modules/concat/lib/facter/concat_basedir.rb
Info: Loading facts in /etc/puppet/modules/firewall/lib/facter/ip6tables_version.rb
Info: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables_version.rb
Info: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/postgres_default_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Caching catalog for puppetdb1.vm
Info: Applying configuration version '1393254884'
Error: /Stage[main]/Main/Service[foobarbaz]: Could not evaluate: Could not find init script for 'foobarbaz'
Notice: Finished catalog run in 11.65 seconds
From daemon.log:
Feb 24 15:15:47 puppetdb1 puppet-agent[55165]: Retrieving plugin
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/postgresql/lib/facter/postgres_default_version.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/concat/lib/facter/concat_basedir.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/firewall/lib/facter/ip6tables_version.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables_version.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /etc/puppet/modules/firewall/lib/facter/iptables_persistent_version.rb
Feb 24 15:15:48 puppetdb1 puppet-agent[55165]: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
Feb 24 15:15:48 puppetdb1 puppet-a
Jira (PDB-472) For commands submission, avoid unpacking and repacking JSON just to add annotations
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-472 For commands submission, avoid unpacking and repacking JSON just to add annotations Issue Type: Improvement Assignee: Unassigned Created: 24/Feb/14 8:13 AM Priority: Normal Reporter: Kenneth Barber We should try to avoid the extra unpacking/packaging we do at a JSON level during commands submission. If you take a look at enqueue-raw-command! https://github.com/puppetlabs/puppetdb/blob/master/src/com/puppetlabs/puppetdb/command.clj#L235-L256 you can see that we are only unpacking to add these annotations. A better method would be to do one of two things: Figure out if we can attach metadata to the message itself. There is an attributes field in clamq publish that might do the trick: https://github.com/sbtourist/clamq#message-producers ... but generally JMS messages should support the concept of headers with application specific metadata, so if we can store it with the message but not in the body that would be perfect. Perhaps we can just wrap the command itself inside another JSON document, avoiding the need for unwrapping the command until its received by the command processing thread. This should also go hand-in-hand for future support for streaming to MQ (not possible with ActiveMQ today it seems) if we choose to do that later on.
Jira (PDB-473) Investigate and implement raw JSON submissions to commands end-point
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-473 Investigate and implement raw JSON submissions to commands end-point Issue Type: Improvement Assignee: Unassigned Created: 24/Feb/14 8:21 AM Priority: Normal Reporter: Kenneth Barber During some recent investigations I've found that during large catalog submissions the amount of time spent doing url encoding is quite prohibitive. Not to mention that extra string that is kept is just translated to another format and discarded. We can avoid this whole problem but simple accepting raw JSON submissions. This will allow us to avoid this encoding on the terminus side (less memory/CPU) and also avoid the decoding on the server side. The old format should still probably be supported, and we could probably use this work to lead us into other encoding formats in the future (like msgpack). The terminus code should also be modified to support raw JSON submission also if possible. The main gotcha is around the 'checksum' field, but we can probably keep that as a URL parameter during submission, or look into turning that into a header instead. Add Comment
Jira (PDB-473) Investigate and implement raw JSON submissions to commands end-point
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-473 Investigate and implement raw JSON submissions to commands end-point Attached file shows a sample CPU profiling with a 100k resource catalog being submitted. It shows the url decoding to be very heavy, although we should run more tests to prove these finds are true. Regardless, the amount of RAM used for the translation is wasteful and unnecessary with the option to use JSON raw submissions instead. Change By: Kenneth Barber Attachment: Screen Shot 2014-02-21 at 18.26.51.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-111) Switch message publishing from Strings to bytes
Title: Message Title Kenneth Barber commented on an issue Re: Switch message publishing from Strings to bytes Linking to PDB-472 and PDB-473 which are issues and improvements I've found during investigating this original issue. Add Comment PuppetDB / PDB-111 Switch message publishing from Strings to bytes Currently the command is written to a string (via chesthire) then published via clamq. In clamq/Spring, that message is then converted from a string into bytes and published to the MQ. We could save on some memory if instead we used cheshire to serialize to bytes and give that to clamq. The API seems to support passing bytes directly. Even better wou... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-19) Stream POST body of commands directly to ActiveMQ
Title: Message Title Kenneth Barber commented on an issue Re: Stream POST body of commands directly to ActiveMQ I've been quickly researching this over the last few days as its mildly related to the PDB-111 work. I can't see a way to stream into ActiveMQ today, it looks like its support for streaming is deprecated. https://activemq.apache.org/jms-streams.html HornetQ on the other hand does support JMS message streaming, it does this by streaming its input directly into a file before processing using FileOuputStream/FileInputStream which means the entire message is never stored in RAM until it gets processed by the consumer. Of course I'm not saying HornetQ is the only thing that does this, my point is mainly around ActiveMQ's limitations in this arena. Other technology should be researched. Add Comment PuppetDB / PDB-19 Stream POST body of commands directly to ActiveMQ In the current implementation of our command processor, when we receive a command request, we (via the ring 'wrap-params' middleware) slurp the entire POST body into a string, JSON deserialize it into an in-memory data structure, add one or two tiny bits of data to it, reserialize it to a string, and then write that out to ActiveMQ. In the case where w... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-472) For commands submission, avoid unpacking and repacking JSON just to add annotations
Title: Message Title Kenneth Barber commented on an issue Re: For commands submission, avoid unpacking and repacking JSON just to add annotations This effort kind of duplicates PDB-110, at least if one is implemented the other is no longer necessary. PDB-110 talks about decoding the JSON in a stream, and re-encoding it. Whereas this ticket (PDB-472) is all about somehow removing the need for the decoding/encoding completely. Add Comment PuppetDB / PDB-472 For commands submission, avoid unpacking and repacking JSON just to add annotations We should try to avoid the extra unpacking/packaging we do at a JSON level during commands submission. If you take a look at enqueue-raw-command! https://github.com/puppetlabs/puppetdb/blob/master/src/com/puppetlabs/puppetdb/command.clj#L235-L256 you can see that we are only unpacking to add these annotations. A better method would be to do one of t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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, se
Jira (PDB-471) Reports with "status=failure" aren't stored in PuppetDB
Title: Message Title Kenneth Barber commented on an issue Re: Reports with "status=failure" aren't stored in PuppetDB Urban Kujo this smells like PUP-1524 . Can you upgrade your puppet master to 3.4.3 and try again? Add Comment PuppetDB / PDB-471 Reports with "status=failure" aren't stored in PuppetDB Hi, First of all: I'm running the Puppetmaster and PuppetDB on 2 separate machines. I'm trying to get information about reports with "status=fail" with: curl -G 'http://prdlnx42.genua.de:8080/v3/events' --data-urlencode 'query=["=","status","failure"]' --> What I get is: [] --> 1) I intentionally triggered reports with "status=fail" 2) The report... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 htt
Jira (PDB-474) PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-474 PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-474) PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-474 PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber Change By: Kenneth Barber Sprint: 20140219 to 20140226 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-474) PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-474 PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber Change By: Kenneth Barber Fix Version/s: 2.0.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-474) PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-474 PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber Change By: Kenneth Barber Affects Version/s: 2.0.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-474) PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-474 PR (868): Fix puppetdb-env.erb so we don't get stripped carriage returns - kbarber Change By: Kenneth Barber Fix Version/s: 2.0.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-354) Deprecate old versions of the command API
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-354 Deprecate old versions of the command API Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-354) Deprecate old versions of the command API
Title: Message Title Kenneth Barber commented on an issue Re: Deprecate old versions of the command API PR is here: https://github.com/puppetlabs/puppetdb/pull/869 Add Comment PuppetDB / PDB-354 Deprecate old versions of the command API We currently support 3 versions of the replace-catalog command and 2 versions of the store report command. We should be able to deprecate the older command versions for 2.0.0 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-475) PR (122): Use $is_pe for PE determination - reidmv
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-475 PR (122): Use $is_pe for PE determination - reidmv Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-113) Remove swank
Title: Message Title Kenneth Barber commented on an issue Re: Remove swank PR is here: https://github.com/puppetlabs/puppetdb/pull/870 Add Comment PuppetDB / PDB-113 Remove swank Deprecate swank in favour of nrepl. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-475) PR (122): Use $is_pe for PE determination - reidmv
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-475 PR (122): Use $is_pe for PE determination - reidmv Change By: Kenneth Barber Sprint: 20140219 to 20140226 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-476) Convert the terminus performance logging one-off support solution to something permanent
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-476 Convert the terminus performance logging one-off support solution to something permanent Change By: Kenneth Barber Summary: Convert the terminus performance logging one-off support solution to something permanent Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-473) Investigate and implement raw JSON submissions to commands end-point
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-473 Investigate and implement raw JSON submissions to commands end-point Change By: Kenneth Barber Sprint: 20140305 to 20140312 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-470) Investigate and implement setStatementsCacheSize for repetitive SQL performance
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-470 Investigate and implement setStatementsCacheSize for repetitive SQL performance Change By: Kenneth Barber Sprint: 20140305 to 20140312 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-472) For commands submission, avoid unpacking and repacking JSON just to add annotations
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-472 For commands submission, avoid unpacking and repacking JSON just to add annotations Change By: Kenneth Barber Sprint: 20140305 to 20140312 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-402) Disable AOT compiling of PuppetDB code
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-402 Disable AOT compiling of PuppetDB code Change By: Kenneth Barber Fix Version/s: 2.0.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-336) Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-336 Investigage - PuppetDB won't start: OutOfMemoryError: Java heap space Change By: Kenneth Barber Fix Version/s: 2.0.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-402) Disable AOT compiling of PuppetDB code
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-402 Disable AOT compiling of PuppetDB code Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-402) Disable AOT compiling of PuppetDB code
Title: Message Title Kenneth Barber commented on an issue Re: Disable AOT compiling of PuppetDB code PR is here: https://github.com/puppetlabs/puppetdb/pull/871 Add Comment PuppetDB / PDB-402 Disable AOT compiling of PuppetDB code We currently need to use AOT to support "java -jar .. services..." form of execution. We can instead switch to "java -cp ... clojure.main -m services ..." which does not require AOT compiling and removes the need to do any AOT compiling of PuppetDB code. This would have saved us a lot of headaches. The steps needed to do this are below: - Change scri... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-476) Convert the terminus performance logging one-off support solution to something permanent
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-476 Convert the terminus performance logging one-off support solution to something permanent Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1772) Proposal to un-private Puppet::Util::Profiler#profile
Title: Message Title Kenneth Barber created an issue Puppet / PUP-1772 Proposal to un-private Puppet::Util::Profiler#profile Issue Type: Task Assignee: Unassigned Created: 26/Feb/14 11:29 AM Priority: Normal Reporter: Kenneth Barber The current profile method: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/profiler.rb#L30-L32 Would be perfect for PuppetDB terminus to use to solve any profiling issues internally. We've had some bugs raised on this in the past but it would be great to be able to produce profiling information in the same fashion that Puppet does. This will mean that users seeing any performance issues on their master will see the terminus profiling right alongside it. It also means we don't need to reinvent the wheel in terminus to do this action. Right now I only see the method #profile as needing to be exposed, the others can probably happily stay private. I'm going to provide a patch as well today, and I'll attach the URL for a PR to this ticket very shortly. Add Comment
