Try our new open source stack builder and get a free, customized report >> Get Started
Adopting open source software for use in the DevOps toolchain without a sound strategy can present a long list of challenges.
In this blog, we show four components of a successful strategy as outlined by the Gartner Report, "Four Steps to Adopt Open-Source Tools in the DevOps Toolchain."
Using open source software for DevOps can offer significant advantages to companies who want to achieve the full potential of DevOps.
According to Gartner, “OSS tools help organizations lower development and operational costs, enable experimentation and prototyping, and reduce the risk of vendor lock-in. Despite these obvious benefits of open-source tools, their ad hoc adoption without adequate planning leads to a fragmented toolset. Likewise, skills required to manage OSS are niche and in high demand, making it difficult to attract and retain talent.”*
But the advantages of open source software don't come without their own set of operational hurdles.
Gartner writes, “OSS tools are not necessarily backed by a supporting ecosystem, and hence may not be preintegrated with the existing IT portfolio. This puts the onus on IT teams to piece together a toolchain using a maze of disparate tools. Gartner sees an increasing interdependence between tools, which comes with its own risks of interoperability and compatibility issues.”*
So how can companies avoid the challenges of incorporating open source software for DevOps?
In the Gartner Report, "Four Steps to Adopt Open-Source Tools in the DevOps Toolchain," they outline four fundamental steps companies should follow when adopting open source tools for DevOps.
Finding the requisite talent for incorporating open source technologies into the DevOps toolchain presents challenges that all organizations need to overcome. Gartner writes:
“Open-source tools generally need more programming effort in the form of scripting and configuration tasks compared to commercial and proprietary solutions. This is because most open-source tools have their roots in the development community. The guiding philosophy behind OSS has been to develop open and free software that is of the developer, by the developer and for the developer.”*
Open source implementation doesn't end with integration. A successful project requires an ongoing, calculated effort. Gartner writes:
“A scalable DevOps toolchain requires managing it on an ongoing basis. I&O leaders must create a process for continually updating the toolchain. As business needs evolve, the tools need to keep up with changing priorities — both technical and functional.”*
Many companies who rely on community support for open source software integrations find that support lacking. Finding the right support fit is critical. According to Gartner:
“A focus on self-support to lower the TCO can lead to under-managed OSS tools. All too often, organizations underestimate OSS complexity (especially in regards to scripting, integration and upgrades) and overestimate community support (for customization and on-demand requirements). This can be problematic if the tools are mission-critical for the organization and IT has to meet rigid SLAs.”*
Picking the right open source tool for DevOps is an integral piece of the integration process. Following a well-established and understood approach is key. According to Gartner, there are four requisite steps that must be followed to select open-source tools:*
Get full details on the recommended steps for adopting open source software for DevOps when you download a complimentary copy of the Gartner Report today.
*Source: Gartner, Four Steps to Adopt Open-Source Software as Part of Your Test Automation Stack, 16 December 2020, Thomas Murphy, Joachim Herschmann, Jim Scheibmeir
**General Disclaimer: This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from OpenLogic.
GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally, and is used herein with permission. All rights reserved.