Hi Jack, I got a call from Sandy, the secret project's PM, she says that
the DEV servers are not ready yet, I really want you to understand how
critical is this project for the organization, please, don't let me down...
Hi Jack, I understand you have been working on the secret project
servers setup recently, don't forget that we need to keep the
documentation uptodate yeah?
Fear of deploy
Because systems are fragile, each deployment is like a trip to the
Devs and SysOps make development cycles longer to be as far as
possible from the deploy date
Slower time to market, systems are down more often
Nobody is happy!
The feedback loop
Through configuration management and deploy automation, we can
deploy more often and reduce risk
The feedback loop gets shorter
Functionalities are rolled out with higher frequency
Systems are always in a known state
Changes to the system can be simulated and impacts calculated
Sharing responsibility II
The focus of DevOps is on automating the tasks performed during the
build, QA and deployment stage
The risk of deployment errors is reduced drastically by having a strong
automated testing suite, automated deployment workflow, well
defined/automated rollback process
Culture : People over processes and tools. Software is made by and
Automation : Automation is essential for DevOps to gain quick
Measurement : DevOps finds a specific path to measurement. Quality
and shared (or at least aligned) incentives are critical.
Sharing : Creates a culture where people share ideas, processes, and
Whenever you add new logging statement to your code, remember
that the guy on the other side can actually read it!
Logging level, message and frequency of logging can help or disturb