Project

Profile

Help

Story #4908

closed

[Epic] As a user, I can manage modular content

Added by ppicka over 3 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
07/15/2019
Due date:
% Done:

100%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

All the use cases are described here: https://etherpad.net/p/modularity_use_cases

There are three types of modular content

- modulemd
- modulemd-defaults
- modular errata

Add possibility to manage all these modular types to pulp3.

For modulemd:
- sync
- publish
- copy (with artifacts, maybe (needs discussion) with module_defaults)
- recursive copy when depsolving is ready
- upload
- removal from a repo (with module artifacts)
- tracking a relationship between modulemd and its packages

For modulemd-defaults:
- sync
- publish
- ulpload
- simple copy/removal (provided by the core or general simple copy by rpm plugin)

For modular errata:
- sync
- publish
- upload
- simple copy/removal (provided by the core or general simple copy by rpm plugin)
- recursive copy when depsolving is ready


Subtasks 4 (0 open4 closed)

Task #4873: Add models for future use with modularityCLOSED - CURRENTRELEASEppicka

Actions
Task #5171: Extend UpdateRecord model to support modular advisoryCLOSED - CURRENTRELEASE

Actions
Story #5172: As a user, I can sync modular contentCLOSED - CURRENTRELEASEppicka

Actions
Story #5493: As a user, I can publish repository with modular contentCLOSED - CURRENTRELEASEppicka

Actions

Related issues

Related to RPM Support - Story #6271: As a user, I can upload modular contentCLOSED - DUPLICATE

Actions
Actions #1

Updated by ppicka over 3 years ago

  • Project changed from Pulp to RPM Support
Actions #2

Updated by ttereshc about 3 years ago

  • Subject changed from As a user I can manage modular content to [Epic] As a user, I can manage modular content
  • Description updated (diff)
Actions #3

Updated by ttereshc about 3 years ago

  • Sprint/Milestone set to Pulp 3.x RPM (Katello 3.16)
Actions #4

Updated by ttereshc about 3 years ago

  • Blocks Story #5127: {Epic] As a user, I can migrate all RPM plugin content from Pulp2 to Pulp3 added
Actions #5

Updated by ttereshc about 3 years ago

  • Blocks Story #5111: [Epic] As a user, I can calculate applicability added
Actions #6

Updated by ttereshc about 3 years ago

  • Blocks Story #4762: [Epic] As a user, I can copy content added
Actions #7

Updated by ttereshc about 3 years ago

  • Due date set to 09/23/2019
  • Start date set to 07/15/2019
Actions #8

Updated by ttereshc about 3 years ago

  • Description updated (diff)
Actions #9

Updated by ttereshc over 2 years ago

  • Blocks deleted (Story #4762: [Epic] As a user, I can copy content)
Actions #10

Updated by ttereshc over 2 years ago

  • Blocks deleted (Story #5127: {Epic] As a user, I can migrate all RPM plugin content from Pulp2 to Pulp3)
Actions #11

Updated by ttereshc over 2 years ago

  • Blocks deleted (Story #5111: [Epic] As a user, I can calculate applicability)
Actions #12

Updated by ttereshc over 2 years ago

  • Due date deleted (09/23/2019)
  • Sprint/Milestone deleted (Pulp 3.x RPM (Katello 3.16))
Actions #13

Updated by dalley over 2 years ago

What is the current status of this epic?

If the remaining issues (upload) are not immediately critical, perhaps it would be better to remove them from the epic and deal with them as a separate story, and close this one out to simplify the book-keeping.

The PR has been open for a while now, is that due to priorities or design struggles or just a lack of review? https://github.com/pulp/pulp_rpm/pull/1468

If it just needs review then we should go ahead and get it cleaned up and merged.

Actions #14

Updated by dalley over 2 years ago

  • Related to Story #6271: As a user, I can upload modular content added
Actions #15

Updated by dalley over 2 years ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE

Also available in: Atom PDF