https://wiki.gnome.org/action/show/Projects/OSTree OSTree is a neat way of performing deployments and atomic field upgrades, as well as being useful for development work by allowing atomic upgrades between development builds and simple switching between production and debug images. The initial implementation of this is bootstrapped using a fork of Poky, so we should merge back the upstreamable changes and considering supporting ostree as a deployment method.
A potential incremental step is to simply take the current RPM/dpkg output, and commit that to the tree directly. This is quite simple to do, but is slow as it incurs the cost of re-SHA256 checksumming all of the input again. What gnome-continuous does is to store components[1] a sub-commits in the same repository, then the final tree(s) are a union. We avoid checksumming again by computing a mapping from (device,inode) to checksum in the repository (as they're all hardlinks). See also https://bugzilla.gnome.org/show_bug.cgi?id=707827 Doing something more like Continuous would involve nontrivial changes to the package layer to optimize things. However, I am looking at some of these optimizations also in the context of rpm-ostree: https://github.com/projectatomic/rpm-ostree
Also, this would significantly help Continuous because right now it's a poky fork, instead of an OE layer as it should be.
What is the status of this? From what I have been reading (didn't tried), this has been already integrated into AGL (an OpenEmbedded-based distro). https://wiki.automotivelinux.org/subsystem/agl-sota/ostree And for Poky, there is a layer providing the missing OSTree integration https://github.com/advancedtelematic/meta-updater Is Poky planning to integrate support for OSTree directly into the core?
I'm not the right assignee for this. At present I have no plans to work on OSTree items.
I don't think ostree belongs in core, and meta-updater covers integration.