This centralized page, for all Beijing projects, is aimed at identifying the risks as they are foreseen within the release lifecycle.
A Risk that materialized becomes an Issue.
- Identified: a risk that has been identified, but has not yet been analyzed / assessed yet
- Assessed: an identified risk which currently has no risk response plan
- Planned: an identified risk with a risk response plan
- In-Process: a risk where the risk response is being executed
- Closed: a risk that occurred and is transferred to an issue or the risk was solved/avoided
- Not occurred: a risk that was identified but that did not occur
- Rejected: created and kept for tracking purposes but considered not to be used yet
Project Team or person identifying
(Description and potential impact)
Team or component impacted by the risk
(actions to prevent the risk to materialize)
Contingency Plan - Response Plan
(actions in case the risk materialized)
Probability of occurrence
(probability the risk
|1||Katel34||3/12/2018||CII Badging - Beijing Release Criteria is addressing Critical Security issues (7-10) but not Severe Security issues (4-6) identified by Nexus IQ Server. Therefore some projects might not pass their CII Badging||Any Project team who has marked 'Unmet' concerning "There MUST be no unpatched vulnerabilities of medium or high severity that have been publicly known for more than 60 days"||Fix any remaining Severe security issue post-M4 that will not jeopardize the Integration Testing activities (no major architecture change)||Provide an impact analysis about the remaining "Severe" security vulnerabilities and a delivery plan as part of the Casablanca Release.||High||Medium|
ONAP DM Modeling SDC Requirements
2 new sets of normative types are required from the Modeling team:
Impact on vVOLTE Use Case
|SDC, Integration Team impacted by Modeling project|
To be able to meet M4 all this items need to be delivered by 3/16/2018 :
If not then VoLTE use case will not be re certified by M4.
|Descope this SDC Feature to support DM Modeling||High|
Waiting for the Models to be validated and then the VNF packages should be provided.
Late delivery of Nitrogen ODL
We were expecting to be integration newer version of ODL in Sprint 2; however, due to late delivery, this work is falling into the last sprint for Beijing release. Nitrogen brings a lot of changes that will make the component unstable until completed and will impact testing, plus may take longer than 1 sprint to complete. In Amsterdam, it took us a couple of sprint to work through issues and there were a number of fixes that were needed in CCSDK discovered as we attempted integration. I expecting that we will have similar experience.
We are being trying to prioritize the features in APPC and update those that are needed for Beijing as top priority.
Also working closely with CCSDK PTL on any issues found in CCSDK that may block us.
|De-scope upgrade to Nitrogen; fall back to released version of Carbon from CCSDK Amsterdam distribution.||High||High|
We are still working through upgrade issues; Nitrogen/Karaf 4 don't seem to be very stable and we are running into issues with bundles freezing up during deployment, which is made difficult to troubleshoot since there are no error messages.
Confidence level to complete by 3/29: Low
Target completion based on M4 Review: 4/13/2018
APPC upgrade to Nitrogen submitted. Testing of runtime functionality in progress.
Late delivery of AAF-91 dependency
This feature was expected by 2/15; however, as of 3/13, delivery of feature has not been received yet. Demo of feature provided did not deliver the requested scope.
Working closely with AAF team to get gap addressed to enable APPC to deliver AAF integration to secure APIs exposed via ODL apidoc.
Based on current discussion with AAF team, we expect this to be a configuration change on APPC only. If that turns out not to be the case, delivering APPC-404 by code freeze may not be possible.
De-scope APPC-404 in Beijing and address in Casablanca.
|Medium at this time; will monitor to see how it goes in the next week and determine if risk level needs to change.||High|
3/27/18 update: Still waiting on official delivery of AAF-91 in Nexus. We have tested with beta version provided by Dev team, but APPC feature cannot be completed until AAF-91 is published.
Confidence level to complete by 3/29: Medium to Low
Showstopper for Beijing Release since it has a broader impact than APPC
Integration work is still in progress; currently blocked by AAF-250. AAF team is working on it.
4/25/18 update: Successfully tested AAF integration. APPC-404 complete
Code Merge from ATT Ecomp 1806 to ONAP SO
Risk as identified at M1 and M2 has materialized. ATT code is not merged yet. This may impact code quality (static code checks, security vulnerabilities and Licensing) and code coverage. Code merge may impact other current development. Code Merge is currently planned by March 14.
Working closely for the merge to be on time.
Code merge has been completed on 14th March and around 82K lines of added+ Modified code has been introduced new.
Need to re-asses the functional features commitment.
|6||VF-C||3/12/2018||VF-C have planned to implement ETSI NFV compliant API in Beijing, some of the committing companies raised the IPR issue(there may be risks of ETSI intellectual property rights infringement). VF-C also asked about LF suggestions.In order to avoid risks, the LF suggested that VF-C hold contribution until Casablanca or the intermediate version of Beijing and Casablanca||VF-C||VF-C hold contribution until Casablanca or the intermediate version of Beijing and Casablanca||VF-C provide the R1 APIs||High||Low|
We consulted Linux Foundation, they said they are working with ETSI to discuss this and haven’t have result before M4. They suggested we wait their conclusion and postpone the implementation to next release to avoid the risk. So the ETSI interface alignment and implementation will be postponed to Casablanca
Security - Support of HTTPS and Certificates Distribution Strategy for the Beijing release is not yet available. Since all projects need to implement TLS for S3P requirements, a centralized solution is needed so that all projects can have their certificates signed by an ONAP CA and only have to trust the ONAP CA rather than each project distributing self-signed certificates. Also need a solution for cert subject naming conventions so that systems do not have to disable hostname verification, and have a central DNS solution as well
|Any Project team who require a certificate & will support HTTPS||Feedback required from the Security Subcommittee||Mitigated Action: Re-use openecomp toy CA that was used for a few projects in Amsterdam. Finalize the Certificates/HTTPS strategy by Casablanca M1 (Planning Milestone) since it will potentially require significant development.||High||High|
Dependency with Risk #4
|Large code drops at the M4 code freeze date does not allow time for OOM to integrate these changes into Beijing. Significant changes are expected from SDC, SO, SDNC/R, and DCAE prior to M4. Any others?||All teams|
Teams planning to release significant changes to either the docker containers or configuration of these containers should contact the OOM team (Roger Maitland).
|ONAP integration will likely start with stable components and proceed with components with significant changes as they are on-boarded to OOM.||High||High|
March 28, 2018 Update (M4 code review):
•Priority of cpts to be integrated
|Nexus3 docker image download throttling causing timeouts during onap deployments||all teams||LF adds more scaling to the AWS based nexus3 server||pull off-hours or from a mirror|
(last occurrence March 19 after 1600 EDT GMT-4)
|High (system unstable)|
IT issue - can you please provide LF Help-desk number?
|10||VNF Requirements||The items in VNF Requirements testability list are not discussed thus some requirement items are not clarified. <This risk needs to be better defined. What is impacted by requirements not discussed? How does this impact the VNF Requirements project?>|
|Agreement must be reached after a discussing soon. < any clarification/change to requirements can be raised as a JIRA bug to be fixed>||Un-clarified items could be removed from R2 or be clarified as bugs during RC0||Medium||High (unclear VNF requirements are published)|
Can you please provide an update from the meeting organized on 3/22?
|11||Multi VIM/Cloud||MVP features are blocked by -2||Multi VIM/Cloud/VFC||Team has voted to make project technical decision making||defer MVP feature deliver and function support to VoLTE||High||High||Done|
|12||CLAMP||Control Loop Design UI needed for CLAMP will be missing||CLAMP||SDC must be allowed to add the seed code for the DCAE-D part||manual provisioning of Control Loop blueprint||Medium||High|
Workaround is available to kick-off the integration testing. DCAE-D remains a stretch goal for Beijing.
closing the risk as there is a workaround
|13||VNFSDK||3/23/18||VNFD is not yet finalized, putting HPA support in jeopardy. Related to #2.||VNFSDK||Model needs to be finalized by 3/26 or HPA updates will be deferred to a maintenance release||defer to Casablanca or interim release||high||low|
Waiting for the Models to be published
|14||Multi VIM/Cloud||OOF integration is under development to enable CSIT||Multi VIM/Cloud/OOF||Primary functions are under development and lack of CSIT||defer to Casablanca or interim release||Medium||High||In-Process|
|15||CLAMP||UI login authentication using AAF will be missing||CLAMP||AAF still facing issue interoperating with CLAMP||authentication of user like in R1 release using CLAMP internal DB||Medium||Medium|
workaround is to use CLAMP internal DB like in R1 ONAP release
|16||NBI (formerly knows as External API)||05/04/2018||Late delivery of NBI docker image||Any project team that plan to install this compoent||Prioritize a #1 by project team to deliver it by RC1||Code is already available||Medium||Low|
|17||Policy||04/10/2018||Bad Amsterdam release artifacts, Beijing artifacts unavailable||Any project team that integrates with AAF client-cadi jars.||Policy will be reverting back to github open source versions of AAF used in Amsterdam release.||Policy will not support any AAF Beijing functionality unless supported by older artifacts||Medium||Medium||Resolved|