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

Compare with Current View Page History

« Previous Version 51 Next »

M1

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


M1 Feedback to Projects (11/9)

M1 Ready to Go - AAI, APPC, CLAMP, CCSDK, DCAE, DMaaP; ExtAPI, Integration,  Modeling, MutliCloud, OOM, Policy, SNDC, SDC, VID, VNFReqs, VVP

Conditionally approved: MSB

NO GO: AAF, CLI, HOLMES, MUSIC, OOF, PORTAL

Component not part of Frankfurt Release: Logging? Check with Integration team to re-use El Alto containers.

Major resource constraint for PORTAL - CALL For Help

AAI

  • Line coverage for repos are above 55%. Some clarifications are requested about unused repositories for Frankfurt - AAI-2666 - Getting issue details... STATUS

AAF

  • Concern about meeting code coverage requirements due to shifting resources. See  AAF-1008 - Getting issue details... STATUS
  • Questions about test planning in release plan, some "TSC MUST HAVE" not found.  Se AAF-1024 - Getting issue details... STATUS
  • Arch team to meet with AAF prior to M2 to review arch changes.
  • New API REQ-140 - Getting issue details... STATUS

Application Controller

  • Gating issue for code coverage goal  APPC-1757 - Getting issue details... STATUS - Require IT Support: IT-17899
  • Arch team to meet with Application Controller team prior to M2 to review architectural changes.  See  APPC-1752 - Getting issue details... STATUS
  • New API - see  APPC-1753 - Getting issue details... STATUS

Clamp

  • Requires architectural review.  See  CLAMP-522 - Getting issue details... STATUS
  • Moving to Java 13.  See  CLAMP-539 - Getting issue details... STATUS

CLI

  • Waiting feedback about oParent - CLI-238 - Getting issue details... STATUS
  • Have not committed to TSC "must have" requirements.  See  CLI-243 - Getting issue details... STATUS

HOLMES

  • Need to complete the remaining Release Management tickets

LOGGING

  • No feedback due to PTL Resignation - Not part of the release?

MSB

  • Provide feedback on documentation - MSB-402 - Getting issue details... STATUS

MULTICLOUD

  • Require IT Support: IT-18225 - MULTICLOUD-855 - Getting issue details... STATUS
  • Python 3 migration completed except for multicloud-azure.  See  MULTICLOUD-862 - Getting issue details... STATUS
  • K8s Security and traffic controller not committed - missing information MULTICLOUD-880 - Getting issue details... STATUS

MUSIC

  • Waiting for infor regarding 1 TSC "must have" requirement.  See MUSIC-529 - Getting issue details... STATUS
  • SONAR jobs for some repos are missing and below 30%

OOM

  • Architectural review required by M2.  See  OOM-2140 - Getting issue details... STATUS

OOF

  • Need to complete the remaining Release Management tickets
  • Require IT Support to fix SONAR job: OPTFRA-630

PORTAL

  • Address TSC must have requirements.  See  PORTAL-774 - Getting issue details... STATUS
  • Need test resources to achieve code coverage goals.  See  PORTAL-768 - Getting issue details... STATUS
  • parent update more complex than expected.  PORTAL-769 - Getting issue details... STATUS

SDC

  • Raise an IT Ticket to remove SONAR jenkins job on SDC-jtsoca. SDC-2605 - Getting issue details... STATUS

SO

  • Have not committed to TSC "must have" requirements and unclear which use case/requirement(s) are committed.  See SO-2485 - Getting issue details... STATUS

Usecase-UI

  • Have not committed to TSC "must have" requirements.  See USECASEUI-344 - Getting issue details... STATUS

VF-C

  • Have not committed to TSC "must have" requirements.  See VFC-1564 - Getting issue details... STATUS

VNFSDK













  • No labels