raulcd commented on issue #814: URL: https://github.com/apache/arrow-nanoarrow/issues/814#issuecomment-3430788108
I've had a chat with @assignUser and INFRA about this. The next steps would be to create a JIRA ticket for INFRA to set this up and ask them to allow the app for `admin:write` and for us to configure and spin up the cloudformation stack from here: https://runs-on.com/guides/install/ My current concern is that as a first time user of runs-on for an open source project, the combination of the server side of runs-on being closed source, see the licensing, us having to ask for a non-profit (free) license and the App requiring `admin:write` aren't ideal. https://github.com/runs-on/runs-on?tab=readme-ov-file#license From my understanding @assignUser has had a chat with the author of runs-on and he would be willing to allow for an audit from ASF infra to validate the usage of the `admin:write` permissions. Once the App is installed and running on the infrastructure there's no auto-update so we would be sure the app won't be tampered. run-on is pretty nice as it would allow us to have bigger machines out of the box, which could help with issues with capacity we've had with some jobs (example linux packages having to free disk space) and cuda runners, see: https://runs-on.com/runners/gpu/ https://runs-on.com/runners/linux/ runs-on seems to be a pretty similar concept to what we did at: https://github.com/voltrondata-labs/gha-controller-infra and https://github.com/voltrondata-labs/cuda-action-runner-builder It basically gives you a cloudformation stack that sets up some infrastructure on AWS and creates a GitHub app that manages the self-hosted runners for you. The benefit of it versus our own setup is a lot less maintenance work, no-hassle updates to newer runners, otherwise we would have to maintain those repositories ourselves. Do we want to create a ticket for INFRA to start the conversation? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
