Context Navigation

← Previous Revision
Next Revision →
Normal
Revision Log

XSSimResSchema.xsd @ 464

Revision 464, 18.3 KB checked in by wojtekp, 13 years ago (diff)

Property svn:mime-type set to `text/plain`

Rev	Line
[234]	1	<?xml version="1.0" encoding="UTF-8"?>
	2	<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
	3	elementFormDefault="qualified" attributeFormDefault="unqualified">
[293]	4
[315]	5	<xs:complexType name="pluginType">
[293]	6	<xs:annotation>
[325]	7	<xs:documentation>Base plugin type.
[348]	8	Plugins allow configuring and adapting the simulation framework to his/her experiment
[325]	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>
[293]	11	</xs:annotation>
	12	<xs:sequence>
[296]	13	<xs:element name="name" type="xs:string"></xs:element>
[299]	14	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[293]	15	</xs:sequence>
	16	</xs:complexType>
[234]	17
[315]	18	<xs:complexType name="timeEstimationPluginType">
	19	<xs:annotation>
[348]	20	<xs:documentation>TimeEstimationPlugin derived from pluginType.
[325]	21	Time estimation plugin provides means to include specific application performance models during simulations
[348]	22	and allows introducing specific ways of calculating task execution time.</xs:documentation>
[315]	23	</xs:annotation>
	24	<xs:complexContent>
[325]	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>
[315]	31	</xs:complexContent>
	32	</xs:complexType>
[303]	33
[296]	34	<xs:complexType name="resourceType">
	35	<xs:annotation>
[325]	36	<xs:documentation>Base resource type.
	37	It allows to define simulation entities like computing resources, devices, schedulers.
[340]	38	Attributes: class - determines the component of the architecture i.e. rack, processor, memory, storage etc.
[325]	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>
[296]	42	</xs:annotation>
[299]	43	<xs:sequence>
[315]	44	<xs:element name="description" type="xs:string" minOccurs="0"></xs:element>
[299]	45	</xs:sequence>
[315]	46	<xs:attribute name="class" type="xs:string" use="required"/>
	47	<xs:attribute name="type" type="xs:string" use="optional"/>
[325]	48	<xs:attribute name="name" type="xs:ID" use="optional"/>
[293]	49	</xs:complexType>
	50
[298]	51	<xs:complexType name="computingResourceType">
[293]	52	<xs:annotation>
[348]	53	<xs:documentation> ComputingResource derived from resourceType
[325]	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>
[293]	61	</xs:annotation>
	62	<xs:complexContent>
[296]	63	<xs:extension base="resourceType">
[315]	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>
[317]	69	<xs:element name="profile" type="profileType" minOccurs="0" maxOccurs="1"></xs:element>
[325]	70	<xs:element name="location" type="locationType" minOccurs="0" maxOccurs="1"></xs:element>
	71	<xs:element name="computingResource" type="computingResourceType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[315]	72	</xs:sequence>
[325]	73	<xs:sequence>
	74	<xs:element name="templateId" type="xs:IDREF"/>
	75	<xs:element name="location" type="locationType" minOccurs="0" maxOccurs="1"></xs:element>
	76	</xs:sequence>
[315]	77	</xs:choice>
	78	</xs:sequence>
[299]	79	<xs:attribute name="groupId" type="xs:integer" use="optional"/>
[298]	80	<xs:attribute name="count" type="xs:integer" use="optional"/>
[293]	81	</xs:extension>
	82	</xs:complexContent>
	83	</xs:complexType>
	84
[298]	85	<xs:complexType name="computingResourceTemplateType">
[293]	86	<xs:annotation>
[348]	87	<xs:documentation>ComputingResourceTemplate derived from resourceType.
[340]	88	It allows user to define model of computing resource component that may constitute other computing resources
[325]	89	Computing resource templates can be then referred in computing resource definition</xs:documentation>
[293]	90	</xs:annotation>
	91	<xs:complexContent>
[298]	92	<xs:extension base="resourceType">
	93	<xs:sequence>
[299]	94	<xs:element name="resourceUnit" type="resourceUnitType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[312]	95	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[317]	96	<xs:element name="profile" type="profileType" minOccurs="0" maxOccurs="1"></xs:element>
[325]	97	<xs:element name="computingResource" type="computingResourceType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[293]	98	</xs:sequence>
	99	</xs:extension>
	100	</xs:complexContent>
	101	</xs:complexType>
	102
	103	<xs:complexType name="schedulerType">
	104	<xs:annotation>
[348]	105	<xs:documentation>Scheduler derived from resourceType.
[325]	106	It allows to model scheduling entity responsible for managing resources.</xs:documentation>
[293]	107	</xs:annotation>
	108	<xs:complexContent>
[296]	109	<xs:extension base="resourceType">
	110	<xs:sequence>
[293]	111	<xs:element name="schedulingPlugin" type="schedulingPluginType" minOccurs="0" maxOccurs="1"></xs:element>
[464]	112	<xs:element name="queue" type="queueType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[299]	113	<xs:choice minOccurs="1" maxOccurs="unbounded">
[293]	114	<xs:element name="scheduler" type="schedulerType"></xs:element>
[325]	115	<xs:element name="managedComputingResources" type="managedComputingResourcesType"></xs:element>
[293]	116	</xs:choice>
[299]	117	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[293]	118	</xs:sequence>
	119	</xs:extension>
	120	</xs:complexContent>
	121	</xs:complexType>
	122
	123	<xs:complexType name="schedulingPluginType">
	124	<xs:annotation>
[348]	125	<xs:documentation>SchedulingPlugin derived from pluginType.
	126	Scheduling plugins allow plugging scheduling algorithms into the simulated environment.
[325]	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>
[293]	129	</xs:annotation>
[315]	130	<xs:complexContent>
	131	<xs:extension base="pluginType">
	132	<xs:sequence>
[343]	133	<xs:element name="frequency" type="doubleValueWithUnitType" minOccurs="0" maxOccurs="1"></xs:element>
[315]	134	</xs:sequence>
	135	</xs:extension>
	136	</xs:complexContent>
[293]	137	</xs:complexType>
	138
[296]	139	<xs:complexType name="resourceUnitType">
[293]	140	<xs:annotation>
[340]	141	<xs:documentation>Resource unit is used to define non-computing resource like memory, storage etc.
[325]	142	Elements: amount - represents concrete amount (values) of specific resource unit</xs:documentation>
[293]	143	</xs:annotation>
	144	<xs:complexContent>
[296]	145	<xs:extension base="resourceType">
	146	<xs:sequence>
[343]	147	<xs:element name="amount" type="doubleValueWithUnitType"/>
[317]	148	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[296]	149	</xs:sequence>
[293]	150	</xs:extension>
	151	</xs:complexContent>
	152	</xs:complexType>
[325]	153
[343]	154	<xs:complexType name="doubleValueWithUnitType">
[325]	155	<xs:annotation>
[348]	156	<xs:documentation>DoubleValueWitUnit derived from double. Allows providing units in which the given value is expressed
	157	Attributes: unit - indicates appropriate units, for instance: seconds, watts, bytes etc. </xs:documentation>
[325]	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>
[293]	165
[343]	166	<xs:complexType name="stringValueWithUnitType">
	167	<xs:annotation>
[348]	168	<xs:documentation>StringValueWitUnit derived from string. Allows providing units in which the given value is expressed
	169	Attributes: unit - indicates appropriate units. </xs:documentation>
[343]	170	</xs:annotation>
	171	<xs:simpleContent>
	172	<xs:extension base="xs:string">
	173	<xs:attribute name="unit" type="xs:string" use="optional"/>
	174	</xs:extension>
	175	</xs:simpleContent>
	176	</xs:complexType>
	177
[464]	178	<xs:complexType name="queueType">
	179	<xs:annotation>
	180	<xs:documentation>Profile acts as a container for resource profiles: power and air throughput</xs:documentation>
	181	</xs:annotation>
	182	<xs:sequence>
	183	<xs:element name="name" type="xs:string"></xs:element>
	184	<xs:element name="priority" type="xs:int"></xs:element>
	185	<xs:element name="reservation" type="xs:boolean"></xs:element>
	186	</xs:sequence>
	187	</xs:complexType>
	188
[325]	189	<xs:complexType name="managedComputingResourcesType">
[293]	190	<xs:annotation>
[348]	191	<xs:documentation>ManagedComputingResource type specifies computing resources controlled by scheduler.
	192	They can be provided either by listing their names or listing the group ids which they belong to.
	193	Attributes: include - specifies whether the given resource layer (listed resources) can be allocated by the scheduler
	194	In other words, false (default) value indicates that scheduler maneges only the subcomponents of the listed resources;
[325]	195	true value determines that also listed resources will be under the control of the defined scheduler</xs:documentation>
[293]	196	</xs:annotation>
[325]	197	<xs:choice>
[339]	198	<xs:element name="resourceName" type="xs:string" minOccurs="1" maxOccurs="unbounded"></xs:element>
	199	<xs:element name="resourceGroupId" type="xs:string" minOccurs="1" maxOccurs="unbounded"></xs:element>
[325]	200	</xs:choice>
[310]	201	<xs:attribute name="include" type="xs:boolean" default="false"/>
[293]	202	</xs:complexType>
[234]	203
[293]	204	<xs:complexType name="energyEstimationPluginType">
[234]	205	<xs:annotation>
[348]	206	<xs:documentation>EnergyEstimationPlugin derived from pluginType.
	207	Energy estimation plugin is used to estimate energy consumption of the given computing resource.
	208	It has access to the detailed resource description including power and air throughput profiles
[332]	209	and application characteristics running on a given resource</xs:documentation>
[293]	210	</xs:annotation>
[315]	211	<xs:complexContent>
	212	<xs:extension base="pluginType"/>
	213	</xs:complexContent>
[293]	214	</xs:complexType>
	215
[317]	216	<xs:complexType name="profileType">
[293]	217	<xs:annotation>
[325]	218	<xs:documentation>Profile acts as a container for resource profiles: power and air throughput</xs:documentation>
[293]	219	</xs:annotation>
	220	<xs:sequence>
[317]	221	<xs:element name="powerProfile" type="powerProfileType" minOccurs="0"></xs:element>
	222	<xs:element name="airThroughputProfile" type="airThroughputProfileType" minOccurs="0"></xs:element>
[293]	223	</xs:sequence>
	224	</xs:complexType>
	225
[317]	226	<xs:complexType name="powerProfileType">
[296]	227	<xs:annotation>
[343]	228	<xs:documentation>Power profile provides energyEstimation plugin, powerStates and other power-related parameters definition</xs:documentation>
[296]	229	</xs:annotation>
[282]	230	<xs:sequence>
[354]	231	<xs:element name="energyEstimationPlugin" type="energyEstimationPluginType" minOccurs="0"></xs:element>
[317]	232	<xs:element name="powerStates" type="powerStatesType" minOccurs="0"></xs:element>
	233	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	234	</xs:sequence>
	235	</xs:complexType>
[234]	236
[282]	237	<xs:complexType name="powerStatesType">
[296]	238	<xs:annotation>
[340]	239	<xs:documentation>PowerState type act as a container for power states. It contains energy-related characteristics of the computing resource</xs:documentation>
[296]	240	</xs:annotation>
[325]	241	<xs:sequence>
	242	<xs:element name="powerState" type="powerStateType" minOccurs="1" maxOccurs="unbounded"></xs:element>
[296]	243	</xs:sequence>
[282]	244	</xs:complexType>
	245
	246	<xs:complexType name="powerStateType">
[296]	247	<xs:annotation>
[340]	248	<xs:documentation>Power state defines available (for computing resource) power states.
[325]	249	Elements: name - denotes name of the given power state
	250	powerUsage - defines power consumption in the given state
[357]	251	transition - specifies possible power states transitions from the given power state</xs:documentation>
[296]	252	</xs:annotation>
[282]	253	<xs:sequence>
	254	<xs:element name="name" type="xs:string"></xs:element>
[464]	255	<xs:element name="powerUsage" type="doubleValueWithUnitType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[325]	256	<xs:element name="transition" type="powerStatesTransitionType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[319]	257	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	258	</xs:sequence>
	259	</xs:complexType>
	260
[325]	261	<xs:complexType name="powerStatesTransitionType">
[296]	262	<xs:annotation>
[325]	263	<xs:documentation>Description of power states transtition
	264	Elements: to - denotes name of target power state
	265	powerUsage - defines transition cost in the form of power consumption
	266	time - specifies transition time</xs:documentation>
[296]	267	</xs:annotation>
[282]	268	<xs:sequence>
[293]	269	<xs:element name="to" type="xs:string"></xs:element>
[343]	270	<xs:element name="powerUsage" type="doubleValueWithUnitType"></xs:element>
	271	<xs:element name="time" type="doubleValueWithUnitType"></xs:element>
[319]	272	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	273	</xs:sequence>
	274	</xs:complexType>
	275
[343]	276	<xs:complexType name="airThroughputEstimationPluginType">
	277	<xs:annotation>
[348]	278	<xs:documentation>AirThroughputEstimationPlugin derived from pluginType.
[343]	279	Air Throughput plugin is used to estimate air flow value based on the defined air throughput states</xs:documentation>
	280	</xs:annotation>
	281	<xs:complexContent>
	282	<xs:extension base="pluginType"/>
	283	</xs:complexContent>
	284	</xs:complexType>
	285
[317]	286	<xs:complexType name="airThroughputProfileType">
[312]	287	<xs:annotation>
[343]	288	<xs:documentation>AirThrouhputProfile provides airThroughputEstimation plugin, airThroughputStates and other airThroughput-related parameters definition</xs:documentation>
[312]	289	</xs:annotation>
[325]	290	<xs:sequence>
[354]	291	<xs:element name="airThroughputEstimationPlugin" type="airThroughputEstimationPluginType" minOccurs="0"></xs:element>
	292	<xs:element name="airThroughputStates" type="airThroughputStatesType" minOccurs="0"></xs:element>
[343]	293	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
	294	</xs:sequence>
	295	</xs:complexType>
	296
[464]	297	<xs:complexType name="airThroughputStatesType">
[343]	298	<xs:annotation>
[347]	299	<xs:documentation>AirThroughputStates type act as a container for air throughput states.</xs:documentation>
[343]	300	</xs:annotation>
	301	<xs:sequence>
[325]	302	<xs:element name="airThroughputState" type="airThroughputStateType" minOccurs="1" maxOccurs="unbounded"></xs:element>
[315]	303	</xs:sequence>
	304	</xs:complexType>
	305
[319]	306	<xs:complexType name="airThroughputStateType">
[315]	307	<xs:annotation>
[325]	308	<xs:documentation>Air througput state provides means to define air flow level.
	309	It can represent, for instance, a fan working state</xs:documentation>
[315]	310	</xs:annotation>
[312]	311	<xs:sequence>
[317]	312	<xs:element name="name" type="xs:string"></xs:element>
[343]	313	<xs:element name="value" type="doubleValueWithUnitType"></xs:element>
	314	<xs:element name="powerUsage" type="doubleValueWithUnitType" minOccurs="0"></xs:element>
[319]	315	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[312]	316	</xs:sequence>
	317	</xs:complexType>
	318
[293]	319	<xs:complexType name="locationType">
[282]	320	<xs:annotation>
[353]	321	<xs:documentation>The location type describes placement of the computing resource using 3 coordinates</xs:documentation>
[282]	322	</xs:annotation>
	323	<xs:sequence>
[328]	324	<xs:element name="horizontal" type="xs:long"/>
[293]	325	<xs:element name="vertical" type="xs:long"/>
	326	<xs:element name="depth" type="xs:long"/>
[319]	327	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	328	</xs:sequence>
	329	</xs:complexType>
[296]	330
[299]	331	<xs:complexType name="parameterType">
[282]	332	<xs:annotation>
[340]	333	<xs:documentation>Parameter of resource. Allows defining additional resource parameters.
[325]	334	Contains a list of parameter values or a list of key-value pairs.
[340]	335	Attribute : name - denotes parameter name</xs:documentation>
[282]	336	</xs:annotation>
[317]	337	<xs:choice>
[343]	338	<xs:element name="value" type="stringValueWithUnitType" minOccurs="0" maxOccurs="unbounded"/>
[325]	339	<xs:sequence>
	340	<xs:element name="property" minOccurs="0" maxOccurs="unbounded">
	341	<xs:complexType>
	342	<xs:annotation>
[341]	343	<xs:documentation>Property of parameter. Allows defining additional properties of parameter as a list of values.
[325]	344	Attribute : name - denotes property name</xs:documentation>
	345	</xs:annotation>
	346	<xs:sequence>
[343]	347	<xs:element name="value" type="stringValueWithUnitType" minOccurs="0" maxOccurs="unbounded"/>
[325]	348	</xs:sequence>
	349	<xs:attribute name="name" type="xs:string" use="required"/>
	350	</xs:complexType>
	351	</xs:element>
[317]	352	</xs:sequence>
	353	</xs:choice>
[296]	354	<xs:attribute name="name" type="xs:string" use="required"/>
[282]	355	</xs:complexType>
	356
[234]	357	<xs:element name="environment">
	358	<xs:annotation>
[293]	359	<xs:documentation>Schema describing simulation environment</xs:documentation>
[234]	360	</xs:annotation>
	361	<xs:complexType>
	362	<xs:sequence>
[299]	363	<xs:element name="description" type="xs:string" minOccurs="0" ></xs:element>
[325]	364	<xs:element name="timeEstimationPlugin" type="timeEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element>
[234]	365	<xs:element name="resources">
	366	<xs:annotation>
	367	<xs:documentation>Description of resources</xs:documentation>
	368	</xs:annotation>
	369	<xs:complexType>
	370	<xs:sequence>
[327]	371	<xs:element name="description" type="xs:string" minOccurs="0" ></xs:element>
[293]	372	<xs:element name="computingResource" type="computingResourceType" maxOccurs="unbounded"/>
[296]	373	<xs:element name="scheduler" type="schedulerType" maxOccurs="unbounded"/>
[234]	374	</xs:sequence>
	375	</xs:complexType>
	376	</xs:element>
[293]	377	<xs:element name="templates" minOccurs="0">
	378	<xs:annotation>
[325]	379	<xs:documentation>Definition of computing resource templates that can/will be used in resource description section </xs:documentation>
[293]	380	</xs:annotation>
	381	<xs:complexType>
[325]	382	<xs:sequence>
[328]	383	<xs:element name="description" type="xs:string" minOccurs="0" ></xs:element>
[325]	384	<xs:element name="computingResourceTemplate" type="computingResourceTemplateType" maxOccurs="unbounded"/>
[293]	385	</xs:sequence>
	386	</xs:complexType>
	387	</xs:element>
[234]	388	</xs:sequence>
	389	</xs:complexType>
	390	</xs:element>
	391
	392	</xs:schema>

Note: See TracBrowser for help on using the repository browser.

Download in other formats:

Original Format