Project

Profile

Help

Pulp RPM Roadmap

This is a living document that is moving towards a long term plan to develop RPM plugin for Pulp 3.0 and beyond.

K2 - Katello gap
K3 - Katello gap, lower priority than K2

Supported Content Types

MVP

Post-MVP

  • DRPM
  • Distribution (kickstart tree) - K2
  • Comps.xml content types (package group, environment, category, langpacks) - K2
  • Yum repo metadata file - K2
  • Modules - K2

Pulp RPM Plugin Use Cases

MVP

Sync
  • Basic Sync - K2
    • As an authenticated user, I can sync a remote yum/dnf repository
  • Sync types
    • As a user, I can exactly mirror the content of a remote repository. [provided by pulpcore] - K2
    • As a user, I can mirror the content of a remote repository with an additive behavior, so content is never removed locally. [provided by pulpcore] - K2
  • Download Behaviors
    • As a user, my sync task does not fail just because one download failed. [provided by pulpcore?] - K2
    • As a user, I can limit the number of concurrent downloads - K3
    • As a user, I can sync content on-demand by setting a repository's download policy - K2
Publish
  • As an authenticated user, I can publish a yum/dnf repository. - K2
  • As a user, I can specify relative path at which a repository will be served. [provided by pulpcore] - K2
  • As a user, I can configure if a repository will be served over an SSL or a non-SSL connection. [provided by pulpcore] - K2 (already done right?)
  • As user, I can sync from a yum/dnf repo published by Pulp. [should be taken into account for any publish story] - K2

Post-MVP

Sync
  • Basic Sync
    • As an authenticated user, I can sync a remote yum/dnf repository
      • DRPM
      • Distribution (kickstart tree)
      • Comps.xml content types (package group, environment, category, langpacks)
      • Yum repo metadata file
      • Modules
  • Sync behaviors
    • As a user, I can mirror only the most recent X versions that correspond to a particular rpm name.
    • As a user, I can force a full re-sync of a remote repository - K2
    • As a user, I can sync from a mirrorlist feed.
    • As a user, I can sync from a metalink URL to avoid a replay attack from a malicious mirror. [provided by pulpcore 3415]
    • As a user, I can sync only signed packages (RPM/DRPM/SRPM)
    • As a user, I can have sync skip one or more content types, e.g. drpm, errata, etc - K2
    • As a user, I can sync yum/dnf repository when only primary.xml is provided in repomd.xml - K3
  • Performance features
    • As a user, my sync will skip most of its work if the repomd.xml revision number has not changed is equal to or older (lower) than the previously successfully synced one. - K3
    • As a user, my sync is not skipped if it's a first sync - K2
    • As a user, my sync is not skipped if the importer configuration has changed since the last sync - K3
    • As a user, my sync is not skipped if any content has been removed from the repository since the last sync - K2
    • As a user, downloading of content starts quickly
  • Sync types
    • As a user, I can sync a kickstart tree from the same feed as other rpm/yum/dnf content. - K2
  • Download Behaviors
    • As a user, I can limit the maximum speed of downloading in bytes / sec - K3
    • As a user, I can specify the number of retries to be done before failing a given download
  • Checksum Features
    • As a user, I can sync a repository and have the files' checksums validated to ensure that no content is corrupt. - K3
  • GPG Signature Features
    • As a user, I can verify that repo metadata has a valid signature. (would be a new feature)
    • As a user, I can specify a set of trusted GPG keys. Any packages that are not signed with one of these keys is not synced.
  • Mirror List Support
    • As a plugin writer I can configure mirror lists and rotate between the mirrors
      • round robin support
      • nearest mirror support (GeoIP or ping times)
Publish
  • As an authenticated user, I can publish a yum/dnf repository.
    • DRPM
    • Distribution (kickstart tree) - K2
    • Comps.xml content types (package group, environment, category, langpacks) - K2
    • Yum repo metadata file - K2
    • Modules - K2
  • As a user, I can publish a repository incrementally (re-use the pre-existing metadata and only add additional units) [not relevant in Pulp3 world?]
  • As a user, I can force a full republish of a repository. - K3
  • As a user, my publish will skip most of its work if no changes to a repository were made since last publish. - K3
  • As a user, I can configure which checksum algorithm to use when creating metadata. - K2
  • As a user, I can configure which checksum algorithm to use when creating updateinfo.xml. - K2
  • Special publish for modules [TBD]
Export
  • As a user, I can export a repository or group of repositories to an ISO file (ISO 9660) - K3
  • As a user, I can export a repository or group of repositories to a DVD / Blueray file (UDF aka. ISO/IEC 13346) - K3
  • As a user, I can export a repository to a specified directory - K3
  • As a user, I can export a repositories content that is associated or updated (errata) since a specific datetime( aka incremental?) - K3
  • As a user, I can export RPM packages and errata as a set of JSON files
Upload
  • As an authenticated user, I can upload yum/dnf content types (not including Distribution) - K2
  • As an authenticated user, I can upload a comps.xml file and have it parsed into its constituent content units (requires knowledge of the destination repo at creation time)
Copy
  • As a user, I can copy a content of a specific type from one repository to another repository - K2
  • As a user, I can copy RPM packages and all their dependencies from one repository to another repository - K2
  • As a user, I can copy an Erratum and all the RPM packages it references from one repository to another repository
  • As a user, I can copy an Erratum and all the RPM packages it references and all the RPM dependencies from one repository to another repository - K2
  • Some content types create a new content unit in the destination repo instead of just copying, e.g. yum_repo_metadata_file
  • Special copy for modules [TBD]

Not much yet discussed use cases

Content Protection
  • As an authenticated user, I can use key based authentication to allow/disallow access to content served by the content app - K3
  • As an authenticated user, I can use user/password based authentication to allow/disallow access to content served by the content app.
Applicability
  • As an authenticated user, I can trigger an applicability for a consumer.
  • As an authenticated user, I can trigger an applicability for a repository.
Rsync Distributor
  • As a user i can distribute rpm content using a remote server.

Pulp 2 features not present in Pulp 3

  • "gpgkey" importer setting - only used by pulp-agent.
  • "generate_sqlite" - sqlite files are only used by yum as an optimization. DNF does not use them and has no plans to. Performance gains marginal.
    • they are also used by the "repoview" feature which we will also leave out of 3.0. Making browseable publications will hopefully be solved in the core.
  • As a user, I can have publish skip one or more content types, e.g. drpm, errata, etc
    • We can't think of a use case for this. Maybe export of only RPMs and Errata, see export use case.

Also available in: PDF HTML ODT TXT