Provision Engines

What is a Provision Engine?

A provision engine is a connection to a system that is capable of installing an Operating System on a blank VM or a physical server. CloudBolt supports three provision engines: Razor, Cobbler, and HP Server Automation.

Creating New Provision Engines

CloudBolt Admins can create new provision engines by:

  1. Click Admin
  2. Click External Systems
  3. Click Provision Engines
  4. Click Add a provision engine
  5. Choose a technology
  6. Provide the details CloudBolt needs to connect to your technology
  7. Click Create
  8. After this, one can import OS Builds into CloudBolt from the provision engine (and also applications, in the case of HP SA)

Special Considerations for Provision Engines


When using a Provision Engine to install an OS on a VMware VM, CloudBolt skips checking with VMware tools to wait for the OS to be booted and have the appropriate IP & hostname. This is skipped because the Provision Engine OS build may not have VMware tools on it, and VMware tools may be installed by a later step, such as when Chef or Puppet agent installs software on the server.

Even though this wait step is skipped, in the case of Cobbler, an additional wait is still needed to wait for the OS to boot up and be ready for the next steps (such as Chef agent installation). To configure CloudBolt to wait for a set period of time after the base OS is installed, add the “Post Provisioning Delay” parameter to the environment(s) using Cobbler and set it to a number of seconds in which any OS should be able to fully boot.


Setting up a Razor provision engine requires you to create a parameter in Admin -> Parameters:

  • named razor_broker
  • labeled ‘Razor Broker’ (or a name of your choice)
  • of type ‘String’
  • with ‘Show on Servers’ set to true

This references the name of the ‘broker’ instance that Razor will use during post-provisioning. For more details on brokers, consult the Razor documentation. You can use the razor brokers command on your razor server to see the list of broker names available.

On your Environments, you will want to add the following parameters:

  • ‘Razor Broker’, created above.
  • ‘New Password’, the password Razor will set on your server after provisioning.
  • ‘Skip Network Configuration’, if you are using VMware but do not have VMware Tools on your image.