14:02:17 <r-mibu> #startmeeting doctor
14:02:17 <collabot`> Meeting started Tue Nov 22 14:02:17 2016 UTC.  The chair is r-mibu. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:17 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:02:17 <collabot`> The meeting name has been set to 'doctor'
14:02:27 <r-mibu> #topic roll call
14:02:29 <cgoncalves> #info Carlos Goncalves
14:02:35 <yujunz> #info Yujun Zhang
14:02:59 <tojuvone> #info Tomi Juvonen
14:03:07 <GeraldK> #info Gerald
14:03:19 <yujunz> Yes, loud and clear
14:03:20 <r-mibu> #info Ryota Mibu
14:03:27 <psous> #info Pedro Sousa
14:06:04 <yujunz> #link https://gerrit.opnfv.org/gerrit/#/c/24143/
14:06:42 <yujunz> #info Host specific VMs list
14:09:31 <r-mibu> #topic Q4 hackfest
14:10:05 <r-mibu> #link https://etherpad.opnfv.org/p/doctor_meetings
14:10:11 <r-mibu> from line 40
14:11:29 <yujunz> #info yujunz and wenjuan will not attend hackfest, but Julien might attend
14:13:34 <yujunz> Aaron Smith according to the purple color
14:16:47 <r-mibu> #topic Inspector design guideline
14:16:49 <ljlamers> #info Larry Lamers
14:16:57 <tommyL> #info Tommy Lindgren
14:17:03 <r-mibu> yujunz, seems like bit different color
14:17:15 <yujunz> He just typed in attendee
14:17:44 <yujunz> #link http://artifacts.opnfv.org/doctor/review/24143/design/index.html#document-inspector-design-guideline
14:18:02 <cgoncalves> #link https://gerrit.opnfv.org/gerrit/#/c/24143/
14:19:15 <yujunz> #link https://jira.opnfv.org/browse/DOCTOR-76
14:19:32 <yujunz> #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2016-October/013036.html
14:27:12 <yujunz> #info r-mibu suspects that notifier may have taken most time of the whole doctor test
14:29:58 <yujunz> #info r-mibu suggests detail investigation may need to be done to see if there is alternative solution
14:31:55 <yujunz> #info r-mibu suggests that some improvement could be done in the message queue
14:35:44 <yujunz> #info yujunz suggests to detail the specific problem description in each bullet of guideline
14:37:01 <r-mibu> #topic test code refactoring
14:37:44 <dwj> # link https://github.com/openzero-zte/doctor_test_refactor
14:38:01 <r-mibu> #link https://lists.linux-foundation.org/pipermail/opnfv-tech-discuss/2016-November/013683.html
14:46:17 <GeraldK> #info Gerald thinks the refactoring is going into the right direction, however, due to the other high prio tasks, suggests to delay this activity for a later release and for now focus on smaller changes to the existing scripts
14:46:32 <yujunz> I put it on etherpad
14:47:12 <GeraldK> #info Carlos will share his thoughts via email (due to an issue his reply was not sent on the ML)
14:47:32 <GeraldK> #info     Carlos: Definitely Python would be better to profile performance rather than Bash as we have at the moment.      I  propose that we work on this in parallel with the tests Bash code refactoring activity that is ongoing. Later on, still at Danube development time frame, we can make a decision of which one to use by default – although for that it would be required adding more verify jobs (2 tests branches (Bash and
14:48:47 <GeraldK> #info Yujun: Sounds like a good idea. +2 for parallel development on both bash and Python. In fact, it helps us to create reusable components such as sample inspector and sample monitor.
14:51:36 <yujunz> #info r-mibu suggests submit the code and verify it with a non-voting job
14:52:05 <r-mibu> #topic performance profiler
14:52:07 <cgoncalves> +2 on all of these notes
14:52:12 <yujunz> #link http://artifacts.opnfv.org/doctor/review/23963/scenarios/index.html#performance-profile
14:59:26 <GeraldK> #info Aaron proposes to use standard terminology such as the ETSI FM cycle
14:59:52 <GeraldK> agreement be several people to use ETSI terminologies
15:06:27 <OPNFV-Gerrit-Bot> Yujun Zhang proposed doctor: Performance profiling specs  https://gerrit.opnfv.org/gerrit/23963
15:09:03 <r-mibu> #endmeeting