Is Puppet Labs saying they are ending support of MySQL and instead will
only support PostgreSQL? That is going to be a big problems for shops
that do not support PostgresSQL, or are only allowed to run DB systems
on an approved list. Why wouldn't a DB-agnostic model be used?
Right now, I can say that due to these types of issues, I cannot even
evaluate PuppetDB, and will not be able to for the foreseeable future.
Also, does this mean that the existing inventory service and store
configs functionality goes away?
On Mon May 21 07:11:07 2012, Erik Dalén wrote:
On 19 May 2012 01:44, Deepak Giridharagopal <[email protected]> wrote:
On Fri, May 18, 2012 at 7:48 AM, Philip Brown <[email protected]> wrote:
On Friday, May 18, 2012 7:21:26 AM UTC-7, Michael Stanhke wrote:
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:
...
As this is the first public release, the version is 0.9.0 (a.k.a. “open
beta”).
While we’ve been using PuppetDB internally at Puppet Labs for months
without
incident, we encourage you to try it out, hammer it with data, and let us
know
if you run into any issues! A 1.0 release will come after a few cycles of
bug
squashing.
Sounds interesting. I have a question about integration;
How does this interact or integrate with puppet dashboard?
Is this an "either one or the other" sort of thing? Or do they play nicely
together? or do they actually do completely different things?
Dashboard uses the inventory service API to do its queries for things like
nodes and facts. As luck would have it, PuppetDB's terminuses implement that
same API. If you configure your Puppetmaster so that PuppetDB handles
inventory service queries (this is covered in the installation docs), and
point Dashboard at your Puppetmaster, things will Just Work.
PuppetDB doesn't (yet) do report storage, so that will continue to work
inside of Dashboard as it always has.
Do you plan on merging it so that the inventory service node queries
can use classes and parameters in the search queries?
I know this is already possible using foreman.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
