> Within https://github.com/theforeman/foreman-packaging/pull/1541 it was
> expressed that yum.theforeman.org does not have enough resources to hold
> the katello repos as they are today (but that this PR was not the right
> place to discuss it). This mailing list does seem like the current place.
Unsurprisingly, I'm in favour of this change, broadly speaking, since it
benefits me on the metrics side. More generally though, I see no logical
reason to keep one specific plugin separate to all the others, even if for now
the repo structure still needs some careful handling.
> What are the resource limitations that prevent this from happening? The
> details in the PR are quite limited.
>
> For size, here are the last few releases, binary RPMS:
>
> 52M 3.3
> 106M 3.2
> 105M 3.1
>
> Source RPMS:
>
> 298M 3.1
> 142M 3.2
> 79M 3.3
>
> Are there any other reasons to not host the repositories there?
Space shouldn't be too much of a concern, as far as I know. Web02 does run out
of space from time to time, but it's invariably the Deb repos that cause it,
and they can be cleaned up as required.
I do think bandwidth/traffic may be an issue, as we already (I believe)
consume a large proportion of our Rackspace budget on the existing packages.
Dominic, do I have that right, or is my info out of date?
Assuming bandwidth is a legitimate concern, I recently learned there's an
initiative within Red Hat to provide public-IP boxes to upstream communities
(properly isolated so that even non-RH staff can have shell access to do
community work). My research so far shows that this is a case of bring-your-
own-hardware, but comes with free power, public IP and bandwidth. Thus, moving
to this may be a way forward. I'm investigating further (e.g. is there a cap
to the free bandwidth, etc) and will report back, if we think it would be
useful.
That said, if the bandwidth is not an issue, then I know of no other blocker
to merging this.
Greg
···
On Wednesday, 8 March 2017 20:15:10 GMT Justin Sherrill wrote:
