Hi All,
Please find the minutes of Thursday's bottlenecks meeting below and welcome to
our next meeting!
Thanks,
Yang
________________________________
Minutes of Bottlenecks Discussion on August 11, 2016
* Date and Time
* Thursday at
0100-0200<http://www.timeanddate.com/worldclock/fixedtime.html?hour=13&min=0&sec=0>
UTC, August 11, 2016
* Thursday at 0900-1000 Beijing, August 11, 2016
* Wednesday at 1800-1900 PDT, August 10, 2016
* Minutes
* Yang Yu
* Participants (8 peoples):
* Yang Yu
* Qi Liang
* Manuel Rebellon
* Lawrence Lamers
* 4 Web users
Agenda:
* Bottlenecks Colorado Discuss Yang
* Colorado Milestones
* Bottlenecks Colorado Testing Framework (Rubbos example)
* Proposals in Bottlenecks (Draft) Yang
* Goals and Scope (Draft)
* Proposals (Draft)
Discussion & Action Item
The meeting materials could be downloaded
HERE<https://wiki.opnfv.org/display/bottlenecks/Bottlenecks?preview=%2F2926187%2F6828238%2FProposals+in+Bottlenecks.pdf>.
More information about our meeting could be found at Bottlenecks
WIKI<https://wiki.opnfv.org/pages/viewpage.action?pageId=6828202>.
1. Bottlenecks Colorado Discuss
* Hongbo has another meeting to attend. So yang is delegated to organize
the discussion
* Yang reports the discussion from the last Colorado release weekly meeting
* There will be a window period for stable branches and documents which
lasts one week from August 15-22
* PTLs of each projects should determine their Milestone time that
within this window period including Bottlenecks
* MS9:Stable branch created
* Projects are branched from main
* Commits are limited to critical issues
* Commits must be cherry-picked
* MS10:Documentation completed
* Updated
* Reviewed
* Verified
* Committed to repo
* Yang briefly introduce the new Bottlenecks Colorado framework
* Bottleneck uses puppet to refactor the testing framework
* Jumper server is the CI entrance for the Bottlenecks and will
download all the codes
* Environment and resources are configured and provided in the Jumper
server
* By taking Rubbos as an example, Yang introduce that the softwares
that are needed in each nodes are downloaded and configured, and how puppet
master/slave distributes. The Rubbos controller triggers the testing and the
results will be sent to DB.
2. Proposals in Bottlenecks (Draft)
* Yang introduce the goals and scope of the proposals
* Goals of the proposals in Bottlenecks
* Enhance interaction with other project
* Add value to OPNFV Certification
* Feedback development suggestions to upstream through OPNFV feature
projects
* Improve the performance of OPNFV reference platform
* Scope of the proposals in Bottlenecks
* OPNFV Testing projects
* OPNFV Feature projects
* Modeling, Testing and Data analysis
* Parameters choosing and Algorithms
* Yang gives an introduction about the development proposal in Bottlenecks
* Yang suggests that Bottlenecks communicates with testing and feature
projects about the test cases, uses yardstick for testing and collects data
from DB. Then the results will be analyzed and the bottlenecks will be
classified into 5 categories. In addition, the bottlenecks analysis results
will be feedback to each feature projects to output development suggestions to
upstream projects.
* Manuel asks the connection between the feature/scenario from the
feature projects and Bottlenecks project, and does Bottlenecks also act over
those projects.
* Yang explained that the proposal of Bottlenecks project classified
the results into 5 categories and outputs the bottlenecks for each category.
For each feature test case, the bottlenecks will be searching within the 5
categories
* Manuel asks about the interconnection between the feature projects and
Bottlenecks
* Yang explained that the proposal of Bottlenecks expects that the
feature projects should also participant the discussion for the test cases,
target parameters, etc.
* Yang also suggest to take the existing testing work in the
community as advantages for Bottlenecks project.
* Yang volunteers to help organize the bottlenecks meeting and will discuss
with Hongbo about the details of the proposals
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
