[chef] Re: Problems with the standalone installation - using an external database and git repository

[Tensibai < >]

Le 2015-02-06 10:38, Bart a écrit :

 

 

When looking at the local pgsql I can see there are 4 databases and a few users. I've created all of those on our DB server. But even then no luck, it seems the databases aren't populated and thus Chef won't work.

 

[...] we don't want the Chef software to populate the DB server, it has a dedicated Job as a DB server and we'd like to keep that as clean as possible.

 

Don't get you there, you don't want chef to populate the DB but you want it to populate the DB ???? 

You can try dumping the local DBs to remote and then point chef-server to the remote...

 

Also, since I havent even gotten to the Git part yet, will I get similar issues when I try to use an external Git for Chef? Is it even possible?

There's no link between chef-server and git, the git repo are used to store/version the cookbooks before being uploaded to the chef server. (Or I have missed something somewhere)

 

The chef-server is made of more moving parts than just api frontend and DB backend, there's bookshelf too which will store the cookbooks and is an s3 compatible service storing files by checksum (global idea).

 

If you're starting with chef, I would advise starting to learn it with a simple standalone install before trying to make a distributed one...

 

Using a remote DB sounds overkill to me and may get you in unknown and untested problems.

This won't give you a zero downtime system without managing to replicate bookshelf, rabbitmq and solr indexes too (at least).

 

In my opinion if you want to achieve HA on the chef server, you'd better:

- look at the HA commercial addon (replication)

or

- take time to understand deeply each part an how they works  together before trying to hack over them.