Project

Profile

Help

Maintenance: Planio will be observing a scheduled maintenance window this Tuesday, November 5, 2024 from 03:00 UTC until 06:30 UTC to perform urgent network maintenance in our primary data center. Your Planio account will be unavailable during this maintenance window.

Story #2384

closed

As a user I can sync manifest lists

Added by ipanova@redhat.com almost 8 years ago. Updated over 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0:00 h)
Platform Release:
2.14.0
Target Release - Docker:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 22
Quarter:

Description

As a result of this story, Pulp Docker will support manifests lists for sync, publish and copy.

https://docs.docker.com/registry/spec/manifest-v2-2/#manifest-list

To support manifest lists we need to:
1. Manifest list will be a new content type, so a Manifest list model should be defined.
2. During sync always make 3 requests to the registry and in each request set properly the headers( We would need to make 3 requests to support schema 1, schema2 and manifest lists)
- some parts of sync logic should be changed so it would correctly process manifest list and its image manifests
- also some changes would be needed to be done to the copy operation, so it would properly copy referenced image manifests in the list
- also some changes would need to be in the tagging of the manifest, so it would tag properly the manifest list and respect the fact that the tag is unique per repo
3. As a result of 3rd request we will have to save to the DB manifest list
4. Update Tag model, so it would be aware that it references a manifest list. Based on changes, write a migration.
5. Update apache config to set headers for published manifest list directory to reflect the correct Content-Type, similar to existing behavior with schema 1 vs 2
6. Change publish dir structure, so it would add a directory for manifest lists
7. Change the schema of the crane metadata file to add manifest lists
8. Change publish to create the new crane metadata file
9. Release notes and user docs
10. update crane metadata file docs


Sub-issues 1 (0 open1 closed)

Crane - Story #2385: Update crane to serve manifest listsCLOSED - CURRENTRELEASEipanova@redhat.com

Actions

Related issues

Blocked by Docker Support - Story #2099: As a user, I can sync v2 schema manifestsCLOSED - CURRENTRELEASEipanova@redhat.com

Actions
Copied to Docker Support - Story #2766: As a user I can sync and publish manifest listsCLOSED - WONTFIX

Actions
Actions #1

Updated by ipanova@redhat.com almost 8 years ago

  • Blocked by Story #2099: As a user, I can sync v2 schema manifests added
Actions #2

Updated by ipanova@redhat.com almost 8 years ago

  • Description updated (diff)
Actions #3

Updated by ipanova@redhat.com almost 8 years ago

I made it blocked by #2099 because of changes needed to be in Tag model

Actions #4

Updated by mhrivnak almost 8 years ago

  • Tracker changed from Issue to Story
  • % Done set to 0
Actions #5

Updated by mhrivnak over 7 years ago

  • Copied to Story #2766: As a user I can sync and publish manifest lists added
Actions #6

Updated by ipanova@redhat.com over 7 years ago

  • Description updated (diff)
Actions #7

Updated by ipanova@redhat.com over 7 years ago

  • Description updated (diff)
Actions #8

Updated by mhrivnak over 7 years ago

  • Description updated (diff)
Actions #9

Updated by bmbouter over 7 years ago

I'm not very familiar with this, but this issue reads like it has all the right parts. +1 to grooming.

Actions #10

Updated by mhrivnak over 7 years ago

  • Sprint/Milestone set to 40
  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes
Actions #11

Updated by ipanova@redhat.com over 7 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com
Actions #12

Updated by mhrivnak over 7 years ago

  • Sprint/Milestone changed from 40 to 41
Actions #13

Updated by ipanova@redhat.com over 7 years ago

  • Status changed from ASSIGNED to POST

Added by ipanova@redhat.com over 7 years ago

Revision 5cde929f | View on GitHub

As a user I can sync manifest lists.

closes #2384 https://pulp.plan.io/issues/2384

Added by ipanova@redhat.com over 7 years ago

Revision 5cde929f | View on GitHub

As a user I can sync manifest lists.

closes #2384 https://pulp.plan.io/issues/2384

Added by ipanova@redhat.com over 7 years ago

Revision 5cde929f | View on GitHub

As a user I can sync manifest lists.

closes #2384 https://pulp.plan.io/issues/2384

Added by ipanova@redhat.com over 7 years ago

Revision 5cde929f | View on GitHub

As a user I can sync manifest lists.

closes #2384 https://pulp.plan.io/issues/2384

Actions #14

Updated by ipanova@redhat.com over 7 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #16

Updated by pcreech over 7 years ago

  • Platform Release set to 2.14.0
Actions #17

Updated by pcreech over 7 years ago

  • Status changed from MODIFIED to 5
Actions #18

Updated by Ichimonji10 over 7 years ago

There are now automated tests for syncing and publishing Docker manifest lists. The most relevant changes are:

In addition, I've performed some manual testing. The manual testing was as simple as installing Docker, starting the Docker daemon, and executing docker pull localhost:5000/{repo_id} for several different repositories.

Actions #20

Updated by pcreech about 7 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #21

Updated by bmbouter over 6 years ago

  • Sprint set to Sprint 22
Actions #22

Updated by bmbouter over 6 years ago

  • Sprint/Milestone deleted (41)
Actions #23

Updated by bmbouter over 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF