Server blueprints
The smallest useful blueprint deploys a single server
A blueprint is what appears in the Catalog. It describes how the service is provisioned, how it is torn down, and which operations users can run on it as resource actions. It can define something as simple as a single server or as involved as a multi-tier application stack.
Blueprints also connect to groups and environments, which gives you access control and parameter inheritance. This section covers blueprint development; see Using the platform for how to manage existing blueprints.
The smallest useful blueprint deploys a single server
Use XaaS blueprints to create Catalog entries for services Cloud Management Platform (CMP) does not natively support
Orchestration actions run your code at fixed points in an order or job, applying reusable behavior everywhere it’s needed