Minutes of Bottlenecks Discussion on July 6, 2017
* Date and Time
* Thursday at
0100-0200<http://www.timeanddate.com/worldclock/fixedtime.html?hour=13&min=0&sec=0>
UTC, July 6, 2017
* Thursday at 0900-1000 Beijing, July 6, 2017
* Wednesday at 1800-1900 PDT, July 6, 2017
* Minutes
* Yang Yu
* Participants (2 peoples):
* Ace Lee
Agenda:
* Stress Testing Discuss & Release Discuss
* Action Items Review
Discussion & Action Item
1. Stress Testing Discuss & Release Discuss
* Stress test cases are collected from email
* from Yardstick, StorPerf, VSperf and Bottlenecks
* Cross project stress is under consideration
* Running VSperf while StorPerf is excuted
* Bottlenecks act as load manager while monitoring/analyzing
* https://lists.opnfv.org/pipermail/test-wg/2017-June/000304.html
2. Euphrates Planning updated
* https://wiki.opnfv.org/display/bottlenecks/Bottlenecks+Release+Plan
* Stress Testing
* Implements test cases discussed in Danube
* An intern project is proposed
* Amit has been recruited for CPU baseline stress test
* Another project is need to implemented other tasks
* Will communicate with tongji student this Friday for the stress
internship
* Long duration POD
* TSC meeting is cancelled this week. Discussion regarding the
request will be started next week.
* Work with VSPERF/Storperf
* Testing Framework Refactoring
* Monitoring module has been assigned high priority
* Compare Prometheus and Collectd this week and make up the plan next
week
* Top logic for tuning test is under investigation
* Initiate Container Testing
* This plan has been assigned low priority
* Prakash will feed back about Kola after the holiday
* K8S, OpenRetriever, ...
* Initiate Tuning Testing
* WIKI page has been created
* https://wiki.opnfv.org/pages/viewpage.action?pageId=12386549
* Ceph or CPU tuning is under consideration
3. Project Engagement
* More contributors are welcome to Bottlenecks
* Interns are recruited through Intern-projects
* Cooperation with other projects
* Integration with upstream
* Non-active committer contact
* To determine they are willing to contribute or not
Action Item Review
* https://wiki.opnfv.org/display/bottlenecks/Release+Plan
Euphrates:
* How to use Quota - Prakash
* Reliability project in Openstack - Prakash
* WIKI page restructured for closely updating project details @done
(17-05-11 09:20)
* Testing framework
* General env pre commond for all test cases? Maybe different test
cases call diffrent functions?
* Requirements investigation of DPDK and SR-IOV in Bottlenecks
* Which categories we should put them in?
* What the structure of their report?
* Is there any existing implementation we could use?
* Do we need to separate the env pre and test executing operations?
* Test report
* (Automatically) Test result report to MongoDB
* Landing page (on-going, in plan)
* Stress testing
* Implementing the rest stress test cases discussed during Danube
* Collect stress test case
* Request/maintaining long duration pod
* Work with VSPERF & StorPerf
* Initiate Tuning Test
* Ceph Tuning ( installer deployment tuning?)
* Comparison results
* Initiate Container Testing
* K8S, OpenRetriever, unicore
* Work with installers team for Kola deployment testing
* Prakash to check OpenStack for Kola testing
* Testing Framework Refactoring
* Overall framework design
* Determine requirements & Initiate the overall framework design
* Unified entrance/top logic for system limit/tuning test
* Initiate top logic design & investigation
* Separated monitoring module
* Work with StorPerf & VSPERF adding monitoring function
* Monitoring using yardstick? Barometer?
* Stand-alone & offline
* More Contributors in Bottlenecks
* Intern projects
* Integrate upstream
* More contributors in project
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
