Page tree
Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 280 Next »

This weekly meeting is for topics common across projects focused on testing (this is a good place to start if you want to get high-level status of the individual projects and learn about hot topics related to OPNFV Testing)

Test working group wiki page: https://wiki.opnfv.org/display/testing

  • Test projects should try to have a rep attend this meeting

  • New test related projects should be discussed in this forum to gain feedback from the OPNFV testing community
  • Agenda varies but typically is structured ...
    • 15 min report out / sharing by projects (high level status / plans)
    • 20 min discussion on test project collaboration topic/s
    • 20 min – share new test projects or other test topics

  • Usual time (this timeslot): Every Thursday 15:00-16:00 UTC
    Thursday GTM: https://global.gotomeeting.com/join/819733085
    Access Code: 819-733-085
    IRC channel: #opnfv-testperf @ Freenode

 


Useful links ...

Testing overview page with links to testing projects

Pharos project page


Meeting Chair and Minutes Schedule

This is a proposed schedule for the weeks ahead.  Please feel free to sign up and change as needed.

Calendar


Subscribe now

  1. EDIT THE CALENDAR

    Customise the different types of events you'd like to manage in this calendar.

    #legIndex/#totalLegs
  2. RESTRICT THE CALENDAR

    Optionally, restrict who can view or add events to the team calendar.

    #legIndex/#totalLegs
  3. SHARE WITH YOUR TEAM

    Grab the calendar's URL and email it to your team, or paste it on a page to embed the calendar.

    #legIndex/#totalLegs
  4. ADD AN EVENT

    The calendar is ready to go! Click any day on the calendar to add an event or use the Add event button.

    #legIndex/#totalLegs
  5. SUBSCRIBE

    Subscribe to calendars using your favourite calendar client.

    #legIndex/#totalLegs


Proposed Agenda Topics


To be planned

  • test plan (automatic documentation based on DB)
  • tooling catalog
  • testing coverage
  • monitoring and supervision
  • Results alignment for Bitergia dashboard: Result alignment for ELK post-processing
  • Documentation improvement for Euphrates
  • Wish list to infra group for Euphrates
  • Traffic generator
  • Sync Bitergia

 

Agenda -  - APAC Time: UTC 8:00-9:00 / PST  24:00-1:00 / Beijing 16:00-17:00 / IST  13:30-14:30

  • Action points follow-up
    1. gabriel summarize the bitergia activities and invite them in the next week meeting
    2. gabriel reach out to David about XCI-baremetal and CI chain requirements
    3. Prakash will help to check storperf's reporting
    4. Jack send email to David to figure out a way to add time stamp
  • Topics
    1. Landing page for F release
      1. Testing results graphing
      2. Monitoring results for long duration test
      3. Unified entrance of Testperf resources
    2. Plugfest Preparation
      1. Missing topics
      2. https://etherpad.opnfv.org/p/testing_group_plugfest_4
  • Minutes: http://ircbot.wl.linuxfoundation.org/meetings/opnfv-testperf/2017/opnfv-testperf.2017-11-08-08.02.html
  • Actions
    1. gabriel invite biterg in the next week meeting
    2. Sridhar cooperate with Jack for VSPERF reporting
    3. gabriel add topic for landing page, F release priorities

 

Agenda -  - Usual Time: 15:00-16:00 UTC / PST 7:00-8:00 / Beijing 23:00-24:00 / IST 20:30-21:30

 

Agenda - 

 

Agenda - 

Agenda -  (APAC slot !!!!!!!!!!!!!!!!!!!!!!!!!=

  • Action points follow-up
  • Testing group organization
  • Minutes:

Agenda - 

 

Agenda - 

Agenda - 

 

Agenda - 

Agenda - 

 

Agenda - 

 

Agenda - 

Agenda - 

 

Agenda - 

 

Agenda - 

 

Agenda - 

  • Action point follow-up
  • Sync with Bitergia
  • Docker container management (versioning and build workflow)
    • problem statement: 

      Every artifact (we can start with docker container images) produced by OPNFV must be traceable to the exact source code version used to create that artifact. The current workflow and versioning scheme does not seem to address this properly. As container images get to be used by more and more external parties, it will be extremely difficult to support them properly without proper versioning and traceability.

    • related ref:
    • identify level of interest and list of required people/projects to help address the problem 
  • Testing plan for long duration POD
  • minutes

Agenda - 

  • Action point follow-up
  • Discussion on stress/long-term testing on OSA or OPNFV installers
  • minutes

Agenda -  Adhoc Meeting sync Bitergia !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Agenda -  APAC SLOT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Agenda - 

 

Agenda - 

 

Agenda -  

 

Agenda -  

Agenda -  

Agenda -  

 

Agenda -   Quorum not reached => meeting canceled

 

Agenda -  

 

Agenda -  

Agenda -  

Agenda -  

Agenda -  

Agenda -  

Agenda -   (APAC slot!!!!!!!!!!!!!!!)

Agenda -   

 

 

Agenda -   

 

Agenda -   

  • Action point follow-up
  • Status on Danube priorities: what will be achievable  what not 
  • Minutes:

Agenda -   ********** APAC slot  ********************

Agenda -   CANCEL QUORUM NOT REACHED

Agenda -  

Agenda -  

Agenda -  (APAC SLOT!!!!!!!!!!!!!!!!!!!!!!!!!!)

  • Action point follow-up
  • Bottlenecks & Yardstick update:

      

 

Agenda - 

(55 min)

Testing working group archive 2016

Archive

  • No labels