You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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 IDProject Team or person identifying the riskIdentification DateRisk (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
1SDNC1/14/19NETCONF/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/APPCWe will try to target NETCONF/TLS for an early sprint to allow ample recovery time if we need to fall back to NETCONF/SSH



215/01/19PNF 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 PNF use case in Dublin.CCSDK
CDS
SO



LowAssessed
3Portal8 Jan 2019Security impact on Policy, VID apps that use portal/sdk regarding addressing NexusIQ security issues which is not committed by Portal team so far due to lack of resources;Policy, VIDRequesting open community for resources who can help with NexusIQ security critical issues in portal/sdk and portal.
HighHighAssessed
4Portal8 Jan 2019Impacts 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/TestingRequesting open community for resources who can help with Footprint Optimization, Logging Capabilities in Portal under OOM scripts.
HighLowAssessed


  • No labels