Registration is open for Slerm DevOps in Moscow
TL; DR
Slurm DevOps will be held in Moscow on January 30 - February 1.
Again we will analyze the DevOps tools in practice.
Details and program under the cut.
SRE was removed from the program, because together with Ivan Kruglov, we are preparing a separate SREM SRE. The announcement will be later.
Thanks to Selectel, our sponsors from the first Slurm!
About philosophy, skepticism and unexpected success
I visited DevOpsConf in Moscow at the end of September.
Summary of what I heard:
- DevOps need most of any large projects;
- DevOps is a culture, like any culture, it must come from within the company. You can not hire a DevOps engineer and dream that he will offend processes.
- At the very end of the list of what is needed for the DevOps transformation, there are technologies, that is, the very DevOps tools that we train.
I realized that we didn’t correctly include the philosophy and culture of DevOps in the course, because this cannot be systematically taught. Whoever needs to read in books. Or he will find a super-cool coach who will convince everyone with his charisma and authority.
Personally, I have always been a supporter of the “movement from below”, the partisan introduction of culture through tools. Something like that described in the Phoenix Project. If we have correctly configured teamwork with Git, you can slowly supplement it with regulations, and there it comes to values.
And all the same, when we were preparing the DevOps Slurm, where it was exclusively about tools, I was afraid of the participants' reaction: “You told wonderful things. Sorry, I can never implement them. " There was so much skepticism that we immediately put an end to the repetition of the program.
However, the majority of participants responded in a survey that the knowledge gained is applicable in practice, and that they will implement something in their own near future. At the same time, everything that we explained was in the list of useful: Git, and Ansible, and CI / CD, and SRE.
It would be worth remembering that they also said about Slurm Kubernetes that it was impossible to explain k8s in 3 days.
With Ivan Kruglov, who led the topic of SRE, we agreed on a separate program. Now we are discussing the details, I will soon make an announcement.
What will happen on Slurm DevOps?
Program
Topic # 1: Teamwork with Git
- Basic commands git init, commit, add, diff, log, status, pull, push
- Git flow, branches and tags, merge strategies
- Working with multiple remote reps
- Github flow
- Fork, remote, pull request
- Conflicts, releases, once again about Gitflow and other flow in relation to teams
Theme №2: Working with the application from a development point of view
- Writing a Microservice in Python
- Environment variables
- Integration and Unit Tests
- Using docker-compose in development
Topic 3: CI / CD: Introduction to Automation
- Introduction to Automation
- Tools (bash, make, gradle)
- Using git-hooks to automate processes
- Factory conveyor assembly lines and their application in IT
- An example of constructing a “common” pipeline
- Modern CI / CD software: Drone CI, BitBucket Pipelines, Travis, etc.
Topic # 4: CI / CD: Working with Gitlab
- Gitlab ci
- Gitlab Runner, their types and application
- Gitlab CI, customization features, best practices
- Gitlab CI Stages
- Gitlab CI Variables
- Assembly, testing, deployment
- Control and execution restrictions: only, when
- Work with artifacts
- Templates inside .gitlab-ci.yml, reusing actions on different parts of the pipeline
- Include - sections
- Centralized management of gitlab-ci.yml (one file and automatic push to other repositories)
Topic # 5: Infrastructure as Code
- IaC: an approach to infrastructure as a code
- Cloud providers as infrastructure providers
- System initialization tools, image assembly (packer)
- IaC on the example of Terraform
- Configuration storage, collaboration, application automation
- Practice creating ansible playbooks
- Idempotency, declarativeness
- IaC as Ansible
Topic # 6: Testing Infrastructure
- Testing and continuous integration with Molecule and Gitlab CI
- Vagrant Application
Topic # 7: Monitoring Infrastructure with Prometheus
- Why monitoring is needed
- Types of monitoring
- Notifications in the monitoring system
- How to build a healthy monitoring system
- Human readable notifications, for everyone
- Health Check: what to look for
- Automation based on monitoring data
Topic # 8: Application Logging with ELK
- Best Logging Practices
- ELK stack
Topic # 9: Infrastructure Automation with ChatOps
- DevOps and ChatOps
- ChatOps: Strengths
- Slack and alternatives
- Bots for ChatOps
- Hubot and alternatives
- Security
- Best and worst practices
Location: Moscow, Sevastopol Hotel Conference Hall.
Dates: from January 30 to February 1, 3 days of hard work.
All Articles