14:02:12 #startmeeting trove 14:02:13 Meeting started Wed Aug 22 14:02:12 2018 UTC and is due to finish in 60 minutes. The chair is zhaochao. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:16 The meeting name has been set to 'trove' 14:02:20 hi 14:02:23 zhaochao: no problem - it is great you are here 14:02:28 mpiwowarczy: dkrol_ hi 14:02:33 Hello 14:02:45 bzurkowski: hello 14:02:52 dkrol_: :) 14:03:09 #topic roll call 14:03:32 it seems we could just skip this topic 14:03:45 however let's still wait for another minute 14:03:55 what is this topic about ? 14:04:17 I'm trying to make notes for future meetings :) 14:04:18 dkrol_: just wait for people to show up 14:05:21 dkrol_: when would you like to begin charing our weekly meetings? :) 14:06:01 zhaochao: it is not important for me but I would like to be prepared just in case 14:07:17 zhaochao: so my question would be when do you want to stop chairing the meetings ? :) 14:07:18 dkrol_: then you could decide, maybe the next one or the one after the next 14:07:32 OK, it seems only us here today 14:07:34 let's start 14:07:40 #topic Rocky goal updates 14:08:11 so we only have more than one week for the Rocky cycle 14:08:34 I think most of the Rocky goals have to delayed to Stein, :( 14:08:50 for the last week, I didn't have time work on the project 14:09:06 is there any list of these goals and their state ? 14:09:42 I noticed some new patches and some updated patches, but didn't have time to review on them 14:10:05 dkrol_: yes, I talked about the pads before 14:10:33 #link https://etherpad.openstack.org/p/trove-priorities-and-specs-tracking 14:10:46 I have to unearthed two changes https://review.openstack.org/#/c/558096/ https://review.openstack.org/#/c/585875/ 14:10:59 and a google sheet 14:11:04 there is also https://review.openstack.org/#/c/589760/ 14:11:11 #link https://docs.google.com/spreadsheets/d/1Jz6TnmRHnhbg6J_tSBXv-SvYIrG4NLh4nWejupxqdeg/edit#gid=0 14:11:18 and https://review.openstack.org/#/c/594241/ 14:11:18 are ready for review 14:11:44 https://review.openstack.org/#/c/591959/ - this one was abandoned 14:13:17 zhaochao: ok, I remember now. I should create a new similar etherpad with priorities and goals for Stein release 14:13:22 mpiwowarczy: yes, I got the noficiation mails, thanks for working on that 14:14:06 zhaochao: your welcome 14:14:29 dkrol_: yes, that could be useful 14:15:08 I only managed to update the trovestack redesign page today 14:15:17 add some basic ideas about the plan 14:16:09 sooon I want to finish change from python3-first topic 14:16:25 no problem, we did some reviews. I will work on plan for Stein release this week 14:16:35 I made a review for zhanggang related to cluster OSC: https://review.openstack.org/#/c/591958/ - it is very close to the submission. 14:16:52 By the way we have found that some conventions from the global guideline are not respected in the python-troveclient, e.g. the naming of long options. zhanggang declared to work on unifying this in the near future. 14:17:12 https://docs.openstack.org/python-openstackclient/latest/cli/commands.html 14:17:17 mpiwowarczy: that would be great, I did some investigation of the problems for the current python3 first patches, I will help on review 14:17:51 zhaochao: got it 14:18:12 At the very last moment I also added a few comments from my side to trovestack-redesign. I will add more after the meeting. 14:18:57 dkrol_: that's great, most of the rocky goals may have to be moved the Stein page and reevaluated 14:21:24 bzurkowski: Oh, migrating to OSC client have been slowly progressing from Queens, hoping we could finally finish it, and yes, we should follow the OSC convention 14:21:40 * zhaochao reading comments for the trovetask redesign 14:23:48 bzurkowski: I read about your comments, let's make trovestack redesign a seperate topic later 14:24:17 ok 14:24:27 for the last week updates, I see the rocky branch creating patches are merged today 14:25:45 and we don't have some critical patches recently, so we may won't have any patches to be merged into the rocky branch in the next weeks 14:26:52 it is ok for me 14:27:08 OK, that's all from my side for the last week, do you have any other topics on that? 14:27:43 nothing 14:27:46 No more comments from my side 14:28:32 just to summarize: Rocky release is going ok, we should prepare a new plan for Stein taking into account progress during Rocky; we have some merged commits and ongoind development 14:29:20 dkrol_: good summary, thanks, :) 14:30:36 dkrol_: you could use a \#info command to make a note for that 14:31:03 dkrol_: for the meetbot irc commands, you could refer to https://wiki.debian.org/MeetBot 14:31:23 I think only a few commands may be frequently used 14:32:09 OK, I temporarily add another topic for trovestack redesign 14:32:17 let's move on to that 14:32:22 ok 14:32:39 #topic trovestack redesign 14:33:15 bzurkowski: for the DIB elements, I may not make it clear 14:33:30 yes, we should have them in the trove repo 14:34:55 the elements will be refined (based on current trovestack elements and for CentOS, the projects you mentioned in the comments)) 14:35:40 and for building guestagent images in the devstack plugin 14:36:16 the logic is, when we run the trove devstack plugin, we're expecting an usable trove dev environment 14:36:54 and the guestagent image are one necessary part, so we cannot move it out of the devstack plugin 14:38:21 this is good point 14:38:39 usually we only need to one guestagent image during the dev env setup, so I think the time for preparing dev env should be OK 14:39:03 I agree that the plugin should provide Trove environment ready for use 14:39:19 The problem with building guest images using devstack plugin is, however, that the process may take a significant amount of time and it is error-prone 14:39:41 and if the DIB elements are well structured, we may also need to provide another simple script to create guestagent for any datastore (and datastore version) 14:39:47 One timeout or inactive package repo may crush the installation 14:40:31 bzurkowski: this could also be solved by allowing devstack plugin to use pre-built guestagent images 14:41:16 zhaochao: Do you mean, to expose pre-built images to the public? That could be an option. 14:41:58 we could also try to prepare a more lightweight image for testing purpose 14:42:20 It seems to me that I have already heard about similar idea during one of the summits. 14:42:24 pre-built image is a valid option but it creates additional effort to host them 14:42:49 bzurkowski: no, just provide different choices for the users of the devstack plugin, the CI job may also need to build the guestagent images every time 14:43:35 for the end users/developers, they could use their own pre-built images to avoid slowing the devstack 14:44:14 zhaochao: I see 14:44:57 the problem for CI jobs is we may don't have a easy way to tell the job whether it's necessary to build a new guestagent image(i.e the testing patch is changing the guestagent related source files) 14:45:49 the time we need to wait doesn't worry me, but if it often fails due to some transient issue and the whole installation stops, this seems to be more important issue 14:47:35 dkrol_: I remember there was the official pre-built images, however I think it's difficult to make the images 'official', the users may always have to build their own images 14:47:51 dkrol_: do you mean the CI jobs or the real deployment? 14:48:32 zhaochao: what about periodic build? zuul has obs triggered on a timer 14:48:57 *jobs 14:49:26 zhaochao: Pre-built images may be a good option for Trove new-comers. At this stage they are not interested in building own images, but rather in evaluating Trove featureset. 14:49:44 zhaochao: both - IMHO building images should be as reliable as possible 14:49:59 mpiwowarczy: previously the trove dev images are built on that way 14:51:12 bzurkowski: dkrol_ yes, then we could reimplement the post CI jobs for building dev images just like mpiwowarczy mentioned 14:52:06 Having tested usable guestagent images could be much more friendly for the new users 14:53:06 so we could make this to our todo list of trovestack redesign topic too 14:54:03 sounds great 14:54:18 I'm a little bit concerned about pre-built images. I'm not sure why creating images couldn't be a part of trovestack installation ? 14:54:36 what are issues ? 14:56:06 OK, I add a 'TODO list' section in the trove redesign pad 14:56:36 dkrol_: what do you mean by creating images be a part of trovestack installation? 14:57:22 Oh, we're near the deadline for this meeting now, :( 14:57:53 "usually we only need to one guestagent image during the dev env setup, so I think the time for preparing dev env should be OK" - I'm not sure why we want to change this logic to get pre-built images instead 14:58:19 ok, we can continue our discussion on etherpad or on #openstack-trove 14:58:30 do we have any other important topics ? 14:58:41 dkrol_: yes, please add your concerns in the etherpad 14:58:50 no more topics from me 14:59:00 I'm also ok 14:59:19 and it is great we have this discussion :) 14:59:23 dkrol_: for the pre-built images, I think we're not changing the logic, the pre-built images is for the new users 14:59:50 dkrol_: the CI job will always build guestagent images everytime 15:00:00 OK, let's end here today 15:00:05 thanks, everyone 15:00:10 thanks 15:00:14 thanks, bye 15:00:14 Good Day! 15:00:19 you too 15:00:20 Thank you and goodbye! 15:00:30 #endmeeting