Project

General

Profile

Actions

Refactor #21399

open

Consolidate required yum repositores

Added by James Shewey over 6 years ago. Updated over 6 years ago.

Status:
Needs design
Priority:
Normal
Assignee:
-
Category:
Packaging
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

In order to install The Foreman on CentOS, no less than 14 separate repositories are needed. This problem has been growing for some time: For example, earlier versions of foreman did not require the installation of pulp beyond what was in the EPEL repositories. In the current nightly build, puppet-agent is now required which requires now a 15th source. These repositories are sourced from 5 different providers: CentOS, SCLo, Puppet, Katello and The Foreman. The SCLo repositories can be particularly challenging, and if any one of the aforementioned 5 parties has a problem, installation is not possible. It is also not readily apparent to users who may be upgrading from an old version to a newer version that a new repo is now required. This makes installation unnecessarily difficult and adoption and community involvement suffer as a result.

The obvious (to me) solution is to expand The Foreman's repo to include all of the needed packages and dependencies, including those published by other projects. Any updates they publish can be synced into The Foreman's repository on a nightly basis. The point of a yum repository is to allow yum to resolve dependencies for the user instead of forcing the user to resolve dependencies themselves. By requiring such a multiplicity of sources we are inadvertently forcing users back into the dark ages of having to resolve rpm dependencies manually. It also increases the likelihood for error by the user in that a single error in the .repo file. This change would also make it easier for security minded companies that whitelist URLs or IPs in that it significantly reduces the IPs and/or URLs needed to be authorized in any firewalls.

All told, I have spent at least two weeks merely trying to resolve repo issues.

Actions #1

Updated by James Shewey over 6 years ago

  • Subject changed from But in yum repo configuration to Bug in yum repo configuration
Actions #2

Updated by Marek Hulán over 6 years ago

  • Category set to Packaging
  • translation missing: en.field_release deleted (297)
  • Difficulty deleted (easy)

I don't think it's easy. Also it would cause a lot of extra effort of maintaining all packages ourselves. Maybe the vendorizing would help, see foreman-dev mailing list if you're interested.

Actions #3

Updated by Anonymous over 6 years ago

  • Tracker changed from Bug to Refactor
  • Subject changed from Bug in yum repo configuration to Consolidate required yum repositores
  • Status changed from New to Needs design
Actions

Also available in: Atom PDF