Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emulab
emulab-devel
Commits
dd2289cb
Commit
dd2289cb
authored
Apr 07, 2011
by
Jonathon Duerig
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Regenerate xsd files for modified rspec.
parent
71d3fad5
Changes
20
Hide whitespace changes
Inline
Side-by-side
Showing
20 changed files
with
641 additions
and
93 deletions
+641
-93
protogeni/rspec/0.1/ad-common.xsd
protogeni/rspec/0.1/ad-common.xsd
+4
-0
protogeni/rspec/0.1/ad-top.xsd
protogeni/rspec/0.1/ad-top.xsd
+68
-3
protogeni/rspec/0.1/manifest-common.xsd
protogeni/rspec/0.1/manifest-common.xsd
+4
-0
protogeni/rspec/0.1/manifest-top.xsd
protogeni/rspec/0.1/manifest-top.xsd
+68
-3
protogeni/rspec/0.1/request-common.xsd
protogeni/rspec/0.1/request-common.xsd
+4
-0
protogeni/rspec/0.1/request-top.xsd
protogeni/rspec/0.1/request-top.xsd
+68
-3
protogeni/rspec/0.2/ad-common.xsd
protogeni/rspec/0.2/ad-common.xsd
+4
-0
protogeni/rspec/0.2/ad-top.xsd
protogeni/rspec/0.2/ad-top.xsd
+68
-3
protogeni/rspec/0.2/manifest-common.xsd
protogeni/rspec/0.2/manifest-common.xsd
+4
-0
protogeni/rspec/0.2/manifest-top.xsd
protogeni/rspec/0.2/manifest-top.xsd
+68
-3
protogeni/rspec/0.2/request-common.xsd
protogeni/rspec/0.2/request-common.xsd
+4
-0
protogeni/rspec/0.2/request-top.xsd
protogeni/rspec/0.2/request-top.xsd
+68
-3
protogeni/rspec/0.2/top.rnc
protogeni/rspec/0.2/top.rnc
+124
-0
protogeni/rspec/2/ad-common.xsd
protogeni/rspec/2/ad-common.xsd
+35
-24
protogeni/rspec/2/ad.xsd
protogeni/rspec/2/ad.xsd
+3
-17
protogeni/rspec/2/common.rnc
protogeni/rspec/2/common.rnc
+2
-2
protogeni/rspec/2/manifest-common.xsd
protogeni/rspec/2/manifest-common.xsd
+16
-14
protogeni/rspec/2/manifest-request.xsd
protogeni/rspec/2/manifest-request.xsd
+7
-2
protogeni/rspec/2/request-common.xsd
protogeni/rspec/2/request-common.xsd
+15
-14
protogeni/rspec/2/request.xsd
protogeni/rspec/2/request.xsd
+7
-2
No files found.
protogeni/rspec/0.1/ad-common.xsd
View file @
dd2289cb
...
...
@@ -102,6 +102,10 @@
</xs:simpleType>
</xs:element>
<xs:element
name=
"packet_loss"
>
<xs:annotation>
<xs:documentation>
Static packet loss probability of the link as a fraction
(ie. 0.01 == 1%)
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:float"
>
<xs:minInclusive
value=
"0.0"
/>
...
...
protogeni/rspec/0.1/ad-top.xsd
View file @
dd2289cb
...
...
@@ -25,6 +25,10 @@
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"type_slots"
use=
"required"
>
<xs:annotation>
<xs:documentation>
How many virtual nodes of this type this physical node can
handle.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union>
<xs:simpleType>
...
...
@@ -41,6 +45,14 @@
</xs:simpleType>
</xs:attribute>
<xs:attribute
name=
"static"
>
<xs:annotation>
<xs:documentation>
element unlimited { empty }?,
A flag that indicates that this physical node *always*
has this type - a node is only allowed to have one dynamic
(ie. not flagged as static) type at a time, but any number
of static types at a time
element static { empty }?
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -57,6 +69,15 @@
</xs:sequence>
</xs:complexType>
<xs:group
name=
"LinkTypeSpec"
>
<xs:annotation>
<xs:documentation>
Link types are currently just a siple string. They will almost certainly
have to get more complicated, for two reasons:
First, I want to allow virtual links to specify more than one type, so
that we can ask for links that are, say, 'ethernet or loopback'
Second, I want to have a lot more control over links that get mapped to
multi-hop paths
TODO: MAYBE this should be combined with NodeTypeSpec
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
name=
"link_type"
>
<xs:complexType>
...
...
@@ -66,6 +87,10 @@
</xs:sequence>
</xs:group>
<xs:group
name=
"LinkEndPoints"
>
<xs:annotation>
<xs:documentation>
A link has two endpoints. Right now, they are order
independent. But they might become order-dependant later.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:source_interface"
/>
<xs:element
ref=
"rspec:destination_interface"
/>
...
...
@@ -82,6 +107,11 @@
</xs:annotation>
</xs:element>
<xs:group
name=
"LinkCharacteristics"
>
<xs:annotation>
<xs:documentation>
Link characterstics which affect traffic.
TODO: In the future, the bandwidth, latency, and packet loss will be
moved to features and/or properties
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:bandwidth"
/>
<xs:element
ref=
"rspec:latency"
/>
...
...
@@ -90,9 +120,24 @@
</xs:group>
<xs:element
name=
"fd"
>
<xs:complexType>
<xs:attribute
name=
"fd_name"
use=
"required"
/>
<xs:attribute
name=
"fd_weight"
use=
"required"
/>
<xs:attribute
name=
"fd_name"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Name of this feature or desire
element fd_name { text },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"fd_weight"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Weight assocated with the feature or desire
element fd_weight { xsd:float },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"violatable"
>
<xs:annotation>
<xs:documentation>
A flag indicating whether or not a failure to match the desire with a
a feature is a constraint violation
element violatable { empty }?,
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -117,6 +162,11 @@
</xs:complexType>
</xs:element>
<xs:attributeGroup
name=
"GlobalSpec"
>
<xs:annotation>
<xs:documentation>
GlobalSpec = element global {
element operator { "OnceOnly" | "FirstFree" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"global_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -127,6 +177,12 @@
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup
name=
"LocalSpec"
>
<xs:annotation>
<xs:documentation>
LocalSpec = element local {
element operator { "+" }
attribute local_operator { "+" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"local_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -136,6 +192,10 @@
</xs:attribute>
</xs:attributeGroup>
<xs:complexType
name=
"InterfaceSpec"
>
<xs:annotation>
<xs:documentation>
Interfaces
InterfaceSpec = element interface { InterfaceContents }
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
minOccurs=
"0"
maxOccurs=
"unbounded"
ref=
"rspec:property"
/>
</xs:sequence>
...
...
@@ -195,7 +255,12 @@
<xs:documentation>
Name of this property
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_value"
type=
"xs:string"
/>
<xs:element
name=
"property_value"
type=
"xs:string"
>
<xs:annotation>
<xs:documentation>
Value associated with this property
TODO: Add ranges and other types from rspec
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_penalty"
>
<xs:annotation>
<xs:documentation>
The penalty associated with this property
</xs:documentation>
...
...
protogeni/rspec/0.1/manifest-common.xsd
View file @
dd2289cb
...
...
@@ -106,6 +106,10 @@
</xs:simpleType>
</xs:element>
<xs:element
name=
"packet_loss"
>
<xs:annotation>
<xs:documentation>
Static packet loss probability of the link as a fraction
(ie. 0.01 == 1%)
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:float"
>
<xs:minInclusive
value=
"0.0"
/>
...
...
protogeni/rspec/0.1/manifest-top.xsd
View file @
dd2289cb
...
...
@@ -25,6 +25,10 @@
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"type_slots"
use=
"required"
>
<xs:annotation>
<xs:documentation>
How many virtual nodes of this type this physical node can
handle.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union>
<xs:simpleType>
...
...
@@ -41,6 +45,14 @@
</xs:simpleType>
</xs:attribute>
<xs:attribute
name=
"static"
>
<xs:annotation>
<xs:documentation>
element unlimited { empty }?,
A flag that indicates that this physical node *always*
has this type - a node is only allowed to have one dynamic
(ie. not flagged as static) type at a time, but any number
of static types at a time
element static { empty }?
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -57,6 +69,15 @@
</xs:sequence>
</xs:complexType>
<xs:group
name=
"LinkTypeSpec"
>
<xs:annotation>
<xs:documentation>
Link types are currently just a siple string. They will almost certainly
have to get more complicated, for two reasons:
First, I want to allow virtual links to specify more than one type, so
that we can ask for links that are, say, 'ethernet or loopback'
Second, I want to have a lot more control over links that get mapped to
multi-hop paths
TODO: MAYBE this should be combined with NodeTypeSpec
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
name=
"link_type"
>
<xs:complexType>
...
...
@@ -66,6 +87,10 @@
</xs:sequence>
</xs:group>
<xs:group
name=
"LinkEndPoints"
>
<xs:annotation>
<xs:documentation>
A link has two endpoints. Right now, they are order
independent. But they might become order-dependant later.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:source_interface"
/>
<xs:element
ref=
"rspec:destination_interface"
/>
...
...
@@ -82,6 +107,11 @@
</xs:annotation>
</xs:element>
<xs:group
name=
"LinkCharacteristics"
>
<xs:annotation>
<xs:documentation>
Link characterstics which affect traffic.
TODO: In the future, the bandwidth, latency, and packet loss will be
moved to features and/or properties
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:bandwidth"
/>
<xs:element
ref=
"rspec:latency"
/>
...
...
@@ -90,9 +120,24 @@
</xs:group>
<xs:element
name=
"fd"
>
<xs:complexType>
<xs:attribute
name=
"fd_name"
use=
"required"
/>
<xs:attribute
name=
"fd_weight"
use=
"required"
/>
<xs:attribute
name=
"fd_name"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Name of this feature or desire
element fd_name { text },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"fd_weight"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Weight assocated with the feature or desire
element fd_weight { xsd:float },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"violatable"
>
<xs:annotation>
<xs:documentation>
A flag indicating whether or not a failure to match the desire with a
a feature is a constraint violation
element violatable { empty }?,
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -117,6 +162,11 @@
</xs:complexType>
</xs:element>
<xs:attributeGroup
name=
"GlobalSpec"
>
<xs:annotation>
<xs:documentation>
GlobalSpec = element global {
element operator { "OnceOnly" | "FirstFree" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"global_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -127,6 +177,12 @@
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup
name=
"LocalSpec"
>
<xs:annotation>
<xs:documentation>
LocalSpec = element local {
element operator { "+" }
attribute local_operator { "+" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"local_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -136,6 +192,10 @@
</xs:attribute>
</xs:attributeGroup>
<xs:complexType
name=
"InterfaceSpec"
>
<xs:annotation>
<xs:documentation>
Interfaces
InterfaceSpec = element interface { InterfaceContents }
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
minOccurs=
"0"
maxOccurs=
"unbounded"
ref=
"rspec:property"
/>
</xs:sequence>
...
...
@@ -195,7 +255,12 @@
<xs:documentation>
Name of this property
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_value"
type=
"xs:string"
/>
<xs:element
name=
"property_value"
type=
"xs:string"
>
<xs:annotation>
<xs:documentation>
Value associated with this property
TODO: Add ranges and other types from rspec
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_penalty"
>
<xs:annotation>
<xs:documentation>
The penalty associated with this property
</xs:documentation>
...
...
protogeni/rspec/0.1/request-common.xsd
View file @
dd2289cb
...
...
@@ -104,6 +104,10 @@
</xs:simpleType>
</xs:element>
<xs:element
name=
"packet_loss"
>
<xs:annotation>
<xs:documentation>
Static packet loss probability of the link as a fraction
(ie. 0.01 == 1%)
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:float"
>
<xs:minInclusive
value=
"0.0"
/>
...
...
protogeni/rspec/0.1/request-top.xsd
View file @
dd2289cb
...
...
@@ -25,6 +25,10 @@
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"type_slots"
use=
"required"
>
<xs:annotation>
<xs:documentation>
How many virtual nodes of this type this physical node can
handle.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union>
<xs:simpleType>
...
...
@@ -41,6 +45,14 @@
</xs:simpleType>
</xs:attribute>
<xs:attribute
name=
"static"
>
<xs:annotation>
<xs:documentation>
element unlimited { empty }?,
A flag that indicates that this physical node *always*
has this type - a node is only allowed to have one dynamic
(ie. not flagged as static) type at a time, but any number
of static types at a time
element static { empty }?
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -57,6 +69,15 @@
</xs:sequence>
</xs:complexType>
<xs:group
name=
"LinkTypeSpec"
>
<xs:annotation>
<xs:documentation>
Link types are currently just a siple string. They will almost certainly
have to get more complicated, for two reasons:
First, I want to allow virtual links to specify more than one type, so
that we can ask for links that are, say, 'ethernet or loopback'
Second, I want to have a lot more control over links that get mapped to
multi-hop paths
TODO: MAYBE this should be combined with NodeTypeSpec
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
name=
"link_type"
>
<xs:complexType>
...
...
@@ -66,6 +87,10 @@
</xs:sequence>
</xs:group>
<xs:group
name=
"LinkEndPoints"
>
<xs:annotation>
<xs:documentation>
A link has two endpoints. Right now, they are order
independent. But they might become order-dependant later.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:source_interface"
/>
<xs:element
ref=
"rspec:destination_interface"
/>
...
...
@@ -82,6 +107,11 @@
</xs:annotation>
</xs:element>
<xs:group
name=
"LinkCharacteristics"
>
<xs:annotation>
<xs:documentation>
Link characterstics which affect traffic.
TODO: In the future, the bandwidth, latency, and packet loss will be
moved to features and/or properties
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:bandwidth"
/>
<xs:element
ref=
"rspec:latency"
/>
...
...
@@ -90,9 +120,24 @@
</xs:group>
<xs:element
name=
"fd"
>
<xs:complexType>
<xs:attribute
name=
"fd_name"
use=
"required"
/>
<xs:attribute
name=
"fd_weight"
use=
"required"
/>
<xs:attribute
name=
"fd_name"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Name of this feature or desire
element fd_name { text },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"fd_weight"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Weight assocated with the feature or desire
element fd_weight { xsd:float },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"violatable"
>
<xs:annotation>
<xs:documentation>
A flag indicating whether or not a failure to match the desire with a
a feature is a constraint violation
element violatable { empty }?,
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -117,6 +162,11 @@
</xs:complexType>
</xs:element>
<xs:attributeGroup
name=
"GlobalSpec"
>
<xs:annotation>
<xs:documentation>
GlobalSpec = element global {
element operator { "OnceOnly" | "FirstFree" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"global_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -127,6 +177,12 @@
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup
name=
"LocalSpec"
>
<xs:annotation>
<xs:documentation>
LocalSpec = element local {
element operator { "+" }
attribute local_operator { "+" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"local_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -136,6 +192,10 @@
</xs:attribute>
</xs:attributeGroup>
<xs:complexType
name=
"InterfaceSpec"
>
<xs:annotation>
<xs:documentation>
Interfaces
InterfaceSpec = element interface { InterfaceContents }
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
minOccurs=
"0"
maxOccurs=
"unbounded"
ref=
"rspec:property"
/>
</xs:sequence>
...
...
@@ -195,7 +255,12 @@
<xs:documentation>
Name of this property
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_value"
type=
"xs:string"
/>
<xs:element
name=
"property_value"
type=
"xs:string"
>
<xs:annotation>
<xs:documentation>
Value associated with this property
TODO: Add ranges and other types from rspec
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_penalty"
>
<xs:annotation>
<xs:documentation>
The penalty associated with this property
</xs:documentation>
...
...
protogeni/rspec/0.2/ad-common.xsd
View file @
dd2289cb
...
...
@@ -90,6 +90,10 @@
</xs:simpleType>
</xs:element>
<xs:element
name=
"packet_loss"
>
<xs:annotation>
<xs:documentation>
Static packet loss probability of the link as a fraction
(ie. 0.01 == 1%)
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:float"
>
<xs:minInclusive
value=
"0.0"
/>
...
...
protogeni/rspec/0.2/ad-top.xsd
View file @
dd2289cb
...
...
@@ -25,6 +25,10 @@
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"type_slots"
use=
"required"
>
<xs:annotation>
<xs:documentation>
How many virtual nodes of this type this physical node can
handle.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union>
<xs:simpleType>
...
...
@@ -41,6 +45,14 @@
</xs:simpleType>
</xs:attribute>
<xs:attribute
name=
"static"
>
<xs:annotation>
<xs:documentation>
element unlimited { empty }?,
A flag that indicates that this physical node *always*
has this type - a node is only allowed to have one dynamic
(ie. not flagged as static) type at a time, but any number
of static types at a time
element static { empty }?
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -57,6 +69,15 @@
</xs:sequence>
</xs:complexType>
<xs:group
name=
"LinkTypeSpec"
>
<xs:annotation>
<xs:documentation>
Link types are currently just a siple string. They will almost certainly
have to get more complicated, for two reasons:
First, I want to allow virtual links to specify more than one type, so
that we can ask for links that are, say, 'ethernet or loopback'
Second, I want to have a lot more control over links that get mapped to
multi-hop paths
TODO: MAYBE this should be combined with NodeTypeSpec
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
name=
"link_type"
>
<xs:complexType>
...
...
@@ -66,6 +87,10 @@
</xs:sequence>
</xs:group>
<xs:group
name=
"LinkEndPoints"
>
<xs:annotation>
<xs:documentation>
A link has two endpoints. Right now, they are order
independent. But they might become order-dependant later.
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:source_interface"
/>
<xs:element
ref=
"rspec:destination_interface"
/>
...
...
@@ -82,6 +107,11 @@
</xs:annotation>
</xs:element>
<xs:group
name=
"LinkCharacteristics"
>
<xs:annotation>
<xs:documentation>
Link characterstics which affect traffic.
TODO: In the future, the bandwidth, latency, and packet loss will be
moved to features and/or properties
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
ref=
"rspec:bandwidth"
/>
<xs:element
ref=
"rspec:latency"
/>
...
...
@@ -90,9 +120,24 @@
</xs:group>
<xs:element
name=
"fd"
>
<xs:complexType>
<xs:attribute
name=
"fd_name"
use=
"required"
/>
<xs:attribute
name=
"fd_weight"
use=
"required"
/>
<xs:attribute
name=
"fd_name"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Name of this feature or desire
element fd_name { text },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"fd_weight"
use=
"required"
>
<xs:annotation>
<xs:documentation>
Weight assocated with the feature or desire
element fd_weight { xsd:float },
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"violatable"
>
<xs:annotation>
<xs:documentation>
A flag indicating whether or not a failure to match the desire with a
a feature is a constraint violation
element violatable { empty }?,
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -117,6 +162,11 @@
</xs:complexType>
</xs:element>
<xs:attributeGroup
name=
"GlobalSpec"
>
<xs:annotation>
<xs:documentation>
GlobalSpec = element global {
element operator { "OnceOnly" | "FirstFree" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"global_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -127,6 +177,12 @@
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup
name=
"LocalSpec"
>
<xs:annotation>
<xs:documentation>
LocalSpec = element local {
element operator { "+" }
attribute local_operator { "+" }
}
</xs:documentation>
</xs:annotation>
<xs:attribute
name=
"local_operator"
use=
"required"
>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
...
...
@@ -136,6 +192,10 @@
</xs:attribute>
</xs:attributeGroup>
<xs:complexType
name=
"InterfaceSpec"
>
<xs:annotation>
<xs:documentation>
Interfaces
InterfaceSpec = element interface { InterfaceContents }
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element
minOccurs=
"0"
maxOccurs=
"unbounded"
ref=
"rspec:property"
/>
</xs:sequence>
...
...
@@ -195,7 +255,12 @@
<xs:documentation>
Name of this property
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_value"
type=
"xs:string"
/>
<xs:element
name=
"property_value"
type=
"xs:string"
>
<xs:annotation>
<xs:documentation>
Value associated with this property
TODO: Add ranges and other types from rspec
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element
name=
"property_penalty"
>
<xs:annotation>
<xs:documentation>
The penalty associated with this property
</xs:documentation>
...
...
protogeni/rspec/0.2/manifest-common.xsd
View file @
dd2289cb
...
...
@@ -95,6 +95,10 @@
</xs:simpleType>
</xs:element>
<xs:element
name=
"packet_loss"
>
<xs:annotation>
<xs:documentation>
Static packet loss probability of the link as a fraction
(ie. 0.01 == 1%)
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:float"
>
<xs:minInclusive
value=
"0.0"
/>
...
...
protogeni/rspec/0.2/manifest-top.xsd
View file @
dd2289cb
...
...
@@ -25,6 +25,10 @@
</xs:annotation>
</xs:attribute>
<xs:attribute
name=
"type_slots"
use=
"required"
>
<xs:annotation>
<xs:documentation>
How many virtual nodes of this type this physical node can
handle.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union>
<xs:simpleType>
...
...
@@ -41,6 +45,14 @@
</xs:simpleType>
</xs:attribute>
<xs:attribute
name=
"static"
>
<xs:annotation>
<xs:documentation>
element unlimited { empty }?,
A flag that indicates that this physical node *always*
has this type - a node is only allowed to have one dynamic
(ie. not flagged as static) type at a time, but any number
of static types at a time
element static { empty }?
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction
base=
"xs:token"
>
<xs:enumeration
value=
"true"
/>
...
...
@@ -57,6 +69,15 @@
</xs:sequence>