I vote for different life-time for different purpose, precisely as David suggests: scratch, test, RC, Final (Beta). 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. Ideally, we should also keep track of released/available amis so people are able to easily find particular version and flavor of Fedora amis. My usual use case is: reproduce a bug on e.g. F20 + some software stack. I find F20 ami ideal for this but the issue is to locate it[1].
Cheers, milan [1] http://thecloudmarket.com/ 2015-03-19 5:11 GMT+01:00 M. Edward (Ed) Borasky <zn...@znmeb.net>: > On Wed, Mar 18, 2015 at 3:38 PM, David Gay <d...@redhat.com> wrote: > > Greetings! > > > > We sort of ran out of time in today's Cloud WG meeting, but I did want > to ask: > > > > 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: > > > > - AMIs only cost us for storage, so it's not a *huge* cost to maintain a > public AMI > > - 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 > > - 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)) > > - This total number will only grow larger as we add instance-store > AMIs, and so on > > - 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 > > > > 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. > > > > Any input is appreciated. We can certainly talk about this at next > week's meeting, as well. > > > > -- David > > _______________________________________________ > > cloud mailing list > > cloud@lists.fedoraproject.org > > https://admin.fedoraproject.org/mailman/listinfo/cloud > > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > > "In God We Trust - All Others Bring Data" ;-) > > Surely you or someone on the team must have some raw data on usage for > the existing AMIs, including comparisons for how much usage Fedora > AMIs get vs. CentOS AMIs and RHEL AMIs. Don't build / maintain what > people aren't using! > > If you have raw data, I'd be happy to explore it for you - email me > off-list if you need an NDA or something like that. > > > -- > OSJourno: Robust Power Tools for Digital Journalists > > http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists > > Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday. > _______________________________________________ > cloud mailing list > cloud@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/cloud > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >
_______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct