You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Managing multiple AAP instances (dev,test,prod) or in different network zones is a challenge. The tasks often performed are:
start, stop, and restart of services
healthchecks
etc
Basic "Day 2" operations on AAP platform.
So, for example, I want to bring AAP down for some maintenance or whatnot, perhaps I run a playbook that ensures all running jobs are stopped, no new jobs are running, and then I shutdown the web layer (controller), the app layer (exec nodes) and then database layer (postgres) in that order to ensure a clean shutdown sequence. A playbook like that would be cool, which uses roles that support managing the different services (postgres, etc)
Or maybe I just want to bounce the postgres database service. Use a playbook/role for that. "aap_manage_postgres.yml" playbook would be called with extra var mode=restart for example.
The text was updated successfully, but these errors were encountered:
Managing multiple AAP instances (dev,test,prod) or in different network zones is a challenge. The tasks often performed are:
Basic "Day 2" operations on AAP platform.
So, for example, I want to bring AAP down for some maintenance or whatnot, perhaps I run a playbook that ensures all running jobs are stopped, no new jobs are running, and then I shutdown the web layer (controller), the app layer (exec nodes) and then database layer (postgres) in that order to ensure a clean shutdown sequence. A playbook like that would be cool, which uses roles that support managing the different services (postgres, etc)
Or maybe I just want to bounce the postgres database service. Use a playbook/role for that. "aap_manage_postgres.yml" playbook would be called with extra var
mode=restart
for example.The text was updated successfully, but these errors were encountered: