“Just fell in love with @Rundeck to let non-ops people run @ansible playbooks.”-CTO, Digital Agency
"But... how?" is an immediate response we often hear when presenting the idea of moving to a Self-Service Operations model that allows the standardization and delegation of operations tasks to people outside of traditional ops roles. This is usually followed by a statement like "the benefits make sense and the end-state is appealing, but I'm having difficulty seeing how we get from here to there."
We've learned that this uncertainty is usually an artifact of the historical belief that automated operations procedures are a monolithic task. As people separate their thinking about automated operations procedures into distinct elements, the belief dissipates, and the path to Self-Service Operations becomes clearer. These elements are: the ability to define a procedure, the ability to execute that procedure, and the governance around that procedure. Once separated, you can start to see how each element can be distributed to the teams and roles in your organization where it most improves the flow of work or utilization of labor.
I'm excited about a new set of features that are deceptively simple, yet add a significant level of power to the Rundeck platform.
I'm talking about the ability to capture data in one workflow step and use it in another, automatically mask sensitive data in the job output, and highlight or format output.
To see just how easy and powerful these new features are, watch this introductory video by Rundeck's Alex Honor.
DevOps and digital transformations have brought an unprecedented increase in the pace and volume of daily change in IT. While this may sound like great news to development and product groups, IT operations management is often alarmed by the potential risk that its already overloaded workforce will be squeezed beyond the breaking point.