Uploaded image for project: 'Ansible Automation Platform RFEs'
  1. Ansible Automation Platform RFEs
  2. AAPRFE-2345

RFE - Support a two-node multi-AZ Growth topology with HA in AAP 2.5+.

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 2.5
    • controller
    • False
    • Hide

      None

      Show
      None
    • False

      What is the nature and description of the request?

      • Officially support, test, and document a two-node, multi-AZ Growth topology for Red Hat Ansible Automation Platform (AAP) 2.5+ covering Gateway, Controller, and EDA.
      • Both nodes are active across two Availability Zones with shared RDS, HA job scheduling, and defined failover behavior.
      • Provide clear upgrade guarantees for this topology from 2.5 forward.

      Why does the customer need this? (List the business requirements here)

      • Achieve AZ-level resilience without the cost and operational overhead of the Enterprise topology at this scale.
      • Reduce EC2 compute costs while maintaining HA. Example: 6 instances vs 27 instances at ~$0.190/hr (m6a.xlarge) is roughly $10k/year vs $45k/year, a ~$35k/year difference before RDS, storage, and networking.
      • Keep the footprint smaller to meet sustainability and efficiency goals.
      • Have an explicit support stance to reduce risk during upgrades and incidents, and to plan for Redis removal.
      • Avoid the resilience gap of single-AZ Growth and manual failover.

      How would you like to achieve this? (List the functional requirements here)

      • Provide a tested reference design for a two-node, multi-AZ Growth topology using a shared RDS database.
      • Define HA and scheduler behavior for Controller across both nodes, including failure, drain, and recovery cases.
      • Document required network, latency, and health-check expectations between AZs for Receptor mesh, Gateway, Controller, and EDA.
      • Supply installer and upgrade guidance that validates this layout and preserves it during upgrades.
      • Publish sample inventory files, example diagrams, and operational runbooks for failover, maintenance, and upgrades.
      • Clarify supported limits and any constraints unique to two-node multi-AZ Growth.
      • Confirm compatibility and migration notes tied to Redis deprecation and future removal.

      List any affected known dependencies: Doc, UI etc.

      • Documentation: Tested deployment models, installer, Controller scheduler, Receptor mesh, Gateway routing, EDA clustering, external DB/RDS guidance, upgrade docs, and KB articles.
      • Installer/validation: Checks and flags for two-node multi-AZ Growth.
      • Operational tooling: Health checks, logs, and metrics guidance to verify HA behavior.
      • Support policy: Explicit statement that this topology is supported on 2.5+.

              bcoursen@redhat.com Brian Coursen
              rhn-support-johenson Joshua Henson
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: