Download to read offline
Uploaded byMarian Marinov
Managing sysadmins
Marian Marinov, an experienced system administrator and head of DevOps, discusses management methodologies relevant to sysadmin/DevOps teams, emphasizing the significance of infrastructure setup and maintenance. Key points include the necessity for monitoring, time management, documentation, and training to avoid knowledge silos among team members. Marinov also advises that flexibility in planning for disasters is crucial, often prioritizing immediate needs over long-term goals.
More Related Content
Managing sysadmins
- 1.
- 2.
- 3.
- 4.
- 5.
- 6. Management methodologies ➢ Agile ➢ Waterfall(Waterflaw) ➢ DevOps Mainly for developers
- 7. Dev projects ➢After delivery tocustomers, there is mainly maintenance. ➢ Maintenance depends on the quality of the product
- 8. Defining the work of sysadmin/devops project ➢ Needs tosetup the infrastructure ➢nice if: ➢ you have to setup just one DB ➢ spin up your AWS instance and sync the files ➢ very complicated if you have to setup ➢an HA environment ➢cluster
- 9. Defining the work of sysadmin/devops project ➢ Monitoring ➢ willthis be monitored ➢ how much overhead are we adding to the team ➢ new projects come in - they only add to the amount of current projects
- 10. Executing the work ➢ The differencewith Devs is that Sysadmins are always in maintenance mode ➢ security updates (Software, Firewall, IDS/IPS) ➢ feature updates ➢ client software updates ➢ authentication/authorization management ➢ configuration changes
- 11. Time management ➢ Most ofthe time you should plan to have available resource ➢ problems may happen every day ➢ IT work is offloaded to them, as they know how to do it ➢ like setup that printer ➢ fix the VPN for that employee
- 12. Documentation ➢ Skilled adminscan sometimes work without or with poor documentation ➢ Junior admins ALWAYS require GOOD and tested documentation ➢ Makeing sure your admin team keeps up with the documentation guarantees easier recovery or faster maintenance
- 13. Siloed people ➢In many companieswe have people that are the most knowledgeable or even the only person that can do specific tasks ➢ either document that ➢ or train more people to do it
- 14. Similarities with Devs ➢ You haveto know your infrastructure ➢ machines, software, network ➢ As the Devs know theirs ➢ framework, databases, worflow
- 15. Takeaways ➢ Separate thework week into a few categories ➢ Monitoring ➢ Maintenance ➢ New deployments or upgrades ➢ Long term goal
- 16. Takeaways ➢ It isnot mandatory you keep all of the hours the same each week ➢ It is not important that you have all of them every week ➢ Just try to accomodate everything wihin the week
- 17. Takeaways ➢ Always planwith 50% chance for disaster. So keep a second view of the backlog... as if there is a disaster. ➢ I personally always sacrifice the log term goal in case of emergencies ➢ In cases where the team is overwhelmed I also delay deployments and even some times remove peopel from monitoring.
- 18.
- 19.