TL; DR
will be held in Moscow on January 30-February 1.
We will again analyze 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 Slurm SRE. 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 is needed by most of any large projects;
- DevOps is a culture, like any culture, it must come from within the company. You canβt hire a DevOps engineer and dream that he will devop processes.
- At the very end of the list of what is needed for DevOps transformation, there are technologies, that is, the very DevOps tools that we teach.
I realized that we were right not to include the DevOps philosophy and culture in the course, because this cannot be taught systematically. Who needs it, read it 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 guerrilla implementation of culture through tools. Something like the one described in the Phoenix Project. If we have teamwork with Git set up correctly, we can slowly supplement it with regulations, and then it will come to values.
And still, when we prepared the DevOps Slurm, where it was all about tools, I was afraid of the reaction of the participants: βYou said great things. Too bad I'll never be able to implement them." There was so much skepticism that we immediately put an end to the repetition of the program.
However, the majority of the participants answered in the survey that the acquired knowledge is applicable in practice, and that they will implement something in their country in the near future. At the same time, everything that we explained was included in the list of useful things: Git, Ansible, CI / CD, and SRE.
It would be worth remembering that at the beginning they also said about Kubernetes Slurm that it was impossible to explain k3s in 8 days.
With Ivan Kruglov, who led the SRE topic, we agreed on a separate program. We are discussing the details now, I will make an announcement soon.
What will happen at 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 flows in relation to teams
Topic #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 building a "general" 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 uses
- Gitlab CI, customization features, best practices
- Gitlab CI steps
- Gitlab CI Variables
- Build, test, deploy
- Execution control and restrictions: only, when
- Working with artifacts
- Templates inside .gitlab-ci.yml, reusing actions in different parts of the pipeline
- Include - sections
- Centralized management of gitlab-ci.yml (one file and automatic pushes to other repositories)
Topic #5: Infrastructure as Code
- IaC: approach infrastructure as code
- Cloud providers as infrastructure providers
- System initialization tools, image building (packer)
- IaC on the example of Terraform
- Configuration storage, collaboration, application automation
- The practice of creating Ansible playbooks
- Idempotency, declarative
- IaC on the example of Ansible
Topic #6: Infrastructure Testing
- Testing and continuous integration with Molecule and Gitlab CI
- Vagrant application
Topic #7: Infrastructure monitoring with Prometheus
- Why monitoring is needed
- Monitoring types
- Notifications in the monitoring system
- How to build a healthy monitoring system
- Human-readable notifications, for everyone
- Health Check: what to look out 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, conference hall of the Sevastopol hotel.
Dates: from January 30 to February 1, 3 days of hard work.
Source: habr.com