Self-hosted Github Actions GPU runners

[volcacius]

Currently we are not running CI in a GPU enviroment. Best way to do might be through a self hosted runner on our own servers.
For security reasons, running code from pull request coming from forks should be disabled. To do so: https://github.community/t5/GitHub-Actions/don-t-run-actions-on-pull-request-from-fork/td-p/45499

[volcacius]

Relevant read: https://dev.to/wayofthepie/ephemeral-self-hosted-github-actions-runners-1h5m

[aktech]

Hi @volcacius I am the creator of Cirun.io, "Github Actions GPU runners" caught my eye.

FWIW I'll share my two cents. I created a service for problems like these, which is basically running custom machines (including GPUs) in GitHub Actions: https://cirun.io/

It is used in multiple open source projects needing GPU support like the following:

• https://github.com/pystatgen/sgkit/
• https://github.com/qutip/qutip-cupy

It is fairly simple to setup, all you need is a cloud account (AWS or GCP) and a simple yaml file describing what kind of machines you need and Cirun will spin up ephemeral machines on your cloud for GitHub Actions to run. It's native to GitHub ecosystem, which mean you can see logs/trigger in the Github's interface itself, just like any Github Action run.

Also, note that Cirun is free for Open source projects. (You only pay to your cloud provider for machine usage)

[volcacius]

Hi @aktech,

Thanks but that's not relevant to our use case. We have our own GPU servers, and it doesn't seem like cirun.io can handle on-premise deployments.

[aktech]

Hey @volcacius Cirun.io now does support on-prem deployments via OpenStack. I am happy to help to set it up if you'd like:
https://docs.cirun.io/cloud/auth.html#openstack