Storeconfig and mcollective using activemq

[Svein]

How can I set up both Storeconfig and mcollective using activemq for both? mcollective should use username and password, but it seems to me that storeconfig don't have an option to use user:pw.
I'm saving the config in an postgres db.

[Ken Barber]

Why don't you try using PuppetDB for stored configs instead? Its
asynchronous, uses activemq behind the scenes and supports postgres.

https://github.com/puppetlabs/puppetdb

> --
> 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/-/j6aKTi8PABYJ.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.

[Mike Skint]

One reason I wouldn't do this is that the puppet console *only* uses mysql and as I understand it
puppetdb doesn't support mysql,  I'm not chuffed by the idea of running both..

[Andrew Stangl]

RE: puppetdb and pgsql: it all depends on how big your environment is - the suggestion for puppetdb is, if you have fewer than 100 nodes, that you use the built in haskell/cloujure db - I've ended up doing this, since the env is fairly small where we've got this configured, and the storeconfigs were painfully slow. I was also disappointed to discover that there's no pgsql backend for the dashboard - hopefully this is something that will be available soon - there are feature requests in the puppetlabs redmine for it. 

Right now, I've installed puppetdb and using the built in db, and I've not seen major performance gains with store configs, to be honest ... but further profiling seems to be pointing a finger at the speed of file serving as opposed to config retrieval via storeconfigs ... just another bottleneck in the pain that my puppet setup has become