On Fri, Apr 4, 2014 at 3:09 PM, Karanbir Singh <mail-lists@karan.org> wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">
rpm-ostree: <a href="https://github.com/cgwalters/rpm-ostree">https://github.com/cgwalters/rpm-ostree</a> ( this is what one
would use to take a bunch of rpms and make them into an ostree VM, it
spits out a qcow2 image )</div></blockquote><br><div>Yep, also it is now useful on the *client* side: you can use "rpm-ostree upgrade" which at the moment just uses libostree. It will get significantly more exciting when I support adding packages on top of a base tree.</div><div><br></div><div>Also a quick note; the qcow2 image generation predates Anaconda support - it's mostly only useful until that lands. When that happens, Anaconda is the clearly correct thing to use to generate disk images.</div><div><br></div><div>(For example, the rpm-ostree qcow2 code hardcodes XFS and the disk size, etc.)</div><div><br></div><div>Details aside:</div><div><br></div><div>I'm quite interested to see if anyone in the CentOS community in this sort of deployment model. I presented at Devconf.cz on this topic:</div><div><a href="http://www.youtube.com/watch?v=Hy0ZEHPXJ9Q">http://www.youtube.com/watch?v=Hy0ZEHPXJ9Q</a></div><div><br></div><div>And the feedback I got was that some of the admins could really imagine using it for server farms, but not necessarily on their desktops. Given you guys are more of the server farm, I'd like to explore that use case more. Any feedback appreciated!</div><div><br></div>