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
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 serve
or "Apps - Ops = Openwhisk" to refine it further?
On Thu, May 4, 2017 at 7:04 AM, Rodric Rabbah wrote:
> I like Michael's "Serverless - by Apache"
> I'd refine Daniel's to "Apps without Ops" or "Apps with NoOps"
>
I like Michael's "Serverless - by Apache"
I'd refine Daniel's to "Apps without Ops" or "Apps with NoOps"
If you're not afraid of some controversy (at least it'll start some more
conversations)... :)
"Apps without the Ops"
Michael Marth wrote on 05/03/2017 03:09:56 PM:
>
> Initial idea:
> “Serverless - by Apache"
>
>
>
>
> On 03/05/17 04:02, "Carlos Santana" wrote:
>
> >I’m attending ApacheCon May
