Minutes of Bottlenecks Discussion on July 13, 2017
* Date and Time
* Thursday at
0100-0200<http://www.timeanddate.com/worldclock/fixedtime.html?hour=13&min=0&sec=0>
UTC, July 13, 2017
* Thursday at 0900-1000 Beijing, July 13, 2017
* Wednesday at 1800-1900 PDT, July 13, 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
* Long duration POD for stress testing
* Report from last TSC meeting
* A concrete proposal is need that TSC could vote on
* Morgan has provide a proposal that include clear benefit and
plan of the long duration test
* Discussion in Testperf meeting suggests only consider mid-term
goal based on current situation
* Cross project stress is under consideration
* Running VSperf while StorPerf is excuted
* Bottlenecks act as load manager while monitoring/analyzing
* Intern Projects
* Have contacted the intern for CPU limit
* Might need voice communication/interview before official start
* Action on Gabriel to confirm and initiate the process
* Euphrates Planning updated
* https://wiki.opnfv.org/display/bottlenecks/Bottlenecks+Release+Plan
* Testing Framework Refactoring
* Monitoring module has been assigned high priority
* Decide to integrate Prometheus with Collectd exporter and maybe
some host monitoring tools
* Prakash feedback about the node monitoring process suggesting
included in Bottlenecks for stress testing monitoring
* Top logic for tuning test should be included in JIRA
* Initiate Container Testing
* This plan has been assigned low priority
* Prakash should feedback about Kola deployment/testing
* K8S, OpenRetriever, ...
* Initiate Tuning Testing
* WIKI page should be elaborated
* https://wiki.opnfv.org/pages/viewpage.action?pageId=12386549
* Ceph or CPU tuning is under consideration now
* Need investigation work
* Action item on Gabriel
2. Project Engagement
* More contributors are welcome to Bottlenecks
* Cooperation with other projects
* Integration with upstream
* Non-active committer contact
* Has sent out emails to confirm the involvement plan of committers for
E release
3. 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 @done
* 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
* Abandon docker-compose usage and adaptively testing sourcing OPNFV
credentials.
* 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
