IBM Cloud Pak integration
IBM Cloud Pak integration
Use Cloud Pak to manage cloud resources across multiple providers.
IBM Cloud Pak for Kyndryl Modern Operations Applications is an open, hybrid cloud management platform that allows you to securely manage applications across your organization regardless of how they are designed and where they are deployed. It also provides the following capabilities:
- Model applications and application dependencies
- Manage the lifecycles of both applications and infrastructure
- Consistently govern and secure applications and their deployment models
- Deliver observability for your entire stack
For more information about IBM Cloud Pak for Multicloud Management, navigate to https://www.ibm.com/ and search for
IBM Cloud Pak
.Integrating IBM Cloud Pak for Kyndryl Modern Operations Applications provides the following capabilities for customers to address their Hybrid IT needs:
- Modernize infrastructure management
- Use intelligent, secure cloud operations
- Modernize applications and management
- Manage governance and compliance
The following are the set of modules/functions provided by IBM Cloud Pak for Kyndryl Modern Operations Applications:
- Infrastructure Management
- Terraform Automation
- Cloudforms
- Ansible Tower
- Security Governance and Risk Console
- Multicloud Manager
- Cloudforms
- Vulnerability Advisor
- Mutation Advisor
- Container Management
- Multicloud Manager
- IBM CloudApp Manager
- IBM Cloud Event Manager
Supported version
The current version of the integration is supported by IBM Cloud Pak for Kyndryl Modern Operations Applications 2.1 on ROKS.
Terraform Automation
Terraform Automation is part of the
Infrastructure Management
tab of Cloud Pak for Kyndryl Modern Operations Applications. It allows you to automate infrastructure provisioning using Terraform templates and Ansible playbooks. The Terraform Automation consists of Service Composer to design catalogs using Terraform templates and Ansible playbooks, and Service Library that stores all the catalogs created using the Service Composer.The following are key capabilities of Terraform Automation:
- Automate and standardize delivery of infrastructure and application stacks consistently in many cloud providers
- Compose and orchestrate complex environments into easy-to-consume cloud services that can be accessed with a DevOps tool chain or published into a self-service catalog
- Manage workload and stack lifecycle across many cloud providers
- Built with open technology to avoid vendor lock-in
Before you design new catalogs and publish them for consumption with Terraform Automation, you need to understand the following key concepts:
Cloud connection
Cloud connection is the place in Cloud Pak for Kyndryl Modern Operations Applications where the administrator manages connection end points to third party providers such as public and private clouds. The cloud connections consist of the credentials and the URL that must be used to connect to the third-party providers.
Service Composer
Service Composer is a GUI-based service designer interface that is used within Terraform Automation to create catalogs using Terraform templates and Ansible playbooks.
The editor or administrator can use the Service Composer to manage services. Service Composer provides the capability to add parameters and external API calls, and to generate forms for the end users to order catalogs using the appropriate UI controls.
Service library
The service library is a single portal where all the catalogs are displayed with information including the deployed instances for catalogs. The catalogs can be in either Complete or Saved state based on the completion of the catalog definition in the service composer.
The catalog library also supports catalog versioning based on the V.R.M.F. format.
Namespaces
Namespaces are a construct created in the Cloud Pak for Kyndryl Modern Operations Applications IAM module that get carried forward into Terraform Automation. You can then segregate resources by team through allocation of your namespaces to individual teams.
Both the catalogs and the cloud connections must be part of a namespace. The namespaces are assigned to teams, which provides those teams permission to access the resources associated with a given namespace.
Do you have two minutes for a quick survey?
Take Survey
