#62: notification of pending security updates in motd ------------------------------+-------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: normal | Milestone: Fedora 21 (Alpha) Component: Cloud Base Image | Resolution: Keywords: | ------------------------------+-------------------------------- Comment (by langdon): I am not sure if this is the right place to answer this (vs the bug reference in comment:1), but the reason many cloud instances do not get updated is because they operate in a MTTR vs. a MTBF model. In other words, an instance should never get updates, rather, when updates are required, a new instance (w/ the updates) should be created, the application tested, traffic migrated, and then the original instance is destroyed. In recognition that most computing stereotypes are well shy of the 80% rule :), I think having this function, perhaps even by default, is a good thing, as long as it is "disable-able" easily. In many environments, the performance and/or network hit of collecting this information would not be acceptable. -- Ticket URL: <https://fedorahosted.org/cloud/ticket/62#comment:3> 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