14:00:33 #startmeeting trove 14:00:34 Meeting started Wed Oct 10 14:00:33 2018 UTC and is due to finish in 60 minutes. The chair is dkrol. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:37 The meeting name has been set to 'trove' 14:00:47 Hello All Trove developers :) 14:01:01 Hi Dariusz 14:02:17 hi guys 14:04:09 we should wait a few more minutes for the rest 14:04:18 hi 14:04:29 fanzhang: hello 14:05:51 Hello, hello 14:05:58 Did you get me email reply 14:06:27 Hey bzurkowski 14:06:28 fanzhang: no, I did not receive anything 14:07:41 Reply to your weekly meeting invitation at 2nd Oct. 14:07:57 this one I received :) 14:08:12 Oh good. 14:08:34 unfortunately no one else responded 14:08:56 o/ 14:09:09 sorry, wrong meeting :) 14:09:17 rdopiera: no problem :) 14:11:04 I think we can start 14:11:09 #topic Recent changes and reviews 14:11:33 did you have time to work on any new reviews or changes ? 14:13:24 This week I added two minor changes 14:13:35 https://review.openstack.org/#/c/608640/ 14:13:36 https://review.openstack.org/#/c/608653/ 14:13:45 in fact, I started (today) working on documentation (/trove/doc/source/admin/building_guest_images.rst) and editing, rephrasing, making language more academic and augmenting with examples - from perspective of a newcomer, will commit asap 14:14:34 Cool, I can help review that, but TBH, I am not familiar with devstack plugin 14:14:51 cezary_zukowski: This is great, this is what we need to attract new users and developers 14:15:40 bzurkowski: thanks, and I really want to find time to review your changes :) btw. Zuul is an automate to test the changes? 14:16:20 bzurkowski: is your change only related to vitrage ? 14:16:51 cezary_zukowski: great, please share it once it is ready and we can review it 14:17:09 dkrol: Yes, I need it for my Vitrage PoC to fetch all instances into Entity Graph 14:17:22 #link https://review.openstack.org/#/c/608640/ 14:17:26 but as bzurkowski said - it is very important to work on changes that can attract more users 14:17:27 However it might by useful for future integrations with other services 14:17:40 #link https://review.openstack.org/#/c/608653/ 14:18:49 ok, great - I saw Marcin already added a few comments 14:19:12 I am trying to build Entity Graph with Trove instances and clusters, connected to VMs, storage and neutron ports; and then conduct Trove-oriented RCA 14:20:41 I see 14:21:29 I suppose we can move to our next topic 14:21:31 RCA - root cause analysis? What are main difficulties there? 14:21:51 ok 14:22:19 #topic Trovestack redesign 14:22:33 cezary_zukowski: We can continue discussion about RCA after the meeting ;) 14:22:54 I'm still working on https://review.openstack.org/#/c/608653/ 14:22:59 bzurkowski: sure, time's up 14:23:00 #link https://review.openstack.org/#/c/608653/ 14:23:34 there are some difficulties with stack user on the machine as I moved trove guest image build to devstack plugin 14:23:53 correct link? 14:23:57 I still need to debug it but it seems to be related to openstack infra and permissions 14:24:12 dkrol: https://review.openstack.org/#/c/606960/ 14:24:41 lol correct link ^ 14:24:51 yes :) 14:24:59 too many tabs opened :) 14:25:41 anyway, this task still requires additional work 14:26:05 fingers crossed 14:26:15 I hope I will have better news next time 14:27:03 next topic should be about python3-first support but Marcin Piwowarczyk is absent so we can skip it 14:27:07 #topic Building the community 14:27:24 bzurkowski: do you want to comment on this ? 14:27:52 #link https://etherpad.openstack.org/p/trove-revitalization 14:28:13 btw. is distributing guest images a part of "Trove redisign"? it could attract more people (as Docker images) 14:28:48 cezary_zukowski: It is already included in Trove revitalization pad 14:28:51 cezary_zukowski: the idea is to build images automatically during devstack instalation 14:29:32 okay, but all this happens at the local installation? no public image repositor online? 14:29:47 no public images repo 14:30:10 Looking at our ideas in the pad there are several actions that we could undertake as the first step 14:30:32 dkrol: okay, just curious 14:30:54 1. Write emails to each contributor that participated in reviews or development in Rocky and Stein releases 14:31:10 2. Write email to OpenStack "community support" asking about the guideline 14:31:23 e.g. Kendall Nelson (Upstream Developer Advocate) and Ildiko Vancsa (Ecosystem Technical Lead) 14:32:26 3. Add mailing list to inform interested people about the roadmap, progress and issues 14:32:43 What do you think? 14:32:50 good points, growing the network always counts 14:33:17 These actions shouldn't take much effort 14:33:37 yes, they look good to me 14:33:39 so no reason for asking - just do it 14:33:52 4. make #openstack-trove not as silent as now :) 14:34:08 we can get email addresses from stackanalytics 14:34:35 so 1. is oriented towards previous users/developers 14:34:46 2. and 3. is about new users 14:35:02 About feature matrix, my experience is that we only have MySQL in production, redis and mongodb is stable but simple. I am not sure how we define experimental nowadays. 14:35:24 but I'm wondering how can we get direct access to existing users 14:36:03 Datastore maturity was defined years ago: https://specs.openstack.org/openstack/trove-specs/specs/kilo/experimental-datastores.html 14:36:10 Email is the only way I guess, maybe some social networking apps 14:36:38 fanzhang: reviewing datastore support status was an action point for Rocky release 14:36:58 it was not touch due to lack of resources I suppose 14:38:00 it is something in the update documentation task as well 14:38:40 cezary_zukowski: Since you started updating docs maybe it would be a good idea to look at current state of datastore capability matrix? 14:39:04 we can bring casandra to next level with not big effort but the question is " is it our goal for now " ? 14:39:23 I would like also to emphasize that ongoing development and stable number of pushed and merged changes should be one of our priorities 14:40:12 bzurkowski: https://wiki.openstack.org/wiki/Trove/DatastoreCompatibilityMatrix 14:40:35 cezary_zukowski: Yes, this one 14:40:36 pgodek: I think we have other more important priorities and we don't have enough men power :/ 14:41:02 @dkrol this is alos my impression 14:41:27 Maybe we should we put the matrix into better accessible place to show that Trove is versatile and powerful tool 14:41:48 bzurkowski: Let's do it. 14:42:43 I have just impression that if we will not show stable development Trove will be visible as a dead project 14:43:07 Good point 14:43:31 Working on docs maybe a fresh start. 14:43:47 bzurkowski: I will have a closer look at the document and whether it's up-to-date 14:44:14 We also have one talk about Trove at OpenStack Summit in Berlin 14:44:19 That could help advertise the project 14:44:36 having documentation updated is very important for new people 14:44:37 I mean, the talk + project update 14:45:32 Is there any etherpad notes about the discussion? bzurkowski 14:45:34 bzurkowski: yes, this will give us audience but it would be great to have some progress to show in terms of merged changes 14:46:18 dkrol: Right, we must prepare something concrete 14:46:47 fanzhang: What discussion? 14:46:58 it is great we have the same point of view :) now we should just deliver 14:47:31 I thought you mean you guys have had a talk at the past summit 14:48:16 :) 14:48:29 we will have thalk in berlin ( next month ) 14:48:32 https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22273/towards-production-grade-database-as-a-service-in-openstack 14:48:33 fanzhang: I meant, we are presenting the talk at the conference in Berlin, mid-November 14:49:41 Yeah I see. Don’t realize summit in Berlin is the coming one. :( 14:52:07 fanzhang: I suppose you are not coming to Berlin then ? :) 14:52:38 No I will not go to Berlin. 14:53:30 ok, do we have any other open discussion topics ? 14:54:59 No more from my side. Thanks for all of you taking over trove and trying to make it great again. 14:55:22 No more from me either 14:55:41 fanzhang: thanks, I hope you will be still around 14:55:54 No more from my side 14:55:55 I suppose we can finish our meeting for today 14:55:56 Try my best. Thanks 14:55:57 many thanks all :) 14:56:15 Thank you all for great meeting :) 14:56:17 see you all next time 14:56:19 #endmeeting