... | ... | @@ -61,6 +61,11 @@ the same as on any other platform: |
|
|
non-homogeneous networks, provided that all devices support RESTCONF
|
|
|
and implement the data models.
|
|
|
|
|
|
A number of YANG modules that already are (or will soon be) published
|
|
|
as RFCs may be potentially useful for OpenWRT routers. A
|
|
|
non-exhaustive selection can be found in the
|
|
|
[Appendix](#appendix-standard-yang-modules).
|
|
|
|
|
|
## Deployment Options
|
|
|
|
|
|
Three main deployment options may be considered (combinations are
|
... | ... | @@ -76,6 +81,59 @@ possible, too): |
|
|
1. Use a system like [Sysrepo](http://www.sysrepo.org/) for improving
|
|
|
back-end integration of deamons and services.
|
|
|
|
|
|
## Hardware-Related Considerations
|
|
|
The first option is relatively light-weight in that it doesn't change
|
|
|
anything in OpenWRT itself, just adds an extra configuration layer. It
|
|
|
could be used only for configuration as there is in general no easy
|
|
|
way for translating state data emitted by daemons into the format
|
|
|
that's expected by standard models.
|
|
|
|
|
|
On the other hand, the extra layer added by option #1 increases the
|
|
|
complexity of the whole system and, since the flow of data is still
|
|
|
only in one direction, it just amplifies the problems of UCI mentioned
|
|
|
above. For example, if an admin directly edits a generated UCI file,
|
|
|
this change
|
|
|
|
|
|
## Available RESTCONF Implementations
|
|
|
|
|
|
## Hardware-Related Considerations
|
|
|
|
|
|
## Appendix: Standard YANG Modules
|
|
|
|
|
|
* [ietf-yang-types](https://tools.ietf.org/html/rfc6991#section-3) –
|
|
|
common data types such as `hex-number` or `dotted-quad`, integer
|
|
|
parameters with special semantics (counters, gauges).
|
|
|
|
|
|
* [ietf-inet-types](https://tools.ietf.org/html/rfc6991#section-4) –
|
|
|
data types related to TCP/IP (addresses, ports) and other
|
|
|
Internet-related parameters.
|
|
|
|
|
|
* [ietf-interfaces](https://tools.ietf.org/html/rfc7223#section-5) –
|
|
|
interface management (all layers).
|
|
|
|
|
|
* [ietf-ip](https://tools.ietf.org/html/rfc7277#section-4) –
|
|
|
static configuration and management of IPv4/IPv6 on L3 interfaces.
|
|
|
|
|
|
* [ietf-routing](https://tools.ietf.org/html/rfc8022) – basic
|
|
|
configuration and management of the routing subsystem, static routes
|
|
|
(for both IPv4 and IPv6).
|
|
|
|
|
|
* [ietf-access-control-list](https://tools.ietf.org/html/draft-ietf-netmod-acl-model-09#section-4) –
|
|
|
access control lists, packet filters.
|
|
|
|
|
|
* [ietf-dhcpv6](https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-yang-03#section-3) –
|
|
|
DHCPv6.
|
|
|
|
|
|
* [ietf-logical-network-element](https://tools.ietf.org/html/draft-ietf-rtgwg-lne-model-01#section-6) –
|
|
|
management of virtual machines and NFV.
|
|
|
|
|
|
* [ietf-rip](https://tools.ietf.org/html/draft-ietf-rtgwg-yang-rip-02#section-3) –
|
|
|
RIP routing protocol.
|
|
|
|
|
|
* [ietf-ospf](https://tools.ietf.org/html/draft-ietf-ospf-yang-06#section-4) –
|
|
|
OSPF routing protocol.
|
|
|
|
|
|
* [ietf-isis](https://tools.ietf.org/html/draft-ietf-isis-yang-isis-cfg-14#section-6) –
|
|
|
IS-IS routing protocol.
|
|
|
|
|
|
* [ietf-snmp](https://tools.ietf.org/html/rfc7407#section-4.2) – SNMP
|
|
|
monitoring. |