similar to: Announce: PuppetDB 1.0.1 Available

PuppetDB 1.1.1 is now available for download! This is a bug-fix release of PuppetDB. For details on the new features in PuppetDB 1.1.x, check out the blog post at https://puppetlabs.com/blog/announcing-puppetdb-1-1-do-more-with-your-data/ ================= ### Downloads ### ================= Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com

PuppetDB 0.11.0 is the fifth beta release on the road to 1.0. Changes include new features and bug fixes. For details on changes in this release, please see the release notes below. Please note that upgrading may take longer than in previous releases, due to new indices being added to the database. In our upgrades with large datasets (~2300 nodes, 900k resources) we didn''t see upgrade

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

PuppetDB 1.1.0-rc4 is now available for download! This is a feature and bug-fix release candidate of PuppetDB. Note: Release candidates 1-3 were never pushed to repositories due issues in packaging that were discovered prior to release. RC-4 is the first packaged release candidate for PuppetDB 1.1.0. # Downloads ============== Available in native package format in the pre-release repositories

PuppetDB 0.9.2 is the third beta release on the road to 1.0. Changes include new features and bug fixes. For details on changes in this release, please see the release notes below. # 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

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

trying to deploy puppetdb , puppet server is RHEL 6.1 , [root@puppet ~]# rpm -qa|grep puppet puppetdb-0.9.1-2.el6.noarch puppet-dashboard-1.2.9-1.el6.noarch puppet-server-2.7.17-1.el6.noarch puppetdb-terminus-0.9.1-2.el6.noarch puppet-2.7.17-1.el6.noarch on the clients, got an error for puppetdb , client1 :~ # puppet agent --test err: Could not retrieve catalog from remote server: Error 400

I could use some help debugging a bazaar PuppetDB problem. Exported resources seem to be working fine everywhere except for on the Puppet Masters themselves. Whenever I run the puppet agent on them everything seems to go fine and I see the catalog getting submitted to PuppetDB in the logs. However, when I run puppet on the node that should collect these resources they aren''t

Dear all, I have this setup on Ubuntu 12.04 and using puppetmaster/puppet 2.7.14 and puppetdb/puppetdb-terminus 0.9.0 from puppetlabs. My puppetmaster also run puppetdb. I also use hiera in this setup. hadoop4 is puppetmaster and hadoop02 is puppet client. puppet node status hadoop4.west.net hadoop4.west.net Currently active Last catalog: 2012-06-05T23:23:33.159Z Last facts:

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: * It’s a drop-in, 100% compatible replacement for storeconfigs * It’s a drop-in, 100% compatible replacement for inventory service * It hooks into your Puppet infrastructure using Puppet’s pre-existing

I just installed PE, and notice that it does not use either stored config nor puppetdb. It uses the activerecord to store facts in a mysql db. Why puppetlabs let us to use these but they do not use them in their enterprise version? Thanks. Hai T. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

A new release of the puppetlabs/puppetdb module is now available on the Forge: https://forge.puppetlabs.com/puppetlabs/puppetdb/1.3.0 This feature release provides us with a few new features for the PuppetDB module. You can now disable SSL when using the `puppetdb` class by using the new parameter `disable_ssl`: class { ''puppetdb'': disable_ssl => true, }

Hi, I''ve just been configuring my new Puppet 3.1.1 / Dashboard setup with Passenger to use PuppetDB for the inventory service. I configured it via the puppetdb forge module, and it all seems to be configured correctly as far as the docs describe. When I look at a node in the dashboard, under the inventory section, I just see: Could not retrieve facts from inventory service: 404

I am attempting to install PuppetDB from source. I am a bit confused however, is lein required? thanks! -- 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

Hi, Has anyone successfully performed this scenario? I''m installing Puppet Enterprise 3.1, and want to have the Console service running on the Puppet Master. However, I want to have the PuppetDB service on another server. It seems like the installer either puts all of the services on one host, or separate out to three hosts. I saw this discussed in

Hi everyone I''m currently trying to install Puppetdb on my puppet master server (on Suse 11 SP2 64bits) using the Source method<http://docs.puppetlabs.com/puppetdb/1.3/install_from_source.html>and I can''t figure out why it is not working. It''s seems to be stuck at the begining of the rake install I have Facter in version 2.0.0 # facter -v 2.0.0 I installed

Is the module puppetdb from the forge still correct ? Every time I try to install puppetdb from the puppet module ("puppet module install puppetlabs/puppetdb"), i got a warning : *Warning: cprice404-inifile is deprecated; please update to puppetlabs-inifile* How may i install the puppetlabs-inifile instead of cprice404 ?? -- You received this message because you are subscribed to

Hello, I am having problems with Puppet since upgrading to 3.0.0. When I call an inventory search I get a Error 400. I have used dashboard + Perl Oct 4 08:58:43 puppet01 puppet-master[7008]: Handling request: GET /production/facts_search/search?facts.lsbdistcodename.eq=lenny Oct 4 08:58:43 puppet01 puppet-master[7008]: header too long ii facter

I finally got around to installing PuppetDB and connecting it to my Master. I even set up Nginx to act as a reverse proxy, and I can make API calls like a pro. The dashboard is nice, but I''m anxious to get at least the same functionality that Puppet Dashboard gave me. Namely, a quick look at recent catalog changes or run failures (is this even possible, since PuppetDB

Trying to get my puppet up and running but running into a slight problem - trying to view a resource I get an error for undefined method [root@puppet puppet-dashboard]# puppet resource user root Error: Could not run: undefined method `prune_parameters'' for nil:NilClass [root@puppet puppet-dashboard]# uname -a Linux puppet.luminexcorp.com 2.6.32-358.0.1.el6.x86_64 #1 SMP Tue Feb 26