Hi everyone,
I am looking and playing with Openwisp and Netjson. I hope i can ask u
some questions.
Currently i am trying to automate a managed switch. I came to the
horrible conclusion it only allows for changes using web-ui. I made a
very basic webscraper that is able to do some very basic things like
enabling / disabling network ports or enabling / disabling Power over
Ethernet (POE)
Would such a module be something u see as being in the scope of netjson?
I mean having some kind of adapter <Openwisp/configuration frontend> -
<Adapter script> - <Switch WebUI>. The way i see netjson would be as a
universal configuration format. Having something like Openwisp produce a
netjson file and having something else (could be the device itself)
applying it on the device.
I miss somethings in the netjson standard
- encryption. I think there should be a standard way to encrypt netjson
files on the wire with for example a shared key. U could leave that to
the transport but i think it would be better to have a way of doing it
in a standard.
- push vs pull:
Now all openwisp device do a configuration pull every x minutes. I think
that's a waste of resources on the controller side. What it your vision
on using MQTT/AMQP or another open protocol to push configurations to
devices. Advantage in this case would also be that u don't need to pull
config that often or not at all. The configuration can be applied within
seconds after the are changed on the server no matter where the device
is located (behind NAT/Firewall).
This would also allow for a new possibility of having a easy way to get
data from the device. And also integration in home-automation systems
would be a lot easier.
Kind regards,
Pimmetje
--
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.
