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 Auto | Scaling Manual | PNF | Network Slicing | Data Collection | Path Selection | ||
| A&AI | Yes | Yes | No | Yes | Change Mngt: Available in Amsterdam | ||||
| Application Authorization Framework | NA | NA | |||||||
| APPC | NA | NA | No | No | NA | NA | NA | NA | Change Mngt: not impacted for Beijing, because Use case is about L3 VNF. L4 to L7 would be impacted. Scaling Auto and Manual: Lack of ressources. Lack of detailed requirements. |
| CLAMP | NA | NA | ? | ||||||
| Common Controller SDK | NA | NA | |||||||
| DCAE | NA | NA | No | ||||||
| DMaaP | NA | NA | |||||||
| Documentation | NA | NA | |||||||
| External API Framework | NA | NA | |||||||
| Holmes | NA | NA | |||||||
| Yes | Yes | Yes | |||||||
| Logging Enhancements Project | NA | NA | |||||||
| Microservices Bus | NA | NA | |||||||
| Modeling | Yes | NA | |||||||
| Multi VIM/Cloud | Yes | NA | Yes | ||||||
| MUSIC | NA | NA | |||||||
| ONAP CLI | NA | NA | |||||||
| ONAP Operations Manager | NA | NA | |||||||
| ONAP Optimization Framework | Yes | NA | No | ||||||
| ONAP Usecase UI Project Proposal | NA | NA | Yes | ||||||
| Policy Framework Project Proposal | Yes | NA | No | NA | NA | NA | NA | NA | Scaling: Lack ressource |
| Portal Platform Project Proposal | NA | NA | |||||||
| SDN-C | NA | Yes | ? | ||||||
| Service Design & Creation | Yes | NA | ? | Yes | |||||
| Service Orchestrator | Yes | Yes | Yes | Yes | |||||
| VFC | NA | NA | Yes | ||||||
| VID | NA | Yes | ? | Yes | |||||
| VNF SDK | Yes | NA | |||||||
| VNF Requirements | Yes | NA | No | ||||||
| VNF Validation (VVP) | NA | NA | |||||||