Some notable changes in Oracle Linux Automation Manager Release 2.0 are:

• Service Mesh: Service Mesh provides a multi-service network that links control and execution nodes within a secure mesh that enables the sharing of job execution. The Service Mesh can include up to 20 nodes. For more information about configuring the Service Mesh, see Oracle Linux Automation Manager 2.2: Installation Guide and Oracle Linux Automation Manager 2.2: User's Guide.

• Control Plane: The control plane is part of the Service Mesh that consists of control plane nodes that provide the user interface, role-based access control, and content management functionality. The Control Plane defines how automation is initiated, deployed, audited and delegated to the Execution Plane. From the Control Plane user interface or through the RESTful API, users can manage features such as inventory, schedule workflows, track changes, initiate reporting and so on. For more information, see Oracle Linux Automation Manager 2.2: Installation Guide and Oracle Linux Automation Manager 2.2: User's Guide.

• Execution Plane: The Execution Plane is part of the Service Mesh that consists of execution plane nodes that execute Oracle Linux Automation Engine playbooks. Execution plane nodes use a ready-built container with Oracle Linux, ansible-core, python and provides collections and libraries, which enables a consistent and defined environment every time they run. Execution environments replace python virtual environments. For more information, see Oracle Linux Automation Manager 2.2: Installation Guide and Oracle Linux Automation Manager 2.2: User's Guide.

• Hop Nodes: Hop nodes are connecting nodes that can link together cluster nodes within the Service Mesh, such as control and execution nodes, that cannot directly reach one another. These nodes do not appear as part of instance groups, but do appear as part of the Service Mesh peer relationships.
• Remote Database Options: You can now optionally install a PostgreSQL database on a separate host. For more information, see Oracle Linux Automation Manager 2.2: Installation Guide.
• Upgrade Path from Release 1.0 to 2.0: You can upgrade Oracle Linux Automation Manager Release 1.0 instances to Release 2.0. The upgrade path includes remaining on a single node instance to upgrading to a full clustered instance. For more information, see Oracle Linux Automation Manager 2.2: Installation Guide.
• Workflow Templates: You can create workflow templates using the Workflow Visualizer graphical tool. You can use the tool to specify the run sequence of disparate components such as job templates and management jobs, as nodes in a linear graph-like design. For more information, see Oracle Linux Automation Manager 2.2: User's Guide.
• Instance Groups: You can group control plane nodes and execution plane node into instance groups. By default, the Oracle Linux Automation Manager installation process creates a default instance group for control plane nodes and a default instance group for execution plane nodes. You can add or remove control and execution plane nodes to an instance group. And you can create additional instance groups for execution plane nodes to further manage what execution plane node runs a specific job. For more information, see Oracle Linux Automation Manager 2.2: Installation Guide and Oracle Linux Automation Manager 2.2: User's Guide.

Some highlighted features in Oracle Linux Automation Manager Release 2.0 are:

• Oracle Linux Automation Manager REST API: You can now use the REST API to programmatically interact with Oracle Linux Automation Manager servers. The API is based on AWX version 15.0.1 open-source software and all upstream features are exposed in the REST API; however, support is limited to those features discussed in Getting Started With Oracle Linux Automation Manager. For more information, see Oracle Linux Automation Manager 1.0: CLI and API Reference Guide.

• Oracle Linux Automation Manager CLI: You can now install and use the Oracle Linux Automation Manager CLI to interact with Oracle Linux Automation Manager servers. The CLI is based on AWX version 15.0.1 open-source software and all upstream features are exposed in the CLI; however, support is limited to those features discussed in Getting Started With Oracle Linux Automation Manager. For more information, see Oracle Linux Automation Manager 1.0: CLI and API Reference Guide.

• Oracle Cloud Infrastructure Ansible Collection credential type: Oracle Linux Automation Manager now includes the OCI credential type for accessing the OCI Ansible collection within an Oracle Linux Automation Engine playbook. If your Oracle Linux Automation Engine playbook uses the OCI Ansible collection, see https://docs.oracle.com/iaas/Content/API/SDKDocs/ansible.htm and find the setup instructions relating to AWX. The OCI credential type removes the need to manually create the OCI credential type as described in the Using Oracle Cloud Infrastructure with Ansible Tower and AWX blog post.