Infrastructure

Infrastructure | Automation Orchestrator — Hub (Start Here)

Path 1: one JT for AO · Path 2: seed demos that actually run

View on GitHub
Author: Roger Lopez

Automation Orchestrator — Hub (Start Here)

Start here for Automation Orchestrator (AO) on the Ansible Product Demos catalog item from demo.redhat.com. OpenShift, credentials, and the AO execution environment are already wired.

Before either path: confirm AO templates exist — if not, run APD ǀ Multi-demo setup (or APD ǀ Single demo setup → infrastructure).

Path 1 — Just install AO

Stupid simple: one job template.

  1. Launch Infrastructure ǀ Automation Orchestrator ǀ Install.
  2. Open the AO URL from the job output and log in as admin with the printed password.

You now have AO. Seeded demo workflows may appear in AO, but they will not run end-to-end without Path 2 (no aws_rhel9, no Mattermost, and so on). Install warns on missing deps; it does not fail.

Skip Network Configuration on RHDP — Install already ran it.

Path 2 — Pre-seeded demos that actually run

Still simple — short cloud/chat setup, then Install, so curated content can hit a real host and post to chat.

  1. Run Deploy Cloud Stack in AWS, then sync AWS Inventory (aws_rhel9 for disk check / remediate).
  2. Launch Infrastructure ǀ AWS - Provision Mattermost (details) — Mattermost, Controller credential, and inventory host for Notify Chatroom. Save the Mattermost UI login from that job (apdadmin / Ansible123! by default) for when you open chat later.
  3. Launch Infrastructure ǀ Automation Orchestrator ǀ Install.
  4. Use the seed summary at the end of Install for AO URL / admin password (and Mattermost URL + default UI login when provisioned).
  5. Open the seeded workflow you want to show.

You are ready to present. Curated demos:

Demo Directions
Disk utilization Disk Utilization & Remediation

The three AO templates

Template When to use it Playbook
Infrastructure ǀ Automation Orchestrator ǀ Install Path 1 — stands up AO, wires AAP, seeds demos from demos.yml. install.yml
Infrastructure ǀ AO Network Configuration ǀ Install Rare re-run of allow-listing. Skip on RHDP. network-access.yml
Infrastructure ǀ Automation Orchestrator ǀ Uninstall Tear down AO when the lab session is done. Waits until the automation-orchestrator namespace is gone so Install can be re-run cleanly. uninstall.yml

Configure credentials

Credential Type On demo.redhat.com
OpenShift Credential OpenShift or Kubernetes API Bearer Token Pre-configured
AAP Credential Red Hat Ansible Automation Platform Pre-configured
Mattermost Custom (server + webhook id) Path 2 — created/updated by Provision Mattermost

Under the hood

What Install does when it seeds curated demos:

  • Reads demos.yml and seeds entries with enabled: true (today: disk-utilization from aap-orchestrator-demos).
  • Creates the AAP Orchestrator Demos project and those demo job templates in org Ansible Product Demos (APD).
  • Rewrites each workflow’s organization_name from Default → APD, then imports it into AO.
  • When present, attaches the Mattermost credential and Product Demos EE to Notify Chatroom.

AAP drives this with aapctl. The Mattermost credential stores an incoming webhook id for community.general.mattermost (not a bot personal access token).

See other Infrastructure demos

Browse all Infrastructure demos →

Workflow

flowchart LR
  P1["Path 1"] --> I1["AO Install"]
  I1 --> AO["AO ready"]
  P2["Path 2"] --> REQ["Setup deps"]
  REQ --> I2["AO Install"]
  I2 --> R["Ready to present"]
  style P1 fill:#2d2d2d,stroke:#888,color:#fff
  style I1 fill:#1e3a5f,stroke:#4a90d9,color:#fff
  style AO fill:#162c46,stroke:#58a6ff,color:#fff
  style P2 fill:#2d2d2d,stroke:#888,color:#fff
  style REQ fill:#1a3d2e,stroke:#3dd68c,color:#fff
  style I2 fill:#1e3a5f,stroke:#4a90d9,color:#fff
  style R fill:#162c46,stroke:#58a6ff,color:#fff
← All demos