I agree with Nick there is devils, devops is large spectrum of practices. I see that some tasks you keep doing, another set you do differently and another set you don't worry like which kernel patch to apply, orchestrating containers, setting up nginx/load balancers and capacity planning.
But there is plenty testing, automation, blue/green swap, monitoring, logging, tracing and debugging and other operations task for your actions "Serverless - by Apache" its growing on me Now to see if I can print a tshirt by then - Carlos Santana @csantanapr > On May 4, 2017, at 2:46 PM, Nick Mitchell <moose...@gmail.com> wrote: > > maybe a bit of caution is needed in the use of "no-ops"? amongst the first > things i did with my serverless apps is.... get jenkins health checks going! > > you may not have a server, but you have assets that can, and so will fail. > > perhaps the implication of "no-ops" is that skill set needed for serverless > ops different than for conventional ops? yes, certainly, but, not as much > as i would have expected. > > don't need DBA skills? that's just DBaas, not serverless (functions as > service). > > don't need Express skills? we have already seen, in a recent email/blog > post, that people want to pull all of that over into the serverless world. > > don't need networking skills? ha! many of us have already spent plenty of > time with 502s --- and to no fault of openwhisk! rather, it's a fact of the > loosely coupled, highly firewalled/gateway'd world we live in. > >> On Thu, May 4, 2017 at 2:13 PM, Eric Na <hyunwoo...@gmail.com> wrote: >> >> or "Apps - Ops = Openwhisk" to refine it further? >> >>> On Thu, May 4, 2017 at 7:04 AM, Rodric Rabbah <rod...@gmail.com> wrote: >>> >>> I like Michael's "Serverless - by Apache" >>> I'd refine Daniel's to "Apps without Ops" or "Apps with NoOps" >>> >>
