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 |
View in Jira
M1 Feedback to Projects (11/15)
M1 Ready to Go - AAI, AAF, APPC, CLAMP, CCSDK, DCAE, DMaaP; ExtAPI, Integration, Modeling, MUSIC, MSB, MutliCloud, OOM, Policy, SNDC, SDC, SO, VF-C, VID, VNFReqs, VVP, VNFSDK + OOF, UUI
==================================================================================
??? - impact on use case/requirement: OOF, PORTAL, UUI
Plan to move forward
Can we help the PTL with additional people? - PTL to confirm or not they have got additional feedback by 11/19 EOD
If not then can the impacted requirements/use cases be re-assessed?
if they can still deliver their use cases/requirements without them - Owners to re-assess by 11/21 EOD
if not then shall we make an exception? TSC final vote
============================
NO GO- no impact on use cases/requirements: CLI, HOLMES, LOGGING
=> Re-use El Alto containers except if any blocking issue are identified during the Frankfurt testing cycle by the Integration Team.
Any other finding (security, non blocking issue) should be documented in the Frankfurt Release Note
===========================
Major resource constraint for PORTAL, CLI - CALL For Help
AAI
AAF
- Arch team to meet with AAF prior to M2 to review arch changes.
- New API - REQ-140Getting issue details... STATUS
Application Controller
- Gating issue for code coverage goal - APPC-1757Getting 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-1752Getting issue details... STATUS
- New API - see - APPC-1753Getting issue details... STATUS
Clamp
- Requires architectural review. See - CLAMP-522Getting issue details... STATUS
- Moving to Java 13. See - CLAMP-539Getting issue details... STATUS
CLI
HOLMES
- Need to complete the remaining Release Management tickets
LOGGING
- No feedback due to PTL Resignation - Not part of the release?
MULTICLOUD
- Require IT Support: IT-18225 - - MULTICLOUD-855Getting issue details... STATUS
- Python 3 migration completed except for multicloud-azure. See - MULTICLOUD-862Getting issue details... STATUS
- K8s Security and traffic controller not committed - missing information - MULTICLOUD-880Getting issue details... STATUS
OOM
OOF
- JBB Jenkins jobs to be fixed to support Python 3.0: OPTFRA-630
PORTAL
- Waiting feedback regarding 1 TSC MUST HAVE. See - PORTAL-774Getting issue details... STATUS
- Need test resources to achieve code coverage goals. See - PORTAL-768Getting issue details... STATUS
- Will keep open this ticket since the team will use it to track their integration with oParent - PORTAL-769Getting issue details... STATUS
SDC
- Raise an IT Ticket to remove SONAR jenkins job on SDC-jtsoca. - SDC-2605Getting issue details... STATUS