Project

General

Profile

Bug #6680

Capsule installer should be it's own RPM

Added by Eric Helms almost 8 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Foreman Proxy Content
Target version:
Difficulty:
medium
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Related issues

Related to Katello - Feature #6781: Capsule: need method of restarting capsule services, akin to 'katello-services'Closed2014-07-25

History

#1 Updated by Eric Helms almost 8 years ago

  • Related to Feature #6781: Capsule: need method of restarting capsule services, akin to 'katello-services' added

#2 Updated by Eric Helms almost 8 years ago

  • Category set to Foreman Proxy Content
  • Target version set to 54
  • Difficulty set to medium
  • Triaged changed from No to Yes

#3 Updated by Eric Helms almost 8 years ago

  • Target version deleted (54)

#4 Updated by Stephen Benjamin over 7 years ago

I wouldn't really want to maintain another set of puppet modules separate from the katello-installer. I suppose we could build a capsule-installer RPM out of the katello-installer repository though.

However, I don't know if we should even be maintaing a capsule-installer: how much effort would it be to move this into foreman-installer?

It may take some effort, but it would be nice if deploying a Katello capsule wasn't a special thing. You'd just be deploying a normal foreman proxy, just with content support.

#5 Updated by Eric Helms over 6 years ago

  • Status changed from New to Resolved

#6 Updated by Eric Helms almost 6 years ago

  • Legacy Backlogs Release (now unused) set to 166

Also available in: Atom PDF