14:00:18 #startmeeting trove 14:00:19 Meeting started Wed Aug 8 14:00:18 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:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:22 The meeting name has been set to 'trove' 14:00:31 #topic roll call 14:03:19 Courtesy ping fanzhang kumarmn maciejjozefczyk songjian1994 wangyao zhanggang bzurkowski dkrol 14:04:07 looks like no one is joining me today... 14:04:19 let me wait for some more minutes 14:05:00 dkrol: hi 14:05:06 hello all 14:05:20 Sorry for being late 14:05:32 but I had to register :) 14:06:09 dkrol: hi, it's fine, but it looks like only two of us today... 14:06:46 bzurkowski and mpiwowarczyk will join soon 14:06:58 but anyway we can start :) 14:06:59 I was think about making some notes and then finish this meeting quickly 14:07:06 OK 14:07:24 #topic Rocky goal updates 14:07:55 last week we also have a few patches merged 14:08:16 the ones about extended_propoerties when creating cluster 14:08:41 the one to support creating cluster with configuration in troveclient 14:09:26 I got focusing on the project on last two days 14:09:59 I saw you activity, it was impressive :) 14:10:17 and went through most of the active patches 14:10:23 dkrol: thanks, :) 14:11:12 we have 3 patches inside trove-tempest-plugin, the first two look good to me, and I gave my +2 votes 14:11:45 I updated the third change a while ago 14:11:51 we also have 2 pathes to fix some problems during resizing flavor 14:11:51 Thanks for reviewing 14:12:16 bzurkowski: :) my pleasure, thanks for working on them 14:12:27 #link https://review.openstack.org/#/c/588194/ 14:12:35 #link https://review.openstack.org/#/c/588432/ 14:13:00 I think the related bugs are valid 14:13:19 but the fixes are based on the stable/queens branch 14:14:06 I commented about resubmmiting against master 14:14:46 however it seems TingtingYu may still not get my comments 14:15:59 OK, that's all from my side about patches and reviews in Trove projects 14:16:18 do you have some topics to dicuss on them? 14:16:32 ok great, we can check these reviews this week 14:17:07 one topic from me it about PTL. I was told to push a change to openstack/governance repo and I did it - https://review.openstack.org/#/c/588510/ 14:17:19 it is now being voted by TC 14:17:29 dkrol: that's great 14:17:46 I reviewed one of the changes related to resizing flavors 14:17:58 It looks good to me 14:18:08 many members from the TC have voted on that 14:18:16 But as already said, we must firstly rebase onto master 14:18:48 dkrol: I think the patch will be approved by the TC 14:19:46 bzurkowski: yes, I saw your comments and also commented on the patch, we'll recheck when it's rebased on to master 14:19:55 zhaochao: yes, I see TC members are voting. Every day I see new votes :) 14:20:07 I hope it will end soon 14:20:36 but anyway we are working on current patches 14:20:49 is there anything to do for Rocky release ? 14:21:17 bzurkowski: we may also need one or more new unittests on that change 14:22:12 dkrol: the TC did reach to me about it, so I also don't know how long will the patch get merged 14:22:13 zhaochao: Yes, we should ensure that this change is fully tested 14:22:52 about the Rocky releases 14:23:05 this week we have to release Rocky RC1 14:23:37 as I stated before in my comment for the extended_properties patch 14:24:09 the deadline of troveclient is much earlier 14:24:47 ok, I see 14:24:52 and I just found the some patches to create the rocky branch for troveclient 14:25:15 they are auto-generated, we have to review on them 14:25:41 though none of the current team members are in the stable-maintain group 14:25:51 do you have ids of these patches ? 14:26:03 so we only have the permission to add a +1 14:26:31 sure, but we can review them and give some comments anyway 14:26:54 dkrol: yes, let me get the list of those patches 14:27:45 https://review.openstack.org/#/q/owner:infra-root%40openstack.org+status:open+project:openstack/python-troveclient+(branch:master+OR+branch:stable/rocky) 14:27:59 zhaochao: ok, thanks, we will take a look 14:28:09 and for the trove and trove-dashboard repo 14:28:43 I'm going to tag trove just before the extended_properties patch being merged 14:29:42 that is I6a21ba2ba890a82875f9b6dae3c6b93bc9fdb4b0 14:29:58 ok, this sounds good 14:30:50 we don't have new patches merged in trove-dashboard 14:31:01 so it should be the same commit as the milestone-3 14:32:06 ok 14:32:14 that's should be all we have to do with the rc1 release 14:32:44 ok, great 14:32:56 I don't have any other topics 14:33:12 after rc1 release, as the rocky branch is created, we could move on with the development 14:34:30 dkrol: OK, let's move the open discussion topic, do you have any ideas about the trove-tempest-plugin 14:34:42 #topic Open discussion 14:35:23 Regarding trove-tempest-plugin 14:35:38 After merging current changes I was going to focus on proposing the first Tempest scenario so we could start discussion and review 14:35:58 bzurkowski: yes 14:36:27 This is going to be a critical point in the development of this project, I guess :) 14:36:52 Feedback from all of you will be highly appreciated 14:36:58 bzurkowski: that's great, and yes, I agree 14:37:08 as I have some time these two days 14:37:25 I was thinking about how to make it working with scenario tempest tests 14:37:47 The scenario will cover single instance provisioning and basic database operations (eg add data to instance, verify and remove) 14:38:36 Some ideas from native integration tests could be reused 14:39:06 yes, the simplest and quickest solution to reuse the trovestack script 14:39:12 zhaochao: we have scenario tests running internally and we have a vision how to do it. we wanted to push 2 scenario tests first and explain the vision 14:39:15 we only need the kickstack part 14:39:17 For example helpers for each individual datastore to communicate with database service in an unified way 14:40:19 Implementing the tests is one thing but we also have to build infrastructure 14:40:56 zhaochao: You already mentioned that some Ansible playbooks will have to be updated to setup testing env for Tempest scenarios 14:42:22 dkrol: bzurkowski Oh, yes, I see, are you also working on the infrastructure part? 14:44:01 Not yet, but we have some internal playbooks to setup devstack with support for our Tempest scenarios 14:44:27 With Trove and datastore images in place 14:45:12 We could use these playbooks as reference 14:45:30 bzurkowski: OK, I'll also help on this topic, then we could focus on the migration of integration tests 14:46:48 zhaochao: the point here is we don't know how tempest tests are run by zuul so we will need you support here 14:47:42 but anyway we will start releasing first tests to share our vision and open discussion 14:48:04 zhaochao: Do we have some other IRC channel to communicate outside wednesday meetings? 14:48:16 dkrol: got that, I'll try my best not to slow down the process of adding scenario tests 14:48:42 bzurkowski: dkrol forgot to tell you about the IRC channel 14:48:49 yes, the #openstack-trove channel 14:49:12 thought very few people on that channel 14:49:32 but we still have some users going there for help 14:50:09 ok, I see 14:50:15 is this also for communicating trove development ideas ? 14:50:20 sadly the current team members don't have much time to offer help 14:50:37 dkrol: yes, the channel is the official team IRC channel 14:51:08 ok, we will use it more often :) 14:52:07 great, :) in fact, I'm on the channel on the day time(UTC+8), though may not be responsing very quickly 14:53:03 ok great 14:54:04 OK, I think that'all tonight, if no more topics from you, I think we could finish it a little earlier 14:54:25 ok, no more things from my side 14:54:32 thanks 14:54:45 No more from my side nither 14:54:52 Thank you 14:55:00 OK, let's end here, thanks, dkrol bzurkowski 14:55:17 #endmeeting