" "

Create Public &
Private GPU Clouds

Coming SoonWatch Demo

aarna.ml GPU Cloud Management Software

The above diagram shows the architecture of the aarna.ml GPU Cloud Management Software (CMS)

aarna.ml AI/ML Workload Intent

Users can order GPU resources using a variety of means: model serving, job scheduling, GPU instances

Automated Scaling

The infrastructure can scale-in or scale-out depending on the workload requirement

Recovery

Workloads can be deployed across clouds and can auto-recover upon cloud region failures

Auto-Stop

Automatic clean-up of resources upon workload completion to free up precious resources

aarna.ml Cloud Brokering

GPUaaS providers and enterprises can acquire excess capacity when needed. GPUaaS providers can sell underutilized capacity. The arna.ml GPU Marketplace is a SaaS implementation of the Cloud Brokering functionality.

aarna.ml On-Demand GPU Instance Management

Users can create, observe, manage, and terminate bare metal, virtual machine, and container instances on-demand along with storage options; fully isolated across CPU, GPU, storage, networking, and Infiniband.

cloud brokering functionality

aarna.ml Admin Console

Comprehensive functionality such as hardware discovery and inventory, observability, tenant management, software image catalog, fault management and correlation, NVAIE integration.

aarna.ml GPU Cloud Management Software

NVIDIA Reference Architecture Integrations

aarna.ml GPU Cloud Management System is compliant to the NVIDIA NCP and storage reference architectures along with scale testing. We integrate with NVIDIA HGX, MGX, Base Command Manager, NVAIE, SpectrumX, Quantum-2, VAST, WEKA, DDN and popular Kubernetes distributions, switch, and WAN gateways.

Service Provider Grade Admin Functionality

aarna.ml Support SLAs

We offer Premium or Basic Support depending on your particular needs or requirements

Contact Us

Support Included

Support hours 24 hours x 7 days OR 8 hours x 5 days

Committed Service Level Agreement (SLA) — see below

Number of operational support incidents — see below

Maintenance support included (access to new versions of software)

Designated support engineer

Community advocacy

Knowledge base

Technical bulletins

Premium Support (24x7)

Severity Level
Initial Response
Ongoing Updates
Severity 1
1 hour
Every 4 hours
Severity 2
2 hour
Every business day
Severity 3
Every business day
Every 3 business days
Severity 4
24  hours
None

Basic Support (8x5)

Severity Level
Initial Response
Ongoing Updates
Severity 1
4 business hours
Every 8 business hours
Severity 2
8 business hours
Every business day
Severity 3
2 business days
Every 3 business days
Severity 4
24  hours
None

Severity Definitions

Severity 1 – Critical Impact
Underlying open source project(s) is down and non- functional or there is a critical impact to End-User’s business operations due to the problem and no procedural workaround exists.
Severity 2 – High Impact
A Severity 2 Issue occurs when there is a sporadic underlying open source project(s) outage or a problem that is consistently encountered with significant impact to functionality.
Severity 3 – Medium Impact
A Severity 3 Issue occurs when there is a problem that affects the functionality or features of the underlying open source project(s) environment but there is no impact to critical functionality.
Severity 4 – Low Impact
A Severity 4 Issue occurs when there is a problem that leads to minor loss of functionality or where it affects the functionality of a particular feature of the underlying open source project(s). Severity 4 Issues may also include information requests, feature requests and cosmetic fixes.

There is no limit on the number of the tickets as long as the requests are reasonable.