[Nsi-wg] OpenNSA with NSI2 up at nsi.nordu.net

[Tomohiro Kudoh]

Hi Henrik,

When we issued a request from AIST/GL to OpenNSA, we got the following error for the
attached request.

----------------------------------------------------
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
       <SOAP-ENV:Fault>
           <faultcode>SOAP-ENV:Server</faultcode>
           <faultstring>STP localId (urn:ogf:network:nordu.net:2012:bi-ps) is not within specified network urn:ogf:network:nordu.net:2012:ets</faultstring>
       </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
----------------------------------------------------


Don't know this is related, but "VLAN" should be all upper cases according to:
https://forge.ogf.org/sf/go/doc16514?nav=1
so it should be: type="VLAN"

We request/accept upper cases only.

Tomohiro


On Wed, 9 Jan 2013 14:08:28 +0100 (CET)
Henrik Thostrup Jensen <htj at nordu.net> wrote:

> Hi
> 
> (since we don't have an NSI implementors list)
> 
> So, better late than never. But OpenNSA should support NSI2 more or less 
> now. I have an instance up and running for testing:
> 
> URL: http://nsi.nordu.net:9080/NSI/services/CS2
> Network: nordu.net:2012:ets
> 
> Ports:
> 
>    bi-ps
>    bi-nordu-netherlight
>    bi-nordu-uvalight
> 
> All ports should accept (and require) labels like this:
> 
> <labels>
>    <attribute targetNamespace="http://schemas.ogf.org/nml/2012/10/ethernet#" type="vlan">
>      <value>1782</value>
>    </attribute>
> </labels>
> 
> Though the targetNamespace might be optional. VLAN range 1780-1783 is 
> accepted. It is possible to specify candiates like source vlan 1781, 
> dest vlan 1780-1783 etc.
> 
> It isn't hooked up to any hardware just yet (TLS will also have to be 
> enabled for that).
> 
> If you have a client, feel free to give it a whirl. Please let me know of 
> any result, especially if something does not work.
> 
> 
> Known issues:
> 
> Query is not implemented (yet).
> 
> Aggregation does not work (path finding with labels not implemented yet).
> 
> No modify (don't expect this any time soon).
> 
> Request with label ranges will fail with cannot connect STP to itself if 
> port and ranges are the same (label support isn't quite implemented 
> everywhere yet).
> 
>      Best regards, Henrik
> 
>   Henrik Thostrup Jensen <htj at nordu.net>
>   Software Developer, NORDUnet
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nordureq.xml
Type: application/octet-stream
Size: 2908 bytes
Desc: not available
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20130111/a97f394b/attachment.obj>