Project

General

Profile

Actions

Bug #6178

closed

The installer should use puppetlabs modules where possible

Added by Walter Heck over 10 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Foreman modules
Target version:
-
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

Description

Right now, a few of the modules the foreman-installer uses are theforeman specific. This creates problems when you want to use theforeman/foreman module in a larger puppet repository, and not install theforeman through foreman-installer. If the modules were using the standard puppetlabs modules as much as possible that would be really much more usable. foreman-installer is great for a simple test install, but in production environments I would imagine anyone would want to configure foreman as part of a much larger repository.

Actions #1

Updated by Dominic Cleal over 10 years ago

Specifically which ones are you thinking of?

Actions #2

Updated by Walter Heck over 10 years ago

Specifically puppetlabs/puppet is the toughest, as you can't have puppetlabs/puppet and theforeman/puppet in a single repo, and they don't share the same classes or anything. puppetlabs/puppet doesn't currently have ENC functionality, but that shouldn't be hard to put in a pull request.

Less important is theforeman/concat_native vs puppetlabs/concat.

Actions #4

Updated by Anonymous over 7 years ago

  • Status changed from New to Resolved

I think all that's possible for now has been done.

Actions #5

Updated by Ewoud Kohl van Wijngaarden over 7 years ago

I'd like to merge theforeman-dhcp into voxpupuli-dhcp (formerly puppetlabs-dhcp) but we still need to merge quite a bit into their module that I think currently our module is of a higher quality. That means I agree that for now this can be closed.

Actions

Also available in: Atom PDF