1 | <?xml version="1.0"?> |
---|
2 | <definitions name="fedd" |
---|
3 | targetNamespace="http://www.isi.edu/faber/fedd_internal_messages" |
---|
4 | xmlns:tns="http://www.isi.edu/faber/fedd_internal_messages" |
---|
5 | xmlns:xsd1="http://www.isi.edu/faber/fedd_types" |
---|
6 | xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" |
---|
7 | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" |
---|
8 | xmlns="http://schemas.xmlsoap.org/wsdl/"> |
---|
9 | |
---|
10 | <!-- |
---|
11 | The message definitions are all simple embeddings of one of the types |
---|
12 | from fedd_types.xsd |
---|
13 | --> |
---|
14 | |
---|
15 | <message name="FaultMessage"> |
---|
16 | <part name="FaultBody" type="xsd1:faultType"/> |
---|
17 | </message> |
---|
18 | |
---|
19 | <message name="AllocateProjectRequestMessage"> |
---|
20 | <part name="AllocateProjectRequestBody" type="xsd1:projectAllocType"/> |
---|
21 | </message> |
---|
22 | |
---|
23 | <message name="AllocateProjectResponseMessage"> |
---|
24 | <part name="AllocateProjectResponseBody" |
---|
25 | type="xsd1:projectAllocResponseType"/> |
---|
26 | </message> |
---|
27 | |
---|
28 | <message name="StaticProjectRequestMessage"> |
---|
29 | <part name="StaticProjectRequestBody" type="xsd1:projectAllocType"/> |
---|
30 | </message> |
---|
31 | |
---|
32 | <message name="StaticProjectResponseMessage"> |
---|
33 | <part name="StaticProjectResponseBody" |
---|
34 | type="xsd1:projectAllocResponseType"/> |
---|
35 | </message> |
---|
36 | |
---|
37 | <message name="Ns2SplitRequestMessage"> |
---|
38 | <part name="Ns2SplitRequestBody" type="xsd1:ns2SplitRequestType"/> |
---|
39 | </message> |
---|
40 | |
---|
41 | <message name="Ns2SplitResponseMessage"> |
---|
42 | <part name="Ns2SplitResponseBody" type="xsd1:ns2SplitResponseType"/> |
---|
43 | </message> |
---|
44 | |
---|
45 | <portType name="feddInternalPortType"> |
---|
46 | <operation name="AllocateProject"> |
---|
47 | <documentation> |
---|
48 | This internal interface allows the part of a fedd running on a machine |
---|
49 | other than the boss node of the emulab in question to request creation |
---|
50 | of a dynamic project on the boss node. |
---|
51 | </documentation> |
---|
52 | <input message="tns:AllocateProjectRequestMessage"/> |
---|
53 | <output message="tns:AllocateProjectResponseMessage"/> |
---|
54 | <fault name="InternalFault" message="tns:FaultMessage"/> |
---|
55 | </operation> |
---|
56 | <operation name="StaticProject"> |
---|
57 | <documentation> |
---|
58 | This internal interface allows the part of a fedd running on a machine |
---|
59 | other than the boss node of the emulab in question to request |
---|
60 | modification of a static project. For example keys can be added or |
---|
61 | node access granted. |
---|
62 | </documentation> |
---|
63 | <input message="tns:StaticProjectRequestMessage"/> |
---|
64 | <output message="tns:StaticProjectResponseMessage"/> |
---|
65 | <fault name="InternalFault" message="tns:FaultMessage"/> |
---|
66 | </operation> |
---|
67 | <operation name="Ns2Split"> |
---|
68 | <documentation> |
---|
69 | This allows a fedd that does not have direct access to the modified ns |
---|
70 | parser that splits a CEDL description into federation data to access |
---|
71 | that functionality remotely. |
---|
72 | </documentation> |
---|
73 | <input message="tns:Ns2SplitRequestMessage"/> |
---|
74 | <output message="tns:Ns2SplitResponseMessage"/> |
---|
75 | <fault name="InternalFault" message="tns:FaultMessage"/> |
---|
76 | </operation> |
---|
77 | </portType> |
---|
78 | </definitions> |
---|