December 2011 - Nsi-wg - lists.ogf.org

Re: [Nsi-wg] Issue 2 in ogf-nsi-project: GenericAcknowledgmentType
by ogf-nsi-project＠googlecode.com 12 Jan '12

12 Jan '12

Comment #11 on issue 2 by imo...(a)gmail.com: GenericAcknowledgmentType http://code.google.com/p/ogf-nsi-project/issues/detail?id=2 This was re-discussed on the Wed. call, with the following results: 1. Message transport layer takes care of ack retransmission in case of a packet loss. 2. Confirm/Fail message responses should be sent out without waiting on the receipt of the message ack. [comment on error recovery: if message transport layer is broken, say unidirectionally, the ack sending will eventually timeout and generate a message transport error that the NSA will need to handle] 3. From the receiving state machine perspective, receiving a confirm/fail message from a particular NSA should cancel out the need to receive an ACK. So the state machine should not only continue to process the confirm/fail message, but not gate on or wait for the ACK message. Hope this resolves this issue

1 2

ServiceException needs further details
by John MacAuley 04 Jan '12

04 Jan '12

Resend.... I have added some new errors I implemented as part of CS11. Please comment and add to the list. Guy would like to add an appendix in the CS protocol document. John. Peoples, I took and action to start the error handling discussion so that we, as a group, can document the error messages and behaviors. I would like to start it off with when an NSIServiceException is returned as a SOAP fault to a request, and when it is returned in a specific failed response message. OpenDRAC used the strategy of validating a “key” set of attributes in the request before returning an ACK response or SOAP fault. This gives OpenDRAC the opportunity to validate parameters needed to accept the message for processing, and possibly return the asynchronous failed message at a later time. Here is the list of parameters I will validate in a reservation message and return a SOAP fault if they are incorrect or missing. HTTP authentication – if you don’t have valid credentials you are rejected with an HTTP 40x message. correlationId - needed for any acknowledgment, confirmation, or failed message. Must be unique within the context of the providerNSA otherwise the request cannot be accepted. replyTo - we will send the confirmation, or failed message back to this location. We do not validate the contents of the endpoint, just that it exists. Reservation – if the reservation parameters are not present then we reject. requesterNSA and providerNSA – must be present and resolve to an NsNetwork in topology. Also, the providerNSA must be the NsNetwork OpenDRAC is managing or we reject the message. connectionId – this is used as the primary reference attribute for reservation state machines and must be present. If any of these fields are missing or invalid OpenDRAC will return a SOAP fault containing the NSIServiceException set to an appropriate error message. I typically fill in MISSING_PARAMETER - "SVC0001", "Invalid or missing parameter" for this generic case and specify attributes identifying the parameter in question. Here is a list of error messages currently implemented in OpenDRAC. The list continues to expand. I have kept the text generic with the specific error values being returned in the associated attribute list. We will also need to agree on the format of the message/errorId. MISSING_PARAMETER, "SVC0001", "Invalid or missing parameter" UNSUPPORTED_OPTION, "SVC0002", "Parameter provided contains an unsupported value which MUST be processed" ALREADY_EXISTS, "SVC0003", "Schedule already exists for connectionId" DOES_NOT_EXIST, "SVC0004", "Schedule does not exists for connectionId" MISSING_SECURITY, "SVC0005", "Invalid or missing user credentials" TOPOLOGY_RESOLUTION_STP, "SVC0006", "Could not resolve STP in Topology database" TOPOLOGY_RESOLUTION_STP_NSA, "SVC0007", "Could not resolve STP to managing NSA" PATH_COMPUTATION_NO_PATH, "SVC0008", "Path computation failed to resolve route for reservation" INVALID_STATE, "SVC0009", "Connection state machine is in invalid state for received message" INTERNAL_ERROR, "SVC0010", "An internal error has caused a message processing failure" INTERNAL_NRM_ERROR, "SVC0011", "An internal NRM error has caused a message processing failure" STP_ALREADY_IN_USE, "SVC0012", "Specified STP already in use" BANDWIDTH_NOT_AVAILABLE, "SVC0013", "Insufficent bandwidth available for reservation" Would people like to add to the list? Comments? John.

3 3

Endpoint update for northernlight
by Henrik Thostrup Jensen 02 Jan '12

02 Jan '12

Hi everyone (especially to the topology maintainer) Northernlight is now running TLS, and only TLS. Meaning no regular http requests will be accepted. Right now it should not perform any certificate verification, but that will come later. The endpoint for the northernlight is now running on port 9443, meaning that this is the URL for the nsa endpoint: http://orval.grid.aau.dk:9443/NSI/services/ConnectionService I realize this will break things. Both the TLS only, and the endpoint change (though that is just an topology update), but I think this is an important thing to push for. Of course Northernlight is an edge-node with no transits in the current topology to impact is minimal, but I hope to upgrade Starlight (which has a rather central place in the topology) sometime in January, so if you haven't started on TLS support, now is the chance :-). Have a nice christmas/holiday/work during the latter half of December. Best regards, Henrik Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.

1 1

NSI BOF tomorrow: 5:30 - 7:30 pm. Agenda!!!!
by Inder Monga 22 Dec '11

22 Dec '11

Hi All, We have been able to put an exciting agenda for the NSI BOF at Supercomputing. It is exciting to see seven interoperable software implementations - hear from the developers! The agenda is as follows: 5:30 - 5:45: Agenda and NSI Concepts introduction: Inder Monga 5:45 - 6:00: Automated GOLE Demonstrations with NSI: Jerry Sobieski 6:00 - 6:10: NSI Demonstration Live: Tomohiro Kudoh 6:10 - 6:20: CORONET and Need for Dynamic Networking: George Clapp 6:20 - 6:50: Panel with NSI Developers - Progress and Lessons Learnt Panelists: Henrik Jensen, Tomohiro Kudoh, Takahiro Miyamoto, Jeonghoon moon, Gerben van Malenstein, Evangelos Chaniotakis (more panelists still to be confirmed) The panel will consist of no slides but 1 minute summaries from all the panelists, followed by questions from the moderator and the audience. 6:50- 7:10: Topology Service - Looking forward: Jerry Sobieski and Jeroen Van de Ham (10 minutes each) 7:10 - 7:30: Open Mike for audience We look forward to your participation Thanks, Inder -- Inder Monga 510-486-6531 http://www.es.net Follow us on Twitter: ESnetUpdates/Twitter <http://bit.ly/bisCAd> Visit our blog: ESnetUpdates Blog <http://bit.ly/9lSTO3><http://bit.ly/d2Olql>

2 2

Topology Use-Case
by Jeroen van der Ham 22 Dec '11

22 Dec '11

Hello, One of my action points for the NSI meeting was to draft a use-case for topology descriptions. The goal is to have both proposals describe in detail the approach for topology description and how that would support pathfinding. My proposal is that both approaches outline the following: - Define a topology description for the Automated GOLE topology as was used during SC11 (10 networks, 4 VLANs, and their interconnections), diagram attached. - Describe how a pathfinding algorithm would consume the above-mentioned topologies, and then find path candidates from UvA to KRLight, and finally how to select one of the listed candidates in the following three scenarios: 1) none of the networks have VLAN retagging, 2) Only Netherlight supports VLAN retagging, 3) All network support VLAN retagging. - A *short* analysis of how complex this solution is for the topology. - A *short* analysis of how the solution would extend to multi-layer descriptions. The goal of these proposals is to inform the NSI group on the proposals, their complexity, and their future-proofness. I propose that we have a 3 page limit on the descriptions in order not to burden the rest of the group too much. Suggestions? Jeroen.

3 7

NSI CS document updated to v1.1
by Guy Roberts 21 Dec '11

21 Dec '11

I have updated the NSI connection service protocol document to reflect the WSDL and other v1.1 changes. This is available here: https://forge.ogf.org/sf/go/doc16045?nav=1 Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

1 0

Wednesday's NSI call
by Guy Roberts 19 Dec '11

19 Dec '11

Hi all, The following is dial-in information for Wednesday's NSI call, time: 7:00 PDT 10:00 EDT, 15:00 GMT, 16:00 CET, 24: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 topology * NSI Face-to-face confirmed for 14th-16th March in Oxford * Other issues Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

1 0

extended NSI face to face meeting at OGF34
by Guy Roberts 16 Dec '11

16 Dec '11

Hello NSI team, A meeting room has been arranged in Oxford for an extended NSI face-to-face meeting from 14th-16th March. This meeting is timed to fit straight after the regular OGF working group sessions. The agenda for this meeting is to agree the functionality for NSI version 2.0. I hope to see you there. Guy -----Original Message----- From: Alan Sill [mailto:alan.sill@ttu.edu] Sent: 16 December 2011 08:59 To: Guy Roberts Cc: Alan Sill Subject: Fwd: extended NSI meeting in Oxford FYI Begin forwarded message: > From: David Wallom <david.wallom(a)oerc.ox.ac.uk> > Subject: Re: extended NSI meeting in Oxford > Date: December 16, 2011 2:07:28 AM CST > To: "Sill, Alan" <alan.sill(a)ttu.edu> > > Room Is booked > > DW > -- > > ++++++++++++++++++++++++++++++++++++++++ > Dr David Wallom > Associate Director Innovation, Oxford eResearch Centre Technical > Director, UK NGS VP Communities, OGF > > Oxford eResearch Centre > 7 Keble Road > Oxford > OX1 3QG > UK > > Tel: +44 1865 610601 > ++++++++++++++++++++++++++++++++++++++++ > > > > > On 15/12/2011 10:17, "Sill, Alan" <alan.sill(a)ttu.edu> wrote: > >> >> David is checking on the extra day on the 16th. The rest falls in the >> interval of OGF34 already scheduled, and should be fine. >> >> Hope this helps, >> Alan >> >> >> On Dec 14, 2011, at 2:13 PM, "Sill, Alan" <alan.sill(a)ttu.edu> wrote: >> >>> Hi Guy, >>> >>> Thanks for the note. It's good to hear about the plans for the >>> extended meeting. >>> >>> I'll pass this on to David Wallom as our host for the Oxford >>> meeting, and I'm sure that Joel has taken note of this request also. >>> David and Joel, can we help arrange this? >>> >>> Alan >>> >>> On Dec 14, 2011, at 12:06 PM, Guy Roberts wrote: >>> >>>> Hi Alan, >>>> >>>> The NSI working group would like to hold an extended meeting in >>>> Oxford at OGF34. For this we would like a meeting room for a full >>>> 3 days in addition to the normal OGF meetings. This would most >>>> likely be on the 14th-16th March. >>>> >>>> I was wondering if you can help me arrange our own meeting room >>>> directly with Oxford e-Research Centre? Who is the contact person >>>> at Oxford e-Research Centre that I should discuss this with? >>>> >>>> Regards, >>>> Guy Roberts >>>> >>>> ___________________________________________________________________ >>>> __ >>>> >>>> ** Guy Roberts, PhD Network Engineering & Planning >>>> * * Tel: +44 (0)1223 371300 >>>> * * City House Direct: +44 (0)1223 371316 >>>> * 126-130 Hills Road Fax: +44 (0)1223 371371 >>>> * Cambridge >>>> * CB2 1PQ E-mail: guy.roberts(a)dante.net >>>> D A N T E United Kingdom WWW: http://www.dante.net >>>> ___________________________________________________________________ >>>> __ >>>> >>> >

1 0

NSI face-to-face meeting
by Guy Roberts 16 Dec '11

16 Dec '11

In today's NSI conf call we proposed holding the face-to-face meeting to discuss NSI v2.0 straight after OGF34 on the 14th-16th March in Oxford. I expect that the OGF meetings will be held on Monday and Tuesday (12th and 13th) and we would like to hold the face-to-face meeting on Wednesday through Friday (14th-16th). Could you please give me some feedback on whether this arrangement would be practical for you? Regards, Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

4 3

NSI conf call minutes
by Guy Roberts 15 Dec '11

15 Dec '11

The minutes from today's NSI conf call are available here.... http://forge.gridforum.org/sf/go/doc16369?nav=1 Please take time to review the action points. Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

1 0