Carry DevOps to the masses
“We need to carry DevOps to the masses more actively,” we decided last year, conducted a large-scale rebranding of RootConf and launched DevOpsConf , as a place where engineers were able to discuss many pressing issues and see what is happening around them than they live in related areas, how come out of similar, but still great situations. We managed to put together a cool program and, more importantly, an audience of professionals who needed pain and their solutions and understood.
Well, we will not dwell on what has been achieved - we will continue to advance the approach of integrating development, testing and operation processes in May at RIT ++ .
Since DevOps, in our understanding, is about combining all development processes, the RIT ++ conference festival, in which both server and client developers, and managers of different levels, people who build business processes, and many other IT specialists participate, is the place to talk about DevOps.
To involve many in the process, we have shifted the conference vector compared to RootConf. We are interested in not only and not so much tools and technical hardcore, but also processes, management, team transformation, and everything related to software development in technology companies . The DevOpsConf program will be interesting not only to system administrators, but to everyone who wears a beard :) Although, practice shows that you can do without a beard. That is, there are topics for different developers, and for CTO.
Conceived, of course, cannot be realized without a fair share of community participation . In this role, we have a large Program Committee, which consists of first-class Ops and Dev specialists and is responsible for the DevOps part at many conferences, including HighLoad ++ (by the way, this year there will be three of them, and our section will be everywhere). We talked about their background and their views on the DevOps transformation here . We no longer take breaks in preparation between conferences, but are constantly studying the needs of the audience and searching for new viable ideas. Here is what we have identified for the near future:
Apply for a report if any of these items is part of your daily tasks. Or, if you are still in the process of solving a problem, but the stuffed cones are no longer haunted, and you want to talk about them. Moreover, if DevOps in your company is not yet a standard, but much has already changed in the processes on the way to it, we will be happy to consider such a report.
If in doubt, do not hesitate . The main thing is that the topic was personally very interesting to you personally, and the solution was one that you can’t read about on stackoverflow, but which can help someone save time and nerves. For the rest, we will help, ask the right questions, tell you where to develop the report, and even in preparation for the speech, we have a secret life hack (in fact, here it is).
Here are some suggestions from the Program Committee to help you decide.
Danila Shtan wants to hear more alternatives to "default" products like Kubernetes or Prometheus in practice.
Dmitry Malykhin would like to hear about the practices of GitOps and SRE.
In a word, do not drag out - send theses. For inspiration, you can use the playlist with videos of the best DevOpsConf Russia 2018 reports.
Write in the comments which topics we missed in vain, what hurts you in the context of DevOps. Advise whom we need to call, etc. Follow the example of the program committee.
Come to the chat conference with your requests. Other participants will be able to tell you whether it is worth talking about a topic, perhaps they will tell you how to supplement it - we are a community.
Meet offline at RIT ++ in May!
Well, we will not dwell on what has been achieved - we will continue to advance the approach of integrating development, testing and operation processes in May at RIT ++ .
Since DevOps, in our understanding, is about combining all development processes, the RIT ++ conference festival, in which both server and client developers, and managers of different levels, people who build business processes, and many other IT specialists participate, is the place to talk about DevOps.
To involve many in the process, we have shifted the conference vector compared to RootConf. We are interested in not only and not so much tools and technical hardcore, but also processes, management, team transformation, and everything related to software development in technology companies . The DevOpsConf program will be interesting not only to system administrators, but to everyone who wears a beard :) Although, practice shows that you can do without a beard. That is, there are topics for different developers, and for CTO.
Theme
Conceived, of course, cannot be realized without a fair share of community participation . In this role, we have a large Program Committee, which consists of first-class Ops and Dev specialists and is responsible for the DevOps part at many conferences, including HighLoad ++ (by the way, this year there will be three of them, and our section will be everywhere). We talked about their background and their views on the DevOps transformation here . We no longer take breaks in preparation between conferences, but are constantly studying the needs of the audience and searching for new viable ideas. Here is what we have identified for the near future:
- How to sell DevOps in case of outsourcers.
- Implementation of SRE approaches.
- Distributed tracing.
- How DevOps differs from well-organized operation.
- Differences between GitOps and Infrastructure as Code for Configuration Management.
- Successful Service mesh implementation cases.
- Design patterns of distributed systems.
- Alternatives to Docker - Podman?
- Legitimization of DevOps for auditors.
- ITIL v4 and DevOps.
- Separation of duties and the four-eye principle in DevOps.
- DevOps on the Internet of things.
- DevOps in Machine Learning.
- Cloud providers: AWS, Azure, GCP, etc.
Call for papers
Apply for a report if any of these items is part of your daily tasks. Or, if you are still in the process of solving a problem, but the stuffed cones are no longer haunted, and you want to talk about them. Moreover, if DevOps in your company is not yet a standard, but much has already changed in the processes on the way to it, we will be happy to consider such a report.
If in doubt, do not hesitate . The main thing is that the topic was personally very interesting to you personally, and the solution was one that you can’t read about on stackoverflow, but which can help someone save time and nerves. For the rest, we will help, ask the right questions, tell you where to develop the report, and even in preparation for the speech, we have a secret life hack (in fact, here it is).
Here are some suggestions from the Program Committee to help you decide.
Danila Shtan wants to hear more alternatives to "default" products like Kubernetes or Prometheus in practice.
Dmitry Zaitsev is waiting for reports about:Artyom Kalichkin is interested in cases of transition to DevOps rails in an ecosystem where not only microservices, but also any heavy legacy, ESB, RDBMS.
- Workable and proven experience in embedding security checks in delivery pipelines.
- Working and tested experience of analytics ops and automation in general in matters of packaging, delivery and further work with models.
- Managing complexity is not in words but in deeds.
Dmitry Malykhin would like to hear about the practices of GitOps and SRE.
Valeria Pilia hopes that someone will talk about:We accept applications for reports until March 27 . Yes, this is only two weeks, but do not postpone the submission for the last day. Firstly, we will begin to confirm the reports without waiting for the end, and the competition will increase. Secondly, you and we will have less time to refine and refine the topic, that is, now there is a chance to get into the program above. And just take pity on us - so as not to drown from the reports filed simultaneously.
- Real Continuous Delivery commit cases for complex applications, hung with security and regulations, and not just for lightweight fronts.
- The extinction of the Hadoop ecosystem and the pain of moving from it. Alternatives from an architectural point of view.
- The love of datasatanists, developers, testers and engineers in a single rush to create a product.
In a word, do not drag out - send theses. For inspiration, you can use the playlist with videos of the best DevOpsConf Russia 2018 reports.
We will form a program together
Write in the comments which topics we missed in vain, what hurts you in the context of DevOps. Advise whom we need to call, etc. Follow the example of the program committee.
Come to the chat conference with your requests. Other participants will be able to tell you whether it is worth talking about a topic, perhaps they will tell you how to supplement it - we are a community.
Meet offline at RIT ++ in May!