OBSOLETE, all requirements were moved to Merged list of R2 functional requirement candidates
R1 missing Platform capabilities
Residential vCPE Multi-cloud support
Support real-world service design in SDC with standard based TOSCA model
Unify all design tools (DG, Policy, DCAE Template, CLAMP, Holmes, A&AI schema, etc) and make them as integral part of service design
VNF image management
DNS name configuration
|Title||Priority||Summary||Use Cases||R1 Status||R2 Status|
|Provide powerful test and debug environment/tools||1||Powerful tools are needed to facilitate service development and operation.||All||Not supported|
|Integrated design environment||1||Integrate workflow design, policy design, CLAMP, DG design, and AAI schema design into SDC||All||Not supported|
|Platform capabilities exposure.||1||Ability to stitch together functionality provided by ONAP components to achieve an E2E management task.||Change Management||Not supported|
|VNF Components Capability||1||The capability to model complex VNFs composed of VNFCs which are scaled independently.||All||Unknown.|
|PNF Modelling Capability||1||Support PNF modeling and associated workflow design in SO.||All||Supported by SDC and A&AI. Not supported by SO.|
|VNF Homing Capability||2||Homing functionality for choosing the appropriate MultiCloud instance for ONAP components and VNFs in a Distributed DC deployment||All||Not Implemented.|
Provided by ONAP-OF Homing and Allocation Service.
|Enhanced Platform Awareness Capability||2||The capability orchestrate and configure VNFs with EPA requirements.||Performance, Security and resource isolation||Not Supported.|
|Enhance SDC capabilities||2||A list of features are suggested.||All||Not supported|
|Enhance SO Capabilities||2||A list of features are suggested.||All||Not supported|
|Is there a need to consolidate VID and UUI?||2||Discussion is need on if there is a need to consolidating VID and UUI into one GUI.||All||Not supported|
|Dynamic Update of Cloud Resources in Multi-Vim||2||How to support dynamic addition/removal of cloud resources in multi-vim?||All||Not applicable|
|Standard/Generic Process to Pass Configuration Data to APPC||2||How to pass potentially large amount of application-level configuration data to APPC, especially during service deployment.||All||Not applicable|
|Task Scheduling||2||Allow tasks to be scheduled for execution||All||Not implemented.|
|Service Modification Capability||2||The capability to modify existing services||All||Not implemented.|
|VNF/VNFC Scale-Out Capability||3||The capability scale-out a VNF or VNFC by adding vServers.||All||Not Supported.|
|VNF/VNFC Scale-Up Capability||3||The capability to scale-up a VNF or VNFC by adding resources.||All||Not Supported.|
|Service Ownership||4||Allow services to have set of owners.||All||Not implemented.|
|Locking Mechanism.||4||Support of locking mechanism that can prevent different parts of ONAP from accessing||Change Management||Not supported|
|Service Aggregation Capability||4||The capability to model and orchestrate services which are composed of other services, recursively||All||Only Allotted Resource implemented.|
|Service Chaining Capability||5||The capability to model and orchestrate chains of connected services.||All||Not Supported.|
To add a missing capability:
- View one of the existing capabilities.
- Click the button at the top right, to view the page menu, and select Copy.
- Accept the defaults.
- Overwrite the copied content as appropriate.
- Make sure the new page has the label platform-capability, so it is included in the query above.