IT Operations Teams are Pushed to Keep Up with Dev
Can DevOps tools help achieve Agile for Ops?
Until now Agile has mostly been applied to Development practices. But where does that leave Ops? Operations teams are naturally being pushed to keep up with Dev’s pace. Ops is struggling though. It’s not from a lack of talent. It’s not from a lack of trying.
Ops teams are working harder than ever but
- They have a different set of concerns than Dev. Rather than focus on quickly turning out new features and updates like their colleagues in Dev, Ops teams also require scale, stability, support, security and speed.
- Due to a lack of automation tool choices, Operations teams have had to rely on cumbersome processes and reviews (CABs, ITIL), custom scripting, homegrown solutions and a nest of SharePoints and spreadsheets to manage change.
Until technology changes, Agile for Ops will remain frustratingly out of reach for most organizations.
Are DevOps tools the answer?
Perhaps. But most “DevOps” tools benefit Dev far more than Ops. Maybe we should consider them “DevDev” tools. Examples include:
- Scripting-centric server and OS configuration management tools
- Continuous Integration tools
- Automated Test tools
Contrast those Dev-friendly advances to the situations that Ops teams face. Operations’ environments often grew organically with siloed pockets of automation optimized for elements of Windows, Linux and WebSphere across on-premise, virtual and cloud environments. Because of this, Ops has less of a toolchain and more “tool pain”. This level of tool complexity undermines efforts to bring Agile to Ops.
Rollbacks are a Symptom. Not a Solution.
As an example, Application Release Automation vendors often tout their easy rollbacks. While helpful, it is also an unspoken admission of how often deployments go wrong. Sometimes it’s code. Often it is the environment configuration. And until Orca, there was not much anyone could do about it.
To support Agile for Ops efforts, teams not only need better coordination and communication. They also require application release automation solutions that are environment-aware and work equally well across multiple platforms and environments, especially in Production.
“It was like finding the needle in a haystack. It was just much easier to roll back.”
Orca supports Agile in Ops
Orca’s application configuration automation works across Windows and Linux ecosystems whether on-premises, virtual or cloud based. Its intuitive interface and at-a-glance drift detection enhance transparency and collaboration across teams.
For Release Managers, Orca combines the application artifacts with the current captured infrastructure configuration data so they promote their business critical applications and configurations simultaneously – achieving environment-aware releases – and nearly eliminating the need for redos and rollbacks because production has drifted or other applications dependent on the infrastructure break.
After Release, Orca continues to monitor, manage and enforce Day 2 compliance in application, middleware, database and OS configurations out of the box for Configuration Managers.
Orca creates a Prod-to-Dev information flow that updates necessary configuration tweaks. This “OpsDev” approach ensures that Dev incorporates the most up-to-date configs for its future releases.
While no single automation platform can deliver “Agile for Ops”, Orca eliminates error-prone tasks and manual work throughout Operations, delivering speed, agility and collaboration that Agile teams need.