Welcome!

Linux Containers Authors: Zakia Bouachraoui, Elizabeth White, Yeshim Deniz, Liz McMillan, Pat Romanski

Related Topics: @DevOpsSummit, Linux Containers, Containers Expo Blog, SDN Journal

@DevOpsSummit: Blog Post

Keep CALMS and Release More By @TrevParsons | @DevOpsSummit [#DevOps]

How to Keep CALMS and Release More!

How to Keep CALMS and Release More

DevOps is fundamentally changing.

It is no longer considered a fad by those working with the latest development tools. Now, DevOps emphasizes people and processes as much as the cool tools, and there are many different approaches to bringing them together.

If you Google search for "DevOps flow," you will find lots of flow diagrams and methodologies. While each one highlights different priorities and names, they all have the same general themes.

  1. Start with people
  2. Bring in automation
  3. Stay lean
  4. Measure everything
  5. Share

This strategy is called the CALMS approach.

Keep CALMS and Release more

CALMS vs ITSM?
CALMS grew out of the need to bridge the gap between ITSM principles and DevOps. The challenge faced by those familiar with ITSM, who might view as an alternative to DevOps, is understanding where they differ. If the differences are not immediately obvious when viewing the ITSM documentation examples, they will be as you explore the general concepts of the methodology.

The CALMS acronym will help illustrate these different methodologies at a quick glance, and as you observe culture is the first point, it quickly becomes clear that a side-by-side comparison is not possible.

ITSM is generally focused on documentation, change control, and repeatability, where DevOps is focused on people who drive results. With ITSM, repeatability is a main component, but the structure and processes are not primary objectives.

What Does CALMS Stand For?
Culture

Culture is not something you implement; it is the natural environment that houses the entire development team. Entire means all the developers, QA, AND operations. In this eco-system of people and tools, the culture is necessary to remove barriers and facilitate collaboration to hit team objectives.

There is nothing fluffy about culture.

Culture plays a major role in the success of the business so getting it right is important. In the case of DevOps where red tape, time spent on needless activities, and with the silos of responsibilities, bad culture hinders goal completion and company objectives.

Automation
Once you have culture in place you can focus on automation. This is not just creating scripts for infrastructure or using Selenium for functional testing.

Automation is the idea that you should program everything.

Find a way to lead all new initiatives with automation and then think about automation constantly to help scale.

Lean
As you build automation you also have to remember to be lean.

Running lean means keeping everything to a minimum.

Tools, meetings, and even sprints should all be kept lean. This also is often part of the culture, when you are a minimalist, and every tool, and process you select has a purpose.

It also applies to your teams.

You must keep teams to an effective size to avoid diminishing returns from too many cooks in the kitchen. If the application complexity warrants larger teams, then break them into sub groups, as many large organizations have done.

Measurement
Measurement is the glue that keeps it all together. When you are a lean organization automating everything, you can lose the ability to remember and document it all. Naysayers of DevOps can quickly point to this challenge as being a reason to avoid DevOps, and they are not wrong.

If a team does not have visibility into everything, something will eventually go horribly wrong.

When measurement is implemented correctly this should not happen. If you measure everything and think in terms of reporting on your development team and processes, you will have the ability to analyze and correlate all processes, tools, and production data together.

However, this cannot be done in the traditional spreadsheet style system. In the minimalist organization, you do not have time to inventory everything, which is prone to human error anyway.

Measurement has to happen using more advanced tools for data collection, like a log analysis platform. One that goes beyond event monitoring and reporting, and can push insights to you. This way you can avoid thinking about pulling information on regular tasks or maintenance, and can delegate the effort to the platform. Once you know what you regularly need to observe, you can build a dashboard that (in a glance) tells you everything you need to know.

Sharing
With all this data, you need to disseminate what is learned, what went wrong, and how to correct.

The benefit of breaking down the walls between developers and operations is the information flow becomes bi-directional, and you avoid the concept of "throwing things over the fence". However, this is worthless if information is not shared proactively.

Sharing is not just reporting facts, it is regular exchanging of ideas across teams.

Developers can suggest QA and operations try new tools to improve production quality, and operations can suggest functionality that helps back-end management.

Use CALMS for Loose Direction, not GPS
All DevOps flows similar to CALMS serve the same general function, which is to be used as a guide, and not a definitive answer.

What is unique with the CALMS description of DevOps is the emphasis on culture.

Culture is not easy, nor straight forward. It takes time to mold unless you have the luxury of hiring all awesome people. Sometimes it is awkward to start, but eventually becomes habit.

Because CALMS is a guide, not an answer, you must remember that it will not be perfect.

I personally believe CALMS is missing an R and an I. CRIALMS, (which sounds like something from World of Warcraft). Results and iterations are also incredibly important. Both, like the above, are culture and directives in parallel.

By nature if you are results driven, you will be analytical, and your results will come faster with leaner operations that collaborate well. In order to execute with the this framework, you need to evaluate your progress on small fast chunks; iterations.

This exercise is important not because CALMS should, or should not, be a standard we throw around like candy, but because when new movements come along (like DevOps) there needs to be a path from the hype to the practice. CALMS helps those who have lived operations and those who do not know what operations even is, but realize they have to work with them.

More Stories By Trevor Parsons

Trevor Parsons is Chief Scientist and Co-founder of Logentries. Trevor has over 10 years experience in enterprise software and, in particular, has specialized in developing enterprise monitoring and performance tools for distributed systems. He is also a research fellow at the Performance Engineering Lab Research Group and was formerly a Scientist at the IBM Center for Advanced Studies. Trevor holds a PhD from University College Dublin, Ireland.

IoT & Smart Cities Stories
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
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...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
Chris Matthieu is the President & CEO of Computes, inc. He brings 30 years of experience in development and launches of disruptive technologies to create new market opportunities as well as enhance enterprise product portfolios with emerging technologies. His most recent venture was Octoblu, a cross-protocol Internet of Things (IoT) mesh network platform, acquired by Citrix. Prior to co-founding Octoblu, Chris was founder of Nodester, an open-source Node.JS PaaS which was acquired by AppFog and ...
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Cloud-enabled transformation has evolved from cost saving measure to business innovation strategy -- one that combines the cloud with cognitive capabilities to drive market disruption. Learn how you can achieve the insight and agility you need to gain a competitive advantage. Industry-acclaimed CTO and cloud expert, Shankar Kalyana presents. Only the most exceptional IBMers are appointed with the rare distinction of IBM Fellow, the highest technical honor in the company. Shankar has also receive...