Post B5e5VIllXii0givCL2 by lluad@mastodon.ie
(DIR) More posts by lluad@mastodon.ie
(DIR) Post #B5e3ViGIYwuZqLGsXQ by azonenberg@ioc.exchange
0 likes, 0 repeats
Set up a fourth CI builder instance running the freshly released Ubuntu Resolute / 26.04. I might eventually put a GPU on it, but for the moment it's using llvmpipe (I do want to run some tests without a GPU just to make sure that config works).Temps were acceptable, but on the warm side, maxing out just under 80C CPU temp. Interestingly the DIMMs and VRMs on one side are much hotter than the others. I need to go back and look at the motherboard diagram, perhaps I could do some 3D printing of air dams or something inside the case to make the CPU exhaust airflow go where I want it (out of the case) and not recirculating in the rather awfully laid out board/case's dead spots?As of now 3 of the 4 builders have a NVIDIA 1630 GPU, and all four have 8 vCPUs and 32GB of RAM.(By comparison, the standard GitHub Actions Ubuntu runners have 4 vCPUs, 16GB RAM, and no GPU so mine are significantly beefier, although I'm not sure how my Xeon 8362 compares core-for-core to whatever Azure is using today for these runners)
(DIR) Post #B5e4CpzPhuFWGJw9Sq by azonenberg@ioc.exchange
0 likes, 0 repeats
(thanks again to the various folks who have contributed time, ideas, and hardware to enable this... your hand-me-down server parts are a big improvement over what I had been using)Next on deck for the setup, in no particular order:* Finish building the Arch runner, I got interrupted a while back midway through provisioning the instance and I can't remember how much I got done. I've never used Arch btw, so there was quite the learning curve* Set up a Fedora runner. Straightforward, just haven't had the time yet* Set up a Windows runner. Slightly more annoying because windows, but should work well enough. I have an ISO and a license key from another VM I'm no longer using that should work. This is probably going to be my next task.* Set up a MacOS runner on the Mac Mini the ThunderScope team sent me. This will require some help from my Mac-using friends as I have no idea how to virtualize on MacOS. The hardware is here I just need to learn the software stack. * Figure out pushing of build artifacts somewhere, not just pass/fail state and test logs* GitHub integration so I can have pushes and maybe eventually approved pull requests run jobs on the platform, and report status back to GH. (We may eventually move the project off GH entirely, but the near term migration is just getting the CI off GH Actions)
(DIR) Post #B5e4nWeUZAHN0Ee4Ce by lluad@mastodon.ie
0 likes, 0 repeats
@azonenberg I found https://github.com/framna-dk/tartelet useful for setting up self-hosted ephemeral GitHub runners on macOS. It’s probably a decent place to start.
(DIR) Post #B5e4uiAS9NFwkE1NIm by azonenberg@ioc.exchange
0 likes, 0 repeats
@lluad I'm not using GitHub Actions. This is a completely independent CI infrastructure built around SLURM and xcp-ng.But I might refer to it around the mechanics of how to start, stop, wipe, etc. a VM on cue.
(DIR) Post #B5e5VIllXii0givCL2 by lluad@mastodon.ie
0 likes, 0 repeats
@azonenberg Yeah, it’s a VM runner that clones a template machine, then runs a script, then destroys the VM on exit. Nothing particularly GitHub-specific, as I recall.
(DIR) Post #B5e5hnrvk38CcGlZ2m by azonenberg@ioc.exchange
0 likes, 0 repeats
@lluad Yeah might be useful then.All of my non-MacOS runners are done via the XAPI interface to xcp-ng where I can issue an API key to my orchestrator VM that has the ability to start, stop, and revert-to-snapshot any VM that the "ci" user group has permissions on.So then I can have my SLURM scripts issue simple shell commands via xo-cli that do all of the VM scheduling. Hopefully there's something similar for Mac hiding in the guts of all that.I'm gonna wait until my mac-daily-driving catgirl friend from across town is free to come over and help me set it up though. I have lots of other things to keep me busy in the meantime.