On 2011-07-28 8:36, Tim Flink wrote: Instance storage of this sort does not go away when instances are merely rebooted. It is only destroyed at instance termination time. Creating Fedora respins midway through a release consumes time and resources that, given our difficulty with the F15 images alone, we appear to lack. Building updates into images also calls GPL compliance into question, as updates that are superseded by newer updates get removed from mirrors and eventually garbage-collected by koji. This is not the case for packages in the release repository, which stick around forever, or the Fedora Unity respins, which provide source media alongside the binary media. I wouldn't be too concerned about supplying people with updated cloud images; they are really only a baseline that people can respin for themselves and others as they wish. People who wish to use EC2 merely as a pay-per-hour VPS provider can use either type of instance and keep it up to date via the usual channels like they are used to doing elsewhere. People who are running cloud applications have designed their applications such that individual instances are unimportant and replaceable. In those cases it is frequently easier to simply terminate out-of-date instances and replace them with new instances from fresh system images that cloud application writers already create as their applications evolve.

On Thu, Jul 28, 2011 at 01:57:20PM -0400, Andy Gospodarek wrote: Amazon has deprecated S3 backed instances at this point. And yes, they are non-updateable (without respinning the base image). --Hugh -- == Hugh Brock, hbrock(a)redhat.com == == Engineering Manager, Cloud BU == == Aeolus Project: Manage virtual infrastructure across clouds. == == http://aeolusproject.org == "I know that you believe you understand what you think I said, but I’m not sure you realize that what you heard is not what I meant." --Robert McCloskey