Philip Rowlands
Let's face it—manual patching is no fun, all toil. The solution? Better automation, better patching.
"There's no record of what third-party software/versions we use. I don't know what updates are available, and of those, which are the most important. It's hard to get downtime on production systems. There's no test environment for this. I'm scared the upgrade will break stuff, and when it does, rolling back will be even harder."
If these complaints ring true for your organisation, this talk chases each one away with examples of applying automation for an easier life.
Philip Rowlands[node:field-speakers-institution]
Philip Rowlands has been an SRE since before he really understood what it was. Because he doesn't scale, he relies on software for leverage. He has worked over the years on automated telephony, Google Production SRE, Mainframe Linux, and more recently for various financial firms. He cannot juggle.
SREcon21 Open Access Sponsored by Indeed
author = {Philip Rowlands},
title = {Software Patching Needn{\textquoteright}t Be a Can of Worms},
year = {2019},
address = {Dublin},
publisher = {USENIX Association},
month = oct
}
