Valohai can be deployed in your environment, either in the cloud or on-premise. The platform can also be deployed in multi-cloud setups and in hybrid setups with both cloud and on-premise resources.
When using Valohai:
-
Your data stays in your environments (object storage, databases, and data warehouses).
-
The machine learning jobs are performed on your own virtual machines.
-
Models are deployed to your own object stores and registries.
Cloud |
Architecture |
Installation |
---|---|---|
AWS |
Architecture |
|
GCP |
Architecture |
|
Azure |
Architecture |
Valohai components
The Valohai application doesn’t directly access your workers but instead writes requests and updates to the job queue machine, from where your own workers find jobs that are scheduled for them.Valohai comprises of two layers, the Application Layer and the Compute & Data Layer.
Application layer |
Compute & Data Layer |
---|---|
Hosted by Valohai |
Hosted in your cloud/on-premises |
|
|
See also
Need to run Valohai completely inside your own network? See the guide Deploy a self-hosted Valohai
Permissions and access
Valohai will need a set of permissions in your cloud environment to autoscale your virtual machines and store logs, snapshots, and generated files in object storage.
First, you provision the core Valohai services in your cloud and register your organization in Valohai. Then you can set up your projects and connect them with your Git repositories, object storage, and private Docker registries.
See also
See the installation pages for AWS, GCP, and Azure for detailed guides and installation templates.
Service |
Access |
Configuration |
---|---|---|
Core Services |
Access to manage virtual machines and read/write to one object storage. |
|
Object Storage |
Read or Read/Write access to existing object storage (AWS S3, GCP Cloud Storage, Azure Blob Storage). |
Configured in-app: Add a cloud data store |
Git repository |
SSH or Deploy key with read-only access to select repositories. |
Configured in-app: Connect to a Git repository |
Docker Registry |
Permissions to pull from your Docker repository. |
Configured in-app: Access a private Docker repository |
Kubernetes Cluster |
A Kubernetes service account that can manage pods and other resources in a defined namespace. Permissions to read/write to your private Docker registry. |
Comments
0 comments
Please sign in to leave a comment.