11490 2017-05-10 09:45:18 +0000 Configuration Management Solution Study 2017-08-09 11:00:05 +0000 1 1 6 Yocto Project Subprojects IoT Reference OS Kit intel-iot-refkit-default 2.4 All Multiple RESOLVED FIXED Medium enhancement 2.4 M2 1 krisztian.litkey amarnath.valluri amarnath.valluri jose.perez.carranza patrick.ohly jair.de.jesus.gonzalez.plascencia --- --- No (bug/feature does not impact docs) oldest_to_newest 73157 0 krisztian.litkey 2017-05-10 09:45:18 +0000 Evaluate the suitability of existing configuration management solutions (uci/luci, etc.) for integration into refkit. 75078 1 patrick.ohly 2017-07-17 18:53:09 +0000 Amarnath, are you now working on this instead of Krisztian? Is it realistic to finish this before 2.4 M2 (basically end of this month)? 75098 2 amarnath.valluri 2017-07-18 09:15:15 +0000 (In reply to comment #1) > Amarnath, are you now working on this instead of Krisztian? Is it realistic > to finish this before 2.4 M2 (basically end of this month)? Yes, i been working on this. Currently evaluating the usage of UCI/LuCI on refkit. I think we can finish this for M2 scope. 75766 3 amarnath.valluri 2017-08-09 11:00:05 +0000 Here is the update on OpenWRT's uci/LuCI evaluation: - UCI: is the configuration solution for OpenWRT's systems. - LuCI/LuCI2/JuCI : is the web interface for configuring devices running OpenWRT system, built on top of UCI. License: Apache-2.0 - LuCI is Lua based, and uses Lua extensions to access subsystem info and is appeared to be quite resource consuming and didn't work well on devices with slow CPU and little amount of RAM. - LuCI2 is a new(experimental) web interface with a different architecture written using JavaScript. It uses XHR(XmlHTTPRequest) method., that means building the HTML pages is done at client side. LuCI2 uses ubus(inter-process communication bus system) to communicate with the subsystem. License: Apache v2.0 - JuCI is modern web interface build using HTML5 and angular.js, and uses websockets for communicating with a compact and fast lua backend running o the device. License: GPLv3 - LuCI2 is preferred web interface over Luci and Juci due to it's simple architecture, less external dependencies and flexible licensing. - LuCI2 web interface provides configuration ui for: - System information such as host name, device model, Firmware version, Kernel version, Device memory information, Storage details. - Routes – IPv4/v6 routes active on the system - Kernel logs - System logs (/var/log/messages) - Sending signals to running processes - Add/remove ssh keys(dropbear) - Adding/removing network interfaces - enable/disable a network device - Luci2 provides base widgets(JS objects) which can be extended to customize the ui. New UI tabs/views can be added by extending Luci's L.ui.view JavaScript object. - External dependencies we bring-in: libubox – C utility functions for OpenWrt uci - A small utility written in C, intended to centralize the configuration ubus – OpenWrt micro bus for inter process communication rpcd – ubus RPC backend server luci2 - OpenWrt web user interface uhttp2 – light weight web server ustream-ssl - Ustream SSL wrapper library The Yocto meta data for these components are grouped under meta-configuration layer: https://github.com/avalluri/meta-configuration There needs to be work done at system adaptation., i.e, Make refkit core components such as openssh, connman etc., aware of UCI configuration, by writing adapters. Similar proof of concept work is done here: https://github.com/avalluri/rpcd-system-plugin https://github.com/avalluri/connman-uci