If you manage a large number (say 30+) of Fedora servers and need them to all remain at the same code levels, whats the best way to approach this?
It's clear to me that having 30+ machines reach out to the internet for updates is a waste of bandwidth. There must be a way to have a single server download the updates, then the rest of them update from that single server. I've never done this so I have basically two questions..
1. is it possible?
2. whats it called? i.e. point me to where i can read up on how to setup such an architecture and get a functional model.
I am familiar with kickstart already but haven't read anything that would allow me to do the above.
Ideally one could roll out updates in stages. Say I have 30+ servers and want to run the latest updates on a subset of servers first, before pushing it out enterprise-wide.
Thanks very much!
It's clear to me that having 30+ machines reach out to the internet for updates is a waste of bandwidth. There must be a way to have a single server download the updates, then the rest of them update from that single server. I've never done this so I have basically two questions..
1. is it possible?
2. whats it called? i.e. point me to where i can read up on how to setup such an architecture and get a functional model.
I am familiar with kickstart already but haven't read anything that would allow me to do the above.
Ideally one could roll out updates in stages. Say I have 30+ servers and want to run the latest updates on a subset of servers first, before pushing it out enterprise-wide.
Thanks very much!