Dublin Risks
- cl664y@att.com
- Former user (Deleted)
- Manoop Talasila
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 | Some team members have conducted early testing of NETCONF/TLS and are working closely with the OpenDaylight community so that any defects can be addressed in Fluorine timeframe. | Fall back to NETCONF/SSH | Medium | Medium | Closed - we upgraded to Fluorine SR2 to pick up a fix that we needed for NETCONF/TLS. Other than that, testing has been successful and we did not need to fall back. |
2 | @Yuriy Malakov | 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 | 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. <Viable alternative?> | Medium/High (Scorecard for M2 still empty) | Low | Assessed Closing as alternative exists and RC cycles not endangered |
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 | 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. We have removed the Stretch Goals from our Commitment | Community Step-up | Not a Risk | Not a Risk | Closed |
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. We have removed the Stretch Goals from our Commitment | a) someone finds reliable CMPv2 libraries for Java b) Write own from scratch | Not a Risk | Not a Risk | Closed |
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 | Closed (3/28 - based on expected contributions from IBM for CSIT) |
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 | Closed (3/12 - Based on discussion with Policy team, DCAE proceeding with new api implementation support) |
12 | Integration | 14-Feb-2019 | S3P- Geo-Redundancy - Lab Environment to be available by M4 | Integration | Brought it up to TSC | Test Rancher clusters in Windriver lab | High | 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 | Medium | Medium | Assessed Integration sanity test has been added to milestone checklist. The remaining issue is to solve blocking issues quickly |
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 | High | High | Assessed The current plan is to bring back TLab. No specific timeline is given |
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, VID | Get confirmation from PTLs that the breaking change is OK | Do not accept the change in Dublin | Low | High | Being assessed Closed 3/5, won't do in Dublin. Will add a release note to Dublin to warn implementors of the pending change in El Alto |
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 Moved to El Alto - closed |
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 Closed 2/28 as #68891 is resolved. |
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 descope. | May need to push to El Alto. | Medium | High | Closed - resolved questions with SDC team. |
19 | DMaaP | 25-Feb-2019 | For Footprint Optimization requirement, the decision regarding Ubuntu vs. Alpine vs. something else needs to be solidified. Need to know the final outcome so that teams can focus on their implementation efforts. | DMaaP, all apps on Linux impacted by this requirement. | TSC to hold a meeting to discuss this further to arrive at a conclusion. update - TSC held the meeting and decided to move further with Alpine for Dublin. | May need to push to El Alto | High | High | Closed |
20 | SDC | 3-Mar-2019 | May not be able to reach 55% test coverage due to insufficient resources | SDC | Asking the community to contribute as many tests as possible | Consulting TSC Finish by RC2 | High | Low | Being assessed |
21 | SDC | 6-Mar-2019 | May not be able to deliver a CSIT/OOM test | SDC | Asking the community to contribute such test | Consulting TSC Move to El Alto | High | Low | Being assessed |
22 | CLAMP | 8-Mar-2019 | May not be able to deliver a CSIT/OOM test | CLAMP | Asking the community to contribute such test | Consulting TSC Move to El Alto | Medium | Medium | Realized (this risk is perceived as low impact to Dublin) |
23 | SO | 11-Mar-2019 | May not be able to deliver a CSIT/OOM test | SO | Asking the community to contribute such test | Consulting TSC Move to El Alto | Medium | Medium | Being assessed (Need to assess this risk - although perceived low impact to Dublin) |
24 | Scaling Use Case | Mar 19, 2019 | Since VNF Instantiation is not working now we are unable to get valid contents of AAI custom query which is blocking develop of Policy | Policy | Must be able to instantiate VNFs soon! | Investigate if we can continue to use named query | High | High | Closed (Instantiation finally works) |
25 | SDC | 26-Mar-2019 | Won't integrate with AAF and support HTTPS | SDC | Postponing to El Alto | Postponing to El Alto | High | Medium | Closed |
26 | MultiCloud | 29-Mar-2019 | Lack of resource to meet S3P/Security requirement for MultiCloud Azure plugin: Docker Image footprint optimization, Secured Communication. | MultiCloud Azure Plugin | Postponing to EI Alto | Postponing to EI Alto | High | Low | closed (not do in dublin) |
27 | SDC | 1-Apr-2019 | Might not be able to deliver CCVPN use case support in Dublin | CCVPN use case team | Raised the risk in SDC weekly | Postponing to EI Alto | Medium | Medium | Being assessed Closing - move to future release |
28 | OOM | 10-Apr-2019 | Helm Chart transfer not complete | AAI, SO, Policy, Clamp, OOF | Allowed to complete migration post M4 | Postponing to EI Alto | High | Medium | Action plan discussed (Helm xfers until RC0 - else move to El Alto) Closed |