Develop blueprints on CloudBolt Documentation

Server blueprints

Mon, 01 Jan 0001 00:00:00 +0000

This topic walks through a minimal configuration of one server tier on a blueprint’s Build tab and one group on its Groups tab. For the full set of build items and options, see Build configuration.

Before you start

You need permission to create blueprints, at least one OS Build, and one environment, which in turn requires a configured resource handler.

Create the blueprint

On the Catalog page, select Create Blueprint, enter a name, then select Save.

XaaS blueprints

Mon, 01 Jan 0001 00:00:00 +0000

Anything-as-a-Service blueprints call an external API to provision, delete, and manage a service. Users order it from the Catalog the same way they order a server. You define what happens at each stage, while CMP handles the catalog, order form, approvals, and auditing.

Start by giving the service a custom resource type. This is what holds the deployment’s parameters and gives day-2 operations something to attach to.

Lifecycle

Develop these in order. Build is what makes the service orderable. Without teardown, deleting a resource in CMP leaves the real service running at the provider.

Deployment trigger points

Mon, 01 Jan 0001 00:00:00 +0000

An action attached to a blueprint runs only for that blueprint. The same action attached to a trigger point runs for every order or every server provisioned, which is ideal for policy, naming, validation, and notifications. This topic covers the trigger points a deployment passes through and what each one receives.

Where the trigger points fall

Deploying a blueprint that contains a single server runs two jobs: a Deploy Blueprint job that processes the order and a Provision Server job that builds the server, each with its own trigger points. Actions can also be triggered on order status changes. See Orchestration actions for the full list of trigger points.