LISP Flow Mapping¶

Major Features¶

Feature URL: https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob;f=features/features-lispflowmapping/src/main/features/features.xml
Feature Description: This is the core feature that provides the Mapping Services and includes the LISP southbound plugin feature as well.
Top Level: Yes
User Facing: Yes
Experimental: No
CSIT Test: https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-msmr-all-carbon/

Feature URL: https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob;f=features/features-lispflowmapping/src/main/features/features.xml
Feature Description: This feature provides neutron integration.
Top Level: Yes
User Facing: Yes
Experimental: Yes

Feature URL: https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob;f=features/features-lispflowmapping/src/main/features/features.xml
Feature Description: This feature provides a GUI to access the Mapping Service data.
Top Level: Yes
User Facing: Yes
Experimental: Yes

Do you have any external interfaces other than RESTCONF?
Yes, the southbound plugin
- If so, how are they secure? * LISP southbound plugin follows LISP RFC6833 security guidelines.
- What port numbers do they use? * Port used: 4342
Other security issues? * None

Link to Sonar Report (68%)
Link to CSIT Jobs
All modules have been unit tested. Integration tests have been performed for all major features. System tests have been performed on most major features.
Registering and retrieval of basic mappings have been tested more thoroughly. More complicated mapping policies have gone through less testing.

Is is possible 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.

List of bugs fixed since the previous release:
6536 Clustering: operational data is not showing up in the in-memory map-cache on the replicas 2016-09-08
6754 No serializer defined for IPv6 prefix SimpleAddress 2016-09-20
6759 Expired mappings are not returned from SimpleMapCache before deletion. 2016-09-21
6634 LispNeutronService give exception: java.lang.NullPointerException 2016-10-13
6782 RadixTrie parent insertion not done correctly for non-empty children 2016-10-13
6925 Error during Map-Register performance test 2016-10-13
7018 Null pointer exception when SMR map request is received 2016-10-25
7035 Boron autorelease failing on lispflowmapping tests 2016-11-01
6361 LispSouthboundHandler is marked @ChannelHandler.Sharable but is not stateless 2016-11-23
7293 Radix trie node removals that update the root don’t work 2016-12-05
7586 Fix broken lispflowmapping features failing the new extended SingleFeatureTest incl. TestBundleDiag 2017-01-23
7789 Odl-lispflowmapping-ui breaks DLUX 2017-02-15
7628 Karaf 4 migration: provide Karaf 4 lispflowmapping features 2017-03-24
7818 Map-Register fast path not working correctly 2017-03-27
6071 Map Notify Authentication Data is not computed correctly 2017-03-27
6381 Expired xTR-ID mappings are not removed 2017-03-27
8248 Intermittent SingleFeatureTest failures in autorelease 2017-04-26
8429 Integration tests fail intermittently with unexpected SMR (a.k.a. the Heisenbug) 04:21:56
7272 Map-resolver replies with wrong mapping record and TTL 05:04:17

Clustering is still an experimental feature and may have some issues particularly related to operational datastore consistency.
Link to Open Bugs

The LISP implementation module and southbound plugin conforms to the IETF RFC6830 and RFC6833 , with the following exceptions:
- 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.
- LISP LCAFs are limited to only up to one level of recursion, as described in the IETF LISP YANG draft.
- No standards exist for the LISP Mapping System northbound API as of this date.