PuppetDB 1.0 is now available!
PuppetDB, a component of the Puppet Data Library, is a centralized storage
daemon for auto-generated data. This initial release of PuppetDB targets the
storage of catalogs and facts.
Much more information is available on the Puppet Labs blog:
http://puppetlabs.com/blog/introducing-puppetdb-put-your-data-to-work/
...and on the docs site:
http://docs.puppetlabs.com/puppetdb/1/
...and there will also be 2 talks involving PuppetDB at next week''s
PuppetConf.
What can it do for you?
* It’s a drop-in, 100% compatible replacement for storeconfigs
* It’s a drop-in, 100% compatible replacement for inventory service
* It''s already in production at many sites, handling thousands of
nodes and
millions of resources
* It hooks into your Puppet infrastructure using Puppet’s pre-existing
extension points (catalog/facts/resource/node terminuses)
* It’s much faster, much more space-efficient, and much more scalable
than current storeconfigs and the current inventory service.
* We can handle a few thousand nodes, with several hundred
resources each, with a 30m runinterval on our laptops during
development.
* It stores the entire catalog, including all dependency and
containment information
* It exposes well-defined, HTTP-based methods for accessing stored information
* Documented at http://docs.puppetlabs.com/puppetdb
* It presents a superset of the storeconfigs and inventory service
APIs for use in scripts or by other tools
* In particular, we support arbitrarily nested boolean operators
* It decouples catalog and fact storage from the compilation process
* PuppetDB obsoletes previous puppetq functionality
* It works Very Hard to store everything you send it; we auto-retry
all storage requests, persist storage requests across restarts,
and preserve full traces of all failed requests for post-mortem analysis
* It’s secured using Puppet’s built-in SSL infrastructure
* It’s heavily instrumented and easy to integrate its performance info into
your monitoring frameworks
We encourage you to try it out, hammer it with data, and let us know
if you run into any issues!
# Downloads
Available in native package format at
http://yum.puppetlabs.com
http://apt.puppetlabs.com
Source (same license as Puppet): http://github.com/puppetlabs/puppetdb
Available for use with Puppet Enterprise 2.5.1 and later at
http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/
Puppet module (Puppet Enterprise support is forthcoming):
http://forge.puppetlabs.com/puppetlabs/puppetdb
# Documentation (including how to install): http://docs.puppetlabs.com/puppetdb
# Issues can be filed at:
http://projects.puppetlabs.com/projects/puppetdb/issues
# See our development board on Trello:
http://links.puppetlabs.com/puppetdb-trello
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Erik Dalén
2012-Sep-21 05:44 UTC
[Puppet Users] Re: [Puppet-dev] Announce: PuppetDB 1.0 Available
Great work! But what are the changes since 0.11.0? It would also be interesting to see a roadmap of post 1.0 features that are planned. On 21 September 2012 02:03, Moses Mendoza <moses@puppetlabs.com> wrote:> PuppetDB 1.0 is now available! > > PuppetDB, a component of the Puppet Data Library, is a centralized storage > daemon for auto-generated data. This initial release of PuppetDB targets the > storage of catalogs and facts. > > Much more information is available on the Puppet Labs blog: > > http://puppetlabs.com/blog/introducing-puppetdb-put-your-data-to-work/ > > ...and on the docs site: > > http://docs.puppetlabs.com/puppetdb/1/ > > ...and there will also be 2 talks involving PuppetDB at next week''s PuppetConf. > > What can it do for you? > > * It’s a drop-in, 100% compatible replacement for storeconfigs > * It’s a drop-in, 100% compatible replacement for inventory service > * It''s already in production at many sites, handling thousands of nodes and > millions of resources > * It hooks into your Puppet infrastructure using Puppet’s pre-existing > extension points (catalog/facts/resource/node terminuses) > * It’s much faster, much more space-efficient, and much more scalable > than current storeconfigs and the current inventory service. > * We can handle a few thousand nodes, with several hundred > resources each, with a 30m runinterval on our laptops during > development. > * It stores the entire catalog, including all dependency and > containment information > * It exposes well-defined, HTTP-based methods for accessing stored information > * Documented at http://docs.puppetlabs.com/puppetdb > * It presents a superset of the storeconfigs and inventory service > APIs for use in scripts or by other tools > * In particular, we support arbitrarily nested boolean operators > * It decouples catalog and fact storage from the compilation process > * PuppetDB obsoletes previous puppetq functionality > * It works Very Hard to store everything you send it; we auto-retry > all storage requests, persist storage requests across restarts, > and preserve full traces of all failed requests for post-mortem analysis > * It’s secured using Puppet’s built-in SSL infrastructure > * It’s heavily instrumented and easy to integrate its performance info into > your monitoring frameworks > > We encourage you to try it out, hammer it with data, and let us know > if you run into any issues! > > # Downloads > > Available in native package format at > > http://yum.puppetlabs.com > > http://apt.puppetlabs.com > > Source (same license as Puppet): http://github.com/puppetlabs/puppetdb > > Available for use with Puppet Enterprise 2.5.1 and later at > > http://yum-enterprise.puppetlabs.com/ and http://apt-enterprise.puppetlabs.com/ > > Puppet module (Puppet Enterprise support is forthcoming): > > http://forge.puppetlabs.com/puppetlabs/puppetdb > > # Documentation (including how to install): http://docs.puppetlabs.com/puppetdb > > # Issues can be filed at: > http://projects.puppetlabs.com/projects/puppetdb/issues > > # See our development board on Trello: > http://links.puppetlabs.com/puppetdb-trello > > -- > You received this message because you are subscribed to the Google Groups "Puppet Developers" group. > To post to this group, send email to puppet-dev@googlegroups.com. > To unsubscribe from this group, send email to puppet-dev+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en. >-- Erik Dalén -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Nick Lewis
2012-Sep-21 09:38 UTC
[Puppet Users] Re: [Puppet-dev] Announce: PuppetDB 1.0 Available
On Thursday, September 20, 2012 10:44:34 PM UTC-7, Erik Dalén wrote:> > Great work! > > But what are the changes since 0.11.0? > >We''ve been treating our releases until now as betas/release candidates, so actually 1.0 is just a promotion of 0.11.0. It''s identical in features. I guess we didn''t really make that clear. The main reasons for this release are to formalize the API and to send the message that it''s ready for general production use.> It would also be interesting to see a roadmap of post 1.0 features > that are planned. >We''re looking for ways to be more transparent about development. To that end, we recently opened our development board on Trello to the public: http://links.puppetlabs.com/puppetdb-trello Caveats are that those are mostly low-level tasks, rather than a general high-level overview, and the backlog is largely unprioritized. But until we have something better, that at least shows what we''re working on at any given time. Anyone is free and encouraged to comment and/or vote on cards. And if you''re looking to get involved with development, it''s a good place to start. In lieu of a formal roadmap, I can tell you that the general plan for the next few months includes better fact queries, report storage, possibly historical catalog storage, and what we''re calling Grand Unified Query (queries for any kind of data based on every other kind of data). And, as always, making the whole thing even faster and more space-efficient. Of course, having said that, I can''t promise the plan won''t change wildly at any moment. :) If you have any ideas about how we can better communicate this information, or other information you''d like available, I''d love to hear them. Nick Lewis> > On 21 September 2012 02:03, Moses Mendoza <mo...@puppetlabs.com<javascript:>> > wrote: > > PuppetDB 1.0 is now available! > > > > PuppetDB, a component of the Puppet Data Library, is a centralized > storage > > daemon for auto-generated data. This initial release of PuppetDB targets > the > > storage of catalogs and facts. > > > > Much more information is available on the Puppet Labs blog: > > > > http://puppetlabs.com/blog/introducing-puppetdb-put-your-data-to-work/ > > > > ...and on the docs site: > > > > http://docs.puppetlabs.com/puppetdb/1/ > > > > ...and there will also be 2 talks involving PuppetDB at next week''s > PuppetConf. > > > > What can it do for you? > > > > * It’s a drop-in, 100% compatible replacement for storeconfigs > > * It’s a drop-in, 100% compatible replacement for inventory service > > * It''s already in production at many sites, handling thousands of nodes > and > > millions of resources > > * It hooks into your Puppet infrastructure using Puppet’s pre-existing > > extension points (catalog/facts/resource/node terminuses) > > * It’s much faster, much more space-efficient, and much more scalable > > than current storeconfigs and the current inventory service. > > * We can handle a few thousand nodes, with several hundred > > resources each, with a 30m runinterval on our laptops during > > development. > > * It stores the entire catalog, including all dependency and > > containment information > > * It exposes well-defined, HTTP-based methods for accessing stored > information > > * Documented at http://docs.puppetlabs.com/puppetdb > > * It presents a superset of the storeconfigs and inventory service > > APIs for use in scripts or by other tools > > * In particular, we support arbitrarily nested boolean operators > > * It decouples catalog and fact storage from the compilation process > > * PuppetDB obsoletes previous puppetq functionality > > * It works Very Hard to store everything you send it; we auto-retry > > all storage requests, persist storage requests across restarts, > > and preserve full traces of all failed requests for post-mortem > analysis > > * It’s secured using Puppet’s built-in SSL infrastructure > > * It’s heavily instrumented and easy to integrate its performance info > into > > your monitoring frameworks > > > > We encourage you to try it out, hammer it with data, and let us know > > if you run into any issues! > > > > # Downloads > > > > Available in native package format at > > > > http://yum.puppetlabs.com > > > > http://apt.puppetlabs.com > > > > Source (same license as Puppet): http://github.com/puppetlabs/puppetdb > > > > Available for use with Puppet Enterprise 2.5.1 and later at > > > > http://yum-enterprise.puppetlabs.com/ and > http://apt-enterprise.puppetlabs.com/ > > > > Puppet module (Puppet Enterprise support is forthcoming): > > > > http://forge.puppetlabs.com/puppetlabs/puppetdb > > > > # Documentation (including how to install): > http://docs.puppetlabs.com/puppetdb > > > > # Issues can be filed at: > > http://projects.puppetlabs.com/projects/puppetdb/issues > > > > # See our development board on Trello: > > http://links.puppetlabs.com/puppetdb-trello > > > > -- > > You received this message because you are subscribed to the Google > Groups "Puppet Developers" group. > > To post to this group, send email to puppe...@googlegroups.com<javascript:>. > > > To unsubscribe from this group, send email to > puppet-dev+...@googlegroups.com <javascript:>. > > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. > > > > > > -- > Erik Dalén >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/lZ04UpCYCwEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.