Foreman can connect to a local database or can be configured and installed using a remote database host with the following option in the installer: --foreman-db-host but we need to add this to the documentation in the new installer instructions to include how to setup a Satellite 6 to use a database that is *not* on the local system. Need to detail out the ramifications of using that flag during installation and how to ensure firewalls and networking is setup correctly so Foreman and other Satellite 6 service can connect to a remote Postgres server.
FWIW, Satellite 5.6 docs for reference (including requirements and install instructions) - https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/5.6/html-single/Installation_Guide/index.html#sect-Installation_Guide-Hardware_Requirements
Hi Mike, Xixi, In order to add this into the Installation Guide, I need the information as soon as I can. Preferably by next week. My questions at the moment: 1. Add "Database Requirements" section in Prerequisites - what are the sizing requirements for the external database? - what are the pre-installation configuration required for the externall database - firewall and networking requirements 2. Other than adding --foreman-db-host added to katello-installer, what else is needed? - what are the issues that come with using this flag - is this supported? 3. If they install from the ISO image, how do they install with an external database? Please also review the proposed changes to the Table of COntents to accommodate this: Chapter: Red Hat Satellite Installation Section: Connected Satellite Installation Section: Data Management Options at Installation Installing a Connected Satellite Server with the Managed Database [9711] Installing a Connected Satellite Server with an External Database Section: Disconnected Satellite Installation Section: Data Management Options at Installation Installing a Disconnected Satellite Server with the Managed Database [15772] Installing a Disconnected Satellite Server with an External Database
This bug has now been open for three years, and the original engineering bug on which this bug depends is on 'ASSIGNED' status. I will close this bug in its role as a tracker for now, but we understand this is an important use case, and will raise a tracker or re-open this bug when the engineering bug has been addressed.