May 2013 - Nsi-wg - lists.ogf.org

Version 0 question
by John MacAuley 27 May '13

27 May '13

Peoples, I was closing off the WSDL documentation last night when I stumbled upon something I think we need to clarify. The agreement so far as I understand it is that when the initial reservation sequence is in progress any queries to of that schedule will return version 0 with no associated criteria. Here is the XSD segment in question (I have expanded the element group in line for readability): <xsd:complexType name="QuerySummaryResultType"> <xsd:sequence> <xsd:element name="connectionId" type="tns:ConnectionIdType" /> <xsd:element name="globalReservationId" type="tns:GlobalReservationIdType" minOccurs="0" /> <xsd:element name="description" type="xsd:string" minOccurs="0" /> <xsd:element name="criteria" type="tns:ReservationConfirmCriteriaType" minOccurs="0" maxOccurs="unbounded" /> <xsd:element name="requesterNSA" type="ftypes:NsaIdType" /> <xsd:element name="connectionStates" type="tns:ConnectionStatesType" /> <xsd:element name="children" type="tns:ChildSummaryListType" minOccurs="0" /> </xsd:sequence> </xsd:complexType> So in the case of a query of a version 0 reservation I have a bit of an issue based on the current structural layout: 1. The "criteria" element was made optional to allow for version 0 and no committed criteria. The version attribute is in the criteria element (see below), so it will not be available for version 0 in the current form. Are we okay with that? If we agree then when querying a version 0 reservation there will be no version number. <xsd:complexType name="ReservationConfirmCriteriaType"> <xsd:sequence> <xsd:element name="schedule" type="tns:ScheduleType" /> <xsd:element name="bandwidth" type="xsd:int" /> <xsd:element name="serviceAttributes" type="ftypes:TypeValuePairListType" /> <xsd:element name="path" type="tns:PathType" /> </xsd:sequence> <xsd:attribute name="version" type="xsd:int" use="required" /> </xsd:complexType> 2. The "connectionStates" element is not optional, however, there is an "unknown" state in each SM to allow for this initial undefined state. Are we okay with this as well? <xsd:complexType name="ConnectionStatesType"> <xsd:sequence> <xsd:element name="reservationState" type="tns:ReservationStateEnumType" /> <xsd:element name="provisionState" type="tns:ProvisionStateEnumType" /> <xsd:element name="lifecycleState" type="tns:LifecycleStateEnumType" /> <xsd:element name="dataPlaneStatus" type="tns:DataPlaneStatusType" /> </xsd:sequence> </xsd:complexType> 3. The "children" element that models the child NSA connections associated with this reservation would not be present for version 0, however, I only model the current version of the child connection information. Did we agree that this should be versioned as well and tracked for each reservation version made available? Finally, we will need to clearly document this somewhere in the core of the document. In the initial version 0 case we would have something like this (minimal): <reservation> <connectionId>connid-000001</connectionId> <requesterNSA>urn:ogf:network:netherlight.net:2012:nsa</requesterNSA> <connectionStates> <reservationState>ReserveHeld</reservationState> < provisionState>Unknown</provisionState > <lifecycleState>Unknown</lifecycleState> <dataPlaneStatus> <active>false</active> <version>0</version> <versionConsistent>true</versionConsistent > </dataPlaneStatus > </connectionStates> </reservation> Comments? John

2 3

NML Schema document
by Jeroen van der Ham 23 May '13

23 May '13

Hi, The public comments period for the NML base schema version has ended, unfortunately without any public comments. If you have read (parts of) the document, could you please let me know, or send a message to editor(a)ogf.org ? Even if it is just a "I have read this and I have no comments" message. Thanks, Jeroen.

1 0

More WSDL changes :-)
by Henrik Thostrup Jensen 23 May '13

23 May '13

Since, I know you love these emails ReserveResponseType can deleted and GenericConfirmedType be used instead. ReserveConfirmedType has a ReservationInfoGroup in it. This type includes an awful lot of data which is included in the initial reservation, but doesn't actually change, such as globalReservationId, description, schedule, bandwidth, and some of the stuff in the path type. This is static information which the client just send, there is no need to include it. AFAICT the only thing that is really needed here is the connectionId, sourceSTP, destSTP, and probably the ero if it was specified in the request. I realize this means a new type, but it is a lot of junk to send back. And symmetric -> symmetricPath :-). Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet

2 3

Re: [Nsi-wg] Topology Representation Schema
by Ahmed 22 May '13

22 May '13

Hi Jeroen, I just want to point out a small typo in the draft Network Service Interface Topology Representation. In page 7 section 3.2.2: has a typo in the relation NSA->managesy->Topolgy should be NSA->manages->Topology. -- -Ahmed

1 0

minutes from today's NSI conf call
by Guy Roberts 22 May '13

22 May '13

... are available here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6529 Here is a summary of the APs: AP1: John to update the document with all the WSDL changes agreed in this call and prepare a finalized document by Tuesday 23th May AP2: John to describe new query that would return a full list of previous errors. AP3: Chin to review the section 17 pseudo code text to make sure that concerns raised by Erik are addressed. AP4: Guy to update the error codes section of the CS protocol doc and add explanations requested by Erik. Guy _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0

When is it possible to provision a connection
by Henrik Thostrup Jensen 22 May '13

22 May '13

Hi With the statemachine in NSI2 it is not clear when it is possible to provision a connection. Is this possible: reserve - provision - reserveCommit Or does there need to be a committed version first? Can a provision happen during a modify? Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet

2 3

Re: [Nsi-wg] Issue 5 in ogf-nsi-project: Query on requester interface - is this needed?
by ogf-nsi-project＠googlecode.com 22 May '13

22 May '13

Comment #7 on issue 5 by imo...(a)gmail.com: Query on requester interface - is this needed? http://code.google.com/p/ogf-nsi-project/issues/detail?id=5 This discussion was not concluded, but I will capture the thoughts as were shared on the call: 1. Query as a separate WSDL was discussed, issue 22 has also been opened for this 2. The main use-case was monitoring or management agents that might not be NSAs. Unanswered questions are: a. Can query work if the entities querying are not NSA agents? b. Should query be a separate WSDL in any case? c. Which credentials - user credentials or peer relationships when walking the service tree? 3. There was support on the call for the need for query in both directions whether it be commercial networks or research networks scenario. This discussion was not deemed important for 1.0SC and resolution postponed till another date Inder

1 2

Issue 87 in ogf-nsi-project: Update WSDL with new state machine state names
by ogf-nsi-project＠googlecode.com 22 May '13

22 May '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 87 by jmacau...(a)gmail.com: Update WSDL with new state machine state names http://code.google.com/p/ogf-nsi-project/issues/detail?id=87 Remove "Initial" state from reservation state machine. Change "Reserved" state to "ReserveStart" in the reservation state machine. Change "Initial" state from lifecycle state machine to "Created". As agreed in weekly OGF NSI working group meeting on May 8th 2013. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

Wednesday's NSI conf call
by Guy Roberts 21 May '13

21 May '13

Hi all, The following is dial-in information for Wednesday's NSI call. Time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 23:00 JST 1. Dial Toll-Free Number: 866-740-1260 (U.S. & Canada) 2. International participants dial: Toll Number: 303-248-0285 Or International Toll-Free Number: http://www.readytalk.com/intl 3. Enter 7-digit access code 8937606, followed by "#" Agenda: -NSI documentation updates. -Meeting room arrangements Maastricht - questions from Surfnet NSI developers Guy _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

2 1

NSI v2 protocol documentation comments
by Erik Rozendaal 16 May '13

16 May '13

Hi, Thanks for the preview of the standard document. This was helpful with implementing the aggregator. We've read through the NSI v2 0.9 and 0.10 draft documentations and have a few questions/comments: In section 8.9 Reservation Versioning Information: "Version numbers of failed (e.g. timed-out) or aborted modifications are not stored, and therefore can be reused …" Is this special case really needed? Why not always require monotonically increasing version numbers? In section 4 NSI State Machines, on the PSM: "An instance of the PSM is created when an initial reservation is committed, and at that time it remains in the Released state." but in section 17.1.1 Processing of NSI the pseudo-code for NSI_rsv.rq creates the RSM, PSM, and LSM immediately and doesn't mention the initial state. In section 18.1 Message transport error handling a few errors are predefined. However, there are two errors with ID SVC0012. We're also missing an error code for the aggregator when one or more child providers return an error. In this case the requester should look at the childExceptions element of the ServiceExceptionType to find the root error. For now we added our own custom error: ID: SVC???? description: CHILD_ERROR text: One or more children reported an error. See the child exceptions for details. Finally, there is not much mention of the interaction between the various state machines. Can a requester still send Provision/Release requests when the LSM is already terminated? Is there any guiding principle or documentation we've missed? Regards, Erik

1 0