2019-10-23 - [CNTT - RI - 01] - Meeting Agenda and Minutes
Meeting Logistic:
Every Wed. at UTC 14:00-14:45
Attendee List:
@Qiao Fu (China Mobile)
@Trevor Cooper (Intel)
@Mark Shostak (AT&T)
@Michael Fix (AT&T)
@Rajamani, Rajesh (Spirent)
@Cédric Ollivier (Orange)
@Daniel Balsiger (Swisscom)
@Ashok Kumar (VoerEir)
@Pierre Lynch [Keysight] (Keysight)
@Lei Huang (China Mobile)
@Manik Sidana (VoerEir)
@victor gao (Huawei)
Meeting Agenda:
New name for OPNFV project Common Infrastructure Realization and Validation (CIRV)”
CNTT restructure result update. CNTT Workstream Signup
call for co-lead for
CNTT RI 1 Core (Current Lead: Fu Qiao)
CNTT RI 1 Labs (Current Lead: Rajesh Rajamani )
Call for contributors for all WS.
Working Items (Git issues) assignment
RI 1 Core Lead Fu Qiao: https://github.com/cntt-n/CNTT/labels/RI%201%20Core
RI 1 Labs Lead Rajesh Rajamani: https://github.com/cntt-n/CNTT/labels/RI%201%20Labs
RI 1 Dev Lead Cedric Ollivier, Rex Lee and Lei Huang: https://github.com/cntt-n/CNTT/labels/RI%201%20Dev
Work scheme for RI
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.
Walk-on Items (by @Michael Fix)
CNTT Jan 2020 Release: CNTT Snezka
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.
RI WS → move from RC minutes on 10/23
Documentation - https://github.com/cntt-n/CNTT/tree/master/doc/ref_impl/cntt-ri
Core
Issues - https://github.com/cntt-n/CNTT/issues?q=is%3Aopen+is%3Aissue+label%3A%22RI+1+Core%22
Status
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 Oct 25, 2019
Tasks (Work in progress)
Creation of PDF/SDF Templates
Hand-off to RC WS
Lab Setup
Issues - https://github.com/cntt-n/CNTT/issues?q=is%3Aopen+is%3Aissue+label%3A%22RI+1+Labs%22
Status
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 Oct 25, 2019
POD10 (CNTT RI PoC) - will be used for initial install of OS via AirShip
Status
Deployment? (Cedric) On-going. Rajesh, collect status from Sridhar. And, open a GitHub issue.
Jenkins setup? (Cedric) Jobs written. Waiting for slave from LF. Working with Jim to get traction. Support ticket opened. And, open GitHub issue.
POD15 (CNTT RI target state) - end state lab for RI 1.0
Status:
Target date to start base install? (Rajesh) Provide date for install.
What about the creation/use of PDF/SDF? (Fu Qiao) Take back to Core Team for how to incorporate/start these consumables.
Tasks (Work in progress)
PoC on Trial Lab
POD10Confirm availability (10/9)Confirm access (10/16)Perform AirShip installer (owner | date)Validate install status & env health (smoke test) (owner | date)Confirm & correct deployment issues - tune manifest (10/16-EOM Oct) (owner | date)Implementation on Target Lab
POD15Confirm availability (10/9)Confirm access (10/16)Perform AirShip installer (owner | date)Validate install status & env health (smoke test) (owner | date)Confirm & correct deployment issues - tune manifest (10/16-EOM Oct) (owner | date)
Dev
Issues - https://github.com/cntt-n/CNTT/issues?utf8=✓&q=is%3Aopen+is%3Aissue+label%3A"RI+1+Dev"+
Status
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 Oct 25, 2019
Tasks (Work in progress)
Item 1
Item 2
Item 3
Actions
10/23 Meeting
--------------------
AOB (Any other Business):
Useful Program links
CNTT Re-Org/Workstream (WS, aka "sign-up sheet") info: https://lf-networking.atlassian.net/wiki/display/LN/CNTT+Workstreams
CNTT Kekes (next release, WS tasks/deliveries): https://lf-networking.atlassian.net/wiki/display/LN/CNTT+Kekes
GitHub for Issue/PR tracking (initial "RI Dev" link for example): https://github.com/cntt-n/CNTT/labels/RI%201%20Dev
Cadence
Weekly RI calls will be used to deliver the RI work Stream
Typical Agenda will consist of:
Issues/PRs discussion
Writing & Delivery of Chapter Content
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
POD15 (CNTT RI target state) - Intel lab utilized: https://wiki.opnfv.org/display/pharos/Intel+POD15
Who needs access?
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
https://wiki.opnfv.org/display/pharos/Intel+Labs+VPN+Quickstart
https://help.github.com/en/articles/generating-a-new-gpg-key → GPG key generation
https://help.github.com/en/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent → SSH key generation
https://jira.opnfv.org/browse/INFRA-354 → Example Request
Meeting Minutes: