Expect each RI WS lead to arrange and follow the issues for their own WS. Will use this call as general time where WS share updates and discussion for necessary topics. RI WS Lead can also arrange their own separate calls to get things going.
Currently the issues are mainly about the documents. However things need to be improved and promoted in OPNFV and CNTT as well. Would expect each WS to promote the following action items
Labs related, Lead: Rajesh
current suitable labs for RI implementation within OPNFV
PDF and SDF updates to fit into CNTT RA's requirement (need collaboration with Infra WG within OPNFV)
Devs related, Lead: Cedric
Work with Installer project ( currently only Airship) for the first RI code development, make sure it meet the need from CNTT, and get alliance with RI requirement
work with testing projects (functest et al) for the compliance testing code development.
CNTT-RI (OPNFV) Project name change: Common Infrastructure Realization & Validation (CIRV)
Discussed the name change.
No concerns.
Questions arose re: the need for "Common Infra" being included in the name, which was logically chosen to denote the targeted focus of supporting the implementation of a "Common Infrastructure", building upon the CNTT RA delivery.
See above & below for POD10 and POD15 status, and action items below.
Provided overview of documentation on GitHub
Requested Lead + Contributors to review the GitHub repo and identify where they can support, or assist with content
Similar for issues, requesting all to review GitHub Issues and self-assign, or have the lead assign owners by EOW
Tasks (Work in progress)
Item 1
Item 2
Item 3
Actions
10/23 Meeting
Owner: All →Review/respond to GitHub issues by
Owner: Leads- Assign / work action items by EOW
Owner: Leads- Review / Add Milestones to the Minutes in the Appropriate 'Status | Milestones' section by
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
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: Rajesh- get current status from Srihdar on POD10 installs, and open a GitHub issue to track the deployment by
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
Owner: Cedric- open a GitHub issue for the setup of the Jenkins hosts for RI validation by
Owner: Fu Qiao- identify how to incorporate, or start developing, PDF and SDF consumables by
Weekly RI calls will be used to deliver the RI work Stream
Typical Agenda will consist of:
Issues/PRs discussion
Writing & Delivery of ChapterContent
Lab Setup and Delivery Status
RI Scope
RI Core Scope
Eco-system requirements (Labs, tooling, installers, releases and automation requirements)
NFVI, RI, and VNF Requirements.
Chapters:
Ch01:Introduction
Ch02:RI Requirements.
Ch03:NFVI + VNF Target State & Spec
Ch04:Lab Requirements
Ch05:Installers Requirements
RI Labs Scope
Procure initial target lab
Ensure all entry / exit criteria met
Assist with lab selection options (LAAS, Community, Self Service)
Release Alignment
Chapter:
Ch06:Lab Operations
RI Dev (upstream)
Covers installers, automation, etc.
Integration of installers and components.
Gap analysis with required actions for existing eco-system within LFN/OPNFV community projects
Assign Engineering resources into community projects to address gaps
Lead and manage Engineering resources pool
Chapters:
Ch07:Integration
Ch08:Gap analysis & Development
RI Delivery Status
RI Labs - Intel Lab
Target Labs have been identified (Intel Labs POD10 and POD15)
POD10 and POD15 were made available for access & installation on/by 10/9
By EOD 10/15, access requests were being processed and initial connectivity attempts (by Mike Fix) were successful
Additional details
POD10 (CNTT RI PoC)- will be used for initial install of OS via AirShip
Clarification needed as to why we can start on 15 in parallel or first → for PoC, installation validations, not anticipated to impact POD15 delivery cycle
Test | Validation | Framework: Rajesh/Sridhar, Mehment/Kyle,Cedric, Pierre (placeholder) → Lead Mike confirmed Cedric can lead this area
Installers: Sridhar (confirm if he will work with AirShip OPNFV install process), Luc, Mike/Kyle/Mark → Lead Sridhar confirmed will lead this area
Lab Support / Admin (SAs): Trevor - confirm SA role and responsibility (h/w) → Lead Trevor confirmed will lead, but caveat that this is limited support
To request VPN access please follow Wiki instructions and assign the ticket to Gustave Hellman