Thanks for the detailed reply, this is very useful.
So setting up devices is one thing I'd be interested in
Sounds great, this is the first use-case I'm working towards currently. A very simple declarative provisioning system.
but also monitoring of wireless clients. On which AP are clients connected? How's the roaming history? I've currently got DAWN running in all AP's, all AP's also have the Luci-app for DAWN installed but it's not really intuitive to see in a simple overview (graphically) on which AP and radio/channel a client is connected, it's basically a big list of SSID's and MAC addresses with percentages. I need to stare at it for minutes to understand what's going on.
I think this would certainly be a very useful feature, and shouldn't be too hard to implement.
What's also something I'd be very interested in, is SQM usage; when getting SQM right, it involves knowledge of different qdiscs and how to interpret the values the
tc -s qdisc command produces.
This is an interesting case which I've not considered before, could most certainly implement this.
I'm not a developer, but what I would consider for such a project is to keep it simple and reuse existing techniques to get the job done. Would you consider UCI via SSH, or Ansible for instance? What would be required to run the controller itself? Is it possible to create it so lightweight it might run even on a OpenWRT router itself with 2 cores and at least 512MB of RAM for instance? Or do you need at least 2GB of RAM and 3GB of disk space for the controller software to run? Is it intended to run inside the home network, or is it (also) offered as a cloud service? I'd prefer to be fully in control of my own home network, no spying eyes, no cloud services that need monthly fees...
I'm planning to make the controller as simple and lightweight as possible at least initially. I'll most probably start with UCI over SSH as an initial provisioning mechanism, but could also look at re-purposing the OpenWISP backend for OpenWRT. I think at least initially, resource requirements would be very small, probably run-able on single core with >=256MB RAM, probably <100MB disk space so the controller could possibly run on larger OpenWRT devices, and other platforms like Pi's etc. Perhaps down the line I could offer some sort of cloud service, similar to UniFi, and charge a fair fee for that, but the software would otherwise be completely open source and self host-able.
These are just some ramblings, don't know if this is what you're looking for?
This is exactly the kind of feedback I am looking for, thank you very much!