[OpenWrt-Devel] [LEDE-DEV] [OpenWrt] Project proposal: The GNUnet of autonomous Things
arturo at arduino.org
Fri Dec 2 21:58:17 EST 2016
as Kathy mentioned as first answer to Daniel, a proper setup running GNUnet
on our boards could give us a boost in the IoT world. During the last years
we have developed a new approach to the arduino "bridge" interaction with
this is of course requires the use of Python as high level language since
it is designed around it but transparent to any kind of connectors. If I
understand well from this first email exchange, since *ubus* will be the
running engine of the new it is a completely native approach being it an
underlying running service of OpenWRT. Am I wrong or didn't John show
something similar that night at C-base in Berlin as first attempt of
creating a sort of new approach to the bridge itself ?
This leads me to think about the possibility to use this solution in
combination with *lininoIO*, our new approach for exposing the MCU gpio(s)
as filesystem devices and using them to interact with sensors, actuators
and so on (it was one of the topics of my talk in Berlin). Would this be a
reasonable approach for you ? Please let us know what you think about it
and in case we'll discuss it in the scheduled call.
2016-12-01 16:51 GMT+01:00 Felix Fietkau <nbd at nbd.name>:
> On 2016-12-01 16:38, Daniel Golle wrote:
> > Hi Felix,
> > On Thu, Dec 01, 2016 at 04:12:38PM +0100, Felix Fietkau wrote:
> >> On 2016-12-01 16:05, Daniel Golle wrote:
> >> > I was following your posts and do believe there is quite some overlap.
> >> > It would thus be feasible to generalize the common parts (ubus call
> >> > proxy, ubus service proxy, ubus remote monitor) by agreeing on a
> >> > interface the actual implementations shall use. In that way, people
> >> > can choose whether they want WebSockets, TR-069 or a suitable P2P
> >> > framework depending on their specific needs.
> >> > Has anything of your current approach at IOPSYS been made available
> >> > publicly (eg. on github?)
> >> >
> >> > From what I can tell there is also some overlap with Felix' proposed
> >> > System Configuration Abstraction Layer, just that my envisioned use
> >> > exceeds system configuration as it includes sensors, events and actors
> >> > rather than just access to a configuration model.
> >> If it makes sense, I'd be open to extending my abstraction layer to make
> >> it suitable for your use case as well.
> >> Feel free to propose changes to it if you like.
> > Having a first deeper look at scal I believe that access to sensors
> > and actors could be implemented inside scal similar to the existing
> > shell and system backends. That would be nice, as then scal would
> > make things available on ubus and provide the ACL mechanics.
> Nice. Maybe we can reinterpret the acronym as "System Communication
> Abstraction Layer". I'd be fine with renaming it to something else as
> well, I just didn't find a better name for it yet.
> I think a good approach would be to add a dlopen plugin API to the json
> plugin itself, so you can use json files to parameterize access to
> sensors and other devices.
> Event handling could also be scripted through .json files using
> > I'll have a deeper look and play with it to see whether that can
> > work.
> > Ideally, data collection (think: interface counters and such things
> > which need to be polled) and triggering events (think: link status
> > updates) should also be made accessible.
> > A local database which exceeds UCI state as suggested by Luka could
> > also be very useful, eg. for renewable energy or other applications
> > where loss of connectivity should never imply loss of collected data.
> Makes sense.
> - Felix
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel