Report from RedSlerma about monitoring (Monit, Zabbix)
3r350. 3r350. 3r350.
3r3338. The first day of RedSlerom passed, an intensive system administration.
At RedSlerm, Southbridge system administrators tell what they use and why. Special thanks to Selectel for resources for practice.
3r3338. 40 people gathered at RedSlerm (14 in the hall, 26 online). Considering that we will no longer repeat RedSlurm, it turned out to be a cute exclusive small party.
3r3338. Compared to r3r327. First Slurm
there is not enough summer, trash and the feeling of sweaty and bloody victory over circumstances. There we were gathering on the veranda in the evening, opening laptops and beer, and sitting until midnight. There was something in between a hackathon and a bard rally.
3r3338. Here we started on time and ended up ahead of time, because there was not a single delay for which we were laying a reserve. The bus flew from Moscow for 1:20 (and we laid 2 hours), the Internet did not fall, the sound did not disappear, the technical support unit immediately answered questions, in general, fans of the event action among the organizers already broke something to break, then heroically to fix. And before dinner, we went to the pool. That is, the orgs found an hour and a half to swim. That's what a good playground means.
3r3338. It's not too late to sign up for Slurm-2 (we start cluster Kubernetes, on October 25-27) and MegaSlerm (create a production-ready cluster Kubernetes, October 29-31).
It may be interesting