LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

7 responses to “NoOps Is As Legitimate As DevOps”

  1. Chad Arimura

    Well said Krishnan.

    There is a perception of threat to ops and with any threat comes pushback and controversy. The reality is that ops is not going away, it’s being 1) pushed up stack (as James Urquhart pointed out), 2) into the service providers themselves (as you pointed out), and 3) into more strategic ops roles — think value creation beyond “are my apps up and running”.

    Of course the early adopters are startups, dev shops, and smaller workgroups within larger organizations, but as PaaS matures and more core components of the stack become available as part of the platform, wider adoption will surely follow.

  2. Sacha Labourey

    Krishnan,

    Great blog.

    I really like the NoOps white paper by Forrester as they define it in a very un-emotional/un-marketing way and back it with with clear examples of what they mean. I also like “NoOps” because it forces people to PAUSE and THINK; this is exactly what needs to happen for people to really grasp what this significant paradigm shift means to their own environment.

    Now, I don’t think IT should feel overly threaten by this, au contraire. Yes, things are going to drastically change, the job they are doing today is not the job they will be doing tomorrow. Fine. But the move to the cloud will also create lots of new “IT roles”. Think about having a unified identity management among your multiple cloud providers, think about your map of vendors and how their respective SLA will fit together, think about your enterprise data “schema”, now fully distributed (with part of your data in salesforce.com, part in Zendesk, part in WorkDay, etc.) will make sense as a whole, think about how to smartly sync-up some of that data together, etc. This won’t fall from the sky, Ops or NoOps, and will require smart individuals and strong processes, attributes that IT teams typically have.

    Also, the DevOps/NoOps debate is also slightly “Palo Alto Echo Chamber’esque” :) If you go out in the field, you quickly realize most companies are not in that debate. Their day-to-day concerns are called servers, middleware, upgrades, provisioning and they are starting to think how the cloud can help them in a very pragmatical way i.e. “what’s required for app A to live in the cloud?” It is not about Ops, DevOps, NoOps, PlainOps, FakeOps, OpsIDidItAgain. The only certainty they have is that, all things being equal, if they can have the smoothest experience and have to worry as little as possible about provisioning, uptime, alerting, monitoring, scaling, updates, patching, etc. then they like it – however you call it. Remember: the cloud is about THE SERVICE! ;)

    Onward,

    Sacha Labourey
    http://www.cloudbees.com

  3. Jeff Schneider

    Wiring PaaS elements together, configuring them, defining security settings, setting auto-scale properties, validating auto-scaling trigger thresholds, creating IaaS & PaaS monitors, creating application monitors and smoke tests, creating SSL certificates, managing the changing DNS host names, managing dev/test/stage/prod environments, automating the deployment/installation of software binaries (and source for dynamic languages), enabling run-time configuration changes to PaaS elements, scheduling backups, validating restores work, automating pager duties (yes, things break), implementing semaphores on deployment dependencies, bundling AMI’s, mapping machine images across availability zones for HA, seeding databases, … are only a few example of what people do to create applications based on PaaS, automate their deployment pipelines and significantly reduce the level of effort to operate their systems.

    PaaS based development is a huge productivity improvement. What we’re finding is that people actually spend MORE time on DevOps tasks in Apps-on-PaaS. The reason is simple, they’re aiming for a higher level of automation and cost reductions. They believe they can achieve these goals through proper DevOps automation. Again, I do not subscribe to “MiracleHappensHereOps / NoOps”.

    NoOps is a No-Op.

  4. Can We Use DevOps And PaaS In The Same Sentence?

    [...] spite of my post yesterday explaining the nuances behind the usage of the term NoOps, vendors with tools in Ops and DevOps [...]

  5. Mu Dynamics Blog » NoOps, ShmoOps and Somebody Else’s Problem

    [...] week there’s been much talk about NoOps with posts from @adrianco, @allspaw and @krishnan, to name a few. It all started with this infographic from @appfog. The challenge is that the [...]

  6. NoOps means Ignorance - badgerhound industries -

    [...] NoOps Is As Legitimate As DevOps [...]