Bug 1338977

1. Proposed title of this feature request

Parameterize the candlepin database hostname
 

2.  (Next BZ update)
 

3. What is the nature and description of the request?

Add a parameter to the installer to allow for candlepin database host to differ from the hardcoded 'localhost' in the param.pp

   "We are looking to hosting postgres on a separate node. We were able to pass '--foreman-db-host'  to the katello-installer to get foreman to use a different DB node. However Candlepin, also uses postgresdb & the the hostname is hardcoded to localhost in '/usr/share/katello-installer/modules/candlepin/manifests/params.pp'. 

This should be parameterized as well, to enable users to choose a different DB node.  And the same applies to db_user & db_password."
 


4. Why does the customer need this? (List the business requirements here)

Customer is efforting the steps needed to split out the database onto a separate host, and feeding those steps back to engineering.   Changing the installer to allow a parameter so that something besides localhost can be specified is one of the necessary first steps.  This RFE is in concert with BZ#1052713 - which is the overall BZ for having a standalone database option for Satelite 6.
 

5. How would the customer like to achieve this? (List the functional requirements here)

   Either use the existing --foreman-db-host parameter for candlepin, or provide another installer parameter.
    
  
6. For each functional requirement listed in question 5, specify how Red Hat
and the customer can test to confirm the requirement is successfully implemented.

   When the parameter is specified from the command line, it will configure Candlpin to point to the remote server, where the database exists.
 

7. Is there already an existing RFE upstream or in Red Hat bugzilla?

   While there is an RFE for the overall effort to support a standalone database (BZ#1052713), this RFE is for just one particular aspect, with the hopes that it could be delivered separately.

8. Does the customer have any specific timeline dependencies?

   Ideally, they'd love for this to be in 6.2.z


9. Is the sales team involved in this request and do they have any additional input?

   Involved and aware.   No additional input.
 

10. List any affected packages or components.

     

11. Would the customer be able to assist in testing this functionality if implemented?

   Yes.