OS builds

One OS build can gather the equivalent template or image from several resource handlers, so an order form can offer a choice of operating system rather than a list of platform-specific template names. The build also controls which environments offer it. Cloud Management Platform (CMP) uses the build to decide what to deploy from, and users never see the underlying template names.

Add an OS build

Managing OS builds needs the osbuild.manage permission.

1. Go to Admin > OS Builds.
2. Select Add.
3. Fill in the fields, then select Add again to create the build.

Fields on an OS build

The list page also offers Remove Unused OS Builds, which clears out builds that nothing is using.

Associate images or templates

A new build has nothing to deploy from until you attach at least one image or template. Open the build and select its second tab.

1. Select Add followed by the technology’s term, such as Add Template.
2. Select the images or templates you want, then select Associate Selected followed by the same term.

Attach one per resource handler that should be able to deploy this operating system. The tab shows which handler each one comes from, and its actions include dissociating an image from the build without deleting it.

Offer the build in environments

A build is only offered in the environments set on it. There are two ways to set them:

• Edit the OS build and set its Environments.
• On a resource handler’s templates tab, select the pencil icon in the OS Build Environments column for the target template.

If a build has more than five environments, the list page shows the first five and a count of the rest.

Where OS builds are used

A blueprint’s server build item names the OS build it deploys. Administrators also see the Servers and Blueprints tabs on a build, which list the servers deployed from it and the blueprints that use it. To order it, open one of those blueprints and place the order.