andrey adamovich - enterprise flight into devops space - confu
TRANSCRIPT
Andrey AdamovichBio: Developer, coach, speaker, author
Company: Aestas/IT (http://aestasit.com)
E-mail: [email protected]
Linkedin: http://www.linkedin.com/in/andreyadamovich
Lanyrd: http://lanyrd.com/profile/andrey-adamovich
GitHub: https://github.com/aadamovich
SO: http://stackoverflow.com/users/162792/andrey-adamovich
Twitter: @aestasit
••••••••
03
Another emailHi 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...
Francis, VP
10
Jack's bossHi Jack, I understand you have been working on the secret project
servers setup recently, don't forget that we need to keep the
documentation up-to-date yeah?
11
UNKNOWN STATE IIToo many people working on too many issues
Each server is managed independently and without cohesion••
19
Are you serious?Jack and his team can't keep up with the work: Hundreds of servers to
configure, monitor, backup, restore, fix ...
Documentation is left behind
•
•
23
Fear of deployBecause systems are fragile, each deployment is like a trip to the
nearest casino
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
•
•
••
39
The feedback loopThrough 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
•
••••
44
Sharing responsibility IIThe 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
•
•
46
LoggingWhenever 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
•
•
73
MonitoringEmbed monitoring capabilities into your code
Know monitoring channels that your operations use: JMX, SNMP,
HTTP
••
74
ConfigurationStructure application configuration
Backward-compatibile, good defaults, good naming••
75
AutomationAutomation over documentation
Automate everything repeatable:
build
release
deploy
test
••
••••
76
Problem solvingGet developers to solve production problems
Look at how they did it
Post-mortem analysis
•••
78
MonitoringCreate dashboards! Many, but meaningful dashboards!
Analyze your data!
Create alerts!
•••
79
DevOps blogshttp://enterprisedevops.com/
http://itrevolution.com/devops-blog/••
93