10 main difficulties on the way to adaptation DevOps
According to the Quali survey, more than 2,000 directors from the IT industry *, DevOps' adaptation to improve its workflow and productivity is impeded by very different problems: from the inherited infrastructure to the personal preferences of specialists and the lack of the necessary culture.
The authors of the study note that more than half of the respondents (54%) admitted that there was no IaaS (that is, an infrastructure that is available to them as a service) and that they use tickets to manage the infrastructure. At the same time, only 23% of respondents could have infrastructure deployed within one day, for 33% of survey participants this process can take up to a month, and for 26% even more so.
“Today we see a great emphasis on speed, flexibility and the need to do everything quickly, and the clouds and the as-a-service approach [IaaS, PaaS, etc. - approx. trans.] contribute to this. In the survey results, we saw that the lack of access to infrastructure-as-a-service is a very narrow throat, ”the authors from Quali emphasized.
')
What does the whole list of main difficulties on the way to DevOps look like and what will help in solving them?
Companies need to focus on building a culture with interactions with common (shared by all participants) goals. It is also important to find employees who can lead DevOps activities within the organization.
Many companies discard testing automation by focusing on CI / CD processes. However, continuous testing is the key to success in DevOps. From the very beginning, safety issues must be taken into account.
Accounting for outdated infrastructure and applications should be an integral part of your DevOps implementation plans. Installing new equipment or software and their simultaneous coexistence with older systems is always difficult.
When changing the architecture of the application, lay the possibility of using SaaS, cloud infrastructure, containers.
Create a clear plan that includes milestones, responsible and concrete results.
Standardization and automation of working with complex environments for DevOps can be achieved using containers from cloud service providers and other off-the-shelf tools.
Teams need to train DevOps. The company should standardize processes and general operating procedures.
Remember that Open Source does not mean free of charge: you have to pay for the integration and complexity of operation.
Avoid the use of disparate utilities (loved by individual developers, and not well integrated with other infrastructure) - otherwise it will increase costs.
Tell your company executives about the benefits of DevOps in order to enlist their support in finance and resources.
It is significant that even the most important difficulties that took the first 3 places in this “rating” received a rather small percentage of the votes: for 14% the main barrier is culture, for 13% - test automation, for 12% - obsolete systems. The resulting variability suggests that the introduction of DevOps practices should take into account many disparate factors, which, like DevOps, are associated not only with technologies, but also with people, and with the processes themselves. Moreover, if many of them are common to all companies, then some may be specific.
PS For fans of statistics: Jenkins (21%), Docker (16%), Puppet (14%) and Chef (13%) are the most popular software tools used by respondents to organize DevOps.
* Quali is a company with Israeli origins and headquarters in the United States that specializes in cloud technologies, DevOps and BizOps. The survey was conducted among visitors to such major IT events last year as Cisco Live, VMWorld, Jenkins World, and others.
Some of the refinements to the survey were taken from the Madison Moore article in the SD Times .
The authors of the study note that more than half of the respondents (54%) admitted that there was no IaaS (that is, an infrastructure that is available to them as a service) and that they use tickets to manage the infrastructure. At the same time, only 23% of respondents could have infrastructure deployed within one day, for 33% of survey participants this process can take up to a month, and for 26% even more so.
“Today we see a great emphasis on speed, flexibility and the need to do everything quickly, and the clouds and the as-a-service approach [IaaS, PaaS, etc. - approx. trans.] contribute to this. In the survey results, we saw that the lack of access to infrastructure-as-a-service is a very narrow throat, ”the authors from Quali emphasized.
')
Challenges and Solutions
What does the whole list of main difficulties on the way to DevOps look like and what will help in solving them?
1. Lack of culture
Companies need to focus on building a culture with interactions with common (shared by all participants) goals. It is also important to find employees who can lead DevOps activities within the organization.
2. Test Automation
Many companies discard testing automation by focusing on CI / CD processes. However, continuous testing is the key to success in DevOps. From the very beginning, safety issues must be taken into account.
3. Legacy systems
Accounting for outdated infrastructure and applications should be an integral part of your DevOps implementation plans. Installing new equipment or software and their simultaneous coexistence with older systems is always difficult.
4. The complexity of the application
When changing the architecture of the application, lay the possibility of using SaaS, cloud infrastructure, containers.
5. No DevOps Plan
Create a clear plan that includes milestones, responsible and concrete results.
6. Environmental management
Standardization and automation of working with complex environments for DevOps can be achieved using containers from cloud service providers and other off-the-shelf tools.
7. Lack of skills
Teams need to train DevOps. The company should standardize processes and general operating procedures.
8. Budget
Remember that Open Source does not mean free of charge: you have to pay for the integration and complexity of operation.
9. Unsuitable tools
Avoid the use of disparate utilities (loved by individual developers, and not well integrated with other infrastructure) - otherwise it will increase costs.
10. Leadership support
Tell your company executives about the benefits of DevOps in order to enlist their support in finance and resources.
Summarizing
It is significant that even the most important difficulties that took the first 3 places in this “rating” received a rather small percentage of the votes: for 14% the main barrier is culture, for 13% - test automation, for 12% - obsolete systems. The resulting variability suggests that the introduction of DevOps practices should take into account many disparate factors, which, like DevOps, are associated not only with technologies, but also with people, and with the processes themselves. Moreover, if many of them are common to all companies, then some may be specific.
PS For fans of statistics: Jenkins (21%), Docker (16%), Puppet (14%) and Chef (13%) are the most popular software tools used by respondents to organize DevOps.
* Quali is a company with Israeli origins and headquarters in the United States that specializes in cloud technologies, DevOps and BizOps. The survey was conducted among visitors to such major IT events last year as Cisco Live, VMWorld, Jenkins World, and others.
Some of the refinements to the survey were taken from the Madison Moore article in the SD Times .
Source: https://habr.com/ru/post/324664/
All Articles