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

Add more realistic storage requirements including Package Hub #2433

Open
stdevel opened this issue Sep 6, 2023 · 1 comment
Open

Add more realistic storage requirements including Package Hub #2433

stdevel opened this issue Sep 6, 2023 · 1 comment
Labels
docs backlog In the docs backlog

Comments

@stdevel
Copy link
Contributor

stdevel commented Sep 6, 2023

Documentation Update Required

Currently, the documentation lists ~50 GB of storage per SUSE product as requirement. This might be realistic for the base repositories - but it is not sufficient for the Package Hub repository.

What does the documentation say now?

50 GB per SUSE product.

What change is required?

It would be a nice addition to have the hint, that Package Hub requires additional ~20 GB of storage. From my point of view, the most customers/users also sync this repository (like most EL users also sync the EPEL repository).

What content needs to be added?

A small notice could be added.

Subject Matter Expert (SME)

?

Version

It is applicable to SUSE Manager 4.x / Uyuni 2022.xx or newer. It can be backported, if you want.

@keichwa
Copy link
Contributor

keichwa commented Sep 14, 2023

Thanks for the report. I hope we now can fix it together with #2446 . Maybe, you now can watch that one, and add comments and concerns if changes are not clear enough. YaST now warns if less than 100 GB is available.

PR is here: #2448 --maybe, we should mention Package Hub explicitly.

@keichwa keichwa added the docs backlog In the docs backlog label Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs backlog In the docs backlog
Projects
None yet
Development

No branches or pull requests

2 participants