Hello everybody, at our company, we are doing preparations to move over to OpenWISP.
Our devices have a unique serial number which is currently used as the unique identifier of a device. So I'm thinking about how to integrate that with OpenWISP. In the OpenWISP controller, a device currently has the following fields: - id: randomly generated upon device registration/creation - key: generated by openwisp-config based on the shared secret and the MAC address of a specific interface (default eth0) - mac_address: MAC address of the interface mentioned above - name: hostname of the device (or MAC as fallback) The name is also used in django-netjsonconfig as the device identifier whenever a list of devices is displayed. Additionally, the name is read-write which means that the hostname of the device can be changed through django-netjsonconfig. To integrate all of this, I'm proposing the following: - On the controller the hostname should be a field of its own, independent from the name of the device, so people can set different values for the hostname of the device and the name of the device on the controller - In the configuration of openwisp-config there should be an option to define a command or script to get the initial value for the name of the device on the controller (default hostname - in our case a command to get the serial number) - there might be the requirement to add another unique identifier for the device on the controller, a department number, some address, etc (which can be displayed in the devices listing or used for searching devices). Maybe the notes field can be used for this What do you think about this? Greetings, Oliver -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
