So at my Fedora.next talk at DevConf, I mentioned that OSTree might be an interesting thing for Fedora Cloud to look at.
I am obviously interested in this =) I have some forthcoming work to post within a week or so.
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!
Ok so there are two cases:
1) Fedora provides OSTree repository
2) Downstream consumes RPMs and creates internal OSTree repository
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).
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"? =)
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. I'll post more about that soon too.
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
