Project

General

Profile

Feature #10364

Suggestions for managing puppet modules using CVs

Added by Dhaval Joshi over 4 years ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
-
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Hello,

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.

Please comment if this is possible to implement ?? and vote please.

Regards,
DJ

History

#1 Updated by Dominic Cleal over 4 years ago

  • Project changed from Foreman to Katello
  • Category deleted (Puppet integration)
  • Triaged set to No

#2 Updated by Eric Helms about 4 years ago

  • Category set to Puppet
  • Status changed from New to Needs design
  • Triaged changed from No to Yes

#3 Updated by Eric Helms almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 114

#4 Updated by Ondřej Pražák over 2 years ago

  • Bugzilla link set to 1243051

#5 Updated by John Mitsch about 2 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from Needs design to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF