14:00:08 #startmeeting trove 14:00:09 Meeting started Wed Jul 11 14:00:08 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:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:12 The meeting name has been set to 'trove' 14:00:19 #topic roll call 14:00:37 hi 14:00:43 gang: hi 14:02:14 let's wait a few more minutes for others to join us 14:02:22 o/ 14:02:37 long time no see:) 14:02:40 fanzhang: hi 14:02:57 hi 14:03:07 wangyao: hi 14:04:14 :) today we're having a bigger gathering, let's start 14:04:34 #topic Rocky goal updates 14:05:12 we still don't have many new patches last week 14:05:38 for the trove repo, we have one backport to the queens branch 14:05:46 #link https://review.openstack.org/#/c/580584/ 14:06:48 we also have 5 different issues for the queens branch, and 3 of them should be squashed into one commit to satisfy the CI 14:07:22 and it's finally working now, please also help to review on that patch 14:07:44 I'll add the stable-maint group to the reviewers list later 14:08:21 I saw some patches of you guys,but got no time to review in the past two weeks. Will try tomorrow:) 14:08:22 troveclient 14:08:45 fanzhang: good news, thanks, :) 14:09:38 troveclient, I just found wangyao_ has submit a new patch for OSC, thanks, I'll help review on that 14:09:53 #link https://review.openstack.org/#/c/581710/ 14:10:40 and the Zuul v3 migration which has been there for about 3 months 14:11:13 so I add a wf+1 last week(or the week before last) 14:11:25 #link https://review.openstack.org/#/c/561936/ 14:11:26 zhangchao thanks, Because there is no test environment, the correctness is not known. Please help review it 14:11:37 zhangchao-->zhaochao 14:12:08 however there is a new issue in troveclient py27 test 14:12:34 wangyao_: thanks for the work, will review asap 14:13:04 and I also got a patch for the troveclient py27 test 14:13:09 Today, I try to review https://review.openstack.org/#/c/581210/ , but not familiar with buildins (: 14:13:11 #link https://review.openstack.org/#/c/581210/ 14:13:39 gang: thanks, did you reproduce the problem 14:14:27 zhaochao: no, I did't do the reproduce work 14:14:52 I got that problem about 'test_module_create' when did tox 14:15:54 gang: for simple test, would just install the python-future package and test to import builtins module 14:16:23 gang: and then try to mock 'builtins.open', just simulate how the test_module_create test runs 14:17:00 wangyao_: yes, the problem will be fixed by the 'correctly mocking builtin open ...' patch 14:17:40 OK, that's what'new in our main repos 14:17:41 zhaochao: OK, tomorow I will try. I could just use the tox just wangyao said. 14:17:44 so we should merge this patch as soon as possible 14:17:55 gang: thanks 14:18:17 wangyao_: yes, please help review the patch if you have time 14:18:39 will do 14:19:02 for the python3 first patches, I did some first investigations before 14:19:08 wangyao_: thanks 14:19:38 and it turns out that we may have to do some 'not small' changes to troveclient to get things work 14:20:26 however I'm afraid I don't have much time on that, if the bandwith permits, I'll continue on that 14:21:39 but for python 3 first in troveclient repo itself, the patch looks like simple, I'll try to got that one merged recently 14:22:43 OK, that's all about the updates in the last week from my side 14:23:03 we have 2 weeks left for the rocky-3 14:23:15 do you have any updates? 14:24:24 fanzhang: do you have time to continue on the file injection bp? 14:25:11 Seems like the bp could not be finished in this cycle. I could do some framework things, but it may be little rough 14:26:32 I will try submit two or three patches about ocs 14:27:13 fanzhang: OK, I think that's fine, if you think it's ready to submit the patches for review, please do, but I think we can wait for more time 14:27:32 wangyao_: that will be great, thanks 14:28:33 Recently I try to take advantage of extended_properties to update my previous commit about mongodb configserver volume size and qutoas volume size. Maybe this can be as a part of cluster supoorting job. 14:31:23 gang: I recalled about that patch, this? 14:31:28 #link https://review.openstack.org/#/c/536684/ 14:32:24 Yes, this patch. 14:33:04 And also intend to add extended_properties into trove cluster-create in troveclient repo, well, if possible 14:33:56 Since we have support this parameters but never used before. 14:34:27 gang: that would be great, it's great to see we could make progress on that, :) 14:34:43 Sounds great. Come on gang 14:35:05 👍🏼 14:35:32 :) hope could make some progress under this cycle. 14:36:01 o, that's a sad topic 14:36:28 I think we may have finished the updates topic, let's move to the open discussion 14:36:43 #topic Open discussion 14:37:59 it's now near the end of rocky cycle, we have 60~70 commits for all trove repos 14:38:50 comparing to queens, the number was 240+ 14:39:44 Major general nearly four times:( 14:40:22 Nearly four times less 14:40:35 Em, there are lots of reasons, we cannot blame on ourselves. 14:40:46 yes 14:41:01 many OpenStack projects have similar problems 14:41:30 The number of contributers is less than Queens. 14:41:56 so the question is, do you have some thoughts about the direction of Trove under the current situation 14:42:54 remain stable, reduce new feature development~ 14:42:56 gang: yes, I did draw some charts about these numbers in the Openinfra speech 14:44:28 wangyao_: in some way, trove is quite 'stable', no many big features were brought in for several years now 14:44:50 It seems nova, cinder and neutron is still active, some other pals and Saas projects are losing contributions. because we don’t have users’ requirements , I don’t have a clear direction what we should be working towards 14:45:09 Paas 14:46:05 I found the main features all came out before Kilo, cluster was latest(Juno) 14:46:43 after that the main development is about supporting more datastore engines, and fixing existing problems 14:47:18 fanzhang: yes, that's may be the biggest problem 14:47:52 There are many use cases I think somewhere in the whole world, but we may not ever hear some. So what should and what can we bring up? It’s hard. 14:48:24 Have you ever talked to TC? 14:48:53 gang was talking about improving clustering, I also agree on that, however as none of us are now focusing on the databases themselves 14:49:02 so this could also be hard 14:49:04 There also has a sound that openstack should just focus on IaaS, and drop all of Paas and Saas. 14:49:43 fanzhang: yes, TC did reached me, and exchanged the situation about the project 14:50:04 Do they have some visions for projects like us? Or maybe on pig, we may have some users interested in trove. 14:50:18 On PTG 14:50:36 and TC was saying would talk to more interested users and companies to help on the project 14:51:31 gang: it may be related to the big tent discussion 14:51:48 some people recently post some patches in trove, that may be a good starting I guess? 14:52:47 And IMHO, we should try to organize a PTG gathering to collect users voices. 14:53:11 Even just by emails, and seek some help from tc 14:56:32 So what do you say... 14:57:06 fanzhang: do you mean we should organize a dicussion about Trove on the mailinglist? 14:57:55 Yeah, that could work. 14:58:44 OK, I'll consider about it. Arimth did that before, but the result seems not good...:( 14:59:44 and comparing the Arimth, we don't have more user cases to support the discussion 14:59:47 Join a tc meeting, have some discussions and try to find some use cases, and collecting opinions about trove, we don’t have other ways besides these 14:59:51 O, time is up 15:00:10 Just one more thing 15:00:31 If you show up in PTG, that would be great 15:00:36 :) 15:00:56 Ok, that’s all 15:01:59 fanzhang: thanks, for the PTG, I didn't prepare for that... 15:02:10 thanks, everyone 15:02:20 good night 15:02:22 and sorry for the horizon team meeting... 15:02:25 Bye 15:02:25 good night 15:02:31 night 15:02:42 #endmeeting