This page describes the current startup and provisioning process for the collaboration tools on the cloud.

Phase States

1. Instance Start-up
2. Configuration
3. Run

Each component needs the equivalent of a start-up script.

Instance Start-up

Each component of the collaboration tools has a machine image that contains all needed applications and software dependencies.  A provisioning script for each component uses parameters from a tracking repository to start an instance and configure the applications on this instance.  The basic startup process for an instance is as follows:

1. Provisioner retrieves AMI-ID, EBS volumes, user data and other startup paramters from the tracking repository
2. Provisioner starts an instance of an AMI using these paramters
3. Provisioner waits for AMI to startup and then attached EBS volumes
4. Provisioner updates tracking repository with information about the instance such as public, private dns
5. Provisioner makes any necessary updates to other interconnected components (such as the web server or SSO service)

Configuration of Applications

Once the instance has booted, volumes must be mounted and applications configured before they can be started.  These configuration parameters are stored and retrieved as the user-data for this instance and used by a shell script to mount the volumes and configure the apps.

Start Applications

Once the apps are configured, a shell script then starts the applications.