Red Hat Ansible Automation Platform Database Scope of Coverage
What databases are supported by Red Hat Ansible Automation Platform, and what is supported when using them?
Ansible Automation Platform can work with two varieties of database:
Database, installed with Ansible Automation Platform
This database consists of a PostgreSQL installation done on the controller node, hub node, or separate node as part of Ansible Automation Platform installation using PostgreSQL packages provided by Red Hat.
An embedded database carries the following scope of coverage:
Covered by Red Hat | Not Covered by Red Hat |
---|---|
Installation | Replication configuration for HA or DR |
Upgrades as part of a full platform upgrade | HA/DR operation |
Backup and restore | Upgrades independent of platform upgrades1 |
Performance diagnosis and potential tuning |
Notes:
- Upgrading or customizing the Ansible Automation Platform-installed database manually, outside of a full platform upgrade that manages the database upgrade, renders the database "customer provided" and limits the supportability as such.
Customer-provided or configured database
This is an external database that is provided by the customer, whether on bare metal, virtual machine, container, or cloud hosted service.
When the Automation Platform is installed, the connectivity credentials for each database required for the platform are provided by the customer through documented models of Ansible Automation Platform installation types, i.e. RHEL, operator, etc. Customers are responsible for creating the databases, users, ownership permissions, and related db tasks prior to installing Ansible Automation Platform. No other database host or db configuration is performed by the Ansible Automation Platform.
A customer-provided database host may be:
- a customer-deployed HA or DR configuration using PostgreSQL packages provided by Red Hat
- a customer-provided PostgreSQL database provided by a customer-internal team
- a cloud-hosted PostgreSQL database
- a third-party PostgreSQL offering
A customer-provided database must be a PostgreSQL-compatible database of the appropriate version for the installed version of Ansible Automation Platform. See the Ansible Automation Platform installation documentation for database requirements for a specific version of Ansible Automation Platform. The database host/service should reside in the same data center/location/geography as the infrastructure hosting Ansible Automation Platform.
A customer provided database carries the following scope of coverage:
Covered by Red Hat | Not Covered by Red Hat |
---|---|
Platform configuration and platform operation connected to the database | Replication configuration for HA or DR |
Backup and restore (for Postgres versions that match what is supported by the Platform) | HA/DR operation |
Commercially reasonable performance diagnosis and potential tuning | Software and version upgrades |
Customized configurations and hardening |
Ansible Automation Platform connecting to a highly-available or disaster-recovery configured database is a supported configuration. In this scenario, support is limited to the connection to the database as described above. During troubleshooting, if issues are detected that are determined to be with the HA configuration or the underlying infrastructure, Red Hat may at their discretion provide suggestions, or refer the customer to their third-party database vendor, cloud provider, or other responsible organizations.
For covered operations, no support exceptions are required.
For more information, see the Red Hat Ansible Automation Platform Scope of Coverage.
Notes:
- If you are running a version of PostgreSQL different than noted tested versions in the Ansible Automation Platform minimum requirements, then platform functionality may not function as expected or at all.
Comments