Contents
LISP Flow Mapping
Features
List of top level features:
- Feature Name: odl-lispflowmapping-msmr
- Feature URL: https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob_plain;f=features/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/sample/job/sample-csit-1node-feature-all-boron/
- Feature Name: odl-lispflowmapping-neutron
- Feature URL: https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob_plain;f=features/src/main/features/features.xml;
- Feature Description: This feature provides neutron integration.
- Top Level: Yes
- User Facing: Yes
- Experimental: Yes
- Feature Name:odl-lispflowmapping-ui
- Feature URL: https://git.opendaylight.org/gerrit/gitweb?p=lispflowmapping.git;a=blob_plain;f=features/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
Non-Code Aspects (user docs, examples, tutorials, articles)
- Release notes
- Installation Guide(s)
- No project specific steps needed. Config options are documented in the User Guide documentation.
- User Guide
Architectural Issues
N/A
Security Considerations
LISP southbound plugin follows LISP RFC6830 security guidelines. A key/password is associated with every EID prefix which is used to create a MAC (Message Authentication Code) of the UDP LISP control messages for authentication and integrity protection of the UDP messages. This is implemented as specified in the LISP RFC6830. These keys can be defined through the northbound APIs.
Quality Assurance (test coverage, etc)
- Unit Tests: coverage is at 80.5% as reported in Sonar.
- Integration Tests: Fairly large set of integration tests have been implemented and are passed.
- Automated System Tests are all passing:
- System tests performed manually with success.
- No blocking issues identified as yet.
End-of-life (API/Features EOLed in Release)
N/A
Bugzilla (summary of bug situation)
5 outstanding bugs, with normal or minor criticality, targeted for SR1.
Standards (summary of standard compliance)
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.
Schedule (initial schedule and changes over the release cycle)
Original schedule was followed.