Supported Instance Setup Events

Our provisiniong and deployment of your cloud and instances is based on a couple of events. You can use them to hook into our process using custom Chef recipes. The following events are available for each role:

• setup: The initial provisioning of an instance after it has booted. If you have any additional services you want to have set up, this is the place to put them. A setup will be done only once for an active instance. When you stop an instance and later start it back up again, it'll again be in a clean slate and will run setup again.

• configure: Every time your cloud's state changes, e.g. an instance is added or goes away, all instances will be sent this event, together with the data describing your cluster. The data doesn't describe what exactly has changed, for now that's up to you to figure out if necessary.

• deploy: When you deploy code this is the event that's triggered. If the deployment hooks you can use through files in your application aren't enough, you can use this event to do more things in a Chef-style manner.

• undeploy: When you remove an application it's removed from the cloud it was running on. If you have any additional cleanup steps you need to run, this is where they'd go.

• shutdown: When you stop an instance Scalarium first sends the instance the shutdown event before actually stopping it on EC2. The instance has 45s to do any cleanup. After the 45s the instance is really shutdown. Usually you would shutdown services during shutdown to ensure they are cleanly stopped.