-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DESIGN] A phasing effect for publications that were recently served by a distribution. #911
Comments
I had a chance to think of a design. Feedback welcome. I'm imagining this will be released as a tech preview and is independent of the APT_BY_HASH feature we introduced. SettingWe'll introduce a new setting I think minutes probably makes sense and a default of 0 (at least initially). When using APT_BY_HASH, the recommendation should be 4320 minutes (3 days). ModelDistributedPublicationInherits from ModelBase.
Whenever a distribution is created/updated and publication_id is set or has changed, it will create a new DistributedPublication with the publication_id. Whenever a publication is created, it will check for any distributions where repo id matches the publication's repo id. For any match, a new DistributedPublication gets created. Content handlerThe distribution will have a content handler method to handle requests. When a request comes in, it'll search the artifacts for any completed publication for the particular distribution where If there are no matching distributed_publications or the code fails to find a matching artifact, the method returns letting the content app handle the request. |
Do we need to somehow discriminate between artifacts that should still be served, and artifacts that should no longer be served? |
My original thought was that pulp_deb would only serve old by-hash files but @mdellweg made the point that the publication should serve the old artifacts along with the old metadata. What if we introduce a second setting |
This all sounds good to me. |
Apt-by-hash is supposed to serve files at known locations for some time (order of days) after the corresponding publication has been replaced by a newer version. This can be accomplished by a distribution that can serve multiple publications like overlays, as long as it can be assured that the publications exist sufficiently long.
Originally posted by @mdellweg in #884 (comment)
The text was updated successfully, but these errors were encountered: