Cloud Deployments are different from Application Deployments.
To deploy to a cloud, simply send a POST request to the URI
/api/clouds/XXXXXX/deploy. A request body containing
at least the command to be executed is expected.
RestClient.post("https://manage.scalarium.com/api/clouds/XXXXX/deploy", JSON.dump(:command => 'update_custom_cookbooks'), headers)
The attributes in the request body must at least contain the command to be run, e.g. 'update_custom_cookbooks', 'update_dependencies', and so on. Optionally you can specify the following attributes:
- command (string):
- 'update_dependencies' to update all dependencies on that machines
- 'install_dependencies' to install the dependencies given to each role
- 'update_custom_cookbooks' will update all your custom cookbooks
- 'execute_recipes' can be used to execute selected recipes e.g. backup tasks. If you use this you will also have to provide the recipes as an hash
- recipes (string): list of recipes that will be executed if command is 'execute_recipes' e.g. 'my-backup, redis::default'
- custom_json: the possibility to add custom JSON to the deployment
- comment (string): A comment describing the deployment.
- instances (array of IDs): An array containing the IDs of instances the deployment should be executed on. If empty, all instances that are online are deployed on.
The result will contain the ID of the newly generated deployment, return a HTTP status 202 and a resource location to the new deployment. See the knowledge base entry on Fetching Deployment Details for information on how to fetch and handle this data.
- Tutorial: Customizing your Scalarium Cloud using Chef
- Customizing your Scalarium Cloud using Chef: The Scalarium Lifecycle System
- Customizing your Scalarium Cloud using Chef: Cooking with Chef
- Customizing your Scalarium Cloud using Chef: Writing a Cookbook to set up Redis
- Customizing your Scalarium Cloud using Chef: Configuring Custom Cookbooks
- View all (4 more)