[Interop-dev] Network Device JSON Schema

[Moritz Warning]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yes, it is for a map. We do not gather any more information about nodes.
Maybe we will sha256sum the MAC for the links at some point. Just an idea.

On 10/26/2014 06:43 PM, Nemesis wrote:
> Hey,
> 
> On 10/26/2014 03:50 AM, Moritz Warning wrote:
>> I guess that ventures too munch into the meta domain.
>> Let's first try to get to a common ground without. :-)
>>
> 
> I agree.
> 
>> For what it matters, we use this rather minimal format:
>>
>> {
>>     "name" : "foobar",
>>     "firmware" : "ffbi-0.3",
>>     "community" : "somecity",
>>     "geo" : "52.02513078 8.55887",
>>     "links" : [
>>         { "smac" : "b0:48:7a:f6:85:76", "dmac" : "8c:21:0a:d8:af:2b",
>> "qual" : 251 },
>>         { "smac" : "2a:88:01:80:6b:93", "dmac" : "ee:51:43:05:1f:ef",
>> "qual" : 255 }
>>     ],
>>     "clientcount" : 2
>> }
> 
> Let's see.. we have name, firmware, geo, links and clientcount, it looks
> like a node on a map web interface more than a network device, is that
> the case?
> 
> Something in common is probably "firmware" (even though in what we
> proposed there's "os" and "os_version". Also, nothing should stop anyone
> from mixing customs attributes with what we would come up with.
Yes, that sounds good.

> 
> On 10/25/2014 11:54 PM, Jernej Kos wrote:
>> Hello!
>>
>> Please also check out the nodewatcher-agent schema, which has an
>> implementation. The main difference to your proposed schema is that it
>> is not monolithic, but is modular, with each module's output being
>> versioned.
>>
>>   https://github.com/wlanslovenija/nodewatcher-agent
>>   https://github.com/interop-dev/network-device-schema/issues/1
> 
> Thanks for posting the full JSON here:
> https://github.com/interop-dev/network-device-schema/issues/1#issuecomment-60508259
> 
> So, let me recap why I am doing this:
> 
>   * everybody of us is using a different structure to represent "stuff"
>     in our networks
>   * the "stuff" gets passed from app to app, sometimes changing
>     structure in apps of the same community
>   * we don't have a clear definition of what that "stuff" is, a
>     geographic object? a server? a router? a link? all or some of those?
> 
> What i think is achievable in a short time:
> 
>   * define what a network device is
>   * create a JSON schema to represent a network device only, we can
>     define other objects (eg: links) in future steps
>   * start offering this format in our apps and software - we would not
>     have to give up what we currently use, we might offer both formats
>     if that is more convenient
> 
> So I start asking you few questions.
> 
> *1. *Have you ever felt the need of having a widely used standard
> structure to represent network-devices?
Me? - nope. :)

> 
> *2. *Do you agree with this definition?
> 
> /A network device is any device which is connected to a layer2 or layer3
> network and should provide some basic information/ (let's define what
> this minimum information is).
> 
> *3. *Do you like the idea of starting small?
> 
> Federico
> 
> 
> 
> _______________________________________________
> Interop-dev mailing list
> (spam-protected)
> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBCAAGBQJUTUUwAAoJECHrh56PP4wpVJgIANEAXfz7x1SN5IXNoNEAJ8IX
nPsiJ+R+/M06xwcUKtq5vtFu9v7M4ANEIhmIY9l9zTRntC2/1UgGVjprrNdbtEp1
3DwdKy9f9E96PbwNw9w9Xf7zPbBsoFGihtbjlQf1khaG8PbySDCoRUgPFubVgmB6
dTYavaS5jQxdw2D1RXW/+PF187zpUwIVKEJI6d59vI9jCUne3dOaFa+w7csyMtMa
Hm2DHDR+f9hmdXV2JyiRmdOqBiFMoV/kszrR0qAz4LVQh8ltRBrEMXdSG5nS9sda
U5eEqCX32x7Ss+x3vj7+4LrPjAXqDEHct5gfOK987+rOX388GFv+Cmb72Y25qNQ=
=M28I
-----END PGP SIGNATURE-----