[16:41] <eea> hello all, just curious if there is any additional documentation aside from https://wiki.ubuntu.com/Mirrors that I should read prior to setting up a local mirror to be used for pxe installs and software updates
[16:41] <eea> so far from my reading, it looks like I can get away with a releases rsync mirror
[18:20] <sarnold> eea: releases is really just cd images; it might be enough for the pxe installs, but wouldn't handle software updates
[18:22] <sarnold> eea: depending upon your goals, your environment, etc, it might be easy enough to set up a squid-deb-proxy or apt-cacher-ng for the network, and just cache updates as they're requested by clients -- this gives decent bandwidth reduction and speedups for a little bit of effort, and not too much storage. a full mirror takes a lot more storage and probably more network traffic to the archives
[18:23] <eea> sarnold: thank you for the info
[18:23] <eea> i am running an rsync now to a releases url 
[18:23] <eea> and it looks to be pulling in /pool/*
[18:24] <eea> storage and network resources are not constraints for me
[18:24] <eea> i simply can not have any of the imaged systems hitting the internet
[18:26] <sarnold> eea: did you set up one of the two-stage rsync scripts? I'm really surprised to hear that grabbing something like "releases" gets you to the pool/ bit..
[18:27] <eea> no, docs say i can just rsync the releases
[18:27] <eea> 2 stage is for full mirror
[18:27] <eea> as i understood it
[18:28] <eea> thing is, I could not find much valid info for restricting what i mirror to specific release 
[18:28] <eea> i.e. focal
[18:29] <cjwatson> Partial mirroring of archive mirrors (as opposed to image mirrors) by release requires some kind of smart mirroring tool that can parse the metadata files and work out which files from pool/ are needed, such as debmirror
[18:41] <eea> ah ha, looks like debmirror is exactly what I need
[18:41] <eea> thank you for the info