What is new

The following new features are available in the Cloud Automation Manager 3.1.2.1 release on IBM Cloud Private 3.1.2 and 3.2.0 versions:

What is new in Cloud Automation Manager 3.1.2.1

• Services and templates can be isolated to a specific namespace.
• You can create a duplicate template or service. For more information, see Duplicating a template and Duplicating a service.
• Mail configurations can be isolated to a specific namespace. For more information, see Managing Email Configuration.
• You can import existing PowerVC or OpenStack deployments. For more information, see Importing an existing PowerVC or OpenStack virtual machine.
• Improvements to SMTP connections API. For more information, see SMTP connection API.

What is new in Cloud Automation Manager Content 3.1.2.1

• Cloud Automation Manager 3.1.2.1 also ships terraform templates and services to deploy and configure IBM Cloud Private 3.1.2 and Multi Cloud Management 3.1.2 versions respectively.
• You can deploy, scale and federate Azure AKS clusters and Google GKE clusters in Multi Cloud Manager. For the list of new templates and services, see Integrating with Multi Cloud Manager.
• Cloud Application Management integration service and template are available in the Git repository. For more information about the available service and template, see Managing services in service library and Managing Integration Template Library.

• Starter packs have been renamed to have unique names:

  • "LAMP stack deployment " (AWS template) is renamed to: "LAMP stack deployment on AWS"
  • "LAMP stack deployment " (VMware template) is renamed to: "LAMP stack deployment on VMware"
  • "MEAN stack deployment" (AWS template) is renamed to: "MEAN stack deployment on AWS"
  • "MEAN stack deployment" (VMware template) is renamed to: "MEAN stack deployment on VMware"
  • "MongoDB on a Single VM" (IBM Cloud template) is renamed to: "MongoDB on a Single VM on IBM Cloud"
  • "MongoDB on a Single VM" (VMware template) is renamed to: "MongoDB on a Single VM on VMware"
  • "Node.js on a Single VM" (IBM Cloud template) is renamed to: "Node.js on a Single VM on IBM Cloud"
  • "Node.js on a Single VM" (VMware template) is renamed to: "Node.js on a Single VM on VMware"
  • "Strongloop 3 Tier Deployment" (IBM Cloud template) is renamed to: "Strongloop 3 Tier Deployment on IBM Cloud"
  • "Strongloop 3 Tier Deployment" (VMware template) is renamed to: "Strongloop 3 Tier Deployment on VMware"
  • "Strongloop Stack on a Single VM" (IBM Cloud template) is renamed to: "Strongloop Stack on a Single VM on IBM Cloud"

  • "Strongloop Stack on a Single VM" (VMware template) is renamed to: "Strongloop Stack on a Single VM on VMware"

    For more information or to download the starter packs, see GitHub repository .