Hacker News new | ask | show | jobs
by rhythmvertigo 2166 days ago
Yep, it will work with your GPUs! You just set up self-hosted runners as usual https://docs.gitlab.com/runner/

GitHub & GitLab have both made it quite easy to use your own resources as runners. I recently met someone who was doing Actions with a Jetson Nano on their dresser :)
1 comments
gravypod 2166 days ago
That's really cool. I might have to play around with this. Do you have any docs on what you do to deploy a model? Something I've been doing at work is dealing with the output of some ML code we have. We end up with ~150GB of data that needs to be synced to a file share in prod. I'm assuming DVC can be used for this.

After the run, output files, upload as a data set in DVC or something?

Documenting this full workflow would save a lot of confused devopsy people (like myself) survive in the world of ML. Thanks for this hard work you've all put into this!

link
calebkaiser 2166 days ago
Not to be too self-promotional here, but I'm a maintainer of Cortex, a model deployment platform that sounds like it might be useful: https://github.com/cortexlabs/cortex

With DVC/Cortex, you can set things up so that all you have to do is run `dvc push` to update your model and `cortex deploy` to deploy it.

link
dmpetrov 2166 days ago
150Gb ML model file? That's cool!

Yes, DVC can help with that. Where the data lives? S3/GCS or just a server with SSH?

Disclaimer: I'm a creator of DVC.

link
gravypod 2166 days ago
They live in an Azure Storage Account (Azure's not-S3). They're mounted as a network storage into pods in our kube cluster. All we need to do to deploy is copy the data into `/<thing>/<timestamp>` and the code finds the newest version and loads it up. So really I'm just looking for a way to abstract azure blob storage from my ML people and to allow them to do the equivalent of `docker tag...` to choose what we roll out.
link
ishcheklein 2166 days ago
I think DVC (+CML) is a good solution for this. It "wraps" artifacts that you store into Git. And Git repo abstracts access to the cloud. In your case of the mounted storage it will look like `git pull` + `dvc checkout` after model is "merged" in the production/master branch.

CML can automate and make the process of preparing the model to be merged into that branch reliable, visible, robust, etc.

I'm happy to help with this flow, ping me on Twitter - @shcheklein in DM or ivan on DVC Discord.

link