[Nodeshot] Refactoring doubt: device fields firmware and OS

[Nemesis]

The problem with having OS version is that the automatic scripts running
get a version number which is quite complex.

Firmware in AirOS: XM.ar7240.v5.3.3.sdk.9634.111221.2238
uname -a output in AirOS: Linux version 2.6.15-5.2 (saverio at nockid) (gcc
version 4.1.2)

While in the case of OpenWRT the name extracted with this method:
https://github.com/nemesisdesign/nodeshot/blob/refactoring/nodeshot/networking/connector/classes/OpenWRT.py#L24

OpenWrt Attitude Adjustment (Scooreggione v4 12.09, r36608)

uname -a output is: Linux version 3.3.8 (saverio at nockid) (gcc version
4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) )

Is it really useful to have separate fields for OS and OS version?


A similar issue is related to RoutingProtocols.

By just running the script on 2 devices I already have these 2 OLSR
entries in the routing protocols DB table:

name: OLSR; version: pre-0.6.3-git_-hash_b493c377b33f6e45d0b2e8b4c8e7c5db
name: OLSR; version:
0.6.5.3-git_3491d09-hash_459f792b8d1a10846916b0bf3e21f727

Federico


On 11/06/2013 05:50 PM, Clauz wrote:
> Hi.
> If we want to keep it simple would suggest using "OS" (which is more
> general than "Firmware") and "OS Version". In this way also statistics
> on OS/Firmware usage could be easily computed.
>
> Clauz
>
>
> On 11/06/2013 04:28 PM, nemesis wrote:
>> I don't have time at the moment to refactor the field to become a table.
>> Maybe in the future if we start offering firmware images to download or
>> stuff like that it would be a nice feature.
>>
>> The question was if we should have OS and Firmware fields or if we
>> should have just OS and in case the device is an embedded device we
>> could fill OS with the name of the firmware, eg: OpenWRT Attitude
>> Adjustment, AirOS, ecc
>>
>> Federico
>>
>>
>> On Wed, 6 Nov 2013 16:22:14 +0100, Fabio Capriati
>> <fabio.capriati at gmail.com> wrote:
>>> It's possible to retrive these information from devices remotly and
>>> building automatically this table by script.
>>>
>>> 2013/11/6 nemesis
>>>  Your proposal could be useful if we used that information to
>>> generate the image to be installed on devices, but at the moment this
>>> is not on my todo list, and I would adopt the kiss principle and keep
>>> it as more simple as possible.
>>>
>>>  Federico
>>>
>>>  On Wed, 6 Nov 2013 14:35:10 +0100, Fabio Capriati  wrote:
>>>
>>>  In my opinion, it could be righta a table "Firmware" with this
>>>  fields:
>>>
>>>  Integer "ID"
>>>  String "Operative System"   (OperWRT | MicrotiKOS | AirOS)
>>>  String "Name" (Stock | Sburratone | Scorreggione)
>>>  Integer "Version"
>>>  Bool "Support IPV6"
>>>  Bool "Support SNMP"
>>>  Bool .... 
>>>
>>>  So into device you can put only the ID reference.
>>>
>>>  2013/11/6 Stefano De Carlo
>>>
>>>   Il 06/11/2013 14:00, nemesis ha scritto:
>>>
>>>    > In the Device table at the moment we have "os" which stands for
>>>   > "operating system" and "firmware", both are optional fields.
>>>   >
>>>   > Does it have sense to have both? Or in case of embedded device
>>> the
>>>  OS
>>>   > field should be filled with the firmware name?
>>>   >
>>>   > Have your say
>>>
>>>   In my experience I think It's best not to have semantic clashes
>>> like
>>>   this one and just go for an agnostic term. "Operating System" will
>>>  work
>>>   just fine for the whole device spectrum.
>>>
>>>   Stefanauss.
>>>
>>>  _______________________________________________
>>>   Nodeshot mailing list
>>>   Nodeshot at ml.ninux.org [3] [2]
>>>   http://ml.ninux.org/mailman/listinfo/nodeshot [4] [3]
>>>
>>>  Links:
>>>  ------
>>>  [1] mailto:stefanauss at gmail.com [5]
>>>  [2] mailto:Nodeshot at ml.ninux.org [6]
>>>  [3] http://ml.ninux.org/mailman/listinfo/nodeshot [7]
>>>
>>>  _______________________________________________
>>>  Nodeshot mailing list
>>>  Nodeshot at ml.ninux.org [8]
>>>  http://ml.ninux.org/mailman/listinfo/nodeshot [9]
>>>
>>>
>>>
>>> Links:
>>> ------
>>> [1] mailto:nemesis at ninux.org
>>> [2] mailto:fabio.capriati at gmail.com
>>> [3] mailto:Nodeshot at ml.ninux.org
>>> [4] http://ml.ninux.org/mailman/listinfo/nodeshot
>>> [5] mailto:stefanauss at gmail.com
>>> [6] mailto:Nodeshot at ml.ninux.org
>>> [7] http://ml.ninux.org/mailman/listinfo/nodeshot
>>> [8] mailto:Nodeshot at ml.ninux.org
>>> [9] http://ml.ninux.org/mailman/listinfo/nodeshot
>> _______________________________________________
>> Nodeshot mailing list
>> Nodeshot at ml.ninux.org
>> http://ml.ninux.org/mailman/listinfo/nodeshot
>
>
>
> _______________________________________________
> Nodeshot mailing list
> Nodeshot at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/nodeshot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.ninux.org/pipermail/nodeshot/attachments/20131106/35523945/attachment-0001.html>