The Foreman installer has an option to specify the remote database host where postgres (or others) live:
we need this to also be used when configuring the database the Katello engine uses as well as Candlepin.
This will allow us to support a database server that isn't the same machine as the Satellite 6 instance.
(In reply to Mike McCune from comment #0)
> The Foreman installer has an option to specify the remote database host
> where postgres (or others) live:
Hi Mike, just to clarify/follow up from IRC, is this BZ only for external Postgres DB - or Managed Postgres and External Oracle as well (i.e. all options currently offered as of Satellite 5.6 )?
There's been questions from support about customers who're on Satellite 5.6 with external dbs (Postgres or Oracle) about how to transition while keeping their db setup.
*** Bug 1331533 has been marked as a duplicate of this bug. ***
Please also do add gutterball to the list of DB's that need to have support to be on external DB's.
*** Bug 1338977 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/19667 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19667 has been resolved.
Moving back to Assigned due to some pending work on backup & restore.
Adding upstream issue for tracking progress on support for remote db in backup and restore scripts
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20550 has been resolved.
Upstream bug assigned to email@example.com
Upstream bug assigned to firstname.lastname@example.org
Updating $SUBJECT to be clear to what is being delivered. Satellite will ship with support for an external PostgreSQL database.
Support for Oracle databases are NOT planned for a near-term release of Satellite 6.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.