9.2. Default Scaling Build Life Cycle

Deploy Phase

1. OpenShift Enterprise starts the secondary cartridges on the application's head gear.
2. OpenShift Enterprise runs the web proxy's deploy hook on the head gear.
3. The web proxy runs deployment steps on the application's secondary gears. For example, the default web proxy, HAProxy, preforms the following steps:
   1. It stops the secondary gears.
   2. It synchronizes the code and build artifacts from the head gear to the secondary gears.
   3. It runs the primary cartridge's control update-configuration command on the secondary gears.
   4. It starts all the secondary cartridges on the secondary gears.
   5. It runs the primary cartridge's control deploy command on the secondary gears.
   6. It runs the deploy user action hook, if present, on the secondary gears.
   7. It starts the primary cartridge on the secondary gears. The application is now running on the secondary gears.
   8. It runs the primary cartridge's control post-deploy command on the secondary gears.
   9. It runs the post-deploy user action hook, if present, on the secondary gears.
4. OpenShift Enterprise runs the primary cartridge's control deploy command on the head gear.
5. OpenShift Enterprise runs the deploy user action hook, if present, on the head gear.
6. OpenShift Enterprise starts the primary cartridge on the head gear.
7. OpenShift Enterprise runs the primary cartridge's control post-deploy command on the head gear.
8. OpenShift Enterprise runs the post-deploy user action hook, if present, on the head gear.