3.1+ Ideas (post MVP)¶

Authentication¶

• External
• Expiring passwords
• REMOTE_USER support?

Authorization¶

<put ideas here>

Versioned Repository¶

As an authenticated user, I can get a list of a repo's versions.

As an authenticated user, I can specify how many versions to keep at a time.

As an authenticated user, I can get a reference to a new repo version from any task that adds or removes content.

As an authenticated user, I can publish a repo and have it default to the latest version.

As an authenticated user, I can run a publisher with a repository version.

Content Manipulation¶

• Sync can have "sync" options.
• Sync options are different than "importer" attributes.

Upload¶

• Allow for a large single file to have its chunks uploaded in parallel.

Importers¶

• Sync from multiple importers
• We need to support multiple importers to properly support distributions and ostree (with distributions).
• add auto-publish feature

Task Management¶

Allow filtering of tasks on 'completed' or 'started'. These 'meta' states are not states directly, but they represent a group of states. For instance 'completed' would be represent 'skipped', 'completed', 'failed', and 'canceled'.

Additional filtering support:

• worker
• started_at, filtered by less than, greater than
• finished_at, filtered by less than, greater than
• resource field on an associated ReservedResource

As an authenticated user I can DELETE a task

Task Scheduling¶

• As an authenticated user, I can schedule a task.

Data Exports¶

As an authenticated user, I can export a group of published repositories to a single media

As an authenticated user, I can export an incremental publish of a group of repositories to a single media

For both use cases ^, the layout needs some more discussion.

• maybe it is specified by the user?
• maybe it is maintains the published filesystem tree structure?

Also there are two main options in this area.

1. One is a publish bundler that bundles up all the units published to disk. Then this media (e.g. an iso) is mounted and brought into another Pulp installation using a sync. This will only work for content types that don't require 'live APIs'

2. Another option is to export database model data and disk content units from one Pulp to media and then import by directly adding those units to another Pulp. This could be done through the API possibly. This would allow things like Docker to be exported and imported, but it may not work for OSTree??

Also there was discussion about OSTree possibly never supporting and incremental export/import due to how OSTree stores content.

Server Plugins (which content types are available and importers and publishers)¶

Orphans¶

As an authenticated user, I can remove one or more units from one or more repositories

• filtering support on the unit(s)
• filtering support on the repositories

As an authenticated user, I can delete content units even when associated with repositories.

Plugin Download API¶

• FTP

Status API¶

Status API return status of Squid (aka Proxy), web server, streamer

API to view an overall health attribute that returns a message when something is not operating properly or True.

I can view information about unapplied migrations

I can view a verbose Status API which returns a Pulp version for each component along with a list of all plugins and their versions.

Alternate content source support¶