Open source Chef Server 10.18.2

The following steps are performed by a Shell script when executed as user deploy on a utility host.

1. Initialize variables
2. Get the latest revision hash from GitHub
3. Disable availability monitoring to prevent alerts over HTTP 503 status
4. Switch all web and utility hosts to maintenance mode
5. Deploy utility
  1. Stop Magento’s cron and all Resque workers
	2. Address filesystem dependencies
	3. Chef checks out the defined revision as a new release
	4. Address Magento dependencies
	5. Update all cron tasks and scripts for automation
	6. Deploy all modules
	7. Clear cache
	8. Run any migrations
	9. Start the Magento cron
	10. Start Resque workers
6. Deploy the first web host
	1. Address filesystem dependencies
	2. Chef checks out the defined revision as a new release
	3. Address Magento dependencies
	4. Deploy all Magento modules
7. Mark a new deployment in New Relic
8. Enable availability monitoring services
9. Disable load balancer services to all other web hosts
10. Continue deployments on web hosts, sequentially bringing them online
11. Perform Chef routines for the Endeca hosts