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

Compare with Current View Page History

« Previous Version 24 Next »

M1

Charts

Project Status
Closed T:
Active and Available Inventory 11 11
Application Authorization Framework 1 1
Clamp 11 11
Command Line Interface 11 11
Common Controller SDK 11 11
Data Collection, Analytics, and Events 11 11
Data Movement as a Platform 11 11
Documentation 6 6
External API Framework 11 11
Holmes 11 11
Integration 6 6
Microservices Bus 11 11
Modeling 11 11
Multicloud 11 11
Network Controller 11 11
ONAP Operations Manager 6 6
Optimization Framework 11 11
Policy Framework 11 11
Portal 11 11
Service Design and Creation 11 11
Service Orchestrator 11 11
Use Case UI 11 11
VNF Requirements 6 6
VNF Validation Program 11 11
Virtual Function Controller 11 11
Virtual Infrastructure Deployment 11 11
Vnfsdk 11 11
Total Unique Issues: 267 267
Showing 27 of 27 statistics.
View in Jira
Total: 267 . Chart by: Status

M1 Feedback to Projects (7/9) -  73% Completion

Congratulations to CLAMP, DCAE, 

June 19 - M1 release management issues published

July 8 - APPC, MUSIC and Logging are no more part of any ONAP release. These are moving under maintenance

  • AAI - Additional actions are required - TSC MUST HAVE Gaps
  • AAF - No PTL - Waiting feedback from the AAF Committers - Currently NO GO
  • CLI - 1 TSC MUST HAVE Gap (REQ-380) but no risk raised - Link to Release Planning to be added, architecture review to be scheduled
  • CCSDK- TSC MUST HAVE Gaps
  • DCAE - TSC MUST HAVE Gaps
  • DMaaP - Additional actions are required - TSC MUST HAVE Gaps
  • DOC - Project Life cycle notification to be sent
  • ExternalAPI - Additional actions are required
  • Holmes - TSC MUST HAVE Gaps
  • VNFREQS - Additional information requested concerning the Release Planning
  • VVP - Waiting feedback about Architecture Team; Additional information requested concerning the Release Planning and Project Review
  • VFC - No TSC MUST HAVE -Additional information requested concerning the Release Planning
  • VID - 1 TSC MUST HAVE Gap (REQ-361) but no risk raised - architecture review to be scheduled and project review notification to be sent to TSC when ready
  • VNFSDK -1 TSC MUST HAVE Gap (REQ-380) but no risk raised Link to Release Planning to be added, architecture review to be scheduled
  •  


  • No labels