DevOps

Разработка

Куратор секции: Дмитрий Катаев

Приглашаем обсудить DevOps - популярный, но непонятный многим феномен. Давайте вместе разберемся, можно ли установить настоящее взаимопонимание между ролями в проекте, создать единый цикл разработки, эксплуатации и деплоя программного обеспечения. Посмотрим, модное ли это слово, или серьёзное дело.

Мои контакты для любых вопросов:

E-mail: dmitry.kataew@gmail.com
Facebook: https://www.facebook.com/dmitry.kataev


Alexander Kirillov
Software engineer @ Evrone

Most web projects have long outgrown the level of monolithic applications and broke into the world of microservices. It's no secret that many developers choose containerization as one of the ways to deploy infrastructure. In my speech I will tell you why we chose Kubernetes, what difficulties we faced and wat solutions we found. Also, speaking in the context of Docker cluster I'll discuss the main points that web developers encounter, and will also address the issue of using the developer-environment based on Docker-containers.


Alexander Chistyakov
Principal Engineer @ Git in Sky
St. Petersburg

Practicing DevOps is not only necessary, but also boring, so I'll try to be a visionary, despite having Cassandra complex. Before my eyes, the world has changed several times, and each time not everyone got into the brave new world. Is DevOps engineer position safe enough to remain a well-paid specialist at the next change? How and where will the world change next time? Will the Docker survive, or the ‘blue whale’ on the logo will inevitably lead to a suicide? As always, a bit of shock content: why Jenkins is still in the trend, and why Java is not as bad as it's thought of.



Nikita Samokhvalov
Deputy CTO @ Notamedia
Moscow

При слове «госпроект» вы думаете об абсолютном водопаде, неисправимой бюрократии и неповоротливой эксплуатации? Всё гораздо хуже. Но мы их победили. Давайте разберёмся, как?

Я расскажу про опыт Notamedia и наших коллег по рынку:

— Что из себя представляет госпроект с точки зрения инженера.

— Как в таких проектах сочетаются Dev-ы и Ops-ы.

— Какие трудности возникают при внедрении новых фич и как с ними можно бороться.

— DevOps-практики в госсекторе.


Ilya Zhilenkov
@ Castle
Samara

The last couple of years the technology of containerization via Docker has gained incredible popularity. Many teams already successfully use infrastructure services, staging, testbed in containers, but many people are afraid of using containers to deploy applications in production. The community still lacks success-stories, especially for applications without microservice architecture. The huge number of approaches and recipes does not as well add confidence in what you are doing.

This report is about our fears, successes and solutions for the dockerization of the classical monolith in production..


Ivan Evtukhovich
CEO @ Express 42
Moscow

In our work as DevOps advisors, we often come across a customers question of what exactly DevOps consists of. The CAMS abbreviation is not good for selling, because no one will buy culture or Knowledge Sharing. We recommend our clients to implement the following practices: Infrastructure As a Code, Continuous Delivery, Continuous Monitoring, Automated Testing and Test Data Management. In the report, I will tell you what we mean by all this, and also about some cases from our work with large Russian companies.


1. Build a productive SSD shared storage for a cluster of more than 1000 machines. Comparative analysis with a cloud solution from Microsoft.

2. Work with real-time reconfiguration of the front-end server to build a cloud shared CaaS service. Comparison of Nginx, HAProxy, GoBetween.


Alexey Vakhov
CTO @ Uchi.ru
Moscow

When a company is growing by several times over the year in all parameters - traffic, servers, and employees - this is very difficult. Teams, processes and rules are being settled and at the same time they all need the help of an IT team. It's not even about traffic, which is growing, and not in databases, which are growing too, but about the constant colossal growth of the logical complexity of the system. My name is Alex and I work for this type of a company.

The technical department of Uchi.ru, which used to consist of a worker and the technical director in one person, for several years grew into a large, distributed team of 40 developers. More than a million schoolchildren from all over Russia are engaged in regular mathematics classes with us. In addition, we hold mass online Olympiads in different subjects. At the first Olympiad, the CEO gave me the phone which number was written on the home page and within an hour while the Olympiad was going on, I was talking with the teachers who took their pupils to the computer class where the Olympiad site would not start. It was emotionally difficult and since then my work is more than just a profession for me. I feel responsible to teachers and children when they are engaged in our product, to colleagues who conduct seminars or work for the support service.

I want to tell you how we were building and developing our stack, what mistakes we made, and what results we came to. This will be a story about iron servers and OpenStack, Ansible and Terraform, monitoring and backups, Docker and Docker again and how the system approach helps to cope with the ever increasing complexity.



В докладе я расскажу вам как: - Развернуть инфраструктуру для веб-разработки и поддержки клиентских сайтов? - Надежно работать с резервными копиями на паре-тройке выделенных серверов в разных ДЦ и хранить в системе контроля версий код который обычно не версионируют? - Дорабатывать и поддерживать кучу различных специфичных проектов включая устаревшие и экзотичные CMS?