DevOps in a Box

My long time fantasy has been to demonstrate an entire CI/CD pipeline with continuous operations of applications to discuss behavior driven operations and testing as monitors.

The call for this happened over and over at DevOpsDays to answer: how does one learn DevOps, practice site reliability engineering, or have a full application lifecycle environment?

So let’s create a minimal viable product BTD scenario of my DevOps Automation system, extend it to prefix Governance and suffix Management, and then drive maturity to illustrate and discuss best practices. I’ve been discussing this with my Nutanix colleagues @mjasted and @andytschmid for a while, so here is the outline and plan of action!

Calm.io: a blog series recap!

From September 23, 2015 to May 26, 2016, I took hiatus from my personal blog to explore, explain, and write a number of DevOps articles for my employer on the Calm.io blog. Nutanix acquired Calm.io and I am still part of the Nutanix Calm team, but I’m re-posting these articles on my personal blog since the originals are no longer directly accessible. I am also enhancing them to clarify language, add learnings, and append significant developments as postscripts.

The DevOps Maturity Diagram

The opening of my first Calm.io DevOps article started with:

Let me share what I’ve learned on my journey to DevOps: it is a culturally rendered term and it has a different meaning for everyone.

In that article, I go on to define DevOps and explain the term. Let me share my experience to easily chart the journey of progressive stages to DevOps maturity.

Ten Steps from Pets to Cattle

Why do we need DevOps when IT and Operations succeed in their responsibility for security and uptime, using administrative tools to maintain, backup, and restore those systems? Because the operations domain must be documented, democratized, and distributed to achieve agility before Operations returns to become a force multiplier instead of a keep the lights on organization. Let me demonstrate that traditional values for long lived infrastructure and their retroactive justification do not apply when progressing to a DevOps mindset.

Reconciling Configuration Management and Immutable Infrastructure

Configuration Management in the DevOps World

Demystifying Continuous Integration, Delivery, and Deployment

Infrastructure as Code and Calm Blueprints

Why is DevOps So Hard?

DevOps Demystified

For a term that is not even six years old, DevOps remains a mysterious pursuit for many software engineering organizations. Let me define DevOps to help you understand and chart your own journey. Hint: it is a cultural term!

I Dream of DevOps, but What is DevOps?

DevOps BTD Pattern for Continuous Deployment

What happens when you find the same macro and micro pattern in your automation diagram? You reinforce your goals to improve code flow and service design on the way to test driven development!

Today's DevOps Automation Diagram

#shipit and #failfast: I want to share and discuss the DevOps Automation Diagram for continuous deployment. Via open source and this blog, we can elevate the state of our software engineering and service design!

A DevOps Automation State Diagram

Wonderful accomplishments kicked-off my Infrastructure as Code project. One needs to start with a map of the world before deciding where to focus their efforts. It’s even better when you can optimize and render the new map in real-time!

About Mark

A DevOps professional with pioneering work on the world’s biggest Internet real-time event and web sites across the engineering, operations, content, and marketing disciplines. Mark’s focus is on people and software development along with system design thinking for the whole life cycle: he can build, grow, and manage teams, applications, networks, and servers to work together while planning and nurturing their continuous improvement.