Currently we have two disjoint families of node ID conventions:
mac address
mac address with four zeros prefix added
This grew out of many scripts querying the mac address directly and using it without padding it with zeros and, perhaps, a misunderstand of why the zeros were added in the first place.
Now, some nodes have data labelled with both kinds of IDs which is not handled by the current data serving process. Needless to say, this is confusing.
The good thing is, we just need to be more consistent with our own naming, add some sanitization in the data loaders and clean up the datasets in use. The database itself shouldn't care at all as any string could be used as a node ID.
Currently we have two disjoint families of node ID conventions:
This grew out of many scripts querying the mac address directly and using it without padding it with zeros and, perhaps, a misunderstand of why the zeros were added in the first place.
Now, some nodes have data labelled with both kinds of IDs which is not handled by the current data serving process. Needless to say, this is confusing.
The good thing is, we just need to be more consistent with our own naming, add some sanitization in the data loaders and clean up the datasets in use. The database itself shouldn't care at all as any string could be used as a node ID.