Welcome!

Microservices Expo Authors: Liz McMillan, Flint Brenton, Jason Bloomberg, Elizabeth White, Yeshim Deniz

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
"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.
Most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes a lot of work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reduction in cost ...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, 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.
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Archi...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
"DivvyCloud as a company set out to help customers automate solutions to the most common cloud problems," noted Jeremy Snyder, VP of Business Development at DivvyCloud, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
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...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., 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.
In his session at Cloud Expo, Alan Winters, U.S. Head of Business Development at MobiDev, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to maximize project result...