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

Compare with Current View Page History

« Previous Version 15 Next »

This centralized page, for all Frankfurt 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
#1AAF11/6/2019AAF continues to have Resource issues for regular AAF work.No specific Team or component is impacted.If required, we will request a waiver for JUnit requirements.
MediumMediumUnknown
#211/6/2019

Description: Projects dependent on oparent are blocked from migrating to Java 11 until oparent v3 is released.

Risk: oparent v3 release may happen too late in the Frankfurt release cycle to enable projects to migrate to Java 11 on schedule.

All projects dependent on oparent.Release oparent v3 ASAP to give projects enough time to complete Java 11 migration within the Frankfurt schedule.Complete migration in the Guilin release (1H20)MediumLowV3 in process and expected to be released by the end of Nov '19.
#312/19/2020

DCAE - MOD delivery (Self Serve Control Loop)

Recent resource change impacts delivery of MOD scope planned under REQ-9                                                  

CLAMPPrioritizing MOD functional delivery for Frankfurt. CLAMP integration and other non-functional requirement (sonar coverage, https) will be deferred to GuilinComplete MOD delivery for Guilin release and continue SDC-DS for FrankfurtHighLow

1/9 - Assessed. CLAMP support through manual workaround for Frankfurt

12/19 - Will be reviewed early Jan and feasibility assessed

#4AAI1/9/2020

Description: AAI UI update to portal 2.6

Risk: Resource contention on AAI means that we might not make the backend software change by M2/M3

AAIAsked for resources, Amdocs has committed to provide a resource to look at it over next several weeks but M2/M3 is unlikelyPortal team might have suggestionHighLow, UI is not heavily used
#5AAI1/9/2020

Description: Securing Elasticsearch with FOSS

Risk: The AAI team does not have a path forward to enable encryption with a component with an acceptable license.  Reached out to Stephen Winslow for guidance and his response was that the approaches we had considered are unacceptable.  

AAISolicit suggestions for alternatives that can be used without license issuesContinue with unencrypted use of ElasticsearchHighLow
#6SDC1/13/2020The OVP Testing and Certification Support Within SDC (Frankfurt) feature might not be delivered in R6SDCAsking community for resourcesThe feature won't be deliveredHighMediumPlanned
#7SDC1/13/2020Secured connection to Cassandra might not be fully delivered in R6SDcAsking community for resourcesSecured connection will be developed in certain areas, while other areas will be left unsecured. Work will be completed in R7HighMediumPlanned
#8MUSIC1/14/2020MUSIC https support maybe not be fully delivered by Frankfurt releaseOOFAsking community for resourcesThis will not affect functionality and work will be completed in the next release if we get community resourcesHighMediumWork in Progress with IBM helping
#9INTEGRATION21/12/2019

Description: WIndriver lab availability after lab move

Risk: no resources for developers

Integrationcreate ONAP stack on Azurefind the budget to deploy new stackslowhigh
#10CLAMP19/12/2019DCAE-MOD CLAMP interactionCLAMPprioritizing other functionalities above this one and relying on manual operation to go around DCAE-MOD.Work will be complete in Giulin release depending on DCAE-MODlowhighPlanned
#11SO06/01/2020AAF integration is blocking the OJSI issuesSOAAF related changes are not yet merged that is blocking the OJSI issues.In discussion with security subcomitee.MedMedWorking with eth security subcomiittee.


  • No labels