> How can we improve and automate more of patching and deployment?

• patching
• deployment
  • BE (boot environments)
  • pkgbase
  • etcupdate
• appliance-style

> patching today (for base systems, not ephemeral/immutable jails) is manual

• freebsd-update x2 reboots, merging /etc changes often requires manual changes & then installing package updates - key customised files include:
  • /etc/
    • hostid
    • passwd db
    • rc.conf & rc.conf.d/*
  • /boot/loader.conf

A number of things could be improved:

• a supported way of mirroring official freebsd-update patches locally - e.g. rsync or pulling down a .txz or a pre-prepared zfs dataset
• integrating beinstall (updates via boot environment) into patching process
• improve conflict resolution of /etc/* customised files

• beinstall.sh is awesome (thanks will@ )
• https://svnweb.freebsd.org/base/head/tools/build/beinstall.sh?view=markup

• deploying full datasets
• staging freebsd-update locally: improving mirror diversity
• pkgbase beinstall
• PKG_ROOTDIR in Mk/tools/…
• overlay /etc

• we would like the patching process simpler, faster and supported

• poudriere image
  • miniroot
    • shell
    • fetch
  • PXE boot style

• MFSBSD
  • http://mfsbsd.vx.sk/
  • https://github.com/mmatuska/mfsbsd
  • let's merge it