This centralized page, for all El-Alto 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 | Aug 1, 2019 | After enabling Javascript (JS) coverage, the portal's coverage dropped from 72.9% to 21.6%. This is a huge drop, as the project contain good amount of Javascript code. The risk here is not achieve 55% coverage with JS in El Alto. | PORTAL | The team is planning to upgrade to latest Angular 6 which is in Typescript (rather than in Javascript), along with this new upgrade, the team will explore the test coverage process for typescript code. So, the recommendation is not to invest efforts in adding code coverage for old JS code, rather invest in typescript code. | For El Alto, it is recommended to disable JS code coverage and start enabling coverage for typescript code. However, achieving 55% code coverage in new Typescript code is aggressive for El Alto release. | High | Medium | In Progress on mitigation plan | |
| 2 | Seshu Kumar Mudiganti | July 25 2019 | OJSI issues | ||||||
| 3 | Aug 7, 2019 | Due to unanticipated delays associated with issues in self release process and in new CLA process, we will be approximately a week behind schedule in delivering El Alto early drop release artifacts. | CCSDK, SDNC | Recommend that we delay the El Alto early drop by a week, since it is likely that other projects are experiencing similar challenges. | High | High | RESOLVED - El Alto early drop cancelled | ||
| 4 | Aug 1, 2019 | Early Drop picks up planned public Lookup name designed in Dublin. | All AAF using "Locator" | Per Brian F, we found all references we could in OOM files for Locator, and changed during Integration Tests | Per Brian, "We're committed". However, we've worked through known instances around Aug 1. | Very Low (because of pre-release effort) | Low | Not a blocker for Integration at last check. | |
| 5 | July 25, 2019 (email sent to onap-release list) | Enablement of Javascript coverage dropped policy/engine repo below 55% | Policy | We have a committed resource who will try to bump coverage via Java as that is the fastest/easiest route. | This repo is scheduled for deprecation post-Frankfurt so a waiver would be desirable. | Medium | Low | In Progress | |
| 6 |
| Policy project is the initial project for supporting multi-architecture docker support and the use dockerhub. The changes for this are coming in late in the dev process and may be disruptive to our artifact delivery. | Policy | Managed by both LF and Cristina Pauna/Paul-Ionut Vaduva as a high priority, working with the policy team to ensure minimal disruption. | Cristina and Paul-Ionut will provide resources to help solve any issues arising. | Low | Low | In Progress assessing ramifications of this. | |
| 7 | Aug 31, 2019 | APPC docker release on 9/6 (M4) | APPC |
| Continue working with Jess and Dan to resolve the issues. | High | High | In Progress | |
| 8 | Sep 1, 2019 | Might not solve all OJSI tickets in El Alto | SDC | Solve in Frankfurt those we can't close in El Alto | Update CII accordingly | High | High | In progress | |
| 9 | Gervais-Martial Ngueko | Sep 2, 2019 | Enablement of Javascript coverage and introduction of new JS framework might dropped clamp coverage repo below 55% | CLAMP | Will be solved in Frankfurt depending on available Resources | Continue adding more tests as Resources bacame available | High | Low | In Progress |
| 10 | Gervais-Martial Ngueko | Sep 2, 2019 | Might not implement all CSIT test | CLAMP | Will be solved in Frankfurt depending on available Resources | Continue adding more tests as Resources bacame available | High | Low | In Progress |
| 11 | Takamune Cho | Sep 4, 2019 | OJSI tickets | APPC | Using AAF's bath feature to allow certain user to access ODL url path | working with Sai from AAF | High | Low | In Progress |
| 12 | Sep 4, 2019 | Enabling HTTPS on OOF-Music Interface | OOF | Changes from the OOF end would be made such that we can start consuming HTTPS once MUSIC's helm charts are fixed for using HTTPS ( OPTFRA-330 - Getting issue details... STATUS , OPTFRA-562 - Getting issue details... STATUS ). Our pairwise testing could still happen over http. | Work with the Music team for workarounds. | High | Low | In Progress | |
| 13 | Sep 4, 2019 | Not all OJSI tickets can be addressed in El Alto | DCAE | Will be targeted in Frankfurt depending on resource availability | Update CII accordingly | High | High | In Progress | |
| 14 | Sep 4 2019 | Certain El-Alto scoped item/jiras related to DCAE MS optimization/enhancements may have to be deferred to due to resource changes | DCAE | Will be targeted in Frankfurt | Continue using Dublin MS version | Medium | Low | In Progress | |
| 15 | Prudence Au | September 5, 2019 | Due to resources issue, might not be able to resolve all high/highest bugs for El Alto | Logging | Will be targeted in Frankfurt | There are JIRA tickets associated to this | Medium | Low | In Progress |