<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi everybody,<br>
<br>
I'm back from the US, sorry for responding so late, I had a very
bad jetlag.<br>
<br>
let me clarify:<br>
<br>
initially my intention was to define a representation of a network
device:<br>
<ul>
<li>device name</li>
<li>device model</li>
<li>hardware stuff that is easy to retrieve programmatically</li>
<li>configuration of interfaces</li>
<li>wireless configuration<br>
</li>
</ul>
I was not attempting - <b>yet</b> - to define a standard for node
monitoring, but we can work on it in parallel, I'd be happy to
deal with it sooner rather than later.<br>
<br>
It's true that the schema contains also dynamic attributes (like
noise and dbm) which change over time, and after you pointed that
I realized it might not have sense to put it there.<br>
<br>
But that's why I like doing stuff collaboratively, rather than by
myself, I know that by doing it alone it would take me years to
get it right, and moreover, we risk doing everyone a different
thing that is not able to talk to each other, it would be much
better to do it together than one group or one person going solo.<br>
<br>
We could start to define a few object to start with.<br>
<br>
I see that we have two different priorities:<br>
<ul>
<li>network device configuration</li>
<li>monitoring data</li>
</ul>
<p>Latelly i've been working more on the network device
configuration object, which I simplified by calling it
network-device-schema.<br>
</p>
@Ralf:<br>
I have taken a look at the link you posted.<br>
<br>
What I'm trying to do is related but slightly different.<br>
It's not an API, but a JSON schema that I would like to use to
represent some of those points listed in
<a class="moz-txt-link-freetext" href="https://github.com/Common-Node-DB/paper/blob/master/common-api.txt">https://github.com/Common-Node-DB/paper/blob/master/common-api.txt</a>
(eg: net device, net interfaces, net wireless)<br>
<br>
You can immagine it like GeoJSON which is widely used in GIS apps
and GIS libraries.<br>
You can pass a GeoJSON to most GIS low level libraries and it will
be converted to a geographic object of that specific library, that
approach has been very successfull.<br>
<br>
It would be really cool if we could define a schema for network
"stuff" that we could pass to libraries and apps like it already
happens with GeoJSON.<br>
<br>
One example:<br>
<ol>
<li>web app A returns NetJSON from its HTTP API</li>
<li>library B parses the NetJSON and does some calculations</li>
<li>library B passes the NetJSON to web app C</li>
<li>web app C converts the NetJSON in its own specific database
object<br>
</li>
</ol>
app A, library B and web app C might be developed by completely
different people, in different communities, from opposite sides of
the world, but would be collaborating in creating an ecosystem
rather than redeveloping apps and libraries that do not talk to
each other like we have been doing latelly. The problem with what
we have been doing latelly is that every project is all or
nothing: you either buy the entire stack or redevelop your own,
like proprietary systems :-D :-P<br>
<br>
Sure we should split the NetJSON in more components, and we can
surely work on it in parallel.<br>
<br>
So my next questions are<br>
<ul>
<li>is it clearer now? If not I might spend some more time
trying to explain myself clearer</li>
<li>do you think it's worth it? if not could you explain what
alternative you would prefer?<br>
</li>
<li>do you have time to start collaborating on defining the
components you are most interested in?</li>
<li>which are the components you are most interested in right
now?<br>
</li>
</ul>
Federico<br>
<br>
<br>
On 10/28/2014 07:43 AM, L. Aaron Kaplan wrote:<br>
</div>
<blockquote
cite="mid:D81842F7-4316-4E51-A77C-F5361B1C75CE@lo-res.org"
type="cite">
<pre wrap="">
On Oct 28, 2014, at 7:27 AM, Jernej Kos <a class="moz-txt-link-rfc2396E" href="mailto:jernej@kos.mx"><jernej@kos.mx></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello!
On 28. 10. 2014 03:14, Nicolás Echániz wrote:
</pre>
<blockquote type="cite">
<pre wrap="">So... uptime is the only "telemetry" information in that document?
</pre>
</blockquote>
<pre wrap="">
No, all attributes could be interpreted as telemetry (reports about
addresses and MTU configured on interfaces, we have all that in our
nodewatcher-agent telemetry reports, routing protocol package versions,
etc.).
Also see the "dbm" and "noise" reported on the wireless radio.
So Federico should comment if this is meant as static configuration
and/or network device telemetry. I still believe it is the latter.
</pre>
</blockquote>
<pre wrap="">
I believe the most useful for us right now would be static config.
At lest from my perspective. For sure, telemetry is *also* important, but for me personally right now it has a lower importance value.
my 2 cents,
a.
</pre>
<blockquote type="cite">
<pre wrap="">
Jernej
_______________________________________________
Interop-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Interop-dev@lists.funkfeuer.at">Interop-dev@lists.funkfeuer.at</a>
<a class="moz-txt-link-freetext" href="https://lists.funkfeuer.at/mailman/listinfo/interop-dev">https://lists.funkfeuer.at/mailman/listinfo/interop-dev</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Interop-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Interop-dev@lists.funkfeuer.at">Interop-dev@lists.funkfeuer.at</a>
<a class="moz-txt-link-freetext" href="https://lists.funkfeuer.at/mailman/listinfo/interop-dev">https://lists.funkfeuer.at/mailman/listinfo/interop-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>