Task #1368
closed
Include Pulp in the Fedora Project
Status:
CLOSED - CURRENTRELEASE
Description
This ticket will serve as a tracker ticket for all the tasks that need to be completed to get Pulp included as part of the Fedora Project. Fedora is requesting to be able to have Pulp's upcoming Docker v2 support included in Fedora 24. Fedora 24 has a feature proposal deadline in January. The upcoming Docker v2 support will require Pulp 2.8, which may or may not be released by that time. It is currently unknown if a Fedora feature freeze is allowed to include a beta or not, so we should determine a timing strategy early on. The high level items are:
- Pulp's dependencies must all be included in Fedora.
- Some of Pulp dependencies have been patched to fix certain issues or add some features. These patches must be reviewed and must either get included upstream, get included by the Fedora maintainer, or Pulp must work around not having the patch.
- Pulp itself must go through and pass package review. We have been offered assistance by Adam Miller for this stage.
- Pulp 2.8 must be at beta by January. If Fedora requires only stable releases during feature freeze, it may also have to be released in order to make it into Fedora 24.
- pulp-docker 2.0 similarly needs to be ready by January.
I will file individual tickets for these items at a later time, and they will be listed as blocking this ticket.
Should Pulp continue to package its own SELinux policies, or does Fedora package all SELinux policies from all packages together into a single RPM?
- Blocked by Refactor #863: Convert pulp_docker to use MongoEngine models for units added
- Priority changed from Normal to High
rbarlow wrote:
Should Pulp continue to package its own SELinux policies, or does Fedora package all SELinux policies from all packages together into a single RPM?
I learned from maxamillion that it is not a requirement for Pulp's SELinux policies to be included in Fedora's core SELinux package, though that would be a good long term goal for us. Due to time constraints, we will not attempt to do this in Fedora 24.
- Blocked by Task #1370: Test Pulp with RabbitMQ added
- Description updated (diff)
Things are coming along smoothly in this work. I believe there are only a few outstanding issues and tasks that need to be taken care of:
- We need BZ#1285135 to be fixed in Fedora Rawhide. The maintainer seems to be absent, so I have filed BZ#1287148 so that I can take over as package maintainer. At this point it does seem that neither of the maintainers are going to respond, so I expect that I will be able to file the formal request to take over this package on Tuesday of next week. Therefore, I do not expect this to be a problem for Pulp getting into Fedora 24.
- Pulp needs to tag a beta release for both Pulp and pulp_docker so that the package review has a beta to build. Having betas for the other plugins would be nice to have but not required.
- Of course, we need to write spec files for whichever repos have betas ready, and file Fedora package review tickets. I do not expect this to be difficult but there will be a package review for each plugin in addition to the platform. For the purposes of our January timeline, it is only necessary to get pulp and pulp_docker accepted, so the others are "nice to have" and can reasonably be added at a later date if we are in a crunch.
- bmbouter is working with other Fedora packagers to get a newer version of python-celery and python-kombu in Fedora. Additionally, he is working with upstream to fix a bug that breaks disconnect support with qpidd. If Fedora's infrastructure team uses RabbitMQ, this effort will not affect them but this work would be good to get done nonetheless. Brian, do you have links to any upstream issues or BZs that you can add to this ticket?
- We should test Pulp with RabbitMQ, since we may recommend that Fedora consider it for a message broker given the qpidd instabilities that we've experienced (particularly in Fedora!). This one is taking a back seat to many of our other tasks so we may not get to it in time for the initial builds, but getting to it earlier in 2016 would be ideal.
The reconnect support of python-kombu being broken or not is not yet know. smyers is testing that currently to investigate. If it is broken an upstream bug will be filed and should be linked to here.
Separate from that, there is a user experience issue in upstream kombu where tracebacks are shown on a normal stop. That supposedly has gone away with 3.0.32 (current upstream release), so we're waiting to file a bug once we know if it is still an issue. smyers is also investigating that.
- Related to Issue #1386: python-kombu is newer on fedora23, so fedora23 is missing several bugfixes that our patches fix added
- % Done changed from 0 to 50
- Blocked by deleted (Task #1370: Test Pulp with RabbitMQ)
- Blocked by deleted (Refactor #863: Convert pulp_docker to use MongoEngine models for units)
- Related to deleted (Issue #1386: python-kombu is newer on fedora23, so fedora23 is missing several bugfixes that our patches fix)
- Status changed from ASSIGNED to CLOSED - CURRENTRELEASE
- % Done changed from 50 to 100
Also available in: Atom
PDF
.