<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Capacity Planning on </title>
    <link>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/</link>
    <description>Recent content in Capacity Planning on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Overview</title>
      <link>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/overview/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/overview/</guid>
      <description>&lt;p&gt;&lt;a id=&#34;cappacity-overview&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;!--# Overview --&gt;&#xA;&lt;h2 id=&#34;how-should-i-read-this-chapter&#34;&gt;&#xA;  How Should I Read This Chapter&#xA;  &lt;a class=&#34;anchor-link&#34; href=&#34;#how-should-i-read-this-chapter&#34; aria-label=&#34;Link to this section&#34;&gt;&#xA;    &lt;i class=&#34;fas fa-link fa-xs&#34;&gt;&lt;/i&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;This Chapter shows the different mechanisms available to administrators and users for controlling the capacity assigned to Virtual Machines:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;First, you can control the apparent capacity of Hosts by &lt;a href=&#34;http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/overcommitment/#overcommitment&#34;&gt;configuring host overcommitment&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Similarly, you can limit the resources that are made available to users, by using the &lt;a href=&#34;http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/quotas/#quota-auth&#34;&gt;quota system&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Finally, some workloads may require that you co-allocate or coordinate the capacity assigned to a group of Virtual Machines. &lt;a href=&#34;http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/affinity/#vmgroups&#34;&gt;Affinity and placement rules can be set for VM groups&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Additionally, you can consult the &lt;a href=&#34;http://51.159.138.137:8082/devel/product/cloud_system_administration/scheduler/&#34;&gt;Scheduler&lt;/a&gt; section to fine-tune &lt;a href=&#34;http://51.159.138.137:8082/devel/product/cloud_system_administration/scheduler/overview/&#34;&gt;the scheduling policies&lt;/a&gt; that control how resources from Hosts, Datastores, and Virtual Networks are allocated to Virtual Machines.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Host Overcommitment</title>
      <link>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/overcommitment/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/overcommitment/</guid>
      <description>&lt;p&gt;&lt;a id=&#34;overcommitment&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;!--# Host Overcommitment --&gt;&#xA;&lt;p&gt;Before allocating a VM to a Host, the Scheduler checks that the capacity requested by the VM fits in the available capacity of the Host. The overall number of VMs assigned to a Host can be controlled by:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Adjusting the total capacity announced by each Host.&lt;/li&gt;&#xA;&lt;li&gt;Adjusting the capacity requested by the VM.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;h2 id=&#34;virtual-machine-capacity&#34;&gt;&#xA;  Virtual Machine Capacity&#xA;  &lt;a class=&#34;anchor-link&#34; href=&#34;#virtual-machine-capacity&#34; aria-label=&#34;Link to this section&#34;&gt;&#xA;    &lt;i class=&#34;fas fa-link fa-xs&#34;&gt;&lt;/i&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;The resource allocation of the VM is expressed with the following attributes:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Usage Quotas</title>
      <link>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/quotas/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/quotas/</guid>
      <description>&lt;p&gt;&lt;a id=&#34;quota-auth&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;!--# Usage Quotas --&gt;&#xA;&lt;p&gt;The quota system tracks user and group usage of system resources, and allows the system administrator to set limits on the usage of these resources. Quota limits can be set for:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;users&lt;/strong&gt;, to individually limit the usage by a given user.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;groups&lt;/strong&gt;, to limit the overall usage by all the users in a given group. This can be of special interest for the OpenNebula Zones and Virtual Data Center (VDC) components.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;resource-limits&#34;&gt;&#xA;  Resource Limits&#xA;  &lt;a class=&#34;anchor-link&#34; href=&#34;#resource-limits&#34; aria-label=&#34;Link to this section&#34;&gt;&#xA;    &lt;i class=&#34;fas fa-link fa-xs&#34;&gt;&lt;/i&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;The quota system allows you to track and limit usage on:&lt;/p&gt;</description>
    </item>
    <item>
      <title>VM Groups (Affinity)</title>
      <link>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/affinity/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>http://51.159.138.137:8082/devel/product/cloud_system_administration/capacity_planning/affinity/</guid>
      <description>&lt;p&gt;In enterprise-grade cloud environments, orchestrating the physical placement of virtualized workloads is paramount to achieving infrastructure resilience, performance optimization, and strict fault isolation. OpenNebula addresses these requirements through its &lt;strong&gt;VM Group&lt;/strong&gt; architectural subsystem (&lt;strong&gt;Affinity&lt;/strong&gt; and &lt;strong&gt;Anti-Affinity&lt;/strong&gt; Groups). This mechanism enables system administrators and cloud architects to define relationship policies among multi-VM application tiers. Operational realities such as urgent infrastructure maintenance, emergency capacity rebalancing, or live patching frequently demand that in certain cases these rules must be temporarily bypassed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
