<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Virtualization on Cozystack</title><link>https://cozystack.ru/topics/virtualization/</link><description>Recent content in Virtualization on Cozystack</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 27 Apr 2026 22:15:09 +0500</lastBuildDate><atom:link href="https://cozystack.ru/topics/virtualization/index.xml" rel="self" type="application/rss+xml"/><item><title>Cozystack 1.3: Storage-Aware Scheduling, LINSTOR GUI, and VM Default Images</title><link>https://cozystack.ru/blog/2026/04/cozystack-1-3-storage-aware-scheduling-linstor-gui-and-vm-default-images/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://cozystack.ru/blog/2026/04/cozystack-1-3-storage-aware-scheduling-linstor-gui-and-vm-default-images/</guid><description>&lt;figure&gt;&lt;img src="https://cozystack.ru/blog/2026/04/cozystack-1-3-storage-aware-scheduling-linstor-gui-and-vm-default-images/cozystack-v1.3.0.png"
 alt="Cozystack v1.3.0" width="720"&gt;
&lt;/figure&gt;

&lt;h3 id="cozystack-13-storage-aware-scheduling-linstor-gui-and-vm-default-images"&gt;Cozystack 1.3: Storage-Aware Scheduling, LINSTOR GUI, and VM Default Images&lt;/h3&gt;
&lt;p&gt;
&lt;a href="https://github.com/cozystack/cozystack/releases/tag/v1.3.0" target="_blank"&gt;Cozystack v1.3.0&lt;/a&gt; is now available. The release also rolls up every fix shipped in the v1.2.1 → v1.2.4 patch line.&lt;/p&gt;
&lt;p&gt;This cycle pushes the platform forward in five clear directions: smarter storage placement, a managed UI for LINSTOR, a built-in catalog of VM base images, deeper application-level observability, and a complete cross-namespace VM backup-restore experience.&lt;/p&gt;
&lt;h3 id="main-highlights"&gt;Main highlights&lt;/h3&gt;
&lt;h4 id="storage-aware-scheduling-via-the-linstor-extender"&gt;Storage-aware scheduling via the LINSTOR extender&lt;/h4&gt;
&lt;p&gt;The &lt;code&gt;cozystack-scheduler&lt;/code&gt; now consults a &lt;strong&gt;LINSTOR scheduler extender&lt;/strong&gt; when placing pods that declare both a &lt;code&gt;SchedulingClass&lt;/code&gt; and LINSTOR-backed PVCs. Pods are preferentially scheduled to nodes where their volume replicas already live, cutting cross-node replication traffic and lowering I/O latency for storage-heavy workloads — databases, object stores, VMs.&lt;/p&gt;</description></item></channel></rss>