Sign in

Patch Tuesday, Patch Wednesday... Or Patch NEVER??

maintenanceoperationspatching8 replies 路 214 views 路 started
Reply
  1. Kai
    @packet_pusher144

    so annoyed rn our pathcing is whenever someone rmeembers and entirely manual, which means some servers get skipped for months. i want to fix this without breaking things... how do u structure rings, approvals and reboots?

    theres also the reboot question xD some of these servers havent been restarted in a very long time, and everyone is scared of what happens if we do. how do you introduce regular reboots without causing a panic the first time??

    2
  2. Omar M.
    @tensor_owl

    hmmm are your applications clustered so you can patch nodes one at a time?

    4 1 helpful
  4. Lars O.
    @larso444

    Track compliance, not intentions. A simple reprot of last patch date and pending reboots per server shows which machines silently fell behind. lmk how it goes

    20 0 helpful
  5. Gabe Petrov
    @gpetrov

    yeahhh reboots are the hard part. tools like needrestart (Debian/Ubuntu) or needs-restarting -r (RHEL family) tell u whether a reboot is actually required, so you only reboot when needed. good luck man!

    2 0 helpful
  6. Noor
    @noor.lund96

    Agree teh window with app owners once and put it in writing, including what happens if a patch breaks something. It turns every monthly argument into following a process. fingers crossed 馃

    6 0 helpful
  7. Ivan C.
    @ivan.celik

    wait what counterpoint to rings: with a small a mixed Windows and Linux estate, a sinlge well-tested window may be simpler than three groups to manage. but hey ymmv

    18 0 helpful
  9. Kai
    @packet_pusher144
    in reply to @noor.lund96

    @noor.lund96 we're starting with security-only auto updates plus a monthly ring-based window for the rest. management signed off.

    6 2 helpful

Reply to this topic

Sign in or create an account to reply.