Azure Cloud Deployment Specifications

On This Page


This document lists the hardware specifications for deployment of version 3.5.5 of the MLOps Platform ("the platform") on the Microsoft Azure cloud; for details, refer to the Azure documentation.

Docker Registries
The platform is deployed with a default, on-cluster docker registry. This registry can only be used for playground environments, as it is volatile and images are lost when it is restarted. Operational clusters must be connected to an external Docker registry. Create the registry in your cluster, then configure it post-installation through the platform dashboard.
All capacity calculations in the hardware specifications are performed using the base-10 (decimal) number system. For example, 1 TB = 1,000,000,000,000 bytes.
  • Provisioning of the servers is handled automatically by the platform installer (Provazio).
    Don't attempt to provision the servers manually prior to the deployment.

  • The data-node instances include Non-Volatile Memory Express (NVMe) SSD-based instance storage, which is optimized for low latency, very high random I/O performance, and high sequential read throughput. The data doesn't persist on the NVMe if the instance is stopped.
    Don't attempt to shut down any of the data nodes, as it will erase the data.

Hardware Configurations

Iguazio Playground

A single data-node and single application-node cluster implementation. This configuration is designed mainly for evaluation trials and doesn't include high availability (HA) or performance testing.

You can deploy a Proof of Concept (POC) in the Iguazio playground configuration. Be aware that the POC cannot be used as development environment or for a production environment.
AWS Production Cluster
When deploying with public IPs, the use of static public IP addresses is required. For more information, see the Azure documentation.

Azure Data-Node Specifications

Data nodes in platform Azure cloud deployments must fulfill the following hardware specification requirements:

Component Specification
Instance type Standard_L16s_v2
vCPUs 16
Memory 128 GB
Data disks (local storage) 2 x 1.9 TB NVMe SSD
OS boot disk (Azure managed disk) Premium SSD; 400 GB (minimum)
Usable storage capacity 1 node (Playground) — 2.5 TB;
3 nodes (Operational Cluster) — 4 TB

Azure Application-Node Specifications

Application nodes in platform Azure cloud deployments are supported on Azure Kubernetes Service (AKS) and must use one of the following instance types. Choose the type that best fits your requirements. For specification details for each type, refer to the Azure documentation.

All of the supported application-node configurations also require a 250 GB (minimum) premium-SSD OS boot disk (Azure managed disk).
  • Standard_D16s_v3 (default configuration)
  • Standard_D32s_v3
  • Standard_D48s_v3
  • Standard_D64s_v3
  • NCv3-series (GPU optimized)

Backing up the Platform

To ensure safety of your MLOps Platform data, you must periodically back up your data and configuration.

Allocate one fileshare in your AKS for backing up your platform. See full details in Backing Up the Platform.

See Also