Before you create an XaaS blueprint, you must understand the intent of your blueprint so that you can create one that correctly provisions your resources.

You can create and use XaaS blueprints as a blueprint component in the design canvas or as a standalone blueprint. The blueprint can be a provisioning blueprint or a non-provisioning blueprint.

Table 1. XaaS Blueprint Types and Outcomes

XaaS Blueprint Type

Is a custom resource required?

Is the blueprint scalable in a deployment?

Can I run a resource action on the deployed blueprint?

Blueprint component that provisions resources

Yes

Yes.

If it is configured to scale, it will scale when the deployment is scaled.

Yes.

It scales when the deployment is scaled, and you can run other resource actions on the deployed component.

The blueprint component appears on your Items tab.

Blueprint component that runs a workflow but does not provision resources

No.

The blueprint uses the vRealize Orchestrator server configuration, but it does not require an XaaS custom resource.

No.

It does not provision resources, but it can run as part of a scale operation.

For example, update a load balancer with the new configuration based on the scale operation.

No.

You cannot run a resource action on a non-provisioning component.

Standalone blueprint that provisions resources

Yes

No.

You must create resource actions to add or destroy instances.

Yes.

You can run resource actions on the deployed resource, including any actions that you created to support scaling.

The blueprint appears on your Items tab.

Standalone blueprint that runs a workflow but does not provision resources

No.

The blueprint uses the vRealize Orchestrator server configuration, but it does not require an XaaS custom resource.

No.

It does not provision resources, but it can run as part of a resource action.

No.

You cannot run a resource action on a non-provisioning component.