What is new
The following new features are available in the Cloud Automation Manager 3.1.2.0 release on IBM Cloud Private 3.1.2.0:
What is new in Cloud Automation Manager 3.1.2.0
- Cloud Automation Manager is PCI compliant. For more information, see IBM Cloud Private Knowledge Center .
- Support is added for running Cloud Automation Manager on s390x zLinux as a managed-from environment.
- Support to integrate with Multi Cloud Manager product. For more information, see Integrating with Multi Cloud Manager.
- Support is added to deploy IBM Cloud Private simple and HA topologies into public clouds. For more information see Deploying IBM Cloud Private on public clouds.
- Support is added to deploy Kubernetes services into IBM Cloud. For more information see Deploying IBM Cloud Kubernetes Service on IBM Cloud.
- Support for VMware NSX-T cloud connection. For more information about VMware NSX-T cloud connection, see Configuring a VMware NSX-T connection.
- Support for Huawei Cloud connection. For more information about Huawei Cloud connection, see Configuring a Huawei Cloud connection.
- Support to integrate with IBM Cloud Orchestrator. For more information, see Integrating with IBM Cloud Orchestrator.
- Cloud Automation Manager is accessibility compliant.
- Ease of navigation within the user interface elements by using keyboard.
- Synchronized tabbing through interactive elements.
- Ease of reading with changes to color contrast.
- Shortcut Keys.
For more information on accessibility, see Accessibility features for Cloud Automation Manager.
- Carbon Version 9 for operating system.
- Upgrade from Node Version 6 to Node Version 8.
- You can dynamically tag cloud resources from a set of system tags. For more information, see Tag module.
- Support for creating and managing virtual machine snapshots for VMware template instance. For more information, see Creating and managing snapshots.
- Operating system restart support is included in VMware vSphere virtual machine Actions. For more information, see Managing virtual machine resources.
- Cloud Automation Manager Template Designer enhancements:
- Ability to add tags. For more information about adding tags to terraform template from Template Designer, see Creating a template from Template Designer.
- Ability to use shared parameters (Data Types and Data Objects) for your terraform templates from Template Designer user interface. You can add shared parameters defined in Cloud Automation Manager as default values for variables or create new shared parameters. For the actual procedure, see Shared parameters in Template Designer.
- Cloud connections, Data Objects, deployed instances, and content runtime can be isolated to a specific namespace. If you create a cloud connection in a specific namespace, then only deployments to that namespace can use the cloud connection. All connections created prior to 3.1.2.0 are by default globally accessible across all namespaces. However, for content runtime, you must migrate the content runtime that got created prior to this release so that your middleware content instance deployments can continue to function as before. For more information, see Migrating content runtime created prior to Cloud Automation Manager 3.1.2. When you deploy a new middleware template, then a Data Object is created that is associated with "advanced_content_runtime_chef" Data Type. The newly created Data Object can be made globally accessible to namespaces if you want to deploy middleware into a different namespace using this content runtime. For more information, see Deploying a template and Provisioning and managing your Content Runtime infrastructure.
- The user interface for service library, template library, and deployed instances have been enhanced. The records are now displayed in a table format with sort and pagination capabilities. The search filters are also improved for better retrievability of records.
- Cloud Automation Manager composer enhancements:
- You can run a service workflow while you destroy an instance. For more information, see Rest Hooks. Also, in the Editing a service file topic, see
the
"on_delete"
section of Rest Hooks. - You can configure timeout value for Rest Hook. In the Editing a service file topic, see the Rest Hooks section.
- The "datatypes" element is introduced in Service Composition Language V3 to support Shared Parameters in service definition. For more information, see Using shared parameters in service interpolations and Editing a service file.
- You can dynamically link shared parameters in a service definition and fetch the details at runtime. For more information, see Shared parameters in Templates topic. For the behavior of this dynamic shared parameter at runtime, see Creating a service instance.
- Support for error flow in the composition flow. For more information, see Working with Composition tab.
- Support is included for interpolation of primary flow activity parameters in Error flow. For more information, see Service instance level parameters in Error flow section of Service instance level parameters topic.
- You can create and invoke a stand-alone action that is independent of any service or service instance. For more information, see Create Action API and Invoke Action API.
- Ability to define pricing in plan. For more information about the pricing in service plan, see Pricing for service plan. For the pricing definitions in Service Composition Language, see plans section in Editing a service file page.
- Support for automatically generating system tags when you deploy a service. For more information, see the catalog_metadata section of Editing a service file page.
- You can make Rest Hooks calls and send email notifications from Cloud Automation Manager behind the proxy set up.
- Support is added to use IBM Business Process Manager (BPM) provider templates in a service. For more information to enable during installation of Cloud Automation Manager, see Offline and online installation sections. To know about the procedure to set Business Process Manager post the installation, see Enabling and disabling Business Process Manager. For the procedure to set BPM connection details during the service definition, see Templates. For the long running service that includes a BPM template wherein claim and approvals are required, see Creating a service instance.
- Using APIs, you can run retry, resume, and bind with updated service instance parameter values. For more information about the APIs, see Service and service instance parameters.
- You can retire draft services by using the APIs. For more information, see Service and service instance APIs.
- You can create dynamic cloud connections for a template during service definition wherein the connection details are fetched during runtime. For more information, see the Different ways of adding values for the cloud connection in Templates topic. For the behavior of this dynamic cloud connection at runtime, see Creating a service instance.
- You can run a service workflow while you destroy an instance. For more information, see Rest Hooks. Also, in the Editing a service file topic, see
the
What is new in Cloud Automation Manager Content 3.1.2.0
- You can deploy IBM Cloud Private in a private or public cloud as a non-root user. Sometimes, root users are not enabled for direct SSH connection to guest VMs. The user (sudoer) who deploys IBM Cloud Private is enabled in the VMware template.
- RHEL support for IBM Cloud Private templates.