You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Meeting Logistic: 

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

 https://zoom.us/j/694881078

Attendee List:

Qiao Fu (China Mobile)

Trevor Cooper (Intel)

Mark Shostak (AT&T)

MICHAEL FIX (AT&T)

Rajamani Rajesh (Spirent)

Cedric Ollivier (Orange)

Daniel Balsiger (Swisscom)

Ashok Kumar (VoerEir)

Pierre Lynch (Keysight)

Lei Huang (China Mobile)

Manik Sidana (VoerEir)

Meeting Agenda:

  1. New name for OPNFV project Common Infrastructure Realization and Validation (CIRV)”

2. 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.

2. 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

3. 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

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. 


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