Whether you’re ironing out kinks in disk provisioning at scale or implementing service mesh for microservices. Let’s talk about the problems we’re currently tackling.
(Without violating NDA’s of course)
I’ll go first - I’m working on the reliability of some migration patterns between a couple managed cloud implementations. A bring-your-own-account model underpinned the legacy setup, while the newer cloud offering allows us to retain it all in our accounts.
This is on top of generally sussing out the reliability of the newer product with some chaos testing.
The unfortunate bit is that my OPS workload is so high that I struggle to get much traction on the above. Not to mention that this new product moves so fast that it’s hard to get any sort of week-to-week consistency. Often requiring environment re-provisioning. Not exactly stuff that the community can really help with, but hey, that’s what’s on my plate.
Ugh, my biggest problem is fighting through my executive dysfunction to get started on documentation updates. >_<
This week (likely most of the month) I am rebuilding a backup process which appears to currently rely on Syncthing and hasn’t been tested in years. Everybody got to put in their opinions, so I need to design something which has a single source of truth, also has 3-2-1 replica counts, takes snapshots of the production DBs without degrading them, and burns a monthly DVD on a workstation in the office. Once I’m done with that, I get to look at the office VPN’s performance problems.
