Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
1–10 of 68 posts
Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#2Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#3I'm not sure I understand your question fully? You write documentation, like you do anything. And configure everything with code, so you can go read it (Terraform, Chef/Puppet/Ansible, etc).
Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#4Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#5If you want something more clever; say keeping track of asset values etc, you'll want a CMDB. Google around and you should find something that fits your needs. We used SeviceNow in a previous life.
Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#6Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#7- configure everything as code (we use Ansible for the infrastructure up to OS level, Kubernetes w/ Helm for applications), have it read the values from the DCIM so that the DCIM remains the single source of truth (we need to still get better on this part....)
Links: https://github.com/digitalocean/netbox https://www.ansible.com https://www.kubernetes.io
That's at work. At home, I do much of the same, except that maintaining a DCIM is excessive for 2 VPS and a home network of 3 boxes.
Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#8(like, I don't want to have to configure 1000 moving parts)
typically this seems to fall into the 'roll your own' or 'giant lumbering enterprise behemoth' category that does 10 other things. I'm looking for the sweet spot.
Re: Ask HN: How do you document and keep tabs on your infrastructure as a sysadmin?
#9There are a couple of exceptions, but those are actively being brought under the above model (mostly because they are effectively invisible, and the existing documentation for them is... incomplete).
Any documentation outside of that is stale in a few hours, and obsolete in a week.