- Nsi-wg - lists.ogf.org

NSI issues document
by Guy Roberts 18 Jul '11

18 Jul '11

Attached is the summary of conclusions of the open issues relating to NSI version 1.0 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

2 additional NSI sessions at OGF32
by Guy Roberts 18 Jul '11

18 Jul '11

I have reserved the Alta room from 4pm through 7pm to give us time to complete the NSI discussions. 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 1

Updated NSI WSDL
by John MacAuley 16 Jul '11

16 Jul '11

NSI'ers, I have attached an updated set of WSDL and XSD files. There are still a few open items to solve before we can close on an official draft v1. Here is a list of changes and open questions. 1. Added generic OGF disclaimer to all files. 2. Namespace change based on GWD-C.083 http://www.ogf.org/documents/GFD.84.pdf http://schemas.ogf.org/nsi/2011/07/connection/types http://schemas.ogf.org/nsi/2011/07/connection/interface http://schemas.ogf.org/nsi/2011/07/connection/service 3. Shortened the default SOAP endpoint URL to https://localhost:8443/nsi/ConnectionService_v1_0. This is typically ignored by all compilers. 4. Modified port names and bindings in service definition to have versioning information (i.e. ConnectionService_v1_0). 5. On or about May 9th we discussed removing the replyTo fields from the interface specification and agreed to use the nsaAddress field to identify the SOAP endpoint. I did not make this change for two reasons: a) Jerry's request to keep the XSD file transport protocol free would be violated if we decided to stick a transport specific address in the field. Many of us had planned on using our NSA's URN within this field anyways. b) Jerry has requested we stop using nsaAddress and change it to a more abstract nsaId. This will allow us to keep the CS payload separate from the Web Services transport. 6. Added the forcedEnd notification needed as part of the new state machine. 7. Modified all security attributes to use the saml:attribute element as per Mary's security proposal. Now import http://docs.oasis-open.org/security/saml/v2.0/saml-schema-assertion-2.0.xsd. Created the SubjectAttributeSequenceType to hold these attributes. 8. Updated state machine states in ConnectionStateType. 9. Added ConnectionStateType to the GenericFailedType to relate current state machine. 10. Fixed a non UTF-8 character issue with a comment "STP’s". 11. Renamed techSpecAttrs in ServiceParametersType to serviceAttrs. 12. Renamed techSpecAttrs in ServiceTerminationPointType to stpSpecAttrs. Open Questions: 1. Should security attributes be removed from confirmed messages? 2. Do we need security attributes in the NsaType as well as the common message body? 3. Do we need to support a connectionId mapping to multiple child component connections for a single reservation? The Requestor NSA references a reservation using connectionId, however, this can map to multiple Provider NSA connectionId. Do we care about the children connection? At one point Jerry indicated he wanted a recursive query operation so that it pulls back all children connections down the tree as well. Currently, the WSDL assumes a summary model where the queried connectionId represents an aggregation of child states. 4. Can we change the connectionId to a URI and model as a globally unique Universally Unique Identifier (UUID) URN as per ITU-T Rec. X.667 | ISO/IEC 9834-8:2005 and IETF RFC 4122? 5. Do we make the renaming cosmetic change? Request a reservation: reserveRequest -> reservationRequest reserveConfirmed -> reservationConfirmed reserveFailed -> reservationFailed Terminate a reservation: cancelReservationRequest -> terminateReservationRequest cancelReservationConfirmed -> terminateReservationConfirmed cancelReservationFailed -> terminateReservationFailed State machine change Terminating (Canceling) – a terminateReservationRequest (cancelRequest) has been sent and a cancelation is ongoing John.

5 12

Fwd: [geysers-wp6] Call for Papers - CFP- 3rd IEEE WORKSHOP on Network Infrastructure Services as part of Cloud Computing (NetCloud)
by Joan A. Garcia-Espin 15 Jul '11

15 Jul '11

Hi all, Below, a CFP that may be of your interest. Sorry if you get multiple copies of it. Kind regards, -- Joan A. García-Espín DANA, Fundació i2CAT > > *************************CALL FOR > PAPERS*********************************** > > 3rd IEEE WORKSHOP on Network Infrastructure Services as part of > Cloud Computing (NetCloud) > Nov. 29- Dec. 1, 2011, Athens, Greece, http://2011.cloudcom.org/ > > Collocated with: > > 3rd IEEE International Conference on Cloud Computing technology and > Science (IEEE CloudCom 2011) > Nov. 29- Dec. 1, 2011, Athens, Greece, http://2011.cloudcom.org/ > > ****************************************************************** > Introduction > > The Cloud computing emerges as a new computing paradigm which aims > to provide secure and reliable, on demand QoS guaranteed computing > environments for the end-users. Cloud computing services usage in > both academia and industry, changed the way of thinking on how > users’ needs can be satisfied by computational infrastructures. > However, with the increase of data transferred among different > places, it became critical how to support distributed computing > resources with advanced network infrastructure services. It is > envisioned that network infrastructure services provisioned on- > demand could be managed and reconfigured dynamically by Cloud > operators and user applications to achieve optimal usage criteria. > Such dynamic infrastructures reveal new aspects in network > virtualization, service delivery automation and general > infrastructure resources management that should be supported by well- > defined information models and related middleware. New components of > the required netw > > ork infrastructure for Cloud services and applications should create > an integrated self-management environment that can react to changes > in workloads and other events with minimal human interference. > Security issues should addressed as a part of the general service > delivery framework/workflow and support both infrastructure > provisioning process and secure virtualised services/infrastructures > operation. > The workshop will discuss issues of optical network virtualisation > to create internal distributed datacenter network infrastructure and > provide dedicated inter-cloud network connectivity on-demand. > > Objective > > NetCloud, collocated with IEEE CloudCom 2011, attempts to address > the problem of how the underlying network infrastructure is capable > of supporting advanced cloud computing cases. The workshop is > intended to bring together network research community, commercial > network operators and industry with the major cloud computing > players, including IT specialists, researchers and commercial > providers. > Topics of Interest > > The workshop includes, but is not limited to the following topics: > > Dynamic infrastructure services for Clouds > Heterogeneous network architectures and frameworks for distributed > and high performance computing > Information modeling for combined network and IT resources > infrastructure services > New services provisioning/delivery models for multi-provider > business environment > Network virtualization technologies > Virtual networking and network services in Clouds > Network infrastructure provisioning and management as a part of > cloud computing workflows > Network interfaces for clouds > Performance and reliability issues > Service Level Agreement and QoS guarantees in the network layer > Dynamically provisioned security infrastructures (integration with > provider and customer legacy services and service provisioning > workflow, security policy definition, security context management) > End-to-end techniques for autonomic management of cloud resources > Policy based infrastructure services management > Experimental platforms that support network management in Cloud > computing > Experimentation testbeds and measurements studies > > Call for papers: > Papers describing original research on both theoretical and > practical aspects of dynamic network services for cloud computing > are solicited. > > *********************************************************** > Important Dates: > Paper Submissions: August 28, 2011 > Author’s Notification: September 21, 2011 > Camera-ready paper submission: October 1, 2011 > *********************************************************** > > > Paper submission instructions: > > This workshop will only accept for review original papers that have > not been previously published. Papers should be formatted based on > the IEEE Transactions journals and conferences style; maximum > allowed camera-ready paper length is six (6) pages. Submissions must > be in Adobe PDF format, including text, figures and references. > Accepted papers will be published in the CloudCom2011 proceedings, > for further information see IEEE CloudCom 2011 web page http://2011.cloudcom.org/ > . Review procedure All submitted paper will be reviewed by > international program committee. > > Workshop Organizers > > Mary Grammatikou, National Technical University of Athens, Greece > (mary (at) netmode.ntua.gr) > Bartosz Belter, Poznan Supercomputing and Networking Center, Poland > (bartosz.belter (at) man.poznan.pl) > > > Technical Program Committee > Ilias Baldine (RENCI, US) > John Baras (Maryland, US) > Thomas Michael Bohnert (SAP, Switzerland) > Graca Carvalho (Cisco, The Netherlands) > Nicola Ciulli (Nextworks, Italy) > Pasquale Donadio (Alcatel-Lucent Italy, Italy) > Yuri Demchenko (UvA, Netherlands) > Joan Antoni Garcia Espin (i2CAT, Spain) > Athanasios Liakopoulos (GRnet, Greece) > Diego R. Lopez (RedIRIS, Spain) > Norbert Meyer (PSNC, Poland) > David O'Callaghan (TCD, Ireland) > Max Ott (NICTA, Australia) > Symeon Papavassiliou (NTUA, Greece) > Anna Tzanakaki (AIT, Greece) > Pascale Vicat-Blanc (Lyatiss, France)

1 0

Feedback for WS protocol
by Henrik Thostrup Jensen 14 Jul '11

14 Jul '11

Hi everyone (I'm the NORDUnet developer creating the OpenNSA NSI implementation). (Also, please ignore a potential double post due to wrong sender email) I have some feedback/changes/wishes/questions for the WS-rendering of the NSI protocol. 1. Odd request/reply structure. The request/reply structure is somewhat odd. It seems that for every request there is an message to imply that the message itself has been received as well as the actual response, which also has a response. I.e., the interaction will look like this for a reservation (AFAICT) A -> B: reserveRequest A <- B: reserveResponse A <- B: reserveConfirmed A -> B: reserveConfirmedResponse This means that 4 messages are exchanged, when 2 would be enough. This is silly in my opinon, and only adds complexity to the implementation without adding any value. Also, at some point in time the reserveResponse and reserveConfirmed will get reordered as they don't have any ordering between them, meaning the requester will have to understand that case. It also seems to against the spec, which defines the primitives reserveRequest, reserveConfirmed, and reserveFailed. 2. Moving pathObject out of ServiceParameters I would very much like to move pathObject out of serviceParameters and into the top-level attributes. As a reservation is created the pathObject send around changes, where as the rest of the ServiceParameters does not. This also reflects itself in data structures where this becomes somewhat backwards to keep track of the path in aggregate connections. It is of course completely possible to keep the current structure, but it would simplify the implementation to move the path out of the service parameters. Also: Rename pathObject to path everywhere. We do not put the object suffix on other things either. Also(2): Rename OrderedStpListType to StpListType in spec. and protocol. A list is by definition ordered, otherwise it would be called a multiset or bag. 3. Protocol service parameters differ spec service parameters In the spec. schedule is in service parameters, in the WS protocol it is in the ReservationRequestType. I don't have any strong opions on where it should be, but I think it should be consistent. Somewhat similarly the spec. has guarenteed and preferred under serviceAttrs (which is under ServiceParameters). In the WS protocol guaranteed and preferred are directly under ServiceParameters. Again I don't have any strong opions on what is correct, but I think it should be consistent. 4. The transactionId The transactionId is not mentioned in the spec., but is used to denote session due to SOAPs lack of it. Could we call it something less misleading? It has nothing to do with transactions. E.g., sessionId, requestId (i prefer the latter as a session could technically consist of several requests). 5. Inconsistent path description The spec. introduces the notion of a service demarcation point as a pair of connected STPs. Could we introduce this type (essentially a tuple/struct/complextype with two STPs), and use it for describing paths, such that a path is a (sourceSTP, destSTP, SDPList). Best regards, Henrik Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.

3 5

NSI Connection Service protocol specification version 0.9
by Guy Roberts 14 Jul '11

14 Jul '11

Please find attached version 0.9 of the NSI connection service protocol. Guy PS gridforge is still down. _____________________________________________________________________ ** 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

tomorrow's NSI conf call
by Guy Roberts 13 Jul '11

13 Jul '11

Hi all, The following is dial-in information for tomorrow's NSI call: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CET, 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: * Review NSI CS protocol doc and make decision on freezing this document in preparation for NSI plugfest * Preparations for OGF32: presentations 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

updated NSI protocol doc
by Guy Roberts 09 Jul '11

09 Jul '11

Hi All, I have updated the NSI CS protocol document to reflect the current WSDL and current state machine discussion. I would like to fix this as version 0.9 for plug-fest development early next week in time for OGF32 at SLC. Could you please take a look and send be any comments you have by EoB Tuesday, and I will integrate comments ready SLC. Regards, Guy P.S. gridforge is playing up today- I will upload as soon as it is working again. _____________________________________________________________________ ** 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

minutes from today's NSI call
by Guy Roberts 07 Jul '11

07 Jul '11

The minutes from today's NSI call are available here: http://forge.gridforum.org/sf/go/doc16279?nav=1 _____________________________________________________________________ ** 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

updated state machine slide
by Tomohiro Kudoh 06 Jul '11

06 Jul '11

Here is updated state machine slide. Tomohiro

1 0