...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Guilin |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Nokia, Ericsson, Wipro, ChinaMobile, T-Mobile, Huawei? |
Scope
What is this release trying to address?
...
| REQ# | Description | TSC Priority | DCAE Commit Status | DCAE Impact Assesment | DCAE JIRA # |
| REQ-380 | ONAP container repository (nexus) must not contain upstream docker images | MUST HAVE | YES | Add explicit references to dockerhub or nexus to all images Commitment based on Samsung, AT&T | DCAEGEN2-2322 |
| REQ-379 | ONAP projects must use only approved and verified base images for their containers | MUST HAVE | Stretch-goal | HIGH RISK - Approved base images list NOT CONFIRMED + MULTIPLE DCAE COMPONENT IMPACT (RISK#5- Guilin Risks)
Commitment : Multiple companies AT&T, Nokia, Ericsson, Wipro, ChinaMobile | DCAEGEN2-2323 |
| REQ-374 | ONAP shall use STDOUT for logs collection | PTL | Stretch-goal | Multiple platform components impacts (CBS, DH, PH, Cloudify not complain). (Long- Stretch goal depending on OOM team support) | DCAEGEN2-2324 |
| REQ-373 | ONAP must complete update of the Python language (from 2.7 -> 3.8) | MUST HAVE | YES | Per TSC 2.7->3.8 important; 3.7-3.8 (nice to have) Except Cloudify and SNMPTrap - all other DCAE components will be migrated to 3.8. SECCOM approved exception on 7/3 (refer jira) Commitment based on T-Mobile | DCAEGEN2-2292 |
| REQ-366 | Containers must crash properly when a failure occurs | MUST HAVE | YES | MEDIUM RISK - Need further assessment on DCAE components impacted (RISK#6 Guilin Risks) Commitment based on Ericsson | DCAEGEN2-2326 |
| REQ-365 | Containers must have no more than one main process | MUST HAVE | YES | MEDIUM RISK - Need further assessment on DCAE components impacted (RISK#6 Guilin Risks) Exception required for Cloudify due to upstream dependency. Commitment based on Ericsson | DCAEGEN2-2327 |
| REQ-364 | Replace NodePorts with ingress controller as a default deployment option | PTL | Stretch-goal | Need to be create DCAE jira if OOM team support is confirmed (may just need to update your tests to use urls instead of IPs) Resource TBD | NA |
| REQ-361 | Continue hardcoded passwords removal | MUST HAVE | YES | 1) Evaluate certInitializer integration impact for DCAE-tls init container Commitment based on Orange/Samsung/AT&T | DCAEGEN2-1972 |
| REQ-360 | Application config should be fully prepared before starting the application container | PTL | NO | Okay for service components (as CBS is used); Platform component should be okay. MOD - to be verified (possibly MOD/Nifi container) + Dashboard | NOT Committed |
| REQ-358 | No root (superuser) access to database from application container | YES | Stretch-goal | Need further assesment. Current list of component impact - Dashboard/Inventory/TCA-gen2/heartbeat/PM-Mapper/DL-feed/Son-handler Commitment based on WIPRO/ChinaMobile | DCAEGEN2-2329 |
| REQ-351 | ONAP must complete update of the java language (from v8 -> v11) | MUST HAVE | YES | MEDIUM RISK : Due to number of DCAE components impacted. (RISK#7 Guilin Risks)
Commitment : Multiple companies AT&T, Nokia, Ericsson, Wipro, ChinaMobile | DCAEGEN2-2223 |
| REQ-350 | Each ONAP project shall improve its CII Badging score by improving input validation and documenting it in their CII Badging site. | PTL | Stretch-goal | DCAEGEN2-2332 | |
| REQ-349 | Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage | MUST HAVE | YES | Already complaint for Frankfurt components; new component/enhancement to adhere Commitment : Multiple companies AT&T, Nokia, Ericsson, Wipro, ChinaMobile | DCAEGEN2-2333 |
| REQ-323 | Each project will update the vulnerable direct dependencies in their code base | MUST HAVE | YES | Commitment : Multiple companies AT&T, Nokia, Ericsson, Wipro, ChinaMobile | DCAEGEN2-2242 |
DCAE Backlog Reduction
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Resouce and Repositories in the centralized page.
...
Anyone reading this section should have a good understanding of all the interacting modules.
Platform Maturity
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| VES Collector | API for VNFs to send VES data | Will be updated for new VES spec (7.2) | ||
| DCAE Deployment Handler | NB API for invoking the deployment of DCAE subcomponents | Currently Available | R3 | |
| DCAE Inventory | API for Add/Delete DCAE copy's TOSCA models | Currently Available | R3 | |
| Healthcheck | API for querying DCAE component healthcheck | Currently Available | R4 | |
| DCAE Onboarding API | API for publishing DCAE spec into MOD | Currently Available | R6 | |
| DCAE Inventory | API for CLAMP to retrieve flow information | Currently Available | R6 | |
| Data Extraction Service (DES) | API for data retrieval and simple computation from DL-Handler maintained storages (For R7, this will be used by DCAE components such Slice-Analyis MS) and ExternalAPI(TBC by usecase team)UUI | Will be provided during M2/M3 | R7 | |
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
Cloudify support for Python 3.x not available currently, expected in by Aug 2020 timeframe. This impacts migration of Cloudify and associated plugins in Guilin (REQ-373) | Continue Frankfurt version of Cloudify and Plugins under python 2.7 | None |
Resources
Fill out the Resources Committed to the Release centralized page
Release Milestone
...