Skip to end of banner
Go to start of banner

OVSDB: Lithium Release Plan

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


Contents

 [hide] 


Introduction

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

Trello

The Trello is at [1].

Release Deliverables

NameDescription
Bug fixingHigh-priority bug fixes. Bugs identified when the odl stackforge testing infrastructure is in place.
Sonar coverageIncrease unit, integration and code coverage reported by Sonar to improve code quality and stability
Tempest coverageEnable more Tempest test coverage
AD-SAL DeprecationDeprecate AD-SAL dependencies
MD-SAL OVSDBAdd MD-SAL interface to OVSDB

Release Milestones

MilestoneOffset 2 DateDeliverables
M11/8/2015
NameStatusDescription
Intent to participateDoneIntent to participate in Lithium Simultaneous Release
Project Lead electedDoneProject Lead election
Test Contact specifiedDoneTest Contact announced
Candidate Release PlanDoneCandidate Release Plan
M22/5/2015
NameStatusDescription
Release PlanDoneFinal Release Plan
Project ChecklistDoneProject Checklist completed
OpenDaylight CIDoneOpenDaylight CI infrastructure usage for system test
Rackspace Test Tools InstallationDone
M33/19/2015
NameStatusDescription
Functionality FreezeDone
Karaf Features DefinedDoneUser Facing Features
Documentation StartedDonegerrit 18486 gerrit 20328
Integration and System Test TemplateDoneOVSDB:Lithium_Integration_Test
M44/16/2015
NameStatusDescription
API FreezeDone
Documentation word countDone
Maven Central RequirementsDone
Simple Integration and System TestDone
M55/14/2015
NameStatusDescription
Code FreezeDone
Stability BranchDoneStability branch, i.e., stable/lithium, must be cut and local project versions bumped on the master

to avoid overwriting lithium SNAPSHOTS

String FreezeDoneAll externally visible strings frozen to allow for translation & documentation
Documentation Complete
Only editing and enhancing should take place after this point.
Integration & System TestDone
RC05/28/2015
NameStatus
Release Candidate 0
RC16/4/2015
NameStatus
Release Candidate 1
RC26/11/2015
NameStatus
Release Candidate 2
RC36/18/2015
NameStatusDescription
Bugfix & more
Bugfixing, samples
Release Review
Release Review
Release Candidate 3
Blocking Bugs
Formal Release6/25/2015
NameStatusDescription
Formal Lithium Release

Release patch
Release patch to the stable/lithium branch and bump versions
SR1 Release8/13/2015
NameStatusDescription
Release patch
Release patch to the stable/lithium branch and bump versions
SR2 Release9/24/2015
NameStatusDescription
Release patch
Release patch to the stable/lithium branch and bump versions

Externally Consumable APIs

ArtifactStatusDescription
OvsdbInventoryListenerStableExisting APIs to perform OVSDB crud operations
SouthboundTentativeMD-SAL OVSDB crud operations

Expected Dependencies on Other Projects

Providing ProjectDeliverable NameNeeded ByAcknowledged?Description
controllerfeaturesM3Nobasic controller features
odlparentfeaturesM3Noodlparent values
openflowpluginfeaturesM3Noflow programming and extensions
yangtoolsfeaturesM3Noyangtools 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 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







  • No labels