<div dir="ltr"><div>I see 3 editions based on the current images offered [1] (not a fan of the terms, just looking at the web page):<br></div><div>* Base Cloud</div><div>* Atomic Host</div><div>* Docker Base</div><div><br></div><div>The current Cloud PRD [2] refers (in my reading) mainly to Base Cloud. This is where I think the discussion of removal of python sits. I think it's a balance between Req #1 of the PRD and Req #6 as well as sticking to the user stories, not building a new way users are required to use Fedora. </div><div><br></div><div>Building updated images as an *option* for folks who want to or have the processes in place to do "immutable servers" or other Ops patterns shouldn't preclude those who still want to run "dnf update" from using Fedora Base Cloud.</div><div><br></div><div>What Atomic is going to do re: faster 2 week releases starting w/ F22 b/c of speed of release of core software is separate. It adds to the confusion, certainly.</div><div><br></div><div>And I jumped the gun on SCL, I hadn't realized that proposal had been marked rejected after stalling on package reviews. I think Req #5 and the need for multiple stacks is the ideal argument for SCL.</div><div><br></div><div>[1] <a href="https://getfedora.org/en/cloud/download/">https://getfedora.org/en/cloud/download/</a></div><div>[2] <a href="https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD">https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD</a></div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 4, 2015 at 2:08 PM, Josh Boyer <span dir="ltr"><<a href="mailto:jwboyer@fedoraproject.org" target="_blank">jwboyer@fedoraproject.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Thu, Jun 4, 2015 at 1:34 PM, Matt Micene <<a href="mailto:nzwulfin@gmail.com">nzwulfin@gmail.com</a>> wrote:<br>
>> But in order to be really useful unless they're all-in on Fedora, many<br>
>> people will want the python version for their<br>
>> infrastructure/environment, not whichever python we happen to ship in a<br>
>> given release.<br>
><br>
><br>
> That's always been the case and why software collections came about.<br>
> Rewriting system tools to make it easier for someone who might like to use a<br>
> different version of python at /usr/bin sounds like overkill. A lot EC2<br>
> AMIs, public and private, are 8GB+ snapshots with 2GB+ of OS installed.<br>
><br>
> I may be "broken record"ing but I'm still seeing context switches between<br>
> the cloud "flavors" (atomic, docker base, cloud-ified server). We need to<br>
> be careful were making the right changes to the right "flavor". Ripping<br>
<br>
</span>Yes, please. It's gotten to the point where I don't even know what<br>
the Cloud Edition actually is any longer. It was confusing enough<br>
with the changes from F21->F22, and now (I thought) we basically are<br>
"dropping" all of the Atomic flavors that were done in F22 because<br>
Fedora moves to slow. So what is left, what are the images, and what<br>
are they based on?<br>
<br>
So confused.<br>
<span class=""><font color="#888888"><br>
josh<br>
</font></span><div class=""><div class="h5">_______________________________________________<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" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
</div></div></blockquote></div><br></div></div>