ALTO: Carbon: Release Plan
Contents
Introduction
In the Carbon release the ALTO project is aimed to support some to-be-standard functionalities from the IETF ALTO Working Group. Also, simultaneous efforts must be made to improve the code quality of the existing components.
Functionalities
Code quality
Migrate to blueprint, see the introduction to blueprint
Use a unified namespace for ALTO services to simplify the migration when an experimental feature becomes a standard
Increase the test coverage to at least 40% (current is 21%), see sonar report
Release Deliverables
Only new deliverables are listed here, see ALTO:Main and visit corresponding release plans for deliverables from previous releases.
Name | Description |
---|---|
alto-core |
|
alto-basic |
|
alto-extension |
|
Release Milestones
Offset: 2
Milestone | Offset X Date | Deliverables |
---|---|---|
M1 | 11/1/2016 | |
M2 | 12/8/2016 | |
M3 | 2/2/2017 | |
M4 | 3/2/2017 | |
M5 | 3/30/2017 | |
RC0 | 4/13/2017 | |
RC1 | 4/20/2017 | |
RC2 | 4/27/2017 | |
RC3 | 5/4/2017 | |
Formal Release | 5/11/2017 |
Externally Consumable APIs
Network map service (Stable)
Cost map service (Stable)
Endpoint cost service (Stable)
Endpoint property service (Stable)
Configurable map service (Stable)
Simple IRD service (Stable)
Simple path management service (Stable)
Incremental update (In progress)
Routing state abstraction (In progress)
Expected Dependencies on Other Projects
Depends on OpenFlow Plugin, L2Switch and all their dependent projects.
Expected Incompatibilities with Other Projects
Not compatible with `odl-l2switch-switch`.
Compatibility with Previous Releases
Both namespace migration and the adoption of incremental update and multicost can lead to incompatibilities with previous releases.
We would provide a script to help with the migration.
Themes and Priorities
Requests from Other Projects
N/A
Test Tools Requirements
OpenDaylight CSIT Framework
Mininet