the basic configuration works, using the database deployed by the Tower installer, and self-signed certificates;
a more complex configuration with standalone/external database should be possible, but not tested. I didn't even look at the SSL configuration aspects.
I took also the chance to rename 'tower_database' to 'tower_database_host' which is clearer.
How should this be tested?
Add the tower_ah_... variables to your inventory and re-run the setup.
Is there a relevant Issue open for this?
n/a
Other Relevant info, PRs, etc.
The installation fails when installing a single node Tower with embedded database, and with the AH using the embedded database, because the setup playbooks don't open the firewall. I only added a commented out potential fix, subject to discussion (because @sean-m-sullivan said he needs the role to work without admin rights).
What does this PR do?
the basic configuration works, using the database deployed by the Tower installer, and self-signed certificates; a more complex configuration with standalone/external database should be possible, but not tested. I didn't even look at the SSL configuration aspects. I took also the chance to rename 'tower_database' to 'tower_database_host' which is clearer.
How should this be tested?
Add the
tower_ah_...
variables to your inventory and re-run the setup.Is there a relevant Issue open for this?
n/a
Other Relevant info, PRs, etc.
The installation fails when installing a single node Tower with embedded database, and with the AH using the embedded database, because the setup playbooks don't open the firewall. I only added a commented out potential fix, subject to discussion (because @sean-m-sullivan said he needs the role to work without admin rights).