2019-11-27 - [CNTT - RC - 01] - Meeting Agenda and Minutes
Attendees:
Please add your name in here:
@Rajamani, Rajesh(Spirent)
@Mark Shostak (AT&T)
@Deepanshu Bhatia (VoerEir)
@Mark Beierl (VMware)
Goals of Meeting/
Agenda Bashing
Antitrust:
(see below) Confirm agreement on Table of Contents
(see below) Chapter Progress by Authors per recent PRs created
VNF & Storage Questions (discussion needed & path-forward)
Can we run SampleVNF and FuncTest VNF connectivity/validation? (Owner?)
Owner to review StorePerf and start that work in POD10
Prototype Plan Status - is this something we can use today in POD10/15? (Trevor)
Deployment and Compliance Validation (Cedric) > unless covered in RI discussions
RM/RA requirements extraction (Rajesh, Sridhar) > unless covered in RI discussions
*****************************
Table of Contents + Owners:
RC: status | issues
NFVI
Ch01: Introduction: Rajesh, Kanagaraj, Manik (confirmed) - https://github.com/cntt-n/CNTT/pull/658
(Refer to PR https://github.com/cntt-n/CNTT/pull/658)
Synopsis
Introduction
Principles & Guidelines
Goals & Objectives
Best Practices
Verification methodologies
Assumptions & Dependencies
Results Collation & Presentation
Measurements, Monitoring
Governance
Resources & References
Ch02: NFVI E2E C&V Framework Requirements: Cedric, Manik (confirmed) - https://github.com/cntt-n/CNTT/pull/701
Methodology
Certification Strategy & Vehicle
Profiles Reference
Compliance, Verification, and Certification
Entry & Exit Criteria
Frameworks: e.g. Functest (StorePerf, SampleVNF, others?)
Ch03: NFVI Test Case Requirements: Georg, Toshi https://github.com/cntt-n/CNTT/pull/702
Assumptions: Automatable, Integrated with CICD tool chain
Type of requirement: Bare metal, API, etc
Table showing Profile Catalog
Identify SW Reference
Identify HW Reference
Options Available / Configured
Extensions Available / Configured
Ch04: NFVI TC Traceability to RA Requirements: Rajesh, Dan, Ashok, Deepanshu (confirmed)- https://github.com/cntt-n/CNTT/pull/703
SME: Functest knowledge
Define RM/RA-1 Openstack requirements
Map Framework to Requirements
VNF
VNF Prototype Plan - details, dates (Trevor)
Ch05: VNF E2E C&V Framework Requirements: Kanagaraj, Cedric, Shiby (confirmed) - https://github.com/cntt-n/CNTT/pull/704
Methodology
Introduction of Golden VNFs &/or Prototype VNFs
Certification Strategy & Vehicle
Profiles Reference
Compliance, Verification, and Certification process
Entry & Exit Criteria
Frameworks: Functest, SampleVNF, Prototype Family/Class
Ch06: VNF Test Case Requirements: Fu Qiao, Yan Yang (confirmed), Chuyi Guo, Kanagaraj, Shiby (confirmed) - https://github.com/cntt-n/CNTT/pull/705
Assumptions: Automatable, Integrated with CICD tool chain
Developer Deliverables (artifacts)
Type of requirement: Bare metal, API, etc
Type of Interactions: Extended Topology, Complex (Akraino), Functional, HA, Fault, Interoperability
Table showing Performance Profiles
Table of VNF Class/Family & Characteristics of Each
Ch07: VNF TC Traceability to RM Requirements: Rajesh, Kanagaraj, Yan Yang (confirmed) - https://github.com/cntt-n/CNTT/pull/706
SME: Functest knowledge
Define RM/RA-1 Openstack requirements
Map Framework to Requirements
Dev
Deployment Validations (Cedric)
Ch08: E2E Framework Integration: Cedric, Kanagaraj, Sridhar Yan Yang (confirmed) - https://github.com/cntt-n/CNTT/pull/707
Identify Framework Needs, Goals, and Dependencies
Define Opensource Integration (OPNFV, OVP, Functest, CVC, others)
Provide Automation Toolchain (list, topology, flow)
Ch09: NFVI Tests Traceability to TC Requirements: Cedric, Deepanshu (confirmed)- https://github.com/cntt-n/CNTT/pull/708
Define RM/RA-1 Openstack requirements
Map Framework to Requirements
Ch10: VNF Tests Traceability to TC Requirements: Cedric, Liping Zhao , Shiby (confirmed) - https://github.com/cntt-n/CNTT/pull/709
Define RM/RA-1 Openstack requirements
Map Framework to Requirements
Ch11: Gap analysis & Development: Cedric, Kanagaraj, Shiby (confirmed) - https://github.com/cntt-n/CNTT/pull/710
Test Case Gaps (Analysis)
Automation Gaps
Open Stack release comparisons (Ocata, Pike, Queens, Stein, etc)
*******************************************************
Status | Milestones:
Work-stream
NFVI (Lead = Rajesh, Mike)
Issues: 6 open
PRs: 0 open
Assistance Needed
(In progress) 11/13 - Sridhar/Rajesh/Mark shifting ownership to RM/RA 1 team for extraction → Rajesh, work with Mark S., Sridhar → work in progress(In progress) Manifest validations vs. 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 changingTune the declarative files to meet RA requirements (re-deploy)Status | Tasks (Work in progress)
Receive Lab (date)(In progress) Translate RA requirements to Manifest Needs (See above for Assistance needed)Tune Manifest to match RA requirements (Target End State Lab - POD15) - status of POD 10, then date for POD 15Testing
VNF (Lead = Mike)
Issues: 6 open
PRs: 0 open
Assistance Needed
Empirical Validations - VNF Prototype Plan / Strategy
Trevor - details / dates for Network profiles and testing
Status | Tasks (Work in progress)
VNF Prototypes
(In Progress) Families Identified(In Progress) Test Requirements IdentifiedStrategy
Testing
Create Test Plan
Finalize Test Harness/Framework
Results Collection & Normalization
Dev (Lead = Cedric)
Notes:
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
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:
11/27 Meeting
Owner: All →Review/respond to GitHub issues by Dec 4, 2019Owner: 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 Nov 29, 2019Owner: Fu Qiao - identify how to incorporate, or start developing, PDF and SDF co11/20 Meeting
Owner: All →Review/respond to GitHub issues by Nov 27, 2019Owner: Mark (Victor) - Setup call to start Tracing RM Comp to RC Chapter sections by Nov 15, 201911/13 Meeting
Owner: All →Review/respond to GitHub issues by Nov 20, 2019Owner: Leads - Review / Add Milestones to the Minutes in the Appropriate 'Status | Milestones' section by Nov 15, 201911/06 Meeting
Owner: All →Review/respond to GitHub issues by Nov 13, 201910/30 Meeting
Owner: All →Review/respond to GitHub issues by Nov 6, 2019Owner: Rajesh - get current status from Srihdar on POD10 installs, and open a GitHub issue to track the deployment by Nov 1, 201910/23 Meeting
Owner: All →Review/respond to GitHub issues by Oct 29, 2019Owner: Leads - Assign / work action items by EOW Oct 25, 2019Owner: Rajesh - Meet w/ Trevor + others to discuss overall CNTT Lab Requirements (needs - e.g. POD10, 15, 17-18 (AirShip), 19-Test Tools, etc) by Oct 23, 2019Rajesh (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 Oct 23, 201910/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/2310/9 Meeting
Owner: All → Review/respond to GitHub issues by Oct 16, 2019Owner: Impacted Individuals (Test, Installer, Support) - needing access to POD15, request/receive access by Oct 16, 2019Owner: Mike - confirm with Cedric O. (Orange) if he will be the "lead" to centralize Implementation & Adoption of Test Hardness/Framework efforts on/by Oct 11, 2019Owner: Rajesh - confirm with Sridhar (Spirent) if he will be the "lead" to centralize s/w deployments on/by Oct 11, 2019