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 Name | Functional Requirements | Comments | ||||||
| HPA | ChangeMngt | Scaling | PNF | Network Slicing | Data Collection | Path Selection | ||
| A&AI | COMMITED JIRA | Yes | No | Yes | Change Mngt: Available in Amsterdam | |||
| Application Authorization Framework | No | NA | ||||||
| APPC | No | NA | No | Lack of resources | ||||
| CLAMP | No | NA | ? | |||||
| Common Controller SDK | No | NA | ||||||
| DCAE | No | NA | No | |||||
| DMaaP | No | NA | ||||||
| Documentation | Yes | NA | ||||||
| External API Framework | No | NA | ||||||
| Holmes | No | NA | ||||||
| Yes | Yes | Yes | ||||||
| Logging Enhancements Project | No | NA | ||||||
| Microservices Bus | No | NA | ||||||
| Modeling | Yes | NA | ||||||
| Multi VIM/Cloud | Yes | NA | Yes | |||||
| MUSIC | No | NA | ||||||
| ONAP CLI | No | NA | ||||||
| ONAP Operations Manager | No | NA | ||||||
| ONAP Optimization Framework | Yes | NA | No | |||||
| ONAP Usecase UI Project Proposal | No | NA | Yes | |||||
| Policy Framework Project Proposal | Yes | NA | ? | ? | ||||
| Portal Platform Project Proposal | No | NA | ||||||
| SDN-C | No | Yes | ? | |||||
| Service Design & Creation | Yes | NA | ? | Yes | ||||
| Service Orchestrator | Yes | Yes | Yes | Yes | ||||
| VFC | No | NA | Yes | |||||
| VID | NA | Yes | ? | Yes | ||||
| VNF SDK | Yes | NA | ||||||
| VNF Requirements | Yes | NA | No | |||||
| VNF Validation (VVP) | NA | NA | ||||||