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

Fwd: NSI meeting Wednesday morning (October 12th)
by Inder Monga 12 Oct '11

12 Oct '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: > > 1. NSI roadmap: agree on a roadmap for new NSI features, draft roadmap > here: > https://docs.google.com/spreadsheet/ccc?key=0ApTOJNVUoixhdF9UYWNBTGNWeWRkZG… > > 2. Review open issues, agree resolution and assign work: > http://code.google.com/p/ogf-nsi-project/issues/list > 3. Preparation for demo at SC11 > > See you tomorrow. > > Inder >

1 0

Request for developer for NSI visualisation software
by Radek Krzywania 07 Oct '11

07 Oct '11

Hi all, For SC demonstration there is a need to have a centralised tool which will be able to show global reservation state and visualise the NSI demo topology. The first draft of such application will be required in about 4 weeks for Future Internet Week event held in Poznan between 24-28 Oct, where pre-SC NSI demo will be shown. During my discussion with Jerry Sobieski, we would like to propose the following specification for this visualisation tool: - A simple WebService needs to be implemented at network managers, which will allow to register event listeners (a WS addresses in fact), which will be the visualisation tool - NSI enabled network managers will notify listeners on all events regarding reservations (mostly reservation status change according to NSI reservation lifecycle model) - A visualisation tool will have a WS interface to receive the notifications from all domains involved in the demo - A visualisation tool will be able to show global status on the screen, possibly a topology map. It would be good if a reservation paths could be shown (either delivered by NSI implementations or "guessed" by a tool having knowledge on involved domains) The way of showing a view is a subject to discuss, it can be either a web page or an standalone application. The details should be clarified soon, at the beginning of the next week. As developers who are already involved in coding the NSI and their network managers, it will be best to find someone else dedicated especially for visualiser task. Jerry and I will appreciate any volunteering developers here, so please if you feel being able to write a simple tool to support with a little graphical interface for NSI demos, please rise your hand. In case of any questions, feel free to ask on mailing list or directly to me or Jerry. Best regards Radek ________________________________________________________________________ Radoslaw Krzywania Network Research and Development Poznan Supercomputing and radek.krzywania(a)man.poznan.pl Networking Center +48 61 850 25 26 http://www.man.poznan.pl ________________________________________________________________________

7 11

Keep those
by Henrik Thostrup Jensen 07 Oct '11

07 Oct '11

Hi Please remember to keep your NSI agents running and well-taken care of so people can test their implementations against yours. Here is a short reservation test result: OpenNSA WS reservation test client Network: Aruba Reservation created. Connection ID: urn:uuid:bcfa9dda-ea7b-11e0-9905-00144f20a8d2 Network: Bonaire Callback for call urn:uuid:bd0924e0-ea7b-11e0-9905-00144f20a8d2/reservation from urn:ogf:network:nsa:Bonaire-OpenDRAC timed out. Network: Curacao Callback for call urn:uuid:c8f50fa8-ea7b-11e0-9905-00144f20a8d2/reservation from urn:ogf:network:nsa:Curacao-AutoBAHN timed out. Network: Dominica Callback for call urn:uuid:d4e0feee-ea7b-11e0-9905-00144f20a8d2/reservation from urn:ogf:network:nsa:Dominica-OSCARS timed out. Network: Grenada org.apache.cxf.binding.soap.SoapFault: Could not initialize class com.sun.xml.internal.ws.spi.ProviderImpl Network: Jamaica Reservation created. Connection ID: urn:uuid:e18453ee-ea7b-11e0-9905-00144f20a8d2 Network: Martinique Callback for call urn:uuid:e5561296-ea7b-11e0-9905-00144f20a8d2/reservation from urn:ogf:network:nsa:Martinique-DynamicKL timed out. Result: 2/7 succesfull registrations. Come on, we can do better :-). Best regards, Henrik Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.

2 8

10 issues changed in ogf-nsi-project
by ogf-nsi-project＠googlecode.com 05 Oct '11

05 Oct '11

Updates: Labels: FixedInVersion-1.SC Comment by imo...(a)gmail.com: (No comment was entered for this change.) Affected issues: issue 1: ConnectionStateType.TERMINATEING - maybe TERMINATING looks better http://code.google.com/p/ogf-nsi-project/issues/detail?id=1 issue 2: GenericAcknowledgmentType http://code.google.com/p/ogf-nsi-project/issues/detail?id=2 issue 7: change reservation name in WSDL http://code.google.com/p/ogf-nsi-project/issues/detail?id=7 issue 15: XML/WSDL name spaces documentation needed http://code.google.com/p/ogf-nsi-project/issues/detail?id=15 issue 23: "NsiExceptionType" change to "serviceException" http://code.google.com/p/ogf-nsi-project/issues/detail?id=23 issue 24: ServiceException needs further details http://code.google.com/p/ogf-nsi-project/issues/detail?id=24 issue 25: Change 'reservation' primitive to 'reserve' http://code.google.com/p/ogf-nsi-project/issues/detail?id=25 issue 29: clarify usage of providerNSA and requesterNSA http://code.google.com/p/ogf-nsi-project/issues/detail?id=29 issue 34: time zones - document usage http://code.google.com/p/ogf-nsi-project/issues/detail?id=34 issue 38: push/pop attributes from SOAP layer - documenation http://code.google.com/p/ogf-nsi-project/issues/detail?id=38 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 41 in ogf-nsi-project: Do we replace the replyTo field with a topology/NSA configuration lookup?
by ogf-nsi-project＠googlecode.com 05 Oct '11

05 Oct '11

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1 New issue 41 by jmacau...(a)gmail.com: Do we replace the replyTo field with a topology/NSA configuration lookup? http://code.google.com/p/ogf-nsi-project/issues/detail?id=41 Description of Issue: At the moment we get the requestor endpoint information using the replyTo field in the SOAP message payload. We are looking up the csProviderEndpoint in the topology so should we also look up the requestor endpoint in a similar fashion? If we do use an external mapping mechanism then which fields do we use to perform this mapping (requesterNSA)? Discussion of Issue: Resolution of Issue:

2 2

Re: [Nsi-wg] Issue 33 in ogf-nsi-project: getting WSDL from servers
by ogf-nsi-project＠googlecode.com 05 Oct '11

05 Oct '11

Comment #2 on issue 33 by jmacau...(a)gmail.com: getting WSDL from servers http://code.google.com/p/ogf-nsi-project/issues/detail?id=33 Best practices are to make the WSDL available for remote download, however, should we really rely on this given we can function without it?

1 0

Re: [Nsi-wg] Issue 32 in ogf-nsi-project: Interface version discovery
by ogf-nsi-project＠googlecode.com 05 Oct '11

05 Oct '11

Comment #1 on issue 32 by jmacau...(a)gmail.com: Interface version discovery http://code.google.com/p/ogf-nsi-project/issues/detail?id=32 Schema is already versioned. What we need is the ability to discover which versions are supported on an NSA.

1 0

NSI meeting Wednesday morning
by Inder Monga 05 Oct '11

05 Oct '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: 1. NSI roadmap: agree on a roadmap for new NSI features, draft roadmap here: https://docs.google.com/spreadsheet/ccc?key=0ApTOJNVUoixhdF9UYWNBTGNWeWRkZG… 2. Review open issues, agree resolution and assign work: http://code.google.com/p/ogf-nsi-project/issues/list 3. Preparation for demo at SC11 See you tomorrow. Inder

1 0

code.google email updates to list
by Guy Roberts 03 Oct '11

03 Oct '11

Hi All, F.y.i I have configured code.google.com/p/ogf-nsi-project to automatically send emails to the list when changes are made to the issues list. Guy -------------- -----Original Message----- From: nsi-wg-bounces(a)ogf.org [mailto:nsi-wg-bounces@ogf.org] On Behalf Of ogf-nsi-project(a)googlecode.com Sent: 03 October 2011 14:22 To: nsi-wg(a)ogf.org Subject: Re: [Nsi-wg] Issue 38 in ogf-nsi-project: push/pop attributes from SOAP layer - documenation Comment #3 on issue 38 by nsi....(a)gmail.com: push/pop attributes from SOAP layer - documenation http://code.google.com/p/ogf-nsi-project/issues/detail?id=38 Test comment added to this issue to see if email forwarding to the NSI working group mailing list is working. Guy Roberts _______________________________________________ nsi-wg mailing list nsi-wg(a)ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg

1 0

Re: [Nsi-wg] Issue 38 in ogf-nsi-project: push/pop attributes from SOAP layer - documenation
by ogf-nsi-project＠googlecode.com 03 Oct '11

03 Oct '11

Comment #3 on issue 38 by nsi....(a)gmail.com: push/pop attributes from SOAP layer - documenation http://code.google.com/p/ogf-nsi-project/issues/detail?id=38 Test comment added to this issue to see if email forwarding to the NSI working group mailing list is working. Guy Roberts

1 0