Making "push on green" a reality

• Autores: Daniel V. Klein, Dina M. Betser, Mathew Monroe
• Localización: ;login:: the magazine of USENIX & SAGE, ISSN 1044-6397, Vol. 39, Nº. 5, 2014 (Ejemplar dedicado a: Operating systems ), págs. 26-32
• Idioma: inglés
• Texto completo no disponible (Saber más ...)
• Resumen

  • Updating production software is a process that may require dozens, if not hundreds, of steps. These include creating and testing new code, building new binaries and packages, associating the packages with a versioned release, updating the jobs in production datacenters, possibly modifying database schemata, and testing and verifying the results. There are boxes to check and approvals to seek, and the more automated the process, the easier it becomes. When releases can be made faster, it is possible to release more often, and, organizationally, one becomes less afraid to “release early, release often". And that’s what we describe in this article—making rollouts as easy and as automated as possible. When a “green” condition is detected, we can more quickly perform a new rollout. Humans are still needed somewhere in the loop, but we strive to reduce the purely mechanical toil they need to perform.