#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 dustymabe):
Replying to [comment:3 jsmith]:
>
> 2) AMIs for final releases should be deleted at the time that the
particular Fedora release goes EOL. For example, when Fedora 20 goes EOL,
the AMI should get deleted at that same time.
I don't know if I agree. I'd much prefer keeping final release AMIs around
for a while (maybe not in all regions, but at least 1) for longer than
that. The "cloud" can be quite useful for spinning up and debugging
something on an older release to see how the behavior differs from how you
remember it behaving and from how it behaves today. I'd compare it to
using a live cd to do the same thing.
One example would be that we find bug in kernel Z and want to quickly spin
up older versions of Fedora to see how far it goes back. I think the cloud
is an interesting use case for being able to test these things out quickly
rather than having to find where the images are stored and figure out all
the options needed to start it locally.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/99#comment:4>
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
