...

Agenda and Minutes:

• Agenda Bashing
• Antitrust: https://r.lfnetworking.org/Antitrust%20Slide.pdf
• RI: status
  • CNTT-RI Project Name Change → Common Infrastructure Realization & Validation (CIRV)
  • Labs status - setup, automation
    • Discussed PR 535 as a start for Installer Requirements
    • Discussed need for RI (as well as RC) and Run Book documentation to be delivered with Jan F2F
    • See complete minutes from RI meeting.  CNTT - RI - 01
  • Tracking:
    • Core: Issues, PRs
    • Labs: Issues, PRs
    • Dev: Issues, PRs
  • PR to review:  Minor edits to RI-1 Core CH2 section headings and initial content: @fuqiao123 requested your review on: #519 Update chapter02.md.535 discussed and reviewed, along with general push for team members to review open PRs and approve
• RC: status
  • Status | Milestones - CNTT Snezka (next CNTT release)
  • RC WS Status | Issues
    • NFVI
    • VNF
    • Dev → Volunteers for Dev new issues by Cedric?
• AOB

...

• General
  • CNTT Jan 2020 Release:  CNTT Snezka
  • RC Documentation - https://github.com/cntt-n/CNTT/tree/master/doc/ref_cert/lfn
    • To be written (completed) by the CNTT Jan Release
• Work-stream
  1. NFVI (Lead = Rajesh, Mike)
     1. Issues, PRs
     2. Assistance Needed
        •  (In progress) RA 1 requirements extraction → Rajesh, work with Mark S.,
        Sridhar
        • Sridhar  → work in progress
        •  (In progress) Manifest validations vs.
        RA Req
        • RA Req → discussed in the RI work stream call, work in progress as AirShip manifests were followed for installs, but confirmation needed to ensure RA requirements have been met; offline discussion happening in email to confirm if manifest require changing
        •  Tune the declarative files to meet RA requirements (re-deploy)
     3. Status | Tasks (Work in progress)
        •  Receive Lab (date)
        •  (In progress)
        •  Translate RA requirements to Manifest Needs (date)
        •  Tune Manifest to match RA requirements (Target End State Lab - POD15) - status of POD 10, then date for POD 15
        •  Testing
          1. Prepare automation harness - connectivity, validation (POD10)? – Cedric?
             1. e.g. functest-smoke-cntt was just created. neutron-tempest-plugin-api is already conformed with the current API section.
          2. Create Test Plan
          3. Finalize Test Harness/Framework
          4. Perform Manifest Validations
          5. Results Collection & Normalization
  2. VNF (Lead = Mike)
     
     1. Issues, PRs
     2. Assistance Needed
        1. Empirical Validations - VNF Prototype Plan / Strategy
        2. Trevor - details / dates for Network profiles and testing
     3. Status | Tasks (Work in progress)
        1. VNF Prototypes
           •  (In Progress) Families Identified
           •  (In Progress) Test Requirements Identified
           •  

             Strategy

             1. Use POD10 for Network Intensive. 

             2. Measure stats related to the NFVi datapath capacity.

             3. Goal will be to demonstrate full automation of the environment (continuous deployment) with test cases with some useful test results (continuous testing).
             4. Status?  Then look at adding compute and storage intensive VNFs and identify test cases that map back to CNTT specified capabilities. (Luc, Sridhar, Al, Trevor - creating more detailed plan?).
        2. Testing
           1. Create Test Plan
           2. Finalize Test Harness/Framework
           3. Results Collection & Normalization
  3. Dev (Lead = Cedric)
     1. Issues, PRs
     2. Assistance Needed
        1. Deployment Validations and continuous deployment / integration 
     3. Status | Tasks (Work in progress)
        1. Jenkins setup
        2. VNF prototype
           1.  Development
           2. Connectivity to POD15

...