2019-10-16 - [CNTT - RI - 01] - Meeting Agenda and Minutes

Meeting Logistic: 

Every Wed. at UTC 12:00-13:00

 https://zoom.us/j/694881078

Attendee List:

Meeting Agenda:

1. RI project/RI WS basic introduction, meeting plan, document plan, code plan
2. project/WS working items 

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

        • https://wiki.opnfv.org/display/pharos/Intel+POD10

      • 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/INF/Infra+Lab+Support

          • 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:

1. RI and RC calls are sharing the 1h for now, the situation will change probably for next week. Will send out email notice and calendar invite

2. This call is for the combined team for RI WS and OPNFV new project

3. Will use OPNFV wiki as main page to keep minutes, and will reference with each other from the LFN wiki

4. Document for RI will go to CNTT Github and will follow CNTT release cycle. Code for RI will probably go into installer projects and testing projects within OPNFV, and will follow OPNFV release cycle

5. OPNFV project is suggested to change a new name. After the name is determined, Jim Baker will help create official project page

6. Jim Baker asked about the weekly report at OPNFV TSC. Fu Qiao suggested it should be a report for the CNTT in general, not the responsibility for a single project

7. Mike lead the group to go through the github issues for RI and RC WS. Will proceed the WS work using github. Mike will update the useful link in the minutes page

8. Next meeting will be for the working items, and for specific people who will drive the items.