Context Navigation

XSSimResSchema.xsd @ 347

Revision 347, 17.8 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.
	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>
[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>
[325]	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>
[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>
[325]	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>
[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>
[325]	87	<xs:documentation>ComputingResourceTemplate derived from Resource.
[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>
[325]	105	<xs:documentation>Scheduler derived from Resource.
	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>
[299]	112	<xs:choice minOccurs="1" maxOccurs="unbounded">
[293]	113	<xs:element name="scheduler" type="schedulerType"></xs:element>
[325]	114	<xs:element name="managedComputingResources" type="managedComputingResourcesType"></xs:element>
[293]	115	</xs:choice>
[299]	116	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[293]	117	</xs:sequence>
	118	</xs:extension>
	119	</xs:complexContent>
	120	</xs:complexType>
	121
	122	<xs:complexType name="schedulingPluginType">
	123	<xs:annotation>
[325]	124	<xs:documentation>SchedulingPlugin derived from Plugin. Scheduling plugins allow plugging scheduling algorithms into the simulated environment.
	125	Elements: frequency - is used to enable scheduling periodically; it specifies the time interval (in seconds by default) between subsequent scheduling invocations
	126	</xs:documentation>
[293]	127	</xs:annotation>
[315]	128	<xs:complexContent>
	129	<xs:extension base="pluginType">
	130	<xs:sequence>
[343]	131	<xs:element name="frequency" type="doubleValueWithUnitType" minOccurs="0" maxOccurs="1"></xs:element>
[315]	132	</xs:sequence>
	133	</xs:extension>
	134	</xs:complexContent>
[293]	135	</xs:complexType>
	136
[296]	137	<xs:complexType name="resourceUnitType">
[293]	138	<xs:annotation>
[340]	139	<xs:documentation>Resource unit is used to define non-computing resource like memory, storage etc.
[325]	140	Elements: amount - represents concrete amount (values) of specific resource unit</xs:documentation>
[293]	141	</xs:annotation>
	142	<xs:complexContent>
[296]	143	<xs:extension base="resourceType">
	144	<xs:sequence>
[343]	145	<xs:element name="amount" type="doubleValueWithUnitType"/>
[317]	146	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[296]	147	</xs:sequence>
[293]	148	</xs:extension>
	149	</xs:complexContent>
	150	</xs:complexType>
[325]	151
[343]	152	<xs:complexType name="doubleValueWithUnitType">
[325]	153	<xs:annotation>
[343]	154	<xs:documentation>DoubleValueWitUnit derived from double. Allows providing units in which a given value is expressed
[325]	155	Attributes: unit - indicate appropriate units, for instance: seconds, watts, bytes etc. </xs:documentation>
	156	</xs:annotation>
	157	<xs:simpleContent>
	158	<xs:extension base="xs:double">
	159	<xs:attribute name="unit" type="xs:string" use="optional"/>
	160	</xs:extension>
	161	</xs:simpleContent>
	162	</xs:complexType>
[293]	163
[343]	164	<xs:complexType name="stringValueWithUnitType">
	165	<xs:annotation>
	166	<xs:documentation>StringValueWitUnit derived from string. Allows providing units in which a given value is expressed
	167	Attributes: unit - indicate appropriate units. </xs:documentation>
	168	</xs:annotation>
	169	<xs:simpleContent>
	170	<xs:extension base="xs:string">
	171	<xs:attribute name="unit" type="xs:string" use="optional"/>
	172	</xs:extension>
	173	</xs:simpleContent>
	174	</xs:complexType>
	175
[325]	176	<xs:complexType name="managedComputingResourcesType">
[293]	177	<xs:annotation>
[325]	178	<xs:documentation>ManagedComputingResource type specifies controlled (by scheduler) computing resources.
	179	They can be provided either by listing their names or listing the group ids for which they belong
[340]	180	Attributes: include - specifies whether scheduler should be built on top of given resources or should also include them.
	181	In other words, false (default) value indicates that scheduler manner only subcomponents of the listed resources;
[325]	182	true value determines that also listed resources will be under the control of the defined scheduler</xs:documentation>
[293]	183	</xs:annotation>
[325]	184	<xs:choice>
[339]	185	<xs:element name="resourceName" type="xs:string" minOccurs="1" maxOccurs="unbounded"></xs:element>
	186	<xs:element name="resourceGroupId" type="xs:string" minOccurs="1" maxOccurs="unbounded"></xs:element>
[325]	187	</xs:choice>
[310]	188	<xs:attribute name="include" type="xs:boolean" default="false"/>
[293]	189	</xs:complexType>
[234]	190
[293]	191	<xs:complexType name="energyEstimationPluginType">
[234]	192	<xs:annotation>
[325]	193	<xs:documentation>EnergyEstimationPlugin derived from Plugin.
	194	Energy estimation plugin is used to customize estimation of energy consumptions of the given computing resource
[332]	195	to specific applications and hardware. It has access to the detailed resource description including power and air throughput profiles
	196	and application characteristics running on a given resource</xs:documentation>
[293]	197	</xs:annotation>
[315]	198	<xs:complexContent>
	199	<xs:extension base="pluginType"/>
	200	</xs:complexContent>
[293]	201	</xs:complexType>
	202
[317]	203	<xs:complexType name="profileType">
[293]	204	<xs:annotation>
[325]	205	<xs:documentation>Profile acts as a container for resource profiles: power and air throughput</xs:documentation>
[293]	206	</xs:annotation>
	207	<xs:sequence>
[317]	208	<xs:element name="powerProfile" type="powerProfileType" minOccurs="0"></xs:element>
	209	<xs:element name="airThroughputProfile" type="airThroughputProfileType" minOccurs="0"></xs:element>
[293]	210	</xs:sequence>
	211	</xs:complexType>
	212
[317]	213	<xs:complexType name="powerProfileType">
[296]	214	<xs:annotation>
[343]	215	<xs:documentation>Power profile provides energyEstimation plugin, powerStates and other power-related parameters definition</xs:documentation>
[296]	216	</xs:annotation>
[282]	217	<xs:sequence>
[343]	218	<xs:element name="energyEstimationPlugin" type="energyEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element>
[317]	219	<xs:element name="powerStates" type="powerStatesType" minOccurs="0"></xs:element>
	220	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	221	</xs:sequence>
	222	</xs:complexType>
[234]	223
[282]	224	<xs:complexType name="powerStatesType">
[296]	225	<xs:annotation>
[340]	226	<xs:documentation>PowerState type act as a container for power states. It contains energy-related characteristics of the computing resource</xs:documentation>
[296]	227	</xs:annotation>
[325]	228	<xs:sequence>
	229	<xs:element name="powerState" type="powerStateType" minOccurs="1" maxOccurs="unbounded"></xs:element>
[296]	230	</xs:sequence>
[282]	231	</xs:complexType>
	232
	233	<xs:complexType name="powerStateType">
[296]	234	<xs:annotation>
[340]	235	<xs:documentation>Power state defines available (for computing resource) power states.
[325]	236	Elements: name - denotes name of the given power state
	237	powerUsage - defines power consumption in the given state
	238	transition - specifies possible power states transitions form the given power state</xs:documentation>
[296]	239	</xs:annotation>
[282]	240	<xs:sequence>
	241	<xs:element name="name" type="xs:string"></xs:element>
[343]	242	<xs:element name="powerUsage" type="doubleValueWithUnitType" minOccurs="0" maxOccurs="1"></xs:element>
[325]	243	<xs:element name="transition" type="powerStatesTransitionType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[319]	244	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	245	</xs:sequence>
	246	</xs:complexType>
	247
[325]	248	<xs:complexType name="powerStatesTransitionType">
[296]	249	<xs:annotation>
[325]	250	<xs:documentation>Description of power states transtition
	251	Elements: to - denotes name of target power state
	252	powerUsage - defines transition cost in the form of power consumption
	253	time - specifies transition time</xs:documentation>
[296]	254	</xs:annotation>
[282]	255	<xs:sequence>
[293]	256	<xs:element name="to" type="xs:string"></xs:element>
[343]	257	<xs:element name="powerUsage" type="doubleValueWithUnitType"></xs:element>
	258	<xs:element name="time" type="doubleValueWithUnitType"></xs:element>
[319]	259	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	260	</xs:sequence>
	261	</xs:complexType>
	262
[343]	263	<xs:complexType name="airThroughputEstimationPluginType">
	264	<xs:annotation>
	265	<xs:documentation>AirThroughputEstimationPlugin derived from Plugin.
	266	Air Throughput plugin is used to estimate air flow value based on the defined air throughput states</xs:documentation>
	267	</xs:annotation>
	268	<xs:complexContent>
	269	<xs:extension base="pluginType"/>
	270	</xs:complexContent>
	271	</xs:complexType>
	272
[317]	273	<xs:complexType name="airThroughputProfileType">
[312]	274	<xs:annotation>
[343]	275	<xs:documentation>AirThrouhputProfile provides airThroughputEstimation plugin, airThroughputStates and other airThroughput-related parameters definition</xs:documentation>
[312]	276	</xs:annotation>
[325]	277	<xs:sequence>
[343]	278	<xs:element name="airThroughputEstimationPlugin" type="airThroughputEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element>
	279	<xs:element name="airThroughputStates" type="airThroughputStatesType" minOccurs="1" maxOccurs="unbounded"></xs:element>
	280	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
	281	</xs:sequence>
	282	</xs:complexType>
	283
	284	<xs:complexType name="airThroughputStatesType">
	285	<xs:annotation>
[347]	286	<xs:documentation>AirThroughputStates type act as a container for air throughput states.</xs:documentation>
[343]	287	</xs:annotation>
	288	<xs:sequence>
[325]	289	<xs:element name="airThroughputState" type="airThroughputStateType" minOccurs="1" maxOccurs="unbounded"></xs:element>
[315]	290	</xs:sequence>
	291	</xs:complexType>
	292
[319]	293	<xs:complexType name="airThroughputStateType">
[315]	294	<xs:annotation>
[325]	295	<xs:documentation>Air througput state provides means to define air flow level.
	296	It can represent, for instance, a fan working state</xs:documentation>
[315]	297	</xs:annotation>
[312]	298	<xs:sequence>
[317]	299	<xs:element name="name" type="xs:string"></xs:element>
[343]	300	<xs:element name="value" type="doubleValueWithUnitType"></xs:element>
	301	<xs:element name="powerUsage" type="doubleValueWithUnitType" minOccurs="0"></xs:element>
[319]	302	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[312]	303	</xs:sequence>
	304	</xs:complexType>
	305
[293]	306	<xs:complexType name="locationType">
[282]	307	<xs:annotation>
[325]	308	<xs:documentation>The location type describes placement of the computing resource in the 3D coordinate system</xs:documentation>
[282]	309	</xs:annotation>
	310	<xs:sequence>
[328]	311	<xs:element name="horizontal" type="xs:long"/>
[293]	312	<xs:element name="vertical" type="xs:long"/>
	313	<xs:element name="depth" type="xs:long"/>
[319]	314	<xs:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"></xs:element>
[282]	315	</xs:sequence>
	316	</xs:complexType>
[296]	317
[299]	318	<xs:complexType name="parameterType">
[282]	319	<xs:annotation>
[340]	320	<xs:documentation>Parameter of resource. Allows defining additional resource parameters.
[325]	321	Contains a list of parameter values or a list of key-value pairs.
[340]	322	Attribute : name - denotes parameter name</xs:documentation>
[282]	323	</xs:annotation>
[317]	324	<xs:choice>
[343]	325	<xs:element name="value" type="stringValueWithUnitType" minOccurs="0" maxOccurs="unbounded"/>
[325]	326	<xs:sequence>
	327	<xs:element name="property" minOccurs="0" maxOccurs="unbounded">
	328	<xs:complexType>
	329	<xs:annotation>
[341]	330	<xs:documentation>Property of parameter. Allows defining additional properties of parameter as a list of values.
[325]	331	Attribute : name - denotes property name</xs:documentation>
	332	</xs:annotation>
	333	<xs:sequence>
[343]	334	<xs:element name="value" type="stringValueWithUnitType" minOccurs="0" maxOccurs="unbounded"/>
[325]	335	</xs:sequence>
	336	<xs:attribute name="name" type="xs:string" use="required"/>
	337	</xs:complexType>
	338	</xs:element>
[317]	339	</xs:sequence>
	340	</xs:choice>
[296]	341	<xs:attribute name="name" type="xs:string" use="required"/>
[282]	342	</xs:complexType>
	343
[234]	344	<xs:element name="environment">
	345	<xs:annotation>
[293]	346	<xs:documentation>Schema describing simulation environment</xs:documentation>
[234]	347	</xs:annotation>
	348	<xs:complexType>
	349	<xs:sequence>
[299]	350	<xs:element name="description" type="xs:string" minOccurs="0" ></xs:element>
[325]	351	<xs:element name="timeEstimationPlugin" type="timeEstimationPluginType" minOccurs="0" maxOccurs="1"></xs:element>
[234]	352	<xs:element name="resources">
	353	<xs:annotation>
	354	<xs:documentation>Description of resources</xs:documentation>
	355	</xs:annotation>
	356	<xs:complexType>
	357	<xs:sequence>
[327]	358	<xs:element name="description" type="xs:string" minOccurs="0" ></xs:element>
[293]	359	<xs:element name="computingResource" type="computingResourceType" maxOccurs="unbounded"/>
[296]	360	<xs:element name="scheduler" type="schedulerType" maxOccurs="unbounded"/>
[234]	361	</xs:sequence>
	362	</xs:complexType>
	363	</xs:element>
[293]	364	<xs:element name="templates" minOccurs="0">
	365	<xs:annotation>
[325]	366	<xs:documentation>Definition of computing resource templates that can/will be used in resource description section </xs:documentation>
[293]	367	</xs:annotation>
	368	<xs:complexType>
[325]	369	<xs:sequence>
[328]	370	<xs:element name="description" type="xs:string" minOccurs="0" ></xs:element>
[325]	371	<xs:element name="computingResourceTemplate" type="computingResourceTemplateType" maxOccurs="unbounded"/>
[293]	372	</xs:sequence>
	373	</xs:complexType>
	374	</xs:element>
[234]	375	</xs:sequence>
	376	</xs:complexType>
	377	</xs:element>
	378
	379	</xs:schema>

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

Download in other formats:

Original Format