Recommended
Recommended
More Related Content
What's hot
What's hot (15)
Similar to DevOps Engineer Role
Similar to DevOps Engineer Role (20)
More from Rauno De Pasquale
More from Rauno De Pasquale (12)
Recently uploaded
Recently uploaded (20)
DevOps Engineer Role
- 1. DEVOPS ENGINEER ROLETorino DevOps Meetup
- 3. Is SRE an alternative to DevOps? Google creates and evolved the concept independently from DevOps movement. «If you think of DevOps like an interface in a programming language, class SRE implements DevOps. SRE includes additional practices and recommendations that are not necessarily part of the DevOps interface. DevOps and SRE are not two competing methods for software development and operations, but rather close friends designed to break down organizational barriers to deliver better software faster. DevOps emerged as a culture and a set of practices that aims to reduce the gaps between software development and software operation. The DevOps movement does not explicitly define how to succeed. SRE prescribes how to succeed in the various DevOps areas.” (Liz Fong-Jones, Seth Vargo) DEVOPS VS SRE (SITE RELIABILITY ENGINEERING)
- 4. DevOps movement in the community and SRE initiative in Google started from the same problem, the inefficiency of having Developers and Operators working on the different side of a wall, the first looking for feature and the second for stability. “One could view DevOps as a generalization of several core SRE principles to a wider range of organizations, management structures, and personnel. One could equivalently view SRE as a specific implementation of DevOps with some idiosyncratic extensions.“(Ben Traynor) A DevOps Engineer is someone who understands the full SDLC (Software Development Life Cycle) DevOps focuses more on the automation part SREs focus is more on the aspects like system availability, observability, and scale ”The basic tenet of SRE is that doing operations well is a software problem” SRE VS DEVOPS
- 5. IS DEVOPS ENGINEER A ROLE?
- 9. DEVOPS STATE OF THE NATION
- 10. DEVOPS STATE OF THE NATION Gene Kim: “back in 2013 DevOps was a domain of the tech giants (as Google, Microsoft, etc..) now in 2020 DevOps is being used by large corporate organisation cross every industry” Stephen Thair: “what changed from 2013 to now clouds were for early adopter while now it is mainstream, and along with cloud DevOps became mainstream because it was the opportunity to reset how to manage the solutions using the clouds” “DevOps transformation is not something you need your CTO or manager to drive you to, you can start working in your team, but if senior managers are not supporting these activities the DevOps adoption in the company will not work, it will remain inside individual teams” “Covid-19 has in some cases be a trigger for DevOps because it was clear that companies adopting this where able to react quicker” “Customers do not care that I can do RubyGems management in my laptop. Technology management has a value only if it provides value to the business” “Maturity of DevOps is visible when we talk about teams and about platforms and not about developers or infrastructure” “DevOps can be enabled by technology, using event sourcing or microservices move you to that way of working” “Leadership has to understand value of investing on developing productivity solutions as equal or higher value than developing customer features”
- 15. OUR SURVEY
- 16. SOURCES
- 17. SOURCES 26% SysAdmin 22% Other 24% Developer 36% Cloud Engineer 14% Release Manager 28% DevOps Engineer 22% SRE Others: Service Manager, Student, Team Leader, IT Advisor, QA
- 18. SYSADMIN ROLE
- 20. SRE ROLE
- 22. ROLES DEFINITION 36% answered “DevOps Engineer is not a role or a title” 56% answered “SRE is a new role” 56% answered “Cloud Engineer is a new role” 59% answered “Cloud Engineer is an evolution of SysAdmin” 30% answered “DevOps Engineer is an evolution of Developer” 19% answered “DevOps Engineer is an evolution of SysAdmin” 19% answered “DevOps Engineer is an evolution of Cloud Engineer” 26% answered “DevOps Engineer is a new role”
- 23. SKILL REQUIRED BY ROLE SysAdmin Developer
- 24. SKILL REQUIRED BY ROLE SRECloud Engineer
- 25. SKILL REQUIRED BY ROLE DevOps Engineer
- 26. SKILL REQUIRED BY ROLE DevOps Engineer SRE Cloud Engineer
- 27. PREDICTIONS In two years which role will no longer exist? DevOps EngineerSysAdmin Cloud Engineer SRE Italian: 75% English: 33% Italian: 22% English: 50% Italian: 47% English: 0% Italian: 19% English: 66%
- 32. THE END – Q&A ?
Editor's Notes
- During the two previous sessions we have been talking about the history of the DevOps movement and about the SRE role and duties and we also discussed about the relationship between DevOps and SRE. One of the key point was about the fact of SRE to be a specific role with prescriptive duties and practices, while DevOps is more a cultural movement, defining principles but not explicit roles and practices.
- We also found that even if the DevOps movement was not defining a role, there is a common usage of the term “DevOps Engineer” and so we were wondering if it was correct or not to use that term to identify a specific role. This is what we want to discuss in this third appointment.
- Looking at the job placements sites not only in Italy but worldwide we see that the terms “DevOps Engineer” is clearly used to identify a job position.
- Looking at the description of those job positions we found some very generic term, but we also see a recurrence of references to Ci\CD, Automation, support to software lifecycle management and definition. We see a prevalence of web based solution and architecture and related technologies and a clear indication of cloud based environments.
- One hour before our appointment, as part of the Microsoft Build online conference, Microsoft presented a very interesting session about ”DevOps State of the Nation”.
- One of the data presented by Microsoft is the result of a survey taken during the conference about DevOps Adoption. The “Starting to adopt” when looked into more details show very different responses, from pilot projects to cultural transformation exercise tot purely technological and practical bases exercises related to introduction of CI\CD platform without touching organisation or cultural aspects.
- Gene Kim and the others discussed about how DevOps perception and adoption changed in the last decade, highlighting how circumstances can be the driver of the change (from technology adoption that force to change the way of working to social distancing caused by Covid-19). A clear point had been remarked about the fact that the transformation can not work if not started from the technical people but at the same time can not move from single team transformation to company transformation without a clean buy-in by the leadership.
- On the 13 of May the “Osservatorio Cloud Transformation” of the Politecnico di Milano, organised a session about DevOps adoption in Italy,
- The result of the survey done by the Osservatorio had as target corporates and enterprises (big companies and not medium or small ones). Only 8% is currently using DevOps as a default, 28% is using it just in some project (new projects or specific teams).
- During the conference two working groups have been created involving the representative of many companies, from small to medium to big corporates, working on many different areas (with only a small part having information technology as the main business). Between the questions there were questions about what had been done in terms of organisation structure and way of working to try to adopt DevOps. The answers highlighted the usage of pilot projects and external consultant (with Agile or DevOps coaches). To break the silos and create multi-functional teams does not look to be so common in this phase, even if done by some company.
- One other question was about what was particularly difficult during the setup of the organisational changes. The conflict between Dev and Ops has been highlighted as the main difficulty. At the same time it has been reported as a clear issue the coordination of the different aspects in the context of having preserved the “silos” organisation, not really working well with the new methodologies.
- We also created our own survey, that was available both in Italian and in English, allowing us to discriminate the answers between Italian people and rest of the world. The results are not having a statistical meaning due to the low number of attendees (98 in total), but it can help to get some information. Looking at the numbers in the next slides please remember that many questions were not mandatory and that many questions also allowed multiple answers.
- On the left you find the Italian survey and on the right the English one. Obviously on the English one none of the people was part of the Meetup group.
- Multiple answers were possible for each response, this were the answer to the question about “which kind of role do you feel would be appropriate to describe your current work” so it was not about role officially assigned but role perceived by who was answering.
- We tried to compare the usage and the definition of various roles: SysAdmin, Cloud Engineer, SRE, DevOps Engineer ( and in some cases we included also Developer). Italian answers on the left, english answers on the right. From top to bottom: usage of the terms as role, how the company it is actually organised for people with that role, how you would like it to be organised if the role exist.
- Italian answers on the left, english answers on the right. From top to bottom: usage of the terms as role, how the company it is actually organised for people with that role, how you would like it to be organised if the role exist.
- Italian answers on the left, english answers on the right. From top to bottom: usage of the terms as role, how the company it is actually organised for people with that role, how you would like it to be organised if the role exist.
- Italian answers on the left, english answers on the right. From top to bottom: usage of the terms as role, how the company it is actually organised for people with that role, how you would like it to be organised if the role exist.
- We asked from a list of definitions which ones were considered valid. Definitions were mainly about a role as a synonymous of one other roles (for example “Cloud Engineer is a synonymous of SysAdmin”) or one role as evolution of one other role (for example “Cloud Engineer is an evolution of SysAdmin”) or a role as something completely new.
- We asked about which skills are more relevant for each role. You can see the different distribution between roles.
- We asked about which skills are more relevant for each role. You can see the different distribution between roles.
- We asked about which skills are more relevant for each role. You can see the different distribution between roles.
- We asked about which technologies are more relevant for each role. You can see the different distribution between roles. First and second lines are: management of OS; ability to write and execute scripting (bash or powershell or other).
- In this question about the prediction of which role will disappear in two years the answers were again very different between Italians and not Italians.
- We asked also some free comment on the evolution of the roles.
- We asked also some free comment on the evolution of the roles.
- We asked also some free comment on the evolution of the roles.
- We asked also some free comment on the evolution of the roles.
- Our own conclusions are: DevOps Engineer is a term used to define a role, especially in Italy, while much less abroad. The definition of a DevOps engineer is very similar to the one of an SRE but with some different focus (DevOps more Ci\CD and SRE more Observability) but it looks like the two terms could be merged in the future. DevOps Engineer is usually perceived as an evolution of the SysAdmin (Ops side so more than Dev) and the difficulties of a SysAdmin to become DevOps are always part of the conferences and discussions, but the survey is reporting a good percentage of DevOps Engineers with a developer background instead of an operation one, so maybe it is worth to concentrate also on the difficulties of Developers to become DevOps Engineers. Some comments also highlighted the threat that usage of Cloud Platform (more and more in PaaS and SaaS mode) is for existence of these roles out of the Cloud providers companies.