Guilin Risks
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 | High | 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
Update 9/4
decrease in coverage happened due to many new features coming with less coverage, hard to identify before merge has sonar results are only visibile after code is merged
Update 9/9 latest metrics shows we are good, above 55% line coverage for all SDC projects Risk CLOSED |
3 | SDC | July 6th 2020 Updated Oct 5 | REQ 351 - Migration to Java 11 | SDC | Try to get commitments from more companies to help on finishing the migration try to still do the upgrade and validate if Janus works upgrade only a subset of containers (the ones not using Janus | will request an exception for Guilin | High Low | Med 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 Updated 8/18 It has been identified that Janusgraph (the client lib used by SDC for the graph DB over Cassandra) is NOT compatible with java8 (due to the lack of support of one of its dep :apache/tinkerpop) It is very likely now that SDC will not support java8 fully due to this in guilin
Updated 9/9 We've been able to build JAVA 11 docker images, we will be trying them during pairwise, will revert if we find anything that is related to the Janusgraph incompatibility, so far nothing broke... Lowering probability of occurence STATUS : In Progress
Updated 10/5 We have not noticed any negative effect of Java11 on JanusGraph behavior, all our pairwise tests are successful and we will be keeping an eye on it for the Integration test cases validation. Lowering risk to low. |
4 | OOF | July 8, 2020 | Meeting non-functional requirements due to resource constraints | OPTF/CMSO | Try to get commitments from potential contributors | will request an exception for Guilin | Low | Low | Not occurred NFRs specific to CMSO are done. Common NFRs will be taken care along with other projects |
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 | Closed: Waiver requested for java components - Guilin Exception Request for DCAE |
6a | DCAE | July 8, 2020 | DCAE being large project with 40+ component, need more time for complaince with non-functional requirements REQ-366 - Containers must crash properly when a failure occurs (DCAEGEN2-2326) | DCAE | Have commitment from Ericsson; more contributors will help mitgating the risk | Will be worked in-phase and need exception for components not compliant | High | Medium | Closed: Waiver requested -Guilin Exception Request for DCAE Identified 8/24/2020 - Ericsson team indicated issues to support; evaluating options to phase (or get additional time). Will likely require an exception for Guilin Note: Split original item into 6a/6b for better tracking |
6b | DCAE | July 8, 2020 | DCAE being large project with 40+ component, need more time for complaince with non-functional requirements REQ-365 - Containers must have no more than one main process (DCAEGEN2-2327)
| DCAE | Have commitment from Ericsson; more contributors will help mitgating the risk | Will be worked in-phase and need exception for components not compliant | Medium | Medium | Closed 8/24/2020 - ChinaMobile and Nokia volunteered to help; this item could be closed soon. |
7 | DCAE | July 8, 2020 | Resource/time constraint for supporting nonfunctional REQ-351 (Java11 upgrade). MOD-Genprocessor components will need exception (due to NiFI upstream dependency) | DCAE | More companies to help with migration | Will be worked in-phase and need exception for components not migrated. | Medium | Low | Closed Exception created for deferred components - Guilin Exception Request for DCAE |
8 | Portal | July 8, 2020 | Meeting the following Non-Functional Priority 1 and 2 Requirements https://jira.onap.org/browse/REQ-380 https://jira.onap.org/browse/REQ-373
| 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 |
9 | Holmes | July 9, 2020 | There's no env for the team to carry out any functional tests. Due to the network restriction in our company, we have no access to the WindRiver lab, so it seems impossible for us to do any tests after code modifications. This would impact the integration with AAF. | Holmes | Trying to apply for HW resources to build up a testing env within our company. | will request an exception for Guilin | Medium | Medium | In-progress. Still trying to deploy the Frankfurt release in our private env. Problems were encountered. Still trying... |
10 | SDC | July 9, 2020 | Meeting non-functional requirements - | SDC | Need support from community | Phased approach and file exceptions for the items that cannot be delivered or picked up by community | High | Medium | Identified Update Oct 5th As planned these could not be achieved for Guilin, will see if they are planned for next releases |
11 | MultiCloud | July 9, 2020 | Meeting non-functional requirements - REQ-373 , REQ-363 , REQ-351, REQ-349 , | MultiCloud | Need support from community | Will request waiver in Guilin release | High | Medium | Waiver created |
12 | AAI | July 9 2020 | Meeting non-functional requirements, https://jira.onap.org/browse/REQ-380 https://jira.onap.org/browse/REQ-361
| AAI | Need support from community | Will request waiver in Guilin release | High | Medium | Waiver Created |
13 | MSB | July 15th | Can not meet REQ-351 lack of capacity | MSB | Need support from community | Will request waiver in Guilin release | High | High | Identified update 1017 Waiver created |
14 | Modeling | July 15th | Meeting non-functional requirements - | Modeling | Need support from community | Will request waiver in Guilin release | High | High | Identified
update 0929 Waiver created |
15 | VID | July 15th | Can not Meeting non-functional requirements - REQ-361 | VID | Need support from community | Will request waiver in Guilin release | High | High | Identified |
16 | VF-C | July 15th | Meeting non-functional requirements - | VF-C | Need support from community | Will request waiver in Guilin release | High | High | Identified
update 0929 Waiver created |
| Policy | July 23 2020 | Meeting non-function requirements - REQ-379 (approved base image) compliance and GPL v3 packages | Policy | Need finalized approval base image ASAP, in order to request the resource from community | Will request waiver in Guilin release | High | Low | Waiver created |
18 | Holmes | July 28, 2020 | Don't know where to get support regarding AAF integration. | Holmes | Mark the requirement as a stretched goal. | Defer it to the next release. | High | Medium | Identified Now M4 is close and we haven't even get started due to Risk 9. This has to be deferred to the next release. |
19 | UUI | July 29, 2020 | Can not Meeting non-functional requirements - REQ-361 | UUI | Mark the requirement as a stretched goal. | Defer it to the next release. | Low | Low | Identified |
20 | CCSDK | July 31 2020 | Meeting non-function requirements - REQ-379 (approved base image) compliance | CCSDK | Need finalized approval base image ASAP. Specifically, need guidance on which base image to use for openjdk 11 on alpine. | Will request waiver in Guilin release | High | Low | Closed - our docker containers now use one of the 2 approved ONAP base images |
21 | SDNC | July 31 2020 | Meeting non-function requirements - REQ-379 (approved base image) compliance | SDNC | Need finalized approval base image ASAP. Specifically, need guidance on which base image to use for openjdk 11 on alpine. | Will request waiver in Guilin release | High | Low | Closed - our docker containers now use one of the 2 approved ONAP base images |
22 | DCAE | Aug 24,2020 | Meeting non-functional requirement REQ-373 (ONAP must complete update of the Python language (from 2.7 -> 3.8) Among 8 components identified only 3 are completed as of 08/24 | DCAE | More companies to help with migration | Will be worked in-phase and need exception for components not migrated. | Medium | Low | Closed 9/15 - Exception created for deferred components - Guilin Exception Request for DCAE 8/31 - Majority of components migration complete; need exception for Cloudify, Plugins, AA. |
23 | Integration | Aug 11, 2020 |