On Oct 31, 2011, at 2:16 PM, <Matt_Domsch(a)Dell.com> <Matt_Domsch(a)Dell.com>
How will your clients know to use your mirror? Editing
/etc/yum.repos.d/* ? By having an assigned netblock or ASN, you can avoid that pain,
but if you can't use those, oh well, edit away.
I can edit the baseurl, but I was hoping that there was a cool trick I could play by
editing the timedhosts.txt and mirrorlist.txt to direct yum to point to my local mirror as
the "fastest", but still be able to fall over to public mirrors in case my
private mirror happens to be hosed or someone happens to be looking for an architecture or
release version that I don't have.
This will all be automated with Chef, so once I've figured out how to make the
necessary changes, I won't have to keep updating the files each time.
The floating IP address won't matter - you'll list a DDNS
name in your URLs.
We've cooked up a DDNS solution (using the REST interface to our DDNS provider), so
that shouldn't be a problem.
rsync is definitely the right way - please pull from a listed public
mirror, and you can exclude any directories (not files within a directory) you wish. E.g.
if you don't need iso/, then exclude such.
You may wish to set up access control lists on your mirror server
httpd to allow only your clients in.
That would be my next problem. Thanks!
Dell | Office of the CTO
Ahh, interesting -- are you in Round Rock? We're actually a small startup hosted by
ATI at what used to be the MCC building (before UT Austin bought the building). Of
course, all our servers are in the Rackspace datacenter in Dallas, so our fastest mirror
is usually lstn.net
I don't suppose you know David Duncan, another fellow member of CT-LUG?
Brad Knowles <bknowles(a)ihiji.com>
SAGE Level IV, Chef Level 0.0.1