Project

Profile

Help

Task #2338

Create pulp software collection

Added by pcreech about 3 years ago. Updated 6 months ago.

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

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 10

Description

Based on the research in https://pulp.plan.io/issues/2314 we can create a pulp software collection to be used on EL7 machines

Work needs to be done setting up an official Pulp software collection in copr.

First, a pulp scl meta package needs to be created (that depends on the rh-python35 software collection)

After this package is created, django and celery will need to be built in the scl:

python-django 1.8
python-celery
python-kombu
python-pytz
python-amqp
python-billiard

There is also the opportunity to get some or all of these packages included in the main rh-python35 scl


Checklist

History

#1 Updated by pcreech about 3 years ago

  • Sprint Candidate changed from No to Yes

#2 Updated by bmbouter about 3 years ago

  • Description updated (diff)
  • Groomed changed from No to Yes

#3 Updated by mhrivnak almost 3 years ago

  • Sprint/Milestone set to 28

#4 Updated by pcreech almost 3 years ago

  • Checklist item pulp scl meta package set to Done

#5 Updated by pcreech almost 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to pcreech

#7 Updated by bmbouter almost 3 years ago

I was reading on epel-devel this morning and I read this0 which identifies that RHSCL is a product versus softwarecollections.org which is like EPEL but for software collections. Which one of these is our SCL work being based on?

[0]: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/M4ACZBF3SK6R6FMIZSHI5W4HRZYKQ5BP/

#8 Updated by pcreech almost 3 years ago

Yes, there are two repositories with software collections in them. There's Red Hat's official software collection, and then there's the softwarecollections.org's software collections.

A quick way of explaining it is the RH software collections are the base, and softwarecollection.org's are extras, much like the epel's relationship to base packages.

pulp-scl is dependent on the rh-python35(0) software collection supported/supplied by Redhat, as this is the only python3.5 software collection. This will be updated to rh-python36 when that is released

If/when an el6 collection is created, it will be dependent upon rh-python34 (the last python3 on el6)

Pulp's scl itself will not live in either of those, as it is product-specific to pulp and will live within our current distribution streams for packages (i.e. copr(1) )

(0) https://www.softwarecollections.org/en/scls/rhscl/rh-python35/
(1) https://copr.fedorainfracloud.org/coprs/g/pulp/scl/

#9 Updated by bmbouter almost 3 years ago

Thanks @pcreech. That is helpful. OK so now I'm left with a couple of confirmation questions.

1. It sounds like we'll be distributing our scl side-by-side our other Pulp bits. Is that right? That sounds good, but I wanted to check my understanding.

2. Is the pulp-scl just going to be one big rpm?

#11 Updated by pcreech almost 3 years ago

1. Sure! With the caveat of this is all NEW stuff for pulp3, and those decisions haven't been 100% talked about or made officially. This task is really focused on just creating the official collection after the first proof of concept, not distributing it

2. No! It will be multiple rpms. The short explanation is pulp-scl{,-build,-sclbuild,-runtime} are just rpms for setting up the SCL environment. There will be other rpms that are built in the environment, like is done in the python scl(0) that are the python packages we will use.

For more questions on scl's in general, I highly recommend experimenting with them and using them.

(0)http://bay.uchicago.edu/centos-vault/centos/7/sclo/Source/rh/rh-python35/

#13 Updated by bmbouter almost 3 years ago

All that sounds good, thanks @pcreech!

#14 Updated by pcreech almost 3 years ago

  • Checklist item python-django set to Done

#16 Updated by pcreech almost 3 years ago

  • Checklist item python-billiard set to Done

#17 Updated by pcreech almost 3 years ago

  • Checklist item python-billiard set to Not done

#18 Updated by pcreech almost 3 years ago

  • Checklist item python-billiard set to Done

#19 Updated by pcreech almost 3 years ago

  • Checklist item python-anyjson added

#20 Updated by pcreech almost 3 years ago

  • Checklist item python-anyjson set to Done

#21 Updated by pcreech almost 3 years ago

  • Checklist item python-amqp set to Done

#22 Updated by pcreech almost 3 years ago

  • Checklist item python-kombu set to Done

#23 Updated by pcreech almost 3 years ago

  • Checklist item python-pytz set to Done

#24 Updated by pcreech almost 3 years ago

  • Checklist item python-celery set to Done

#25 Updated by pcreech almost 3 years ago

  • Status changed from ASSIGNED to POST

#26 Updated by pcreech over 2 years ago

  • Status changed from POST to CLOSED - COMPLETE

#27 Updated by bmbouter over 1 year ago

  • Sprint set to Sprint 10

#28 Updated by bmbouter over 1 year ago

  • Sprint/Milestone deleted (28)

#29 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#30 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF