--- /dev/null
+##################################
+Data Export/Import Developer Guide
+##################################
+
+Overview
+========
+
+This feature is used to export the system data tree state, or part of,
+to the system's file system. It may also be used to import the system
+data tree state, or part of, from the system's file system.
+
+
+Data Export/Import Architecture
+===============================
+
+The daexim feature consists of a single feature, which interacts with
+MD-SAL to export and import the system data.
+
+
+Key APIs and Interfaces
+=======================
+
+The APIs are available via REST. The details are provided are in user-guide.
+
+
+API Reference Documentation
+===========================
+
+The details of the API are also available in the YANG model for this
+feature. This model is accessiable via the APIDOC explorer interface.
capwap-developer-guide
cardinal_-opendaylight-monitoring-as-a-service
controller
+ daexim-developer-guide
didm-developer-guide
distribution-version
dlux
odl-aaa-shiro
-------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob_plain;f=features/shiro/features-aaa-shiro/src/main/features/features.xml;hb=refs/heads/stable/carbon
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob_plain;f=features/shiro/features-aaa-shiro/src/main/features/features.xml;hb=refs/heads/stable/nitrogen
* **Feature Description:** ODL Shiro-based AAA implementation
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** Yes
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-nitrogen/
odl-aaa-authn
-------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob;f=features/authn/features-aaa/src/main/features/features.xml;hb=refs/heads/stable/carbon
-* **Feature Description:** Existing AAA infrastructure, now wrapped by odl-aaa-shiro
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob;f=features/authn/features-aaa/src/main/features/features.xml;hb=refs/heads/stable/nitrogen
+* **Feature Description:** Same as odl-aaa-shiro
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** Yes
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-nitrogen/
odl-aaa-cert
------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob;f=features/authn/features-aaa/src/main/features/features.xml;hb=refs/heads/stable/carbon
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob;f=features/authn/features-aaa/src/main/features/features.xml;hb=refs/heads/stable/nitrogen
* **Feature Description:** MD-SAL based encrypted certificate management
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** Yes
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-nitrogen/
odl-aaa-cli
------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob;f=features/authn/features-aaa/src/main/features/features.xml;hb=refs/heads/stable/carbon
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=aaa.git;a=blob;f=features/authn/features-aaa/src/main/features/features.xml;hb=refs/heads/stable/nitrogen
* **Feature Description:** Basic karaf CLI commands for interacting with AAA
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** Yes
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-all-nitrogen/
Documentation
Quality Assurance
=================
-* `Link to Sonar Report <https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-sonar/>`_ (56.39% code coverage)
+* `Link to Sonar Report <https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-sonar/>`_ (54% code coverage)
* `Link to CSIT Jobs <https://jenkins.opendaylight.org/releng/view/aaa/>`_
Migration
Bugs Fixed
----------
-* `8373 <https://bugs.opendaylight.org/show_bug.cgi?id=8373>`_ Unable to start blueprint container for bundle org.opendaylight.aaa.idmlight
-* `8062 <https://bugs.opendaylight.org/show_bug.cgi?id=8062>`_ Bad padding in encrypted data
-* `8214 <https://bugs.opendaylight.org/show_bug.cgi?id=8214>`_ NPE in org.opendaylight.aaa.shiro.realm.MDSALDynamicAuthorizationFilter
-* `8313 <https://bugs.opendaylight.org/show_bug.cgi?id=8313>`_ AAA dependencies cause it not to come up
-* `8157 <https://bugs.opendaylight.org/show_bug.cgi?id=8157>`_ Deleting a user and recreating it fails using the aaa-cli-jar
-* `7527 <https://bugs.opendaylight.org/show_bug.cgi?id=7527>`_ Karaf 4 migration: provide Karaf 4 aaa features
+* `6772 <https://bugs.opendaylight.org/show_bug.cgi?id=6772>`_ When it is known some features have not activated fully, do not return 401
+* `8717 <https://bugs.opendaylight.org/show_bug.cgi?id=8717>`_ deprecate the existing mdsal AAA datastore impl
+* `8572 <https://bugs.opendaylight.org/show_bug.cgi?id=8572>`_ remove SecureBlockingQueue which is unused
+* `8724 <https://bugs.opendaylight.org/show_bug.cgi?id=8724>`_ clean AAA features
Known Issues
------------
* List key known issues with workarounds
- N/A
+* `5838 <https://bugs.opendaylight.org/show_bug.cgi?id=5838>`_ token authentication fails intermittently
* `Link to Open Bugs <https://bugs.opendaylight.org/buglist.cgi?component=General&list_id=78831&product=aaa&resolution=--->`_
Standards
=========
-* LDAP, ActiveDirectory (less tested)
+* LDAP, JDBC, ActiveDirectory (less tested)
Release Mechanics
=================
-* `Link to release plan <https://wiki.opendaylight.org/view/AAA:Carbon:Release_Plan>`_
+* `Link to release plan <https://wiki.opendaylight.org/view/AAA:Nitrogen:Release_Plan>`_
* Describe any major shifts in release schedule from the release plan
None.
odl-alto-release
----------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=alto.git;a=blob;f=alto-release-features/features-alto/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=alto.git;a=blob;f=alto-release-features/features-alto/pom.xml;hb=refs/heads/stable/nitrogen
* **Feature Description:** This is a summary feature containing the default
functionalities provided by ALTO project.
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** Yes
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/alto/job/alto-csit-1node-setup-all-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/alto/job/alto-csit-1node-setup-all-nitrogen/
Documentation
=============
Quality Assurance
=================
-* `Link to Sonar Report <https://sonar.opendaylight.org/overview?id=50636>`_ 22.0%
-* `Link to CSIT Jobs <https://jenkins.opendaylight.org/releng/view/alto/job/alto-csit-1node-setup-all-carbon/>`_
+* `Link to Sonar Report <https://sonar.opendaylight.org/overview?id=50636>`_ 31.7%
+* `Link to CSIT Jobs <https://jenkins.opendaylight.org/releng/view/alto/job/alto-csit-1node-setup-all-nitrogen/>`_
* The tests are using the OpenDaylight CSIT infrastructure.
* How extensive was it? Not very extensive since the tests are customized to
Migration
---------
-Migration with data from Boron to Carbon isn't supported.
+Migration with data from Boron isn't supported.
Compatibility
-------------
Bugs Fixed
----------
-No bug is fixed in this release.
+* `Fixed Bugs <https://bugs.opendaylight.org/buglist.cgi?bug_status=RESOLVED&chfield=%5BBug%20creation%5D&chfieldfrom=2017-05-25&chfieldto=2017-08-14&list_id=84715&product=alto&query_format=advanced&resolution=FIXED>`_
Known Issues
------------
-* `Bug 5753 <https://bugs.opendaylight.org/show_bug.cgi?id=5753>`_
+Parallel query for simple-ecs service can conduct failure.
-Both Jersey 1.0 and 2.0 are imported in karaf.
-
-This seems like a general bug which resides in several projects.
+* `Bug 8826 <https://bugs.opendaylight.org/show_bug.cgi?id=8826>`_
End-of-life
===========
-* Namespaces:
-
- * urn:opendaylight:alto:core
- * urn:opendaylight:alto:basic
-
-* Packages:
-
- * org.opendaylight.yang.gen.v1.urn.opendaylight.alto.core.*
- * org.opendaylight.yang.gen.v1.urn.opendaylight.alto.basic.*
+* Nothing deprecated, EOL.
Standards
=========
* ALTO protocols are not compatible with YANG model
* Message types for RFC 7285 have been implemented
* ALTO project provides several basic services in RFC 7285
-* Work-in-progress Internet drafts for multi-cost, incremental updates and RSA
- service are also scheduled but not fully implemented.
+* Work-in-progress Internet drafts for path-vector, multi-cost, incremental
+ updates and RSA service are also scheduled but not fully implemented.
Release Mechanics
=================
-* `Link to release plan <https://wiki.opendaylight.org/view/ALTO:Carbon_Release_Plan>`_
+* `Link to release plan <https://wiki.opendaylight.org/view/ALTO:Nitrogen_Release_Plan>`_
* Major shifts:
- * Unable to finish the extensions (multi-cost, incremental update and RSA service)
- * Unable to reach the goal of improving code quality
+ * Unable to finish the extensions (path-vector and RSA service)
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
* Not applicable as there is no previous release.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
Yes, no specific steps needed unless prior updates to config subsystem modules
were made via the controller-config yang-ext mount in which case the
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
N/A as this is first release
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
* No
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
* No. OpenDaylight doesn't support migration natively for applications that use datastore.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
No, current release is backward incompatible.
Compatibility
Quality Assurance
=================
-* `Link to Sonar Report <https://sonar.opendaylight.org/overview?id=50636>`_ (22.0% code coverage)
+* `Link to Sonar Report <https://sonar.opendaylight.org/overview?id=org.opendaylight.l2switch%3Al2switch>`_
* `Link to CSIT Jobs <https://jenkins.opendaylight.org/releng/view/l2switch/>`_
* The tests are using the OpenDaylight CSIT infrastructure.
Release Mechanics
=================
-* `Link to release plan <https://wiki.opendaylight.org/view/L2_Switch:Carbon_Release_Plan>`_
+* `Link to release plan <https://wiki.opendaylight.org/view/L2_Switch:Nitrogen_Release_Plan>`_
* No major changes.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
* LISP Flow Mapping service will auto-populate the datastructures from existing MD-SAL data upon service start if the data has already been migrated separately.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
Yes.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
Yes. No state data kept in datastore. User facing features and interfaces have not changed between releases, only
enhancements/bugfixes were added.
------------
* **Feature Name:** odl-netvirt-openstack
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netvirt.git;a=blob_plain;f=vpnservice/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=netvirt.git;a=blob;f=vpnservice/features/odl-netvirt-openstack/pom.xml;hb=HEAD
* **Feature Description:** This feature provides a network virtualization solution.
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** No
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-ocata-upstream-stateful-carbon/
Documentation
=============
* `Sonar Report <https://sonar.opendaylight.org/overview?id=64219>`_
* `All CSIT Jobs <https://jenkins.opendaylight.org/releng/view/netvirt-csit>`_
-* `Default stateful tests <https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-carbon>`_
-* `Conntrack SNAT stateful tests <https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-stateful-snat-conntrack-carbon>`_
-* `v1 tests <https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-newton-upstream-stateful-carbon>`_
-* `Learn tests <https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-learn-carbon>`_
-* `Transparent tests <https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-newton-nodl-v2-upstream-transparent-carbon>`_
+* `Main test jobs <https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-openstack-ocata-upstream-stateful-nitrogen/>`_
Migration
---------
-Nothing beyond general Carbon migration requirements.
+Nothing beyond general migration requirements.
Compatibility
-------------
-Nothing beyond general Carbon Compatibility requirements.
+Nothing beyond general compatibility requirements.
Bugs Fixed
----------
-* `Closed Bugs <https://bugs.opendaylight.org/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&component=General&list_id=78695&order=changeddate%2Cpriority%2Cbug_severity&product=netvirt&query_based_on=&query_format=advanced&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&version=Carbon>`_
+* `Closed Bugs <https://bugs.opendaylight.org/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&component=General&list_id=78695&order=changeddate%2Cpriority%2Cbug_severity&product=netvirt&query_based_on=&query_format=advanced&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&version=Nitrogen>`_
Known Issues
------------
End-of-life
===========
-* odl-ovsdb-openstack: the feature was replaced with odl-netvirt-openstack
+N/A
Standards
=========
Release Mechanics
=================
-* `Release Plan <https://wiki.opendaylight.org/view/NetVirt:Carbon:Release_Plan>`_
+* `Release Plan <https://wiki.opendaylight.org/view/NetVirt:Nitrogen:Release_Plan>`_
* Project was on schedule
Migration
---------
-* Is it possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
No as incompatble change was introduced.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
Migration with user configuration and state is not supported.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
* Yes, there is no change in config and no need to migrate data in the datastore.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
No, current release is backward incompatible.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
Yes. There are no specific migration aspects related to ODL Parent.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
There is no additional support for migration in OF-CONFIG than there is in
general. User configuration and state will need to be manually migrated when
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
Yes. `single-layer-serialization needs to be disabled <https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:OF13%2B_Single_Layer_Serialization#Enabling.2FDisabling_Single_Layer_Serialization>`_
in order to achieve same functionality as in previous release.
* OpFlex projects are tested with extensive unit testing as well as
Cisco-internal automated testing with ACI.
-* Unit tests run as part of `regular build <https://jenkins.opendaylight.org/releng/view/opflex/job/opflex-merge-carbon/34/>`_
+* Unit tests run as part of `regular build <https://jenkins.opendaylight.org/releng/view/opflex/job/opflex-merge-nitrogen/26/>`_
Migration
---------
OpFlex GBP model and configuration files remain backward compatible.
-Bugs Fixed
-----------
+Changes since previous release
+------------------------------
-* Flows that are routed are allowed to hairpin out the same interface
-* Allow working with newer compilers and development environments
-
- * Newest versions of boost remove support for comments in JSON; we
- work around this by stripping comments before doing JSON parsing
- for configuration files
- * Various changes and improvements to enable working with musl and
- alpine linux
+* Advertise external services on their interface with ARP/ND packets
+ when the interface comes up.
+* Always allow ARP and ND packets without contracts
+* Improved robustness of agent shutdown and OpenFlow socket
+ reconnections
+* Clean up endpoint-related OpenFlow rules when EPG is removed with
+ endpoint remaining
Known Issues
------------
odl-ovsdb-southbound-api
------------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=southbound/southbound-features/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=southbound/southbound-features/odl-ovsdb-southbound-api/pom.xml;h=7baad461a78e7dd311516ec03b7dbf7c9a0679aa;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature provides the YANG models for northbound users to configure the OVSDB device.
These YANG models are designed based on the `OVSDB schema <http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf>`_. This
feature does not provide the implementation of YANG models. If user/developer prefer to write their own implementation
* **Experimental:** No
* **CSIT Test:**
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-only-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-carbon/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-nitrogen/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-nitrogen/
odl-ovsdb-southbound-impl
-------------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=southbound/southbound-features/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=southbound/southbound-features/odl-ovsdb-southbound-impl/pom.xml;h=261a85eacef24c1985a11f60d018816b1f880b10;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature is the main feature of the OVSDB Southbound plugin. This plugin handle the OVS
device that supports the `OVSDB schema <http://openvswitch.org/ovs-vswitchd.conf.db.5.pdf>`_ and uses the
`OVSDB protocol <https://tools.ietf.org/html/rfc7047>`_. This feature provides the implementation of the defined YANG
* **Experimental:** No
* **CSIT Test:**
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-only-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-carbon/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-nitrogen/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-nitrogen/
odl-ovsdb-southbound-impl-rest
------------------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=southbound/southbound-features/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=southbound/southbound-features/odl-ovsdb-southbound-impl-rest/pom.xml;h=6a14e3f90fceba595695d69cdab2571e1a306999;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature is the wrapper feature that installs the odl-ovsdb-southbound-api &
odl-ovsdb-southbound-impl feature with other required features for restconf access to provide a functional OVSDB
southbound plugin. Users, who want to develop application that manages the OVSDB supported devices but want to runs
* **Experimental:** No
* **CSIT Test:**
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-only-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-carbon/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-nitrogen/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-nitrogen/
odl-ovsdb-hwvtepsouthbound-api
------------------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=hwvtepsouthbound/hwvtepsouthbound-features/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=hwvtepsouthbound/hwvtepsouthbound-features/odl-ovsdb-hwvtepsouthbound-api/pom.xml;h=e08f4233a6025da2d84dc1d87b6fb220a187e070;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature provides the YANG models for northbound users to configure the device
that supports OVSDB Hardware vTEP schema. These YANG models are designed based on the
`OVSDB Hardware vTEP schema <http://openvswitch.org/docs/vtep.5.pdf>`_. This feature does not provide the
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** Yes
-* **CSIT Test:** Currently no CSIT Tests are available, but work is in progress and will be available by nitrogen
- release.
+* **CSIT Test:** Minimal set of CSIT test is already in place. More work is in progress and will have better functional
+ coverage in Oxygen release.
+
+ * https://jenkins.opendaylight.org/releng/view/Patch-Test/job/ovsdb-patch-test-l2gw-nitrogen/
odl-ovsdb-hwvtepsouthbound
--------------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=hwvtepsouthbound/hwvtepsouthbound-features/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=hwvtepsouthbound/hwvtepsouthbound-features/odl-ovsdb-hwvtepsouthbound/pom.xml;h=3bb0d9f0093d83d0a82b3b8edffc0acfc93ee93c;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature is the main feature of the OVSDB Hardware vTep Southbound plugin. This plugin
handle the OVS device that supports the `OVSDB Hardware vTEP schema <http://openvswitch.org/docs/vtep.5.pdf>`_ and
uses the `OVSDB protocol <https://tools.ietf.org/html/rfc7047>`_. This feature provides the implementation of the
* **Top Level:** Yes
* **User Facing:** No
* **Experimental:** Yes
-* **CSIT Test:** Currently no CSIT Tests are available, but work is in progress and will be available by nitrogen
- release.
+* **CSIT Test:** Minimal set of CSIT test is already in place. More work is in progress and will have better functional
+ coverage in Oxygen release.
+
+ * https://jenkins.opendaylight.org/releng/view/Patch-Test/job/ovsdb-patch-test-l2gw-nitrogen/
odl-ovsdb-hwvtepsouthbound-rest
-------------------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=hwvtepsouthbound/hwvtepsouthbound-features/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=hwvtepsouthbound/hwvtepsouthbound-features/odl-ovsdb-hwvtepsouthbound-rest/pom.xml;h=8691103618cbe430994657016229b23c9b372d9d;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature is the wrapper feature that installs the odl-ovsdb-hwvtepsouthbound-api &
odl-ovsdb-hwvtepsouthbound feature with other required features for restconf access to provide a functional OVSDB
Hardware vTEP plugin. Users, who want to develop application that manages the hardware vTEP supported devices but want
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** Yes
-* **CSIT Test:** Currently no CSIT Tests are available, but work is in progress and will be available by nitrogen
- release.
+* **CSIT Test:** Minimal set of CSIT test is already in place. More work is in progress and will have better functional
+ coverage in Oxygen release.
+
+ * https://jenkins.opendaylight.org/releng/view/Patch-Test/job/ovsdb-patch-test-l2gw-nitrogen/
odl-ovsdb-library
-----------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=library/features/features/src/main/features/features.xml
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=ovsdb.git;a=blob;f=library/features/odl-ovsdb-library/pom.xml;h=58002499237ac290071a89ca5e0b9c9297974400;hb=refs/heads/stable/nitrogen
* **Feature Description:** Encode/decoder library for OVSDB and Hardware vTEP schema.
* **Top Level:** Yes
* **User Facing:** No
* **Experimental:** No
* **CSIT Test:**
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-only-carbon/
- * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-carbon/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-1node-upstream-southbound-all-nitrogen/
+ * https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-csit-3node-upstream-clustering-only-nitrogen/
Documentation
=============
*
* OVSDB southbound plugin is extensively tested through Unit Tests, IT test and system tests. OVSDB southbound plugin
is tested in both single node setup as well as three node cluster setup. Hardware vTEP plugin is currently tested
- through (1) Unit testing (2) NetVirt project L2 Gateway features CSIT tests and (3) Manual Testing.
- (2) https://jenkins.opendaylight.org/releng/view/netvirt/job/netvirt-csit-hwvtep-1node-openstack-newton-nodl-v2-upstream-stateful-carbon
+ through (1) Unit testing (2) CSIT Tests (3) NetVirt project L2 Gateway features CSIT tests and (4) Manual Testing.
+ (3) https://jenkins.opendaylight.org/releng/view/netvirt/job/netvirt-csit-hwvtep-1node-openstack-newton-nodl-v2-upstream-stateful-nitrogen/
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
Yes. User facing features and interfaces are not changed, only enhancements are done.
Compatibility
-------------
-* Is this release compatible with the previous release? No
-* Any API changes? No changes in the YANG models from previous release. Only one minor enhancement is being done.
- https://git.opendaylight.org/gerrit/#/c/50993/
+* Is this release compatible with the previous release? Yes
+* Any API changes? No changes in the YANG models from previous release.
* Any configuration changes? No
----------
* List of bugs fixed since the previous release
- https://bugs.opendaylight.org/buglist.cgi?chfieldfrom=2016-08-09&chfieldto=2017-05-25&list_id=78767&product=ovsdb&query_format=advanced&resolution=FIXED
+ https://bugs.opendaylight.org/buglist.cgi?chfieldfrom=2017-05-25&chfieldto=2017-09-10&list_id=78767&product=ovsdb&query_format=advanced&resolution=FIXED
Known Issues
------------
Release Mechanics
=================
-* `Link to release plan <https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Carbon_Release_Plan>`_
-* Describe any major shifts in release schedule from the release plan
-
- We planned to do some exploratory work to improve the performance, scalability and robustness, but it didn't make the
- expected progress in this release. Project will continue this effort in the next release.
+* `Link to release plan <https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Nitrogen_Release_Plan>`_
Migration
---------
-* Is is possible migrate from the previous release? Yes
+* Is it possible to migrate from the previous release? Yes
* Migration from PacketCable Boron version to Carbon version can be
accomplished by replacement of the PacketCable plugin components.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
.. note:: This is asking if somebody can move from an installation of the
previous release while keeping data. This isn't currently, natively
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
It is possible to seamlessly migrate consumers to this iteration of the plug-in as there has been no functional
change to features. Migration of state data is not defined.
Migration\r
---------\r
\r
-* Is is possible migrate from the previous release? If so, how?\r
+* Is it possible to migrate from the previous release? If so, how?\r
\r
Yes. Features as well as interfaces are not changed.\r
\r
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
* Yes, no data models were changed that would break the migration.
Migration
---------
-* Is it possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
* Yes, since there's no change of features from the previous releases.
Migration
---------
-* Is is possible migrate from the previous release? If so, how?
+* Is it possible to migrate from the previous release? If so, how?
While it should be possible to export all TTP-related information by doing
RESTCONF GETs and then import it by doing RESTCONF PUTs after the fact, this
Migration
---------
-* Is is possible migrate from the previous release?
+* Is it possible to migrate from the previous release?
No, Current release is backward incompatible.
Compatibility
odl-vbd
-------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=honeycomb/vbd.git;a=blob;f=features/vbd-features/src/main/features/features.xml;hb=refs/heads/stable/carbon
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=honeycomb/vbd.git;a=blob;f=features/odl-vbd/src/main/feature/feature.xml;h=37a666153982e4efa38a37ca0b971be5d5cbdcd6;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature provides models to configure Virtual Bridge Domains on VPP.
* **Top Level:** Yes
* **User Facing:** Yes
odl-vbd-ui
----------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=honeycomb/vbd.git;a=blob;f=features/vbd-features/src/main/features/features.xml;hb=refs/heads/stable/carbon
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=honeycomb/vbd.git;a=tree;f=features/odl-vbd-ui;h=a6172d7fb3d2c1930b0a87213b7043f58a711f60;hb=refs/heads/stable/nitrogen
* **Feature Description:** This feature provides the GUI for VBD.
* **Top Level:** Yes
* **User Facing:** Yes
* VBD project is tested within `FastDataStacks (FDS) <https://wiki.opnfv.org/display/fds/FastDataStacks+Home>`_ testing suite, where severeal automated
tests are performed. More information about FDS testing can be found here:
`FDS testing <https://wiki.opnfv.org/display/fds/FDS+Testing>`_ and test
- results are available here: `FDS test results <http://testresults.opnfv.org/reporting/functest/release/danube/index-status-apex.html>`_
+ results are available here: `FDS test results <http://testresults.opnfv.org/reporting/master/functest/status-apex.html>`_
* FDS automated tests perform series of functests where the whole stack is
beeing tested (Openstack/ODL (GBP,VBD)/HC/VPP).
Migration
---------
-* Please upgrade to VPP 17.04 stable.
+* Please use VPP 17.04 stable.
Compatibility
-------------
Bugs Fixed
----------
-* `Bug 6077 <https://bugs.opendaylight.org/show_bug.cgi?id=6077>`_ RESOLVED Bridge domain is not created when topology and node are created at the same time
-* `Bug 6078 <https://bugs.opendaylight.org/show_bug.cgi?id=6078>`_ RESOLVED BVI is set to true and should be false when creating VXLAN tunnel
-* `Bug 6101 <https://bugs.opendaylight.org/show_bug.cgi?id=6101>`_ RESOLVED Error when creating VLAN flood domain
-* `Bug 6104 <https://bugs.opendaylight.org/show_bug.cgi?id=6104>`_ RESOLVED Ip addresses nullPointerException
-* `Bug 6105 <https://bugs.opendaylight.org/show_bug.cgi?id=6105>`_ RESOLVED Error when removing nodes from bridge domain
-* `Bug 6241 <https://bugs.opendaylight.org/show_bug.cgi?id=6241>`_ RESOLVED Split horizon group is not set for VXLAN tunnel interfaces
-* `Bug 6285 <https://bugs.opendaylight.org/show_bug.cgi?id=6285>`_ RESOLVED HONEYCOMB/VBD Missing from Distribution Feature Index
-* `Bug 6591 <https://bugs.opendaylight.org/show_bug.cgi?id=6591>`_ RESOLVED VXLAN tunnels are not created correctly
-* `Bug 7117 <https://bugs.opendaylight.org/show_bug.cgi?id=7117>`_ RESOLVED Cannot add Virtual Bridge Domains in DLUX
-* `Bug 7118 <https://bugs.opendaylight.org/show_bug.cgi?id=7118>`_ RESOLVED Cannot remove VPP from inventory in DLUX
-* `Bug 7148 <https://bugs.opendaylight.org/show_bug.cgi?id=7148>`_ RESOLVED VBD Carbon Autorelease Build Failure
-* `Bug 7655 <https://bugs.opendaylight.org/show_bug.cgi?id=7655>`_ RESOLVED Karaf 4 migration: provide Karaf 4 honeycomb-vbd features
-* `Bug 8009 <https://bugs.opendaylight.org/show_bug.cgi?id=8009>`_ RESOLVED Mismatched VXLAN tunnel endpoint addresses
-* `Bug 8167 <https://bugs.opendaylight.org/show_bug.cgi?id=8167>`_ RESOLVED Default startup configuration file not created
-* `Bug 8172 <https://bugs.opendaylight.org/show_bug.cgi?id=8172>`_ RESOLVED VBD missing yangs for configuring LISP in VPP
-* `Bug 8173 <https://bugs.opendaylight.org/show_bug.cgi?id=8173>`_ RESOLVED Mismatch of v3po yangs between vbd and hc2vpp
-* `Bug 8354 <https://bugs.opendaylight.org/show_bug.cgi?id=8354>`_ RESOLVED Feature installs fails if installed in a particular order
+* N/A
Known Issues
Release Mechanics
=================
-* `Release plan <https://wiki.opendaylight.org/view/Honeycomb/VBD/Carbon/Release_Plan>`_
+* `Release plan <https://wiki.opendaylight.org/view/Honeycomb/VBD/Nitrogen/Release_Plan>`_
* no major shifts from official release plan
odl-vtn-manager-rest
--------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=vtn.git;a=blob;f=manager/features/features-vtn-manager/src/main/features/features.xml;hb=refs/heads/stable/carbon#l41
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=vtn.git;a=blob;f=manager/features/odl-vtn-manager-rest/pom.xml;h=c130771e9dbc0d77dddf9b81a65d1a0c9aab936c;hb=refs/heads/stable/nitrogen#l24
* **Feature Description:** This is the feature that allows users to use the VTN virtualization, by creating the various components as needed for the network.
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** No
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-carbon/,https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-nitrogen/
odl-vtn-manager-neutron
----------------------
-* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=vtn.git;a=blob;f=manager/features/features-vtn-manager/src/main/features/features.xml;hb=refs/heads/stable/carbon#l49
+* **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=vtn.git;a=blob;f=manager/features/odl-vtn-manager-neutron/pom.xml;h=600411e41a52ddc8ac90e9a3c5c58b73ed774b8c;hb=refs/heads/stable/nitrogen#l24
* **Feature Description:** This feature provides support for integration with Openstack (L2 API)
* **Top Level:** Yes
* **User Facing:** Yes
* **Experimental:** No
-* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-openstack-newton-neutron-carbon/
+* **CSIT Test:** https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-openstack-newton-neutron-nitrogen/
Documentation
=============
Bugs Fixed
----------
-* 6632 - VTN Coordinator Build Issues with Fedora 24
-* 7360 - VTN Coordinator Build Issues in Fedora 25
-* 7402 - VTN Coordinator Tomcat Upgrade to 7.0.73
-* 6859 - Clean up package names across ODL for yangtools
-* 7969 - VTN Coordinator Issues with recent Postgres Versions
-* 7652 - VTN Manager Support for Karaf 4
-* 8191 - VTN Manager Addressed some Checkstyle/findbugs warnings
-* 8184 - VTN Manager Removed some log messages when handling send-barrier RPC
-* 8211 - VTN Manager Addressed Problems in mapping VTN Flow and MD-SAL Flow
-* 8212 - VTN Manager Fixed Failure in retrieving dataflow
+* 8761 - VTN coordinator Portmapping fails due to unnecessary hex conversion.
+* 9024 - VTN Manager Set null to bundle version qualifier if it is empty.
Known Issues
------------
Release Mechanics
=================
-* `Link to release plan <https://wiki.opendaylight.org/view/VTN:Carbon_Release_Plan>`_
+* `Link to release plan <https://wiki.opendaylight.org/view/VTN:Nitrogen_Release_Plan>`_
* There was no deviation from the plan.
-Subproject commit 65a096241e6b9cd95c5b7ec58546de7903733d72
+Subproject commit 71ffcd312c8b5d2664f0c54e1567ff7afeae3b98
-Subproject commit b2d2c126937a5c82968fa2916670d9acf5f477d4
+Subproject commit d22a1e6bb1e0e4aca88ac4d8b0f987b2961935fd
-Subproject commit 425ca4c699ac50e25c1088c771fea6bd143ac46d
+Subproject commit 4c03afdd2ef06285308e7c5b23959dea54480cb4
-Subproject commit 17ae810169063a610a7f51f64f1cdd698dc972b4
+Subproject commit a1b6d1136f3cdafd468160b450071fa59e7f7b63
-Subproject commit 137712fe4ad0e3fb9c62c8e41ea32c1bd4631288
+Subproject commit e75b6a918589cb706e15c14eb914ac4b4d24a03c
-Subproject commit d0d271000d280c8355a965ab9598f449b40aa8e9
+Subproject commit 07baece077510d6015fcc3da8784e2360bf57bc3
-Subproject commit 7c395d93426d408774673d0072c2a8053622cb00
+Subproject commit cd3f77e3f959383441bf979129372d2d25216230
-Subproject commit 93ca49e6a2382eb5412813485f1f6da1c27d87f0
+Subproject commit c9912dd1d528b91c7b5f67f1b3156b586f92d15f
-Subproject commit 623eacaf8b8af6604ec60040ac25412b1b1dcc18
+Subproject commit 0e56096caa76334e1de7d88e3def81fa722024d0
--- /dev/null
+Data Export/Import User Guide
+=============================
+
+
+Overview
+--------
+
+The Data Export/Import is known as "daexim" (pronounced 'deck-sim') for
+short. The intended audience are administrators responsible for
+operations of OpenDaylight.
+
+Data Export/Import provides an API (via RPCs) to request the bulk
+transfer of OpenDaylight system data between its internal data stores
+and the local file system. This can be used for scheduling data exports,
+checking the status of data being exported, canceling data export jobs,
+importing data from files in the file systems, and checking the import
+status.
+
+Such export and import of data can be used during system upgrade,
+enabling the development of administrative procedures that make
+reconfigurations of the base system without concern of internal data
+loss.
+
+Data Export produces a models declaration file and one or more data
+files. The models declaration file records exactly which YANG models
+were loaded (by module name, revision date and namespace). The data
+file(s) contain data store data as per the draft-ietf-netmod-yang-json
+RFC.
+
+Data Import takes a models declaration file and zero or more data
+files. The models declaration file is used to check that the listed
+models are loaded before importing any data. Data is imported into each
+data store in turn with one transaction executed for each data store,
+irrespective of the number of files for that data store, as inter-module
+data dependencies may exist. Existing data store data may be cleared
+before importing.
+
+
+Data Export Import Architecture
+-------------------------------
+
+The daexim feature is a single feature. This feature leverages the
+existing infrastructure provided by MD-SAL and yangtools.
+
+
+Installing the Feature
+----------------------
+
+To install the feature perform the following steps.
+
+.. code:: bash
+
+ karaf > feature:install odl-daexim-all
+
+
+The interactions with this feature are via Restconf RPCs. The details
+are provided in the `Tutorials`.
+
+
+Tutorials
+---------
+
+The following tutorials provide examples of REST API that are supported
+by the Data Export/Import feature. As for all ODL RESTCONF calls, the
+following are the common setting for REST calls:
+
+* Headers:
+ * Content-Type: application/json
+ * Accept: application/json
+ * Authentication: admin:admin
+* Method: HTTP POST
+* <controller-ip> : Host (or IP) where OpenDaylight controller is
+ running, e.g. localhost
+* <restconf-port> : TCP port where RESTCONF has been configured to
+ listen, e.g. 8181 by default
+
+The files created by export are placed in a subdirectory called
+*daexim/* in the installation directory of OpenDaylight. Similarly files
+to import must be placed in this *daexim/* subdirectory.
+
+
+
+Scheduling Export
+^^^^^^^^^^^^^^^^^
+
+The **schedule-export** RPC exports the data at a specific time in the
+future. The *run-at* time may be specified as an absolute UTC time or a
+relative offset from the server clock. Attempts to schedule an export in
+the past times are rejected. Each file has a JSON-encoded object that
+contains module data from the corresponding data store. Module data is
+not included in the object for any module identified in the exclusion
+list. Each file contains at least one empty JSON object.
+
+URL:
+ http://<controller-ip>:<restconf-port>/restconf/operations/data-export-import:schedule-export
+
+Payload:
+
+.. code:: json
+
+ {
+ "input": {
+ "data-export-import:run-at": 500
+ }
+ }
+
+
+
+Checking Export Status
+^^^^^^^^^^^^^^^^^^^^^^
+
+The **status-export** RPC checks the status of the exported data. If the
+status has the value of *initial*, an export has not been scheduled. If
+the status has the value of *scheduled*, *run-at* indicates the time at
+which the next export runs. If the status has the value of
+*in-progress*, *run-at* indicates the time at which the running export
+was scheduled to start. A status of *tasks* indicates activities that
+are scheduled and currently being performed. The *tasks* status serves
+as an indicator of progress and success of the activity. If the status
+has any other value, *run-at* indicates the time at which the last
+export was scheduled to start; and *tasks* indicates the activities that
+were undertaken. If the status for any node has failed, the
+corresponding reason for failure is listed.
+
+URL:
+ http://<controller-ip>:<restconf-port>/restconf/operations/data-export-import:status-export
+
+Payload:
+ No payload
+
+
+
+Canceling Scheduled Export
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The **cancel-export** RPC cancels an already scheduled data export
+job. To cancel the export, the server stops the tasks that are running
+(where possible, immediately), clears any scheduled export time value,
+and releases the associated resources. This RPC may be called at any
+time, whether an export is in progress, scheduled or not yet
+scheduled. The returned result is *True* when the server has
+successfully cleared tasks, the state, and resources. The status is
+*False* on failure to do so. Note that if no export is scheduled or
+running, there is no tasks for the server to clear. Therefore, the
+return result is *True* because the server cannot fail.
+
+URL:
+ http://<controller-ip>:<restconf-port>/restconf/operations/data-export-import:cancel-export
+
+Payload:
+ No payload
+
+
+Import from a file
+^^^^^^^^^^^^^^^^^^
+
+The **immediate-import** RPC imports data from files already present in
+the file system.
+
+URL:
+ http://<controller-ip>:<restconf-port>/restconf/operations/data-export-import:immediate-import
+
+Payload:
+
+.. code:: json
+
+ {
+ "input" : {
+ "check-models" : true,
+ "clear-stores" : "all"
+ }
+ }
+
+
+
+
+Status of Import
+^^^^^^^^^^^^^^^^
+
+The **status-import** RPC checks the last import status. If the status
+has the value of *initial*, an import has not taken place. For all other
+values of status, *imported-at* indicates the time at which the
+restoration has taken place. List nodes hold status about the
+restoration for each node.
+
+URL:
+ http://<controller-ip>:<restconf-port>/restconf/operations/data-export-import:status-import
+
+Payload:
+ No payload
capwap-user-guide
cardinal_-opendaylight-monitoring-as-a-service
centinel-user-guide
+ daexim-user-guide
didm-user-guide
eman-user-guide
fabric-as-a-service
different approach for NETCONF message handling and data
translation. These 2 components will probably merge in the future.
+.. note::
+
+ Since Nitrogen release, there is performance regression in NETCONF
+ servers accepting SSH connections. While opening a connection takes
+ less than 10 seconds on Carbon, on Nitrogen time can increase up to
+ 60 seconds. Please see https://bugs.opendaylight.org/show_bug.cgi?id=9020
+
NETCONF server for config-subsystem
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Code Review / docs.git / commitdiff