Attendees:

Please add your name in here:

Michael Fix (AT&T)
Mark Shostak(AT&T)
Rajamani Rajesh (Spirent)
Shiby Parayil (ICONECTIV)
Pierre Lynch (Keysight)
Georg Kunz (Ericsson)

**Issue with Zoom3 bridge today. Session closed prematurely. Restored about ~5 min later.

Goals of the 10/30 Meeting

RI POD10 status, Lesson's Learned, Manifest validations, and POD15 Target
RC Issues Log, Documentation Status, Automation Harness, VNF Prototype Test Planning

Agenda and Minutes:

Agenda Bashing
RI: status
- CNTT-RI Project Name Change → Common Infrastructure Realization & Validation (CIRV)
- Labs status - setup, automation
- 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.
- POD 10
  - Lesson's Learned
  - Recommendation for preparing POD15 before software deployment
  - Any modifications to POD10/15 to use it as a Reference.
RC: status
- Status | Milestones - CNTT Snezka (next CNTT release)
- RC WS Status | Issues
  - NFVI
  - VNF
  - Dev → Volunteers for Dev new issues by Cedric?
AOB

Status | Milestones:

CNTT Jan 2020 Release: CNTT Snezka
RC Documentation - https://github.com/cntt-n/CNTT/tree/master/doc/ref_cert/lfn

RC WS
1. NFVI (Lead = Rajesh, Mike)
  1. Issues, PRs
  2. Assistance Needed
    1. RA 1 requirements extraction → Rajesh, work with Mark S., Sridhar
    2. Manifest validations vs. RA Req
    3. Tune the declarative files to meet RA requirements (re-deploy)
  3. Status | Tasks (Work in progress)
    1. Receive Lab (date)
    2. Translate RA requirements to Manifest Needs (date)
    3. Tune Manifest to match RA requirements (Target End State Lab - POD15) - status of POD 10, then date for POD 15
    4. Testing
      1. Prepare automation harness - connectivity, validation (POD10)? – Cedric?
        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
  3. Status | Tasks (Work in progress)
    1. VNF Prototypes
      1. Families Identified
      2. Test Requirements Identified
      3. Strategy
        Use POD10 for Network Intensive.
        Measure stats related to the NFVi datapath capacity.
        Goal will be to demonstrate full automation of the environment (continuous deployment) with test cases with some useful test results (continuous testing).
        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

AOB:

Item 1
Item 2
Item 3

Notes:

RC
- Re-Org
  - Personnel
    - RC Organizer: Mike Fix (AT&T)
    - CNTT RC1 NFVI: Leads = Rajesh Rajamani (Spirent) and Mike Fix (AT&T; Co-lead = Dan Zu (Huawai)
    - CNTT RC1 VNF: Lead = Mike Fix (AT&T); Co-leads = Kanagaraj Manickam (Huawai), Yan Yang (China Mobile)
    - CNTT RC1 Dev: Lead = Cedric Ollivier (Orange); Co-leads = Kanagaraj Manickam (Huawai), Yan Yang (China Mobile)
- (old) RM Ch 8 Issues & PRs:

Actions:

10/30 Meeting
- Owner: All →Review/respond to GitHub issues by 06 Nov 2019
- Owner: Rajesh - get current status from Srihdar on POD10 installs, and open a GitHub issue to track the deployment by 01 Nov 2019
- Owner: Rajesh - determine a target date for POD15 installs, taking into consideration POD10 install completion, manifest validations, and API health/smoke tests, being done BEFORE POD15 installs by 01 Nov 2019
- Owner: Mark (Victor) - Setup call to start Tracing RM Comp to RC Chapter sections by 01 Nov 2019
- Owner: Fu Qiao - identify how to incorporate, or start developing, PDF and SDF consumables by 01 Nov 2019
- Owner: Leads - Review / Add Milestones to the Minutes in the Appropriate 'Status | Milestones' section by 06 Nov 2019
10/23 Meeting
- Owner: All →Review/respond to GitHub issues by 29 Oct 2019
- Owner: Leads - Assign / work action items by EOW 25 Oct 2019
- Owner: Rajesh - Meet w/ Trevor + others to discuss overall CNTT Lab Requirements (needs - e.g. POD10, 15, 17-18 (AirShip), 19-Test Tools, etc) by 23 Oct 2019
  - Rajesh (host), Trevor, Mark, and Mike - met to discuss the Intel labs and their intended use; acknowledge 10/15/19 are used for CNTT PoC/TargetState/TestTools labs. 17 and 18 are being used by the Airship project, but not CNTT. Next steps are to research the availability of a 2nd lab within Spirent, and to attend upcoming LF Lab Planning Sessions for future lab needs/support.
- Owner: Cedric - open a GitHub issue for the setup of the Jenkins hosts for RI validation by 23 Oct 2019
10/16 Meeting: Yielded time to RI Kickoff discussions. Refer to RI meeting notes for 10/16 for details
- Setup recurring call for RC series starting 10/23
10/9 Meeting
- Owner: All → Review/respond to GitHub issues by 16 Oct 2019
- Owner: Impacted Individuals (Test, Installer, Support) - needing access to POD15, request/receive access by 16 Oct 2019
- Owner: Mike - confirm with Cedric O. (Orange) if he will be the "lead" to centralize Implementation & Adoption of Test Hardness/Framework efforts on/by 11 Oct 2019
- Owner: Rajesh - confirm with Sridhar (Spirent) if he will be the "lead" to centralize s/w deployments on/by 11 Oct 2019