Story #1997
closed
RFE: Need to get distribution info from cdn atomic tree
Description
Consider the contents of the atomic 'file' repo in the cdn staging url (see comment 1.) It has
- a pulp_manifest file listing the available/syncable artifacts in that repo
- a tree info file giving distribution information like name, version
Katello needs a way via pulp to easily recognize that this is a kickstart tree, and the name, version, and arch of that tree similar to what we get with current yum distributions.
- Related to Story #1769: As a user, I would like to be able to sync distribution trees added
So this is a very reasonable request and once we get our ducks in a row it should be easy. However, two things jump out at me from that repository that I'd really like to change before it gets set in stone.
1. Use the new treeinfo format (http://release-engineering.github.io/productmd/treeinfo-1.0.html). I assume this was built with pungi/lorax, but maybe not a recent-enough version.
2. No PULP_MANIFEST file. The treeinfo file should provide everything necessary to mirror the repository.
On our end, we need to work on #1769 and remodel how distributions work. Kickstart trees can (but are not required to) contain yum repositories. They're currently modeled to be contained by yum repositories in Pulp. I think that if we try to implement this RFE before doing the modeling work, it's going to be a real pain and will produce sub-par results. Once we've modeled it as it really is, this should "just work".
- Tracker changed from Issue to Story
Please rewrite this issue as a story with a complete set of deliverables.
This kind of combination repository should cause us to reconsider the restriction of having only one importer per repository. It's bad enough that the YUM importer handles distributions but adding distribution sync logic to the ostree importer is completely inappropriate. We need to discuss this.
- Status changed from NEW to CLOSED - WONTFIX
According to discussion with @paji today, this is no longer needed since they have #2211.
We are removing the 'API' category per open floor discussion June 16, 2020.
Also available in: Atom
PDF