This centralized page, for all Guilin 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 | ESR | July 1st 2020 | The REQ-341 has dependency on ESR for updating the K8s cluster information. | REQ-341 | To have the friends from Aarna network to help us in this functionality. | In case ESR does not make it to Guilin, we will use the postman for updating the AAi with the detais | High | Med | In progress. |
| 2 | SDC | July 6th 2020 | The REQ-349 - Coverage of 55% | SDC | Minimize impact of changes to limit breakage of coverage metrics | will request an exception for Guilin | Low | Low | Current metrics are at 54.8%, some sonar metrics do not show up on main page but are visible in details. In Progress for improvments |
| 3 | SDC | July 6th 2020 | REQ 351 - Migration to Java 11 | SDC | Try to get commitments from more companies to help on finishing the migration | will request an exception for Guilin | Medium | Low | Migration to Java 11 is well under way on main SDC project, still the complexity of project implies that there are several unknowns in completing this change |
| 4 | OOF | July 8, 2020 | Meeting non-functional requirements due to resource constraints | OPTF/CMSO | Try to get commitments from potential contributers | will request an exception for Guilin | High | Low | Requesting commitments from more companies to meet the non-functional requirements |
| 5 | DCAE | July 8, 2020 | Meeting non-function requirements - REQ-379 (approved base image) complaince | DCAE |
| Will be worked in-phase and need exception for components not migrated | High | Low | Requesting commitments from more companies to meet the non-functional requirements |
| 6 | DCAE | July 8, 2020 | Meeting non-functional requirements - | DCAE | Need more time to assess DCAE components impacted | Will be worked in-phase and need exception for components not complaint | Medium | TBA | Identified |
| 7 | DCAE | July 8, 2020 | Resource/time constraint for supporting nonfunctional REQ-351 (Java11 upgrade). Some MOD components will need exception (due to NiFI upstream dependency) VES-Mapper/RESTConf - Resource TBC | DCAE | More companies to help with migration | Will be worked in-phase and need exception for components not migrated. VESMapper/RESTconf can be deprecated if no community support | Medium | Low | Requesting commitments from more companies to meet the non-functional requirements |
| 8 | Portal | July 8, 2020 | Meeting Non-Functional Priority 1 and 2 items https://jira.onap.org/browse/REQ-380 | Portal | Need support from community | Phased approach and file exceptions for the items that cannot be delivered or picked up by community | High | Medium | Identified |