<?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>article Intelligent Automation For Cloud - Create vCenter Resource Pool  in Data Center and Cloud Knowledge Base</title>
    <link>https://community.cisco.com/t5/data-center-and-cloud-knowledge-base/intelligent-automation-for-cloud-create-vcenter-resource-pool/ta-p/3124106</link>
    <description>&lt;P&gt;This document explains the logic to develop Tidal Enterprise Orchestrator workflow to automate the process of creating vCenter Resource Pool&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* vSphere Power CLI must be installed either on the TEO server or vCenter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* vMA can also be used to achieve the same task&lt;/P&gt;&lt;P&gt;* Script execution must be enabled on the vCenter&lt;/P&gt;&lt;P&gt;* DRS must be enabled on the vCenter in order to create the Resource Pool&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This workflow was build using TEO native Powershell activity. The vCLI snapin was used to execute the Power vCLI commands on the remote vCenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The powershell script is very simple&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Add-PSSnapin VMware.VimAutomation.Core&lt;/P&gt;&lt;P&gt;Connect-VIServer -Server localhost -Protocol http&lt;/P&gt;&lt;P&gt;get-cluster&lt;/P&gt;&lt;P&gt;New-ResourcePool -Location $args[0] -Name $args[1] &lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/1/3/9/65931-ScreenHunter_001.jpg" alt="ScreenHunter_001.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/2/3/9/65932-ScreenHunter_002.jpg" alt="ScreenHunter_002.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/4/3/9/65934-ScreenHunter_004.jpg" alt="ScreenHunter_004.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; After creating the vCenter Resource Pool, the workflow also sets the CPU and Memory reservation values if provided as input. Otherwise, it takes the default values and create RP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/5/3/9/65935-ScreenHunter_006.jpg" alt="ScreenHunter_006.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/6/3/9/65936-ScreenHunter_007.jpg" alt="ScreenHunter_007.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/7/3/9/65937-ScreenHunter_008.jpg" alt="ScreenHunter_008.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Add-PSSnapin VMware.VimAutomation.Core&lt;/P&gt;&lt;P&gt;Connect-VIServer -Server localhost -Protocol http&lt;/P&gt;&lt;P&gt;get-cluster&lt;/P&gt;&lt;P&gt;Set-ResourcePool&amp;nbsp; -ResourcePool $args[0] -MemReservationMB $args[1] &lt;/P&gt;&lt;P&gt;Set-ResourcePool&amp;nbsp; -ResourcePool $args[0] -CpuReservationMhz $args[2]&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 03 Nov 2011 17:08:54 GMT</pubDate>
    <dc:creator>Syed Shahzad Ali</dc:creator>
    <dc:date>2011-11-03T17:08:54Z</dc:date>
    <item>
      <title>Intelligent Automation For Cloud - Create vCenter Resource Pool</title>
      <link>https://community.cisco.com/t5/data-center-and-cloud-knowledge-base/intelligent-automation-for-cloud-create-vcenter-resource-pool/ta-p/3124106</link>
      <description>&lt;P&gt;This document explains the logic to develop Tidal Enterprise Orchestrator workflow to automate the process of creating vCenter Resource Pool&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* vSphere Power CLI must be installed either on the TEO server or vCenter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* vMA can also be used to achieve the same task&lt;/P&gt;&lt;P&gt;* Script execution must be enabled on the vCenter&lt;/P&gt;&lt;P&gt;* DRS must be enabled on the vCenter in order to create the Resource Pool&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This workflow was build using TEO native Powershell activity. The vCLI snapin was used to execute the Power vCLI commands on the remote vCenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The powershell script is very simple&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Add-PSSnapin VMware.VimAutomation.Core&lt;/P&gt;&lt;P&gt;Connect-VIServer -Server localhost -Protocol http&lt;/P&gt;&lt;P&gt;get-cluster&lt;/P&gt;&lt;P&gt;New-ResourcePool -Location $args[0] -Name $args[1] &lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/1/3/9/65931-ScreenHunter_001.jpg" alt="ScreenHunter_001.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/2/3/9/65932-ScreenHunter_002.jpg" alt="ScreenHunter_002.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/4/3/9/65934-ScreenHunter_004.jpg" alt="ScreenHunter_004.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; After creating the vCenter Resource Pool, the workflow also sets the CPU and Memory reservation values if provided as input. Otherwise, it takes the default values and create RP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/5/3/9/65935-ScreenHunter_006.jpg" alt="ScreenHunter_006.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/6/3/9/65936-ScreenHunter_007.jpg" alt="ScreenHunter_007.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/legacy/7/3/9/65937-ScreenHunter_008.jpg" alt="ScreenHunter_008.jpg" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Add-PSSnapin VMware.VimAutomation.Core&lt;/P&gt;&lt;P&gt;Connect-VIServer -Server localhost -Protocol http&lt;/P&gt;&lt;P&gt;get-cluster&lt;/P&gt;&lt;P&gt;Set-ResourcePool&amp;nbsp; -ResourcePool $args[0] -MemReservationMB $args[1] &lt;/P&gt;&lt;P&gt;Set-ResourcePool&amp;nbsp; -ResourcePool $args[0] -CpuReservationMhz $args[2]&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 03 Nov 2011 17:08:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/data-center-and-cloud-knowledge-base/intelligent-automation-for-cloud-create-vcenter-resource-pool/ta-p/3124106</guid>
      <dc:creator>Syed Shahzad Ali</dc:creator>
      <dc:date>2011-11-03T17:08:54Z</dc:date>
    </item>
  </channel>
</rss>

