Changeset 325 for xssim/trunk
- Timestamp:
- 07/18/12 17:08:12 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
xssim/trunk/src/test/rewolucja/schemas/XSSimResSchema.xsd
r319 r325 5 5 <xs:complexType name="pluginType"> 6 6 <xs:annotation> 7 <xs:documentation>Base plugin description</xs:documentation> 7 <xs:documentation>Base plugin type. 8 Plugins allow a researcher to configure and adapt the simulation framework to his/her experiment 9 starting from modeling job performance, through method of calculating energy estimation up to implementation of scheduling policies 10 Name of the plugin specifies the JAVA class that implements dedicated interface.</xs:documentation> 8 11 </xs:annotation> 9 12 <xs:sequence> … … 15 18 <xs:complexType name="timeEstimationPluginType"> 16 19 <xs:annotation> 17 <xs:documentation>Time estimation plugin</xs:documentation> 18 </xs:annotation> 19 <xs:complexContent> 20 <xs:extension base="pluginType"/> 20 <xs:documentation>TimeEstimationPlugin derived from Plugin. 21 Time estimation plugin provides means to include specific application performance models during simulations 22 and allows researchers to introduce specific ways of calculating task execution time.</xs:documentation> 23 </xs:annotation> 24 <xs:complexContent> 25 <xs:restriction base="pluginType"> 26 <xs:sequence> 27 <xs:element name="name" type="xs:string" default="ExecTimeEstimationPlugin"></xs:element> 28 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 29 </xs:sequence> 30 </xs:restriction> 21 31 </xs:complexContent> 22 32 </xs:complexType> … … 24 34 <xs:complexType name="resourceType"> 25 35 <xs:annotation> 26 <xs:documentation>Base resource type</xs:documentation> 36 <xs:documentation>Base resource type. 37 It allows to define simulation entities like computing resources, devices, schedulers. 38 Attributes: class - determines the component of the architecture i.e rack, processor, memory, storage etc. 39 type - type of resource; for instance, continuous for memory, bandwidth, etc. and discrete for processors 40 name - unique resource identifier, if not specified it will be generated by the simulator in the following manner: class + "_" + subsequent_natural_number 41 </xs:documentation> 27 42 </xs:annotation> 28 43 <xs:sequence> … … 31 46 <xs:attribute name="class" type="xs:string" use="required"/> 32 47 <xs:attribute name="type" type="xs:string" use="optional"/> 33 <xs:attribute name=" id" type="xs:ID" use="optional"/>48 <xs:attribute name="name" type="xs:ID" use="optional"/> 34 49 </xs:complexType> 35 50 36 51 <xs:complexType name="computingResourceType"> 37 52 <xs:annotation> 38 <xs:documentation>Computing resource template</xs:documentation> 53 <xs:documentation> ComputingResource derived from Resource 54 Computing resource specifies resources that are able to perform computing operations. 55 From the simulator point of view computing resource is everything that is/contains processing element. 56 Hence, all entities like core, processor, computing node, as well as those which aggregate them (like shelf, rack, container etc.) 57 should be define using this type. This way of description provides flexibility in defining system architecture 58 and allows to build hierarchy of resources that corresponds to real world. 59 Attributes: groupId - allows to group resources of the given class in the logical structures that can be used during binding them with schedulers 60 count - defines number of resources of the given class</xs:documentation> 39 61 </xs:annotation> 40 62 <xs:complexContent> … … 43 65 <xs:choice> 44 66 <xs:sequence> 45 <xs:element name="computingResource" type="computingResourceType" minOccurs="0" maxOccurs="unbounded"></xs:element>46 67 <xs:element name="resourceUnit" type="resourceUnitType" minOccurs="0" maxOccurs="unbounded"></xs:element> 47 68 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 48 69 <xs:element name="energyEstimationPlugin" type="energyEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element> 49 70 <xs:element name="profile" type="profileType" minOccurs="0" maxOccurs="1"></xs:element> 50 </xs:sequence> 51 <xs:element name="templateId" type="xs:IDREF"/> 71 <xs:element name="location" type="locationType" minOccurs="0" maxOccurs="1"></xs:element> 72 <xs:element name="computingResource" type="computingResourceType" minOccurs="0" maxOccurs="unbounded"></xs:element> 73 </xs:sequence> 74 <xs:sequence> 75 <xs:element name="templateId" type="xs:IDREF"/> 76 <xs:element name="location" type="locationType" minOccurs="0" maxOccurs="1"></xs:element> 77 </xs:sequence> 52 78 </xs:choice> 53 <xs:element name="location" type="locationType" minOccurs="0" maxOccurs="1"></xs:element>54 79 </xs:sequence> 55 80 <xs:attribute name="groupId" type="xs:integer" use="optional"/> … … 61 86 <xs:complexType name="computingResourceTemplateType"> 62 87 <xs:annotation> 63 <xs:documentation>Computing resource instance</xs:documentation> 88 <xs:documentation>ComputingResourceTemplate derived from Resource. 89 It allows to define model of computing resource component that may constitute other computing resources 90 Computing resource templates can be then referred in computing resource definition</xs:documentation> 64 91 </xs:annotation> 65 92 <xs:complexContent> 66 93 <xs:extension base="resourceType"> 67 94 <xs:sequence> 68 <xs:element name="computingResource" type="computingResourceType" minOccurs="0" maxOccurs="unbounded"></xs:element>69 95 <xs:element name="resourceUnit" type="resourceUnitType" minOccurs="0" maxOccurs="unbounded"></xs:element> 70 96 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 71 97 <xs:element name="energyEstimationPlugin" type="energyEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element> 72 98 <xs:element name="profile" type="profileType" minOccurs="0" maxOccurs="1"></xs:element> 99 <xs:element name="computingResource" type="computingResourceType" minOccurs="0" maxOccurs="unbounded"></xs:element> 73 100 </xs:sequence> 74 101 </xs:extension> … … 78 105 <xs:complexType name="schedulerType"> 79 106 <xs:annotation> 80 <xs:documentation>Scheduler</xs:documentation> 107 <xs:documentation>Scheduler derived from Resource. 108 It allows to model scheduling entity responsible for managing resources.</xs:documentation> 81 109 </xs:annotation> 82 110 <xs:complexContent> … … 86 114 <xs:choice minOccurs="1" maxOccurs="unbounded"> 87 115 <xs:element name="scheduler" type="schedulerType"></xs:element> 88 <xs:element name="managedComputingResource " type="managedComputingResourceType"></xs:element>116 <xs:element name="managedComputingResources" type="managedComputingResourcesType"></xs:element> 89 117 </xs:choice> 90 118 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> … … 96 124 <xs:complexType name="schedulingPluginType"> 97 125 <xs:annotation> 98 <xs:documentation>Scheduling plugin</xs:documentation> 126 <xs:documentation>SchedulingPlugin derived from Plugin. Scheduling plugins allow plugging scheduling algorithms into the simulated environment. 127 Elements: frequency - is used to enable scheduling periodically; it specifies the time interval (in seconds by default) between subsequent scheduling invocations 128 </xs:documentation> 99 129 </xs:annotation> 100 130 <xs:complexContent> 101 131 <xs:extension base="pluginType"> 102 132 <xs:sequence> 103 <xs:element name="frequency" type=" xs:integer" minOccurs="0" maxOccurs="1"></xs:element>133 <xs:element name="frequency" type="valueWithUnitType" minOccurs="0" maxOccurs="1"></xs:element> 104 134 </xs:sequence> 105 135 </xs:extension> … … 109 139 <xs:complexType name="resourceUnitType"> 110 140 <xs:annotation> 111 <xs:documentation>Description of resource unit</xs:documentation> 141 <xs:documentation>Resource unit is used to define non-computing resource like memory, storage etc 142 Elements: amount - represents concrete amount (values) of specific resource unit</xs:documentation> 112 143 </xs:annotation> 113 144 <xs:complexContent> 114 145 <xs:extension base="resourceType"> 115 146 <xs:sequence> 116 <xs:element name="amount" type=" xs:double"/>147 <xs:element name="amount" type="valueWithUnitType"/> 117 148 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 118 149 </xs:sequence> … … 120 151 </xs:complexContent> 121 152 </xs:complexType> 122 123 <xs:complexType name="managedComputingResourceType"> 124 <xs:annotation> 125 <xs:documentation>Definition of controlled (by scheduler) computing resources</xs:documentation> 126 </xs:annotation> 127 <xs:sequence minOccurs="1" maxOccurs="unbounded"> 128 <xs:element name="resourceId" type="xs:string"></xs:element> 129 </xs:sequence> 153 154 <xs:complexType name="valueWithUnitType"> 155 <xs:annotation> 156 <xs:documentation>ValueWitUnit derived from double. Allows to provide units in which a given value is expressed 157 Attributes: unit - indicate appropriate units, for instance: seconds, watts, bytes etc. </xs:documentation> 158 </xs:annotation> 159 <xs:simpleContent> 160 <xs:extension base="xs:double"> 161 <xs:attribute name="unit" type="xs:string" use="optional"/> 162 </xs:extension> 163 </xs:simpleContent> 164 </xs:complexType> 165 166 <xs:complexType name="managedComputingResourcesType"> 167 <xs:annotation> 168 <xs:documentation>ManagedComputingResource type specifies controlled (by scheduler) computing resources. 169 They can be provided either by listing their names or listing the group ids for which they belong 170 Attributes: include - specifies whether scheduler shoud be built on top of given resources or shoud also incude them. 171 In other words, false (default) value indicates that scheduler maaner only subcomponents of the listed resources; 172 true value determines that also listed resources will be under the control of the defined scheduler</xs:documentation> 173 </xs:annotation> 174 <xs:choice> 175 <xs:sequence> 176 <xs:element name="resourceName" type="xs:string" minOccurs="1" maxOccurs="unbounded"></xs:element> 177 </xs:sequence> 178 <xs:sequence> 179 <xs:element name="resourceGroupId" type="xs:string" minOccurs="1" maxOccurs="unbounded"></xs:element> 180 </xs:sequence> 181 </xs:choice> 130 182 <xs:attribute name="include" type="xs:boolean" default="false"/> 131 183 </xs:complexType> … … 133 185 <xs:complexType name="energyEstimationPluginType"> 134 186 <xs:annotation> 135 <xs:documentation>Energy consumption estimation plugin</xs:documentation> 187 <xs:documentation>EnergyEstimationPlugin derived from Plugin. 188 Energy estimation plugin is used to customize estimation of energy consumptions of the given computing resource 189 to specific applications and hardware.</xs:documentation> 136 190 </xs:annotation> 137 191 <xs:complexContent> … … 142 196 <xs:complexType name="profileType"> 143 197 <xs:annotation> 144 <xs:documentation> Resource profiles</xs:documentation>198 <xs:documentation>Profile acts as a container for resource profiles: power and air throughput</xs:documentation> 145 199 </xs:annotation> 146 200 <xs:sequence> … … 152 206 <xs:complexType name="powerProfileType"> 153 207 <xs:annotation> 154 <xs:documentation>Power profile </xs:documentation>208 <xs:documentation>Power profile allows powerState and other power-related paremters definition</xs:documentation> 155 209 </xs:annotation> 156 210 <xs:sequence> … … 162 216 <xs:complexType name="powerStatesType"> 163 217 <xs:annotation> 164 <xs:documentation> Definition of supportedpower states</xs:documentation>165 </xs:annotation> 166 <xs:sequence minOccurs="1" maxOccurs="unbounded">167 <xs:element name="powerState" type="powerStateType" ></xs:element>218 <xs:documentation>PowerState type act as a container for power states</xs:documentation> 219 </xs:annotation> 220 <xs:sequence> 221 <xs:element name="powerState" type="powerStateType" minOccurs="1" maxOccurs="unbounded"></xs:element> 168 222 </xs:sequence> 169 223 </xs:complexType> … … 171 225 <xs:complexType name="powerStateType"> 172 226 <xs:annotation> 173 <xs:documentation>Definition of the power state</xs:documentation> 227 <xs:documentation>Power state defines availabe (for computing resource) power states. 228 Elements: name - denotes name of the given power state 229 powerUsage - defines power consumption in the given state 230 transition - specifies possible power states transitions form the given power state</xs:documentation> 174 231 </xs:annotation> 175 232 <xs:sequence> 176 233 <xs:element name="name" type="xs:string"></xs:element> 177 <xs:element name="powerUsage" type="xs:double" minOccurs="0" maxOccurs="1"></xs:element> 178 <xs:element name="transition" type="energyStatesTransitionType" minOccurs="0" maxOccurs="unbounded"></xs:element> 179 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 180 </xs:sequence> 181 </xs:complexType> 182 183 <xs:complexType name="energyStatesTransitionType"> 184 <xs:annotation> 185 <xs:documentation>Description of power states transtition</xs:documentation> 234 <xs:element name="powerUsage" type="valueWithUnitType" minOccurs="0" maxOccurs="1"></xs:element> 235 <xs:element name="transition" type="powerStatesTransitionType" minOccurs="0" maxOccurs="unbounded"></xs:element> 236 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 237 </xs:sequence> 238 </xs:complexType> 239 240 <xs:complexType name="powerStatesTransitionType"> 241 <xs:annotation> 242 <xs:documentation>Description of power states transtition 243 Elements: to - denotes name of target power state 244 powerUsage - defines transition cost in the form of power consumption 245 time - specifies transition time</xs:documentation> 186 246 </xs:annotation> 187 247 <xs:sequence> 188 248 <xs:element name="to" type="xs:string"></xs:element> 189 <xs:element name="powerUsage" type=" xs:double"></xs:element>190 <xs:element name="time" type=" xs:double"></xs:element>249 <xs:element name="powerUsage" type="valueWithUnitType"></xs:element> 250 <xs:element name="time" type="valueWithUnitType"></xs:element> 191 251 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 192 252 </xs:sequence> … … 195 255 <xs:complexType name="airThroughputProfileType"> 196 256 <xs:annotation> 197 <xs:documentation> Description of the computing resource fan</xs:documentation>198 </xs:annotation> 199 <xs:sequence minOccurs="1" maxOccurs="unbounded">200 <xs:element name="airThroughputState" type="airThroughputStateType" ></xs:element>257 <xs:documentation>AirThrouhputProfile type acts as a container for air throughput states</xs:documentation> 258 </xs:annotation> 259 <xs:sequence> 260 <xs:element name="airThroughputState" type="airThroughputStateType" minOccurs="1" maxOccurs="unbounded"></xs:element> 201 261 </xs:sequence> 202 262 </xs:complexType> … … 204 264 <xs:complexType name="airThroughputStateType"> 205 265 <xs:annotation> 206 <xs:documentation>Definition of the power state</xs:documentation> 266 <xs:documentation>Air througput state provides means to define air flow level. 267 It can represent, for instance, a fan working state</xs:documentation> 207 268 </xs:annotation> 208 269 <xs:sequence> 209 270 <xs:element name="name" type="xs:string"></xs:element> 210 271 <xs:element name="value" type="xs:double"></xs:element> 211 <xs:element name="powerUsage" type=" xs:double" minOccurs="0"></xs:element>272 <xs:element name="powerUsage" type="valueWithUnitType" minOccurs="0"></xs:element> 212 273 <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> 213 274 </xs:sequence> … … 216 277 <xs:complexType name="locationType"> 217 278 <xs:annotation> 218 <xs:documentation> Location parameters of resource</xs:documentation>279 <xs:documentation>The location type describes placement of the computing resource in the 3D coordinate system</xs:documentation> 219 280 </xs:annotation> 220 281 <xs:sequence> … … 228 289 <xs:complexType name="parameterType"> 229 290 <xs:annotation> 230 <xs:documentation>Description of parameter of resource</xs:documentation> 291 <xs:documentation>Parameter of resource. Allows to define additional resource paramters. 292 Contains a list of parameter values or a list of key-value pairs. 293 Attribute : name - denotes paramter name</xs:documentation> 231 294 </xs:annotation> 232 295 <xs:choice> 233 296 <xs:element name="value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> 234 <xs:sequence minOccurs="0" maxOccurs="unbounded"> 235 <xs:element name="property"> 236 <xs:complexType> 237 <xs:sequence minOccurs="0" maxOccurs="unbounded"> 238 <xs:element name="value" type="xs:string"/> 239 </xs:sequence> 240 <xs:attribute name="name" type="xs:string" use="required"/> 241 </xs:complexType> 242 </xs:element> 297 <xs:sequence> 298 <xs:element name="property" minOccurs="0" maxOccurs="unbounded"> 299 <xs:complexType> 300 <xs:annotation> 301 <xs:documentation>Property of paramter. Allows to define additional properties of parameter as a list of values. 302 Attribute : name - denotes property name</xs:documentation> 303 </xs:annotation> 304 <xs:sequence> 305 <xs:element name="value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> 306 </xs:sequence> 307 <xs:attribute name="name" type="xs:string" use="required"/> 308 </xs:complexType> 309 </xs:element> 243 310 </xs:sequence> 244 311 </xs:choice> … … 253 320 <xs:sequence> 254 321 <xs:element name="description" type="xs:string" minOccurs="0" ></xs:element> 255 <xs:element name="timeEstimationPlugin" type="timeEstimationPluginType" minOccurs="0" maxOccurs="1"> 256 <xs:annotation> 257 <xs:documentation>Specifies which plugin is used to estimate task execution time</xs:documentation> 258 </xs:annotation> 259 </xs:element> 322 <xs:element name="timeEstimationPlugin" type="timeEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element> 260 323 <xs:element name="resources"> 261 324 <xs:annotation> … … 271 334 <xs:element name="templates" minOccurs="0"> 272 335 <xs:annotation> 273 <xs:documentation>Definition of computing resource templates that can/will be used in reso ce description section </xs:documentation>336 <xs:documentation>Definition of computing resource templates that can/will be used in resource description section </xs:documentation> 274 337 </xs:annotation> 275 338 <xs:complexType> 276 <xs:sequence maxOccurs="unbounded">277 <xs:element name="computingResourceTemplate" type="computingResourceTemplateType" />339 <xs:sequence> 340 <xs:element name="computingResourceTemplate" type="computingResourceTemplateType" maxOccurs="unbounded"/> 278 341 </xs:sequence> 279 342 </xs:complexType>
Note: See TracChangeset
for help on using the changeset viewer.
