Ucode support concerns

[mikehansen1970]

The ucode portion of this repository is not in line with the schema and is not updated.

The README needs to be reflected to indicate this disconnect to avoid confusing potential adapters of OLS

If the ucode portion is not going to be used at all, it should probably be removed.
If the ucode portion is to be retained, then it needs to be scrubbed clean and perhaps set up to have stubs for various pieces, and removing dependence on an OpenWrt and/or other ucentral architecture.
It could somewhat resemble the plat-example in the ols-ucentral-client, because the actual implementation could be highly variable between different systems.

Additionally the schema and state definitions would do well to have the AP specific schema elements like radios, as these are not applicable for switches.

This is a significant amount of work and would perhaps be best undertaken in phases, but it is important.

[Cahb]

Thanks Mike!
That's really an important note;

Also adding Paul into CC, maybe he would have some comments and insights as well;

@phwhite FYI

[phwhite]

Thanks @mikehansen1970 for your comments. I agree for now that we should update the README. The reason we haven't scrubbed this yet, is because I'n hoping to work with John Crispin and merge the schema changes back into a single schema for both AP and Switches. There are some complexities here, including how to handle ucode given that is an AP-only aspect.

[mikehansen1970]

Closing.
Resolved by
https://github.com/Telecominfraproject/ols-ucentral-schema/commit/adeeb0457b7060d192e4180f96eca60d562d1d15