Name	Description
Common Model Augmentation	Common model augmentations for device type and device state
Data Models & APIs	Data Models and APIs for common features such as vlan configuration and flow mod adjustment
Identification Component	Component that orchestrates the process of determining the type of a device
Documentation	Documentation and sample Drives
Abstract classes	Abstract/helper classes

Release Milestones

Milestone

Offset 2 Date

Deliverables

M1

1/8/2015

Name	Status	Description
Candidate Release Plan	Out for Review	Candidate Release Plan

M2

2/5/2015

Name	Status	Description
Release Plan	Scheduled	Final Release Plan
Project setup	Scheduled	Project setup in Git and Jenkins

M3

3/19/2015

Name	Status	Description
Functionality Freeze	Scheduled	All project functionality declared
Define common model augmentations	Scheduled	Define the common model augmentations for device type and device state
Model augmentations defined	Scheduled	All model augmentations defined
Drivers defined	Scheduled	Define the Driver to be implemented in Lithium timeframe
Identification component API defined	Scheduled	Identification Component designed and prototype complete

M4

4/16/2015

Name	Status	Description
API Freeze	Scheduled	All external APIs are defined and reviewed with consumer projects (TBD)
Identification Component Complete	Scheduled	Ability to identify a device type based on Openflow description information. Ability to identify a device type based on SNMP information (assumes SNMP Plugin is available)
Data Models and APIs defined	Scheduled	Data Models and APIs defined for drivers to be implemented in the Lithium release
Karaf integration	Scheduled	DIDM as Karaf features
Documentation Plan complete	Scheduled	Define documentation set and who will write first drafts
Define Test plan	Scheduled	Define test plans for unit, system and integration tests

M5

5/14/2015

Name	Status	Description
Code Freeze	Scheduled	Code complete, only bug fixes going forward
All software complete	Scheduled	Identification component and Drivers complete
First Draft of Documentation	Scheduled	First draft of documentation set complete and reviewed by all committers
Unit tests complete	Scheduled	All unit test complete and code coverage goals met
Integration and System Tests complete	Scheduled	All integration and System tests complete and participating in continuous integration tests

RC0

5/28/2015

Name	Description
Documentation complete	Documentation complete and reviewed
All critical defects resolved	All "show-stopper" defects resolved, all other defects agreed to as not critical

RC1

6/4/2015

Name	Description
Bugfixing	Fixing only critical defects since RC0

RC2

6/11/2015

Name	Description
Release Review	Release Review

Formal Release

6/25/2015

Name	Description
DIDM Release	Model augmentations, Data Models and APIs defined, Identification Component, Drivers, and documentation and sample drivers

Externally Consumable APIs

To be defined by M3

API	API Status	Short description
Device type Info Model	Available	Defines an MD-SAL data store model that will contain information used to determine the type of device.
Device Type Augmentation	Available	Defines an MD-SAL data store augmentation that contain the type of device.
Device State Augmentation	Available	Defines an MD-SAL data store augmentation that contain the device's state.
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 Get Request to fetch MIB objects
AAA - Credential Manager

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

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.

Contents

Introduction