14:00:17 #startmeeting trove 14:00:18 Meeting started Wed Apr 18 14:00:17 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:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:21 The meeting name has been set to 'trove' 14:00:31 #topic roll call 14:01:05 hi 14:01:18 gang: hi 14:01:53 looks like today we only very few people to the meeting... 14:02:06 yes... 14:02:16 hi 14:02:35 wait some minutes for others to show up 14:02:38 kumarmn: hi 14:03:25 hi sorry for a little bit late 14:04:01 fanzhang_: :) 14:05:41 OK, let's start 14:05:57 #topic Rocky goal updates 14:06:58 This week we're on rocky milestone-1, so I may have to submit some patches for it 14:07:50 in the first and a half months of rocky cycle, we may don't have many changes 14:08:12 There are some patches from you, and great work! 14:08:55 fanzhang_: thanks 14:09:28 Should we approve the nova file injection bp before rocky milestone-1? Maybe I can start developing ? 14:09:30 zhaochao: You do have to submit a patch to the openstack/releases repository 14:09:32 https://github.com/openstack/releases 14:09:56 Take a look at the README. 14:10:20 kumarmn: thanks, I'm just going to ask, anything more about the milestone ? 14:10:30 fanzhang_: I think you could start developing 14:10:52 something like 'tox -e venv -- new-release rocky trove milestone' 14:11:11 zhaochao sure, I guess I have to code step by step :) 14:11:24 That will take care of trove and trove-dashboard. I believe for python-troveclient, you have to create the snapshot yourself. 14:11:29 fanzhang_: I approved the bp, and will wait for another week for the other core members to approve it 14:12:17 kumarmn: where should I run the tox command , in trove repo or the releases repo ? 14:12:33 releases repo 14:12:41 zhaochao thanks :) really appreciate that anyone can help review this spec :https://review.openstack.org/#/c/557583/ 14:12:48 kumarmn: got that, thanks 14:13:18 #action zhaochao have to do the tasks about Rocky milestone-1 14:13:44 fangzhang: so, need a workflow+1? 14:13:58 #action fanzhang_ should start coding about nova file injection spec. 14:14:25 I'd like you actually review this spec first :) 14:14:28 and for the global goal, mox-removal 14:14:42 it's already solved in the Trove repo 14:14:52 of course :) 14:15:00 and the other repo have to be dealed is trove-dashboard 14:15:11 we now have https://review.openstack.org/#/q/project:openstack/trove-dashboard+topic:mox-removal 14:15:41 ok, will do review later 14:15:54 5 patches for this topic in trove-dashboard 14:16:30 one of them from Chuck Short, but no updates recently to address my comments, so I also updated it today 14:16:34 fanzhang_: thanks, :) 14:17:14 and https://review.openstack.org/#/c/562144/ 14:17:35 this one is related, without it, we cannot merge any patches... :( 14:17:52 better to add them to # link 14:18:16 fanzhang_: good point, I'll do that 14:18:26 #link https://review.openstack.org/#/q/project:openstack/trove-dashboard+topic:mox-removal 14:18:40 #link https://review.openstack.org/#/c/562144/ 14:19:02 another patch need to mention from me 14:19:06 https://review.openstack.org/#/c/562144/ 14:19:10 #link https://review.openstack.org/#/c/562144/ 14:19:38 I'm going to migrate the zuul jobs to Zuul v3 native 14:20:21 the above is the first one, the jobs of trove repo will go after 14:21:53 I have 10(or 11) patches recently, please help to review, thanks 14:22:08 zhaohcao: must say you really have done a lot of work! 14:22:14 that's all from me 14:22:28 gang: :) 14:23:23 one more thing about the stable branches, you guys may have seen the mails in the mailinglist about this 14:23:37 Yes, thanks to Sean and Matt 14:23:49 we got the patches merged 14:24:30 Yes, I think as we don't have much resouce, so currently we will rely on the core stable team to help us to got the patches merged 14:25:03 If you want some fixes merged into the stable branch, please add the core stable team members to the reviewer list 14:25:57 IMHO, it's better this way right now, since we don't have much time focus on the upstream community as our full-time job :-( 14:27:18 agreed, I may be kind of full-time from time to time, like these two weeks, :), but cannot permit that for a longer period 14:28:21 OK, do you have more on the rocky update topic, gang have added another topic about cluster supporting, we could jump to that one 14:29:27 then let's move on 14:29:32 #topic cluster supporting 14:29:40 yes, I am not think clearly about trove cluster, need some advises from you guys 14:30:10 gang: would you tell more about your thoughts about this? 14:31:09 for me, "Remove all instance API and treate instance as a single node cluster." seems not the right way, but I don't know what's your detailed plan 14:31:09 I get some thought from the email and from my production experience. 14:31:18 And I had add to the agenda 14:32:15 for production env, cluster is more import than instance. 14:32:41 gang: agree with the importance of cluster in product env 14:32:54 +1 14:33:07 So, my opinion is maybe we should re-architect clusters. 14:33:17 But it seems a big change. 14:33:18 however from the api level, cluster is already the first citizen as instance 14:34:05 and simple instance as single-node cluster, seems not correct and not easy to achieve 14:34:18 we also support replication of instances 14:34:31 As I mentioned before, we have to figure it out what has been supported in trove, and what has not. And then we can add more useful and urgent functions that user desires most 14:35:04 as for re-architect, if you got the time, well, I think maybe you can try 14:35:22 detail spec should be needed definitely 14:35:54 well, if we can split it into some smaller task, maybe I can try. 14:36:25 It just what I thought trove should looks like... 14:37:15 gang: fanzhang_ yes, bp is needed. the first design is important, any good ideas about this? 14:37:49 Like replication of instances, I mean maybe it should be "transparent" to end user. 14:38:16 or what are problems do you think about the current design of clusters? 14:38:56 gang: ok, I may got some points from that, replications could be a kind of cluster(or strategy, maybe) 14:39:31 the end users may want to know what they're using, replication or real cluster, that really depends on them, not us. 14:41:53 fanzhang_: from gang's idea, we could design something like "cluster type" -> replication/sharded/... 14:43:29 yeah, exposing cluster type to end users may be a great feature 14:43:57 fanzhang_: yes, in some case user want to know the details, this is why we discuss. 14:44:10 however we still have a lot changes for this 14:44:51 zhaochao: yes, if we do this, it will be a huge work. 14:45:37 so, do you think there need a spec? 14:45:56 gang: would you add the related links in https://etherpad.openstack.org/p/trove-priorities-and-specs-tracking, under "Improve cluster supporting" 14:46:03 gang: yes, we need a spec 14:46:23 OK 14:46:26 gang: we may need more discussions about this 14:46:33 definitely 14:46:54 zhaochao: can't agree more 14:47:37 gang: if you like to push this, you could create a new pad for it, or add your thoughts under "Improve cluster supporting" of the tracking page 14:47:57 everyone could help to improve this 14:48:19 I think this coud be a good direction 14:48:36 zhaochao: I will, if I have some step that I would ask you and fan. 14:49:33 would love to help with that 14:50:10 fanzhang: thanks in advance :) 14:50:18 gang: great, I will aslo do some investigation about this topic after I finish the global goals and Zuul v3 migration(may not take too long, one or two weeks maybe) 14:50:42 zhaochao: thanks! 14:51:24 #action gang do the first draft design about improving cluster support, fanzhang and zhaochao will help on the that 14:51:28 gang: no problem 14:52:34 So any thing more about this topic? gang fanzhang_ 14:53:02 no 14:53:13 no 14:53:40 really tired from work and gym 🤣 14:54:02 fanzhang_: good for gym 14:54:18 OK, I'll go the open discussiong topic 14:54:22 #topic Open discussion 14:54:40 I wanted to discuss on the Trove project updated at the Summit in Vancouver 14:54:54 I am not able to go due to a personal trip/vacation. 14:55:30 Any of you planning to go? 14:56:17 kumarmn_: sorry, I'm not going 14:56:22 sorry, can not make it 14:56:28 kumarmn_: I just forgot another question about the rocky-1, do we have a deadline? tomorrow? 14:56:44 Sometime this week, preferably by tomorrow. 14:56:49 me too... sorry 14:57:10 kumarmn_: got that, thanks 14:57:44 kumarmn_: I don't know wether any other core member will go the Vancouver summit 14:58:00 I will check with Maciej 15:00:10 OK, most of the other core members are in China, I didn't hear some of them will go to the summit. fanzhang_ , do you know some of us will go? 15:00:24 no sorry 15:00:41 OK, time's up 15:00:49 that's all today, thanks, everyone 15:00:54 will ask songjian tomorrow 15:01:01 fanzhang_: thanks 15:01:06 #endmeeting