Because we can not even guess what all use cases people have while using a
cloud instance?

I'd say we have the same process with Server.  Most people take a minimal server image and deploy required applications with their own tooling.  There are some opinions (roles) that exist to do some common expected things, but (imo) rolekit is an opinionated configuration tooling system.  Like ansible or shell scripts. 

There's not a lot of difference between the major use cases of Server and Cloud, just an opinion on how minimal a Base should be.

- Matt M



On Wed, Nov 4, 2015 at 4:03 AM, Kushal Das <mail@kushaldas.in> wrote:
On 03/11/15, Matt Micene wrote:
> 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?
Because we can not even guess what all use cases people have while using a
cloud instance? People generally take the base image, and have their own
tooling (say ansible, or shell scripts) which deploys the required
applications in the cloud. This is where the minimal cloud base image
comes handy.

Kushal
--
Fedora Cloud Engineer
CPython Core Developer
CentOS Cloud SIG lead
http://kushaldas.in
_______________________________________________
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct