Lisp Flow Mapping: Lithium: Release Notes
- Manish Kumar Barnwal
Contents
Lithium Release Notes
Major Features
Name | Description |
|---|---|
Improved ELP processing | The mapping Service will Return both ELP and the next hop depending on the requesting xTR. This assists in ELP support for non-ELP enabled xTRs. |
Transition to MD-SAL | The NB API will be transitioned to MD-SAL. The Neutron API should also transition to MD-SAL. |
Continuous integration with Service Function Chaining | The mapping Service will continue support for integration with Service Function Chaining. |
Neutron implementation enhancements | Improve and expand Neutron API support in LISP Flow Mapping. |
Target Environment
For Execution
Languages used: Java
Required: JRE
For Development
JDK
Maven
Known Issues and Limitations
LISP LCAFs are limited to only up to one level of recursion. For instance in the case of a traffic engineering policy every hop can only be a basic address (IPv4, IPv6, MAC, Dist. Name, AS Number), and can not include combinations such as Segment ID, or list.
Testing methodology
All modules have been unit tested. Integration tests have been performed for all major features.
Registering and retrieval of basic mappings have been tested more thoroughly. More complicated mapping policies have gone through less testing.
Compatibility with Previous Releases
Our Northbound service has been EOLed, including all associated northbound REST APIs. Equivalent APIs are now available via RPCs and RESTCONF. API documentation is available at API Documentation.
Southbound plugin is compatible with previous releases.
Per-Project Release Notes
Release Notes For Later Releases
Compatibility with Previous Releases
Our Northbound service has been EOLed, including all associated northbound REST APIs. Equivalent APIs are now available via RPCs and RESTCONF. API documentation is available at API Documentation.
Southbound plugin is compatible with previous releases.
Deprecated, End of Lifed, and/or Retired Features/API
Our Northbound service has been EOLed, including all associated northbound REST APIs. Equivalent APIs are now available via RPCs and RESTCONF. API documentation is available at API Documentation.