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. On demo.redhat.com, Install also wires the pre-filled Controller LiteMaaS credential into AO as an LLM Provider integration so agentic (AI) workflow nodes can run. The Install job template must have LiteMaaS attached (APD setup on this branch does that). If the seed summary says LLM was not wired, re-run Install once after setup so the virtual key injects. Seeded demo workflows may still need Path 2 for cloud/chat deps (aws-rhel9, 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 real hosts (and chat when the demo needs it).

1. Ensure APD ǀ Multi-demo setup (or Single → cloud + infrastructure) created the **Cloud

   AWS

   *** patch/snapshot JTs.

2. Run Deploy Cloud Stack in AWS.
3. For demos that post to chat (disk-utilization): launch Infrastructure ǀ AWS - Provision Mattermost (details). Skip for Multi-OS Cloud Patching.
4. Launch Infrastructure ǀ Automation Orchestrator ǀ Install.
5. Use the seed summary at the end of Install for AO URL / admin password (and Mattermost URL + login when provisioned).
6. Open the seeded workflow you want to show.

You are ready to present. Curated demos:

Task Step Example — LiteMaaS smoke test

No cloud stack. After Install, open Task Step Example, leave the default question (or edit it), and Run. Seed injects both the model (llm_model_id) and the APD LiteMaaS LLM Provider credential (credential_id) on the AI task step — model alone is not enough to call LiteMaaS.

Multi-OS Cloud Patching — manual trigger

The seeded workflow pre-fills inventory limits for the cloud stack. Set aws_region to the region where you deployed the stack, then run:

{
  "_hosts": "aws-rhel9:aws-rhel10",
  "_hosts_windows": "aws-dc:aws_win1",
  "_report_server": "reports",
  "aws_region": "<your region>"
}

The three AO templates

Configure credentials

Under the hood

What Install does when it seeds curated demos:

• Reads demos.yml and seeds entries with enabled: true from aap-orchestrator-demos (disk-utilization, multi-os-cloud-patching) plus local workflows such as Task Step Example.

• Creates the AAP Orchestrator Demos project and any demo-owned job templates (disk-utilization playbooks). Multi-OS reuses existing **Cloud

  AWS

  *** templates from cloud setup — seed only imports the workflow.

• Wires AO-native AAP and LiteMaaS (LLM Provider) integrations; allow-lists the LiteMaaS hostname for AO workers.
• Rewrites each workflow’s AAP org/credential placeholders → APD, and fills llm_model_id on agentic nodes when LiteMaaS is wired, then imports 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). Controller LiteMaaS is the source of truth for the virtual key; AO gets a copy as APD LiteMaaS during Install.

See other Infrastructure demos

Browse all Infrastructure demos →