vCPU pinning is tedious... had Claude build a TUI for vCPU pinning + NUMA binding. Any suggestions?

A research associate has released pindergarten, an open-source terminal UI for vCPU pinning and NUMA binding on KVM hosts, built largely with code generated by Claude. The tool, available on GitHub under an MIT license, edits cputune and numatune XML and takes effect on the next VM boot without altering live scheduling. The developer is seeking feedback on whether the tool is worth polishing beyond its current 'works for me' state.

Hi all, I’m a research associate and got handed the job of managing our faculty’s shared experiment server a two-socket KVM host with a rotating set of GPU-passthrough VMs for whoever needs compute that day . VMs come and go, so I end up repinning constantly, and hand-editing <cputune / <numatune XML while trying to remember which threads are already taken got old fast. So I vibed a terminal UI for it xylophoneengine/pindergarten on github : What it does virDomainDefineXML – takes effect on next VM boot, never touches a running VM’s live scheduling Full disclosure: this is vibecoded The bulk of the code was written with Claude, because I need to focus on my actual job which isn’t IT administration, but somebody has to do it… . I steered, reviewed, and tested it on that server and on my private workstation the screenshot above . It works for me, but it has not been properly battle-tested beyond those two hosts. MIT licensed is this the proper one to choose? I was considering GPLv3 or something, but a friend told me MIT is good . Why I’m posting It’s a tool I needed, and maybe you need it too. So …if a battle-proven tool for this already exists, please point me at it I couldn’t really find one. Is anything obviously missing for your workflow? Not trying to sell anything, just want to know whether it’s worth polishing past “works for me.” Hope you’re all doing great, have a nice one