Contents
Introduction
Release Deliverables
| Name | Description |
|---|
| TTP codec | Ability to read/write TTPs to files/streams |
| TTP Model | Ability to provide TTPs in a compatible manner with how the OpenFlow library models table features. |
| TTP surfacing | Ability to surface the fact that a device currently supports a given TTP in the MD-SAL DOM. |
| TTP registry | Ability to host a set of named TTPs, browse their capabilities, and select interest in them |
| Manual TTP activation | Ability to manually set that a device currently supports a given TTP |
Release Milestones
| Milestone | Offset 0 Date | Deliverables |
|---|
| M1 | 5/12/2014 |
| Name | Status | Description |
|---|
| Candidate Release Plan | Done | Candidate Release Plan |
|
| M2 | 6/09/2014 |
| Name | Status | Description |
|---|
| Release Plan | Done | Final Release Plan | | Pushing to Nexus | Done | Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo | | TTP codec | Mostly (expected M5) | Support for reading/writing JSON TTP files
Mostly: A nearly complete YANG file is able to read and write JSON TTP files with a format that is very close to the ONF spec. We are working on a converter that will do the simple transform from ONF TTP JSON to ODL TTP JSON. |
|
| M3 | 7/07/2014 |
| Name | Status | Description |
|---|
| TTP registry | Mostly (expected M5) | Ability to host a set of named TTPs, browse their capabilities, and select interest in them
TTPs are mostly modeled and once they are, this is a trivial feature | | Started Integration Testing | Done | Integration test with yangtools, controller, and openflowjava created. | | Started Documentation | Partial (expected M5) | Architectural and code documentation exists, but we have yet to start on developer and user documentation. User and Developer documentation may be sparse and mostly be pointers to our Unit and Integration test code. |
|
| M4 | 8/04/2014 |
| Name | Status | Description |
|---|
| API Freeze | Done (some additions until M5) | The only current API we have is the TTP yang file which is mostly complete. We intend to leave the currently defined sections as is and only add fields thus freezing the current API. Other features of the API may come until M5. | | TTP Model | Mostly (expected M5) | This and the TTP codec above are now one and the same. |
|
| M5 | 9/1/2014 |
| Name | Description |
|---|
| Code Freeze |
| | TTP surfacing | Ability to surface the fact that a device currently supports a given TTP in the MD-SAL DOM. | | Manual TTP activation | Ability to manually set that a device currently supports a given TTP |
|
| RC0 | 9/9/2014 |
| Name | Description |
|---|
| Documentation review | Documentation update | | Integration testing | Execution of & Participation in continuous integration tests (IT) |
|
| RC1 | 9/15/2014 |
| Name | Description |
|---|
| Bugfixing | Fixing bugs/issues found during IT |
|
| RC2 | 9/22/2014 |
| Name | Description |
|---|
| Release Review | Release Review |
|
| Formal Release | 9/29/2014 |
| Name | Description |
|---|
| TTP Helium Release | Libraries for interacting with TTPs. Support to enumerate, request, and to which device support TTPs. |
|
Expected Dependencies on Other Projects
Likely dependent on yang tools, openflowplugin, and openflowjava.
Compatibility with Previous Releases
No previous release.
Themes and Priorities
Other