David McBride

• Guilin RC1 Review
  • Ongoing issues with OOM/SO
    • Updates on status of OOM / SO?

      • Jira Legacy
        showSummary false server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SO-3322

      • Jira Legacy
        showSummary false server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SO-3346

      • Jira Legacy
        showSummary false server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SO-3352

  • Guilin Milestone Status (

• • 83%) - Congratulations to AAI, CLAMP, DCAE, DMaaP, EXTAPI, Mutlicloud, OOF, Policy, Portal, UUI, VVP, VID !!!
    • 3 Delivered - Waiting for Integration Team to confirm artifacts well received (Modelin, VFC and SNFSDK)
    • 2 Submitted - Waiting for OOM Team to merge Helm charts (CCSDK/SDNC)
    • 6 In progress - Fixing issues and releasing containers (MSB, SDC, SO, Holmes and CLI)
  • Issue status
    • Total open issues (<

• • • 150 ) - Great progress !!!
    • Issues sorted by project
    • High/highest priority 
  • Integration status
    • CI status
    • Docker version status
    • Test tasks
      
      • Process for indicating that an integration test is blocked
• ACTIONS:
  • Marketing Updates - Missing SECCOM, REQ Subcommittees + Anything from OVP PH2? Guilin Release Key Updates
  • What's the mitigated action plan for the next two weeks?
  • David McBride to publish RC2 tasks for projects that have completed RC1

• Honolulu
  • TSC Initial Feedback
    • Honolulu Release Requirements - 3 Use cases;

• • • 13 functional requirements

• • • (2 submitted post deadline) and 12 non functional requirements (1 submitted post-deadline)
    • M1 approval field was used to provide some feedback - only

• • • 4 functional requirements are candidate to be approved
    • Any new requirement submitted

• • • after Oct 16th, 2020 (Honolulu Deadline Submission) will be reviewed for the Istanbul release except Guilin requirement left-overs
    • Missing Honolulu Impact View per Component and a lot of information to understand the requirements, company commitments etc. - Please use the Requirement Template

• • • Missing company commitments, specially for non functional requirement (30 mins PTL practice might not cover all the needs)
    • REQ-428 - Is it aligned with the Modeling Subcommittee

• • • ?
    • Request to adopt a phasing approach for the Use Cases to avoid large number of components impacted within a release
    • Automated Test Cases are required for the Use Cases - have you factorized this as part of your company's engagement?

• • • EUAG priorities? No new use case but continuity of former use cases i.e. 5G SON, Network Slicing, CCVPN, CNF

+ 2 POC under review

Image Added 

• Use Case(s) that do not require new code but (simply test only) could be submitted any time (including Automation Tests)
• Anything else?

• ACTIONS - No later than Nov 12th, 2020:
  • Subcommittees to follow up with the respective requirement owners and ensure that the remaining information are provided 
  • Requirement Subcommittee to map Guilin requirements & EUAG priorities - Done
  • How does the TSC want to proceed with the first 4 approved requirements?
  • Guilin left-overs - start to meet Requirement Subcommittee for review
• Honolulu schedule & release management process
  • Meeting with Release Process team on Nov 9

Jessica Gonzalez

Krzysztof Opasiak Sylvain Desbureaux

cl664y@att.com