[Spacewalk-list] avoiding the thundering herd

[Jaimie Livingston]

I would suggest using a proxy server and register groups of servers to
different proxies.
For example, I have proxies setup for each of the geographically dispersed
datacenters I work in, and the servers in each datacenter connect to the
local proxy, rather than have to connect back to the primary spacewalk
server.

You could do something similar, but for groups of servers in your
organization.

https://github.com/spacewalkproject/spacewalk/wiki/proxy


*Jaimie Livingston*
Operations Engineer

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender.  Please
note that any views or opinions presented in this email are solely those of
the author and do not necessarily represent those of PeopleFluent.
PeopleFluent accepts no liability for any damage caused by any virus
transmitted by this email and therefore you should check this email and any
attachments for the presence of viruses.


On Tue, Apr 9, 2019 at 5:43 PM Guy Matz <guymatz at gmail.com> wrote:

> Hello!  I am going to be upgrading a number of servers and don't want them
> all banging on my spacewalk server at the same time to download packages .
> . .  I was hoping to be able to "stage" the updates on the servers
> before-hand, then trigger the update via spacewalk.  I was hoping this
> might result in a faster upgrade process on the day of upgrades, making the
> upgrade a bit easier to deal with . . .
>
> Any thoughts on how to go about this?  Any suggestions otherwise?
>
> Thanks a lot,
> Guy
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20190409/1462b6a3/attachment.htm>