Bug 1243051 - [RFE] Management Puppet Environment Similar To Lifecycle Environments
Summary: [RFE] Management Puppet Environment Similar To Lifecycle Environments
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Configuration Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1316897
TreeView+ depends on / blocked
 
Reported: 2015-07-14 16:11 UTC by Dave Sullivan
Modified: 2019-08-12 16:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-03 17:33:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10364 0 None None None 2017-04-21 11:54:18 UTC

Description Dave Sullivan 2015-07-14 16:11:15 UTC
Description of problem:

I would like to put some ideas or may be feature request to manage puppet modules using CVs, below is what i am thinking ...

create puppet ENVs same as your life-cycle environments .. so it will be like "/etc/puppet/environments/{development, stage, production}" ... now when you upload puppet module to CV manage it like .. add puppet module to "/var/lib/pulp/puppet_modules" ( just an example to extract modules here )"

so once you push module from Library -> development create folder like

"/var/lib/pulp/puppet_modules/KT_ORG_development_CV_versionmodules/ntp"

and inside "/etc/puppet/environment/development/modules" create link for this ... ( somewhat similar how rpms are managed )

/etc/puppet/environment/development/modules/ntp -> /var/lib/pulp/puppet_modules/KT_ORG_development_CV_versionmodules/ntp ( soft link )

now the benefit of having this is

1) in GUI you will only have 3 ENVs to manage + "/etc/puppet/environments/" looks very easy to manage
2) if you just assign "development" ENV to a particular host or HostGroup, all modules inside that env will be available to that host or hostgroup ( currently with CV when you assign some ENV, you only have modules from that CV only and you lose other modules from different CV ( unless you have CCV, but that not possible to create every time as you always have to publish child and parent CV and very slow process with CCV of rhel rpms + puppet modules + application team's rpms + app team's puppet modules ).
3) you can still manage versioned CVs.
4) you can still use "roles" and access control similar + i think better way.


Version-Release number of selected component (if applicable):

As of 6.1 public beta



Additional info:

upstream BZ

http://projects.theforeman.org/issues/10364

Note the slow update to CVs may be get covered by these two BZs.

[RFE] assign multiple Content Views (CVs) to hosts / host groups 
https://bugzilla.redhat.com/show_bug.cgi?id=1203267

[RFE] Speed up publish Content View publish and promote especially important for Composite Content View 
https://bugzilla.redhat.com/show_bug.cgi?id=1241261

Comment 3 Bryan Kearney 2016-07-08 20:36:19 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 5 Ondřej Pražák 2017-04-21 11:54:14 UTC
Connecting redmine issue http://projects.theforeman.org/issues/10364 from this bug

Comment 6 Bryan Kearney 2018-05-03 17:33:59 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.