A Playbook for Modernizing the Mainframe, Part 6
Earlier in our playbook, Modernizing Development on Mainframe, my colleague Sujay Solomon outlined the key requirements for DevOps architects to build a robust continuous delivery pipeline for cross-platform DevOps. Success is achieved when DevOps architects have the flexibility to use their preferred industry-standard or home-grown solutions, as well as an easy-to-use UI for configuring mainframe interactions. Only then will they be empowered to architect a DevOps pipeline capable of mitigating strategic risks, amplifying performance of teams in development, test, operations and security, and managing intelligently against increasing cost pressures.
Address the elephant in the room
Choice in tooling and friendly UIs make a solid first step towards modernization, but more is required to resolve issues arising from developers not having adequate access to the mainframe. This becomes a huge problem during application testing, which due to the strict governance involves a highly laborious process to meet regulatory compliance. The result? In my discussions with customers, I’ve learned that simply fulfilling a developer’s change request to provision a test environment may take months, with IT operations needing to oversee every step the process.
Everyone loses with this outcome. On one hand, development teams cannot bring changes to market at the pace required to anticipate and meet escalating customer expectations. On the other hand, the exorbitant cost of provisioning and then maintaining these environments taxes an already shrinking IT budget. Altogether, it creates considerable friction between development and operations, inhibiting progress towards a more unified organization characteristic of DevOps.
Apply an A+ philosophy
Before, with access to preferred tooling came greater agility. Now… with automation of labor-intensive processes comes greater autonomy. Autonomy in the form of self-service provisioning affords IT operations freedom from dedicating time and resources to supporting development teams. Namely, development teams can leverage self-service provisioning capabilities to create dev/test environments and facilitate shift-left testing – all without generating an extra burden for IT Operations.
Project Brightside enables non-mainframe application developers to provision and interact with IBM middleware in a very user-friendly and script-friendly way, and benefit from transparent interaction with the z/OS on which the service is provisioned. Developers continue to interface mainframe through the modern, easy-to-use Command Line Interface, or CLI. Plus, they can continue to use their standard desktop, since Project BrightSide does not require persistent SSH/telnet connection to USS on z/OS.
Transform the mainframe experience
With Project Brightside, what used to take months can be accomplished in mere minutes.
The end result? By leveraging self-service provisioning businesses can:
- Eliminate bottlenecks: Development teams are further enabled to develop and delivery changes at the speed of business by leveraging self-service provisioning that is automated, standardized, and easy-to-use.
- Optimize resourcing: Freed from the need to support development with test environments, IT operations can focus time and resources on optimizing mainframe operations.
You can catch a sneak preview of Project BrightSide here. Plus, be sure to visit us at CA World, where we will be presenting the CA Technologies vision for realizing modernized development on mainframe.