Home Conferences DevOps practices: from magic to tools. 11 speakers and one interview at DUMP conference

DevOps practices: from magic to tools. 11 speakers and one interview at DUMP conference

by admin

Over the years, DevOps has evolved from an exotic to a set of practices and technologies that help effectively solve application problems and bring tangible benefits to companies.

At this year’s conference we decided to focus on cases, which have been developing products and services with the help of DevOps for years. DUMP speakers are ready to share their examples, approaches and metrics. Let’s move from the magic, as DevOps seemed some time ago, to real tools. Speakers will help us with this :

Victor Yeremchenko (Miro). He will talk about Cloud native vs self-hosted solutions when scaling infrastructure. Which to choose? Miro’s experience

Alexander Tarasov (ANNA Money) and his report Not by Helm alone

Kirill Kazarin (DINS) with the theme 4 golden signals at the service of SRE engineer

Vitaly Khabarov (Express 42) is preparing a report How to measure DevOps?

Ruslan Tagirov, Nikita Chesnokov, Maxim Bendin (Rostelecom IT) and Rostelecom Digital Product Platform. How to develop DevOps-infrastructure in "maternity Enterprise"

  • Dmitry Sugrobov (Leroy Merlin ) will make a report Dev.+Ops or building the perfect delivery process

  • Artem Kartasov (Postgres.ai) and subject No rollback until dawn : automatic checking of PostgreSQL migrations in CI

  • Vladimir Lila (Contour) and his report Writing robust ansible roles. This report will be in the public domain – it is included in the free stream from the conference. How to listen to Vladimir and other speakers on May 14, told here.

  • By the way, at the last conference, Vladimir Lila and his report Petabyte-weight elastic generated a lot of interest and great feedback :

    • Another speaker of the DevOps section is Dmitry Kharlamov (Provectus) and his Long way from bash to gitops. We talked more about this. Here’s what Dmitry said about his projects and report :

    At Provectus we have a lot of different projects: from typical ones to very unusual ones. Often launching a project, much less a startup, without knowing the business or understanding the final infrastructure (and if the TOR is changed on the fly as well) is a pain. Pain for both Ops team and Dev. You need to react quickly to the situation, be able to expand/reduce/replace people on a project or the whole stack. But no matter what happens, you have to do it well and meet certain standards.

    Another important factor is to leave the knowledge behind after the project is launched, to pass on the artifacts so that the customer has the ability to maintain the infrastructure in-house. Or to be able to repeat the project with small changes, often within a tight timeframe.

    DevOps practices: from magic to tools. 11 speakers and one interview at DUMP conference

    Using the work of one of our DevOps engineers (that was Terraform, which was familiar to many), we created a tool that allowed us to deploy the underlying infrastructure in AWS with a focus on EKS, and importantly, remove everything we created without leaving anything behind. We decided to call the project Swiss-Army-Kube.

    Tell us more about what your talk will be about? Why did you choose this particular topic?

    I will talk about the journey we took to develop our tool. About what motivated and what hindered us in the process. This is a new experience for me to promote a project that doesn’t make money, but I hope it will be useful. I’ve been using tools that someone else has developed for a long time myself, and now it’s time to make up for the karma and move on. Perhaps someone will recognize themselves in this story and realize what they are missing. Spoiler : definitely not that! I think the report will be useful and some will not make our mistakes. A great reward for me will be if the participants remember something from my presentation.

    What prompted the creation of Swiss-Army-Kube and why did you decide to make the project open?

    The idea to create such a project has been in the company for a long time. We have a lot of experience and a lot of engineers (and this is the very base on which one wants to build such a tool). We made it open because it’s part of our marketing strategy. I’m close to the idea that knowledge needs to be shared, to improve our projects and help others. This is such AIT communism in all its glory.

    What does Provectus do? Tell us about your most unusual projects and your work at the company

    Our main focus is ML/AI consulting. We help launch startups and develop software for customers. It’s a wonderful world of machine learning. Before I met them, I had heard that there are mathematicians, they train models, guess at numbers…And anyway, I was right.

    How has the team’s work been affected by the pandemic?

    It’s all very individual here. Some started to work more remotely, some did not change their usual schedule. There were difficult moments when there was talk about taking time off at your own expense. But Provectus always openly declares that its most important asset is a team of professionals. So the company does everything possible to keep the team. That’s awesome!

    What trends in DevOps have emerged over the past year?

    Heard more often about ML, there is a general trend to move to service, to do as little low-level tasks as possible. That’s partly a good thing. You can concentrate on your tasks. But where do we then, 10 years from now, get people who know how it all works is a big question.

    What would you say to companies that don’t understand the need for DevOps practices?

    Are there more of these?:) The market dictates strict rules and DevOps practices focus on process continuity, guaranteeing code purity. Yes, it is not a silver bullet and often companies have to break established processes and get used to new ones – this can make the job harder. But it’s worth understanding that market giants Netflix, Amazon, and Google have been using these practices for a long time and are generally happy. For those who are not ready to take the transformation process into their own hands, I recommend turning to companies that specialize in this. As they say, you will never know unless you try.

    Working with business tasks teaches you how to react quickly to market changes, adjust to the customer, and build teamwork. What are the hard skills a DevOps engineer needs and what kind of soft skills do you acquire over time?

    It’s worth understanding the specifics of our market and the foreign market. We have no training base and no adequate understanding of what a DevOps-engineer should do. From the hard skills I can name the base of administration, knowledge of operating systems and scripts, the ability to read several popular languages, understanding of the principles of code building, how certificates work and the ability to highlight problems. And an important quality – to google, to find the necessary information for work.

    What skills have come with experience? For me, it’s the ability to find common ground with the team and adjust to a common rhythm. Over time, there was less fear and more responsibility. I’ve even been a team leader and here I realized that I shouldn’t criticize anyone, but it’s important to stand up for goals, talk one-on-one, and find motivation.

    How long does it take to build a team, where to start, and what mistakes are better to avoid?

    In any team, authority is crucial. If there is no conflict of interest, things line up pretty quickly. You have to trust the team and let everyone do their job. It’s important to build an open dialogue and find collaborative ways to solve a problem. Because both failure and success are the merit of the entire team. And there is no shame in asking for help.

    How did your career start?

    Started out as an electrician in a factory. Then I realized I didn’t want to work with my hands, I wanted to work with my head. I started as a DevOps in the ePayments project. I learned there very quickly after a long stagnation. I was given carte blanche there, and I turned around: I used practices from smart books, used automation, I managed to speed up the releases from three to four hours of manual work to 10 minutes after I pushed one button.

    What projects inspire you personally?

    Where there is no rigid framework, you can be imaginative or where there is a challenge. I’m interested when I have to do something complicated quickly and with high quality. I like projects where you can grow. And it’s also important that these companies really make a difference, help make life more comfortable.

    Imagine going back 10 years in time, what would you advise yourself to do?

    Learn that English already, you wuss!:)

    What do you see yourself as in another 10 years?

    That’s the most eerie question in all of the interviews. It’s hard to imagine. Probably still the same me, looking for answers, but more authoritative, with a burning eye and new ideas.

    You may also like