It sounds like chef is indeed a good choice for you.
The only question is how isolated the environments need to be. Generally speaking, you would probably want to set up ONE chef server for all your clients. That means that each client can see the configuration information for all the other clients.
You could also set up a separate chef server for each client. It can be difficult to keep all these servers consistent, though.
Or you can use a single Chef server with multi-tenant support to ensure isolation. The hosted chef server supports it, and I hear that the new version chef server 12 also has that feature.
Our values: Privacy, Liberty, Justice
This is more of a newbie’s confusion than a dev’s request for help. Just trying to ascertain if Chef is a good choice in the given scenario.
I am part of a services team which customizes a product for client usage.
There are multiple clients and each has their own environment for QA, Staging, Production and Dev.
Since the customization is done on a similar product the build and deployment options are same across.
We have been using ANT and Shell Scripts till now - with a lot of manual intervention and have looked at chef.
Are the following assumptions and usage pattern correct -
- Create 1 environment per customer + environment [QA, Staging,etc.]
- Tie the servers/machines or nodes to these environments
- Use Environment specific databags or properties to pass config data to nodes
- Enable different teams like DB, Networking to populate the relevant config values
- Get each node to install required apps like JBOSS, MySql, etc. and update the config files based on entries in databags [ basically edit xml or prop files]
Any insight or pointers to user experience would be of great help.