Hi,
My name is Bill Perkins. I am intending to create a local repository for x86_64 systems on my internal network. I only intending to store and serve up x86_64 and SRPMS files for current releases of Fedora and Rpmfusion. I am still researching on what are the best tools to do this.
---- William M. Perkins, KJ4ASH Linux/Solaris/AIX Systems Administrator The Greenwood ARES DEC-14/EC Grayson Co./Skywarn/ARCA/NTS Baywood, Virginia E-mail - bp241@grnwood.net
"BP" == Bill Perkins bp241@grnwood.net writes:
BP> I am intending to create a local repository for x86_64 systems on BP> internal network.
That's easy. Just copy the content you want and serve it up via http.
BP> I only intending to store and serve up x86_64 and SRPMS files for BP> current releases of Fedora and Rpmfusion.
So you just copy that content and exclude the rest.
BP> I am still researching on what are the best tools to do this.
You don't really need anything other than rsync and a web server. Find nearby mirrors of Fedora and rpmfusion which support rsync access and run rsync to copy the data you want.
I happen to have two full Fedora mirrors on site, but my machines don't use them. Instead I stage the content I need from them into my private network. I use something like the following:
H=rsync://pubmirror2.math.uh.edu/fedora-enchilada/linux
rsync -avpPH --delete --exclude="*-debuginfo-*" --exclude="*.iso" \ --exclude="*.src.rpm" --exclude="armhfp" --exclude='aarch64' \ --exclude="testing" --delete-excluded $H/updates /srv/mirror
rsync -avpPH --delete --exclude="*-debuginfo-*" --exclude="*.iso" \ --exclude=test --exclude="*.src.rpm" --exclude="armhfp" \ --exclude='aarch64' --delete-excluded $H/releases /srv/mirror
That copies all active releases. If you want to limit that further then you certainly can. Limiting to a specific release would mean updating the scripts for each new release to copy just that release directory. A mirror of updates and releases like this currently takes about 430GB. A little less than half of that is F28.
Copying from rpmfusion is similar.
Then you just configure a web server to save out that content. You could also just use NFS if you wanted, but I find plain old https to be just fine.
Getting your clients to access this content is another matter. You of course will give the proper URLs to the installer but once installed the system will use the Fedora-supplied repositories. Personally I replace the repository files in /etc/yum.repos.d when the system first boots. (I use ansible for post-install system configuration.)
- J<
And note that the DNS for grnwood.net is messed up so a direct reply bounces. It is not valid to list IP addresses in MX records.
- J<
Jason, Thank you for the original reply and thank you for correctly pointing out my problem with the MX record. It should be fixed now. Bill
mirror-admin@lists.fedoraproject.org