Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 2. New features and enhancements

The Ansible Lightspeed intelligent assistant is now generally available on Ansible Automation Platform 2.6 on OpenShift Container Platform. It is an intuitive chat interface embedded within the Ansible Automation Platform, utilizing generative artificial intelligence (AI) to answer questions about the Ansible Automation Platform.

The chat experience in the Ansible Lightspeed intelligent assistant interacts with users in their natural language prompts in English, and uses large language models (LLMs) to generate quick, accurate, and personalized responses. These responses empower users to work more efficiently, thereby improving productivity and the overall quality of their work.

To access and install Ansible Lightspeed intelligent assistant, you will need the following:

  • Ansible Automation Platform 2.6 on OpenShift Container Platform
  • An LLM service that is hosted on either Red Hat Enterprise Linux AI or Red Hat OpenShift AI

For more information, see Deploying the Ansible Lightspeed intelligent assistant on OpenShift Container Platform in Installing on OpenShift Container Platform.

Ansible self-service automation portal is now generally available as part of the Ansible Automation Platform subscription. The new self-service automation portal empowers platform admins to provide a streamlined “point-and-click” Ansible automation experience to a broader set of users within the organization. Users who are not Ansible experts now have a dedicated self-service portal from which they can launch a range of automation jobs.

  • Installation: Deployment of self-service automation portal requires Red Hat OpenShift Container Platform using a Helm chart. A future deployment of self-service automation portal on Red Hat Enterprise Linux 10 is planned for Technology Preview in a future asynchronous release of Ansible Automation Platform 2.6.
  • Synchronizes existing automation content: Extend the reach and impact of your automation job templates, while maintaining full control and compliance.
  • Seamless Integration: Uses your existing Ansible Automation Platform configuration—same logins, same security controls, same automation logic.
  • Simplified Interface: A distinct, user-friendly web interface designed for business users, not automation experts.
  • Guided Workflows: Step-by-step forms that walk users through automation requests without technical complexity - automatically generated from your existing job templates.
  • Smart Forms: Real-time field validation, conditional and dynamic forms, and dropdown fields for Ansible Automation Platform artifacts, such as Ansible Automation Platform inventories.

2.3. Technical Preview of Ansible Automation Dashboard
Copier lien

Automation Dashboard is now available in a Technical Preview State as part of the Ansible Automation Platform subscription. Automation dashboard is a utility you can connect to one or more Ansible Automation Platform deployments to visualize automation usage data, determine time savings, track ROI, and drive increased visibility into automation strategy, resource allocation, and prioritization of automation projects. Benefits include:

  • Installation: Deployment of Automation Dashboard is via containerized installation only.
  • Secure on-premise deployment: Simplified deployment as a self-contained, on-premise utility that runs on a dedicated RHEL 9 x86 and ARM host.
  • Easy Integration: Integrates into Ansible Automation Platform 2.4, 2.5 and 2.6 instances with OAuth2 token for read-only access to pull data.
  • Automated data sync: Once configured, the dashboard automatically syncs and visualizes data from connected Ansible Automation Platform instances.
  • Flexible Reporting: Dashboard allows to generate and share customized PDF reports and export raw CSV data for flexible ingestion into BI tools.

For more information, see Ansible automation dashboard.

2.4. Configuration as Code
Copier lien

The ansible.platform collection now provides unified, platform-wide Role-Based Access Control (RBAC) management across Ansible Automation Platform components. New or enhanced modules include Organization, Team, User, Role definitions, Role Assignments (team/user). Additionally:

  • You can declare the RBAC state as code and apply idempotently across services.
  • Ansible collections now use a standard global environment variable prefix across components. Automation controller, Automation hub, and Event-Driven Ansible all use a new standard of “AAP_” instead of "COMPONENT_". For example, aap_hostname. See the documentation in Automation hub for more information.

2.5. Service accounts
Copier lien

  • Service accounts, created in console.redhat.com, can now be used to manage subscriptions in Ansible Automation Platform. Manifest files and basic authentication may still be used for this purpose as well.
  • Service accounts are now required in order to send data to automation analytics.

2.6. Event-Driven Ansible (Automation decisions)
Copier lien

Event-Driven Ansible includes several key enhancements in the Ansible Automation Platform 2.6 release that improve performance, simplify operations, and expand the platform’s capabilities across security, networking, and event processing.

  • External secret management: Event-Driven Ansible now supports external secret management systems, achieving parity with Automation controller. This includes support for HashiCorp Vault, CyberArk, Microsoft Azure Key Vault, and AWS Secrets Manager.
  • Editable project URLs: You can now edit the source control URL for existing Event-Driven Ansible projects, providing greater flexibility to adapt to repository changes.
  • Improved job auditing: A new label is automatically added to jobs triggered by Event-Driven Ansible, along with support for custom labels. This allows for more efficient tracing and auditing of event-triggered automations.
  • Kafka enhancements: The Kafka source plugin now supports multiple topics and allows the use of regular expressions and wildcards. Additionally, it now supports GSSAPI for enhanced authentication.
  • New event filter: A new filter plugin, event_splitter, is available to handle and process nested events more effectively.
  • Rulebook concurrency key: Rulebooks now support a concurrency key, enabling you to group events by resource to ensure they are processed sequentially.

2.7. Installation updates
Copier lien

2.7.1. Containerized installation
Copier lien

Updated system requirements for containerized installation of Ansible Automation Platform include:

  • The Red Hat Enterprise Linux 9.2 operating system requirement was updated to 9.4 or later minor versions of Red Hat Enterprise Linux 9. Red Hat Enterprise Linux 10 system requirements are unchanged.

  • PostgreSQL 15, 16, and 17 are now supported for customer provided (external) databases.

    Note

    External databases using PostgreSQL 16 or 17 must rely on external backup and restore processes. Backup and restore functionality is dependent on utilities provided with PostgreSQL 15.

For more information see System requirements in Containerized installation.

2.7.2. Operator installation
Copier lien

Updated system requirements for Ansible Automation Platform Operator on Red Hat OpenShift Container Platform include:

  • The Red Hat Enterprise Linux 9.2 operating system requirement was updated to 9.4 or later minor versions of Red Hat Enterprise Linux 9. Red Hat Enterprise Linux 10 system requirements are unchanged.
  • PostgreSQL 16 and 17 are now supported for customer-provided (external) databases.
Note

External databases using PostgreSQL 16 or 17 must rely on external backup and restore processes. Backup and restore functionality is dependent on utilities provided with PostgreSQL 15.

For more information about the Ansible Automation Platform Operator system requirements, see Operator topologies in Tested deployment models.

2.7.3. RPM installation
Copier lien

Updated system requirements for RPM installation of Ansible Automation Platform 2.6 include:

  • Ansible Automation Platform RPM installer was deprecated in 2.5 and will be removed in Ansible Automation Platform 2.7. The RPM installer will be supported for RHEL 9 during the lifecycle of Ansible Automation Platform 2.6 to support migrations to existing supported topologies. See the support matrix for more information on upgrade and migration paths.
  • Red Hat Enterprise Linux 9.2 operating system requirement was updated to 9.4 or later minor versions of Red Hat Enterprise Linux 9. Red Hat Enterprise Linux 8 is no longer supported.
  • Red Hat Enterprise Linux 10 is not supported for RPM installations. See support matrix for more information on supported upgrade and migration paths.

  • PostgreSQL 16 and 17 are now supported for customer-provided (external) databases.

    Note

    External databases using PostgreSQL 16 or 17 must rely on external backup and restore processes. Backup and restore functionality is dependent on utilities provided with PostgreSQL 15.

For more information, see System requirements in RPM installation.

2.8. Upgrade paths
Copier lien

The following table outlines the supported upgrade paths for Ansible Automation Platform 2.6.

Note

The RPM-based upgrade paths are deprecated and will be removed in Ansible Automation Platform 2.7.

Expand
Starting DeploymentUpgrade Deployment

2.4 RPM single automation controller node

2.6 RPM growth

2.4 RPM single node automation controller and automation hub

2.6 RPM growth

2.4 RPM multi node automation controller

2.6 RPM enterprise

2.4 RPM multi node automation controller and automation hub

2.6 RPM enterprise

2.5 RPM growth

2.6 RPM growth

2.5 RPM enterprise

2.6 RPM enterprise

2.5 Container growth

2.6 Container growth

2.5 Container enterprise

2.6 Container enterprise

2.4 Operator single automation controller node

2.6 Operator growth

2.4 Operator single node automation controller and automation hub

2.6 Operator growth

2.4 Operator multi node automation controller

2.6 Operator enterprise

2.4 Operator multi node automation controller and automation hub

2.6 Operator enterprise

2.5 Operator growth

2.6 Operator growth

2.5 Operator enterprise

2.6 Operator enterprise

2.9. Migration paths
Copier lien

The following table outlines the supported migration paths for Ansible Automation Platform 2.6. Migration involves transitioning between deployment types, such as from an RPM to a containerized installation. This process is exclusively supported between identical versions (for example, 2.6 to 2.6).

Expand
Source environmentTarget environment

RPM-based Ansible Automation Platform

Container-based Ansible Automation Platform

RPM-based Ansible Automation Platform

OpenShift Container Platform

RPM-based Ansible Automation Platform

Managed Ansible Automation Platform

Container-based Ansible Automation Platform

OpenShift Container Platform

Container-based Ansible Automation Platform

Managed Ansible Automation Platform

2.10. Overview of upgrade improvements
Copier lien

Ansible Automation Platform 2.6 includes changes that significantly improve the upgrade experience when moving from Ansible Automation Platform 2.4 to 2.6.

Note

You must be on the latest version of 2.4 or 2.5 before you upgrade to 2.6.

Expand
ScenarioChangesAdditional information

Upgrading from 2.5 to 2.6

Upgrading from 2.5 to 2.6 does not involve changes to the platform infrastructure requirements, architecture, or services. The improvements described in the 2.4 to 2.6 upgrade path are also present in the 2.5 to 2.6 upgrade path; however, the platform gateway service is already in place in 2.5.

If you upgraded from 2.4 to 2.5, you must migrate your authentication methods and users before upgrading to 2.6 as that legacy authenticator functionality was removed.

Any users that were created during the 2.4 to 2.5 upgrade that were not fully migrated will be removed from the system when upgrading to 2.6. The users that have previously merged their user records while on 2.5 will remain to function as is for 2.6.

Any 2.4 Controller users that have not successfully logged into 2.5 since upgrading from 2.4, will be unable to log into platform-gateway after a 2.6 upgrade. The user will be backwards compatible for direct Automation Execution access but unable to access the full platform. Please ensure all users planning to leverage 2.6 have successfully logged into 2.5 prior to upgrading.

NOTE: Upgrades from the latest 2.5 version to 2.6 are supported with all deployment types: RPM, containerized, and OpenShift Container Platform deployments.

See the upgrade document for your deployment type:

Upgrading from 2.4 to 2.6

Ansible Automation Platform supports upgrading directly from the latest 2.4 version to 2.6. Directly upgrading to 2.6 is the recommended upgrade path from 2.4, as a number of improvements in 2.6 simplify and improve the upgrade experience.

NOTE: You can upgrade directly from the latest 2.4 version to 2.6 with RPM and OpenShift Container Platform deployments. However, upgrading Event-Driven Ansible 2.4 or from the 2.4 containerized deployment is not supported, as both features were Tech Preview in 2.4.

See the upgrade document for your deployment type:

Upgrading from 2.4 to 2.6

Ansible Automation Platform RPM deployments require additional infrastructure compared with 2.4, due to the addition of the platform gateway service. Infrastructure needs vary depending on factors such as whether you implement a growth or an enterprise deployment.

NOTE: Additional infrastructure requirements apply only when upgrading RPM deployments.

See Infrastructure changes for details about infrastructure and inventory file changes in various upgrade scenarios.

Upgrading from 2.4 to 2.6

Enterprise authentication configuration and mappings (for example, SAML, LDAP, OIDC) move from automation controller 2.4 to platform gateway 2.6 as part of the upgrade process. You do not need to manually reconfigure these authentication methods after you upgrade.

NOTE: Authentication upgrade improvements apply to RPM and OpenShift Container Platform deployments. Upgrades from the 2.4 containerized deployment Tech Preview release are not supported. Additionally, upgrading Event-Driven Ansible 2.4 is not supported.

See Access management and authentication for information about authentication options in general.

Upgrading from 2.4 to 2.6

All automation controller Identity Access Management (IAM) data moves from automation controller 2.4 to the platform gateway in 2.6 as part of the upgrade process. With automation controller 2.4 as the default source of IAM data for the platform gateway in 2.6, users retain their memberships and are assigned appropriate platform-level roles in 2.6.

As part of the upgrade process:

  • Users, teams, organizations, their memberships, and common roles in 2.4 move from automation controller 2.4 to the platform gateway in 2.6.
  • Administrators in automation controller 2.4 become platform gateway administrators in 2.6.
  • Controller admins in 2.4 become platform gateway admins in 2.6.

The more organizations, teams, and users being migrated during an upgrade, the longer the upgrade takes. As an example, upgrading and migrating 4,000 users, 400 teams, and 40 organizations may take close to two hours.

NOTE: Identity access management changes apply to RPM and OpenShift Container Platform deployments. Upgrades from the 2.4 containerized deployment Tech Preview release are not supported.

See Data movement during upgrade for more information.

Upgrading from 2.4 to 2.6

Some APIs are being deprecated in 2.6.

See API changes for more information.

2.11. Platform UI
Copier lien

Ansible Automation Platform 2.6 was delivered with the goal to simplify the UI, improve the relationship between user interface elements, and maintain the association between users, organizations, teams, and roles.

Within the Platform UI, the role based access controls (RBAC) have been centralized to give administrators control of users across the entire platform. The centralized RBAC has introduced additional APIs and expanded the scope of those APIs to allow the assignment of roles across any of the platform resources. The details of these changes are reflected within the API changes.

The UI has also been updated to the latest version of Patternfly, which brings significant updates and refinements aiming to enhance user experience, performance, and developer efficiency.

Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat