Translated with AI from the Russian original.

Volcano scheduler considers task priority, computing power, and video memory

Russian infrastructure software developer Orion soft has updated the Nova AI platform for developing and operating AI/ML services. The main change was an automated mechanism for distributing GPUs between different types of workloads.

The Volcano scheduler is responsible for managing computing resources. It forms a queue of AI/ML tasks, taking into account their priorities and available capacities. Thanks to this, productive services, model training, and experimental projects can run in a single cluster without constant manual GPU reallocation.

The distribution takes into account the computing power of video cards and the amount of their video memory. Free resources can be directed to development and testing, without reserving them exclusively for a possible increase in load on working services.

The new version also updates the KServe inference backend for TensorFlow, PyTorch, Triton, and vLLM. In addition, SGLang support has been added. The component update should simplify the preparation of models for industrial launch and reduce the amount of manual integration.

Nova AI is a Kubernetes platform for creating and operating AI/ML services on the customer's infrastructure. It combines GPUs into a cluster, distributes computing resources among projects, and provides working environments for ML engineers.

Now on the front page

Articles

Why even a PC case should be branded

In Russian conditions, the popularity of PCs assembled by small local companies or in-house corporate IT departments continues to grow rapidly. Such solutions have historically been more popular in Russia than in other developed markets, but today new nuances have emerged in the segment's evolution, which we discussed with Karim LASKRI, Business Director of FSP Group in the CIS region.

News

Storage you can trust in the background: Basis SDS 2.3 released with scheduled diagnostics and an observer role

A storage system is the only infrastructure layer where an error cannot be “rolled back”: neither a reboot nor a configuration rollback will restore lost data. That is why users expect predictability from software-defined storage rather than just new features—ensuring background processes finish what they started, and administrators can see the cluster status not only “right now,” but also over time.