| Table of Contents | ||
|---|---|---|
|
Overview
...
| Deliverable Name | Deliverable Description |
|---|---|
| OOF-HAS | Executable, and source code for the Homing Service for the ONAP platform |
| OOF-OSDF | Executable and source code that provides optimization design framework support to optimizers like HAS |
Sub-Components
Architecture
High level architecture diagram
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | Status |
|---|---|---|---|---|---|
| HAS API | API to submit homing requests, and retrieve homing solutions (SO, VFC) | El Alto Release | Completed | ||
| Extensions to APIs to support network slicing workflows (NST, NSI and NSSI selection) | Guilin Release | In progress | In progress | ||
| SON API | API to perform SON optimization | Frankfurt Release | Completed | ||
| Route API | API to perform Route optimization (used by CCVPN use case) | Frankfurt Release | Completed | ||
| API enhancements for Route Selection for MDONS use case | Guilin Release | In progress | In progressMDONS Route API | Completed |
Third Party Products Dependencies
...
Known Defects and Issues
Please refer to Guilin Defect Statusthe latest release notes for the defects and issues.
Risks
Please update any risk on the centralized wiki page - Istanbul Risks.
Resources
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:optf
...
The milestones are defined at the Release Planning: Istanbul and all the supporting project projects agreed to comply with these dates.
...
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended recommended to provide these agreements and dates in this section.
...
- Team contributions to the specific document related to he the project (Config guide, installation guide...).
- Team contributions to the overall Release Documentation and training asset
- High A high-level list of documentation, training, and tutorials necessary to understand the release capabilities, configuration, and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End-User guide
- Admin guide
- ...
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
...
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however, to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third-party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non-Apache version 2 license.
...