Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: @DevOpsSummit, Containers Expo Blog, @CloudExpo

@DevOpsSummit: Article

Rapidly Evolving DevOps Tools By @OmniTI | @DevOpsSummit [#DevOps]

DevOps is all about removing barriers to rapid, safe delivery of new experiences to your customers

Four Ways to Manage Rapidly Evolving DevOps Tools

We all want rapid innovation, but we don't want to have to integrate with it every day.

What Is a DevOps Toolset?
DevOps is all about removing barriers to rapid, safe delivery of new experiences to your customers. Much of this revolves around automating error-prone, human-driven processes so that processes can be standardized, scaled, and varied programmatically. Some of the types of tools used in a DevOps-minded organization might include version control systems, automation servers, and configuration management systems. Many tools can be used across categories, with varying amounts of success. Some vendors offer products that claim to address all of these needs with one solution - most rarely deliver on that promise.

The Pain
Automation is not helpful if each stage of the software delivery and operation cycle automation is isolated. Steps need to flow continuously, with each tool integrating into the overall picture: your CI server needs to talk to your version control system, and probably your IaaS system (for ephemeral test environments). The IaaS system has to talk to the monitoring system, to ensure new nodes are monitored and decommissioned nodes are not flagged as down. And everything has to talk to the communications layer, but not fill the channel with noise.

This is a huge integration job, especially as each piece is changing rapidly. As the DevOps landscape evolves, it can be very hard to get stability in your architecture.

Approach: Stop Time
One approach is to simply adopt a current version of a tool and commit to using it. Instead of dealing with upgrades and tool changes, your team's time will now be focused on delivering features. This may sound appealing as it is much easier to certify a toolset for security, and to fully operationalize it if it does not change. Each toolset change requires changes in run books and training, so fewer changes means less team-impacting shifts.

Unfortunately, this approach is typically not practical for more than a brief period of time (perhaps a year). For example, any new features or bug fixes for the tool will not be available to the team and, worse, as tools come in and out of favor, you may find yourself using a tool that no longer has community support or documentation, or reached an end-of-life. In addition, if one of the tools is a SaaS (which is increasingly likely), you may find that the provider dropped support for your desired version of the API, or shifted its product line to an entirely new API structure.

More subtly, the implementation of the tools may make it very difficult to freeze time. For example, many tools have cross-dependencies on libraries that result in forced upgrades when you upgrade one component. While this is tedious on a day-to-day basis, it can be disastrous if left unmanaged for long periods of time - you may find yourself wanting to upgrade one piece due to a security issue, but forced to upgrade several pieces because of overtight version dependencies. It may even force you to swap out a tool that is no longer actively developed and supported. Each dependency change can have a snowball effect and the longer the time interval between updates, the more likely it will become an avalanche.

Approach: Try to Keep Up
On the opposite end of the spectrum from stopping time, some shops choose to constantly stay on the bleeding edge of the tooling space and adopt tools, versions and workflows as they become available. Typically, passionate individuals will follow a particular project closely, which can translate to expertise within the team and excellent support for the tool.

More commonly, however, individual passion does not translate directly into organizational success. Not all groups will have the same tolerance for instability and integration rework, so it's easy for this approach to become divisive and increase friction among teams. Enthusiasm for the tool may wane, or the passionate individual may be re-assigned or leave the company. Even if support for a tool is broad, staying on top of the latest changes will always require much effort and tradeoffs: the tools that integrate with the new tool may not yet support the new features.

One compromise that often works well is to have a "skunk works," or R&D group, that experiments with new techniques, then sees them through to adoption once they are stable and integrated with the rest of the toolchain in use. It is important to brand this group as a tooling team, not a "DevOps Team."

Approach: Outsourcing
Whenever you're faced with a large integration project across several closely related tools, consider looking to a major vendor for an integrated approach. For example, using a combination of AWS offerings, you can construct a working, nearly complete DevOps toolchain that you can be assured will work well together. By spending more on professional services, you can also have Amazon build out any missing pieces of integration to ensure you have a smooth flow. Other vendors provide similar offerings.

Vendor lock-in is a major drawback here. It will be very difficult, if not prohibitive, to switch providers at a later date: the APIs, tool features, and capabilities will be similar but different enough to invalidate all integration efforts to date. Additionally, outsourcing the entire toolchain will not be cheap, and the ever-evolving nature of the tools means that the custom development cost will never go away - the integration work will never be "done."

Most perniciously, however, is that by hiring people outside your organization to make your DevOps toolchain, you explicitly push outside the lessons learned by having developers and operations staff work side by side to solve each other's' problems. When people share their problems, they tend to come up with solutions quickly. But if a vendor is providing the interface, tooling, and support, you have a big wall between the people who encounter a new problem and the people who are remedying it. That is antithetical to the DevOps approach, and your team will not magically "become DevOps-y" if they don't actually solve problems together.

Approach: Make a Local Wrapper API
Increasingly the underlying components of the toolchain are being offered as services with an API in front of it. In some cases the service is run on-premises, in others they are SaaS; but either way, the coupling is much looser. This allows you to write your own API end points, which perform the tasks your internal customers need to perform, while calling out to the various back-end tools and services. Users need not know which components are actually tools (possibly with awful dependencies) and which are services; in some cases, you may also choose to hide provider-specific details, such as which cloud provider was used to provision a node. Passionate individuals may work on the internal API layer, adapting it to the latest version when new features are desirable. This can usually be done while still providing a stable, backwards-compatible API to the internal customer. The local wrapper API is also an ideal location for various bits of integration (like security checks, inventory management, etc.).

Locally developed APIs are not without their drawbacks. Each internal customer has to agree to use it; the documentation and support must be excellent, and the value compelling or people will revert to simply using the various tools directly. That may not be a problem, especially for groups with unusual needs. Interface levelling - in which unique features of a provider are masked in favor of broader commonalities - can often be more of a problem; in some cases, it may make sense for a user needing Azure-specific features to have an Azure-specific part of the API, for example. Finally, it can easily turn into "one API to rule them all" in which scope creep forces the pull of more and more services under the same roof that was not designed to accommodate the diversity.

That highlights an important aspect of the local wrapper API: when internal customers have unmet needs, they can reach out internally to the API developers and operators - which, in fact, may be the same people.

Conclusion
There is no obvious, simple way forward when dealing with rapidly changing toolsets. Each approach has serious drawbacks, but some compelling advantages. Most organizations will end up using a mixture of approaches - perhaps "stopping time" with automation tools like Chef, but staying bleeding edge by leveraging latest features from a platform like AWS, and a custom local API gluing together their monitoring, communications and inventory control systems. Approaches will vary from group to group as well. As with anything in DevOps, the goal is not some ideal destination as implemented at a unicorn company, but rather gradual, continuous improvement to the processes that most impact your ability to deliver and operate quality software quickly.

More Stories By Clinton Wolfe

Clinton Wolfe leads the DevOps Practice at OmniTI and has been helping organizations deploy and operate web-scale applications since early days of the web. He is especially versed in testable infrastructure, the people problems of highly constrained workplaces, and aligning business needs with engineering capabilities. He collects metrics for fun.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.