8 odl-lispflowmapping-msmr
9 ------------------------
11 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob;f=features/odl-lispflowmapping-msmr/pom.xml
12 * **Feature Description:** This is the core feature that provides the Mapping Services and includes the LISP southbound plugin feature as well.
14 * **User Facing:** Yes
15 * **Experimental:** No
16 * **CSIT Test:** https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-msmr-all-oxygen/
18 odl-lispflowmapping-neutron
19 ---------------------------
21 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob;f=features/odl-lispflowmapping-neutron/pom.xml;hb=stable/oxygen
22 * **Feature Description:** This feature provides Neutron integration.
24 * **User Facing:** Yes
25 * **Experimental:** Yes
27 odl-lispflowmapping-ui
28 ----------------------
30 * **Feature URL:** https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob;f=features/odl-lispflowmapping-ui/pom.xml;hb=stable/oxygen
31 * **Feature Description:** This feature provides a GUI to access the Mapping Service data.
33 * **User Facing:** Yes
34 * **Experimental:** Yes
40 :ref:`lispflowmapping-user-guide`
42 Security Considerations
43 =======================
45 * Do you have any external interfaces other than RESTCONF?
46 * Yes, the southbound plugin
48 * If so, how are they secure?
49 * LISP southbound plugin follows LISP `RFC6833 <https://tools.ietf.org/html/rfc6833>`_ security guidelines.
51 * What port numbers do they use?
54 * Other security issues?
60 * `Link to Sonar Report <https://sonar.opendaylight.org/dashboard?id=org.opendaylight.lispflowmapping%3Alispflowmapping-all>`_ (59.5%)
61 * `Link to CSIT Jobs <https://jenkins.opendaylight.org/releng/view/lispflowmapping/>`_
62 * All modules have been unit tested. Integration tests have been performed for all major features. System tests have been performed on most major features.
63 * Registering and retrieval of basic mappings have been tested more thoroughly. More complicated mapping policies have gone through less testing.
69 * Is it possible to migrate from the previous release? If so, how?
71 * 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. No automated way for transfering the data is provided in this release.
76 * Is this release compatible with the previous release?
84 * Any configuration changes?
91 * `LISPMAP-151 <https://jira.opendaylight.org/browse/LISPMAP-151>`_ Subscribers from both Northbound and Southbound origin are stored in SimpleMapCache
92 * `LISPMAP-152 <https://jira.opendaylight.org/browse/LISPMAP-152>`_ Integration tests: multi-site doesn't send SMR-invoked Map-Request on SMR
93 * `LISPMAP-155 <https://jira.opendaylight.org/browse/LISPMAP-155>`_ SMR scheduler task tracking unreliable
94 * `LISPMAP-163 <https://jira.opendaylight.org/browse/LISPMAP-163>`_ Merging of negative prefixes is incorrect
95 * `LISPMAP-164 <https://jira.opendaylight.org/browse/LISPMAP-164>`_ Negative mapping in SB masking overlapping more specific positive added later to NB
96 * `LISPMAP-165 <https://jira.opendaylight.org/browse/LISPMAP-165>`_ Adding a less specific NB mapping when an included more specific SB exists leads to SB taking preference
97 * `LISPMAP-166 <https://jira.opendaylight.org/browse/LISPMAP-166>`_ Integration tests receiveMap(Request|Notify) don't check for packet type before deserializing
98 * `LISPMAP-168 <https://jira.opendaylight.org/browse/LISPMAP-168>`_ When lazy removing expired mappings, the mapping system doesn't check for less specifics
99 * `LISPMAP-169 <https://jira.opendaylight.org/browse/LISPMAP-169>`_ MapServer should not send SMR for when source EID was AFI=0 (No Address)
100 * `LISPMAP-171 <https://jira.opendaylight.org/browse/LISPMAP-171>`_ Karaf CLI commands should trigger expired mapping removal
101 * `LISPMAP-173 <https://jira.opendaylight.org/browse/LISPMAP-173>`_ NPE in MappingSystem#removeMapping()
107 * Clustering is still an experimental feature and may have some issues particularly related to operational datastore consistency.
109 * `Link to Open Bugs <https://jira.opendaylight.org/projects/LISPMAP/issues/>`_
119 * The LISP implementation module and southbound plugin conforms to the IETF `RFC6830 <https://tools.ietf.org/html/rfc6830>`_ and `RFC6833 <https://tools.ietf.org/html/rfc6833>`_ , with the following exceptions:
121 - In Map-Request message, M bit(Map-Reply Record exist in the MapRequest) is processed but any mapping data at the bottom of a Map-Request are discarded.
122 - LISP LCAFs are limited to only up to one level of recursion, as described in the IETF `LISP YANG draft <https://tools.ietf.org/html/draft-ietf-lisp-yang-07>`_.
123 - No standards exist for the LISP Mapping System northbound API as of this date.
128 * `Link to release plan <https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Oxygen_Release_Plan>`_
130 * No major shifts from the release plan.