Installing engines

To connect the blueprint design server to a cloud system, you need a Heat orchestration engine. Heat orchestration engines interpret blueprints and use them as patterns for cloud resources.

Before you begin

See the system requirements in System requirements and performance considerations.

About this task

The blueprint designer uses engines that are customized with special resource types, which represent artifacts on IBM UrbanCode Deploy and on cloud systems. With these resource types, you can create blueprints that include IBM UrbanCode Deploy components and blueprints that you can provision to clouds.

You can use a single engine to connect to multiple clouds, or you can install multiple engines to spread out the work. You must connect each engine to at least one Keystone server, but you can connect an engine to multiple Keystone servers. If you connect to an OpenStack cloud, then the version of your cloud must match the version of your Heat engine. For example, if you use the Heat engine that is provided with IBM UrbanCode Deploy version 6.2.1.1 or later, you can connect to only Kilo-level OpenStack clouds.

You can install engines in interactive mode or in silent mode, or you can extend existing engines that you use with OpenStack. If you do not currently use an engine with OpenStack, you must install an engine by using the provided installer. You must not extend a new stand-alone engine that you installed by using your Yum repository.

Note: If you are using the blueprint designer with IBM Cloud Manager with OpenStack, you must extend the heat engine from the IBM Cloud Manager with OpenStack environment.

Feedback