/
OVSDB: Lithium Release Plan

OVSDB: Lithium Release Plan



Contents

Introduction

https://wiki.opendaylight.org/view/OVSDB_Integration:Main

Trello

The Trello is at [1].

Release Deliverables

Name

Description

Name

Description

Bug fixing

High-priority bug fixes. Bugs identified when the odl stackforge testing infrastructure is in place.

Sonar coverage

Increase unit, integration and code coverage reported by Sonar to improve code quality and stability

Tempest coverage

Enable more Tempest test coverage

AD-SAL Deprecation

Deprecate AD-SAL dependencies

MD-SAL OVSDB

Add MD-SAL interface to OVSDB

Release Milestones

Milestone

Offset 2 Date

Deliverables

Milestone

Offset 2 Date

Deliverables

M1

1/8/2015





M2

2/5/2015





M3

3/19/2015





M4

4/16/2015





M5

5/14/2015





RC0

5/28/2015





RC1

6/4/2015





RC2

6/11/2015





RC3

6/18/2015





Formal Release

6/25/2015





SR1 Release

8/13/2015





SR2 Release

9/24/2015





Externally Consumable APIs

Artefact

Status

Description

Artefact

Status

Description

OvsdbInventoryListener

Stable

Existing APIs to perform OVSDB crud operations

Southbound

Tentative

MD-SAL OVSDB crud operations

Expected Dependencies on Other Projects

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

controller

features

M3

No

basic controller features

odlparent

features

M3

No

odlparent values

openflowplugin

features

M3

No

flow programming and extensions

yangtools

features

M3

No

yangtools for compiling yang

Expected Incompatibilities with Other Projects

OVSDB is considered incompatible with applications that program the flow tables on vSwitches. This includes:

GBP OpenDOVE VTN

These projects have not held discussions as to how to become compatible because they each provide their own solution to the same problem.

Compatibility with Previous Releases

Removed APIs and/or Functionality

The BridgeDomain APIs are removed since they were deprecated in Helium. The APIs were not used.

Deprecated APIs and/or Functionality

The OVSDB northbound API might be depreciated depending on the outcome of the AD-SAL deprecation. The APIs currently use some AD-SAl dependencies.

Changed APIs and/or Functionality

Themes and Priorities

  • Increasing unit and integration test coverage to improve code quality

  • Deprecate AD-SAL dependencies

  • Provide an MD-SAL interface to OVSDB for crud operations

Requests from Other Projects

Active Requests

  • Requesting Project: VPN Service

  • Providing Project: OVSDB

  • Requested Deliverable Name: OVSDB interface

  • Needed Milestone:

  • Requested Deliverable Description: We only require the ability to query and instantiate non-OpenFlow information such as ports, bridges, tunnels etc.

  • Response:

    • Description:

    • Resources From:

    • Link to Section in Requesting Project Release Plan:

    • Link to Section in Providing Project Release Plan:

  • Negotiation:



  • Requesting Project: VTN

  • Providing Project: OVSDB

  • Requested Deliverable Name: OVSDB interface

  • Needed Milestone:

  • Requested Deliverable Description: We only require the ability to query and instantiate non-OpenFlow information such as ports, bridges, tunnels etc. We prefer the existing OVSDB plugin OVSDBInventoryListener interface and not an md-sal interface due to time constraints.

  • Response:

    • Description:

    • Resources From:

    • Link to Section in Requesting Project Release Plan:

    • Link to Section in Providing Project Release Plan:

  • Negotiation:



  • Requesting Project: SFC (https://lists.opendaylight.org/pipermail/sfc-dev/2015-January/000659.html)

  • Providing Project: OVSDB

  • Requested Deliverable Name: MD-SAL OVSDB

  • Needed Milestone: M2

  • Requested Deliverable Description: Working MD-SAL OVSDB SB plugin for communicating SFC information to the node. Independent of netvirt.

  • Response:

    • Description:

    • Resources From:

    • Link to Section in Requesting Project Release Plan:

    • Link to Section in Providing Project Release Plan:

  • Negotiation:



  • Requesting Project: GBP (https://lists.opendaylight.org/pipermail/release/2015-January/001148.html)

  • Providing Project: OVSDB

  • Requested Deliverable Name: MD-SAL OVSDB

  • Needed Milestone: M2

  • Requested Deliverable Description: Working MD-SAL OVSDB SB plugin for communicating to node independent of netvirt. We only require the ability to query and instantiate non-OpenFlow information such as ports, bridges, tunnels etc. This is probably a duplicate of the SFC request.

  • Response:

    • Description:

    • Resources From:

    • Link to Section in Requesting Project Release Plan:

    • Link to Section in Providing Project Release Plan:

  • Negotiation:

Test Tools Requirements

This project plans on using System Test (ST) inside the OpenDaylight cloud. In particular, the integration piece of OVSDB's Netvirt will require an Openstack Installation that uses ODL as the Neutron ML2. It is the goal to integrate with both Icehouse and Juno.

Update: Flaviof talked with Than and is currently convinced that the infra provided by jjb and sandbox is all that will be needed in terms of infrastructure to have automated tests on OVSDB functionality in Lithium. The plan will utilize VMs of the label 'dynamic_devstack'.

Other