/
Lisp Flow Mapping: Boron: Release Plan

Lisp Flow Mapping: Boron: Release Plan

Contents

Introduction

This project is in offset 1.

Release Deliverables

Name

Description

Name

Description

operational DS vs config

Move SB mapping to operational datastore instead of config.

SB map-register cache

Add a cache layer to SB for improved performance on Map-Registers.

Move String IP to binary

Change map-cache keys and mapping record IPs to binary format.

Basic clustering

Enable clustering

Continuous integration with Service Function Chaining

The mapping Service will continue support for integration with Service Function Chaining.

Locator Scopes (Tentative)

Add support for defining locator scopes and transitional RTRs.

Multithreading in SB (Tentative)

Enable multithreading in SB.

Neutron Support improvements (Tentative)

Add support for xTR-ID in map-registers being stored as a Host-ID, such that Neutron Add/Update Port calls can match an existing xTR in LISP network.

TCP support as a southbound transport (Tentative)

TCP support as a southbound transport .

Release Milestones

Milestone

Offset 1 Date

Deliverables

Milestone

Offset 1 Date

Deliverables

M1

3/17/2016





M2

4/21/2016





M3

5/19/2016





M4

6/16/2016





M5

7/21/2016





RC0

8/11/2016





RC1

8/18/2016





RC2

8/21/2016





RC3

9/1/2016





Formal Release

9/8/2016





Externally Consumable APIs

  • mappingservice-api

Short Name

Description

Type (at M2)

Type (at M3)

Type (release)

Contract

Supporting Code

Short Name

Description

Type (at M2)

Type (at M3)

Type (release)

Contract

Supporting Code

Mapping Service

Main Mapping Service

Provisional

Provisional

Provisional

odl-mappingservice.yang , IMappingService.java

mappingservice.implementation

LISP SB

LISP Southbound Plugin

Provisional

Provisional

Provisional

odl-lisp-sb.yang

mappingservice.southbound

LISP Address Types

LISP Address Types

Provisional

Provisional

Provisional

ietf-lisp-address-types.yang

mappingservice.lisp-proto

Expected Dependencies on Other Projects

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

YANG Tools

Objects to be comparable()

M2?

No
(YANG Tools Release Plan)

YANG Tools objects to have a comparable() method that can be overridden, for use in IPv4/IPv6 prefix lookup tables (see bug 3032)

 ?

Expected Incompatibilities with Other Projects

N/A

Compatibility with Previous Releases

Removed APIs and/or Functionality

  • TBD

Deprecated APIs and/or Functionality

  • TBD

Changed APIs and/or Functionality

  • TBD

Themes and Priorities

The main theme of this release is improved performance and scalability.

Requests from Other Projects

Test Tools Requirements

Test Template

Other

LIST of Dropped Tentative Deliverables

The following tentative deliverables are dropped:

TBD

Related content