Setting up a Debian machine to be a container host for LXC.
- Get quieter heatsink fan setup (duct? other fan?)
- Install Debian Stretch amd64
- Get LXC installed
- Setup Ethernet bridge for containers to be on local LAN (not NAT'ed)
- Setup syslog server on host to receive syslog data from all containers
- Setup LAN's DHCP server to hand out fixed IPs based on hostname in DHCP request for containers that need it (ie: mirror)
- Setup mirror container, transfer over existing mirror data from lati
- Setup build machine container
- Setup disk quotas for containers
- Setup automatic updates for host and containers
- Investigate how to easily apply changes/actions to many machines (ie: ansible?)
- Setup HE.net dynamic dns?
- Configure host and containers to be able to send email alerts to me
- Buy and install additional 4 GB DDR3L SODIMM stick?
- Install extra SSD to use for build machine container scratch area?
- Build machine (for Yocto/OE work)
- Apt-cacher and/or Debian mirror
- Ansible server
- Is it worth still having the mirror on the LAN? Would an apt-cache be more effective considering my time and how the security.debian.org repo integrates into stretch?
- For using apt-cacher-ng (or similar apt cache) you can postfix the cache network address with the remote mirror to fetch from so as to provide tools like debootstrap their normal apt-style interface for fetching packages. Source: https://xen-tools.org/pipermail/xen-tools-discuss/2009-July/000661.html