Provisioning environments from the HCL Launch server (through OpenStack Heat)#
You can create application environments in the HCL™ Launch server by using blueprints from the blueprint designer.
- Connect the blueprint design server to the server. See Connecting the blueprint design server to the server.
- Make sure the Default Orchestration Service is defined on your cloud project on the Blueprint Designer before provisioning any environment. See Creating cloud projects for the blueprint designer.
- Create a blueprint and configuration file, and ensure that these files are appropriate for the target cloud system:
- Modeling environments for Amazon Web Services
- Modeling environments for VMware vCenter
- Modeling environments for VMware vRealize Automation
- Modeling environments for OpenStack and OpenStack-based clouds
- Modeling environments for Microsoft Azure.
- Modeling environments for Google Cloud Platform
- Add components from HCL Launch to the blueprint; see Deploying components with blueprints.
When you model application environments in the blueprint designer, the blueprints you create appear in two places on the HCL Launch server: as blueprints and as application processes. Therefore, there are two ways to apply a blueprint for a cloud that you connect to through OpenStack Heat to an HCL Launch environment:
- You can create an environment from the blueprint. In this case, the blueprint creates the environment and runs the application process on the new environment.
- You can run the application process on an existing environment. In this case, the blueprint behaves like an application process.
The following steps cover creating an environment from a blueprint. To run a blueprint on an existing environment as though the blueprint was an application process, seeUpdating environments.
On the HCL Launch server, click Applications, select an application, and then click Create New Environment.
The Create New Environment window opens.
Give the environment a name.
In the Blueprint field, select the blueprint.
Note: Blueprints with a cloud icon are OpenStack Heat blueprints and are managed on the blueprint designer. Blueprints without a cloud icon are managed through the HCL Launch server.
Specify the rest of the information that is needed to create a new environment, such as the cloud project and region to use, and then click Next.
For more information, see Creating environments.
In the Blueprint Version field, specify the version of the blueprint to use.
The default version for all blueprints is
In the Configuration field, specify the configuration file to use.
If you selected a configuration file, in the Configuration Version field, specify the version of that file to use.
Customize the property values for the blueprint.
For example, in most cases, specify the zone for the environment in the availability_zone field.
For some clouds, click Image Parameters and then specify the flavor for the environment images in the Flavor field. If the list of flavors does not contain the flavors that you expect, make sure that you registered the flavors with the cloud discovery service. See Configuring SoftLayer image flavors or Configuring VMware vCenter image flavors.
In most cases, you select an SSH key by name in the Key Name field under Image Parameters. However, for VMware clouds, paste the contents of the SSH public key in this field.
The blueprint design server provisions the cloud resources and creates an application environment in HCL Launch. Then, the HCL Launch server runs the component processes that are listed in the blueprint.