Shared database for storedconfigs?

[Atha]

Hi all,
We have a clustered, per location puppet master setup, with multiple
masters being able to serve any client at that location. We are about
to enable storedconfigs. Is it possible to have all the masters at
that each location share one database? Or does each master needs its
own db? Being able to share the database backend would be a huge win!

Cheers,
Atha

[Ohad Levy]

Hi Atha,

if you dont have a high latency between your locations, you can technically do that.
You need to ensure that only one server has the dbmigrate option enabled, and its more or less mandatory to run the same puppet version on all of your servers.

however, for each client connection, the server would require the database - if the database is not reachable, non of your puppetmasters will work.

what exactly are you trying to do? export / collect? inventory?

as far as I'm aware, most big puppet installations don't use storeconfig because of the performance (that is dramatically improved with 0.25x) and the single point of failure.

note, that if you want to get any decent performance, you would need 0.25 with puppetqd enabled.

Ohad

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
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=.

[Atha Kouroussis]

Hi Ohad,

thanks for your reply.

The database would be shared per location, not globally, and as such there shouldn't be any latency issues. As everything else in our setup, it would be clustered to ensure availability. We had read puppetqd and will use it. We already have an activemq deployment so it wouldn't be an issue.

The reason for using storedconfigs would be export / collect.

Cheers,

Atha

For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.