Welcome!

Linux Containers Authors: Zakia Bouachraoui, Yeshim Deniz, Elizabeth White, 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
The challenges of aggregating data from consumer-oriented devices, such as wearable technologies and smart thermostats, are fairly well-understood. However, there are a new set of challenges for IoT devices that generate megabytes or gigabytes of data per second. Certainly, the infrastructure will have to change, as those volumes of data will likely overwhelm the available bandwidth for aggregating the data into a central repository. Ochandarena discusses a whole new way to think about your next...
DXWorldEXPO LLC announced today that Big Data Federation to Exhibit at the 22nd International CloudEXPO, colocated with DevOpsSUMMIT and DXWorldEXPO, November 12-13, 2018 in New York City. Big Data Federation, Inc. develops and applies artificial intelligence to predict financial and economic events that matter. The company uncovers patterns and precise drivers of performance and outcomes with the aid of machine-learning algorithms, big data, and fundamental analysis. Their products are deployed...
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...
All in Mobile is a place where we continually maximize their impact by fostering understanding, empathy, insights, creativity and joy. They believe that a truly useful and desirable mobile app doesn't need the brightest idea or the most advanced technology. A great product begins with understanding people. It's easy to think that customers will love your app, but can you justify it? They make sure your final app is something that users truly want and need. The only way to do this is by ...
CloudEXPO | DevOpsSUMMIT | DXWorldEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Cell networks have the advantage of long-range communications, reaching an estimated 90% of the world. But cell networks such as 2G, 3G and LTE consume lots of power and were designed for connecting people. They are not optimized for low- or battery-powered devices or for IoT applications with infrequently transmitted data. Cell IoT modules that support narrow-band IoT and 4G cell networks will enable cell connectivity, device management, and app enablement for low-power wide-area network IoT. B...
The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
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...