Contents
Introduction
Release Deliverables
Release Milestones
| Milestone | Offset X Date | Deliverables |
|---|
| M1 | 2015-07-23 | | Name | Description |
|---|
| Release Plan | Candidate Release Plan | | Deliverable Name | Deliverable Description |
|
| M2 | 2015-08-20 | | Name | Description |
|---|
| Release Plan | Final Release Plan | | MD-SAL AuthN store |
| | AuthN Store Plugin infrastructure |
| | IdmLight Automated Testing |
| | Hashing of stored passwords |
| | AuthZ for REST APIs |
|
|
| M3 | 2015-09-17 | | Name | Description |
|---|
| Feature Freeze |
| | AuthN Store CRUD & Service API |
| | AuthZ for REST APIs |
|
|
| M4 | 2015-10-15 | | Name | Description |
|---|
| API Freeze |
|
|
| M5 | 2015-12-11 | | Name | Description |
|---|
| Code Freeze |
|
|
| RC0 | 2016-01-07 | |
| RC1 | 2016-01-14 | |
| RC2 | 2016-01-21 | | Name | Description |
|---|
| Release Review | Release Review Description |
|
| Formal Release | TBD | | Name | Description |
|---|
| Deliverable Name | Deliverable Description |
|
Externally Consumable APIs
| Short Name | Description | Type (at M2) | Type (at M3) | Type (release) | Contract | Supporting Code |
|---|
| API Name | Short Description | One of Provisional, Tentative, Stable, or Dropped as defined in the Beryrllium release plan definitions. | link to the Java interface, YANG file, WSDL description, etc. that defines the API | list of Karaf features, OSGi bundles, directories, etc. that provide the API |
Expected Dependencies on Other Projects
| Project Name | Deliverable Name | Milestone Needed By | Description of the new deliverable or changes to a deliverable |
| Controller | Restconf | Tentative | Connector + restconf code interface Annotations to enable Shiro |
Expected Incompatibilities with Other Projects
Compatibility with Previous Releases
Removed APIs and/or Functionality
Deprecated APIs and/or Functionality
IdmLight REST API, used for administering the user DB will be changed to be user domain based + no longer requiring an ODL assigned numeric index to access. The change is driven by the need to fix the DB schema to actually support clustering of the data. Previous users of the API will be affected for the user query operations, however our investigations have not revealed any objections to the change from users of this API (currently only used by cisco)
Changed APIs and/or Functionality
See above
Themes and Priorities
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)
- Please specify if the project will run System Test (ST) inside OpenDaylight cloud
- In case affirmative please enumerate any test tool (mininet, etc...) you think will be required for testing your project
- The goal is to start test tools installation in rackspace as soon as possible
- In case negative be aware you will be required to provide System Test (ST) reports upon any release creation (weekly Release, Release Candidate, Formal Release, etc...)
Other