DevOps by REBRAIN
Открытые практикумы по DevOps, Linux, Golang, Networks, Security Мы на связи: info@rebrainme.com +7 (499) 116-34-68 https://rebrainme.com/ Зарегистрированы в РКН: https://knd.gov.ru/license?id=674db558d793bc0b0b8845ff®istryType=bloggersPermission
Show more📈 Analytical overview of Telegram channel DevOps by REBRAIN
Channel DevOps by REBRAIN (@rebrain_devops) in the Russian language segment is an active participant. Currently, the community unites 28 754 subscribers, ranking 4 619 in the Technologies & Applications category and 22 378 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 28 754 subscribers.
According to the latest data from 31 October, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -98 over the last 30 days and by 0 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 8.12%. Within the first 24 hours after publication, content typically collects 6.53% reactions from the total number of subscribers.
- Post reach: On average, each post receives 2 335 views. Within the first day, a publication typically gains 1 878 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 10.
- Thematic interests: Content is focused on key topics such as dovecot, linux, скрипт, postfix, yandex.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“Открытые практикумы по DevOps, Linux, Golang, Networks, Security
Мы на связи:
info@rebrainme.com
+7 (499) 116-34-68
https://rebrainme.com/
Зарегистрированы в РКН: https://knd.gov.ru/license?id=674db558d793bc0b0b8845ff®istryType=bloggersPermiss...”
Thanks to the high frequency of updates (latest data received on 01 November, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
# На отдельном стороннем сервере (не PVE)
apt update && apt install corosync-qnetd -y
# На любой из нод Proxmox
apt install corosync-qdevice -y
pvecm qdevice add 10.10.10.100 # IP-адрес стороннего сервера
2️⃣ Настройка IPMI (аппаратного fencing) в /etc/pve/ha/fence.cfg
По умолчанию Proxmox использует встроенный программный Watchdog для самоизоляции нод. Но для надежности лучше настроить аппаратный IPMI:
# Создаем устройства IPMI для каждой ноды
device: pve-node1-ipmi
agent: fence_ipmilan
ipaddr: 10.10.100.1
login: admin
passwd: your_password
device: pve-node2-ipmi
agent: fence_ipmilan
ipaddr: 10.10.100.2
login: admin
passwd: your_password
# Привязываем устройства к нодам
node: pve-node1
device: pve-node1-ipmi
node: pve-node2
device: pve-node2-ipmi
3️⃣ HA-группы с жесткими ограничениями
# Создаем группу с приоритетом без автовозврата
ha-manager add group production \
--nodes "pve-node1,pve-node2,pve-node3" \
--restricted 1 \
--nofailback 1
# Добавляем VM в HA-группу
ha-manager add vm:100 --group production
4️⃣ Проверка и тесты
# Статус кворума — должен быть YES
pvecm status
# Имитируем падение сети на одной из нод
iptables -A INPUT -s 10.10.10.0/24 -j DROP
# Мониторим статус миграции
ha-manager status
# Лог успешного срабатывания fencing
journalctl -u pve-ha-crm | grep -i "fence"
↘️ Если тема интересна - ждем на практикуме Proxmox
Разбираем кворум, Ceph, Terraform, реальные аварии.
До 22 июня скидка 5000₽