On Mon, Feb 10, 2014 at 1:37 AM, Matthew Miller &lt;mattdm@fedoraproject.org&gt; wrote:<br>
<blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">So at my Fedora.next talk at DevConf, I mentioned that OSTree might be an
interesting thing for Fedora Cloud to look at. </div></blockquote><div><br></div><div>I am obviously interested in this =) &nbsp;I have some forthcoming work to post within a week or so.</div><br><blockquote type="cite"><div class="plaintext" style="white-space: pre-wrap;">But I also mentioned that we
haven't really talked about it here. So let's talk about it. I'm interested
in it for two reasons: it gives us part of an answer to what CoreOS offers,
and we miht have a space where it's an easier problem than for the general
Fedora distro, and therefore could be an incubation/test area. Discuss!</div></blockquote><br><div>Ok so there are two cases:</div><div><br></div><div>1) Fedora provides OSTree repository</div><div>2) Downstream consumes RPMs and creates internal OSTree repository</div><div><br></div><div>It's #2 that I think is going to be most interesting for cloud consumers at present. That's feedback I got from talking to people at devconf - they could definitely see the use case where organizations make their own internal trees and replicate them out to their servers (or clients).</div><div><br></div><div>Right now if we just shipped a cloud image that used OSTree (model #1) most people would just say "but how do I install stuff"? =) &nbsp;&nbsp;</div><div><br></div><div>Though we should have a continuously generated and tested tree for the default cloud that'd be used for development - this is the broader rpm-ostree story. &nbsp;I'll post more about that soon too.</div><div><br></div><div><br></div>