[chef] Correct use of Chef


Chronological Thread 
  • From: Vikas Roonwal < >
  • To:
  • Subject: [chef] Correct use of Chef
  • Date: Tue, 11 Nov 2014 12:07:31 +0530

Hi,
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 -
1. Create 1 environment per customer + environment [QA, Staging,etc.]
2. Tie the servers/machines or nodes to these environments
3. Use Environment specific databags or properties to pass config data to nodes
4. Enable different teams like DB, Networking to populate the relevant config values
5. 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.

Thanks,
Vikas



  • [chef] Correct use of Chef, Vikas Roonwal, 11/10/2014

Archive powered by MHonArc 2.6.16.

§