News for hackers. Stuff that matters.
Re:The DevOps Phenomenon: An executive crash course by TylerE on Wednesday June 05, 2019 @04:11PM (#20108611)
“Make your devs be on call without paying them”
Re:The DevOps Phenomenon: An executive crash course by not_real_acct on Wednesday June 05, 2019 @07:32PM (#20110149)
> “Make your devs be on call without paying them”

1) let's fire all the DBAs

2) let's fire half the operations team, and outsource the rest

3) let's have the devs do the operational work

What could go wrong?!

Re:The DevOps Phenomenon: An executive crash course by cc81 on Wednesday June 05, 2019 @06:04PM (#20109632)
That might be true for some yes. But for others it might be "We are used to Ops patching machines, doing deployments after lengthy handovers etc and now Dev is saying that they can spin up everything they need in the Cloud and wants to deploy every week using a Gitlab. What now?".

Of course Ops is still needed but what they do has probably changed a lot in this case. And their responsibilities and how they work with Dev must changed.

Re:The DevOps Phenomenon: An executive crash course by beat on Wednesday June 05, 2019 @04:22PM (#20108734)
Depending on on-call crisis management is pretty much the opposite of DevOps. DevOps isn't about being on-call; it's about making on-call unnecessary.
Re:The DevOps Phenomenon: An executive crash course by icedchai on Wednesday June 05, 2019 @05:12PM (#20109199)
This sounds like pure fantasy. How are you going to run a 24/7 operation if nobody is on call?
Re:The DevOps Phenomenon: An executive crash course by beat on Wednesday June 05, 2019 @05:17PM (#20109266)
And what's wrong with fantasy?

More correctly, it's something of an unattainable goal. Can we get rid of on-call? Probably not. Can we drastically reduce the frequency and scope of on-call actions? Absolutely! Can we get to where every single time the on-call person has to take action, there's a post-mortem to understand what went wrong, and fix the automation and monitoring so it doesn't happen again?

Re:The DevOps Phenomenon: An executive crash course by peterwwillis on Wednesday June 05, 2019 @05:56PM (#20109575)
Not 'nobody on call', just 'unnecessary on call'.

Have you ever gotten paged for a transient error that went away by the time you checked it? Or paged for the same error 5 weeks in a row? These, and really most pages, are fixed by DevOps.

In a DevOps system, a feedback loop is used to address all alerts as bugs to be immediately and permanently fixed. After a while, if something breaks, it's because someone just changed something, so it's happening during working hours. Alerts pop up in slack and are acknowledged before a page is sent out. So nobody is getting called.

If your infrastructure is ephemeral and managed as code, you use CI/CD to deploy all changes, and you aren't resource-constrained (at this point, cloud-native infra is only constrained by budget) you shouldn't have stuff crashing randomly at 3am, so there should be very few pages.

Re:The DevOps Phenomenon: An executive crash course by logifail on Saturday June 08, 2019 @07:51PM (#20135989)
> you aren't resource-constrained (at this point, cloud-native infra is only constrained by budget)

Isn't "budget" just another type of resource?