Hi Developers, I am Arunkumar Ravichandran currently admitted for masters program at University of California, San Diego. My proposal <https://wiki.freifunk.net/Ideas#Implement_NetJSON_output_in_ubus_.28OpenWRT.2FLEDE.29>*Implement NetJSON output in ubus (OpenWRT/LEDE)* has been accepted to the GSOC 2017 and I would like to tell more about my proposed project.
The main aim of this project is to implement parts of the NetJSON specification in the OpenWRT/LEDE ecosystem. *Why NetJSON ??* NetJSON would allow standardization similar to NETCONF. Since NetJSON uses JSON format, it makes the management of configurations done at a higher level and larger scale to be automated easily. By using NetJSON objects to either produce or collect information, in different vendor’s different hardware, it allows the developers to work on their ideas faster and in a better way. *Implementation:* The support for NETJSON <https://github.com/netjson/netjson>is brought in at the interconnect system- ubus <https://lede-project.org/docs/guide-developer/ubus>. To add support for a new ubus API which allows retrieving these two NetJSON object types: DeviceConfiguration and DeviceMonitoring. DeviceConfiguration NetJSON objects are filled in using the plugins available in System Configuration Abstraction Layer(SCAL <https://github.com/prplfoundation/scal>). Full project proposal can be read at: Google docs <https://docs.google.com/document/d/1b6zersOA_GjUqbOjuaXvFd4E40l1MqUXjIyVagLLd08/edit?usp=sharing> I would welcome further suggestions from the LEDE/ OpenWRT community as that would help in implementing this feature sooner and in a better way, and also more resilient to multiple data models which are being used to represent network configurations. Thanks, Arun
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
