yum-cron in the cloud images?

[Garrett Holmstrom]

On Fri, Dec 14, 2012 at 6:17 AM, Matthew Miller
<mattdm at fedoraproject.org> wrote:
> On Fri, Dec 14, 2012 at 08:05:06AM -0600, Troy Dawson wrote:
>> It's frustrating enough on a local machine when an update goes wrong.
>> But on an Amazon machine, you have no console during bootup.  So if
>> something is going wrong during bootup ... you're out of luck.
>
> Yeah. On the other hand, with Fedora's fast pace, leading edge nature, and
> huge package selection, I feel like we're doing our users a disservice by
> not providing some level of protection.

This is a case for publishing new images periodically, not causing
churn on instances that already exist.  If we were talking about a VPS
provider then this might be different, but on a cloud instances are
ephemeral.  If I want to make a fleet of instances get the latest
stuff then I'll create a new image (or sometimes a new user-data
script) and replace all of the old instances with instances of the new
image.

> What if we did security updates only, by default? (Right now, yum-cron
> doesn't support this, so it'd be a F19 feature.)

I'd be okay with this (or even an all-kinds-of-updates version) if and
only if it becomes the default for the whole distribution.  A cloud
image is even less well-suited to automatic updates than a desktop or
server, and if we can't justify it for those cases, it definitely
doesn't belong here either.

--
Garrett Holmstrom