CloudBolt provides an orchestration framework that enables customization and extension of many back-end processes such as server provisioning and lifecycle management, user authentication, and order approval flows.

This framework has been used to:

  • Create DNS records for servers before they are provisioned
  • Automatically add servers to an external asset tracking system
  • Enable monitoring of new servers
  • Communicate with a storage array to allocate a new LUN when requested by the user
  • Send messages to chat systems when new resources or servers are built
  • Synchronize user-group membership with Active Directory when users log in

Ways to Orchestrate Your Cloud

Actions are executable code in the form of CloudBolt plug-ins, remote scripts, webhooks, emails, and external orchestration flows. Actions can modify jobs, orders, servers, groups, environments, etc. They can take additional input and can be used to communicate progress to the end user or instruct CloudBolt to make calls into external systems (ex. vCenter, AWS, ServiceNow, Infoblox, etc). For details, see Actions.

Ways in which actions may be executed (described in detail below):

  • Orchestration Actions - hook your custom logic into CloudBolt processes at various trigger points, e.g. during server ordering or provisioning.
  • Blueprint Actions - customize the deployment of your blueprint.
  • Server Actions - run actions on individual servers after they are provisioned.
  • Resource Actions - run actions on deployed resources.
  • Rules - periodically tested conditions that may execute actions.
  • External Orchestrators - use your existing orchestration content (HPSA, vCO) from within CloudBolt.
Information All of the Actions above can be imported and exported. Actions can use a password to encrypt/decrypt secrets. See Actions with Secrets for details.    

Content Library

The CloudBolt Content Library hosts samples of the above use cases. Admins can browse these from within the CB user interface and import them with a few clicks. To try it out, go to the admin view of orchestration actions, server actions, and resource actions as well as rules and recurring jobs.