| Summary: | Investigate OSTree integration | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | deployment | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | alex.kiernan, clopez, holger.behrens, phil, Qi.Chen, sgw, walters |
| Version: | 1.7 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Ross Burton
2014-05-01 16:14:11 UTC
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. |