Skip to content
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

[RFE] yum plugins and metadata expiration #276

Open
pgera opened this issue Oct 28, 2018 · 1 comment
Open

[RFE] yum plugins and metadata expiration #276

pgera opened this issue Oct 28, 2018 · 1 comment

Comments

@pgera
Copy link

pgera commented Oct 28, 2018

The out of the box setup makes clients really slow for two reasons, especially if the latency to the server is high. The repo upload plugin, which gets enabled, takes a while to upload all the repos on every yum operation. Second, the metadata is set to expire immediately, as opposed to the more conventional 6h window. Both of these can be adjusted on the client after the fact, but I wonder if there is a) A server side knob to set these and b) A way to set or override it in the bootstrap script.

@sideangleside
Copy link
Member

Regarding metadata expiration, this is by design so that when a minor release of a content view is created (such as going from version 13.0 -> 13.1), the client will immediately be able to get access to the new RPMs. You can override this like such subscription-manager repo-override --repo=rhel-7-server-rpms --add=metadata_expire:50. I would be open to having an option to set metadata expiration.

Regarding the repo upload plugin, it would be difficult to tweak that as it is required to properly calculate errata. That plugin is pretty binary. It is either on or off. I would not be supportive of disabling this plugin in bootstrap.py.

@evgeni Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants