Hmm, you mean different DBs on a single Postgres cluster or the same actual DB? The latter won't work unless you also sync the bookshelf data and that might be tricky across a WAN. Using something like WAL-E for async replication might be more amenable to that kind of setup.
I'm probably missing something obvious here.
But we want to have a open-source chef server in
3 data centers sharing a single postgresql DB.
But I don't see an obvious config parameter/s
to point the different services to the DB..
Has anyone done this kind of setup before?
How about one copy of chef-server on a NAS/SAN mounted volume
but booted on 3 different servers? Have you seen this kind of config
before? Any locking issues, etc..
Thanks again,
Daniel Gutierrez
On Tuesday, June 24, 2014 4:15 PM, Noah Kantrowitz noah@coderanger.net wrote:
Hmm, you mean different DBs on a single Postgres cluster or the same actual DB? The latter won't work unless you also sync the bookshelf data and that might be tricky across a WAN. Using something like WAL-E for async replication might be more amenable to that kind of setup.
I'm probably missing something obvious here.
But we want to have a open-source chef server in
3 data centers sharing a single postgresql DB.
But I don't see an obvious config parameter/s
to point the different services to the DB..
Has anyone done this kind of setup before?
I'm probably missing something obvious here.
But we want to have a open-source chef server in
3 data centers sharing a single postgresql DB.
But I don't see an obvious config parameter/s
to point the different services to the DB..
Has anyone done this kind of setup before?