Am 19.12.2012 um 16:44 schrieb Brad Knowles <
">
>: That way, Chef would never try to upgrade a package in the first place. Yeah, chef is not the problem in that case. But sometimes there are more or less tons of system packages which are to be upgraded due to bug or security fixes. If you're (or a staff member) doing 'apt-get upgarde' and you're seeing about 80 packages to be upgraded, how do you manage that? Do you check every single package if it's managed by chef and maybe 'locked'? If you don't care and/or you're upgrading a version critical package by a mistake (and let apt-get upgrade do it's work), at least your next chef run will fail and you have to fix your chef role/cookbook/node version attribute for one or more packages, or downgrade the package again. And in the worst case it will upgrade and restart your database! What's your way? --
Holger Amann Sauspiel GmbH Reichenberger Str. 113a 10999 Berlin "> Tel. +49 (0) 30 61651135 Fax +49 (0) 30 61651138 Handelsregister Berlin: HRB 131781 Steuernummer: 29/014/05394 Geschäftsführung: A. Reissner, M. Kavalar |
Archive powered by MHonArc 2.6.16.