Well, before I write out a formal proposal… What about storing Openwrt configs 
natively in YANG and then synthesizing appropriate config files out of that for 
various subsystems (Ssh, network, firewall, DHCP, etc)?

We would probably need bi-directional conversion from YANG to UCI, etc. so that 
if someone pushed a config into the box using Netconf, but then ssh’d into it 
and looked at the UCI files, the UCI files would be coherent with the 
“authoritative” configuration.

Likewise, if someone edited the UCI and then restarted a subsystem, the YANG 
source-of-truth would get upgraded internally (and be visible in LUA, etc).

For certain things, UCI is a bit limiting in terms of what sort of 
configuration state you can express.

Especially if there are multiple levels of nesting.

And yes, I realize I just contradicted myself: I’m advocating for more powerful 
configurations which *couldn’t* then be re-exported back into UCI.  Maybe it’s 
worth abandoning UCI altogether?

Or having an import script which ingests and converts your UCI and then deletes 

Don’t know.  These seem like the sort of questions to be looked at during a 
GSoC project.


> On Feb 13, 2018, at 5:10 AM, Andreas Bräu <a...@andi95.de> wrote:
> Hi there,
> we've been accepted again for Google Summer of Code 2018. To see our
> ideas and possible projects, please visit
> https://projects.freifunk.net/#/projects
> What is Google Summer of Code?
> "Google Summer of Code is a global program focused on bringing more
> student developers into open source software development. Students work
> with an open source organization on a 3 month programming project during
> their break from school."
> If you're student and interested this program, please get in touch with
> us or our mentors.
> See also: https://summerofcode.withgoogle.com/organ…/4687947786354688/
> BTW: It's still possible to submit your own ideas! To do so, please
> submit a pull request at
> https://github.com/freifunk/projects.freifunk.net-contents
> Thanks,
> Andi
openwrt-devel mailing list

Reply via email to