NETCONF

Major Features

For each top-level feature, identify the name, URL, description, etc. User-facing features are used directly by end users.

odl-netconf-topology

  • Feature URL: NETCONF Topology

  • Feature Description: NETCONF southbound plugin single-node, configuration through MD-SAL.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: No

  • CSIT Test: NETCONF CSIT

odl-netconf-clustered-topology

  • Feature URL: Clustered Topology

  • Feature Description: NETCONF southbound plugin clustered, configuration through MD-SAL.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: Yes

  • CSIT Test: Cluster CSIT

odl-netconf-console

  • Feature URL: Console

  • Feature Description: NETCONF southbound configuration with Karaf CLI.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: Yes

odl-netconf-mdsal

  • Feature URL: MD-SAL

  • Feature Description: NETCONF server for MD-SAL.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: No

  • CSIT Test: MD-SAL CSIT

odl-restconf

  • Feature URL: RESTCONF

  • Feature Description: RESTCONF

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: No

  • CSIT Test: Tested by any suite that uses RESTCONF.

odl-mdsal-apidocs

  • Feature URL: API Docs

  • Feature Description: MD-SAL - apidocs

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: No

odl-yanglib

  • Feature URL: YANG Lib

  • Feature Description: Yanglib server.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: No

odl-netconf-callhome-ssh

  • Feature URL: Call Hhome SSH

  • Feature Description: NETCONF Call Home.

  • Top Level: Yes

  • User Facing: Yes

  • Experimental: No

  • CSIT Test: Call Home CSIT.

Documentation

Security Considerations

  • Do you have any external interfaces other than RESTCONF?

    Yes, we have MD-SAL and CSS NETCONF servers. Also, a server for NETCONF Call Home.

    • If so, how are they secure?

      • NETCONF over SSH

    • What port numbers do they use?

      • Refer to Ports. NETCONF Call Home uses TCP port 6666.

  • Other security issues?

    • None

Quality Assurance

Migration

  • Is it possible to migrate from the previous release? If so, how?

    • Yes. No additional steps required.

Compatibility

  • Is this release compatible with the previous release?

    • Yes

  • Any API changes?

    • No

  • Any configuration changes?

    • No

Bugs Fixed

  • List of bugs fixed since the previous release.

Known Issues

  • List key known issues with workarounds.

End-of-life

List of features/APIs that were EOLed, deprecated, and/or removed from this release:

  • The RFC8040 RESTCONF endpoint has been promoted to stable, which marks its first release. Its un-authenticated feature has been removed.

  • Since this endpoint corresponds to a published standard and supports various YANG 1.1 features, we will be transitioning to it.

  • To that effect, the bierman02 endpoint is now deprecated, and users should start testing and migrating to the RFC8040 endpoint.

  • The old endpoint will not be removed for at least two releases, after which we will re-evaluate the cost of carrying this code.

Standards

Release Mechanics