DIDM: Beryllium: Release Plan

DIDM: Beryllium: Release Plan

Contents

Introduction

Release Deliverables

Name

Description

Name

Description

FlowMod driver

FlowMod driver for HP 3800

Data Models & APIs

Data Models and APIs for common features such as flow mod adjustment

FRM integration

Component integrated with FRM to push flows

Application Interface

Interface for applications to register flowMods

Documentation

Documentation and sample Drives

Release Milestones

Milestone

Offset 2 Date

Deliverables

Milestone

Offset 2 Date

Deliverables

M1

8/7/2015





M2

9/3/2015





M3

10/15/2015





M4

12/03/2015





M5

1/14/2016





RC0

1/21/2016





RC1

1/28/2016





RC2

2/4/2016





RC3

2/11/2016





Formal Release

2/18/2016





Externally Consumable APIs

  • To be defined by M3

API

API Status

Short description

API

API Status

Short description

AdjustFlow

Available

Defines an RPC that can be used to validate and adjust Flow Mods. This defines the API only. Driver can be developed that implement this API for specific device types.

Expected Dependencies on Other Projects

  • SNMP Plugin - SNMP Set Request to fetch MIB objects

  • AAA - Credential Manager

  • OF plugin - Table features, FRM API to push flows

Compatibility with Previous Releases

N/A

Themes and Priorities

  • Support Device specific functionality

  • Common model augmentations

  • Single Identification component using Openflow description information and SNMP SysObjectId

  • Several Device Drivers to be defined

  • Documentation and sample driver

Requests from Other Projects

For each API / feature request, the requesting project MUST:

  • open Enhancement bug in Bugzilla describing request with Issue Type: Improvement, Change Request or New Feature

  • create an entry as described in Release Plan - Request template, which will also contain number / link to the bug. After creating the entry, the requesting project MUST:

send an e-mail to release@lists.opendaylight.org (mandated by Simultaneous Release)and both projects' dev lists using this template (mandated by Simultaneous Release)

Requesting Project

API Name

Needed By

Acknowledged?

Description

Requesting Project

API Name

Needed By

Acknowledged?

Description











Test Tool Requirements

  • Testing is done in form of Java unit tests and integration tests, no requirements on infrastructure except Maven. Reporting is provided by Jenkins.