DevOps Fan Conference
This is, of course, about DevOpsConf . If you do not go into details, then on September 30 and October 1 we will hold a conference on combining the processes of development, testing and operation, and if you go in - I ask for cat.
In the framework of the DevOps approach, all parts of the technological development of the project are intertwined, occur in parallel and influence each other. Of particular importance here is the creation of automated development processes that can be changed, simulated and tested in real time. It helps to instantly respond to changes in the market.
At the conference, we want to show how this approach influences product development. How to ensure the reliability and adaptability of the system for the client. How DevOps changes the structure and approach of the company to the organization of the workflow.
')
It is important for us to know not only what different companies are doing within the DevOps approach, but also to understand why this is all. Therefore, we invited to the Program Committee not just experts, but specialists who see the DevOps discourse from different perspectives:
On the one hand, this creates difficulties and conflicts when discussing applications for reports. If the engineer is interested in analyzing a major accident, then the developer is more important to understand how to create software that works in the clouds and infrastructures. But by negotiating, we create a program that will be valuable and interesting to everyone: from engineers to CTO.
The task of our conference is not just to choose more interesting reports, but to present the big picture: how does the DevOps approach work in practice, what kind of rake can you run into when moving to new processes. At the same time, we build the content part, going down from a business task to specific technologies.
The conference sections will remain the same as last time .
We divided the potential audience of the conference into five groups: engineers, developers, security specialists, team leaders and CTOs. Each group has its own motivation to come to the conference. And, if you look at DevOps from this perspective, you can understand how to focus your topic and where to place accents.
For engineers who are engaged in the creation of an infrastructure platform, it is important to understand the existing trends, to understand which technologies are currently the most advanced. They will be interested to get acquainted with the real experience of using these technologies and exchange views. The engineer will be happy to hear the report with the analysis of some hardcore accident, we, in turn, will try to pick up such a report and polish it.
For developers, it is important to understand such a thing as a cloud native application . That is, how to develop software so that it works in the clouds and various infrastructures. The developer needs to constantly receive feedback from the software. Here we want to hear cases about how companies are building this process, how to monitor software performance and how the entire delivery process is organized.
It is important for cybersecurity professionals to understand how to customize the security process so that it does not stop the development and change processes within the company. Interesting will be the topic of the requirements that DevOps imposes on such specialists.
Timlides want to know how the process of delivery in other companies is organized. Which way did the company go to this, how did the development processes, quality assurance within DevOps lined up? Cloud native teamlords are also interesting. And yet - questions about the interaction within the team and between development teams and engineers.
For CTO, the most important thing is to figure out how to combine all these processes and adjust them for business needs. He makes sure that the application is reliable both for business and for the client. And here you need to understand what technologies will work for what business tasks, how to build the whole process, etc. CTO is also responsible for budgeting. For example, he must understand how much money he needs to spend on retraining specialists so that they can work in DevOps.
If you have something to say on these occasions, do not be silent, submit a report . The deadline for Call for Papers is August 20th. The earlier you declare, the more time will be spent on finalizing the report and preparing for the presentation. So do not over tighten.
Well, if you don’t have the need to speak in public, just buy a ticket and come to communicate with colleagues on September 30 and October 1. We promise, it will be interesting and inspiring.
To understand exactly what we are investing in the concept of DevOps, I recommend reading (or re-reading) my report “ What is DevOps ”. Walking through the waves of the market, I watched how the idea of ​​DevOps was transformed in companies of various sizes: from a small startup to transnational companies. The report is built on a series of questions, answering them, you can understand whether your company is moving towards DevOps or there are problems somewhere.
DevOps is a complex system, it should contain:
At the end of the report there is a scheme that gives an idea of ​​the DevOps system in the company. It will allow you to see which processes in your company have already been debugged and which ones just have to be built.
Video report can be viewed here .
And now there will be a bonus: several videos from RHS ++ 2019, which deal with the most common issues of the DevOps transformation.
Artyom Naumenko leads the DevOps team at Skyeng and takes care of the development of his company's infrastructure. He told how infrastructure influences business processes in SkyEng: how to calculate ROI for it, which metrics to choose for calculation and how to work on improving them.
Nixys company is engaged in support of loaded web-projects and distributed systems. Its technical director, Boris Ershov, told how to transfer software products to modern rails, the development of which began about 5 years ago (or even more).
As a rule, such projects are a special world, where there are such dark and ancient corners of the infrastructure that current engineers do not know about them. And once selected approaches to architecture and design are outdated and cannot provide businesses with the same pace of development and release of new versions. As a result, each release of the product turns into an incredible adventure, where something constantly falls off, and in the most unexpected place.
Managers of such projects inevitably face the need to transform all technological processes. In his report, Boris said:
Aleksandr Korotkov is the leading developer of the CI / CD system at CIAN. He spoke about automation tools that allowed improving the quality and reducing the time of delivery of the code in production by 5 times. But such results would have been impossible to achieve with only one automation, therefore Alexander drew attention to changes in the development processes.
Alexey Kirpichnikov has been implementing DevOps and infrastructure at SKB Kontur for 5 years. For three years in his company there were about 1,000 fakaps of varying degrees of epicity. Among them, for example, 36% were caused by rolling out a poor-quality release in production, and 14% were caused by maintenance work on iron in the data center.
Obtaining such accurate information about accidents allows the archive of reports (post mortems), which the company's engineers have been conducting for several years in a row. Postmortem writes the engineer on duty, who was the first to react to the alarm about the accident and began to repair everything. Why torture engineers who are fighting at night with packs, writing reports? This data allows you to see the whole picture and move the infrastructure development in the right direction.
In his speech, Alexey shared how to write a really useful post-mortem and how to implement the practice of such reports in a large company. If you love stories about how someone screwed up, watch the video of the speech.
We understand that your vision for DevOps may not coincide with our ideas. It will be interesting to know how you see the DevOps transformation. Share in the comments your experience and vision of this topic.
This week, the Program Committee adopted 4 reports: on security, infrastructure, and SRE practices.
Perhaps the most painful topic of DevOps transformation is how to make sure that the guys from the information security department do not ruin the already established links between development, operation and administration. Some companies do without the department of information security . How, then, to ensure information security? This will tell Mona Arkhipova from sudo.su. From her report, we learn:
The next report deals with the development of infrastructure as a code. Reduce the amount of manual routine and not turn the whole project into chaos, is it possible? Maxim Kostrikin from Ixtens will answer this question. His company uses Terraform to work with the AWS infrastructure. The tool is convenient, but the question is how to avoid using it a huge chunk of code. Serving such a heritage each year will cost more and more.
Maxim will show how code placement patterns work, aimed at simplifying automation and development.
We'll hear another infrastructure report from Vladimir Ryabov from Playkey . Here we will talk about the infrastructure platform, and we will learn:
The secret of this magic is in the ZFS technology for FreeBSD and its recent fork of ZFS on Linux . Vladimir will share cases from Playkey.
Matvey Kukui from Amixr.IO is ready to use examples from his life to tell you what SRE is and how it helps to build reliable systems. Amixr.IO skips client incidents through its backend, dozens of on-duty teams around the world have already resolved 150,000 cases. At the conference, Matvey will share the statistics and insights that his company has accumulated, solving customer problems and analyzing bundles.
In the framework of the DevOps approach, all parts of the technological development of the project are intertwined, occur in parallel and influence each other. Of particular importance here is the creation of automated development processes that can be changed, simulated and tested in real time. It helps to instantly respond to changes in the market.
At the conference, we want to show how this approach influences product development. How to ensure the reliability and adaptability of the system for the client. How DevOps changes the structure and approach of the company to the organization of the workflow.
')
Behind the scenes
It is important for us to know not only what different companies are doing within the DevOps approach, but also to understand why this is all. Therefore, we invited to the Program Committee not just experts, but specialists who see the DevOps discourse from different perspectives:
- senior engineers;
- developers;
- timlidov;
- CTO.
On the one hand, this creates difficulties and conflicts when discussing applications for reports. If the engineer is interested in analyzing a major accident, then the developer is more important to understand how to create software that works in the clouds and infrastructures. But by negotiating, we create a program that will be valuable and interesting to everyone: from engineers to CTO.
The task of our conference is not just to choose more interesting reports, but to present the big picture: how does the DevOps approach work in practice, what kind of rake can you run into when moving to new processes. At the same time, we build the content part, going down from a business task to specific technologies.
The conference sections will remain the same as last time .
- Infrastructure platform.
- Infrastructure as a code.
- Continuous delivery.
- Feedback.
- Architecture in DevOps, DevOps for CTO.
- SRE practices.
- Learning and knowledge management.
- Security, DevSecOps.
- DevOps Transformation.
Call for Papers: what reports are we looking for?
We divided the potential audience of the conference into five groups: engineers, developers, security specialists, team leaders and CTOs. Each group has its own motivation to come to the conference. And, if you look at DevOps from this perspective, you can understand how to focus your topic and where to place accents.
For engineers who are engaged in the creation of an infrastructure platform, it is important to understand the existing trends, to understand which technologies are currently the most advanced. They will be interested to get acquainted with the real experience of using these technologies and exchange views. The engineer will be happy to hear the report with the analysis of some hardcore accident, we, in turn, will try to pick up such a report and polish it.
For developers, it is important to understand such a thing as a cloud native application . That is, how to develop software so that it works in the clouds and various infrastructures. The developer needs to constantly receive feedback from the software. Here we want to hear cases about how companies are building this process, how to monitor software performance and how the entire delivery process is organized.
It is important for cybersecurity professionals to understand how to customize the security process so that it does not stop the development and change processes within the company. Interesting will be the topic of the requirements that DevOps imposes on such specialists.
Timlides want to know how the process of delivery in other companies is organized. Which way did the company go to this, how did the development processes, quality assurance within DevOps lined up? Cloud native teamlords are also interesting. And yet - questions about the interaction within the team and between development teams and engineers.
For CTO, the most important thing is to figure out how to combine all these processes and adjust them for business needs. He makes sure that the application is reliable both for business and for the client. And here you need to understand what technologies will work for what business tasks, how to build the whole process, etc. CTO is also responsible for budgeting. For example, he must understand how much money he needs to spend on retraining specialists so that they can work in DevOps.
If you have something to say on these occasions, do not be silent, submit a report . The deadline for Call for Papers is August 20th. The earlier you declare, the more time will be spent on finalizing the report and preparing for the presentation. So do not over tighten.
Well, if you don’t have the need to speak in public, just buy a ticket and come to communicate with colleagues on September 30 and October 1. We promise, it will be interesting and inspiring.
How do we see DevOps
To understand exactly what we are investing in the concept of DevOps, I recommend reading (or re-reading) my report “ What is DevOps ”. Walking through the waves of the market, I watched how the idea of ​​DevOps was transformed in companies of various sizes: from a small startup to transnational companies. The report is built on a series of questions, answering them, you can understand whether your company is moving towards DevOps or there are problems somewhere.
DevOps is a complex system, it should contain:
- Digital product.
- Business modules that develop this digital product.
- Food commands that write code.
- Practice Continuous Delivery.
- Platforms as a service.
- Infrastructure as a service.
- Infrastructure as a code.
- Selected practices for maintaining reliability, wired inside DevOps.
- Practice feedback that describes it all.
At the end of the report there is a scheme that gives an idea of ​​the DevOps system in the company. It will allow you to see which processes in your company have already been debugged and which ones just have to be built.
Video report can be viewed here .
And now there will be a bonus: several videos from RHS ++ 2019, which deal with the most common issues of the DevOps transformation.
Company infrastructure as a product
Artyom Naumenko leads the DevOps team at Skyeng and takes care of the development of his company's infrastructure. He told how infrastructure influences business processes in SkyEng: how to calculate ROI for it, which metrics to choose for calculation and how to work on improving them.
On the way to microservices
Nixys company is engaged in support of loaded web-projects and distributed systems. Its technical director, Boris Ershov, told how to transfer software products to modern rails, the development of which began about 5 years ago (or even more).
As a rule, such projects are a special world, where there are such dark and ancient corners of the infrastructure that current engineers do not know about them. And once selected approaches to architecture and design are outdated and cannot provide businesses with the same pace of development and release of new versions. As a result, each release of the product turns into an incredible adventure, where something constantly falls off, and in the most unexpected place.
Managers of such projects inevitably face the need to transform all technological processes. In his report, Boris said:
- how to choose the appropriate architecture for the project and put in order the infrastructure;
- what tools to use and what pitfalls are encountered on the way to transformation;
- what to do next.
Release automation or how to deliver quickly and without pain
Aleksandr Korotkov is the leading developer of the CI / CD system at CIAN. He spoke about automation tools that allowed improving the quality and reducing the time of delivery of the code in production by 5 times. But such results would have been impossible to achieve with only one automation, therefore Alexander drew attention to changes in the development processes.
How do accidents help learn?
Alexey Kirpichnikov has been implementing DevOps and infrastructure at SKB Kontur for 5 years. For three years in his company there were about 1,000 fakaps of varying degrees of epicity. Among them, for example, 36% were caused by rolling out a poor-quality release in production, and 14% were caused by maintenance work on iron in the data center.
Obtaining such accurate information about accidents allows the archive of reports (post mortems), which the company's engineers have been conducting for several years in a row. Postmortem writes the engineer on duty, who was the first to react to the alarm about the accident and began to repair everything. Why torture engineers who are fighting at night with packs, writing reports? This data allows you to see the whole picture and move the infrastructure development in the right direction.
In his speech, Alexey shared how to write a really useful post-mortem and how to implement the practice of such reports in a large company. If you love stories about how someone screwed up, watch the video of the speech.
We understand that your vision for DevOps may not coincide with our ideas. It will be interesting to know how you see the DevOps transformation. Share in the comments your experience and vision of this topic.
What reports have we already accepted into the program?
This week, the Program Committee adopted 4 reports: on security, infrastructure, and SRE practices.
Perhaps the most painful topic of DevOps transformation is how to make sure that the guys from the information security department do not ruin the already established links between development, operation and administration. Some companies do without the department of information security . How, then, to ensure information security? This will tell Mona Arkhipova from sudo.su. From her report, we learn:
- what and from whom it is necessary to protect;
- what are the routine safety processes;
- how IT and IS processes intersect;
- what is CIS CSC and how to implement it;
- how and by what indicators to conduct regular checks of information security.
The next report deals with the development of infrastructure as a code. Reduce the amount of manual routine and not turn the whole project into chaos, is it possible? Maxim Kostrikin from Ixtens will answer this question. His company uses Terraform to work with the AWS infrastructure. The tool is convenient, but the question is how to avoid using it a huge chunk of code. Serving such a heritage each year will cost more and more.
Maxim will show how code placement patterns work, aimed at simplifying automation and development.
We'll hear another infrastructure report from Vladimir Ryabov from Playkey . Here we will talk about the infrastructure platform, and we will learn:
- How to understand if storage capacity is used efficiently;
- how several hundred users can receive 10 TB content each, if only 20 TB storage is used;
- how to compress data 5 times and provide it to users in real-time;
- how on the fly synchronize data between several data centers;
- how to eliminate any user influence on each other when using one virtual machine sequentially.
The secret of this magic is in the ZFS technology for FreeBSD and its recent fork of ZFS on Linux . Vladimir will share cases from Playkey.
Matvey Kukui from Amixr.IO is ready to use examples from his life to tell you what SRE is and how it helps to build reliable systems. Amixr.IO skips client incidents through its backend, dozens of on-duty teams around the world have already resolved 150,000 cases. At the conference, Matvey will share the statistics and insights that his company has accumulated, solving customer problems and analyzing bundles.
Once again I urge you not to be greedy and share your experience with the DevOps Samurai. Apply for a report, and you and I will have 2.5 months to prepare an excellent presentation. If you want to be a listener, subscribe to the newsletter with the program updates and seriously think about booking tickets in advance, because they are more expensive to the dates of the conference.
Source: https://habr.com/ru/post/458920/
All Articles