8 For each top-level feature, identify the name, url, description, etc.
9 User-facing features are used directly by end users.
14 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/netconf-connector/odl-netconf-topology/pom.xml;hb=refs/heads/stable/nitrogen
15 * **Feature Description:** NETCONF southbound plugin single-node, configuration through mdsal
17 * **User Facing:** Yes
18 * **Experimental:** No
19 * **CSIT Test:** https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-nitrogen/
21 odl-netconf-clustered-topology
22 ------------------------------
24 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/netconf-connector/odl-netconf-clustered-topology/pom.xml;hb=refs/heads/stable/nitrogen
25 * **Feature Description:** NETCONF southbound plugin clustered, configuration through mdsal
27 * **User Facing:** Yes
28 * **Experimental:** Yes
29 * **CSIT Test:** https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-nitrogen/
34 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/netconf-connector/odl-netconf-console/pom.xml;hb=refs/heads/stable/nitrogen
35 * **Feature Description:** NETCONF southbound configuration with karaf cli
37 * **User Facing:** Yes
38 * **Experimental:** Yes
43 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/netconf/odl-netconf-mdsal/pom.xml;hb=refs/heads/stable/nitrogen
44 * **Feature Description:** NETCONF server for mdsal
46 * **User Facing:** Yes
47 * **Experimental:** No
48 * **CSIT Test:** https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-userfeatures-all-nitrogen/
53 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/restconf/odl-restconf/pom.xml;hb=refs/heads/stable/nitrogen
54 * **Feature Description:** Restconf
56 * **User Facing:** Yes
57 * **Experimental:** No
58 * **CSIT Test:** Tested by any suite that uses Restconf
63 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/restconf/odl-mdsal-apidocs/pom.xml;hb=refs/heads/stable/nitrogen
64 * **Feature Description:** MDSal - apidocs
66 * **User Facing:** Yes
67 * **Experimental:** No
72 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/yanglib/odl-yanglib/pom.xml;hb=refs/heads/stable/nitrogen
73 * **Feature Description:** Yanglib server
75 * **User Facing:** Yes
76 * **Experimental:** No
78 odl-netconf-callhome-ssh
79 ------------------------
81 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netconf.git;a=blob;f=features/netconf-connector/odl-netconf-callhome-ssh/pom.xml;hb=refs/heads/stable/nitrogen
82 * **Feature Description:** Netconf call home
84 * **User Facing:** Yes
85 * **Experimental:** No
86 * **CSIT Test:** https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-callhome-all-nitrogen/
92 Please provide the URL to each document at docs.opendaylight.org. If the
93 document is under review, provide a link to the change in Gerrit.
97 * :ref:`netconf-user-guide`
99 * **Developer Guide(s):**
101 * :ref:`netconf-dev-guide`
103 Security Considerations
104 =======================
106 * Do you have any external interfaces other than RESTCONF?
108 Yes, we have md-sal and css netconf servers. Also server for netconf call-home.
110 * If so, how are they secure?
114 * What port numbers do they use?
116 Please see https://wiki.opendaylight.org/view/Ports. Netconf call-home uses TCP port 6666
118 * Other security issues?
120 None that we are aware of
125 * `Link to Sonar Report <https://sonar.opendaylight.org/overview?id=54548>`_ Test coverage percent: 63.3%
126 * `Link to CSIT Jobs <https://jenkins.opendaylight.org/releng/view/netconf/>`_
131 * Is it possible to migrate from the previous release? If so, how?
135 Several config subsystem yang modules were removed therefore if prior updates to
136 config subsystem modules were made via the controller-config loopback mountpoint
137 then the etc/opendaylight/current/controller.currentconfig.xml file must be manually
138 edited to remove elements corresponding to the removed config yang modules.
139 These include the elements from the following XML files under
140 etc/opendaylight/karaf:
142 * 10-rest-connector.xml
143 * 10-restconf-service.xml
145 The mechanism of spawning netconf connectors via the controller-config loopback
146 mountpoint was removed so any previously configured connectors must be migrated to the
147 config datastore and the elements removed from the controller.currentconfig.xml file.
149 The netconf yanglib config subsystem module was removed so any configuration change
150 that was made via the controller-config loopback mountpoint must be migrated to the
151 config datastore (see the Compatibility section) and must also be removed from the
152 controller.currentconfig.xml file.
154 Since the config subsystem is deprecated, it is recommended to migrate any custom
155 configuration additions and/or changes contained in controller.currentconfig.xml
161 * Is this release compatible with the previous release?
169 * Any configuration changes?
171 * The restconf northbound feature is now started via blueprint instead of the config
172 subsystem. The corresponding config yang file, opendaylight-rest-connector.yang,
173 and the 10-rest-connector.xml file installed under etc/opendaylight/karaf have been
174 removed. The restconf configuration attributes (specifically websocket-port) are
175 now specified via the etc/org.opendaylight.restconf.cfg file.
177 * The JSONRestconfService API is no longer advertised via the config subsystem and
178 the corresponding config yang file, sal-restconf-service.yang, and the
179 10-restconf-service.xml file installed under etc/opendaylight/karaf have been
180 removed. The JSONRestconfService must now be obtained directly from the OSGi
181 service registry (preferably via blueprint).
183 * The netconf yanglib feature is now now started via blueprint instead of the config
184 subsystem and is configured using the yanglib:yanglib-config container defined in
185 yanglib.yang via the config datastore.
190 * List of bugs fixed since the previous release
192 https://bugs.opendaylight.org/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&chfield=resolution&chfieldfrom=2017-07-12&chfieldto=Now&chfieldvalue=FIXED&list_id=78801&product=netconf&query_format=advanced&resolution=FIXED
197 * List key known issues with workarounds
201 * `Link to Open Bugs <https://bugs.opendaylight.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&list_id=78793&product=netconf&query_format=advanced&resolution=--->`_
206 * List of features/APIs which are EOLed, deprecated, and/or removed in this
209 The mechanism of spawning netconf connectors via the config subsystem's
210 controller-config loopback mountpoint was deprecated in the previous release and
216 * `RFC 6241 <https://tools.ietf.org/html/rfc6241>`_ - Network Configuration Protocol (NETCONF)
217 * `RFC 6470 <https://tools.ietf.org/html/rfc6470>`_ - Base Notifications partly supported, netconf-config-change unsupported
218 * `draft-ietf-yang-library-06 <https://tools.ietf.org/html/draft-ietf-netconf-yang-library-06>`_
219 * `draft-bierman-netconf-restconf-04 <https://tools.ietf.org/html/draft-bierman-netconf-restconf-04>`_
220 * `RFC 8040 <https://tools.ietf.org/html/rfc8040>`_ - RESTCONF protocol
226 * `Link to release plan <https://wiki.opendaylight.org/view/NETCONF:Nitrogen:Release_Plan>`_
227 * Describe any major shifts in release schedule from the release plan