Meeting Logistic: 

Every Wed. at UTC 14:00-14:45

 https://zoom.us/j/694881078

Attendee List:

Qiao Fu (China Mobile)

Mark Shostak (AT&T)

Shiby Parayil (iconectiv)

Michael Fix (AT&T)

Lincoln Lavoie  (UNH-IOL)

Manik Sidana  (VoerEir)

Daniel Balsiger (Swisscom)

Georg Kunz (Ericsson)

Jiaqiang Zhang (China Mobile)

Lei Huang (China Mobile)

Rajamani Rajesh (Spirent)

Pierre Lynch (Keysight)

Liang Chen (China Mobile)

Meeting Agenda:

  1. New name for OPNFV project Common Infrastructure Realization and Validation (CIRV)”
  2. CNTT restructure result update.  CNTT Workstream Signup
    1. call for co-lead for
    2. CNTT RI 1 Core (Current Lead: Fu Qiao)
    3. CNTT RI 1 Labs (Current Lead: Rajesh Rajamani )
    4. Call for contributors for all WS.
  3. Working Items (Git issues) assignment
    1. RI 1 Core   Lead Fu Qiao:  https://github.com/cntt-n/CNTT/labels/RI%201%20Core
    2. RI 1 Labs   Lead Rajesh Rajamani:  https://github.com/cntt-n/CNTT/labels/RI%201%20Labs
    3. RI 1 Dev  Lead Cedric Ollivier, Rex Lee and Lei Huang:  https://github.com/cntt-n/CNTT/labels/RI%201%20Dev
  4. Work scheme for RI
    1. 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.
    2. 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
    3. Labs related, Lead: Rajesh
      1. current suitable labs for RI implementation within OPNFV
      2. PDF and SDF updates to fit into CNTT RA's requirement (need collaboration with Infra WG within OPNFV)
    4. Devs related, Lead: Cedric
      1. 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
      2. work with testing projects (functest et al) for the compliance testing code development. 
  5. Walk-on Items (by Michael Fix (AT&T))
    1. CNTT Jan 2020 Release:  CNTT Snezka
    2. 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.
    3. RI WS → move from RC minutes on 10/23
      1. Documentation - https://github.com/cntt-n/CNTT/tree/master/doc/ref_impl/cntt-ri
      2. Core
        1. Issues - https://github.com/cntt-n/CNTT/issues?q=is%3Aopen+is%3Aissue+label%3A%22RI+1+Core%22
        2. Status
          1. Provided overview of documentation on GitHub
          2. Requested Lead + Contributors to review the GitHub repo and identify where they can support, or assist with content
          3. Similar for issues, requesting all to review GitHub Issues and self-assign, or have the lead assign owners by EOW  
        3. Tasks (Work in progress)
          1. Creation of PDF/SDF Templates
          2. Hand-off to RC WS
      3. Lab Setup
        1. Issues - https://github.com/cntt-n/CNTT/issues?q=is%3Aopen+is%3Aissue+label%3A%22RI+1+Labs%22
        2. Status
          1. Provided overview of documentation on GitHub
          2. Requested Lead + Contributors to review the GitHub repo and identify where they can support, or assist with content
          3. Similar for issues, requesting all to review GitHub Issues and self-assign, or have the lead assign owners by EOW 
          4. POD10 (CNTT RI PoC) - will be used for initial install of OS via AirShip
            • https://wiki.opnfv.org/display/pharos/Intel+POD10
            • 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.
          5. POD15 (CNTT RI target state) - end state lab for RI 1.0
            • https://wiki.opnfv.org/display/pharos/Intel+POD15
            • 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.
        3. Tasks (Work in progress)
          1. PoC on Trial Lab
            • POD10
              • Confirm 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)
          2. Implementation on Target Lab
            • POD15
              • Confirm 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)
      4. Dev 
        1. Issues - https://github.com/cntt-n/CNTT/issues?utf8=✓&q=is%3Aopen+is%3Aissue+label%3A"RI+1+Dev"+ 
        2. Status
          1. See above & below for POD10 and POD15 status, and action items below.
          2. Provided overview of documentation on GitHub
          3. Requested Lead + Contributors to review the GitHub repo and identify where they can support, or assist with content
          4. Similar for issues, requesting all to review GitHub Issues and self-assign, or have the lead assign owners by EOW 
        3. Tasks (Work in progress)
          1. Item 1
          2. Item 2
          3. 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  

--------------------

AOB (Any other Business):

  • 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


Meeting Minutes:



  • No labels