I have about a dozen sites with puppet masters in each. They are
geographically located with some slow network links between them. The setup
I was evaluating is to have a centralized stored config server running mysql
with all of my remote masters sending their locations data back to the
central
I evaluated this scenario a couple of years ago (before puppetq), and it was
never a feasible solution due to a. latency (e.g. everything is much
slower), b. if wan goes down, your master wont work.
One of the reasons that I've developed Foreman, is to overcome this problem,
the way I do it is:
-
I don't want to use sqllite... puppetqd doesn't leave me much of a choice
since it will default to it even if you tell it to use mysql as your
storedconfig DB since thats needed for the centraldb. Ultimately I think
puppetqd needs support for keeping a cached copy of various database flavors
On Jun 7, 1:00 pm, Christopher Johnston chjoh...@gmail.com wrote:
Think I found the issue from an strace, the rubygems-sqlit3 rpm was
missing.. still curious on where the logs end up for it though. The fact
that its using sqllite also doesn't help as I think I am running into
locking issues
Think I found the issue from an strace, the rubygems-sqlit3 rpm was
missing.. still curious on where the logs end up for it though. The fact
that its using sqllite also doesn't help as I think I am running into
locking issues if I try to run a cross environment update.
How to deal with sqllite
