Task #2314: Investigate packaging python dependencies in the python35 SCL - Pulp

Agile board
Agile charts

Agile boards

Pulp 2 QE Agile Board
Pulp 2 QE Agile Board - Priority View
Pulp 3 QE Agile Board
Pulp 3 RPM Tests Agile Board
Sprint 112 Agile Board

Custom queries

[All Projects] All Test Trackers
2.21.4 - Next Bugfix Release
2.21.4 MODIFIED
2.21.5
3.14.3
CI/CD
Easy Fix
FIPS open
Functional Tests
Galaxy NG
Groomed
Installer - Triage
Installer Items
Issues for Triage
Katello Integration
Next Docs Day
Operator issues
POST/ASSIGNED - no Sprint - Pulp2
POST/ASSIGNED - no Sprint - Pulp3
Prioritized Bugs
Pulp 3 Docs issues
Pulp2 issues available for next release
Pulpcore
SELinux related
Sprint 111
Sprint 112
Sprint Candidates (also groomed)
Un-Triaged Bugs
Verification Required

Actions

Send by e-mail Copy link

Task #2314

closed

Investigate packaging python dependencies in the python35 SCL

Added by semyers over 7 years ago. Updated about 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

pcreech

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Yes

Tags:

Sprint:

Sprint 9

Quarter:

Description

In particular, we should try to package celery into the SCL, and then test installing it and using it. (Testing on RHEL7 is sufficient).

History
Notes
Property changes

Actions

Copy link

Updated by semyers over 7 years ago

Tags Pulp 3 added

Actions

Copy link

Updated by pcreech over 7 years ago

Groomed changed from No to Yes

Actions

Copy link

Updated by mhrivnak over 7 years ago

Sprint/Milestone set to 27

Actions

Copy link

Updated by pcreech over 7 years ago

Status changed from NEW to ASSIGNED
Assignee set to pcreech

Actions

Copy link

Updated by pcreech over 7 years ago

I was able to build a python 3.5 software collection in copr, and subsequently build Django 1.8 and Celery and it's dependencies for the software collection, viewable here:

https://copr.fedorainfracloud.org/coprs/pcreech17/pulp-scl-demo/

I was also able to utilize these software collections in a demo project, https://github.com/pcreech/django-demo

This turned out to be fairly simple to build a python package against a software collection with a minimal spec file, which can be viewed here

http://copr-dist-git.fedorainfracloud.org/cgit/pcreech17/pulp-scl-demo/python-celery.git/tree/python-celery.spec?h=epel7

For any pulp dependencies that aren't a part of the main rh-python3* software collection, we can create a pulp software collection that depends on the rh-python3* software collection and then build subsequent packages against it, as referenced here:

https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/2/html/Software_Collections_Guide/sect-Using_a_Software_Collection_in_Your_Application.html

Actions

Copy link