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
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.
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.
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