On August 19-21, an online intensive will be held .
The main enemy that the DevOps course fights against: “Very interesting, it’s a pity that this cannot be implemented in our company.” We are looking for solutions that even an ordinary admin in a legacy project can implement.
The course is intended for:
- administrators who want to implement DevOps practices “from below”;
- companies and teams who want to take small and understandable steps towards DevOps culture;
- developers who want to deal with "administrative things" in order to independently solve minor admin tasks and slowly develop towards the team leader of a cross-functional team.
The course is useless for those who already know and use DevOps tools. You won't learn anything new.
Online intensive is a format of new realities, it provides almost the same immersion as offline intensives, only without a trip to Moscow (which is a plus for some and a minus for others).
We've done a DevOps course twice already and we've collected all the bumps we could.
The main cone is deceived expectations. Therefore, we will immediately tell you what will not be on the course.
There will be no best practices. There will be an analysis of one best practice. For example, a CI/CD topic that you can easily do a weekly intensive takes 4 hours. During this time, you can show the basics and build a simple pipeline, but you can’t sort out a pack of best practices for different cases.
There will also be no cases. Cases are the theme for the conference. There you can talk for an hour about one case from life. On Slurm, the lecturer can say that "this example is taken from my practice", no more.
There will be no individual analysis of practice. Practice is not mentoring, it is repetition after the lecturer. The purpose of the practice is to give the opportunity in their experiments to build on a known working option. After the intensive, you can review the recordings and repeat the practice yourself. This will give you maximum results.
There will be no Kubernetes - although this is a DevOps tool, we have it .
What will happen?
Will getting to know the tools from scratch and a complete set of solutions for building basic infrastructure.
There will be a story of practitioners about real application of tools and life tasks. This is the basis to which you can always add independent study of documentation and analysis of cases.
There will be daily answers on questions, where you can ask about your projects.
Will working with feedback: We ask for feedback daily. Write about everything that you do not like, we will correct it on the go.
And there will be a traditional opportunity take the money and leave if you don't like the course.
Intensive 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
The program is in progress and may change slightly.
Price: 30 000 ₽
Source: habr.com