How is it incompatible with packaging? The read only root support that already exists in Fedora today is what would be used.
In that /etc and /var are read-only. Now you're right, there is read-only root which makes sense for certain cases, but changing the OS content to write to a special data partition is taking one farther away from the generality of the package/FHS model.
How do the images get built? Can you use existing image building tools, or it something ostree specific?
The trees (not images) get composed using rpm-ostree. It's just a wrapper around yum --installroot + ostree commit.
From there after Anaconda support lands, one can install a tree (just like a set of packages) into a disk image or bare metal. In this model, Anaconda will be doing far less - it'll just be copying data, not depsolving or running through the SELinux labeling, etc.
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
