Enterprise flight into DevOps space

• Bio: Developer, coach, speaker, author
• Company: Aestas/IT (http://aestasit.com)
• E-mail: andrey@aestasit.com
• 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: @codingandrey, @aestasit

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... Francis, VP

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 up-to-date yeah?

Hey Jack, we can't deploy anymore to our DEV servers. What the hell is going on?

• Because 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!

• 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

• 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 for people.
• Automation : Automation is essential for DevOps to gain quick feedback.
• 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 tools.

• ShadowOps
• DevOoops

• 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

• Structure application configuration
• Backward-compatibile, good defaults, good naming
• Do not mix technical and business configuration

• Embed monitoring capabilities into your code
• Know monitoring channels that your operations use: JMX, SNMP, HTTP

• Technical metrics:

  • CPU, Memory, Disk
  • Resource pools
  • Network I/O
  • Transactions/requests/operations per second/minute/hour
  • Database performance

• Business metrics

• Puppet
• Chef
• Ansible
• Salt

• Same OS version,
• same components,
• same configuration
• as in production environemnt,
• but running in virtual machine on your laptop or at some cloud provider

1. DEV << QA <<< PROD
2. DEV < QA < PROD
3. DEV ~ QA ~ PROD
4. DEV = QA = PROD

• System administrators know how to install standard OS packages
• Just make one for them!
• RPM, DEB, MSI... - it's not that hard to master!

• build
• release
• deploy
• test
• backup
• migration
• restarts

• Get developers to solve production problems
• Look at how they did it
• Post-mortem analysis

• Create dashboards! Many, but meaningful dashboards!
• Analyze your data!
• Create alerts!

• Aggregate logs
• Analyze logs
• Rotate logs
• Clean logs

• Puppet
• Chef
• Ansible
• Salt

• Backups!
• Test your backups. Seriously!
• Capacity planning.

• Local: VirtualBox/VMWare/Parallels (+ Vagrant)
• OS: Docker
• Remote: Various cloud oferrings

• AWS
• VMWare
• Azure
• Google Cloud
• OpenStack

• Puppet
• Chef
• Ansible
• Salt

• Logstash
• Graphite
• Kibana
• Grafana
• Dashing

• Spotify
• Netflix
• Etsy
• Twitter
• Amazon
• Google
• GitHub

• http://enterprisedevops.com/
• http://itrevolution.com/devops-blog/