Project

General

Profile

Feature #7784

As a fortello user, I want to be able to install fortello without docker functionality

Added by David Davis over 7 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Container
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Related issues

Related to Katello - Feature #9413: Create an API by which katello plugins can add content types to katelloRejected
Blocks Katello - Tracker #7125: Docker Content SupportReady For Testing

History

#1 Updated by David Davis over 7 years ago

  • Tracker changed from Bug to Feature

#2 Updated by David Davis over 7 years ago

#3 Updated by David Davis about 7 years ago

#4 Updated by David Davis about 7 years ago

#6 Updated by David Davis about 7 years ago

From #9406:

Right now rubygem-katello requires %{?scl_prefix}rubygem-foreman_docker which causes the Docker functionality to be installed in all cases Katello is installed.

We need to support katello-sam which does not include Docker Content management or provisioning.

1) need to have this requirement hang off the 'katello' meta RPM and not the rubygem if we want main Katello to require it

2) need to ensure that the Content -> Docker Tags menu item does not show up if the foreman_docker plugin is not installed

#7 Updated by David Davis about 7 years ago

  • Priority changed from Low to Normal
  • Legacy Backlogs Release (now unused) set to 23
  • Bugzilla link set to 1193236

#8 Updated by David Davis about 7 years ago

Justin's comment in http://projects.theforeman.org/issues/9406#note-4:

Wouldn't this involve making the docker aspect of katello plugable as well?

I can't imagine even the migrations will work properly in its current state.

#9 Updated by David Davis about 7 years ago

  • Assignee set to David Davis

#10 Updated by Mike McCune about 7 years ago

I accidentally deleted the referenced issue, apologies. we can use this issue to track since it was there originally.

#11 Updated by David Davis about 7 years ago

I'm not sure what to do about the migrations. Would we:

1. Move the katello docker migrations into the katello_docker plugin but then we'd have to find any code in Katello that refers to docker columns and fence it off.
2. Leave the katello docker migrations in Katello but we'd still have to require foreman_docker as our migrations depend on those. I guess we could fence them off (check if we have katello_docker).

In addition, 2 would mean that you couldn't add katello_docker after the fact.

#12 Updated by David Davis about 7 years ago

  • Related to Feature #9413: Create an API by which katello plugins can add content types to katello added

#13 Updated by Eric Helms about 7 years ago

  • Legacy Backlogs Release (now unused) changed from 23 to 31

#14 Updated by Eric Helms about 7 years ago

  • Legacy Backlogs Release (now unused) deleted (31)
  • Triaged changed from No to Yes

#15 Updated by Eric Helms over 6 years ago

  • Legacy Backlogs Release (now unused) set to 114

#16 Updated by Thomas McKay almost 4 years ago

  • Legacy Backlogs Release (now unused) changed from 114 to 166
  • Status changed from New to Rejected

old issue

Also available in: Atom PDF