<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resource Scheduler on</title><link>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/</link><description>Recent content in Resource Scheduler on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/overview/</guid><description>&lt;p&gt;&lt;a id="scheduler-overview"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Resource Scheduler Overview --&gt;
&lt;p&gt;The OpenNebula resource scheduler framework is a modular system that applies different scheduling algorithms to allocate three types of resources:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Hosts&lt;/strong&gt; – Determines the Hosts where VMs will run.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;System Datastores&lt;/strong&gt; – Selects the storage location for VM virtual disk images.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Virtual Networks&lt;/strong&gt; – Assigns Virtual Networks for VM interfaces when set to auto mode.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This scheduling mechanism is used for the following cloud operations:&lt;/p&gt;</description></item><item><title>Scheduler Configuration</title><link>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/configuration/</guid><description>&lt;p&gt;&lt;a id="scheduler-configuration"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Scheduler Configuration --&gt;
&lt;p&gt;The OpenNebula scheduler is a configurable component that determines how Virtual Machines (VMs) are allocated and migrated across the infrastructure. This section describes the relevant configuration parameters found in &lt;code&gt;oned.conf&lt;/code&gt; that control the scheduler’s behavior.&lt;/p&gt;
&lt;h2 id="scheduler-driver-configuration"&gt;Scheduler Driver Configuration&lt;/h2&gt;
&lt;p&gt;The &lt;code&gt;SCHED_MAD&lt;/code&gt; parameter specifies the scheduler driver responsible for managing scheduling operations. The configuration includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;EXECUTABLE&lt;/code&gt;: The path to the scheduler driver executable. This can be either an absolute path or a path relative to &lt;code&gt;/usr/lib/one/mads/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ARGUMENTS&lt;/code&gt;: A set of arguments passed to the scheduler driver:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;-t&lt;/code&gt;: Number of threads, i.e. the number of concurrent scheduling operations.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;-p&lt;/code&gt;: Scheduler used for initial VM placement:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;rank&lt;/code&gt;: The default OpenNebula matchmaking algorithm.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;one_drs&lt;/code&gt;: Optimizes VM placement and balances cluster load.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;code&gt;-o&lt;/code&gt;: Scheduler used for cluster-wide VM optimization:
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;one_drs&lt;/code&gt;: Optimizes VM placement and balances cluster load.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Example configuration:&lt;/p&gt;</description></item><item><title>Rank Scheduler</title><link>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/rank_scheduler/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/rank_scheduler/</guid><description>&lt;p&gt;&lt;a id="scheduler-rank"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Rank Scheduler --&gt;
&lt;p&gt;The OpenNebula Rank Scheduler is responsible for &lt;strong&gt;allocating pending Virtual Machines to available hypervisor nodes&lt;/strong&gt;. It’s a dedicated daemon installed alongside the OpenNebula Daemon (&lt;code&gt;oned&lt;/code&gt;), but can be deployed independently on a different machine. The Scheduler is distributed as part of the operating system package &lt;code&gt;opennebula&lt;/code&gt; with the system service &lt;code&gt;opennebula-scheduler&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a id="scheduler-rank-matchmaking"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;The Rank Scheduler implements a &lt;strong&gt;match-making&lt;/strong&gt; algorithm for VM allocation. The goal of this policy is to prioritize the resources that are more suitable for the VM.&lt;/p&gt;</description></item><item><title>Distributed Resource Scheduler</title><link>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/drs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/cloud_system_administration/scheduler/drs/</guid><description>&lt;p&gt;&lt;a id="scheduler-drs"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# OpenNebula Distributed Resource Scheduler (DRS) --&gt;
&lt;p&gt;The &lt;strong&gt;OpenNebula Distributed Resource Scheduler (DRS)&lt;/strong&gt; optimizes resource allocation and prevents resource contention within a single OpenNebula &lt;a href="https://docs.opennebula.io/7.2/product/cluster_configuration/hosts_and_clusters/cluster_guide/#cluster-guide"&gt;cluster&lt;/a&gt;. It integrates with OpenNebula’s built-in monitoring and forecasting systems, considering real-time Virtual Machine (VM) and Host usage metrics as well as predictions of future resource consumption.&lt;/p&gt;
&lt;p&gt;OpenNebula DRS offers flexible automation levels, allowing recommendations to be generated and applied either automatically or manually. Administrators can review and execute migration suggestions through the OpenNebula Sunstone GUI.&lt;/p&gt;</description></item></channel></rss>