DevOps, configuration management. What is that?

Question

linux

Hello!
Please explain in a popular way what is meant by continuous integration, what is meant by DevOps in the CIS countries, should an admin-supporter in hosting consider this as a development vector, what is fraught with?

Answer 1

As a rule, DevOps is the admin who writes the code. That is, administration of a wide profile, plus writing your own products up to kernel modules. For example, Igor Sysoev, the author of nginx is quite a DevOps, who wrote a web server for his needs.
Configuration management is Chef, Puppet, Ansible - configuration automation. A centralized repository that allows you to describe in detail the entire economy - machine configurations, a set of applications, configs of the applications themselves, up to the fact that you launch the client and go to drink tea. After a while, you have a fully configured host, ready to go into production.
Continuous integration is a slightly different story. It implies a testing tool and code layout, a bug tracker, version control and automation of everything as a single process, these are all sorts of Jenkins, Teamcity, Hudson and so on.
And yes, the first two directions are very desirable. It's hard to imagine a serious project without a chef/puppet, one way or another it will be smeared with automation - small scripts and other knee-jerk crap. DevOps as an intermediate link between the coder and the admin is also a very serious thing. When the admin understands how the code works, sees how to apply this or that system call, what COW is and how the same ruby ​​crap in memory - this is a good admin.
In parallel with DevOps, there is such a thing as operation. These are more "normal" admins who don't write complex stuff, preferring python and bash with perl, solving low level automation tasks.
In general, of course, all this is wildly spread out and not very standardized in Russia.

Answer 2

should an admin-supporter in hosting consider this as a development vector

Well, it's like going from building shitty sites on wordpress to an established software development firm using best practices and tools.
If you are interested in growth, then definitely worth it.

Answer 3

devops is essentially a person who automates processes within the team, in fact, as the admin was and remained
for most of his life, I do this before it was just a Linux admin now it has become Linux devops,
before it was just people who opened new companies, and now they are startups.

Answer 4

In the CIS, DevOps means "well, you write code, but we don't have money for an admin, so you will also be an admin." There are exception companies (large ones or those working for the foreign market), but for the most part, this is exactly the case.
CI, to put it in words, and not a memorized marketing bullshit, is what allows the code to get into review immediately after a commit, after a review for testing, after testing by a button in production. There are still many intermediate stages, but the point is - commit, check, button - testing, button - production. Oh yes, the most important thing - without stopping the work of the service in production.
It is better for the support admin to look in the direction of SRE - this is more of an admin job.

Answer 5

Thanks for answers!