I'm at the Boston Kubernetes meetup and dvol was demoed.
You might take a look at https://ostree.readthedocs.org/en/latest/ for some ideas - dvol is targeting a different use case (mutable data) whereas ostree is oriented for snapshots of immutable state using plain hardlinks.
But if you're aiming for git-like model, some concerns may be shared. For example, OSTree follows git in having a content-addressed store, whereas dvol seems to use uuidgen for commit ids and its snapshots boil down to shelling out to coreutils cp. BTW, you probably want to use --reflink=auto at least so if the underlying FS supports it you'll get CoW.
I'm at the Boston Kubernetes meetup and dvol was demoed.
You might take a look at https://ostree.readthedocs.org/en/latest/ for some ideas - dvol is targeting a different use case (mutable data) whereas ostree is oriented for snapshots of immutable state using plain hardlinks.
But if you're aiming for git-like model, some concerns may be shared. For example, OSTree follows git in having a content-addressed store, whereas dvol seems to use
uuidgenfor commit ids and its snapshots boil down to shelling out to coreutilscp. BTW, you probably want to use--reflink=autoat least so if the underlying FS supports it you'll get CoW.