Top 5 Things to Know When Selecting a DevOps Release Management Solution
Based on a recent discussion between Michael Azoff and Anders Wallgren, here are the top five requirements for selecting a release management solution.
Join the DZone community and get the full member experience.Join For Free
devops is a modern software delivery movement that encompasses agile principles and encourages automation in application delivery. why adopt it? it allows teams to reduce errors due to manual steps and break down silos between teams to improve communication and collaboration between all stakeholders within the business.
whether you’re knee deep in a devops transformation or just getting started, implementing a devops release management solution is an important step along the journey. why? because in today’s on-demand economy, organizations must capitalize on any opportunity to improve application delivery throughout the organization, irrespective of the development processes in place.
based on a recent discussion between michael azoff, principal analyst at ovum , and anders wallgren, cto of electric cloud , i was able to glean why devops release management is a must in order for enterprises to modernize the software delivery process and compete at a higher level. more specifically, michael and anders discussed the top five requirements for selecting a release management solution, which i’ve laid out for you below.
1) application manifest: model and version applications, infrastructure, and middleware.
this is what you’re looking for in an enterprise grade solution—a solution with ease of use in defining an application deployment blueprint, and being able to reuse it and version it and have variations to meet the complex and ever-changing needs of your organization. if you are doing continuous delivery and devops correctly, you should never have to make a change to a deployed application by hand—ideally, changes are made to the application model and then re-released into a production environment. this allows you to make and test changes in one place, and easily keep track of everything in production. having an application manifest is a key facet for a great release management solution.
2) pipeline design: model, version and refactor pipelines, workflows and processes
this is not only an important consideration for selecting a release management solution, but is at the very heart of continuous delivery—the ability to define and manage delivery pipelines for complex legacy applications or newer microservices. for large organizations with lots of technical and process debt, being able to flexibly model and manage that sort of complexity is essential.
ultimately, the whole concept behind devops comes down to the idea that there is the “what,” the “how,” and the “where.” the “what” is the application manifest, mentioned above. the “how” is the pipeline design. what are all the stages this particular application or component or service goes through? understanding your end to end pipeline is very important. you need to have, not just conceptually, but even physically written down somewhere, the end to end of what your software goes through. if you don’t have that that process completely nailed down, you don’t really have a full understanding of what it takes to ship your software. without this complete understanding, it can be much more difficult to have success. by modeling these pipelines, you allow teams to visualize the flow of value through the lifecycle, and make iterative improvements on it in a collaborative and safe manner.
3) pipeline execution: predictably and efficiently deliver legacy and cd-style pipelines and releases at scale
one of the most important things when practicing devops is enabling fast feedback, so getting visibility into pipeline execution as they’re occurring is very important. this provides teams an easy way to troubleshoot problems quickly, and then refactor and optimize the pipeline over time. enterprise pipelines can be very complex and touch a lot of tools—your dev team might be using jenkins, chef, and selenium, and your ops team might be using servicenow, azure cloud, and puppet. we have customers that have over 60 tools as part of their ultimate devops toolchain. for each one of these tools or services you need to make sure you’re getting the best performance possible, and operating them as efficiently as you possibly can. as you execute them, being able to see those executions live as they happen, then collect information about them, and optimize your pipeline helps to make the entire process more efficient.
4) governance, security: role-based access control, traceability, and auditability
this is one of the key functions to consider for an enterprise grade solution. if you just tie together your release capability with tools that still require some manual steps, you’re not able to scale that. this is where a large-scale organization, especially one that is regulated and has auditors, is going to want a solution that can clearly demonstrate that the whole process is governed such that no one can make a change to the process, environments or binaries without it being logged, and that any change that is made has gone through a qa and testing process. those are the sorts of things that are really crucial for the ops people, as they are handed responsibility for ensuring a low-risk environment.
when devops was first getting started, the overwhelming belief around security and governance was: gee, this is going to really bother the auditors . however, it turns out it is quite the opposite—to get good at devops and continuous delivery, you really need to automate everything. what does an auditor want? they want two things:
- document your process and...
- demonstrate you are using that documented process.
in the process of sitting down and automating your software delivery pipeline, you are essentially documenting that process. executing that pipeline gives you the record of what you did: how did we deploy? when? who did it? what was the pipeline that was used? what was the testing? all of those things are now available to be audited.
5) integrations: works with the tools you already use
you want a solution that fits in with the tools and process that you have. it would be a non-starter to show up and say: throw away all of your current tools and let’s use this new thing . it would also be inefficient to have to change your process to fit into some tool’s preconceived notion of how your enterprise should run. make sure you don’t have to change the way you do business and that can help the devops adoption curve quite a bit.
by keeping these top five considerations in mind when selecting a release management solution, you can help ensure your journey into devops and continuous delivery is a much smoother, more efficient, and a more fruitful one. regardless of the tools your organization decides to use, consider first and foremost how you can make your pathway to production a competitive advantage and reap the benefits of an efficient delivery pipeline!
if you want to listen to the full conversation between michael and anders, watch the video on devops.com .
Published at DZone with permission of Sam Fell, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.