Provisioning cloud environments
You can provision an environment from the server or from the blueprint designer. Several different scenarios for provisioning cloud environments are available.
- Clouds that use virtual system patterns
-
To provision environments on clouds that use virtual system patterns, you create blueprints on the IBM UrbanCode Deploy server. For the types of clouds on which the server can provision environments through this method, see Connecting to clouds through IBM UrbanCode Deploy.
To create blueprints on clouds that use virtual system patterns, see Modeling environments for clouds that use virtual system patterns.
To provision environments based on these blueprints, you create environments on the IBM UrbanCode Deploy server using the blueprint as a model. See Provisioning environments through the server (through virtual system patterns).
- Clouds that you connect to via OpenStack Heat
-
To provision environments on clouds via OpenStack Heat, you create blueprints with the blueprint designer. For the types of clouds that the server can provision environments on using OpenStack Heat, see System requirements and performance considerations. For individual instructions for connecting to each type of supported cloud with this method, see Connecting to clouds through the blueprint designer.
There are several different ways that you can use these blueprints to provision environments on clouds via OpenStack Heat. To provision an environment directly from the blueprint designer, see Provisioning environments from the blueprint designer (through OpenStack Heat). To provision an environment from the IBM UrbanCode Deploy server, either as part of creating a new application environment or as part of running an application process, see Provisioning environments from the IBM UrbanCode Deploy server (through OpenStack Heat).
Restriction: If your heat engine is at the Juno level, you cannot provision from a composite blueprint. See Creating composite blueprints.