Bug 1396535

Summary:	[RFE] Incorporate required settings in puppet.conf without having to redo their config manually after every run of the satellite-installer.
Product:	Red Hat Satellite	Reporter:	Vishwanath <vmeghana>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, jcallaha, stbenjam
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-18 17:05:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vishwanath 2016-11-18 15:08:14 UTC

1. Proposed title of this feature request  
   Incorporate required settings in puppet.conf without having to redo their config manually after every run of the satellite-installer.
   
2. Who is the customer behind the request?  
  Account: NOMURA INTERNATIONAL PLC
  TAM customer: Yes
  SRM customer: No
  Strategic: Yes


3. What is the nature and description of the request? 
   After initial installation of Satellite/Capsule whenever satellite-installer command was run again in some scenarios eg: Satellite software upgrade, install custom SSL certificates. The /etc/puppet/puppet.conf was modified.


4. Why does the customer need this and how would the customer like to achieve this? ? (List the business and functional  requirements here)  
 This feature is requested as r10k is a standard tool came from Puppet and the customer wants a formally supported solution from Red Hat.
 Customer does not want to create his own workaround to address this issue.


5. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
 No.


6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
 No. Customer is addressing the issue by his own workaround right now.


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


8. List any affected packages or components.  
 NA.


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

Comment 2 Stephen Benjamin 2016-11-18 17:05:51 UTC

The installer is puppet-based itself and manages a number of configuration files, including puppet itself.  That means any changes you make are overwritten on an installer run, e.g. for an upgrade.

In many cases, we provide installer options to change the configuration to meet your needs and in those cases your configuration will persist, but puppet is not currently one of them because it's called from inside another puppet class.

There's a few classes we indirectly use like puppet and apache.

We have a solution for these using hiera, where users are able to set *any*  parameter in a YAML file. That's BZ1305782. It will most likely be available for 6.3, but could end up earlier in a possible z-Stream.

See https://bugzilla.redhat.com/show_bug.cgi?id=1305782#c14 and comments 15 and 16 for an understanding of how this works, but you'll be able to configure any of the options you want.

If for example, you want the agent to have a splay of 30, you would add this to custom-hiera.yaml:


  ---
  puppet::splaylimit: 30

You can look at /etc/foreman-installer/modules/puppet/manifests/init.pp to see what can be set for the puppet class. Nearly everything is configurable but if something isn't please file an RFE and we'll add it.


Thanks!

*** This bug has been marked as a duplicate of bug 1305782 ***