Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

NameVijay Kumar
Milestone or Requirements Exception?Requirement

Project or Requirement Name and JIRA

  • REQ-351 - ONAP must complete update of the java language (from v8 -> v11)
    •  DCAEGEN2-2223 Majority of DCAE components migrated with exception of below
      • RESTConf, Mapper, DL-Admin (resource constraint; will be targetted for point release)
      • MOD-Genprocessor, MOD-DesignUI (upstream image dependency)
  • REQ-362 - All containers must run as non-root user 
    • Need exception for dcae-cloudify-manager (upstream image dependency requires root) 
  • REQ-373 - ONAP must complete update of the Python language (from 2.7 -> 3.8)
    • Exception for Cloudify (upstream dependency, SNMPTrap (approved by SECCOM - DCAEGEN2-2292)
  • REQ-379 - ONAP Project must use approved base images
    • Most python components were aligned (except SNMPTrap); Java components require exception  
  • POD no limit (Integration defect: DCAEGEN2-2429)
  • REQ-366 - Containers must crash properly when a failure (DCAEGEN2-2326)
    • Following components not complaint 
      • onap/org.onap.dcaegen2.collectors.snmptrap
      • onap/org.onap.dcaegen2.platform.deployment-handler
      • onap/org.onap.dcaegen2.platform.policy-handler
Milestones affected

N/A

Projects affected

N/A

Background description

DCAE being large project (41 components in Guilin) need more resource and time for complaince with non-functional requirements. We made significant progress this release, however due to number of components impacted, adopting phased approach.

DCAE platform also has upstream dependency (NiFi for MOD & Cloudify ) - some of the ONAP NFR requires work in upstream community.

Schedule impact

N/A

Recovery plan

Continue phased approach in coming releases based on commitment from the community.

For upstream dependency : Followup with upstream community and/or determine alternate solution which might involve DCAE ARC impact

Milestone schedule change

N/A

Risk

The risk is that the aforementioned DCAE components will not be able to meet Guilin NFR 

Status
Decision
  • No labels