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

Issue 107 in ogf-nsi-project: Remove ogf_nsi_framework_types_v2_0.xsd dependencies from service specific schema.
by ogf-nsi-project＠googlecode.com 09 Sep '13

09 Sep '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 107 by jmacauley: Remove ogf_nsi_framework_types_v2_0.xsd dependencies from service specific schema. http://code.google.com/p/ogf-nsi-project/issues/detail?id=107 The only dependency the ogf_nsi_services_types_v2_0.xsd has on the ftypes namespace (ogf_nsi_framework_types_v2_0.xsd ) is for the "TypeValuePairListType" as seen below in the labels definition. There can be build issues when importing the WSDL through jax-ws and the services through jaxb compilers. Conflicting package names can result if the default namespace is used during compile for the package names. To fix this issue I would like to remove use of the ftypes namespace in the services types by replacing labels within the STP definition with something local to the ogf_nsi_services_types_v2_0.xsd file. -- 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

Issue 106 in ogf-nsi-project: Remove ftypes namespace from ogf_nsi_services_p2p_v2_0.xsd
by ogf-nsi-project＠googlecode.com 09 Sep '13

09 Sep '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 106 by jmacauley: Remove ftypes namespace from ogf_nsi_services_p2p_v2_0.xsd http://code.google.com/p/ogf-nsi-project/issues/detail?id=106 Remove ftypes namespace and import statement from ogf_nsi_services_p2p_v2_0.xsd as a hold over from when the STP definition was in the service schema. This is will be a backward compatible change and will not result in any impact to existing code. -- 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

Issue 105 in ogf-nsi-project: soapAction namespace needs to be updated to 2013/07
by ogf-nsi-project＠googlecode.com 09 Sep '13

09 Sep '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 105 by jmacauley: soapAction namespace needs to be updated to 2013/07 http://code.google.com/p/ogf-nsi-project/issues/detail?id=105 The soapAction parameter on all operations need to be updated to 2013/07 as it is still at 2013/04. soapAction="http://schemas.ogf.org/nsi/2013/04/connection/service/reserve" should be soapAction="http://schemas.ogf.org/nsi/2013/07/connection/service/reserve" -- 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

Alignment with NML and NML extensions for NSI
by John MacAuley 09 Sep '13

09 Sep '13

Peoples, As I go through the effort of integrating the NML topology files with path finding I am noticing some misalignments based on the different times at which parts of the specification where defined. If other people are finding the same consistency issue please communicate them. I would hope I am not the only one. In the NSI point-to-point service we have defined a label on an STP to be the following: <labels> <attribute targetNamespace="http://schemas.ogf.org/nml/2012/10/ethernet#" type="vlan"> <value>1782</value> </attribute> </labels> However, in NML they have defined a LabelGroupType for label ranges, and a LabelType for specific label specification. <nml:LabelGroup labeltype="http://schemas.ogf.org/nml/2012/10/ethernet#vlan">1780-1783</nml:LabelGroup> The NML also creates unique attribute names/types by combining namespace # attribute, whereas in NSI we have kept them separate requiring two fields (targetNamespace and type) to qualify the attribute name. We should probably normalize these two definitions. Comments? Also, just so we are all on the same page with respect to STPs and their mappings onto NML constructs… The STP networkId is populated with the Topology element identifier, while the STP localId is populated with either the BidirectionalPort element identifier for bidirectional connections, or the PortGroup Id for unidirectional connections. For example, using the netherlight A-GOLE file we would get: networkId = urn:ogf:network:netherlight.net:2013:topology localId = urn:ogf:network:netherlight.net:2013:bi-netherlight-geant Thanks, John

3 3

Cannot specify range of VLAN identifiers in EVTS service
by John MacAuley 09 Sep '13

09 Sep '13

When we moved from using the label field in the STP for specifying VLANs to the explicit VLAN element in the EVTS service element we lost the ability to specify an acceptable range of VLAN identifiers. Does anyone see an issue with this? Thanks, John

3 4

NML Ethernet namespace
by John MacAuley 06 Sep '13

06 Sep '13

Peoples, Can anyone point me to the XML definition for the NML namespace holding the Ethernet definitions? http://schemas.ogf.org/nml/2012/10/ethernet#vlan Thank you, John

1 0

ESnet OSCARS NSIv2 instance up
by Vangelis Chaniotakis 06 Sep '13

06 Sep '13

All, I am happy to announce that the development of the OSCARS NSI bridge is at a point where we are just about ready to start intensive interop testing and to package it for use outside ESnet. The entire lifecycle has been tested and works against the SURFnet web-based client / requester SOAP server, as well as our own Java CXF clients. It has been also tested to interoperate satisfactorily with the production OSCARS and the ESnet network. The ESnet instance is running v99 WSDLs at: https://oscars.es.net/ConnectionService?wsdl We are running this behind an SSL-enabled HTTP proxy. Clients wishing to access the service will need to trust the ESnet CA and certificate chain (easily obtained with a browser). If the SURFnet folks would be so kind as to configure their web requester to trust our cert chain, I will be able to use it for testing. Our NSA ID is: urn:ogf:network:nsa:es.net The STP ids we are supporting right now are: urn:ogf:network:es.net:2013:bi-es-startap urn:ogf:network:es.net:2013:bi-ps I would like to put these details in the Google doc but I don't have access to it. Can someone provide me with the link? Notes: - We only support reservations for EthernetVlanType service. - The serviceType we accept is "http://services.ogf.org/nsi/2013/07/descriptions/EVTS.A-GOLE" - Currently we do not support modifying existing reservations. This will be implemented probably within the next week. - Some parts of query() are still under development. - The instance is currently NOT contacting the production ESnet OSCARS, even though it is running on the same host. Rather it is configured to run against a simulated OSCARS where every request succeeds. - When contacting the actual production OSCARS, reservations will take about 30 seconds to move from RESERVE_CHECKING to RESERVE_HELD. Most other operations will be quick, but the dataplane status notification will take 15-90 seconds to arrive after a provision / release. We also will be creating an RPM to facilitate installation of the NSI bridge on existing OSCARS installation, and producing installation / configuration documentation. It should be a fairly easy package to deploy, configure, and run. -- Evangelos (Vangelis) Chaniotakis, ESnet Network Engineering Group 510 486 7155 / haniotak(a)es.net

1 0

DynamicKL NSI 2.0 is available(WSDL r99)
by 이경민 05 Sep '13

05 Sep '13

Hi all. dynamicKL is now running(NSI v2/WSDL r99). http://nsi2.kisti.re.kr/ConnectionServiceProvider STP information is as follows: urn:ogf:network:dj.test:2013:p0 ~ urn:ogf:network:dj.test:2013:p4 Could you try to connect to our web services? : ) Thank you! -------------------------------------------------------- Korea Institute of Science and Technology Information(KISTI) Networking Service Development Team Lee KyoungMin Mobile : 82+10-9958-8979 e-mail : tsoc(a)kisti.re.kr

1 0

minutes from today's NSI call
by Guy Roberts 04 Sep '13

04 Sep '13

Redmine is down at the moment, so here are the minutes attached. 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

XMLs
by John MacAuley 04 Sep '13

04 Sep '13

1 0