search

vastness-io / project

Vastness-io project status
0 stars 0 forks source link

Centralize all GRPC services #1

Open jw-s opened 6 years ago

jw-s commented 6 years ago

Currently we have a separate service repository for each component

Does it make sense? Should we have them all in one repository?

PI-Victor commented 6 years ago

actually i kinda like the current approach. it's modern and does make sense. Some use cases might be hybrid deployments of the platform.

Tho, it depends on the intended arch, which i'm not familiar with. Is vastness gonna have a node agent? The agent that will build docker images/run builds? if that's the case, you could have the build agent run on KVM or AWS AMI machine (because higher load and accessibility to docker image builds) - Tho dockerfile builds inside of containers are now achievable, in kubernetes with kaniko.

And the rest of the components in a kubernetes cluster.

Again, this is based on the assumption that my current understanding of the project is correct :)

jw-s commented 6 years ago

@PI-Victor Vastness will have a worker model. Workers won't be limited to arch, they should be able to run anywhere and where it sees fit, utillise the underlying arch/platform such as workers running in k8s, aws, bare metal etc