Control and speed are at too often at odds

Time for ITIL-DevOps coexistence

Many organizations are consumed with the need for speed –  the business imperative to release software faster and capture new market opportunities in the process. Whether or not they aspire to be the next Netflix, these groups naturally gravitate to DevOps and Application Release Automation with their promise of Continuous Deployment…until, of course, the Compliance, Security or ITIL teams move in. These teams naturally place a high value on change control, documented process workflows and audit-readiness. Can DevOps and ITIL coexist?

ITIL-DevOps takeaways summary from Gartner Datacenter 2016

  • IT Ops teams still experience uncertainty about the relationship between ITIL and DevOps.
  • ITIL is best for workflows that require high levels of certainty, governance, and control.
  • DevOps, on the other hand, enhances workflows that require speed and innovation.

The recommendation was logical. Use the right framework for the situation at hand.

But is there another way? A way that accelerates application releases while also providing lock-down configuration change control?

Faster, environment-aware application releases

As Orca releases an application from Test to Staging or from Staging to Production, it is aware of the current full stack configuration for the target environment – so it promotes your business critical applications and production-level configurations…simultaneously.

Central, secure configuration change control

  • Orca eliminates the need for direct access to servers, a major source of uncontrolled IT changes and security vulnerability.
  • Central control prevents unauthorizedeven well-intentioned changes enhances security and enforces compliance with a DevOps Security approach. 
  • IT is no longer dependent on homegrown scripts, spreadsheets and tribal knowledge to manage changes.