Two months ago, I gave a talk to a business team about chaos engineering in practice. This post mainly organizes the content of that talk. Click to view the presentation 1. The Origin of Chaos 1.1 The Birth of the Discipline of Chaos Before discussing chaos, let us first think about the relationship between chaos, chaos engineering, and our production services.

1. What Is ChatOps GitOps, ChatOps, AIOps, and the like (hereafter NewOps) are emerging operations philosophies that have appeared in recent years. NewOps separates Ops out of its chaotic state into two parts: one facing users, trending toward being more human, auditable, and traceable; the other facing infrastructure, trending toward being more programmatic, automated, and intelligent.

1. About Labels In an earlier document, How to Create GitLab Labels Automatically with python-gitlab, I already explained that Labels can be used for simple project management. A team usually has more than one code repository. To reduce the cost of communication and learning, besides using a consistent toolchain, it should also reach a certain basic consensus.

1. What Left Shift Is It should be noted that “left” here is not the political left, standing for conservatism or radicalism, but the left that describes a process — moving things earlier in time. I first came across “left shift” while researching automated testing. The idea is appealing, and putting it into practice is simple.

1. What Agile Development Is In the traditional software development model, the cycle from raising a requirement to final delivery is long. The waterfall model proceeds through six steps: requirements analysis, design, coding, integration, testing, and maintenance. Once a requirement changes, the work invested earlier is not only wasted but also hard to adjust.