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
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@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@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg
Hello Tomohiro Thank you very much for testing. On Fri, 11 Jan 2013, Tomohiro Kudoh wrote:
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> ----------------------------------------------------
localId need to be prefixed with full network name, so try with localId like: urn:ogf:network:nordu.net:2012:ets:bi-ps (note the :ets) (On a side note, I find the duplication between network and localId to be somewhat unfortunate, and have added it to a document that I will send to the list sometime. I am also not sure why we use urn:ogf:network to denote a port).
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"
OK. I got mine from the NML spec (version, page 20). but it is just an example on the spec, nothing autorative. Not sure who wrote it, but I must say I find the document on the forge rather confusing. It makes references to "NML:Ethernet Port" and "NML:VLAN", neither which exists in the nml spec. Furthermore it uses both "NML:VLAN" (still does not exist) and "nmleth:vlan" to denote vlan, but without defining what nmleth is. The document also appears to completely miss the targetNamespace and mix namespace and type it together in label type.
We request/accept upper cases only.
OK. I don't really care about the cases, but it is clear that we don't have a clear schema or document describing these things. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
Hi, On 11 Jan 2013, at 00:48, Henrik Thostrup Jensen <htj@nordu.net> wrote:
OK. I got mine from the NML spec (version, page 20). but it is just an example on the spec, nothing autorative.
Not sure who wrote it, but I must say I find the document on the forge rather confusing. It makes references to "NML:Ethernet Port" and "NML:VLAN", neither which exists in the nml spec. Furthermore it uses both "NML:VLAN" (still does not exist) and "nmleth:vlan" to denote vlan, but without defining what nmleth is. The document also appears to completely miss the targetNamespace and mix namespace and type it together in label type.
We request/accept upper cases only.
OK. I don't really care about the cases, but it is clear that we don't have a clear schema or document describing these things.
Good point, I will take that as an action point to fix in the NML schema. We don't want to make the examples too complicated with the namespace declarations, they are listed in the appendix though. But perhaps we should include them anyway. Jeroen.
Hi, On 10 Jan 2013, at 20:59, Tomohiro Kudoh <t.kudoh@aist.go.jp> wrote:
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"
This is incorrectly taken from the NML standard. NML uses lowercase names for label names. The NML examples also use lowercase names for the namespaces. The NML standard will hopefully go into public comments this or next week so that we will have a more clear authorative source for these things. Jeroen.
participants (3)
-
Henrik Thostrup Jensen -
Jeroen van der Ham -
Tomohiro Kudoh