- Nsi-wg - lists.ogf.org

Re: [Nsi-wg] Open dynamicKL NSA
by jeonghoon moon 06 Sep '11

06 Sep '11

To Henrik Thostrup Jensen SyntaxError(Cause : ProviderNSA) was not generated by URN problem. This error was generated by the name space mismatch. I want to show you a query message from autoBahn that was recently dumped by our log system. You can find out that ns2 and ns6 name spaces are defined as attributes of the queryRequest element. <?xml version = "1.0" ?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:queryRequest xmlns:ns2=" http://schemas.ogf.org/nsi/2011/07/connection/interface" xmlns:ns3="http://www.w3.org/2001/04/xmlenc#" xmlns:ns4="http://www.w3.org/2000/09/xmldsig#" xmlns:ns5="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:ns6=" http://schemas.ogf.org/nsi/2011/07/connection/types"> <ns2:correlationId>9fa0a8ce-7d20-482a-8088-349d73c29d24</ns2:correlationId> <ns2:replyTo>http://hemp.man.poznan.pl:9080/nsi/ConnectionRequesterPort </ns2:replyTo> <ns6:query> <requesterNSA>urn:ogf:network:NSnetwork:Curacao</requesterNSA> <providerNSA>urn:ogf:network:NSnetwork:Bonaire</providerNSA> <operation>Summary</operation> <queryFilter /> </ns6:query> </ns2:queryRequest> </soap:Body> </soap:Envelope> The following is a reservationRequest message generated by dynamicKL, which has two name spaces defined as attributes of the reservationRequest element. <ns5:reservationRequest xmlns:ns2="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:ns3="http://www.w3.org/2001/04/xmlenc#" xmlns:ns4="http://www.w3.org/2000/09/xmldsig#" xmlns:ns5=" http://schemas.ogf.org/nsi/2011/07/connection/interface" xmlns:ns6=" http://schemas.ogf.org/nsi/2011/07/connection/types"> <ns5:correlationId>78729d97-8264-4a4b-ad53-8fec5ad529fb</ns5:correlationId> <ns5:replyTo> http://220.69.240.218:2000/kreonet/ConnectionServiceRequester</ns5:replyTo> <ns6:reservation> <requesterNSA>urn:ogf:network:NSnetwork:kreonet</requesterNSA> <providerNSA>urn:ogf:network:NSnetwork:dynamicKL</providerNSA> <reservation> In case of your message, ns1 is defined in the Envelope element. On the other hand, default name space(" http://schemas.ogf.org/nsi/2011/07/connection/types") is defined in the reservation element. Will you check out the usage of name spaces? <SOAP-ENV:Envelope xmlns:ns0="http://schemas.ogf.org/nsi/2011/07/connection/types" xmlns:ns1="http://schemas.ogf.org/nsi/2011/07/connection/interface" xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <ns2:Body> <ns1:reservationRequest> <ns1:correlationId>56561926991634759038257507539181676754</ns1:correlationId> <ns1:replyTo> http://orval.grid.aau.dk:7080/NSI/services/ConnectionService</ns1:replyTo> <reservation xmlns=" http://schemas.ogf.org/nsi/2011/07/connection/types"> <requesterNSA>urn:ogf:network:nsa:OpenNSA-testclient</requesterNSA> <providerNSA>urn:ogf:network:nsa:Martinique-DynamicKL</providerNSA> <reservation> Best regards, YoungWook Cha =================================== http://ngn.andong.ac.kr NGN Lab. Comp. Engineering Dept. Andong National University +82-10-2456-3237, +82-54-820-5714 =================================== ----- Original Message ----- From: "Henrik Thostrup Jensen" <htj(a)ndgf.org> To: "jeonghoon moon" <otello90(a)gmail.com> Cc: "Jerry Sobieski" <jerry(a)nordu.net>; "NSI Working Group" <nsi-wg(a)ogf.org>; "JongUk Kong" <jonguk.kong(a)gmail.com>; "???(YoungWook Cha)" < ywcha(a)andong.ac.kr>; "John MacAuley" <john.macauley(a)surfnet.nl> Sent: Monday, September 05, 2011 9:29 PM Subject: Re: [Nsi-wg] Open dynamicKL NSA > Hi again, sorry for the spamming :-) > > (cc'ing John, as he is the expert and the nsi-wg mailing list appears not > to be working currently). > > On Mon, 5 Sep 2011, Henrik Thostrup Jensen wrote: > >> This changes the error in the dynamicKL log to concern the providerNSA, most >> likely because I don't use the URN scheme (next on the todays todo list). > > I've updated my implementation to use the urn scheme, but I still get a > ProviderNSA syntax error from the log (unfortunately there isn't any more > information available). > > Here is the SOAP envelope: > > <SOAP-ENV:Envelope > xmlns:ns0="http://schemas.ogf.org/nsi/2011/07/connection/types" > xmlns:ns1="http://schemas.ogf.org/nsi/2011/07/connection/interface" > xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> > <SOAP-ENV:Header/> > <ns2:Body> > <ns1:reservationRequest> > <ns1:correlationId>56561926991634759038257507539181676754</ns1:correlationId> > <ns1:replyTo> http://orval.grid.aau.dk:7080/NSI/services/ConnectionService</ns1:replyTo> > <reservation xmlns=" http://schemas.ogf.org/nsi/2011/07/connection/types"> > <requesterNSA>urn:ogf:network:nsa:OpenNSA-testclient</requesterNSA> > <providerNSA>urn:ogf:network:nsa:Martinique-DynamicKL</providerNSA> > <reservation> > <globalReservationId>gid-7087</globalReservationId> > <description>Test Connection</description> > <connectionId>conn-199</connectionId> > <serviceParameters> > <schedule> > <startTime>2011-09-05T12:13:20Z</startTime> > <endTime>2011-09-05T12:15:20Z</endTime> > </schedule> > [snip] > (I still need to fix the correlationId) > > According to the schema, the type for NSAs is xsd:anyURI. I think > "urn:ogf:network:nsa:Martinique-DynamicKL" should be a valid URI, but > perhaps I am overlooking something. > > > Best regards, Henrik > > Henrik Thostrup Jensen <htj at ndgf.org> > NORDUnet / Nordic Data Grid Facility. > > > -- Jeonghoon Moon Supercomputing Center Dept.of Infrastructure Technology Development KISTI(Korea Institute of Science and Technology Information) Tel : +82-42-869-0578 Fax : +82-42-869-0589 H.P : +82-10-2534-6754 Skype : otello90 MSN : otellomoon(a)hotmail.com "Expect Great Things from God Attempt Great Things for God"

1 0

Open dynamicKL NSA
by jeonghoon moon 05 Sep '11

05 Sep '11

HI PlugFest Developers,**** We have just finished the first version of NSI web services. (dynamicKL in KISTI)** Our implementation supports reservation, provision, release, termination, and query messages.**** It can be reached at:**** http://220.69.219.228:8010/nsi/ConnectionServiceProvider**** ** ** We adopted the following URNs for NSA and STPs:**** - NSA: urn:ogf:network:NSnetwork:Martinique**** - STP1: urn:ogf:network:NSnetwork:Martinique:M1**** - STP4: urn:ogf:network:NSnetwork:Martinique:M4**** The log for our web services is available here:**** http://220.69.219.228:8080/dynamicKLInfo/dynamicKL.log**** ** ** Could you try to connect to our web services? **** ** ** Best regards. -- Jeonghoon Moon Supercomputing Center Dept.of Infrastructure Technology Development KISTI(Korea Institute of Science and Technology Information) Tel : +82-42-869-0578 Fax : +82-42-869-0589 H.P : +82-10-2534-6754 Skype : otello90 MSN : otellomoon(a)hotmail.com "Expect Great Things from God Attempt Great Things for God"

4 8

Rio Inter-Domain Topo Ring 1.1b
by Jerry Sobieski 02 Sep '11

02 Sep '11

Hi all- John found a bug in the topofile. Attached is the corrected topology v1.1b. - Corrected STP A3 to be: Aruba hasSTP A3 (instead of the reverse.) The other STPs look ok. - added contact URL for G-LAMBDA AIST. Jerry

1 0

a draft power point on Rio topology
by Jerry Sobieski 31 Aug '11

31 Aug '11

1 0

NSA Dev: JAX-WS generation
by John MacAuley 31 Aug '11

31 Aug '11

Implementors, Is anyone else generating their web services using JAX-WS? I generated this stub through netbeans and think the queryConfirmed and queryFailed methods are incorrect. Should these not being returning "GenericAcknowledgmentType" instead of void? Just want to make sure I have not missed anything. Thanks, John. @WebService(serviceName = "ConnectionServiceProvider", portName = "ConnectionServiceProviderPort", endpointInterface = "org.ogf.schemas.nsi._2011._07.connection.provider.ConnectionProviderPort", targetNamespace = "http://schemas.ogf.org/nsi/2011/07/connection/provider", wsdlLocation = "WEB-INF/wsdl/ConnectionServiceProvider/ogf_nsi_connection_provider_v1_0.wsdl") public class ConnectionServiceProvider { public org.ogf.schemas.nsi._2011._07.connection._interface.GenericAcknowledgmentType reservation(org.ogf.schemas.nsi._2011._07.connection._interface.ReservationRequestType parameters) throws org.ogf.schemas.nsi._2011._07.connection.provider.NSIServiceException { //TODO implement this method throw new UnsupportedOperationException("Not implemented yet."); } public org.ogf.schemas.nsi._2011._07.connection._interface.GenericAcknowledgmentType provision(org.ogf.schemas.nsi._2011._07.connection._interface.ProvisionRequestType parameters) throws org.ogf.schemas.nsi._2011._07.connection.provider.NSIServiceException { //TODO implement this method throw new UnsupportedOperationException("Not implemented yet."); } public org.ogf.schemas.nsi._2011._07.connection._interface.GenericAcknowledgmentType release(org.ogf.schemas.nsi._2011._07.connection._interface.ReleaseRequestType parameters) throws org.ogf.schemas.nsi._2011._07.connection.provider.NSIServiceException { //TODO implement this method throw new UnsupportedOperationException("Not implemented yet."); } public org.ogf.schemas.nsi._2011._07.connection._interface.GenericAcknowledgmentType terminate(org.ogf.schemas.nsi._2011._07.connection._interface.TerminateRequestType parameters) throws org.ogf.schemas.nsi._2011._07.connection.provider.NSIServiceException { //TODO implement this method throw new UnsupportedOperationException("Not implemented yet."); } public org.ogf.schemas.nsi._2011._07.connection._interface.GenericAcknowledgmentType query(org.ogf.schemas.nsi._2011._07.connection._interface.QueryRequestType parameters) throws org.ogf.schemas.nsi._2011._07.connection.provider.NSIServiceException { //TODO implement this method throw new UnsupportedOperationException("Not implemented yet."); } public void queryConfirmed(javax.xml.ws.Holder<java.lang.String> correlationId, org.ogf.schemas.nsi._2011._07.connection.types.QueryConfirmedType queryConfirmed) throws org.ogf.schemas.nsi._2011._07.connection.provider.NSIServiceException { //TODO implement this method throw new UnsupportedOperationException("Not implemented yet."); } public void queryFailed(javax.xml.ws.Holder<java.lang.String> correlationId, org.ogf.schemas.nsi._2011._07.connection.types.QueryFailedType queryFailed) throws org.ogf.schemas.nsi._2011._07.connection.provider.NSIServiceException { //TODO implement this method throw new UnsupportedOperationException("Not implemented yet."); } }

2 2

tomorrow's NSI call
by Guy Roberts 31 Aug '11

31 Aug '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 Plugfest preparation 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 _____________________________________________________________________

2 2

Topology updte
by Jerry Sobieski 31 Aug '11

31 Aug '11

Hi all - especially the NSI Rio Plugfest participants/developers... I have a new Plugfest Guide version 1.1 and the new Rio Ring topology OWL file. Key changes: - More participants (seven) - The topology specification model has changed: !!! -- It now has 3 new objects: "NSnetwork", "STP", and "NSA" objects. in addition to the previous Node, switchmatrix, and Port. -- The new objects correspond well to the NSI CS topology model. -- It separates inter-domain NSI objects, and intra-domain physical topology. See plugfest guide for more details. - The Challenge topologies have changed. -- All the challenges can use a single topology. (with a minor caveat I need to fix). -- Each NSA implementation will be assigned to a particular network in the "Rio Ring" topology. - The test runs are now variable depending upon which NSA is under test. -- The RA and PA NSAs vary and the selection of endpoints is based upon the test objectives and available NSAs. The reason we made these changes was to address the test matrix growth. Even though we have still an artificial data plane topology, we can use the real URLs to reach the NSAs where they are being developed. This means one topology file will (should) suffice for all the tests. But until/unless all NSAs are up and online, the testing will be limited. Please note that there are some edits I still need to complete after discussion today on the NSI call. Also, I still need the URL for the NSAs for OSCARS, G-Lambda(s), and DynamicKL. Thanks Jerry

1 0

NSA implementation addresses
by Jerry Sobieski 30 Aug '11

30 Aug '11

Hi NSI Developers- We now have a modified topology that supports the NSI concepts much better thanks to John Mac and Jeroen vdH. I am updating the topology files and will circulate them shortly. So that everyone understands the model, and has an example or two. We have now seven implementations that want to participate in the Plugfest. In order to simplify the testing, we have created a static configuration of NSI networks and NSA assignments: We have defined seven Networks interconnected at the data plane to form a simple ring. We have assigned one implementation to each Network to act as the NSA. ****--->* What I need from each implementation team is the URL for their test NSA's SOAP endpoint. Here is John Mac's example for OpenDRAC: <nsi:csProviderEndpointrdf:datatype="http://www.w3.org/2001/XMLSchema#anyURI">https://dracproxy01.surfnet.nl:8443/nsi/ConnectionServiceProvider</nsi:csProviderEndpoint> I will put these into the global Rio topology configuration so that the URL is associated with your assigned Network NSA. Then other NSAs can find you. You each will need to read the Global Rio Topology OWL file into your NSA so that your NSA knows what the rest of the world looks like. By using this more static NSA <--> Network assignment, we don't need to reconfigure the NSAs as much to run the tests. We will have to generalize the tests a bit, but I think this will be easier. More detailed info will be circulated shortly. But please forward this URL to me asap. THANKS! Jerry

1 0

NSI specific topology recommendation for plug fest.
by John MacAuley 30 Aug '11

30 Aug '11

Peoples, I think the existing detailed DTOX topology models we have been generating are excellent. I can definitely see how I will be able to incorporate this into future versions of OpenDRAC as a primary topology import mechanism, however, I do not think it is capturing the simplified concepts in NSI that are needed for the demo. I have been playing around with the example topologies trying to massage them into a form where I can learn not only the network and STP topologies, but the managing NSA topologies as well. I found that the existing DTOX topology is very good at the details of nodes, switch matrixes, and ports, but I had a hard time filtering down to the simple aspects. I also believe we will get into some trouble if we try to use the port class to model STP while also modeling physical ports. I am not sure if the DTOX schema can handle this aspect, as I could not find a describing schema. I spent time over the last couple of days discussing this with Jerry while we worked through the plug fest scenarios. He provided good feedback and pulled together the attached slide showing the concepts we are trying to capture. I also mocked up an example OWL file with an NSI topology specific name space, and introduced the NSI concepts of NSnetwork, STP, and NSA. These classes are used to model their simplified namesakes from the NSI CS protocol, and are not meant to replace the DTOX definitions, but augment them with our NSI specific concepts. We can consider the NSI topology elements an overlay on the existing DTOX elements, reusing data properties and including references to DTOX object instances. (I removed the DTOX object instances from the file to simplify the example). I think this will become much clearer when running NSI on out real networks and not this abstract topology for the demo. I have not yet validated the attached OWL so I apologize if it contains errors. The following classes and properties are introduced in the file… NSnetwork: We model a NSI network with the NSnetwork class. Example URN: urn:ogf:network:NSnetwork:Aruba Properties: · label - display name for the network. · canSwap - indicates VLAN Id interchange is supported in the network domain. · managedBy - the Network Services Agent managing this network. · hasSTP - a set of references to the inter-domain Service Termination Points that are within this network. · hasPart - a set of references to the DTOX Node NamedIndividual representing network elements within this network. NSA: We model a Network Services Agent with the NSA class. Example URN: urn:ogf:network:nsa:dracproxy01.surfnet.nl Properties: · label - display name for the NSA. · managing - indicates the network being managed by this NSA. · connectedTo - represents an NSA to which this NSA has a peering relationship. · dnsName - DNS name of the NSA. · csProviderEndpoint - the SOAP endpoint for this NSA's CS provider interface. · adminContact - administrative contact information for this NSA. STP: We model a logical Service Termination point with the STP class. Example URN: urn:ogf:network:stp:Aruba:Aiden Properties: · label - display name for this STP. · partOf - indicates the member network of this STP. · connectedTo - a topological link identifying the peer STP to which this STP is connected. · mapsTo - the logical STP represented by this object instance maps through to this physical entity (port, vlan, etx.) in DTOX. We will need to start up a discussion after the plug fest to address the issue of NSI topology needs. I believe these changes will do until then. Comments? Thank you, John.

3 16

Call for Papers - CFP- 3rd IEEE WORKSHOP on Network Infrastructure Services as part of Cloud Computing (NetCloud) --- Extended Deadline to 10th of September
by Bartosz Belter 29 Aug '11

29 Aug '11

[Apologies if you receive multiple copies of this message] New submitting Deadline for the NetCloud Workshop, September 10, 2011 *************************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--> Extended to September 10, 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