Versions Compared

Version Old Version 12 New Version Current
Changes made by

Deepanshu Bhatia

Michael Fix

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Please add your name in here:

  1. Michael Fix
  2. Qiao Fu (China Mobile)
  3. Mark Shostak (AT&T)
  4. Ashok Kumar (VoerEir)
  5. Rajamani, Rajesh (Spirent)
  6. Shiby Parayil (iconectiv)
  7. Al Morton  (AT&T)
  8. Pierre Lynch [Keysight] (Keysight)
  9. Georg Kunz (Ericsson)
  10. Deepanshu Bhatia (VoerEir)
  11. Jim Baker (LFN)
  12. Trevor Cooper (Intel)
  13. Lincoln Lavoie (UNH-IOL)
  14. Liang Chen (China Mobile)
  15. Jiaqiang Zhang (China Mobile)
  16. Kanag (Huawei)
  17. Lei Huang (China Mobile)
  18. Sridhar Rao (Spirent)
  19. Yan Yang (China Mobile)
  20. Hongli Zhang (China Mobile)
  21. Jiaqiang Zhang (China Mobile)

Goals of the 11/13 Meeting

...

...

  • General
  • Work-stream
    1. NFVI (Lead = Rajesh, Mike)
      1. Issues:  6 open
      2. PRs: 1 open
        1. 11/13 - 2/3 approved, awaiting 3rd reviewer, requested additional reviews
      3. Assistance Needed
        •  (In progress)  11/13 - Sridhar/Rajesh/Mark shifting ownership to RM/RA 1 requirements team for extraction → Rajesh, work with Mark S., Sridhar  → work in progress
        •  (In progress) Manifest validations vs. RA Req → discussed in the RI work stream call, work in progress as AirShip manifests were followed for installs, but confirmation needed to ensure RA requirements have been met; offline discussion happening in email to confirm if manifest require changing
        •  Tune the declarative files to meet RA requirements (re-deploy)
      4. Status | Tasks (Work in progress)
        •  Receive Lab (date)
        •  (In progress) Translate RA requirements to Manifest Needs (dateSee 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
    2. VNF (Lead = Mike)
      1. Issues: 6 open
      2. PRs: 1 open (same as NFVI)
      3. Assistance Needed
        1. Empirical Validations - VNF Prototype Plan / Strategy
        2. Trevor - details / dates for Network profiles and testing
      4. 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
    3. Dev (Lead = Cedric)
      1. Issues: 2 unassigned, 15 total open
        1. 11/13 - 2 unassigned have been assigned to Cedric
      2. PRs: 1 open (same as NFVI, and VNF)
      3. Assistance Needed
        1. Deployment Validations and continuous deployment / integration 
      4. Status | Tasks (Work in progress)
        1. Jenkins setup
        2. VNF prototype
          1.  Development
          2. Connectivity to POD15

...

  • 11/06 Meeting
    •  Owner: All →Review/respond to GitHub issues by 13      
    •  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 01  
    •  Owner: Mark (Victor) - Setup call to start Tracing RM Comp to RC Chapter sections by 01  
    •  Owner: Fu Qiao - identify how to incorporate, or start developing, PDF and SDF consumables by 01  
    •  Owner: Leads - Review / Add Milestones to the Minutes in the Appropriate 'Status | Milestones' section by 08  
  • 11/06 Meeting
    •  Owner: All →Review/respond to GitHub issues by   
  • 10/30 Meeting
    •  Owner: All →Review/respond to GitHub issues by  
    •  Owner: Rajesh - get current status from Srihdar on POD10 installs, and open a GitHub issue to track the deployment by  
  • 10/23 Meeting
    •  Owner: All →Review/respond to GitHub issues by 
    •  Owner:  Leads - Assign / work action items by EOW  
    •  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: Cedric - open a GitHub issue for the setup of the Jenkins hosts for RI validation by  
  • 10/16 Meeting:  Yielded time to RI Kickoff discussions.  Refer to RI meeting notes for 10/16 for details
    •  Setup recurring call for RC series starting 10/23
  • 10/9 Meeting
    •  Owner: All → Review/respond to GitHub issues by  
    •  Owner: Impacted Individuals (Test, Installer, Support) - needing access to POD15, request/receive access by    
    •  Owner: Mike - confirm with Cedric O. (Orange) if he will be the "lead" to centralize Implementation & Adoption of Test Hardness/Framework efforts on/by  
    •  Owner: Rajesh - confirm with Sridhar (Spirent) if he will be the "lead" to centralize s/w deployments on/by 

...