RedHat Satellite Server
Hi Experts,
Long story short:
We have 2 servers (RHEL AS 4) and around 16 workstations (running RHEL WS 4).
Problem:
Different locations. Difficult to deploy new system, update is also time consuming since they all have to download then install or well.. burn a CD / DVD and go to location.
I want to deploy, update, maintain my workstations 'remotely'. One of the solution is to use RedHat Satellite Server. However this proves to be quite expensive. I'm thinking about creating a KickStart server so I can setup things remotely. I'm trying to compare these 2 solutions (pros and cons). I've been looking for any comparison available on the net but so far no luck.
Any ideas?
Long story short:
We have 2 servers (RHEL AS 4) and around 16 workstations (running RHEL WS 4).
Problem:
Different locations. Difficult to deploy new system, update is also time consuming since they all have to download then install or well.. burn a CD / DVD and go to location.
I want to deploy, update, maintain my workstations 'remotely'. One of the solution is to use RedHat Satellite Server. However this proves to be quite expensive. I'm thinking about creating a KickStart server so I can setup things remotely. I'm trying to compare these 2 solutions (pros and cons). I've been looking for any comparison available on the net but so far no luck.
Any ideas?
ASKER
Hey Tintin,
That's what I'm still thinking right now. Could you give me some more info about Satellite server? About its complexity and if you don't mind why your client wants to use it?
I haven't got a chance to use it yet since it is quite expensive and there is no evaluation / trial version.
Thanks a bunch.
That's what I'm still thinking right now. Could you give me some more info about Satellite server? About its complexity and if you don't mind why your client wants to use it?
I haven't got a chance to use it yet since it is quite expensive and there is no evaluation / trial version.
Thanks a bunch.
What sort of info do you want about Satellite server?
Probably the best way of thinking about it is that it's like having your own version of RHN interface (plus some extras) available locally.
Probably the best way of thinking about it is that it's like having your own version of RHN interface (plus some extras) available locally.
ASKER
You mentioned that it's complexity. Why do you think most people only use a small subset of the advanced features?
You also mentioned that your client wanted Satellite Server, what are their justification to use it? (If you don't mind answering). I would like to know that since my only argument now to NOT use Satellite server is the price.
Thanks.
You also mentioned that your client wanted Satellite Server, what are their justification to use it? (If you don't mind answering). I would like to know that since my only argument now to NOT use Satellite server is the price.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well, looks like I have quite the same thing here.. Ater all its their money, and some consider they have to "spend" to get results :D
I guess my last question here would be: in case I use dedicated Linux server to deploy. How can I effectively roll out patches? What did you do in your case?
Thanks a bunch.
I guess my last question here would be: in case I use dedicated Linux server to deploy. How can I effectively roll out patches? What did you do in your case?
Thanks a bunch.
Patch management is pretty much the same if you have a Satellite server or not (assuming all your servers can get HTTP/HTTPS access to redhat.com to download the updates).
ASKER
Pretty much the same : Yes.
What I meant was how do you save time? Right now we have 2 following options:
1. Connect to redhat.com and download updates -- which is quite slow.
2. Download once and well.. a little bit dumb, burn CDs then go to site and install -- which is time consuming.
To be perfectly honest I don't like any of these :D Any suggestions?
What I meant was how do you save time? Right now we have 2 following options:
1. Connect to redhat.com and download updates -- which is quite slow.
2. Download once and well.. a little bit dumb, burn CDs then go to site and install -- which is time consuming.
To be perfectly honest I don't like any of these :D Any suggestions?
If you have a caching proxy server and you specify that up2date uses HTTP instead of the default HTTPS, then you'll have a local copy of the patches when the first server downloads them from Redhat.
In fact, this is a lot more efficient that Satellite as it will download the updates *entire* channel. So if you had a mixture of say RHEL3 & 4 & 5, then Satellite will download all the patches for each of those channels regardless of whether they exist on your servers.
In fact, this is a lot more efficient that Satellite as it will download the updates *entire* channel. So if you had a mixture of say RHEL3 & 4 & 5, then Satellite will download all the patches for each of those channels regardless of whether they exist on your servers.
ASKER
Thanks for the info.
For building the servers, we have a dedicated Linux server sitting on the build network that contains all the various Linux ISO's we use, and it also acts as a DHCP and kickstart server.
When we build a new server, we simply add a new DHCP entry, copy one of the existing kickstart configs on a NFS share, then boot the new server and install with
linux ks ksdevice=eth0
We main reasons we use the Satellite server are:
1. The client wanted to use it.
2. Simplifies management of subscriptions as you just have a single cert that covers all servers with a common expiry date.
3. Saves a little on bandwidth by only needing to download updates once to the Satellite server.
If I had the choice, I wouldn't bother using Satellite server in a small environment. It's a pretty complex beast and while it does have a lot of features, I suspect most people only use a small subset of the advanced features.