1 | <?xml version="1.0" encoding="UTF-8"?> |
---|
2 | <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" |
---|
3 | elementFormDefault="qualified" attributeFormDefault="unqualified"> |
---|
4 | |
---|
5 | <xs:complexType name="pluginType"> |
---|
6 | <xs:annotation> |
---|
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> |
---|
11 | </xs:annotation> |
---|
12 | <xs:sequence> |
---|
13 | <xs:element name="name" type="xs:string"></xs:element> |
---|
14 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
15 | </xs:sequence> |
---|
16 | </xs:complexType> |
---|
17 | |
---|
18 | <xs:complexType name="timeEstimationPluginType"> |
---|
19 | <xs:annotation> |
---|
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> |
---|
31 | </xs:complexContent> |
---|
32 | </xs:complexType> |
---|
33 | |
---|
34 | <xs:complexType name="resourceType"> |
---|
35 | <xs:annotation> |
---|
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> |
---|
42 | </xs:annotation> |
---|
43 | <xs:sequence> |
---|
44 | <xs:element name="description" type="xs:string" minOccurs="0"></xs:element> |
---|
45 | </xs:sequence> |
---|
46 | <xs:attribute name="class" type="xs:string" use="required"/> |
---|
47 | <xs:attribute name="type" type="xs:string" use="optional"/> |
---|
48 | <xs:attribute name="name" type="xs:ID" use="optional"/> |
---|
49 | </xs:complexType> |
---|
50 | |
---|
51 | <xs:complexType name="computingResourceType"> |
---|
52 | <xs:annotation> |
---|
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> |
---|
61 | </xs:annotation> |
---|
62 | <xs:complexContent> |
---|
63 | <xs:extension base="resourceType"> |
---|
64 | <xs:sequence> |
---|
65 | <xs:choice> |
---|
66 | <xs:sequence> |
---|
67 | <xs:element name="resourceUnit" type="resourceUnitType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
68 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
69 | <xs:element name="energyEstimationPlugin" type="energyEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element> |
---|
70 | <xs:element name="profile" type="profileType" minOccurs="0" maxOccurs="1"></xs:element> |
---|
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> |
---|
78 | </xs:choice> |
---|
79 | </xs:sequence> |
---|
80 | <xs:attribute name="groupId" type="xs:integer" use="optional"/> |
---|
81 | <xs:attribute name="count" type="xs:integer" use="optional"/> |
---|
82 | </xs:extension> |
---|
83 | </xs:complexContent> |
---|
84 | </xs:complexType> |
---|
85 | |
---|
86 | <xs:complexType name="computingResourceTemplateType"> |
---|
87 | <xs:annotation> |
---|
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> |
---|
91 | </xs:annotation> |
---|
92 | <xs:complexContent> |
---|
93 | <xs:extension base="resourceType"> |
---|
94 | <xs:sequence> |
---|
95 | <xs:element name="resourceUnit" type="resourceUnitType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
96 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
97 | <xs:element name="energyEstimationPlugin" type="energyEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element> |
---|
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> |
---|
100 | </xs:sequence> |
---|
101 | </xs:extension> |
---|
102 | </xs:complexContent> |
---|
103 | </xs:complexType> |
---|
104 | |
---|
105 | <xs:complexType name="schedulerType"> |
---|
106 | <xs:annotation> |
---|
107 | <xs:documentation>Scheduler derived from Resource. |
---|
108 | It allows to model scheduling entity responsible for managing resources.</xs:documentation> |
---|
109 | </xs:annotation> |
---|
110 | <xs:complexContent> |
---|
111 | <xs:extension base="resourceType"> |
---|
112 | <xs:sequence> |
---|
113 | <xs:element name="schedulingPlugin" type="schedulingPluginType" minOccurs="0" maxOccurs="1"></xs:element> |
---|
114 | <xs:choice minOccurs="1" maxOccurs="unbounded"> |
---|
115 | <xs:element name="scheduler" type="schedulerType"></xs:element> |
---|
116 | <xs:element name="managedComputingResources" type="managedComputingResourcesType"></xs:element> |
---|
117 | </xs:choice> |
---|
118 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
119 | </xs:sequence> |
---|
120 | </xs:extension> |
---|
121 | </xs:complexContent> |
---|
122 | </xs:complexType> |
---|
123 | |
---|
124 | <xs:complexType name="schedulingPluginType"> |
---|
125 | <xs:annotation> |
---|
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> |
---|
129 | </xs:annotation> |
---|
130 | <xs:complexContent> |
---|
131 | <xs:extension base="pluginType"> |
---|
132 | <xs:sequence> |
---|
133 | <xs:element name="frequency" type="valueWithUnitType" minOccurs="0" maxOccurs="1"></xs:element> |
---|
134 | </xs:sequence> |
---|
135 | </xs:extension> |
---|
136 | </xs:complexContent> |
---|
137 | </xs:complexType> |
---|
138 | |
---|
139 | <xs:complexType name="resourceUnitType"> |
---|
140 | <xs:annotation> |
---|
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> |
---|
143 | </xs:annotation> |
---|
144 | <xs:complexContent> |
---|
145 | <xs:extension base="resourceType"> |
---|
146 | <xs:sequence> |
---|
147 | <xs:element name="amount" type="valueWithUnitType"/> |
---|
148 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
149 | </xs:sequence> |
---|
150 | </xs:extension> |
---|
151 | </xs:complexContent> |
---|
152 | </xs:complexType> |
---|
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> |
---|
182 | <xs:attribute name="include" type="xs:boolean" default="false"/> |
---|
183 | </xs:complexType> |
---|
184 | |
---|
185 | <xs:complexType name="energyEstimationPluginType"> |
---|
186 | <xs:annotation> |
---|
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> |
---|
190 | </xs:annotation> |
---|
191 | <xs:complexContent> |
---|
192 | <xs:extension base="pluginType"/> |
---|
193 | </xs:complexContent> |
---|
194 | </xs:complexType> |
---|
195 | |
---|
196 | <xs:complexType name="profileType"> |
---|
197 | <xs:annotation> |
---|
198 | <xs:documentation>Profile acts as a container for resource profiles: power and air throughput</xs:documentation> |
---|
199 | </xs:annotation> |
---|
200 | <xs:sequence> |
---|
201 | <xs:element name="powerProfile" type="powerProfileType" minOccurs="0"></xs:element> |
---|
202 | <xs:element name="airThroughputProfile" type="airThroughputProfileType" minOccurs="0"></xs:element> |
---|
203 | </xs:sequence> |
---|
204 | </xs:complexType> |
---|
205 | |
---|
206 | <xs:complexType name="powerProfileType"> |
---|
207 | <xs:annotation> |
---|
208 | <xs:documentation>Power profile allows powerState and other power-related paremters definition</xs:documentation> |
---|
209 | </xs:annotation> |
---|
210 | <xs:sequence> |
---|
211 | <xs:element name="powerStates" type="powerStatesType" minOccurs="0"></xs:element> |
---|
212 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
213 | </xs:sequence> |
---|
214 | </xs:complexType> |
---|
215 | |
---|
216 | <xs:complexType name="powerStatesType"> |
---|
217 | <xs:annotation> |
---|
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> |
---|
222 | </xs:sequence> |
---|
223 | </xs:complexType> |
---|
224 | |
---|
225 | <xs:complexType name="powerStateType"> |
---|
226 | <xs:annotation> |
---|
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> |
---|
231 | </xs:annotation> |
---|
232 | <xs:sequence> |
---|
233 | <xs:element name="name" type="xs:string"></xs:element> |
---|
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> |
---|
246 | </xs:annotation> |
---|
247 | <xs:sequence> |
---|
248 | <xs:element name="to" type="xs:string"></xs:element> |
---|
249 | <xs:element name="powerUsage" type="valueWithUnitType"></xs:element> |
---|
250 | <xs:element name="time" type="valueWithUnitType"></xs:element> |
---|
251 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
252 | </xs:sequence> |
---|
253 | </xs:complexType> |
---|
254 | |
---|
255 | <xs:complexType name="airThroughputProfileType"> |
---|
256 | <xs:annotation> |
---|
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> |
---|
261 | </xs:sequence> |
---|
262 | </xs:complexType> |
---|
263 | |
---|
264 | <xs:complexType name="airThroughputStateType"> |
---|
265 | <xs:annotation> |
---|
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> |
---|
268 | </xs:annotation> |
---|
269 | <xs:sequence> |
---|
270 | <xs:element name="name" type="xs:string"></xs:element> |
---|
271 | <xs:element name="value" type="valueWithUnitType"></xs:element> |
---|
272 | <xs:element name="powerUsage" type="valueWithUnitType" minOccurs="0"></xs:element> |
---|
273 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
274 | </xs:sequence> |
---|
275 | </xs:complexType> |
---|
276 | |
---|
277 | <xs:complexType name="locationType"> |
---|
278 | <xs:annotation> |
---|
279 | <xs:documentation>The location type describes placement of the computing resource in the 3D coordinate system</xs:documentation> |
---|
280 | </xs:annotation> |
---|
281 | <xs:sequence> |
---|
282 | <xs:element name="horizontal" type="xs:long"/> |
---|
283 | <xs:element name="vertical" type="xs:long"/> |
---|
284 | <xs:element name="depth" type="xs:long"/> |
---|
285 | <xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element> |
---|
286 | </xs:sequence> |
---|
287 | </xs:complexType> |
---|
288 | |
---|
289 | <xs:complexType name="parameterType"> |
---|
290 | <xs:annotation> |
---|
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> |
---|
294 | </xs:annotation> |
---|
295 | <xs:choice> |
---|
296 | <xs:element name="value" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> |
---|
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> |
---|
310 | </xs:sequence> |
---|
311 | </xs:choice> |
---|
312 | <xs:attribute name="name" type="xs:string" use="required"/> |
---|
313 | </xs:complexType> |
---|
314 | |
---|
315 | <xs:element name="environment"> |
---|
316 | <xs:annotation> |
---|
317 | <xs:documentation>Schema describing simulation environment</xs:documentation> |
---|
318 | </xs:annotation> |
---|
319 | <xs:complexType> |
---|
320 | <xs:sequence> |
---|
321 | <xs:element name="description" type="xs:string" minOccurs="0" ></xs:element> |
---|
322 | <xs:element name="timeEstimationPlugin" type="timeEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element> |
---|
323 | <xs:element name="resources"> |
---|
324 | <xs:annotation> |
---|
325 | <xs:documentation>Description of resources</xs:documentation> |
---|
326 | </xs:annotation> |
---|
327 | <xs:complexType> |
---|
328 | <xs:sequence> |
---|
329 | <xs:element name="description" type="xs:string" minOccurs="0" ></xs:element> |
---|
330 | <xs:element name="computingResource" type="computingResourceType" maxOccurs="unbounded"/> |
---|
331 | <xs:element name="scheduler" type="schedulerType" maxOccurs="unbounded"/> |
---|
332 | </xs:sequence> |
---|
333 | </xs:complexType> |
---|
334 | </xs:element> |
---|
335 | <xs:element name="templates" minOccurs="0"> |
---|
336 | <xs:annotation> |
---|
337 | <xs:documentation>Definition of computing resource templates that can/will be used in resource description section </xs:documentation> |
---|
338 | </xs:annotation> |
---|
339 | <xs:complexType> |
---|
340 | <xs:sequence> |
---|
341 | <xs:element name="description" type="xs:string" minOccurs="0" ></xs:element> |
---|
342 | <xs:element name="computingResourceTemplate" type="computingResourceTemplateType" maxOccurs="unbounded"/> |
---|
343 | </xs:sequence> |
---|
344 | </xs:complexType> |
---|
345 | </xs:element> |
---|
346 | </xs:sequence> |
---|
347 | </xs:complexType> |
---|
348 | </xs:element> |
---|
349 | |
---|
350 | </xs:schema> |
---|