This centralized page, for all Dublin projects, is aimed at identifying the risks as they are foreseen within the release life cycle.
A Risk that materialized becomes an Issue.
Status:
- 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
| Risk ID | Project Team or person identifying the risk | Identification Date | Risk (Description and potential impact) | Team or component impacted by the risk | Mitigation Plan (Action to prevent the risk to materialize) | Contingency Plan - Response Plan (Action in case of the risk materialized) | Probability of occurrence (probability of the risk materialized) High/Medium/Low | Impact High/Medium/Low | Status |
|---|---|---|---|---|---|---|---|---|---|
| 1 | SDNC | 1/14/19 | NETCONF/TLS support is new in OpenDaylight Fluorine release. Thus, ONAP will be one of the early adopters and hence there is some element of risk. | SDNC/APPC | We will try to target NETCONF/TLS for an early sprint to allow ample recovery time if we need to fall back to NETCONF/SSH | Fall back to NETCONF/SSH | High | High | Assessment |
| 2 | 1/15/19 | PNF use case being dependent on the delivery of the 5G use case, if it doesn't get deliver, then we won't be able to showcase the E2E automation for the PNF use case in Dublin. | CCSDK CDS SO | We will provide support in discussions around E2E automation and help driving success of PNF use case. | Demonstrate the E2E automation functionality using VNF use case. | Medium/High (Scorecard for M2 still empty) | Low | Assessed | |
| 3 | Portal | 8 Jan 2019 | Security impact on Policy, VID apps that use portal/sdk regarding addressing NexusIQ security issues and AAF integration which is not committed by Portal team so far due to lack of resources; | Policy, VID, AAF | Requesting open community for resources who can help with NexusIQ security critical issues in portal/sdk and portal. | Document the security impact in the release note | High | High | Assessed |
| 4 | Portal | 8 Jan 2019 | Impacts Dublin platform maturity requirements (Footprint Optimization, Logging Capabilities). Also, OOM deployment is impacted if the DB scaling changes are not supported by Portal team; also the changes for simplification of etc/hosts entries impacts the OOM deployment which is not committed by Portal team so far due to lack of resources. | OOM, Integration/Testing | Requesting open community for resources who can help with Footprint Optimization, Logging Capabilities in Portal under OOM scripts. | Risk partially addressed: Michael O'Brien is helping to address the logging capabilities. | High | Medium | Assessed |
| 5 | CLAMP | 23 Jan 2019 | New policy api(and contents) for CRUD operations on policies not defined yet | CLAMP, Policy | use old policy API | create config. policy the old("R3 release") way | Low (Policy team eventually committed so Risk can be closed) | Medium | Closed |
| 6 | CLAMP | 23 Jan 2019 | Blueprint generated by DCAE-D (SDC) might not be compatible with DCAE | CLAMP, DCAE-D, DCAE | Keep current manual blueprint onboarding in SDC (as VFI). | Manually created blueprint with correct format manually on boarded in SDC and distributed to CLAMP and DCAE. | High | Low | Closed |
| 7 | CLAMP | 23 Jan 2019 | New DCAE API to get status of µS not yet defined | CLAMP, DCAE | use current DCAE api | monitor only µS created by CLAMP | High | Low | Closed |
| 8 | AAF | 24 Jan 2019 | NOTE: This Comment is only referring to Stretch Goals. Our Committed work is proceeding apace. Originating company has reduced available developers for AAF. New features cannot be guaranteed. This applies ONLY to Stretch goal of CMPv2 (see #9) and request for Cookie Authentication (not listed here) | AAF | Dublin planning for AAF is conservative on new code commitments. | Community Step-up | Not a Risk | Not a Risk | We have removed the Stretch Goals from our Commitment |
| 9 | AAF | 24 Jan 2019 | This is a Stretch Goal. See #8, we don't have time or resources to accomplish in Dublin. CMPv2 is asked for by VNFs, including Nokia | AAF/VNF | Few Resources. Existing Java Libraries not found. | a) someone finds reliable CMPv2 libraries for Java b) Write own from scratch | Not a Risk | Not a Risk | We have removed the Stretch Goals from our Commitment |
| 10 | OOF | 25 Jan 2019 | Impact of the requirement of migrating to OOM based CSIT | OOF | Requesting the community for resources who can help with this ask for Dublin. | Provide prompt support to any issue that will be identified during the pair-wise testing and integration testing | High | Medium | Assessed |
| 11 | DCAE | 15-Feb-2019 | The new lifecycle Policy API definition being introduced for Dublin are under draft and having frequent churn; this is blocking DCAE Policy Handler evaluation/enhancement required to support this API. Based on current assessment of draft versions - new proposed updates impacts existing client (PH) handling of policy data in significant manner. Also its not clear if the old API's should be also supported by client in parallel, which adds more complexity. | DCAE, Policy, CLAMP | Requesting Policy team finalize the API definition soon in a way its not major rework for the clients. | Continue current (r3) api's | High | High | Planned |
| 12 | Integration | 14-Feb-2019 | S3P- Geo-Redundancy - Lab Environment to be available by M4 | Integration | Medium | Medium | Assessed | ||
| 13 | Integration | 19-Feb-2019 | Resource has been identified and committed to the development of new cases/functional requirements/non-functional requirements, however new development work can and will break existing functionality and delays other team development and testing. There is few mechanism in place today to prevent it until the integration test time (which is too late) | Integration and all teams | Daily integration CI and add passing integration sanity test to milestone checklist | Enforce it at each milestone | High | High | Being Assessed |
| 14 | Integration | 20-Feb-2019 | Windriver lab becomes the solely integration lab right now after TLab was out. Windriver lab is single point of failure for ONAP integration test, and any disturbance or resource shortage in Windriver lab would jeopardize Dublin release. We are already running into resource crunch in Windriver lab now. | Integration | Set up ONAP on Azure and experiment integration test on it (ONAP deployment and vFWCL) | Scale up to support full integration test on Azure in case of disruption or resource shortage in Windriver lab | Medium to High | High | Being assessed |
| 15 | AAI | 19-Feb-2019 | AAI has a breaking change in the PNF object in Dublin. Request for feedback from all PTLs has been made, will assess based on feedback after next week's PTL call whether or not this can go in. If the change goes in, data migration will need to happen for embedded PNFs, and AAI may be resource constrained in developing the migration utilities. | AAI | Get confirmation from PTLs that the breaking change is OK | Do not accept the change in Dublin | Low | High | Being assessed |
| 16 | OOM | 20-Feb-2019 | May not be able to deliver on Network Policies (OOM-1507) due to insufficient resources. | OOM | Need more resources | May be pushed to El Alto if unable to deliver within current release. | High | Low | Assessed |
| 17 | OOM | 20-Feb-2019 | Dublin Helm Charts not being deployed to public ONAP Helm repository. | OOM | Raised [ONAP Helpdesk #68891] | Working with LF now and should be resolved shortly. Once resolved will close this issue. | Low | Low | Assessed |
| 18 | Model Driven Control Loop | 25-Feb-2019 | The work on the SDC TOSCA-Lab compliant models is progressing very slowly. Open questions for the SDC team regarding format of models and issues with current TOSCA-Lab are not getting answered. This is stretch goal for SDC, but is affecting the other projects team to fulfill their commitments. | Policy, DCAE, CLAMP | Requesting SDC to help with open questions | May need to push to El Alto. | Medium | High | Being Assessed |