- Nmc-wg - lists.ogf.org

(no subject)
by Roman Lapacz 11 May '10

11 May '10

Hi Jason & all, I'm reading merge chaining examples in the base doc and I'm not sure that keeping partial metadata elements, which in my opinion are useless after chaining oparation, is a good approach. I don't believe that they might be used for any further processing. Keeping them in the examples presenting merged structures may be confusing for a reader. I would remove them. What do you think (see examples in the attachements)? Roman

7 14

pS Result Codes - proposal
by Roman Lapacz 15 Apr '10

15 Apr '10

As promised Slawek and I have prepared a doc describing new result codes. Comments and updates are welcome. Cheers, Roman

6 9

Call tomorrow 4/15 @ 15:00 UTC
by Jason Zurawski 15 Apr '10

15 Apr '10

All; We will have a call tomorrow, agenda is posted here: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.nmc-wg/wiki/201004… Thanks; -jason

1 1

[ogf nmc-base svn commit] r21 - /
by svn＠ogf.org 07 Apr '10

07 Apr '10

Author: romradz Date: 2010-04-07 08:31:48 -0500 (Wed, 07 Apr 2010) New Revision: 21 Modified: nmc-base.pdf Log: Main doc with updated examples (see previous commit). Modified: nmc-base.pdf =================================================================== (Binary files differ)

1 0

[ogf nmc-base svn commit] r20 - examples
by svn＠ogf.org 07 Apr '10

07 Apr '10

Author: romradz Date: 2010-04-07 08:29:07 -0500 (Wed, 07 Apr 2010) New Revision: 20 Modified: examples/echo1.xml examples/echo2.xml examples/echo3.xml examples/echo4.xml examples/request1.xml examples/request2.xml examples/request3.xml examples/request4.xml examples/request5.xml examples/response1.xml examples/response2.xml examples/response3.xml Log: - Few typos corrected (metadatIdRef -> metadataIdRef) - Example of wrong echo request should have wrong message type but it had the right one. Corrected. Modified: examples/echo1.xml =================================================================== --- examples/echo1.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/echo1.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -8,6 +8,6 @@ </nmwg:eventType> </metadata> - <data id="d1" metadatIdRef="m1" /> + <data id="d1" metadataIdRef="m1" /> </message> Modified: examples/echo2.xml =================================================================== --- examples/echo2.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/echo2.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -1,5 +1,5 @@ <message xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" - type="EchoRequest" + type="Echo" id="message2"> <metadata id="m1"> @@ -8,6 +8,6 @@ </nmwg:eventType> </metadata> - <data id="d1" metadatIdRef="m1" /> + <data id="d1" metadataIdRef="m1" /> </message> Modified: examples/echo3.xml =================================================================== --- examples/echo3.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/echo3.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -8,7 +8,7 @@ <nmwg:eventType>success.echo</nmwg:eventType> </metadata> - <data id="d1" metadatIdRef="m1"> + <data id="d1" metadataIdRef="m1"> <nmwgr:datum>The echo request has passed.</nmwgr:datum> </data> Modified: examples/echo4.xml =================================================================== --- examples/echo4.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/echo4.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -1,12 +1,14 @@ <nmwg:message xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" xmlns:nmwgr="http://ggf.org/ns/nmwg/result/2.0/" - type="EchoResponse" id="message4" messageIdRef="message2"> + type="EchoResponse" + id="message4" + messageIdRef="message2"> <metadata id="m1"> <nmwg:eventType>error.echo</nmwg:eventType> </metadata> - <data id="d1" metadatIdRef="m1"> + <data id="d1" metadataIdRef="m1"> <nmwgr:datum>The echo request has failed.</nmwgr:datum> </data> Modified: examples/request1.xml =================================================================== --- examples/request1.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/request1.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -6,6 +6,7 @@  </metadata> - <data id="d1" metadatIdRef="m1" /> +  + <data id="d1" metadataIdRef="m1" /> </message> Modified: examples/request2.xml =================================================================== --- examples/request2.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/request2.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -3,13 +3,14 @@ id="message2"> <nmwg:parameters id="parameters1"> - <nmwg:parameter name="something">something else</nmwg:parameter> + <nmwg:parameter name="name">value</nmwg:parameter> </nmwg:parameters> <metadata id="m1">  </metadata> - <data id="d1" metadatIdRef="m1" /> +  + <data id="d1" metadataIdRef="m1" /> </message> Modified: examples/request3.xml =================================================================== --- examples/request3.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/request3.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -6,12 +6,14 @@  </metadata> - <data id="d1" metadatIdRef="m1" /> +  + <data id="d1" metadataIdRef="m1" /> <metadata id="m2">  </metadata> - <data id="d2" metadatIdRef="m2" /> +  + <data id="d2" metadataIdRef="m2" /> </message> Modified: examples/request4.xml =================================================================== --- examples/request4.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/request4.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -3,13 +3,14 @@ id="message4"> <metadata id="m1"> -  +  </metadata> <metadata id="m2" metadataIdRef="m1"> -  +  </metadata> - <data id="d1" metadatIdRef="m2" /> +  + <data id="d1" metadataIdRef="m2" /> </message> Modified: examples/request5.xml =================================================================== --- examples/request5.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/request5.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -6,6 +6,7 @@  </metadata> - <data id="d1" metadatIdRef="m2" /> +  + <data id="d1" metadataIdRef="m2" /> </message> Modified: examples/response1.xml =================================================================== --- examples/response1.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/response1.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -7,7 +7,7 @@  </metadata> - <data id="d1" metadatIdRef="m1"> + <data id="d1" metadataIdRef="m1">  </data> Modified: examples/response2.xml =================================================================== --- examples/response2.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/response2.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -7,7 +7,7 @@  </metadata> - <data id="d1" metadatIdRef="m1"> + <data id="d1" metadataIdRef="m1">  </data> @@ -15,7 +15,7 @@  </metadata> - <data id="d2" metadatIdRef="m2"> + <data id="d2" metadataIdRef="m2">  </data> Modified: examples/response3.xml =================================================================== --- examples/response3.xml 2010-03-16 10:05:37 UTC (rev 19) +++ examples/response3.xml 2010-04-07 13:29:07 UTC (rev 20) @@ -7,7 +7,7 @@  </metadata> - <data id="d1" metadatIdRef="m1"> + <data id="d1" metadataIdRef="m1">  </data>

1 0

Cancel 4/1 NMC Call
by Jason Zurawski 29 Mar '10

29 Mar '10

All; I and several others will be unavailable for the NMC call on Thursday (4/1). I propose we cancel, and pick up again on 4/15. Thanks; -jason

2 1

Re: [Nmc-wg] [Fwd: Re: Netconf in pS]
by Arne Oslebo 27 Mar '10

27 Mar '10

Hello, I apologize for not replying to this earlier but I wanted to wait till the documentation that I had written was available. Roman Lapacz wrote: > > -------- Original Message -------- > Subject: Re: [Nmc-wg] Netconf in pS > Date: Thu, 21 Jan 2010 09:39:45 -0500 > From: Jason Zurawski <zurawski(a)internet2.edu> > Reply-To: zurawski(a)internet2.edu > Organization: Internet2 > To: Roman Lapacz <romradz(a)man.poznan.pl> > CC: nmc-wg(a)ogf.org <nmc-wg(a)ogf.org> > References: <4B5701F4.3060607(a)man.poznan.pl> > > > > Hi Roman; > > Thanks for providing this, pretty neat. Also for reference the NETCONF > RFC is here: > > http://tools.ietf.org/html/rfc4741 > >> I'm sending you some info about the investigation work (by Arne >> Oslebo) on Netconf in pS which is being done in Geant3. After a while >> I will add a detailed description from one of project documents but >> it's still under review process so it must wait a bit. >> >> http://software.uninett.no/stager/wiki/netconf > > An obvious issue that the author has pointed out to not use NM-WG/NMC-WG > is the lack of documentation both at a protocol and service level, which > is a failing for the pS consortium in general. Hopefully this will be > rectified soon through this group. There are actually three issues with NM-WG/NMC-WG that we point out: * Lack of proper separation between information model and communication model. * Lack of generic information model for MA and MP. * Lack of proper validation mechanisms. For more details please see the document that Roman sent to the list last week. > > To comment on the subject matter itself, I am having a hard time > justifying in my mind why trying to use a protocol designed for a > similar (but not identical) task is a good idea. In NETCONF's own > words it: > >> provides mechanisms to install, manipulate, and delete the >> configuration of network devices > > This touches a gray area in perfSONAR that has been the topic of DICE > meetings in the past, namely managing the service configuration vs the > measurement configuration. I think there may be a place in perfSONAR > for this protocol, but I don't believe that exchanging/storing the > actual data with the NETCONF primitives makes sense. I know that the topic of what NETCONF can and can not be used for is a controversial topic, even within IETF. Things are however starting to change. For NETCONF to be used as a generic network management protocol it needs proper access control. I attended IETF this week and a private draft proposing an access control model for NETCONF was very well received in the NETCONF working group and it was decided that this is something that the working group will start to work on. So while IETF still has not made any official statement, people are now openly talking about NETCONF becoming the next preferred network management protocol instead of SNMP. This is part of the motivation behind our work. We believe that perfSONAR basically is distributed network management in a multi domain setting. Looking at the data that is stored in the various MA and MP implementations we don't see any fundamental difference between this information and what you typically collect in normal network management. So if NETCONF can be used for normal network management, why can it not be used in perfSONAR? Our simple prototype shows that it can be used. > > I will end by noting a reply that Martin has been known to give in the > past: "its all just XML!". I agree completely but would like to turn this argument around. Since there already exists XML protocols for transporting data from A to B, NETCONF being one of them, why spend so much time and effort defining yet another protocol? After all "its all just XML". > Maybe we can see a demonstration at the next developers meeting to see > how valuable this could be. We had I demo site up and running, but I see that it is now giving error messages. I will look at it next week and try to fix it. I'm currently working on a more stable implementation that will also simplify the information model. The deadline for this work is in June but I hope to have it finished before that. Best regards, Arne

1 0

Base doc - TODO
by Roman Lapacz 22 Mar '10

22 Mar '10

TODO list for NMC base doc (prepared by Jason). http://forge.ogf.org/sf/wiki/do/viewPage/projects.nmc-wg/wiki/NMCBase_TODO (I'm sending this email as a reminder for myself and maybe for others) Roman

2 1

Presentation from OGF 28
by Jason Zurawski 22 Mar '10

22 Mar '10

Hi Andreas; Would you be able to mail the presentation you gave at OGF? I would like to post it to our wiki. Thanks; -jason

2 1

Next NMC Call - April 1st - 15:00 UTC
by Jason Zurawski 22 Mar '10

22 Mar '10

Hi All; We will have our next call on April 1st at 15:00 UTC (N.B. note the timeshift of an hour, both the US and EU *should* be in daylight time by this week). Agenda will be located here: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.nmc-wg/wiki/201004… Thanks; -jason

1 0