Feature #9178
closedAs a user, I can use Katello to manage Python repositories
Description
Hello!
Pulp has recently released the first version of a new set of plugins that enable users to manage Python packages0. With these plugins, it is currently possible to upload Python packages to repositories, copy packages between repositories, delete packages from repositories, and publish repositories. pip can be used from a consumer machine to install the packages once the repository is published. The Pulp team is currently working on adding support for synchronizing packages from PyPI.
We would love to see Katello add support for this new content type. I'd be happy to offer assistance if it is needed.
Updated by Eric Helms over 9 years ago
- Category set to 91
- Triaged changed from No to Yes
First, apologies for taking so long to get to this, it slipped through my normal Redmine workflows. Based on our prior experiences adding yum, puppet and docker types:
1) Are there any caveats, anything special with respect to Python content type that we'd need to account for? I'd assume we would be creating 'Python repositories'.
2) Would users only upload Python packages? Does sync'ing a remote Python repository make sense? Can you point us at an example?
3) Would there be any special properties of Python repositories we'd want to expose to users? For example, for yum repositories we allow setting the checksum.
4) Is this available in an official release? Which one if so?
Updated by Randy Barlow over 9 years ago
First. apologies for taking so long to respond to your questions ☺
1) Yes, you would be creating Python repositories. The Python plugins do not include "consumer" support (yet), so there would not be any component for installing packages on systems.
2) It is possible to synchronize packages with PyPI:
3) All of the importer and unit attributes are documented here:
http://pulp-python.readthedocs.org/en/1.0-release/reference/index.html
There is really only one special setting for the importer, which is a list of packages you wish it to sync from PyPI. Other than that, it supports the usual importer settings that the platform supports.
4) The 1.0.0 release contains all of the above!
Updated by Eric Helms about 9 years ago
- Translation missing: en.field_release set to 86
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release changed from 86 to 114
Updated by dmitry Vasilets over 8 years ago
hello
i working on it. comment for avoid collisions and speed up progress
Updated by Kevin Carrasco almost 7 years ago
Hi guys, Any update on when this might be available on Katello?
Thanks.
Updated by Rene Jr Purcell about 6 years ago
dmitry Vasilets wrote:
hello
i working on it. comment for avoid collisions and speed up progress
Hi, is there anything we can do to help on this ? I'm not what I would call a good programmer but I can help with tests if you need to!
Updated by Ian Ballou 10 months ago
- Status changed from New to Resolved
- Assignee set to Ryan Verdile
- Target version deleted (
Katello Backlog)
Python content management was introduced in Katello 4.2. Closing out this issue.