https://goo.gl/KQajJz

• Saltstack works well with FreeBSD
  • works with sysrc for configuration files
  • Standard documentation & techniques generally apply to FreeBSD
• Puppet
• Ansible
• Chef

• Poudrière
  • supports VM/OS image builds
• Packer
  • builds images for Vagrant, EC2, Azure, VMWare, …
  • needs serial library in go
    • https://github.com/hashicorp/packer/issues/1004#issuecomment-297817313
  • “Bento” from Chef project has FreeBSD configurations
    • https://github.com/chef/bento

• Vagrant
  • BhyveAsVagrantBackend
  • need Suspend/Resume feature
• Openstack

• https://artifact.ci.freebsd.org/snapshot/head/latest_vm/
  • disk-test.img.xz
  • disk.img.xz

• OSQuery
  • needs more people help about tables https://osquery.io/docs/tables/#freebsd
• Prometheus
• SNAP Telemetry

• libifconfig integration for Jail configuration
• structured log data
  • newer syslog RFC
• Improved diskless approach
• Cross-install approach
  • Configure installer from MacOS, Linux, etc.
  • Create SD card image from other another OS
• increased librification

• LibXo
• libucl

• migration away from human-readable formats
  • forward and backward compatibility
• changes in configuration file formats
  • e.g. introduce new UCL config, but allow a long transition where old format (inetd.conf) is accepted
  • Steps
    1. Introduce new format
    2. Switch default
    3. (long transition period here)
    4. Remove old format
• POLA
• Broad concensus that this is the desired path forward, but need to proceed very carefully and thoughtfully
• bsnmp as a good candidate

• Create (on wiki) prioritized list of utilities / configuration files
• Discuss w/ embedded and FreeBSD-derived appliance vendors and particularly smaller ones (Kris Moore @iX, pfSense folks, …)
• Establish as a principle use UCL for newly developed software
• Documentation
• Produce guidance on librification
  • like style(9); perhaps api(3)
  • Session topic for upcoming DevSummits

• Does this apply to ports? Upstream projects not in base?