Add a cloud profile to integrate with providers of public or private cloud services.
-
In the menu, click
.
-
Click the
Cloud Providers tab.
-
Click
New Profile.
The
New Cloud Provider Profile dialog box appears.
-
Select the cloud provider that you want to access from the
Type list of installed plug-ins.
VMware vCloud and
Amazon Web Services are supported out-of-the box.
-
In the
Name field, enter a name for the profile. This name will be displayed in the list of profiles when creating a cloud-hosted execution
server.
-
Enter valid credentials to remotely access the cloud system in the
Username and
Password fields. For
Amazon Web Services, this is the
Access Key and the
Secret Key.
-
To configure a VMware vCloud profile (skip this step to configure a different profile):
-
Enter the URL with the hostname only and do not append
/cloud/org/<organization name> as you would when accessing the system with a Web browser. Example:
https://vdirectorweb.
-
Optional:
Version: Leave the field empty if you are using
VMware vCloud Director 5.5 (default). Enter
V5.1 if you are using vCloud Director 5.1.
-
Organization: Enter the name of the vCloud organization that you want to access, for example
dev_org.
-
To configure an Amazon Web Services profile (skip this step to configure a different profile):
-
Region: Select the region in which you want to deploy your instance.
-
Instance Type: The instance types that Amazon offers. This defines for example how much RAM and CPU power your instance will have. Note
that this also has an impact on lease costs.
For more information, visit the
Amazon EC2 Instances page.
-
Keep instance alive on connection error: Select
true if you want the instance to stay alive when the connection between the application server and the Amazon instance breaks.
-
Click
Test Connection to perform a test connection to the cloud provider with the information that you have entered.
-
Click
OK to save your settings.
If the selected cloud provider has templates named "Micro Focus
Silk Central Execution Server
19.5.0.x", these templates are automatically imported as virtual execution servers. Only templates with exactly the same version
as your running
Silk Central environment (see
) will be imported.