14:06:05 #startmeeting trove 14:06:06 Meeting started Wed Nov 28 14:06:05 2018 UTC and is due to finish in 60 minutes. The chair is mpiwowarczy. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:06:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:06:10 The meeting name has been set to 'trove' 14:06:13 #topic roll call 14:07:17 lets wait for rest of the team 14:07:17 Hi All 14:07:28 pgodek: o/ 14:08:00 czukowki: are you there? :) 14:08:13 mpiwowarczy: yes :) 14:08:30 dkrol: and you? 14:09:32 Hello 14:09:47 dkrol_: o/ 14:11:07 I think we can start 14:11:10 #topic Python 3 first support 14:11:26 Great 14:11:48 Do we have any progress since our last meeting? 14:12:07 don't think so 14:12:13 im still waiting for https://review.openstack.org/#/c/604816/ 14:12:30 can anyone review this change? 14:12:54 Ok, I will check it till the end of this week 14:12:56 it is last change for trove python3-first goals 14:13:27 I see 14:13:33 dkrol: great 14:13:40 I hold you for a word :) 14:13:56 No problem :) 14:14:00 @mpiwowarczy - i assumed that it is not ready yet because only you are reviewers 14:15:04 Let's move forward 14:15:44 pgodek: we need approve from two core members 14:16:06 #topic Documentation 14:16:15 mpiwowarczy: do they need to be from different co? 14:17:01 cezary_zukowski: it should be :) 14:17:36 hmm, in terms of documentation, I have made notes (a generic guide) on how to install 1) devstack 2) generate trove image with trovestack 3) use image in trove (simple write/read) tests 14:17:39 https://docs.google.com/document/d/1eBmIe224yNfq65IoFq_dBRO-vdstInhx9BH2wft5saE/edit?usp=sharing 14:18:01 IMHO I think we can loosen these rules as your community is a little bit small :) 14:18:03 this was possible due to @mpiwowarczy help (his Vagrant installation) 14:18:26 mpiwowarczy: that's better 14:19:16 Nice work 14:19:23 cezary_zukowski: let me know if you need any more help :) 14:19:25 they problem with using trove on laptop is amount of RAM :) 14:19:53 Did you think about upstream ing vagrantfile? 14:20:05 dkrol_: thanks, your work with building image in devstack is also great, I have to delve into it 14:20:33 dkrol_: I may provide a generic quide and mpiwowarczy can submit his Vagrant, I think 14:20:34 cezary_zukowski: can we move this documentation into etherpad? 14:20:55 mpiwowarczy: ok, I will try tomorrow, since almost done with trove doctor 14:21:06 Once I finish working on trovestack we will need to update this guide 14:21:38 dkrol_: lets talk about trovestack in separate topic :) 14:21:58 trovestack is a hot topic today :D 14:22:05 mpiwowarczy: how about vagrantfile? :) 14:22:07 not without reason 14:22:25 this is why it last one - like topic of the night :D 14:23:42 Regarding documentation, could you add TOC for it? 14:23:44 ok, any more things about documentation? 14:24:07 And some initial description 14:24:35 To have it more easy to follow 14:24:56 dkrol_: you mean: https://etherpad.openstack.org/p/trove-docs ? 14:25:10 I think we should push it as fast as possible 14:25:44 I agree 14:25:46 Maybe something more :) 14:26:06 It is very important part of knowagle for newcomers 14:26:18 Community is waiting for a good start guide for trove 14:26:59 some communities use Google Docs for this kind of stuff 14:27:06 Also we should have add slides from trove onboarding and project update from the recent summit 14:28:00 dkrol: I already sent slides to OpenStack Summit operators 14:28:30 After they publish them along with other sessions and videos we can add links to our wiki 14:28:41 I mean we should include them somewhere in the documentation 14:29:08 I see 14:29:12 Sure, I'm just worried we forget 14:29:31 And potential users are waiting :) 14:30:42 By the way 14:30:50 We could publish doc prepared by Cezary on our wiki as well 14:31:01 And colaborate there, in the public 14:31:06 Totally agree 14:31:15 I observed similar approaches on other wikis 14:31:32 No sense to keep it internally until its perfect 14:31:37 first it need to be moved to rst I guess 14:32:23 ok, os rst first 14:32:27 so* 14:32:27 Let's check how to do it 14:33:11 #action research how to update trove wiki page 14:33:26 Hmm 14:33:50 Let's move on 14:33:59 What I meant was to publish link to GD first, review, collaborate and eventually rewrite to RST at some point 14:35:30 ok, I hink we can stop here and back to documentation in next week 14:35:38 Yes, let's move on 14:35:54 Documentation is boring 14:36:01 #topic Trovestack redesign 14:36:03 bzurkowski: exactly :) 14:36:26 dkrol: you probably want to say us something :) 14:36:44 Did you have time to check it? 14:37:22 I must say that trovestack tests are not exactly deterministic 14:37:33 I will try take it to my wall in end of the week 14:37:56 And I don't understand how gtid in mysql is used 14:37:57 dkrol_: only Non Voting jobs or all of them? 14:37:59 dkrol_: because they downloading many things during the tests? 14:38:21 All of them 14:38:49 I'm not sure if this related to downloading 14:38:53 this is something what should be addressed 14:39:08 some changes need to be rechecked over and over 14:39:36 Anyway now a mysql is built by default during trove installation in devstack plugin 14:39:39 dkrol_: when I was testing, network conditions was the case 14:39:40 mpiwowarczy: Who will check? Zuul was killed by Zuul hunter :) 14:40:31 dkrol_: I only have a look, I saw you included cloud.init support, and was wondering why you need to modify "trovestack" script 14:40:33 So trove functional, mysql sing and mysql multi use this image 14:41:00 #link https://review.openstack.org/#/c/606960/ 14:41:15 For some reason there was an issue with checking mysql replication by issue ing ssh command 14:41:38 I couldn't ssh in tests to vm 14:42:26 ok, good to know 14:42:55 most important is, it already works :) 14:43:02 yeah :D 14:43:45 grand work :) 14:44:04 dkrol_: how do you feel? are there any ad hoc or ducktaped pieces? 14:44:31 Hmm 14:44:55 Cloudinit was nacessery 14:45:17 And default values for the image 14:46:04 I see 14:46:56 Probably there is some space for improvements :) 14:47:30 Let's try to merge it as soon as possible 14:47:45 To have some progress finally 14:47:51 ok, I will try review this change once I will find more time slots 14:48:18 ok guys, any out of agenda topics? 14:48:50 Not from my side 14:49:22 it's fine 14:49:29 thanks for participating 14:49:39 see you next week 14:49:41 o/ 14:49:46 Thanks and see you next week 14:49:46 Thanks, take care 14:49:53 bye 14:49:57 #endmeeting