Project

Profile

Help

Story #2602

As a user, I want docker repos to have "mirror on sync"

Added by tomckay@redhat.com over 2 years ago. Updated 7 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Target Release - Docker:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

When an image is synced from a registry, an option to allow only the maintaining of manifests and tags that exist in the upstream registry to exist after sync.


Checklist

History

#2 Updated by mhrivnak over 2 years ago

  • Tracker changed from Issue to Story
  • % Done set to 0

#3 Updated by bmbouter over 2 years ago

How will the feature be enabled? Is it an importer option? What will the option be named?

#4 Updated by tomckay@redhat.com over 2 years ago

I assume the feature would be exactly equivalent to the RPM feature. Are there differences I'm unaware of? "What I have locally after the sync is equal to what I have remotely."

Looking at the rpm docs i see "remove_missing" as the equivalent. I am not familiar with the details in this area just the higher level concept need. If there are other options that pair with that one, please note them.

Thanks!

#5 Updated by bmbouter over 2 years ago

For reference here are the rpm docs: http://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/yum-plugins.html?highlight=remove_missing

OK so to make it exactly like the rpm feature, the feature request is to add a field called remove_missing which will perform the following:

If True, as the repository is synchronized, old <things> will be removed. Valid values to this option are True and False; defaults to False

What are the <things> in ^ that need to be removed? Blobs, tags, layers, all of these? I think if we can clarify that, I would see it clearly enough to groom it.

#6 Updated by tomckay@redhat.com over 2 years ago

Yes, I would say all of the artifacts in the repo should match. The result should be zero difference between a new repo created and synced and this repo re-synced.

#7 Updated by mhrivnak over 2 years ago

bmbouter wrote:

For reference here are the rpm docs: http://docs.pulpproject.org/plugins/pulp_rpm/tech-reference/yum-plugins.html?highlight=remove_missing

OK so to make it exactly like the rpm feature, the feature request is to add a field called remove_missing which will perform the following:

[...]

What are the <things> in ^ that need to be removed? Blobs, tags, layers, all of these? I think if we can clarify that, I would see it clearly enough to groom it.

Rather than "old things", I think it should be "any local content not present in the remote repo".

#8 Updated by bmbouter over 2 years ago

  • Groomed changed from No to Yes

Thanks for the responses. So to recap the feature: the docker_importer will have a new option added called remove_missing which will perform the following:

If True, as the repository is synchronized, any local content not present in the remote repository will be removed. Valid values to this option are True and False; defaults to False

I touched up the checklist items some and I'm marking it as groomed. If there are other questions or comments please post.

#9 Updated by bmbouter 7 months ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF