About Managed services Content
The Managed services library comes pre-populated with sample Terraform templates to help you get started quickly. These templates can be deployed across supported clouds that include IBM Cloud, AWS, Azure, GCP, and VMware. The pre-populated sample templates are fully supported by IBM. The Supported Terraform Templates page lists all the supported templates and their repository location in GitHub .
In addition to these pre-populated templates, the GitHub repository contains templates that are provided as-is with no support. You can import these as-is templates using the instructions in Import Template section. If these templates do not satisfy your requirements, then you can fork the repository and change the template to suite your requirements.
The Terraform template content in Managed services library can be classified into starterpack, middleware, and integration contents.
Managed services Starterpack Library
The starterpack library content contains automation building blocks that deploy a select set of cloud-native payloads. Some automated deployments that you can perform with the included templates are:
- MEAN stack
- LAMP stack
The sources for the starterpack library templates are available at GitHub location. You can deploy the starterpack content templates using these instructions.
Managed services Kubernetes cluster templates
The starterpack library content also contains a set of templates to deploy Kubernetes cluster based on native Kubernetes services on public cloud and Import these clusters to the hub cluster.
The GitHub repository also contains as-is templates to deploy Red Hat OpenShift 3.x and 4.2 on VMware and AWS.
Managed services Middleware Library
The middleware library comes pre-populated with templates to deploy a select set of IBM middleware. These templates contain automation building blocks to deploy
- IBM WebSphere Liberty V17
- IBM WebSphere Application Server ND V9
More as-is middleware templates are available at GitHub location. You can import them using the instructions in Import Template section. Some automated deployments that you can import from this location includes:
- IBM Db2 V11 or V10.5 stand-alone
- IBM MQ Series V8 or V9
The middleware library templates depend on Chef automation to perform the installation of the middleware products. The chef automation is driven by the Content Runtime environment.
A summary of available middleware templates and associated Chef cookbooks is available at GitHub .
The following links provide more information on the middleware templates.
- Middleware Templates Description: This page details the relevant aspects of Terraform templates used in Middleware library.
- Deploying Middleware Template: This page explains how to deploy a middleware library content.
Managed services Integration Library
Integration library templates provide examples on how to integrate with third party services using Terraform templates. These templates can be wrapped in Service Composer to control the execution.
- InfoBlox Integraton
- ServiceNow CMDB Configuration Template
- IBM Cloud App Management integration . For more information about IBM Cloud App Management, see IBM Cloud App Management documentation .
Content Runtime Environment
The Content Runtime Environment is set up by deploying the content runtime templates. The following links provide more information on the Content Runtime Environment.
- Content Runtime Environment Overview: This page explains the concepts and architecture of Content Runtime Environment.
- Managing the Content Runtime: This page explains how to set up and manage the Content Runtime Environment.
- Content Runtime in Offline mode: This page details how to install Content Runtime Environment in offline mode (air-gapped system with no-internet).
- Managed services Content APIs - This page details APIs to manage Chef cookbooks and roles.
- Troubleshooting issues and useful links - This page details how to troubleshoot the issues related to Content Runtime environment and Middleware Templates.
- FIPS compliant Content Runtime Environment - This page details how to enable FIPS compliant Content Runtime Environment.
Custom Terraform providers provided by Managed services
The middleware templates that leverage Chef cookbooks to deploy middleware uses Terraform CAMC provider to perform following Chef related operations:
- Chef bootstrap operation on the target node
- Deploys one or more Chef cookbooks and Chef roles on the target node
- Makes use of the chef-vault gem to store secrets, such as passwords and user names to be defined and used by cookbooks during the software deployment process.
In addition to these operations, Terraform CAMC provider can execute scripts and store the output for use by other resources in your Terraform template.
Filebeat Terraform provisioner installs and configures the Filebeat log data shipper to send log file data back to IBM Cloud Pak® for Multicloud Management. For more information, see Filebeat Terraform provisioner for Managed services.
Proceed to Offline Content Installation to know more about offline content template installation and content runtime installation.
Proceed to Starterpack and Integration Content to know more about starterpack and integration library content.
Proceed to Managing the Content Runtime to know more about Content Runtime Environment.
Proceed to Understanding and Deploying Middleware Content Templates to know more about middleware content.