Download as ODP, PPTX
![class sudo {
package {'sudo':
ensure => latest,
}
file {'/etc/sudoers':
owner => root,
group => root,
mode => '0440',
source => 'puppet:///files/sudo/sudoers',
require => Package['sudo'],
}
}](https://image.slidesharecdn.com/devops-120602091055-phpapp01/85/Dev-ops-37-320.jpg)
Uploaded byEslam El Husseiny
Dev ops
DevOps aims to bridge the gap between development and operations by fostering collaboration. Key aspects of DevOps include establishing a collaborative culture through open communication and engagement between teams, automating processes like builds, deployments, testing and system configuration, and implementing monitoring of applications and infrastructure through metrics and logging to ensure stability and enable issues to be quickly identified and addressed. Tools like Puppet, Munin, Graphite, Logstash and Graylog can help operationalize these aspects of DevOps.
More Related Content
Dev ops
- 1. DevOps Introduction Ops' job is NOT to keep the site stable and fast Ops' job is to enable the business (this is dev's job too)
- 2. Who am i? Systems Administrator @ DevOps Infrastructure as a code ”Puppet” Cloud Computing … @EslamElHusseiny
- 3. Dev or Ops? 6 days after a successful deployment, server experiences troubles ”high load, resources leak”
- 4. Dev or Ops? There is an issue with build server. Code isn't building.
- 5. Dev or Ops? Software is deployed to the test environment. You can't login to application.
- 6.
- 7.
- 8.
- 9. Role of Devsand Ops
- 10. Role of Devsand Ops Dev Create changes Add / modify features Ops Maintain stability Create / enhance services
- 11. Role of Devsand Ops Dev Create changes Add / modify features Ops Maintain stability Create / enhance services
- 12. So ? The problem Disconnect between groups Devs don't deploy consistent software Ops motivated to resist changes Devolpment process is Agile Operations process is Static
- 13.
- 14.
- 15.
- 16. What is DevOpsthen ? ”DevOps is an approach to bridge the gap between agile software development and operations” agileweboperations.com Collaborative mindset of Devs and Ops C.A.M.S
- 17.
- 18. Culture Relationships Engage early, engage often Be open Eradicate ”lastmile syndrome”
- 19. Culture Communication Talk is cheap (get out of your chair) Involve each other in core proccesses and decisions Ask Questions Don't say ”No”
- 20.
- 21. Automation What ca be automated ? Builds Deployments Testing Monitoring Selfhealing System configuration
- 22.
- 23. Metrics Capture, learn, improve. Assist in: Capacity planning Trend analysis Fault finding
- 24.
- 25.
- 26.
- 27.
- 28. Before Talk about functional requirements Talk about nonfunctional requirements Security Backups Availability Upgradeability Configuration management Monitoring / Metrics Logging
- 29.
- 30. After Release Continue to run tests Monitor application and system Issues (might happen) Post meetings
- 31. What are wedoing ?
- 32.
- 33.
- 34.
- 35.
- 36. node default { include ssh include sudo include ntp } node product.dev inherits default { include nginx include tomcat5 } node product.test inherits default{ include nginx include tomcat6 }
- 37. class sudo { package {'sudo': ensure => latest, } file {'/etc/sudoers': owner => root, group => root, mode => '0440', source => 'puppet:///files/sudo/sudoers', require => Package['sudo'], } }
- 38.
- 39. Let's get handson It's deploymnt time
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49. Monit check process unicorn with pidfile /var/run/unicorn/unicorn.pid start program = "/etc/init.d/unicorn start" stop program = "/etc/init.d/unicorn stop" if mem is greater than 300.0 MB for 1 cycles then restart if cpu is greater than 50% for 2 cycles then alert if cpu is greater than 80% for 3 cycles then restart group unicorn
- 50.
- 51. Metrics how many customers are on my site? how many customers were on my site yesterday?
- 52. Metrics how slow is paypal's api? how slow was paypal's api yesterday?
- 53. Metrics how much memory is available on my servers? how much has memory usage grown over four weeks?
- 54. Metrics number of open database connections number of redis commands number of 500 errors rate of HTTP requests number of HTTP connections
- 55. Metrics median response time number of failed resque jobs number of twitter followers 99th percentile github api response time 95th percentile mysql query time
- 56.
- 57.
- 58.
- 59. Metrics as aservice
- 60.
- 61. Logstash log inputs process outputs
- 62.
- 63.
- 64. Summary own your monitoring own your metrics own your logging none of them is optional