I think this highlights the problem we're currently seeing with the Fedora Cloud Base adoption
On 10/28/2015 07:42 PM, Matthew Miller wrote:
> Actually, I don't think that's true. Take a look at "fr1st p0st":
>
> https://lists.fedoraproject.org/pipermail/cloud/2010-January/000001.html
There is no singular Fedora release anymore, so what are people getting when they install Cloud Base? The `cloudtoserver` script essentially disables cloud-init and installs Fedora Server. So what's in the Cloud Base box when we say it's the "base building block of the Fedora flavors"? What was the point of creating use case editions and not using them in the cloud?
I really don't want the answer [ ;-) ] b/c I think the right answer *should be* Fedora Server + required platform elements (cloud-init, cloud-initramfs-tools, etc). The Cloud base didn't change when the rest of Fedora did, and it should have. I see "cloud" as a platform like ARM and the use case for a Cloud Base image the same as any other server OS running in such a platform. I don't believe that folks working in cloud environments need a super minimal install everything OS for what they do.
Regardless of which SIG owns the work, I believe that the Cloud Base build and the Server build should be very tightly coupled. The edition should be Fedora Server, the ever shrinking minimal install target is a red herring, and the Cloud focus is making a Server "spin" (not sure if this is qualifies officially) for a known set IaaS providers.
I also think the Cloud Base could do with a bit of market research to see what other distros are providing in those IaaS platforms so we can avoid chasing geese.
-Matt M
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
