Wednesday August 28, 2019

Attendees:

Please add your name in here:

Agenda:

  • Open Issues
    • Botrange (residual) → zero(0) open prior to, or coming out of, Antwerp F2F
    • Pre-Existing (ownership) - reviewed outstanding issues
    • New Issues | PRs
  • RI Labs - Intel Lab(?)
    • Is a formal request needed?
      • Yes.  Submit the standard (BAU) JIRA ticket for OPNFV Labs procurement.  → Mike to reach out to Bin to initiate the process.
    • Requirements from RA?  (How to extract?)
      • No formal mechanism, or form, (yet) to extract the RA from the CNTT material.  Will leverage PDF and SDF descriptor files & file format for now, along with Intel specific lab documents/formats needed for lab setup.
    • Inventory of Intel (OPNFV) labs in progress → Trevor is handling
      • 6 servers/POD - known
      • Check status and configuration of labs - in progress
      • Confirmation pending of lab availability (few weeks)
  • Deferred discussion
    • Discuss Ch 8 re-write (2nd half of call)
    • Section 8.7 Review - to be discussed 10/2
  • Next Steps
    • RI Labs - confirm availability (10/9), attempt AirShip installer (Sridhar, Mark, Mike, 10/16), confirm & correct deployment issues (10/16-EOM Oct)
    • Continued Documentation Revisions & Reviews

Actions:

  • 10/2 Meeting
    • Owner: All → Review/respond to GitHub issues by   
    • Owner:  All → Continue adding/editing content to Ch 8 (open Issues, generate PR) by   
    • Owner: Mike → Contact Bin Hu to open JIRA ticket to formalize use of Intel lab/POD(s) for RI 1.
      • (In progress) Sent email requesting support (10/2)
    • Owner: Mike → open a PR for minor Lab Req changes from 4x compute nodes to 10x based on need to support B/N/C flavors (2x nodes each)
    • Owner: Mike (and Trevor) → open an Issue (#363) to track comparison and confirmation of terms utilized in the Test Chapter align with OVP/CVC (assigned to Trevor)
    • Owner: Mike → open new Issues to track discussion and resolution to the following items:
      • Define Compliance (Issue 363/Trevor)
      • Clarify that Certification is not possible as the open source team cannot "commercialize" a product (Issue 375/TBD)
      • Update Methodology with clear demarcation of CNTT vs. Community/Supplier Test Responsibilities (Issue #376/TBD)
  • 9/18 Meeting
    • Owner: All → Review/respond to GitHub issues by  
    • Owner:  All → Continue adding/editing content to Ch 8 (open Issues, generate PR) by  
  • 9/11 Meeting
  • 9/4 Meeting
    • Owner:  All → Requesting all team members to review/comment on 8.6 between 9/3-9/11, for discussion 9/11. 
    • Owner: Mike Fix (AT&T) - Verify Validation/Verification/Certification is consistent with CVC verbiage
    • Owner: Murtuza Khan (AT&T) - Add additional test case descriptions 
    • Owner: Kyle Greenwell (Verizon) - generate a PR to merge w/ Master
  • 8/28 Meeting
    • Done!  Add Labels to GitHub Issues → to help with Search (Owners: All, but primarily Mike, Kyle) (recommendation from Kelvin, Nokia)
    • Done - but, added to 8.7.9!  Add Murtuza Khan assessment of Test Cases/Harness (in relation to Functest) on Wiki page → under consideration (Owner: Murtuza K)
    • Done - but, need contributor support to assess.  Add {Name} XCI --> include to Etherpad installer project gap analysis → done (Owner: Mike Fix; will also inform CNTT internal Ch 8 team on 8/28 about the new Installer effort needing review)
    • Owner: ALL → Requesting all team members to review/comment on next sections 8.4-8.6 (changed to 8.5) by 9/3 for discussion 9/4. 


  • No labels