Welcome Padawan. How to start devops
DevOps boot storyboard:
At the Agile 2008 conference, Andrew Clay Shafer and Patrick Debois discussed « Agile Infrastructure », afterwards creating the Agile System Administrators Group on Google.The term « DevOps » was popularized through a series of « DevOps Days » starting in 2009 in Belgium. Since then, there have been DevOpsDays conferences held in many countries worldwide. We also talk about BizDevOps , Biz for Business.
Wikipédia says :
DevOps (a clipped compound of « development » and « operations ») is a software development method that stresses communication, collaboration, integration, automation, and measurement of cooperation between software developers and other information-technology (IT) professionals.
DevOps is a software development method that emphasizes communication, collaboration (information sharing and web service usage), integration, automation, and measurement of cooperation between software developers and other IT professionals.The method acknowledges the interdependence of software development, quality assurance (QA), and IT operations, and aims to help an organization rapidly produce software products and services and to improve operations performance
My opinion (based on my point of view and other feedbacks)
- DevOps doesn’t make specialists obsolete.
- Developers can learn systems and operations, but nothing beats experience.
- Operations people can learn development too, but again, nothing beats experience.
- Operations and development have historically be separated for a reason – there are compromises you must make if you integrate the two.
- Tools and automation are not enough.
- Developers have to want DevOps. Operations have to want DevOps. At the same time.
- Using “DevOps” to save money by reducing staff will blow up in your face.
- You can’t have DevOps and still have separate operations and development teams. Period.
if it ain’t broke, don’t fix it.
If you have a working organization that seems old fashioned, leave it alone. It’s possible to incorporate the tech, and even some of the cultural aspects of DevOps without radically changing how things work !!
You don’t need to call it “DevOps”. It’s just what you do as part of your job. Some days you’re writing code, other days you’re doing a deployment. Everyone shares responsibilities equally.
If we try to integrates Tools in theese