PuppetDB 1.3.0 is now available for download! This is a backward compatible feature release of PuppetDB. ============## Downloads ## ============ Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb/1.<http://docs.puppetlabs.com/puppetdb/1.2> 3 # Issues can be filed at: http://projects.puppetlabs.com/projects/puppetdb/issues # See our development board on Trello: http://links.puppetlabs.com/puppetdb-trello ===========================## PuppetDB 1.3.0 Release Notes ## =========================== Many thanks to following people who contributed patches to this release: * Branan Purvine-Riley * Chris Price * Deepak Giridharagopal * Ken Barber * Matthaus Owens * Moses Mendoza * Nick Fagerlund * Nick Lewis Notable features: * Report queries The query endpoint `experimental/event` has been augmented to support a much more interesting set of queries against report data. You can now query for events by status (e.g. `success`, `failed`, `noop`), timestamp ranges, resource types/titles/property name, etc. This should make the report storage feature of PuppetDB *much* more valuable! * Import/export of PuppetDB reports PuppetDB 1.2 added the command-line tools `puppetdb-export` and `puppetdb-import`, which are useful for migrating catalog data between PuppetDB databases or instances. In PuppetDB 1.3, these tools now support importing and exporting report data in addition to catalog data. Bug fixes: * `puppetdb-ssl-setup` is now smarter about not overwriting keystore settings in `jetty.ini` during upgrades * Add database index to `status` field for events to improve query performance * Fix `telnet` protocol support for embedded nrepl * Upgrade to newer version of nrepl * Improvements to developer experience (remove dependency on `rake` for building/running clojure code) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Tuesday 7 May 2013 at 01:44, Chris Price wrote:> * Report queries > > The query endpoint `experimental/event` has been augmented to support a > much more interesting set of queries against report data. You can now query > for events by status (e.g. `success`, `failed`, `noop`), timestamp ranges, > resource types/titles/property name, etc. This should make the report > storage feature of PuppetDB *much* more valuable!Very nice news. But is this planned to get some further extensions? Some queries I would like to make still seem quite hard (at least to do in a single query). For example finding all nodes that failed their last puppet run seems like it would need one node query and then a event query for each one. Will there be better support for subqueries across reports, events and the other endpoints? That would make some types of queries easier. For example you could make a single query to get the puppet version of all nodes that failed any resource within the last 30 mins. Any suggestions for nifty syntax for puppetdbquery to query stuff like that? :) -- Erik Dalén -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Wednesday, May 8, 2013 5:31:16 AM UTC-7, Erik Dalén wrote:> On Tuesday 7 May 2013 at 01:44, Chris Price wrote: > > * Report queries > > > > The query endpoint `experimental/event` has been augmented to support a > > > much more interesting set of queries against report data. You can now > query > > for events by status (e.g. `success`, `failed`, `noop`), timestamp > ranges, > > resource types/titles/property name, etc. This should make the report > > storage feature of PuppetDB *much* more valuable! > > Very nice news. > > But is this planned to get some further extensions? Some queries I would > like to make still seem quite hard (at least to do in a single query). > > For example finding all nodes that failed their last puppet run seems like > it would need one node query and then a event query for each one. > > Will there be better support for subqueries across reports, events and the > other endpoints? That would make some types of queries easier. For example > you could make a single query to get the puppet version of all nodes that > failed any resource within the last 30 mins. > >This is definitely unfinished (it''s under /experimental). We plan to at least add subqueries like you get with resources/facts, and possibly counting, grouping, and selecting a subset of columns. If you have any further use cases that those features still wouldn''t address, let us know. We want to make this API as robust as we can; until we do, we thought it was best to get what we already had out for users to try.> Any suggestions for nifty syntax for puppetdbquery to query stuff like > that? :) > >I''ll.... get back to you on that. :)> -- > Erik Dalén > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
On Wednesday, May 8, 2013 5:31:16 AM UTC-7, Erik Dalén wrote:> > For example finding all nodes that failed their last puppet run seems like > it would need one node query and then a event query for each one.I''m guessing "last run" is something we''ll bake into the query API at some point too. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.