Project

Profile

Help

Task #931

Investigate and develop a plan for Pulp to use Software Collections

Added by rbarlow over 5 years ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 1
Quarter:

Description

It would reduce the cost of developing Pulp if we could use Software Collections to standardize on the versions of Python and some of our dependencies (such as Django). In the short term, it would allow us to use Python 2.7 for all of our code with likely relatively little effort. In the long term, it will enable us to migrate to Python 3. The long term goal is important as Fedora will soon switch to Python 3 by default. Python 3 also introduces some nice new features that would be beneficial to us[citation-needed].

For the purposes of this task, we'll consider only the short term goal of possibly using Python 2.7 and a newer version of Django. The output of this task should be an actionable story that will deliver the work necessary for Pulp to use Python 2.7 and Django from Software Collections in RHEL 6/7 and CentOS 6/7.

Deliver a filed story in Redmine that takes the following into consideration:

  • Availability of Software Collections for our supported operating systems
  • Decide whether we should require SCs for just the server, or should pulp-admin require it too?
  • Try out SCs in our supported OSes with Pulp, and report how that went
  • Find out what we need to do to communicate to Satellite and our community users that SCs are required now
  • Consider which version of Pulp this requirement should be introduced with (3?)

Might be helpful: http://developerblog.redhat.com/add-packages-to-python-2-7-software-collection/


Related issues

Blocks Pulp - Issue #1135: Pulp's unit tests are not compatible with Mock>=1.1.0CLOSED - WONTFIX<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by bmbouter over 5 years ago

  • Sprint Candidate set to Yes
  • Tags deleted (Sprint Candidate)

#2 Updated by bmbouter over 5 years ago

  • Groomed set to No

#3 Updated by mhrivnak over 5 years ago

  • Groomed changed from No to Yes

#4 Updated by mhrivnak over 5 years ago

  • Description updated (diff)

#5 Updated by amacdona@redhat.com almost 5 years ago

  • Blocks Issue #1135: Pulp's unit tests are not compatible with Mock>=1.1.0 added

#6 Updated by mhrivnak over 4 years ago

  • Sprint/Milestone set to 19

#7 Updated by jcline@redhat.com over 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to jcline@redhat.com

#8 Updated by jcline@redhat.com over 4 years ago

  • Status changed from ASSIGNED to CLOSED - CURRENTRELEASE
  • % Done changed from 0 to 100

I'm not really sure how to close this since the result is a story. I chose 'CLOSED - CURRENTRELEASE', but feel free to change it if you don't feel that's appropriate.

https://pulp.plan.io/issues/1852

#9 Updated by bmbouter over 2 years ago

  • Sprint set to Sprint 1

#10 Updated by bmbouter over 2 years ago

  • Sprint/Milestone deleted (19)

#11 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF