| 1 | <?xml version="1.0" encoding="UTF-8"?> |
|---|
| 2 | <environment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
|---|
| 3 | xsi:noNamespaceSchemaLocation="../../DCWoRMSResSchema.xsd"> |
|---|
| 4 | |
|---|
| 5 | <resources> |
|---|
| 6 | <description> |
|---|
| 7 | The goal of this example is to introduce the templates usage. |
|---|
| 8 | It focuses on showing that appropriate templates may be included on various computing resource levels and moreover can be formed using other templates. |
|---|
| 9 | Simulated architecture consists of data center with 2 racks named rack1 and rack2 respectively. |
|---|
| 10 | Rack1 contains 2 computing nodes - node11 and node12, described in common way. |
|---|
| 11 | Nodes in rack2 are defined using template. Node21 refers to template modelNodeA and, |
|---|
| 12 | thus will be created with respect to the specification given in that template (node will have 4 processors with speed 2). |
|---|
| 13 | Node22 contains 8 processors which definition is included in modeProcessorB template. |
|---|
| 14 | </description> |
|---|
| 15 | <computingResource class="DataCenter" name="dataCenter"> |
|---|
| 16 | <computingResource class="Rack" name="rack1"> |
|---|
| 17 | <computingResource class="ComputingNode" name="node11"> |
|---|
| 18 | </computingResource> |
|---|
| 19 | <computingResource class="ComputingNode" name="node12"> |
|---|
| 20 | </computingResource> |
|---|
| 21 | </computingResource> |
|---|
| 22 | <computingResource class="Rack" name="rack2"> |
|---|
| 23 | <computingResource class="ComputingNode" name="node21"> |
|---|
| 24 | <templateId>modelNodeA</templateId> |
|---|
| 25 | </computingResource> |
|---|
| 26 | <computingResource class="ComputingNode" name="node22"> |
|---|
| 27 | <computingResource class="Processor" count="8"> |
|---|
| 28 | <templateId>modelProcessorB</templateId> |
|---|
| 29 | </computingResource> |
|---|
| 30 | </computingResource> |
|---|
| 31 | </computingResource> |
|---|
| 32 | </computingResource> |
|---|
| 33 | <scheduler class="Cluster" name="cluster"> |
|---|
| 34 | <schedulingPlugin> |
|---|
| 35 | <name>FCFSLocalSchedulingPlugin</name> |
|---|
| 36 | </schedulingPlugin> |
|---|
| 37 | <managedComputingResources include="false"> |
|---|
| 38 | <resourceName>dataCenter</resourceName> |
|---|
| 39 | </managedComputingResources> |
|---|
| 40 | </scheduler> |
|---|
| 41 | </resources> |
|---|
| 42 | |
|---|
| 43 | <templates> |
|---|
| 44 | <description> |
|---|
| 45 | There are two processor templates named modelProcessorA (with cpu speed 2) and modelProcessorB (with cpu speed 1). |
|---|
| 46 | There is also one computing node template denoted as modelNodeA, which contains 4 processors that refer to modelProcessorA template. |
|---|
| 47 | That means that the given processors will be created according to the characteristics defined in template modelProcessorA (they will have speed equal 2). |
|---|
| 48 | </description> |
|---|
| 49 | <computingResourceTemplate class="ComputingNode" name="modelNodeA"> |
|---|
| 50 | <computingResource class="Processor" count="4"> |
|---|
| 51 | <templateId>modelProcessorA</templateId> |
|---|
| 52 | </computingResource> |
|---|
| 53 | </computingResourceTemplate> |
|---|
| 54 | <computingResourceTemplate class="Processor" name="modelProcessorA"> |
|---|
| 55 | <parameter name="speed"> |
|---|
| 56 | <value>2</value> |
|---|
| 57 | </parameter> |
|---|
| 58 | </computingResourceTemplate> |
|---|
| 59 | <computingResourceTemplate class="Processor" name="modelProcessorB"> |
|---|
| 60 | <parameter name="speed"> |
|---|
| 61 | <value>1</value> |
|---|
| 62 | </parameter> |
|---|
| 63 | </computingResourceTemplate> |
|---|
| 64 | </templates> |
|---|
| 65 | </environment> |
|---|
