<div dir="ltr"><div><div>I vote for different life-time for different purpose, precisely as David suggests: scratch, test, RC, Final (Beta).<br>But let's also don't forget about policy for testing the amis: how long to keep amis that failed testing in particular release stage.<br></div>Ideally, we should also keep track of released/available amis so people are able to easily find particular version and flavor of Fedora amis.<br></div><div>My usual use case is: reproduce a bug on e.g. F20 + some software stack.<br>I find F20 ami ideal for this but the issue is to locate it[1].<br><br></div><div>Cheers,<br></div><div>milan<br></div><div><br>[1] <a href="http://thecloudmarket.com/">http://thecloudmarket.com/</a> <br></div><div><div><div> <br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-03-19 5:11 GMT+01:00 M. Edward (Ed) Borasky <span dir="ltr"><<a href="mailto:znmeb@znmeb.net" target="_blank">znmeb@znmeb.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Mar 18, 2015 at 3:38 PM, David Gay <<a href="mailto:dgay@redhat.com">dgay@redhat.com</a>> wrote:<br>
> Greetings!<br>
><br>
> We sort of ran out of time in today's Cloud WG meeting, but I did want to ask:<br>
><br>
> What are your thoughts on AMI lifetimes? That is to say, how long should EC2 AMIs exist before they're deleted? A few points to consider:<br>
><br>
> - AMIs only cost us for storage, so it's not a *huge* cost to maintain a public AMI<br>
> - At the same time, there are a lot of AMIs, since we build 2-4 per AWS region per build, and that number is growing<br>
> - There are 9 regions now, and we have 2 virtualization types, and 2 volume types, as well (9 regions * 2 * 2 = 36 AMIs per Base image build, 18 for Atomic builds (since they are only available in HVM format))<br>
> - This total number will only grow larger as we add instance-store AMIs, and so on<br>
> - This isn't even taking into account any costs we'll have once we secure a deal with other providers like HP, Rackspace, and GCE, to maintain public images on their services<br>
><br>
> I propose we have some sort of discussion regarding how long cloud image builds should be available on services like AWS. I suspect this will resolve to having different lifetimes for scratch, test, RC, final, and maybe other build types.<br>
><br>
> Any input is appreciated. We can certainly talk about this at next week's meeting, as well.<br>
><br>
> -- David<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" 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>
<br>
</div></div>"In God We Trust - All Others Bring Data" ;-)<br>
<br>
Surely you or someone on the team must have some raw data on usage for<br>
the existing AMIs, including comparisons for how much usage Fedora<br>
AMIs get vs. CentOS AMIs and RHEL AMIs. Don't build / maintain what<br>
people aren't using!<br>
<br>
If you have raw data, I'd be happy to explore it for you - email me<br>
off-list if you need an NDA or something like that.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
OSJourno: Robust Power Tools for Digital Journalists<br>
<a href="http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists" target="_blank">http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists</a><br>
<br>
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.<br>
</font></span><div class="HOEnZb"><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>