#99: AMI lifetimes (Cloud WG members vote needed)
--------------------------------------------------+------------------------
Reporter: oddshocks | Owner: oddshocks
Type: task | Status: new
Priority: normal | Milestone: Fedora 22
Component: Infrastructure & Release Engineering | Resolution:
Keywords: aws, images, vote, policy |
--------------------------------------------------+------------------------
Comment (by oddshocks):
OK, it's been a while. Let's close the book on this. There are a lot of
opinions, so I'll boil it down to a few points that folks can vote on:
1. Final AMIs should be deleted when that Fedora version reaches EoL.
2. Final AMIs should never be deleted.
3. Pre-release AMIs should be deleted after the final release.
4. Major pre-release AMIs (Alpha, Beta, etc.) should be kept around for
one more release cycle after final release, in case they might be helpful
for hunting down a bug origins.
As for me, I vote for 1 and 3. My reasoning for this is:
* If someone needs to spin up an older version of Fedora Cloud on AWS for
whatever reason, they can easily create their own AMI for this purpose.
Additionally, Fedimg provides a bin script that allows one to manually
trigger a Fedimg job by providing it with a URL to a .raw.xz image file.
So if someone needs an old Beta or something, all they need to do is give
Fedimg the .raw.xz file.
* It will save space and money.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/99#comment:6>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
