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

Compare with Current View Page History

« Previous Version 12 Next »

Summary of the Teams commitements to support Beijing functional Requirement.

This is summary of outcome of Use case Sub-Committee.

Legend:

Yes: Committed by PTLs to Beijing Release

No: Not committed to Beijing Release

NA: Project not impacted by functional requirement

Project NameFunctional RequirementsComments

HPAChangeMngtScalingPNFNetwork SlicingData CollectionPath Selection
A&AI

Yes

YesNoYes


Change Mngt: Available in Amsterdam
Application Authorization FrameworkNANA





APPCNANANo



Lack of resources
CLAMPNANA?




Common Controller SDKNANA





DCAENANANo




DMaaPNANA





DocumentationNANA





External API FrameworkNANA





HolmesNANA





Integration

YesYes
Yes



Logging Enhancements Project NANA





Microservices BusNANA





ModelingYesNA





Multi VIM/CloudYesNAYes




MUSICNANA





ONAP CLINANA





ONAP Operations ManagerNANA





ONAP Optimization FrameworkYesNANo




ONAP Usecase UI Project ProposalNANAYes




Policy Framework Project ProposalYesNA??



Portal Platform Project ProposalNANA





SDN-CNAYes?




Service Design & CreationYesNA?Yes



Service OrchestratorYesYesYesYes



VFCNANAYes




VIDNAYes?Yes



VNF SDKYesNA





VNF RequirementsYesNANo




VNF Validation (VVP)NANA





  • No labels