14:00:27 #startmeeting trove 14:00:28 Meeting started Wed Jun 6 14:00:27 2018 UTC and is due to finish in 60 minutes. The chair is zhaochao. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:31 The meeting name has been set to 'trove' 14:00:49 Haven't seen all of you for a long time 14:00:50 Hi, zhaochao 14:00:54 #topic roll call 14:00:56 fanzhang: hi 14:01:04 wangyao: hi 14:01:08 hi 14:01:11 o/ 14:01:13 Hi wangyao so busy these days? 14:01:19 o/ 14:01:28 yeah :( 14:01:30 songjian1994: gang hi 14:01:43 zhaochao: hi 14:01:48 hi 14:01:52 Me too🙁 14:01:53 finnaly we have a big gater today, :) 14:02:08 LOL 14:02:08 :) 14:02:21 haha 14:02:38 :) I think we could start now 14:02:55 #topic Rocky goal updates 14:03:31 fanzhang: songjian1994 wangyao please take a look at the log of the last weekly meeting 14:03:42 http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-30-14.00.log.html 14:04:11 all right 14:04:50 gang and I talked about only focusing on some of the goals, as it looks like all of us don't have much time on the community activities 14:06:00 please put your opinions, and we could make a conclusion on that topic 14:06:13 Startling to have some spare time recently. So will get back to upstream contributions 14:06:25 Soon.. 14:06:36 fanzhang: that's greate 14:07:12 I also got many email notifications about patchset updating, thanks, everyone 14:07:52 fanzhang: thanks for update the patch for migrating cryptography 14:08:19 I noticed the gate jobs’ failure,but have no clue what’s the reason. You said that may be the image building,but I did not find the log 14:08:33 for that patch, I was thinking just completely removing cryptograph now 14:08:54 fanzhang: no, the updated patchset failed because not updating unittests 14:08:56 agree 14:09:01 I don't find logs in troveclient 14:09:10 Oh,right,I wanted to tell you about the patch set earlier this day, sorry, forgot to do so 14:09:30 we could stop support some old version 14:09:51 I agree with last week what you talks about, too. 14:10:56 A follow up patch to remove the requirement or doing so in one change, I am ok to both. 14:11:40 wangyao: thanks, is there any other goals you prefer to achieve? 14:13:02 It should be enough for me to complete the bp 😂 14:13:34 fanzhang: yes, according to the updated bug/maillist thread, maybe it's better to just remove cryptograph completely(as they want to remove it from requirements list) 14:14:49 I just want finish this --TroveClient - OSC migration, I have been delayed for a long time, really sorry~ 14:15:01 OK, for the rocky updates, I'm sorry that I am still not able to do something, but I did look though the patchset list from time to time 14:15:05 Will commit a new patch set tomorrow if you don’t have much time to do so. 14:15:42 What about the gate jobs.. 14:15:46 fanzhang: please do, thanks, you could add yourself to the co-author 14:16:03 fanzhang: I'm just going to talk about that 14:16:13 LOL 14:17:16 firstly songjian1994 and I noticed the gate jobs failed weeks ago, and I came up with this: https://review.openstack.org/569405 14:17:52 By the way,Improve cluster supporting is a huge work. I'm afraid it's more difficult to finish 14:18:13 this patch should fix the mysql gate jobs, I added wf-1 because we need some more unittests for the changes 14:18:24 Yes, I noticed the patch and saw your comment 14:18:45 wangyao there will be many smaller bps of cluster supporting I guess 14:19:39 wangyao: agree, we could split that to many smaller ones, can do what we can finish in the Rocky cycle 14:19:52 New unit tests? Of which functions...I don’t see the failure of gate jobs on this patch. 14:20:54 songjian1994: yes, thanks, please help review (or take it if you have time and resource on it), :) 14:21:39 fanzhang: that patch add a new hook mechannism, so new unitests is neccessary 14:22:00 Ok will help review (finishing it may be a bit difficult for me...) 14:22:22 however we have another problem for gate jobs 14:23:01 Emmm.... 14:23:50 the patch from wangyao for troveclient failed by the new problem, I added a comment before 14:24:07 recheck won't help 14:24:24 yeah I see, But I have no idea how to fix it 14:24:56 * zhaochao just look for the patch caused the problem 14:25:16 Same here.i saw your comments,but didn’t find the error logs 14:25:58 the problem caused by a patche merged recetly in DIB 14:25:59 https://review.openstack.org/#/c/568697/ 14:26:47 let me look for the error log 14:27:58 http://logs.openstack.org/73/560373/3/check/trove-functional-mysql/e1d5df8/job-output.json.gz 14:28:14 search for "https://cloud-images.ubuntu.com/SHA256SUMS" 14:28:44 Please link it for easy notes 14:29:30 OK 14:29:41 #link https://review.openstack.org/#/c/568697/ 14:30:43 the change in DIB make trovestack failed to build images 14:31:52 #link https://github.com/openstack/trove/blob/master/integration/scripts/functions_qemu#L36-L37 14:32:36 we have to change lines in the above location to follow the DIB change 14:33:22 and as the previous problem ( mysql restore, caused by xbstream) and this new one both will fail gate jobs 14:34:16 we have to combine two changes into one commit, it's bad, but we have no choice... 14:36:05 Thanks for the detail investigation:) 14:36:11 Maybe we can solve the problem of DIB first, and then solve the problem of mysql, for example, temporarily set the mysql gate to no vote? 14:37:01 songjian1994: yes, that will also work 14:37:09 big +1 for zhaochao, I was stunned 14:39:49 songjian1994: Oh, I just forgot mysql jobs are both in check and gate jobs, and usually gate jobs cannot be set to non-voting, though it should hurt as it's only a workaround 14:39:52 wangyao: :) 14:40:53 fanzhang: wangyao If you have some time available, could you help to fix the gate failures? 14:41:45 It turns out that I didn’t know this before 14:41:52 Anyway, have to solve it no matter what. Will try :) 14:45:04 songjian1994: like some convention(and in fact we can set gate jobs to be non-voting), I learned that by patching jobs for trove-dashboard in the project-config repo... 14:45:07 fanzhang: thanks 14:46:21 OK, for the Rocky milestone-2, it's scheduled this week, but as we didn't get many patches after milestone-1, I think it should be fine to skip this tag 14:46:50 Any suggestions for that? 14:47:02 it may be a bit difficult for me to fix the gate, I'll learn from fanzhang 14:47:31 ski will be a good choice 14:48:27 ski--> skip 14:48:37 So we have no choice but skipping this tag 14:48:46 wangyao: if you setup a working environment by trovestack, to simulate gate jobs could be easier, :) 14:49:55 songjian1994: gang what about you? 14:50:01 will try if I have enough time :) 14:50:38 Also, time is the biggest problem 14:50:42 like fanzhang said, we have no choice 14:51:27 Yes, then let's skip it 14:52:57 hope we have many patches for the Rocky milestone-3 14:53:04 :) 14:53:20 wangyao: yes 14:54:32 #agreed As we didn't have many patches merged after Rocky milestone-1, let's skip Rocky milestone-2 14:54:54 any other topics about rocky goals? 14:55:11 notice that recently there some new committer for trove, looks good. 14:55:34 how about this one https://bugs.launchpad.net/trove/+bug/1763567 14:55:34 Launchpad bug 1763567 in OpenStack DBaaS (Trove) "Trove CLI doesn't support listing instance by project/all with admin" [Wishlist,New] 14:56:04 that's great 14:56:56 The focus of our work is not on trove, we need more new committers 14:57:05 gang: it's great for new contributor to help Trove, though maybe we don't have much support for them 14:57:47 As we actually have not much support either 😂 14:58:23 so I change the importance of this bug to wishlist. 14:58:52 But I think it's a good suggestion. 14:59:18 Time up 14:59:26 gang: yes, listing all instances may be useful 14:59:35 O, yes, time 's up 14:59:36 Leave it for tomorrow:j 14:59:43 :) 14:59:49 0.0 15:00:01 So have a good night guys 15:00:25 good night 15:00:26 just add your comments to the bug if you're intrested on that 15:00:33 thanks, everyone 15:00:34 OK 15:00:35 good night 15:00:41 night 15:01:00 #endmeeting