Ansible Tower
Sources: Deploying Ansible Playbooks to Tower (TRIB 53283351) · RaaS Ansible Deployment Playbook — Azure (TRIB 20936164989) · Run Ad-Hoc Ansible Playbook — Azure (TRIB 20936884240)
Tower Instances
| Tower URL | Region |
|---|---|
https://tower.us.raas.rhapsody.global |
US |
https://tower.uk.raas.rhapsody.global |
UK / EU |
Access is via your firstname.lastname@lyniate.com credentials.
Key Job Templates
| Template | Purpose |
|---|---|
| Deploy Rhapsody | Primary deployment playbook (deploy-raas.yml) |
| Rhapsody - Configure Strongswan | Reconfigure VPN / IPSec tunnels |
| Rhapsody - Update DNS and inventory | Update DNS records and Ansible inventory |
| MAINTENANCE - Service State | Start/stop services during maintenance windows |
| Create RaaS customer SMTP access | Create SES identity + store SMTP credentials in Parameter Store |
| Apply Coralogix Stack | Install/update OTEL collector on instances |
| Rhapsody Smoke Test | Post-deployment health checks |
AWS Deploy Playbook (deploy-raas.yml)
The core deployment playbook runs against all RaaS instances with remote_user: azureuser (AWS instances use the same parameter despite the azureuser name for consistency).
Playbook Tasks (37 total)
The playbook covers the full provisioning lifecycle:
| Category | Tasks |
|---|---|
| Security | SentinelOne EDR install/update |
| OS Config | Timezone, packages, hostname, /etc/hosts |
| Storage | Mount managed disk (/data/orionhealth), mount Azure NetApp Files (NFS) if applicable |
| File Transfer | azcopy install |
| Rhapsody | Install Rhapsody engine, licence, config |
| Observability | Coralogix OTEL role deployment |
| High Availability | HA role discovery via IMDS VM tags — sets ha_role (primary/secondary) and storage_backend |
| Backups | Backup schedule configuration |
| Logging | Log forwarding setup, postfix mail relay |
| HTTPS | Rhapsody port configuration (8444) |
HA Role Discovery
HA role (primary/secondary) is determined at runtime from VM tags via the Instance Metadata Service (IMDS). The playbook reads the ha_role tag from AWS and configures Rhapsody accordingly.
If the tag is missing or incorrect, HA will not be configured as expected — verify tags in the AWS console before running.
Azure Composite Action (run-ansible-playbook)
For Azure RaaS, Ansible playbooks are run via a GitHub Actions composite action rather than directly through Tower.
Inputs
| Input | Purpose |
|---|---|
PLAYBOOK_PATH |
Path to the playbook YAML (relative to repo root) |
INVENTORY_PATH |
Path to the Ansible inventory |
TARGET_HOST |
Hostname or group to limit execution to |
EXTRA_VARS |
JSON string of extra variables |
Outputs
| Output | Description |
|---|---|
exit_code |
Ansible exit code (0 = success) |
output_file |
Path to the captured playbook output log |
Workflows Using This Action
The following GitHub Actions workflows invoke run-ansible-playbook:
asr-failovercertificate(certificate renewal/deployment)disk-resizemaintenance-ssh-keyrhapsody-upgradeconnectivity(VPN/networking checks)download-s3coralogix-stack(Apply Coralogix Stack)strongswan-configureupdate-dns-inventorysmoke-testses-credentialsha-failoverbootstrap-rerunmaintenance-mode
Tip
Use the composite action for any new Azure automation that requires Ansible — it handles authentication, SSH key injection, and output capture consistently.