<div dir="ltr">Ok I didn't notice the date, but, it is at least a clear set of goals. If that's not the focus / direction of the SIG now, then I'm sure that's part of the issue when we hear: <br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">"we have an image you can use, it does the<br>
standard things... we're kind of out of ideas to make it more interesting."<span class="im"><br></span></blockquote><div><br></div><div>I get that the name doesn't have to match the deliverable, it makes it clearer to the outside when trying to get help, trying to get contributors, trying to get the message out.<br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">For the cloud image itself, I don't fully understand why I'd want<br>
a specialized cloud image over a minimal Fedora image -- being<br>
on Amazon and making minimal, but otherwise stock Fedora images<br>
available feels like a core distro task to me.</blockquote><div><br></div><div>This does make sense, if the Server team is willing to take it on. There are a few things that are IaaS specific (cloud-utils-growpart is forever burned into my mind now) but generally might be able to be treated like an arch or a spin. <br><br></div><div>If none of the old-new activities are really ongoing in the SIG, and the main focus of the current SIG members is Atomic, I've got no issues. I guess I always figured we were a small if vocal minority of the SIG membership.<br><br></div><div>- matt m<br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 21, 2015 at 12:16 PM, Jason Brooks <span dir="ltr"><<a href="mailto:jbrooks@redhat.com" target="_blank">jbrooks@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
----- Original Message -----<br>
> From: "Matt Micene" <<a href="mailto:nzwulfin@gmail.com">nzwulfin@gmail.com</a>><br>
> To: "Fedora Cloud SIG" <<a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a>><br>
</span><div><div class="h5">> Sent: Friday, August 21, 2015 6:49:18 AM<br>
> Subject: Re: [DISCUSS] Making Atomic the cloud edition<br>
><br>
> Given:<br>
><br>
> > jzb<br>
> ><br>
> Given that a great deal of interesting work is going into the Fedora<br>
> > Atomic host, we'd like to make Atomic the main deliverable/focus for the<br>
> > Cloud Working Group and Cloud edition.<br>
><br>
><br>
> and<br>
><br>
> mattdm<br>
> ><br>
> For that, we need the Cloud Base to have *internal* visibility and<br>
> > connections, but it doesn't need to confuse the marketing message.<br>
> ><br>
><br>
> I think moving the focus of Cloud SIG to focus on Atomic would confuse<br>
> folks more than the currently slim messaging around the Cloud SIG goals. I<br>
> think CentOS has the right approach with a separate Atomic SIG, and I<br>
> propose that we follow that model. Split Atomic into it's own SIG,<br>
> continue the Cloud SIG to focus on cloud things.<br>
><br>
> Atomic is a new way of doing everything. OS management changes, package<br>
> management changes, Docker + K8S + Nulecule + Atomicapp + ? + ? + ?. We<br>
> are trying to move at a much more rapid pace than the rest of the Fedora<br>
> Project products (see the 2 week release proposal). We are breaking things<br>
> at a much more rapid pace than other products as well. Lots of initial<br>
> answers on ask / IRC wind up as, "update the tree see if it's still<br>
> broken".<br>
><br>
> I don't think that if you say the word "cloud" in a room of IT folks<br>
> today, that over 1% are going to think Atomic. They think OpenStack,<br>
> OpenShift, CloudFoundry, Eucalyptus, AWS, ownCloud, etc. Fedora as<br>
> foundation, Fedora as tenant, Fedora as a Service! The new Cloud SIG draft<br>
> reflects those use cases: <a href="https://fedoraproject.org/wiki/Cloud_SIG-new-draft" rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Cloud_SIG-new-draft</a>.<br>
> Fedora saying "well when *we* say cloud we mean Atomic not what you think"<br>
> and having to explain it doesn't sound like a win.<br>
<br>
</div></div>Thanks for pointing to this doc (though I see now that it was<br>
last updated in 2013). It's a pretty ambitious set of goals --<br>
esp things like getting various IaaS platforms running on Fedora.<br>
<br>
An important question is what our contributor base wants to work on --<br>
I haven't seen much mention of things like getting IaaS running on<br>
Fedora in the cloud sig meetings.<br>
<br>
For the cloud image itself, I don't fully understand why I'd want<br>
a specialized cloud image over a minimal Fedora image -- being<br>
on Amazon and making minimal, but otherwise stock Fedora images<br>
available feels like a core distro task to me.<br>
<br>
It's true, though, that CentOS has both Cloud and Atomic SIGs, both<br>
with plenty to do, so that model might fit here, as well. No need to<br>
wrench the SIG away from non-atomic matters if that's where the SIG<br>
contributors want to place their efforts. The question is, where do<br>
the SIG members wish to focus... I guess that's what this thread<br>
is about.<br>
<span class="HOEnZb"><font color="#888888"><br>
Jason<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> And while there's overlap in uses like cloud-init, Atomic is much more<br>
> likely to want a completely new compatible implementation because the<br>
> dependency tree makes maintenance more complex than a Fedora OpenStack<br>
> guest image will need to care about. (See my previous rants on sizing ;-)<br>
> ). Or a Fedora Server optimized for running nova-compute. The Cloud Base<br>
> Image and the Atomic host or the Docker Base Image don't and shouldn't have<br>
> much in common because the use cases are different.<br>
><br>
> I do think that the Cloud SIG does need better messaging about its intents<br>
> and goals. The new SIG draft looks like a step in the right direction to<br>
> me. Define major focus areas (run IaaS on Fedora, run Fedora in IaaS, etc)<br>
> then layer in use cases and projects from the group.<br>
><br>
> A new Atomic SIG would focus on stabilizing the Atomic host, the delivery<br>
> process, and the Docker base image. Atomic hosts are all about running<br>
> Docker workloads, so that makes sense to couple. As containerization<br>
> grows, I could see the need for moving Docker image management somewhere<br>
> else.<br>
><br>
> Did I miss the 72 hr window?<br>
><br>
> - matt m<br>
><br>
><br>
> On Wed, Aug 19, 2015 at 12:05 PM, Matthew Miller <<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>><br>
> wrote:<br>
><br>
> > On Wed, Aug 19, 2015 at 08:04:33PM +0530, Lalatendu Mohanty wrote:<br>
> > > Does it mean that we are assuming that we have considerable users<br>
> > > using current fedora atomic image<br>
> > > or considerable users using the cloud image mostly for running<br>
> > > containers and going to increase in future ?<br>
> > > I understand that Atomic host having newer technology which is<br>
> > > better for a world of containers but just want to make sure the<br>
> > > decision is driven by user needs.<br>
> ><br>
> > I'm at LinuxCon, which is also at the same time CloudOpen and<br>
> > ContainerCon. The sample size is small and the audience skewed, but:<br>
> > I've talked to several (three) people using/testing Fedora Atomic, at<br>
> > least one of them fairly seriously; no one using Cloud Base image.<br>
> ><br>
> > That's not to say that they don't exist (hi there!), but I think user<br>
> > interest/excitement around Atomic is clear. Perhaps more crucially as<br>
> > we make this plan, I think the people who want basic-Fedora-in-the-cloud<br>
> > are less likely to be a "wedge" audience, where we can market that as<br>
> > their first exposure to Fedora and from there possibly grow into more<br>
> > areas. Rather, they're going to be people who already know Fedora, or<br>
> > are already interested in us in general, and then are looking to have<br>
> > that in a cloud environment.<br>
> ><br>
> > For that, we need the Cloud Base to have *internal* visibility and<br>
> > connections, but it doesn't need to confuse the marketing message.<br>
> > Specifically, I'd like it to go in the "Other Downloads" section of<br>
> > <<a href="https://getfedora.org/en/cloud/download/" rel="noreferrer" target="_blank">https://getfedora.org/en/cloud/download/</a>>, introduced like this:<br>
> ><br>
> ><br>
> > "Looking for a plain, non-Atomic image optimized for cloud<br>
> > environments? Download Fedora Cloud Base Image: [...]"<br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Matthew Miller<br>
> > <<a href="mailto:mattdm@fedoraproject.org">mattdm@fedoraproject.org</a>><br>
> > Fedora Project Leader<br>
> > _______________________________________________<br>
> > cloud mailing list<br>
> > <a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
> > <a href="https://admin.fedoraproject.org/mailman/listinfo/cloud" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
> > Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" rel="noreferrer" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
> ><br>
><br>
> _______________________________________________<br>
> cloud mailing list<br>
> <a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/cloud" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
> Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" rel="noreferrer" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
><br>
_______________________________________________<br>
cloud mailing list<br>
<a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/cloud" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" rel="noreferrer" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
</div></div></blockquote></div><br></div>