13:02:58 #startmeeting doctor 13:02:58 Meeting started Tue Apr 18 13:02:58 2017 UTC. The chair is r-mibu. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:58 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:02:58 The meeting name has been set to 'doctor' 13:03:05 #topic roll call 13:03:08 #info Tomi Juvonen 13:03:10 #info Ryota Mibu 13:03:11 #info Carlos Goncalves 13:03:23 yujunz: ping 13:03:26 bertys: ping 13:03:31 #info Yujun Zhang 13:04:49 #info Gerald 13:05:13 any topic for today's meeting? 13:07:50 #topic E release planning 13:08:28 #link https://etherpad.opnfv.org/p/doctor_e_release_items 13:09:55 #link https://wiki.opnfv.org/display/doctor/Euphrates+Planning 13:09:57 #action ryota to report completion of doctor E release planning to david (using summary template) 13:10:19 #topic Report from meeting with HA 13:10:54 #link https://lists.opnfv.org/pipermail/opnfv-tech-discuss/2017-April/015863.html 13:11:56 #link http://docs.opnfv.org/en/stable-danube/submodules/availability/docs/development/overview/index.html 13:12:11 #link http://artifacts.opnfv.org/availability/docs/development_overview/_images/OPNFV_HA_Guest_APIs-Overview_HLD-Guest_Heartbeat-FIGURE-1.png 13:12:24 #link http://artifacts.opnfv.org/availability/docs/development_overview/_images/OPNFV_HA_Guest_APIs-Overview_HLD-Peer_Messaging-FIGURE-2.png 13:18:48 #info two use cases from HA had been presented. the document will be revised based on the discussion. 13:19:37 in the first use case (figure 1), Doctor work flow can be utilized. in the second use case the overlap is mainly on the notification 13:19:53 #topic AoB 13:20:17 #link https://review.openstack.org/424340 port-data-plane-status was accepted 13:20:45 congrats cgoncalves 13:21:05 #info we can test with those merged code, and can ask installers to backport this feature from pike to ocata 13:21:52 #action cgoncalves will create a new Jira ticket for backporting of this feature 13:24:30 GeraldK: thanks 13:26:48 #info status of collectd support in OPNFV installers; apex will support soon 13:27:45 #link https://gerrit.opnfv.org/gerrit/#/c/33381/ 13:27:58 #info Carlos assigned to DOCTOR-101. plan is to add collectd support introduced by the Barometer project 13:30:21 #info dwj suggests one verify job for python code unit testing and another for doctor function validation 13:30:34 #link https://gerrit.opnfv.org/gerrit/#/c/33381/ 13:30:38 #undo 13:32:03 #info workaround for experimental job type "recheck-experimental" 13:32:44 Otherwise when "check-experimental" will remove verify +1 and does not give verify +1 even when it passes 13:34:34 #info rewrite by python - add tox for test; Wenjuan reported 1) there is a patch set introducing tox, and 2) we can have new job to kick tox 13:34:51 #action ryota to create new tox job for doctor 13:38:45 Could you type a summary? r-mibu 13:38:52 ok 13:39:40 #info Ryota proposed to have some guideline in order to avoid rewrite python code of new codes which will be developed in E release 13:40:43 #info the guideline could be that the asignee/developer of new testing code inform the place in which he/she edit to wenjuan or team 13:41:26 #info so that wenjuan/team can help he/she writing new code with python 13:42:21 Sound good 13:44:35 +1 13:44:37 +1 13:44:40 +1 13:44:43 +1 13:44:44 +1 13:45:08 #info doctor team agreed the guideline 13:46:26 r-mibu: https://wiki.opnfv.org/display/doctor/Euphrates+Planning 13:47:11 r-mibu, check https://wiki.opnfv.org/display/SWREL/Release+Milestone+Description+for+Euphrates 13:47:30 bye 15:07:13 #endmeeting