The IBM® UrbanCode® Deploy server
can use virtual system patterns from cloud systems such as IBM Cloud Orchestrator to
create dynamic environments.
You must have a user account on a cloud system. This account must have
permission to create script packages, to read information about virtual system patterns, IP groups,
cloud groups, and environment profiles, and to create and delete virtual environments. See the
documentation for your cloud system for more information about setting up permissions. For example,
for IBM PureApplication® System, see https://www.ibm.com/support/knowledgecenter/SSCRSX_2.1.0/doc/iwd/aac_user_permissions.dita.
For this type of cloud integration, the following cloud systems are
supported:
- IBM Cloud Orchestrator version 2.4 or later
- IBM SmartCloud® Orchestrator versions 2.2 and
2.3
- IBM PureApplication System version 1.0 or later
- IBM Workload Deployer version 3.1.0.6 or later
Within these cloud systems, you can provision the virtual resources in environment profiles or
in cloud groups. You can also assign the virtual resources to IP groups, but only when you assign
the resources to an environment profile first. For more information, see
Creating environments. You can also use virtual images with no more than one virtual
network card.
IBM UrbanCode Deploy does not support selecting different flavors of virtual resources or virtual nodes that have a
multiplicity greater than 1.
To connect to OpenStack and OpenStack-based clouds, SoftLayer®, Amazon Elastic Compute Cloud, VMware vCenter, or
Microsoft™ Azure, see Connecting to clouds through the blueprint designer.
Note: If you installed a FIPS-compliant server as described in
Installing the server in interactive mode, the
IBM UrbanCode Deploy server cannot integrate with cloud systems through virtual system patterns. Your JVM connects to
only FIPS 140-2 certified IBM providers.
The blueprint design server can still connect to clouds through OpenStack Heat.
- Configure the cloud system to install agents automatically.
- Create a connection to a cloud system.
- Click and then click New
Connection.
- In the Name field, specify a
name for the connection.
- In the Management Console field,
specify the host name of the cloud system.
- In the Username field, specify
the user name of an account that has permission to request cloud resources.
The server stores this user name and password and uses it to
request cloud resources when you use this cloud connection.
- In the Password field, specify
the password for the user account.
- Optional: In the Description field,
specify a description for the connection.
- Optional: In the Teams field,
specify the teams that have access to this connection.
- Optional: Set the timeout for cloud requests
by opening the file installed.properties on the
server and specifying the cloud.requestTimeout property.
This property specifies the timeout in seconds. The default
value is 7200 seconds, or two hours.
- Click Save.
The new cloud connection is included in the Cloud
Connections pane.