This centralized page, for all Casablanca 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 | Katel34 | 6/27/2018 | CII Badging - Casablanca Release Criteria is about addressing test coverage (including JS) Therefore some projects might not pass their CII Badging. | Any Project team who has JS as part of their code and who will not have enough bandwidth | Find an alternative to the current proposal | If it is confirmed that the solution (https://lists.onap.org/g/Onap-seccom/topic/cii_badging_passing_level/22721721?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,22721721) is the right way to move forward then we believe that we should split the JS test coverage into several phases that will be implemented across multiple ONAP releases depending on each project’s bandwidth: Phase 1 – Setup the infrastructure Phase 2- Analyze the SONAR test coverage and build a plan to meet JS test coverage criteria Phase 3- Add test cases to meet the JS test coverage criteria | High | High | In-Process 6/27/18 update:
|
| 2 | Portal | 6/27/2018 | Policy, VID apps that use portal/sdk will be directly impacted under S3P for logging support; also impacted under the JavaScript code coverage support required from portal/sdk due to lack of resources; | Policy, VID, Portal | Requesting open community for resources who can help with logging and JavaScript coverage in portal/sdk. | High | High | Assessed | |
| 3 | Portal | 6/27/2018 | Policy, VID, AAI, SDC will be impacted under Security for AAF role management support required from portal/sdk due to lack of resources; | Policy, VID, AAI, SDC, Portal | Requesting open community for resources who can help with AAF role management in portal/sdk. | High | High | Assessed | |
| 4 | Portal | 6/27/2018 | 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, Portal | Requesting open community for resources who can help with deployment upgrades in Portal using OOM. | High | High | Assessed | |
| 5 | Policy | 7/10/2018 | Scale Out Use Case: Moving to Dmaap based API call to SO for Scale out. This API was for both VID and Policy to use instead of the REST call for simplicity. | Policy | It doesn't look like the SO team has any epic or user story for developing this work in their M1 planning template. | Fallback to using the current RESTful API to make the call - but this may not be sufficient to satisfy the Use Case. | High | High | |
| 6 | OOM | 7/24/2018 | Helm Chart transfer of ownership to project teams. | Prevents project teams from owning helm charts for their components. But more importantly, prevents CI/CD. | High | High | Assessed | ||
| 7 | CLAMP | 7/19/2018 | DCAE-DS service template and policy model not committed for Casablanca | Prevent project to improve the flexibility for supporting new mS | need to agree at least on a design during Casablanca release | CLAMP will fallback on using just the blueprint for C.L distribution from DCAE-DS/SDC | High | Medium | In progress |
| 8 | CLAMP | 7/19/2018 | Policy team not yet sure to support the full api needed for Guard policy | prevent the support of the scale out use case | starting the work using the not final API version given by policy team. | CLAMP not able to support the scale out use case. would need the final policy API by 8/24 to be able to implement it in Casablanca. | Medium | Medium | in progress |
| 9 | APPC | 7/25/2018 | The requirement for A&AI query is not finalized | prevent the support of the scale out use case | upstream component has to post the data to A&AI, so that APPC can query from A&AI | There is a workaround for using curl command to post/query data for A&AI. but it's a manual step. | Medium | ||
| 10 | APPC | 7/25/2018 | The requirement for new traffic migration LCM API is not finalized | prevent the support of the change management use case | need a agreement with owner of Change Management use case to see how we can define new traffic migration LCM API in R3 and look for any alternative in R3 | 7/24/2018: met with Ajay and team, we may use ansible server approach in R3. but still under discussion and investigation. | High |