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

Compare with Current View Page History

« Previous Version 15 Current »

Meeting Logistics: 

Attendee List:

  1. Michael Fix (AT&T)
  2. Mark Shostak (AT&T)
  3. Shiby Parayil (iconectiv)
  4. Mark Beierl (VMware)
  5. Deepanshu Bhatia (VoerEir)
  6. Manik Sidana (VoerEir)
  7. Qiao Fu (China Mobile)
  8. Rajamani Rajesh  (Spirent)
  9. Daniel Balsiger (Swisscom)
  10. Georg Kunz (Ericsson)
  11. Jiaqiang Zhang (China Mobile)
  12. Jim Baker (LFN)
  13. Lei Huang (China Mobile)
  14. Liang Chen (China Mobile)

Goals of Meeting:

  1. Remaining Meeting Coverage
  2. Prague Deliverables (owners)
  3. Status from Lead & Authors 

Agenda:

  • Remaining Meeting Coverage
    DatePurposeHostWho is hereComment
    12/11RI RC CombinedFu Qiao, MikeHosts areRoutine, business as usual
    12/18RI RC CombinedFu Qiao, MikeHosts areMike off 12/18-1/1, return 1/2, but will host
    12/25Move call to 12/23Fu QiaoFu Qiao and China MobileRajesh out 12/25-1/1, Mike off per above, Shiby OoO 12/23-12/30
    1/1Move call to 12/30 Fu QiaoFu QiaoSee above for Rajesh and Mike
    1/8RI RC CombinedFu Qiao, Mikehosts areRoutine, business as usual
  • Prague Deliverables 
    • RI
      • Content for:
        • Lab Requirements (Rajesh, +topology document, send Mark B a link to Pharos)
        • Installer Requirement (Chen Liang)
        • NFVI required State (Manik, Sridhar, +Manifest validations)
        • Cookbook (Mark B., important)
      • Implementation side:
        • PoD state and labs availabilities (Rajesh, +issues/ReleaseNotes)
        • Initial NFVI installation using Airship (even if doesn’t comply to CNTT for now) (Sridhar, +Rajesh)
    • RC
      • Content for:
        • Framework requirement (+Manik will reach out to Cedric)
        • Certification process drafted (+Shiby, + Kanag)
        • Automation / Compliance / Tool chain process and status (+Cedric, +Mark B. reach out to Cedric)

  • Status 


=========================================================

=========================================================

Additional Notes / Links:



  • RC Work stream
    • RC NFVI: Rajesh, Mike
      • Documentation moving along?  Ch's 1,2,3,4
      • Issues
      • PRs
      • Status | Tasks (Work in progress)
        • Receive Lab (date)
        • (In progress) Translate RA requirements to Manifest Needs (See above for Assistance needed)
        • Tune Manifest to match RA requirements (Target End State Lab - POD15) - status of POD 10, then date for POD 15
        • Testing
          1. Prepare automation harness - connectivity, validation (POD10)? – Cedric?
            1. e.g. functest-smoke-cntt was just created. neutron-tempest-plugin-api is already conformed with the current API section.
          2. Create Test Plan
          3. Finalize Test Harness/Framework
          4. Perform Manifest Validations
          5. Results Collection & Normalization
    • RC VNF:  Mike
      • Documentation moving along?  Ch's 5,6,7
      • Issues
      • PRs
      • Status | Tasks (Work in progress)
        1. VNF Prototypes
          • (In Progress) Families Identified
          • (In Progress) Test Requirements Identified

          • Strategy

            1. Use POD10 for Network Intensive. 

            2. Measure stats related to the NFVi datapath capacity.

            3. Goal will be to demonstrate full automation of the environment (continuous deployment) with test cases with some useful test results (continuous testing).
            4. Status? Then look at adding compute and storage intensive VNFs and identify test cases that map back to CNTT specified capabilities.(Luc, Sridhar, Al, Trevor - creating more detailed plan?).
        2. Testing
          1. Create Test Plan
          2. Finalize Test Harness/Framework
          3. Results Collection & Normalization
    • RC Dev: Cedric
      • Documentation moving along?  Ch's 8,9,10,11
      • Issues
      • PRs
      • Status | Tasks (Work in progress)
        • Jenkins setup
        • VNF prototype
          1.  Development
          2. Connectivity to POD15

*****************************

Table of Contents Owners:

  • RC: status | issues
    • NFVI
      • Ch01: Introduction: Rajesh, Kanagaraj,Manik (confirmed) - https://github.com/cntt-n/CNTT/pull/658
        • (Refer to PRhttps://github.com/cntt-n/CNTT/pull/658) 
        • Synopsis
        • Introduction
        • Principles & Guidelines
        • Goals & Objectives
        • Best Practices
        • Verification methodologies
        • Assumptions & Dependencies
        • Results Collation & Presentation
        • Measurements, Monitoring
        • Governance
        • Resources & References

      • Ch02: NFVI E2E C&V Framework Requirements: Cedric,Manik (confirmed) - https://github.com/cntt-n/CNTT/pull/701

        • Methodology
        • Certification Strategy & Vehicle
        • Profiles Reference
        • Compliance, Verification, and Certification
        • Entry & Exit Criteria
        • Frameworks: e.g. Functest (StorePerf, SampleVNF, others?)

      • Ch03: NFVI Test Case Requirements: Georg,Toshi (question)https://github.com/cntt-n/CNTT/pull/702

        • Assumptions: Automatable, Integrated with CICD tool chain
        • Type of requirement: Bare metal, API, etc
        • Table showing Profile Catalog
        • Identify SW Reference
        • Identify HW Reference
        • Options Available / Configured
        • Extensions Available / Configured

      • Ch04: NFVI TC Traceability to RA Requirements: Rajesh, Dan, Ashok,Deepanshu (confirmed)-  https://github.com/cntt-n/CNTT/pull/703

        • SME:Functest knowledge
        • Define RM/RA-1 Openstack requirements
        • Map Framework to Requirements
    • VNF
      • VNF Prototype Plan - details, dates (Trevor)

      • Ch05: VNF E2E C&V Framework Requirements:  Kanagaraj, Cedric,Shiby (confirmed) -  https://github.com/cntt-n/CNTT/pull/704

        • Methodology
        • Introduction of Golden VNFs &/or Prototype VNFs
        • Certification Strategy & Vehicle
        • Profiles Reference
        • Compliance, Verification, and Certification process
        • Entry & Exit Criteria
        • Frameworks: Functest, SampleVNF, Prototype Family/Class

      • Ch06: VNF Test Case Requirements: Fu Qiao,Yan Yang (confirmed), Chuyi Guo, Kanagaraj,Shiby (confirmed) - https://github.com/cntt-n/CNTT/pull/705

        • Assumptions: Automatable, Integrated with CICD tool chain
        • Developer Deliverables (artifacts)
        • Type of requirement: Bare metal, API, etc
        • Type of Interactions: Extended Topology, Complex (Akraino), Functional, HA, Fault, Interoperability
        • Table showing Performance Profiles
        • Table of VNF Class/Family & Characteristics of Each

      • Ch07: VNF TC Traceability to RM Requirements: Rajesh, Kanagaraj,Yan Yang (confirmed) - https://github.com/cntt-n/CNTT/pull/706

        • SME:Functest knowledge
        • Define RM/RA-1 Openstack requirements
        • Map Framework to Requirements
    • Dev
      • Deployment Validations (Cedric)
      • Ch08: E2E Framework Integration: Cedric, Kanagaraj,Sridhar (question) Yan Yang (confirmed) - https://github.com/cntt-n/CNTT/pull/707
        • Identify Framework Needs, Goals, and Dependencies
        • Define Opensource Integration (OPNFV, OVP, Functest, CVC, others)
        • Provide Automation Toolchain (list, topology, flow)

      • Ch09: NFVI Tests Traceability to TC Requirements: Cedric,Deepanshu (confirmed)- https://github.com/cntt-n/CNTT/pull/708

        • Define RM/RA-1 Openstack requirements
        • Map Framework to Requirements
      • Ch10: VNF Tests Traceability to TC Requirements: Cedric,Liping Zhao (question),Shiby (confirmed) - https://github.com/cntt-n/CNTT/pull/709
        • Define RM/RA-1 Openstack requirements
        • Map Framework to Requirements
      • Ch11: Gap analysis & Development: Cedric, Kanagaraj,Shiby (confirmed) - https://github.com/cntt-n/CNTT/pull/710
        • Test Case Gaps (Analysis)
        • Automation Gaps
        • Open Stack release comparisons (Ocata, Pike, Queens, Stein, etc)
  • No labels