Bug #6680: Capsule installer should be it's own RPM - Katello - Foreman

Actions

Copy link

Bug #6680

closed

Capsule installer should be it's own RPM

Added by Eric Helms about 10 years ago. Updated about 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Foreman Proxy Content

Target version:

Katello Recycle Bin

Difficulty:

medium

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Eric Helms about 10 years ago

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

Actions

Copy link

Updated by Eric Helms about 10 years ago

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

Actions

Copy link

Updated by Eric Helms about 10 years ago

Target version deleted (54)

Actions

Copy link

Updated by Stephen Benjamin almost 10 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.

Actions

Copy link