... quick update (just to be as close as possible to MDM RRD MA) Roman W dniu 2012-07-13 13:58, Roman Łapacz pisze:
Thanks Freek. Your changes look very good.
I attached an example of RRD MA metadata file with two metadata elements (I removed vlan info as it is not used by the service). I don't think existing pS services have to use NML in near future but it's valuable to present how this could look like (prove that NML fits).
Roman
W dniu 2012-07-12 16:36, Freek Dijkstra pisze:
On 12-07-2012 15:58, Roman Łapacz wrote:
Hi,
I'm thinking how NML could be used in existing pS services, especially in RRD MA.
See below. Any suggestions/comments how this could be done?
metadata piece valid for RRD MA:
<nmwg:metadata id="meta1"> <netutil:subject id="subj1"> <nmwgt:interface> <nmwgt:hostName>test-hostName</nmwgt:hostName> <nmwgt:ifAddress type="ipv4">10.1.2.3</nmwgt:ifAddress> <nmwgt:ifName>test-0</nmwgt:ifName> <nmwgt:ifDescription>test descripyion</nmwgt:ifDescription> <nmwgt:direction>in</nmwgt:direction> <nmwgt:capacity>1000BaseT</nmwgt:capacity> </nmwgt:interface> </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:parameters id="params1"> <nmwg:parameter name="keyword">project:geant2</nmwg:parameter> </nmwg:parameters> </nmwg:metadata>
a quick proposal using NML's Port that looks strange to me:
<nmwg:metadata id="meta1"> <netutil:subject id="subj1"> <nml:Port> <nml:label labelType="http://schemas.ogf.org/nml/ip/ipv4/if/address/2013/10/">193.10.252.66</nml:label> <nml:label labelType="http://schemas.ogf.org/nml/ip/ipv4/if/hostNames/2013/10/">test-hostName</nml:label>
... ... ... </nml:Port> </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:parameters id="params1"> <nmwg:parameter name="keyword">project:geant2</nmwg:parameter> </nmwg:parameters> </nmwg:metadata> First two comments,
1. I don't think the above are labels. GMPLS and G.800 have a very specific meaning with the term "label". G.800 defines:
"A label provides a means of providing added information for the purpose of distinguishing and identifying individual communications within a communication which is formed to convey a combination of communications" After taking some aspirin I take this to mean "A label is the information that distinguishing individual data stream within a larger data stream". So a VLAN ID in 802.1Q Ethernet, the wavelength in DWDM, the VCI in ATM, or the timeslot in SDH. The hostname is not a label.
2. The URIs look a bit odd to me. GFD.084 would probably use something along the lines of http://schemas.ogf.org/nml/2013/10/dns/hostName, -or with Jason suggestion to move the date further to the back- http://schemas.ogf.org/nml/dns/2013/10/hostName
Now onto the solution. I think that the single strength of NML is that it allows a place to describe all sorts of properties of the network, so all a monitoring system no longer need to provide that information itself, but only need to point to it. So we can rip out all of the<nmwgt:interface> part from the monitoring service, and replace it with a simple (URN) pointer to the (NML) Port, which is described in detail in NML.
I presume the combination of the two looks something like this: (copied as quotation to stop my mailer from wrapping lines)
<!-- NML Topology -->
<nml:Node id="urn:ogf:network:netherlight.net:2010:Asd001a-ome24"> <nml:name>test-hostName</nml:name> <nml:Relation type="http://schemas.ogf.org/nml/base/2013/10/hasInboundPort"> <nml:Port idRef="urn:ogf:network:netherlight.net:2010:Asd001a-ome24:1-5-4:vlan110:in" /> </nml:Relation> </nml:Node>
<nml:Port id="urn:ogf:network:netherlight.net:2010:Asd001a-ome24:1-5-4:vlan120:in"> <nml:name>test-0</nml:name> <nmwgt:description>test description</nmwgt:description> <nml:label encoding="http://schemas.ogf.org/nml/ethernet/2013/10/vlan">120</nml:label> <nmleth:capacity>1000BaseT</nmleth:capacity> <nmlip:ipv4address>10.1.2.3</nmlip:ipv4address> </nml:Port>
<!-- Monitoring Data -->
<nmwg:metadata id="meta1"> <netutil:subject id="subj1"> <nml:Port idRef="urn:ogf:network:netherlight.net:2010:Asd001a-ome24:1-5-4:vlan120:in"/> </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:parameters id="params1"> <nmwg:parameter name="keyword">project:geant2</nmwg:parameter> </nmwg:parameters> </nmwg:metadata>
<nmwg:data metadataIdRef="meta1" id="data.6343912">> <nmwg:datum timeType="unix" value="0.302" valueUnits="float" timeValue="1320605686"/> <nmwg:datum timeType="unix" value="0.821" valueUnits="float" timeValue="1320605687"/> <nmwg:datum timeType="unix" value="0.365" valueUnits="float" timeValue="1320605688"/> <nmwg:datum timeType="unix" value="0.724" valueUnits="float" timeValue="1320605689"/> </nmwg:data> Regards, Freek
_______________________________________________ nml-wg mailing list nml-wg@ogf.org https://www.ogf.org/mailman/listinfo/nml-wg