2. The Return of QTIP
From Brahmaputra to Danube
Yujun Zhang, ZTE Corporation
Julien Zhang, ZTE Corporation

3. A Tweet from OpenStack Telemetry PTL

4. Contents
Story of a community project - QTIP
• Start
• Pause
• Resume
• Continuing

5. Brahmaputra Colorado Danube
GAP PERIODApproved
Arno

6. 2015-1-27

7. QTIP - Platform Performance Benchmarking
targets on establishment
General characterization of an OPNFV platform.
General performance common to the platform itself
Or applicable to multiple OPNFV use cases.
Provide the capability to quantify a platform's performance behavior
Standardized, rigorous, open way, well-documented methodology

8. Inactive for 3 months

9. Story of first commit
Interested in using community tool for testing
Issues encountered
Submit patched to resolve
Wait a long time to review

10. First contact from original core
“Are you interested to take over QTIP project?”

11. Rare experience in OPNFV

12. Take it over
Recommend a new PTL and continue

13. PTL nomination

14. The long voting...
5 votes out of 10 committers required
Many of them are no longer reachable
…
It lasts more than one month in the end

15. QTIP future discussed with original cores

16. Finally approved

17. Improved committer removal policy
At times it may be that a committer is not able to continue his work for
a project and the project leader is not able to get in contact with the
committer any more, e.g. to get his consent to retire from the
committer role.
In this case the PTL may notify the TSC that the inactive committer is
being removed from the project. The PTL then must demonstrate: ...

18. Reactivate the core team

19. Scope collisions
Overlap in test cases although serving different purpose

20. Reshape the project scope
Stick on the original purpose - Platform Performance Benchmarking
Focus more on performance indicator rather than testing itself
A broader vision to build Benchmarking as a Service for community

21. Happy ending of the transition
Successfully released in Danube
Top 3 active measured by commits
2 internship projects
Participated in inter-op testing on plugfest

22. Lessons learned
Communicate with original team
Understand the original purpose
Pivot in case the world changes
Refactor bravely when necessary

23. Brahmaputra Colorado Danube Euphrates
PLUGFEST
GAP PERIODApproved
Arno

24. Questions?
https://wiki.opnfv.org/display/qtip