Preparing to integrate reservations by importing XML files

The Generic-Reservation-XML-file-parser can be used to import data for Reservations from XML files. The following types of Reservation elements can be specified in the XML file that is imported into TrueSight Capacity Optimization using the ETL module:

Reservations
System Templates
Onboardings
Offboardings

Reservation XML overview

The following XML provides a high-level overview of the content in the file. All the sections are optional, which allows you to import one or more Reservation elements into TrueSight Capacity Optimization.

<?xml version="1.0" encoding="UTF-8"?>
<rsvData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="rsv_data_etl.xsd">
<templates> 
<systemTemplate>
</systemTemplate>
</templates>
<reservations> 
<reservation>
</reservation>
</reservations>
<onboardings> 
<onboarding>
</onboarding>
</onboardings>
<offboardings> 
<offboarding>
</offboarding>
</offboardings>
</rsvData>

Before deploying and configuring the various ETL tasks that impacts the Reservations in your system, it is recommended to go through the following preparatory steps:

Analyze the XML file structure: Analyze the structure of your XML files. For details, see the attached sample XML Schema Document.
Determine the mandatory fields: Ensure that all mandatory fields are included in the XML files. For details, see the attached sample XML Schema Document or following examples. For the reservation XML files, the metadata field is optional.
The metadata field can be added only when you apply Patch 1 (20.02.01) of TrueSight Capacity Optimization 20.02.

Examples

The following sections provide examples for the various Reservation items. You can also refer to the attached sample XML file for reference.

System Templates
Reservations
Reservations with custom resource instances
Onboardings
Onboardings with custom resource instances
Offboardings
Offboardings with custom resource instances

System Templates

You must specify unique lookupName while creating System Templates. If an existing System Template uses the same lookupName, it will be updated.

<templates>

<systemTemplate>
<name>VM_Austin_44</name>
<lookupName>VM_Austin_44_9876</lookupName>

<enttypenm>gm:vmw</enttypenm>
<cpuCores>8</cpuCores>
<memTotal>2147483648</memTotal>
<storageTotal>64424509440</storageTotal>
<cpuTotalMHz>20000</cpuTotalMHz> 
<os>UNIX</os> 
<cpuUtilization>0.1</cpuUtilization> 
<cpuEntitledCapacity>0.4</cpuEntitledCapacity> 
<memUtilization>0.9</memUtilization> 
<storageUtilization>0.6</storageUtilization> 
</systemTemplate>
<systemTemplate>

</systemTemplate>
</templates>

Reservations

<reservations>
<reservation> 
<name>Reservation_POC_March</name>
<startDate>2015-03-25</startDate>
<endDate>2015-03-31</endDate> 
<description>Reserve resources for POC</description> 
<owner>Alan</owner> 
<priority>HIGH</priority> 
<probability>75</probability> 
<resources>
<resourceTemplates numItems="1">
<systemTemplateLookup name="VM_Austin_44_9876"/>

</resourceTemplates>
</resources>
<capacityPools>
<capacityPoolLookup id="2211"/>
</capacityPools>
</reservation>
<reservation> 
<name>Reservation_BugHunt</name>
<startDate>2015-02-12</startDate>
<endDate>2015-02-15</endDate> 
<description>Reserve resources</description> 
<owner>Mary</owner> 
<priority>HIGH</priority> 
<probability>90</probability> 
<items>
<item>
<name>My Item</name>
<systemTemplateLookup id="2383"/>

</item>
</items>
<capacityPools>
<capacityPoolLookup id="2211"/>
</capacityPools>
</reservation>
</reservations>

Reservations with custom resource instances

<reservations>
<reservation> 
<name>Lync2013 server upgrade</name>
     <startDate>2020-08-25</startDate>
     <description>Upgrade Lync2013 infrastucture to handle new phone calls</description>
     <owner>David</owner>
    <metadata><![CDATA[{"windows_license":"4","admin_mail":"admin@mail.com","support_level":"premier"}]]></metadata>
     <resources>
       <resourceSpecs numItems="2">
         <enttypenm>gm:vmw</enttypenm>
         <cpuCores>4</cpuCores>
         <memTotal>2147483648</memTotal>
         <storageTotal>64424509440</storageTotal>
         <cpuTotalMHz>20000</cpuTotalMHz>
       </resourceSpecs>
     </resources>
     <capacityPools>
       <capacityPoolLookup>
         <lookupFields>
           <lookupField name="NAME" value="Silver Houston - VMware" />
         </lookupFields>
       </capacityPoolLookup>
     </capacityPools>
   </reservation>
   <reservation>
     <name>Free up Lync2013 server upgrade resources</name>
     <startDate>2020-09-25</startDate>
     <description>Upgrade Lync2013 infrastucture to handle new phone calls</description>
     <owner>David</owner>
     <metadata><![CDATA[{"windows_license":"4","admin_mail":"admin@mail.com","support_level":"premier"}]]></metadata>
     <resources>
       <resourceSpecs numItems="1">
         <enttypenm>gm:vmw</enttypenm>
         <cpuCores>-4</cpuCores>
         <memTotal>-2147483648</memTotal>
         <storageTotal>-64424509440</storageTotal>
         <cpuTotalMHz>-20000</cpuTotalMHz>
       </resourceSpecs>
     </resources>
     <capacityPools>
       <capacityPoolLookup>
         <lookupFields>
           <lookupField name="NAME" value="Silver Houston - VMware" />
         </lookupFields>
       </capacityPoolLookup>
     </capacityPools>
   </reservation>
</reservations>

Onboardings

Onboardings with custom resource instances

<onboarding>
<name>Onboarding_ESXHost_33</name>
<description>Add new ESX host to cluster</description> 
<onboardingDate>2015-03-01</onboardingDate>
<realizationMode>MANUAL</realizationMode>
<resources>
           <resourceSpecs numItems="1">
               <name>vmware_large_spec</name> 
               <enttypenm>gm:vmw</enttypenm> 
               <cpuCores>8</cpuCores>
               <memTotal>2147483648</memTotal>
               <storageTotal>64424509440</storageTotal>
               <cpuTotalMHz>20000</cpuTotalMHz> 
               <cpuEntitledCapacity>4.0</cpuEntitledCapacity> 
               <cpuUtilization>0.1</cpuUtilization> 
               <memUtilization>0.9</memUtilization> 
               <storageUtilization>0.6</storageUtilization> 
</resourceSpecs>
       </resources>


<reservationTargetLookup>
<lookupFields>
<lookupField name="VMW_VMREF" value="domain-c23" />
<lookupField name="NAME" value="cluster23" />
</lookupFields>
</reservationTargetLookup>
</onboarding>

Offboardings

Offboardings with custom resource instances

<offboardings>
<offboarding>
<name>Onboarding_ESXHost_55</name>
<offboardingDate>2015-01-24</offboardingDate>
<description>Offboarding decommissioned host</description> 
<realizationMode>AUTOMATIC</realizationMode> 
       <resources>
           <resourceSpecs numItems="1">
               <name>vmware_large_spec</name> 
               <enttypenm>gm:vmw</enttypenm> 
               <cpuCores>8</cpuCores>
               <memTotal>2147483648</memTotal>
               <storageTotal>64424509440</storageTotal>
               <cpuTotalMHz>20000</cpuTotalMHz> 
               <cpuEntitledCapacity>4.0</cpuEntitledCapacity> 
               <cpuUtilization>0.1</cpuUtilization> 
               <memUtilization>0.9</memUtilization> 
               <storageUtilization>0.6</storageUtilization> 
           </resourceSpecs>
       </resources>
<reservationTargetLookup name="Cluster-1"/>

</offboarding>
</offboardings>