Desktop Team Update - Monday 15th July 2019

ZSYS:

  • Implemented the “machine” layer, which enable to detect and group ZFS datasets per machine (system on boot and late system datasets, userdata and persistent datasets) + history of each one (clones and snapshots)
  • Continue discussion and addressing comments of the Fedora zfs maintainer.
  • Implemented Boot phase: Switch on and off correct datasets for mounting + cloning what’s needed to be cloned, like userdata with user dataset revert if booting on a snapshot. /!\ needs to make them idempotent.
  • Implemented Commit phase: Tag as appropriate user datasets with system, and promote needed ones.
  • Incremented and changed/rethought the design to have as few changes as possible before Commit() and ensure that if boot fails, no impact on further boots.
  • Adapted zfs layer to those changes, simplifying the golden files.
    Note: tests nor CLI hooks are implemented yet, this will be the next steps
  • Found an issue with go-libzfs 0.8 compatible upstream branch now that 0.8 migrated to eoan: https://github.com/bicomsystems/go-libzfs/issues/19. Proposed a fix upstream as https://github.com/bicomsystems/go-libzfs/pull/20. We are using our fork right now.

Misc:

  • Helped on yaru/chromium browser snap debug
3 Likes