----- Original Message ----- > From: "Matthias Runge" <mrunge@xxxxxxxxxxxxxxxxx> > To: cloud@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Tuesday, December 10, 2013 5:45:13 AM > Subject: Re: PRD use cases > > On 12/09/2013 08:39 PM, Matthew Miller wrote: > > Right now, the example use case we have is "cloud image on AWS". This > > suggests that we should have a parallel "cloud image on OpenStack" as > > another primary target, but then as I went to fill that in, I thought... > > maybe this is going about this wrong. I think this is a step or two too low > > level. How about instead, we make the use case be > > > > * Web Application Deployment in a Public Cloud > > > * Web Application Deployment in Hybrid Cloud > > > > > * Separate use case for Private Cloud? > > > > > * Non-web applications? Data crunching? > > > * Docker Container Host > > > > > * Something with Vagrant? > > Two short thoughts about this: > - do we really need to distinguish between public, private and hybrid > cloud? IMHO that shouldn't really matter for the image. In my opinion there really should be different images for the public cloud (and maybe even cloud-specific images) and private cloud. This is actually a whole other discussion that's gone on in the past, so this might not be the best place for the discussion about splitting out the images, though. My general take on it is that there are fundamental things (like enabling iptables by default) that need to happen on only on one "type" of cloud. The alternative to creating completely separate images is using cloud-init to alter what's running in the image at boot. > > Additional use cases: > * Database application > * mail server (yes, that's really old school), like smtp, imap, > spamassassin, etc. > * is there a use case for virtual desktops? +1 to all of these use cases. There's another important one that I don't think we've touched on yet, which is short-lived nodes used for data-processing as part of a pipeline. IMO we should put particular focus on that type of workload because Fedora is the first distro that has lots of pieces of the needed infrastructure for pipeline "big data" processing available in our repos. > > In General, I'd say, everything the server WG targets to would be > applicable for the cloud image, too (except cloud infra providing). > > Matthias > > _______________________________________________ > cloud mailing list > cloud@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/cloud > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
