DevOops yesterday and today

    Today we’ll talk a little bit about the present, future and the DevOops 2019 conference program. DevOps changes every day. Do you remember the year 2004? We have a speaker who worked with clouds at a time when there was no such term. Amazon Web Services launched in 2006. Somewhere at the same time, the first references to DevOps began to appear. A whole life has passed since then.

    Recently they recalled “return my 2007” again. Imagine this world without the ubiquitous virtuals on Amazon, without GitHub (it appeared only in 2008), without cozy and safe dockers. Remember setting up iptables, GNU / Linux package managers, manually rebuilding kernel modules, sleepless nights. Still want to go there? That would be your 2019, if not for the hurricane progress of these years.

    Technology and companies have changed. Let me give you a couple of examples. For example, we all saw Microsoft's wonderful transformation - from Ballmer's “ Linux is Cancer ” in 2001 to the widespread transition to open source, the rescue of GitHub in 2018 and plans in the summer of 2019 to introduce the Linux kernel as part of the Windows delivery. Along with all this movement, the preferences of the engineers regarding the information received changed.

    In 2016, the Google book “ Site Reliability Engineering ” appeared. On the one hand, this book neither then nor now can be considered a guide for everyone and everyone - after all, “ you are not Google", You don’t have a Borg, and there may not be such tasks. In fact, initially being a product of clever Google PR, it did have an effect on a global scale. Few people have not read or heard of her. In August 2018, her Russian-language translation caught up with us, along with the continuation of the Site Reliability Workbook .

    Conferences are constantly changing along with the situation. Appearing in 2017, the DevOops conference in its program reflected the main issues that were at that moment occupied by specialists in DevOps solutions. The archive copy for 2017 will not let you lie: the first item was containers, orchestration and virtualization, including Docker and AWS. Docker, Docker, Docker everywhere. We broughtpeople who could talk about it endlessly, and the conference was opened by Corey Quinn, editor of Last Week in AWS .

    In 2018, it became clear that Docker was already fed up with everything. He became the standard, he began to look at us from everywhere. New posts in Last Week in AWS began to appear more often than 60 times a day. It no longer makes sense to build a conference around such obvious things. Keynote2018 was made by John Willis, a man famous not only as the director of ecosystem development at Docker, but also as one of the original fathers of DevOps, author of the DevOps Handbook and Beyond the Phoenix Project. It's nice that John began to talk not always about tuning, but about the implementation of DevOps as an organizational culture - a topic that is constantly forgotten, distracted by bright toys of new technologies.

    The second main theme of 2018 is Kubernetes. How to use it, how to implement it, is it worth doing at all. This topic ran the red line throughout the program, Kubernetes was, if not in the title, then no, no, and it appeared on the slides.

    Hi, 2019. Kubernetes, like Docker once, has become the standard. Hot wars died down, the victims of early introductions disappeared from the eyes, and only he remained on the battlefield. All new projects are done one way or another with an eye on the new king.

    And along with this, the question arises: what should the DevOops conference have to say this year? This is an open question that the program committee is currently working on.

    The conference program can be presented in two ways. Firstly, you can immediately present a ready-made grid of reports and say - look how cool it is. This produces a wow effect, leads to a quick purchase of tickets, but does not always fully respond to requests from visitors.

    For example, recently a friend wrote to me on VKontakte and asked me to tell what would be in the program. “But after the conference is still six months, why do you need this?” It turned out that in her company it was customary to write a poem for leadership on the topic “Why do I want to go to the conference” in advance. And since the company is large, everything is planned much in advance, then you need to write for six months. She absolutely does not fit the option of the form "the program will be a month before the start."

    This may seem like a special case, but from the many such special cases the overall picture is formed. There is another approach: instead of the final snapshot of the program, you can upload updates in small pieces. This is something agile and lean. If you remember, there is such a concept of value-stream mapping, and although it is not entirely applicable to the consumption of announcements of reports on Habré, there is something similar. For example, if we throw out too much text, you simply will not be able to have time to read it, and you will need to somehow remember what you read until the next time. The descriptions of the reports are adjusted and updated from time to time, the speakers change the names of topics as they work on the report, and this flow of information is not easy to understand, and even more so - to turn it into an understanding of “why do I need this conference.” In other words, publishing the program in pieces as it is filled is a blessing.

    Now we have posted on the sitesome of the first speakers who will definitely be at DevOops 2019. Reporting topics will be coming soon. In order not to miss anything, you can read our blog on Habré or subscribe to the mailing list (for this you need to go to the conference website and click the "subscribe" button there). If you suddenly want to make a report yourself, you still have the opportunity .

    And yet, what will the reports be about? See how the conference description has changed . Kubernetes is still in first place, but not as an independent discipline, but as part of the Cloud Native movement, next to Helm, Istio and service meshes. Note that in third place, the word Observability appeared explicitly (for example, in the book Practical MonitoringMike Julian, this word has not yet been used, a year has passed - and now). Reports will be approximately in this direction. Of course, old topics about Docker and Kubernetes will skip too, but at a higher level.

    I also have thoughts on this subject. For example, for me, DevOps has always been primarily a methodology and culture, and not a set of tuning. You roll out your enterprise Java web app on the customer’s servers, but it doesn’t roll out, something has broken, and you need to instantly orient yourself and fix everything. And it’s better to make rolling out to the prod not a nightmare. That's about this conference - how not to have nightmares with people and releases. What tools this will be done is the second question, we are cool and can handle any. I myself would like more reports on culture and ways of doing things - it’s good, even in the initial list of speakers there are such people (for example, Anton Weiss, Barukh Sadogursky, Roman Shaposhnik).

    In general, enough general words, let's get down to business! Here are our speakers:

    Anton Weiss- Co-owner of technology consulting Otomato Software, the owner of more than 15 years of experience in the field of high technology. He is an expert in technical teaching, the initiator and co-author of the first Israeli DevOps certification course. Anton participates in international conferences and is known as a cool speaker. At DevOops 2018, his report took first place!

    Eric Weld of HashiCorp has been in the cloud for more than 15 years. Prior to HashiCorp, he worked as a consultant at Xebia and became the founder of Instruqt, a platform for learning cloud tuning and other DevOps tools on a real infrastructure.

    Alex Thissenfrom Xpirit has been developing since the late 90s and managed to work as a leader and architect everywhere - from small startups to huge enterprise enterprises. In particular, he is engaged in training developers in Microsoft technologies, and architects in modern distributed cloud systems. Ten-time Microsoft Most Valuable Professional title in the Studio and Development Technologies category.

    Roman Shaposhnikfrom ZEDEDA - a renowned expert and consultant on open source and the transition to digital technologies in large companies. Previously, he played a major role in building open source collaboration within the Linux Foundation, and also held key positions at Pivotal, working primarily with big data and cloud-based application management platforms. His work at Pivotal led him to the intersection of container technology, virtualization, and unikernel architectures, which, in turn, spawned ZEDEDA's mission - to apply these technologies to developing edge computing. Roman is a member of the Apache Software Foundation and Linux Foundation Edge, as well as an active contributor to a number of open source projects.

    Victor Gamov- Developer Advocate at Confluent, a leading contributor to the Apache Kafka project. Helps architects and developers design and develop distributed streaming data processing systems. Co-author of the book "Enterprise Web Development" by O'Reilly. Co-founder and (in the past) leader of the debugging podcast “Flight Debugging”, beloved by many programmers .
    Anton Arkhipov - Developer Advocate at JetBrains, a resident of the Debriefing podcast . Professional interests are related to programming languages ​​and software development tools.

    Baruch Sadogursky(aka JBaruch) - Head of Developer Relations and Developer Advocate at JFrog. He likes to talk about technologies most of all - that is, he loves to chat, but a person who speaks about technologies has a smart look, and 18 years of experience in the field of high technologies have not gone away. When he does not speak (well, or does not fly to the place of the next speech), he studies technologies, people and how they work, or rather, do not work together. Baruch is a co-author of Liquid Software, a CNCF ambassador and a professional speaker on topics such as DevOps, DevSecOps, Go, Java, etc. He regularly speaks at such renowned conferences as Joker, JPoint, DevOops, Heisenbug, DockerCon, GopherCon, Devoxx, DevOps Days, OSCON, Qcon, JavaOne and others. Some of his reports can be viewed here .
    The DevOops 2019 conference will be held on October 29-30 in St. Petersburg.
    Come, it will be cool and useful!
    Early Bird tickets are available on the conference website .

    Also popular now: