3 ms·
Very interesting! So when a user trains a model you guys startup a docker container with everything in it. You guys bind the container's ports to the host and
by kamikazeturtles 5y ago
Very interesting!
So when a user trains a model you guys startup a docker container with everything in it. You guys bind the container's ports to the host and add it to some key value store that a reverse proxy references. Is that correct?
Sorry, I'm just really curious. It's a really interesting project. Do you guys have anything open source?
- llom2600 5y agoMuch of the complexity in the sandbox is in ensuring that the development environment behaves as it it would in production - but also that it loads as fast as possible. So we have to do a bit of stuff behind the scenes involving dynamically linking libraries, provisioning Kubernetes resources, etc. But generally that's about right. We've haven't open-sourced any of it yet, but there are definitely a few components of our system that we'll open source once we feel they're stable enough.
- kamikazeturtles 5y agoI'm sorry I don't have any experience with Kubernetes What benefit would Kubernetes bring to this architecture? You can create and destroy docker container using the api. What do you guys use Kubernetes for?
- llom2600 5y agoKubernetes gives you a ton of extra tools that allow us to manage the lifecycle of our sandboxes, deployed models, asynchronous training jobs, etc. Internally, each pod is just running a docker image. You could probably throw something together with docker/the docker API - but in our case we needed a bit more control.
- kamikazeturtles 5y agoHey Eli! Thanks for the helpful responses! I sent you an email regarding a possible internship opportunity. Are you guys open to interns?