Cloud Services

Enterprise Marketplace

Private cloud integration
Published On Nov 06, 2024 - 7:20 AM

Private cloud integration

Learn how to integrate private cloud providers.
This page covers the integration with private cloud providers. The following providers are supported:

VMware Aria Automation (formerly VMware vRealize Automation)

Your tenant supports private cloud using VMware Aria Automation, versions 8.12.2, 8.12.1, and 8.12.0.
For more information about integrating Aria Automation, see VMware catalog creation.
The following table describes supported functions:
Function
Details
Blueprint types
  • Architects' build software component blueprints.
  • Machine blueprints.
  • Simple Anything as a Service (XaaS) blueprints.
  • VMWare Aria Automation blueprints, available from your tenant.
Pricing
  • Different pricing models.
  • Price calculation based on configuration.
  • Request Unit (RU)-based pricing, such as S, M, L, XL.
  • Ability to call an external pricing engine to provide pricing for Aria Automation during add/edit operations.
Basic operations at the service instance support
Delete.
Viewable service component properties
IP address.
Automatic catalog pull from Aria Automation
The tenant automatically pulls from the Aria Automation catalog. Catalog admins also have the option to edit and publish the catalogs for buyer consumption.
Custom Operations for Aria Automation Service Instances and Components
The application supports the ability to configure and trigger custom operations for catalogs. This capability allows catalog and team setup admins to define custom operations triggered from the
Service Inventory
 page. The feature also enables admins to integrate operations changes into the change management workflow, which makes changes trackable.
Out-of-the-box operations supported in a standard deployment include the following:
  • Stack
    • Edit
    • Delete
  • Stack Component
    • Power on
    • Power off
    • Reboot
The application also supports custom operations defined for Aria Automation catalogs. Change management and financial approval workflows track custom operations.
Template tenant and user name requirements
The tenant and user names used in the provider account for Aria Automation are case sensitive. The names entered must use the same case as the names in Aria Automation.
Single value in template file
When uploading a Aria Automation template to the content server, only one value can be present in the template file. As per the new design, either
configGroupName:
 or
group:
can be part of the template. If both values are present, the template upload will not work.

Terraform Automation

The application integrates with the Terraform Automation module of IBM Cloud Pak for Multicloud Management. The current supported version is IBM Cloud Pak for Multicloud Management 2.0 on ROKS.
For more information about IBM Cloud Pak for Multicloud Management, see IBM Cloud Pak integration.
The following table describes the supported functions for Terraform Automation integrated as an endpoint.
Function
Details
Catalog Ingestion/ Catalog Discovery
The Catalog Admin can use the Discovery process to pull Terraform Automation services.
Service Versioning
Customers can create multiple versions of a single catalog at the time of creation of the service in Terraform Automation of Cloud Pak for Multicloud Management. Note that these versions should be named using the V.R.M.F. format and are onboarded using the Discovery process that must be carried out by the Catalog Admin. All versions of the same service are associated to a catalog group.
Provisioning and Deprovisioning services
The tenant allows users with a Buyer role to provision and deprovision Terraform Automation services.
Standard Operations
The tenant supports standard operations defined for ICAM catalogs. The operation must follow any technical and financial approval workflows.
  • Start VM (VM specific)
  • Stop VM (VM specific)
  • Shutdown VM (VM specific)
  • Taint (all resources)
  • Untaint (all resources)
Edit Stack
Buyer can edit the stack if needed to update the parameter value of the stack.
Upgrade and Downgrade Stack
Buyer can check the Available Versions for the service from stack and can upgrade or downgrade the service version for that service.
Failure Management
As part of Failure Management, the application supports Cancel and Retry operations for failed Cloud Pak. Users can also view logs of failed orders.
  • Cancel:
     Deletes all the resources associated under the service (both successfully deployed and partially deployed resources).
  • Retry:
     Deletes all the resources associated under the service (both successfully deployed and partially deployed resources) and then tries to deploy the service again.
Do you have two minutes for a quick survey?
Take Survey