/
DIDM: Beryllium: Release Plan

DIDM: Beryllium: Release Plan

Owned by Manish Kumar Barnwal
Aug 28, 2021

Contents

Introduction

Release Deliverables

NameDescription
FlowMod driverFlowMod driver for HP 3800
Data Models & APIsData Models and APIs for common features such as flow mod adjustment
FRM integrationComponent integrated with FRM to push flows
Application InterfaceInterface for applications to register flowMods
DocumentationDocumentation and sample Drives

Release Milestones

MilestoneOffset 2 DateDeliverables
M18/7/2015
NameStatusDescription
Intent to participateDoneIntent to participate in Beryllium Simultaneous Release
Project Lead electedDoneDIDM Project Lead election
Test Contact specifiedDoneDIDM Test Contact announce
Candidate Release PlanDoneCandidate Release Plan
M29/3/2015
NameStatusDescription
Release PlanDoneFinal Release Plan
Project ChecklistDoneProject Checklist completed
Project setupDoneProject setup in Git and Jenkins
M310/15/2015
NameStatusDescription
Functionality FreezeDoneFinal list of externally consumable APIs defined and documented
FlowMod driver definedDoneDefine modules to validate and adjust flow for HP 3800
Collect Table features from inventory nodeDoneRead table features from data store
FRM integrationDoneDefine methods or wrappers to invoke FRM APIs to push flows
Documentation StartedDoneIdentified the kinds of documentation to be provided, created AsciiDoc files for them with outlines,

and committed those files in an appropriate location

Integration & System TestDoneSimple system test on a karaf distribution with the project's recommended features installed
M412/03/2015
NameStatusDescription
API FreezeDoneAll external APIs are defined and reviewed with consumer projects
Maven central requirementsDoneMeet the requirements to be included in maven central
Identification of APIs for application interfaceDoneDefine APIs fro application to invoke to push flows to MS-SAL data store
Data Models and APIs definedDoneData Models and APIs defined for drivers to be implemented
Documentation Plan completeDoneDefine documentation set and who will write first drafts
Define Test planDoneDefine test plans for unit, system and integration tests
M51/14/2016
NameStatusDescription
Karaf integrationDoneDIDM as single karaf feature install for all features of DIDM
Code FreezeDoneCode complete, only bug fixes going forward
All software completeDoneIdentification component and Drivers complete
First Draft of DocumentationDoneFirst draft of documentation set complete and reviewed by all committers
Unit tests completeDoneAll unit test complete and code coverage goals met
Integration and System Tests completeDoneAll integration and System tests complete and participating in continuous integration tests
RC01/21/2016
NameDescription
Documentation completeDocumentation complete and reviewed
All critical defects resolvedAll "show-stopper" defects resolved, all other defects agreed to as not critical
RC11/28/2016
NameDescription
BugfixingFixing only critical defects since RC0
RC22/4/2016
NameDescription
Release Candidate 2Release Review
RC32/11/2016
NameDescription
Release Candidate 3Release Review
Formal Release2/18/2016
NameDescription
Formal Beryllium Release

DIDM ReleaseHP 3800 FlowMod driver, Data Models and APIs defined, and documentation and sample drivers

Externally Consumable APIs

  • To be defined by M3
APIAPI StatusShort description
AdjustFlowAvailableDefines 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 ProjectAPI NameNeeded ByAcknowledged?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.

Related content