<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Placeholder VM for Resource Reservation in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Placeholder-VM-for-Resource-Reservation/m-p/1343471#M126108</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At my job, the way we generally operate is, if a project is initiated that has a requirement for virtual machines that use &lt;EM&gt;above&lt;/EM&gt; a certain threshold of compute and/or memory resources, they are required to fund the purchase of a new ESXi host so as to replenish the resources their project will be occupying in the resource pool.&amp;nbsp; Typically the host is provisioned and the VM's built soon after that, no problem.&amp;nbsp; However sometimes we have projects that buy a host but don't have a need for the VM's right away....sometimes not even until 6 months to a year after the hardware was purchased.&amp;nbsp; My question is, from a capacity planning perspective, how do you look at current and available usage of your compute/memory resources for your clusters and remember to take into account, oh yeah, the Accounting team is going to come asking for their two 4 vCPU x 32 GB vRAM virtual machines in a few months.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought about creating a dummy VM and figuring out a way to run a process that would sustain usage of a certain amount of compute and memory resources.&amp;nbsp; That way the VM would always appear to be using those resources and my view of available resources at any given time would not be misleading.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if any of you have run into a similar situation and what you've done to effectively manage it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;BD&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Dec 2013 19:34:36 GMT</pubDate>
    <dc:creator>bsd1977</dc:creator>
    <dc:date>2013-12-20T19:34:36Z</dc:date>
    <item>
      <title>Placeholder VM for Resource Reservation</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Placeholder-VM-for-Resource-Reservation/m-p/1343471#M126108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At my job, the way we generally operate is, if a project is initiated that has a requirement for virtual machines that use &lt;EM&gt;above&lt;/EM&gt; a certain threshold of compute and/or memory resources, they are required to fund the purchase of a new ESXi host so as to replenish the resources their project will be occupying in the resource pool.&amp;nbsp; Typically the host is provisioned and the VM's built soon after that, no problem.&amp;nbsp; However sometimes we have projects that buy a host but don't have a need for the VM's right away....sometimes not even until 6 months to a year after the hardware was purchased.&amp;nbsp; My question is, from a capacity planning perspective, how do you look at current and available usage of your compute/memory resources for your clusters and remember to take into account, oh yeah, the Accounting team is going to come asking for their two 4 vCPU x 32 GB vRAM virtual machines in a few months.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought about creating a dummy VM and figuring out a way to run a process that would sustain usage of a certain amount of compute and memory resources.&amp;nbsp; That way the VM would always appear to be using those resources and my view of available resources at any given time would not be misleading.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was wondering if any of you have run into a similar situation and what you've done to effectively manage it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;BD&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Dec 2013 19:34:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Placeholder-VM-for-Resource-Reservation/m-p/1343471#M126108</guid>
      <dc:creator>bsd1977</dc:creator>
      <dc:date>2013-12-20T19:34:36Z</dc:date>
    </item>
    <item>
      <title>Re: Placeholder VM for Resource Reservation</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Placeholder-VM-for-Resource-Reservation/m-p/1343472#M126109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my company, we do have a "booking" process. The only way we found to follow these requirement is to manage them out of vCenter.&lt;/P&gt;&lt;P&gt;In fact, we use 2 differents sources :&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Health check report, to follow actual resources demands&lt;/LI&gt;&lt;LI&gt;An excel file, where every request that "may soon or not" be activated is listed&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using these 2 files, we made a small program that is able to tell us some key informations:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;How many vCPU are actually declared on the hosts and the ratio with the physical cores&lt;/LI&gt;&lt;LI&gt;Same for vRAM and RAM&lt;/LI&gt;&lt;LI&gt;How many vCPU will be declared if every request are activated&lt;/LI&gt;&lt;LI&gt;Same for vRAM and RAM&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;This enables us to know when new hosts are required (we do not require project to fund them).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We also combined this analysis with vCenter Operations Manager dashboards on every clusters to know the actual resource demand (instead of the "declared" part as stated above).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;Ludovic&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Dec 2013 22:25:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Placeholder-VM-for-Resource-Reservation/m-p/1343472#M126109</guid>
      <dc:creator>ldesfontaines</dc:creator>
      <dc:date>2013-12-20T22:25:36Z</dc:date>
    </item>
  </channel>
</rss>

