Contents
Introduction
Release Deliverables
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 |
---|
M1 | 8/7/2015 | Name | Status | Description |
---|
Intent to participate | Done | Intent to participate in Beryllium Simultaneous Release | Project Lead elected | Done | DIDM Project Lead election | Test Contact specified | Done | DIDM Test Contact announce | Candidate Release Plan | Done | Candidate Release Plan |
|
M2 | 9/3/2015 | Name | Status | Description |
---|
Release Plan | Done | Final Release Plan | Project Checklist | Done | Project Checklist completed | Project setup | Done | Project setup in Git and Jenkins |
|
M3 | 10/15/2015 | Name | Status | Description |
---|
Functionality Freeze | Done | Final list of externally consumable APIs defined and documented | FlowMod driver defined | Done | Define modules to validate and adjust flow for HP 3800 | Collect Table features from inventory node | Done | Read table features from data store | FRM integration | Done | Define methods or wrappers to invoke FRM APIs to push flows | Documentation Started | Done | Identified the kinds of documentation to be provided, created AsciiDoc files for them with outlines,
and committed those files in an appropriate location | Integration & System Test | Done | Simple system test on a karaf distribution with the project's recommended features installed |
|
M4 | 12/03/2015 | Name | Status | Description |
---|
API Freeze | Done | All external APIs are defined and reviewed with consumer projects | Maven central requirements | Done | Meet the requirements to be included in maven central | Identification of APIs for application interface | Done | Define APIs fro application to invoke to push flows to MS-SAL data store | Data Models and APIs defined | Done | Data Models and APIs defined for drivers to be implemented | Documentation Plan complete | Done | Define documentation set and who will write first drafts | Define Test plan | Done | Define test plans for unit, system and integration tests |
|
M5 | 1/14/2016 | Name | Status | Description |
---|
Karaf integration | Done | DIDM as single karaf feature install for all features of DIDM | Code Freeze | Done | Code complete, only bug fixes going forward | All software complete | Done | Identification component and Drivers complete | First Draft of Documentation | Done | First draft of documentation set complete and reviewed by all committers | Unit tests complete | Done | All unit test complete and code coverage goals met | Integration and System Tests complete | Done | All integration and System tests complete and participating in continuous integration tests |
|
RC0 | 1/21/2016 | 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 | 1/28/2016 | Name | Description |
---|
Bugfixing | Fixing only critical defects since RC0 |
|
RC2 | 2/4/2016 | Name | Description |
---|
Release Candidate 2 | Release Review |
|
RC3 | 2/11/2016 | Name | Description |
---|
Release Candidate 3 | Release Review |
|
Formal Release | 2/18/2016 | Name | Description |
---|
Formal Beryllium Release |
|
| DIDM Release | HP 3800 FlowMod driver, Data Models and APIs defined, and documentation and sample drivers |
|
Externally Consumable APIs
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 |
---|
|
|
|
|
|
- Testing is done in form of Java unit tests and integration tests, no requirements on infrastructure except Maven. Reporting is provided by Jenkins.