 | | | Satellite server | Satellite server 2005-08-25 - By Jussi Silvennoinen
Back
> For anyone out there interested in sharing their experiences, we're
> looking at installing Satellite server 3.7. Any comments on the
> following?
>
> 1. Stand-alone database versus embedded database. To have full control
> over the DB, I'm leaning towards embedded, but leaning towards SA for
> disaster recovery. We will have a small deployment, so it may be
> efficient to just do a text dump of the embedded Oracle database and
> back that up. It would have to be pretty small as our backup network
> isn't high speed. It could also be a cold backup in the early morning
> hours.
For my environment, I chose embedded. We don't use Oracle in almost
anything (pure mysql-shop). The box is just a dual 3g xeon with 4gb ram,
four disk RAID10 for data, running RHEL4 w/ RHN 3.71. Things happen
swiftly, the only slightly slow clickety-clack is when I take a full
listing of all boxes, that takes a few seconds. sar output is boring to
read :)
I'm only running a bit more than a hundred clients. I'm expecting this
setup to handle atleast 1000 clients. Dumping out the 6gb of data takes 10
minutes.
For the installation, I recommend getting GPS from Redhat to do it for
you. They'll do a lot more than just install the Satellite. If you have
any gripes, unsolved problems etc they'll help. Competent folks.
It's not too difficult to do on your own. Anyways you'll need to have ample
bandwidth during the installation or download the gazillion iso-images
from the RHN channel beforehand. Btw do not sync random channels just for
fun or testing, they'll stay there forever. Channels cannot be removed.
> 2. Looks like our security group will not allow some of the firewall
> rules
> we require for the server itself. We may be getting a corporate patch
> management solution (www.patchlink.com) for all OSs. Has anyone ever
> tried somehow integrating Satellite server with another patch management
> solution?
Which rules would that be? All that client->satellite needs is https.
World->satellite nothing is required, the other way around you need https to
satellite.rhn.redhat.com, and then some defaultstuff (dns etc).
If you get provisioning and want to use Push updates, you need to allow
client->satellite 5222/tcp also.
>From my POV, patch management is the most important part of Satellite.
Strip that away and you're left with what, a fair gui with a list of your
boxes?
On a related topic, lately (past two weeks) I've seen a shower of spurious
errors with my hourly satellite-sync. Also a sync of 6 channels taking
more than an hour. Previously this was completed in under 10 minutes.
I'm rather sure that our network has not changed in a way which would
affect this. Any clues when RH is supposed to have their EMEA datacenter
up and running and have euro-RHN?
--
Jussi
--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list
Earn $52 per hosting referral at Lunarpages.
|
|
|