Capacity Planning in association with Red Hat Satellite

Latest response

I am really new to Red Hat, especially with respect to the Satellite feature.
I was wondering though, does anyone know how to determine how many packages are in a given repository (for example, Red Hat Enterprise Linux 7 Server x86_64) and also where to determine the disk capacity required to store all of the packages associated with that given repository so as to do a proper job of planning for disk capacity?

Also, since I am a total novice at Satellite... I understand that there is a database that backends the repository framework for any and all repositories that the network has permission to use (manifest controls this I believe); planning for the disk capacity way up front is a reasonable expectation; so, again... for a given repository how much disk capacity is needed at a given moment while downloading using the Red Hat Satellite Sync feature to separately account for disk capacity in support of the PULP database?

We are having major problems with the SYNC capability where I work and we need some sort of level of confidence that we:
1) have enough space for the files to be downloaded,
2) have enough space, also, for the files to be imported into the PULP database, and
3) know, beyond a doubt, that we have received all of the packages (and if not which one(s) are outstanding), and finally
4) have them all in the PULP database with 100% confidence that we won't run updates using the Satellite Framework and corrupt our network of machines because we don't have a full download of all the packages we are required to have.

Thanks

Responses

Hello, take a look at the section Storage Requirements and Recommendations section in the Red Hat Satellite Installation Guide. This section gives advice on the possible sizes to expect. Note that it is not possible to give an exact size for a given repo as the size of a repo changes as new versions of packages are released., and a new version of a package may have new dependencies which will consume more space.

As to point 3, the web UI will tell you when a sync is complete. I cannot understand how anything could be corrupted by having an incomplete sync. Incomplete bits of packages would not be used if that is what you mean.

There's also a feature coming along called Lazy Sync. Some of the code is already there, but I think there are some tweaks to be done before it's considered fully landed. This (I hope) will only pull packages down to your Satellite when they are requested during a host deployment process or patching. This will greatly reduce the storage requirement for your Satellite - unless your installations pull in every package under the sun. We're waiting on this feature as it will also allow our Proxies^H^H^H^H^H^H^H, um Capsules I mean, to slim down their disk requirements.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.