Peoples, Please find attached the latest revision of the WSDL and XSD files. There were a large number of changes incorporated based on the feedback from OGF 32, so please take some time to have a look through. The WSDL compiles, but I have not programatically verified the changes. Please let me know if I have missed or broken anything. John. Version 0.07 Changes to NSI WSDL specification Date: July 29, 2011 Author: John MacAuley Notes: These are changes requested at OGF 32 working group meeting. 1. Created a QueryFailedType to provide a specific type without revervation specific information. 2. Renamed transactionId to correlationId and added the correlationId to the SOAP output response (acknowledgement). 3. Changed globalReservationId to be xsd:anyURI and mandatory but permit it to be nillable. This will allow an OGF URN (reference artifact 6478 "Procedure for Registration of Sub-namespace Identifiers in the URN:OGF Hierarchy") to be used for compatibility with other external systems. 4. Restructured confirmed and failed parameters. 5. Renamed GenericResponseType to GenericAcknowledgmentType. 6. Renamed all WSDL output "Response" messages to "Acknowledgment". 7. Fixed type issue with ProvisionFailedRequestType. 8. Removed the versioning information from WSDL port type names and bindings. 9. Removed connectionState from generic confirmed and reservation confirmed message since the state should be implied. 10. NSA identifiers are now defined as xsd:anyURI to hold an OGF URN. 11. STP definition is now changed to be a xsd:anyURI to hold an OGF URN (urn:ogf:network:stp:<NSnetworkid>:<localid>). 12. Removed the query option in QueryFilterType for search based on connection state. 13. Renamed PathObjectType to PathType. 14. Removed NetworkIdType, LocalIdType, and ServiceTerminationPointGroup since no longer needed. 15. Renamed orderedStpList to stpList as requested since "List" implies "Ordered." 16. Modified the XSD definitions to do local imports and copied the needed external XSD locally to package with NSI definitions. 17. Lined up naming of operations in XSD with specification and associated types to help avoid type name conflicts (ReservationRequestType and QueryRequestType). 18. Simplified the interface portType definitions by defining a single acknowledgment message type for output. 19. Moved directionality of the service into the path object since this is an attribute of the path. 20. Moved path object out of service parameters to allow for different path definitions between the reservation request and the reservation response/query results. 21. Added DetailedReservationInfoType and DetailedPathType to allow for connection tree to be return in the reservation response and query response. This is the groundwork for implementation to provide more detailed connection information and recursive queries (future release). 22. Segmented service bindings into requestor and provider messages sets to help with code modularity and provided proper endpoint definition for RA and PA. This required restructuring of the interface file as well, and moving of the portType definitions into the service bindings. The NSI requestor SOAP endpoint "ConnectionServiceRequestor" contains definitions for: reservationConfirmed reservationFailed provisionConfirmed provisionFailed releaseConfirmed releaseFailed terminateConfirmed terminateFailed query queryConfirmed queryFailed forcedEnd The NSI provider SOAP endpoint "ConnectionServiceProvider" contains definitions for: reservation provision release terminate query queryConfirmed queryFailed Open Issues for after GLIF bake-off in Rio: 1. Need to add the security policies to the WSDL so we can sign the messages to validate authenticity. This will not impact the core schema but will impact the WSDL definitions. 2. Per conenction reservation user/security information in a query response. ---------------
Peoples, I ran a WS-I basic profile test today and found I introduced a non-compliance with my acknowledgment name changes in the output messages. I have corrected the issue in this updated version. Sorry for the additional churn, but it will have little to no impact on your code. John. On 2011-08-01, at 12:22 AM, John MacAuley wrote:
Peoples,
Please find attached the latest revision of the WSDL and XSD files. There were a large number of changes incorporated based on the feedback from OGF 32, so please take some time to have a look through. The WSDL compiles, but I have not programatically verified the changes. Please let me know if I have missed or broken anything.
John.
Version 0.07 Changes to NSI WSDL specification Date: July 29, 2011 Author: John MacAuley
Notes: These are changes requested at OGF 32 working group meeting.
1. Created a QueryFailedType to provide a specific type without revervation specific information. 2. Renamed transactionId to correlationId and added the correlationId to the SOAP output response (acknowledgement). 3. Changed globalReservationId to be xsd:anyURI and mandatory but permit it to be nillable. This will allow an OGF URN (reference artifact 6478 "Procedure for Registration of Sub-namespace Identifiers in the URN:OGF Hierarchy") to be used for compatibility with other external systems. 4. Restructured confirmed and failed parameters. 5. Renamed GenericResponseType to GenericAcknowledgmentType. 6. Renamed all WSDL output "Response" messages to "Acknowledgment". 7. Fixed type issue with ProvisionFailedRequestType. 8. Removed the versioning information from WSDL port type names and bindings. 9. Removed connectionState from generic confirmed and reservation confirmed message since the state should be implied. 10. NSA identifiers are now defined as xsd:anyURI to hold an OGF URN. 11. STP definition is now changed to be a xsd:anyURI to hold an OGF URN (urn:ogf:network:stp:<NSnetworkid>:<localid>). 12. Removed the query option in QueryFilterType for search based on connection state. 13. Renamed PathObjectType to PathType. 14. Removed NetworkIdType, LocalIdType, and ServiceTerminationPointGroup since no longer needed. 15. Renamed orderedStpList to stpList as requested since "List" implies "Ordered." 16. Modified the XSD definitions to do local imports and copied the needed external XSD locally to package with NSI definitions. 17. Lined up naming of operations in XSD with specification and associated types to help avoid type name conflicts (ReservationRequestType and QueryRequestType). 18. Simplified the interface portType definitions by defining a single acknowledgment message type for output. 19. Moved directionality of the service into the path object since this is an attribute of the path. 20. Moved path object out of service parameters to allow for different path definitions between the reservation request and the reservation response/query results. 21. Added DetailedReservationInfoType and DetailedPathType to allow for connection tree to be return in the reservation response and query response. This is the groundwork for implementation to provide more detailed connection information and recursive queries (future release). 22. Segmented service bindings into requestor and provider messages sets to help with code modularity and provided proper endpoint definition for RA and PA. This required restructuring of the interface file as well, and moving of the portType definitions into the service bindings.
The NSI requestor SOAP endpoint "ConnectionServiceRequestor" contains definitions for:
reservationConfirmed reservationFailed provisionConfirmed provisionFailed releaseConfirmed releaseFailed terminateConfirmed terminateFailed query queryConfirmed queryFailed forcedEnd
The NSI provider SOAP endpoint "ConnectionServiceProvider" contains definitions for:
reservation provision release terminate query queryConfirmed queryFailed
Open Issues for after GLIF bake-off in Rio: 1. Need to add the security policies to the WSDL so we can sign the messages to validate authenticity. This will not impact the core schema but will impact the WSDL definitions. 2. Per conenction reservation user/security information in a query response.
---------------
<ogf-nsi-connection-protocol-v0_07.zip>
Hi (Just got around to updating my WSDL yesterday to 0.09, and was a bit puzzled over a change in 0.07) On Mon, 1 Aug 2011, John MacAuley wrote:
22. Segmented service bindings into requestor and provider messages sets to help with code modularity and provided proper endpoint definition for RA and PA. This required restructuring of the interface file as well, and moving of the portType definitions into the service bindings.
Requester and provider are roles, not seperate implementations. An agent can be a provider for one request and requester in another request. Having different endpoints for these two just complicates matters. Now, I'm fairly sure I can hack up my web service stack into having the methods for the same endpoint/url, but this might not be a possibility for all stacks. Aside from that a most of the changes in 0.09 are quite nice :-) Best regards, Henrik Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.
Hi (Just got around to updating my WSDL yesterday to 0.09, and was a bit puzzled over a change in 0.07) On Mon, 1 Aug 2011, John MacAuley wrote:
22. Segmented service bindings into requestor and provider messages sets to help with code modularity and provided proper endpoint definition for RA and PA. This required restructuring of the interface file as well, and moving of the portType definitions into the service bindings.
Requester and provider are roles, not seperate implementations. An agent can be a provider for one request and requester in another request. Having different endpoints for these two just complicates matters. Now, I'm fairly sure I can hack up my web service stack into having the methods for the same endpoint/url, but this might not be a possibility for all stacks. Aside from that a most of the changes in 0.09 are quite nice :-) Best regards, Henrik Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.
Originally I had the same concerns since I was implementing it as one SOAP endpoint, however, the argument for the separation is reasonable. A few of implementations are physically separating the RA and PA functions into separate software modules. In addition, there are cases where people my only implement the RA or PA functions. Since the WSDL is an interface contact, it makes sense to expose only those messages supported by the SOAP endpoint. If an RA was compiled with the complete message set there could be confusion with what is supported if someone is doing WSDL discovery. For implementations like OpenDRAC that will implement both RA and PA I was going to also include the original service WSDL that contains both RA and PA definitions. In the end I did not since I can easily build this by merging the two before compiling. You can do something similar and only expose a single SOAP endpoint if desired. John. On 2011-08-16, at 4:42 AM, Henrik Thostrup Jensen wrote:
Hi
(Just got around to updating my WSDL yesterday to 0.09, and was a bit puzzled over a change in 0.07)
On Mon, 1 Aug 2011, John MacAuley wrote:
22. Segmented service bindings into requestor and provider messages sets to help with code modularity and provided proper endpoint definition for RA and PA. This required restructuring of the interface file as well, and moving of the portType definitions into the service bindings.
Requester and provider are roles, not seperate implementations. An agent can be a provider for one request and requester in another request. Having different endpoints for these two just complicates matters. Now, I'm fairly sure I can hack up my web service stack into having the methods for the same endpoint/url, but this might not be a possibility for all stacks.
Aside from that a most of the changes in 0.09 are quite nice :-)
Best regards, Henrik
Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility. _______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg
participants (3)
-
Henrik Thostrup Jensen -
Henrik Thostrup Jensen -
John MacAuley