- Timestamp:
- 07/20/12 11:35:36 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
xssim/trunk/src/test/rewolucja/schemas/example/coolemall/example3.xml
r349 r350 1 <?xml version="1.0" encoding="UTF-8"?> 1 2 <environment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 2 3 xsi:noNamespaceSchemaLocation="../../XSSimResSchema.xsd"> 3 4 4 5 <!-- CoolEmAll testbed description -->6 5 <resources> 7 <computingResource class="Rack" name="rack"> 8 <resourceUnit class="Storage"> 9 <amount unit="MB">4915200</amount> 10 <parameter name=""></parameter> 11 </resourceUnit> 12 <parameter name="PSU"> 13 <property name="powerUsage"> 14 <value>180</value> 15 </property> 16 </parameter> 17 <computingResource class="RECS" name="recs1"> 6 <description> 7 This short example presents how to describe computing resource location. 8 Simulated architecture consists of data center with 2 racks named rack1 and rack2, respectively. 9 Location of rack1 is defined using vector (4, 0, 2), while rack2 using vector (6, 0, 2) 10 Rack1 contains 2 computing nodes - node11 and node12. Appropriate coordinates for node11 are (0, 0, 0) 11 and for node12 (0, 1, 0). Rack2 contains 2 computing nodes named node21 and node22. Their location is defined as follows: 12 (0, 0, 0) for node21 and (1, 0, 0) for node22. 13 Using 3 coordinates allows to express location in various ways. It can be interpreted as a absolute placement in 3D, as well as the 14 relative position according to the parent computing resource. Moreover, it is possible to define only the arrangement of 15 the computing resources by increasing only the value of one coordinate. 16 In the following example, racks location is defined using relative positions (with respect to the data center), while 17 for nodes the order of appearance is specified (with additional direction in which the order tends 18 (node12 is located after node11 and placed above it, while node22 is located on the right side of node21) 19 It has to be stressed that simulator only stores the location parameters and does not process them. Hence, their interpretation should be done by user. 20 </description> 21 <computingResource class="DataCenter" name="dataCenter"> 22 <computingResource class="Rack" name="rack1"> 18 23 <location> 19 <horizontal> 0</horizontal>24 <horizontal>4</horizontal> 20 25 <vertical>0</vertical> 21 <depth> 0</depth>26 <depth>2</depth> 22 27 </location> 23 <computingResource class="ComputingNode" count="18"> 24 <resourceUnit class="Memory"> 25 <amount unit="MB">16384</amount> 26 </resourceUnit> 27 <computingResource class="Processor" type="i7"> 28 <parameter name="speed"> 29 <value>2</value> 30 </parameter> 31 <computingResource class="Core" count="4"/> 32 </computingResource> 28 <computingResource class="ComputingNode" name="node11"> 29 <location> 30 <horizontal>0</horizontal> 31 <vertical>0</vertical> 32 <depth>0</depth> 33 </location> 34 </computingResource> 35 <computingResource class="ComputingNode" name="node12"> 36 <location> 37 <horizontal>0</horizontal> 38 <vertical>1</vertical> 39 <depth>0</depth> 40 </location> 41 </computingResource> 42 </computingResource> 43 <computingResource class="Rack" name="rack2"> 44 <location> 45 <horizontal>6</horizontal> 46 <vertical>0</vertical> 47 <depth>2</depth> 48 </location> 49 <computingResource class="ComputingNode" name="node21"> 50 <location> 51 <horizontal>0</horizontal> 52 <vertical>0</vertical> 53 <depth>0</depth> 54 </location> 55 </computingResource> 56 <computingResource class="ComputingNode" name="node22"> 57 <location> 58 <horizontal>1</horizontal> 59 <vertical>0</vertical> 60 <depth>0</depth> 61 </location> 33 62 </computingResource> 34 63 </computingResource> 35 <computingResource class="RECS" name="recs2"> 36 <location> 37 <horizontal>0</horizontal> 38 <vertical>1</vertical> 39 <depth>0</depth> 40 </location> 41 <computingResource class="ComputingNode" count="18"> 42 <resourceUnit class="Memory"> 43 <amount unit="MB">4096</amount> 44 </resourceUnit> 45 <computingResource class="Processor" type="Atom"> 46 <computingResource class="Core" count="2"/> 47 </computingResource> 48 </computingResource> 49 </computingResource> 50 <computingResource class="RECS" name="recs3"> 51 <location> 52 <horizontal>0</horizontal> 53 <vertical>2</vertical> 54 <depth>0</depth> 55 </location> 56 <computingResource class="ComputingNode" count="18"> 57 <resourceUnit class="Memory"> 58 <amount unit="MB">2048</amount> 59 </resourceUnit> 60 <computingResource class="Processor" type="AMD Fusion"> 61 <computingResource class="Core" count="2"/> 62 </computingResource> 63 </computingResource> 64 </computingResource> 65 <computingResource class="RECS" name="recs4"> 66 <location> 67 <horizontal>0</horizontal> 68 <vertical>3</vertical> 69 <depth>0</depth> 70 </location> 71 <computingResource class="ComputingNode" count="18"> 72 <resourceUnit class="Memory"> 73 <amount unit="MB">2048</amount> 74 </resourceUnit> 75 <computingResource class="Processor" type="ARM"> 76 <computingResource class="Core"/> 77 </computingResource> 78 </computingResource> 79 </computingResource> 80 </computingResource> 81 64 </computingResource> 82 65 <scheduler class="Cluster" name="cluster"> 83 66 <schedulingPlugin> … … 85 68 </schedulingPlugin> 86 69 <managedComputingResources include="false"> 87 <resourceName> rack</resourceName>70 <resourceName>dataCenter</resourceName> 88 71 </managedComputingResources> 89 72 </scheduler> 90 91 73 </resources> 92 74 </environment>
Note: See TracChangeset
for help on using the changeset viewer.
