Where should the requirement for Puppet and/or PE be housed in the SIMP RPM stack?
- Trevor Vaughan
- Brandon Riden (Unlicensed)
Add your comments directly to the page. Include links to any relevant research, data, or feedback.
Background
At some point in the past, the simp-adapter RPM was created with the primary purpose of downloading the appropriate version of puppet for your system. This spawned two different RPM result sets of simp-adapter-foss and simp-adapter-pe both of which provide simp-adapter so that the underlying RPMs don't have to worry about figuring out which one is required.
As time progressed, this also became the focal point for 'common RPM materials' such as the (infamous) post-installation script that would copy files from where the RPM dropped them into the location that puppet expected.
When this was originally written, there were name changes on the puppet RPM front quite often and things were tremendously in flux. Since then, things have pretty much stabilized and we may be able to remove the strict requirement on PE components with guidance that the user needs to install them manually prior to SIMP installation. This would take away one 'easy button' but may make things easier to maintain over time.
Relevant data
The r10k materials are currently being added to simp-adapter since it is still the nexus of common RPM scripts and materials.
In general, users still want an "easy button" to installing the whole stack and we need to carefully pin versions. Additionally, the simp RPM is not a requirement for anything and has been designed as a strict meta-RPM for ease of use. The adapter took on the hard work for environments that wish to have a partial SIMP installation based around the RPM sets. This is completely valid, but may not be able to be fully supported. At this point though, we should be able to extract the supported puppet versions from the modules metadata.json if we haven't started already.
This was spawned by the conversation started on the initial r10k prototyping work PR.
As a corollary, we should probably take a good hard look at what the RPM is doing in the %post section and determine if this is actually still necessary and/or should be in this RPM instead of in the simp config command or the like.
Options considered
| Option 1: | Option 2: | Option 3: | |
|---|---|---|---|
| Description | Persist the simp-adapter-foss and simp-adapter-pe installation packages with puppet dependencies. | Push all puppet dependencies down to the individual modules | Push all puppet dependencies into the simp RPM. |
| Pros and cons |
|
|
|
| Estimated cost | SMALL | MEDIUM | HIGH |
Allows for a two-package installation of the entire stack if your repositories are set up correctly.
Having | Option 4: | Option 5: | Option 6: | |
|---|---|---|---|
| Description | Add a new RPM whose sole purpose is to pin the version of This was the original goal of | Remove simp-adapter-pe, making simp-adapter-foss default, and add a simp-adapter-unbounded to allow un-pinned versions of Puppet as stated in Option 4 | Remove any requirements for Puppet or Puppetserver and move validation to simp-cli |
| Pros and Cons |
| All Pluses/Minuses from Option 4, plus:
|
|
| Estimated cost | SMALL | SMALL | SMALL |