14:00:48 <dkrol> #startmeeting trove
14:00:49 <openstack> Meeting started Wed Oct 24 14:00:48 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:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:52 <openstack> The meeting name has been set to 'trove'
14:01:09 <dkrol> it is time for trove weekly meeting
14:01:19 <dkrol> #topic roll call
14:01:28 <dkrol> let's wait for others
14:01:42 <mpiwowarczy> o/
14:01:53 <dkrol> hello
14:05:03 <bzurkowski_> Hello
14:05:13 <dkrol> bzurkowski_: Hello
14:05:16 <mpiwowarczy> bzurkowski_: hi
14:06:12 <dkrol> let's start with the first topic
14:06:17 <dkrol> #topic Python 3 first support
14:06:38 <dkrol> mpiwowarczy: can you say about any news ?
14:07:00 <mpiwowarczy> so.. I have update status on etherpad: https://etherpad.openstack.org/p/trove-python-3
14:07:06 <cezary_zukowski> Hi guys
14:07:18 <bzurkowski_> cezary_zukowski: Hi :)
14:07:19 <dkrol> cezary_zukowski: Hi
14:07:25 <mpiwowarczy> but still working on core issue with executing tests in trove project
14:07:53 <mpiwowarczy> there appears some dependency in trove-client project and I need to reproduce this issue in local env
14:08:17 <mpiwowarczy> it is almost done but needs a little bit more time
14:08:25 <dkrol> with which project do you have issues ?
14:09:39 <mpiwowarczy> trove uses client from openstack/python-troveclient repository
14:10:01 <mpiwowarczy> and there appears some uncompatibilities with python3
14:10:03 <bzurkowski_> mpiwowarczy: Can we complete Python 3 goal for any Trove project until OpenStack Summit?
14:10:28 <mpiwowarczy> bzurkowski_: for trove? hope so :)
14:10:45 <bzurkowski_> Yes, for Trove
14:11:02 <mpiwowarczy> as I sad, it is almost done
14:11:08 <mpiwowarczy> dont see any serious issues
14:11:23 <dkrol> this would be great
14:11:34 <bzurkowski_> Great!
14:11:47 <mpiwowarczy> I will focus on that
14:11:51 <mpiwowarczy> :)
14:11:56 <dkrol> fingers crossed :)
14:13:16 <dkrol> ok, we can move to the next topic
14:13:20 <dkrol> #topic Trovestack redesign
14:14:09 <dkrol> I'm still working on image building
14:14:38 <dkrol> right now I have the following errors in trovestack int-tests:
14:14:40 <dkrol> test_make_sure_mysql_is_running_after_resize                FAIL
14:14:48 <dkrol> Make sure MySQL is accessible before restarting.            FAIL
14:14:54 <dkrol> Restart MySQL via the REST API successfully when MySQL is down.FAIL
14:15:01 <dkrol> test_correctly_started_replication                          ERROR
14:15:07 <dkrol> test_slave_user_exists                                      ERROR
14:15:15 <dkrol> test_detach_replica                                         ERROR
14:15:21 <dkrol> Tests the mgmt datastore version list method.               FAIL
14:15:41 <dkrol> and I can reproduce on my local deployment
14:16:06 <dkrol> however I don't have any clue what is happening for now
14:17:10 <dkrol> that is all from my side regarding this topic
14:17:22 <dkrol> we can move to the next topic on our agenda for today
14:18:01 <dkrol> #topic Documentation
14:18:13 <dkrol> cezary_zukowski: do you have any news for us ? :)
14:21:00 <bzurkowski_> I guess he may have problems with communication after he went mobile
14:21:13 <dkrol> aaah
14:21:16 <dkrol> ok :/
14:21:37 <cezary_zukowski> dkrol: nothing to add as now, still waiting for access
14:21:47 <bzurkowski_> Here he is!
14:22:03 <dkrol> cezary_zukowski: what kind of access do you have in mind ?
14:22:41 <cezary_zukowski> To be ale to push to od trochę official repo
14:23:21 <dkrol> I see, but if you have something to push we can push it for you with you as a commiter or author
14:24:20 <cezary_zukowski> Super so we can do that
14:24:56 <dkrol> ok
14:25:48 <dkrol> so we can move to our last topic
14:25:58 <dkrol> #topic openstack summit
14:26:10 <dkrol> bzurkowski_: could you update us about the progress ?
14:28:18 <bzurkowski_> There is still a lot of work to be done for POC demonstration
14:29:15 <bzurkowski_> There were two minor changes in Trove repo
14:29:24 <bzurkowski_> https://review.openstack.org/#/c/608653/
14:29:26 <bzurkowski_> https://review.openstack.org/#/c/608640/
14:29:37 <dkrol> do you play to use google drive for presentations ?
14:29:42 <bzurkowski_> Former is already merged, second near merge
14:30:01 <bzurkowski_> And also one big change in Vitrage
14:30:02 <bzurkowski_> https://review.openstack.org/#/c/610027/
14:30:13 <bzurkowski_> Introducing Trove datasource into Vitrage entity graph and RCA
14:30:41 <bzurkowski_> dkrol: I don't know yet
14:31:02 <bzurkowski_> Probably we will prepare presentation in Google drive and than maybe export it to pptx
14:31:36 <dkrol> ok, I will try to start working on trove project update
14:32:09 <bzurkowski_> dkrol_: Any ideas on what we can include there?
14:32:24 <dkrol> also I will contact organizers to schedule a trove onboarding session
14:32:52 <cezary_zukowski> Cool
14:33:15 <dkrol> based on presentations from previous years I would include the following elements at least:
14:33:31 <dkrol> 1. trove functionality overview as an introduction
14:33:51 <dkrol> 2. stats regarding commits/reviews/etc for the rocky release
14:34:06 <dkrol> 3. main goals for stein
14:34:22 <dkrol> 4. main issues of the project
14:34:34 <bzurkowski_> Remember that we have only 20-minutes slot
14:34:42 <bzurkowski_> We must keep it short
14:34:54 <dkrol> so that would be it :)
14:35:03 <dkrol> trove functionality is about 2-3 slides
14:35:10 <dkrol> stats is 1 slide
14:35:24 <dkrol> maing goals are 2 slides
14:35:30 <dkrol> main issues is 1 slide :)
14:36:18 <dkrol> and I think we can talk about main points on these slides for about 4 minutes each
14:36:30 <dkrol> it should be enough
14:37:04 <dkrol> what do you think ?
14:37:35 <mpiwowarczy> what about future plans?
14:37:56 <dkrol> this would be in main goals for stein
14:39:28 <dkrol> I will prepare first draft and let you know next week
14:39:32 <bzurkowski_> dkrol: We should also describe what was done during Rocky release
14:39:41 <bzurkowski_> I guess it will be included in the second slide
14:40:21 <dkrol> bzurkowski_: good point ! yes, this should be a part of describing the rocky release
14:41:55 <dkrol> Project Onboarding gives attendees a chance to meet some of the project team and get to know the project. Attendees will learn about the project itself, the code structure/ overall architecture, etc, and places where contribution is needed. Attendees will also get to know some of the core contributors and other established community members. Ideally, attendees will know/ have completed the basics of contribution (i.e. irc,
14:42:05 <dkrol> this is a description about cinder onboarding
14:42:55 <dkrol> and it is basically the same for all components
14:43:35 <dkrol> and this session takes 40 minutes
14:44:48 <dkrol> so it is enough time to describe: functionality, architecture, code structure, tests, current goals (where contribution is needed), documentation
14:45:17 <dkrol> I think less slides and more coding/demo
14:45:31 <bzurkowski_> Great opportunity to attract new contributors and learn them how to develop Trove
14:45:39 <bzurkowski_> *teach
14:46:04 <cezary_zukowski> Yeah, agree
14:46:18 <dkrol> maybe we could prepare some bug to fix during the session ? :) to show how we run it, how tests are executed and how to push a change for review ?
14:47:13 <bzurkowski_> Demonstration of development workflow is a good idea
14:48:47 <dkrol> will you have a machine on which you can run devstack ?
14:48:50 <bzurkowski_> I like the idea of participating on onboarding session
14:49:04 <bzurkowski_> *in session
14:49:43 <bzurkowski_> dkrol: We should contact organizators of the event
14:50:16 <dkrol> about devstack ?
14:50:20 <bzurkowski_> Yes
14:50:39 <bzurkowski_> Or prepare offline demo
14:50:41 <dkrol> hmm... but it should be our machine so we control it :)
14:51:06 <bzurkowski_> dkrol: Assuming the machine has sufficient resources to run devstack ;)
14:51:35 <bzurkowski_> Eventually we could prepare screenshots and code snippets embeded into slides
14:51:39 <dkrol> yes, I'm running devstack on my 13inch asus with 16 gb of ram :)
14:52:54 <dkrol> does your macbook have 16 gb of ram ? :)
14:53:15 <bzurkowski_> No, it does not
14:53:19 <bzurkowski_> Only half of it :)
14:53:24 <dkrol> mmmm... :)
14:53:30 <bzurkowski_> Therefore I prefer offline demo :)
14:53:38 <dkrol> maybe we can prepare a machine on aws ?
14:53:51 <dkrol> offline demo is ok if necessary
14:54:07 <dkrol> but live demo can make much better impression
14:54:26 <bzurkowski_> Offline demo is safer, reliable and handy
14:55:09 <dkrol> yes, but there is no "wow" factor
14:55:31 <mpiwowarczy> agree :)
14:56:31 <bzurkowski_> Do you think we have enough time to push purchase of AWS resources through approval process and prepare stable devstack environment until summit?
14:56:44 <dkrol> but I understand we can have issues with resources
14:57:19 <dkrol> maybe przemek will have 16 gb of ram
14:57:28 <dkrol> anyway
14:57:36 <bzurkowski_> 16 GB is nothing for devstack
14:57:38 <dkrol> we need to have backup plan as well
14:57:45 <dkrol> for demo it is enough\
14:57:51 <mpiwowarczy> we can also use vpn and connect to PC in work
14:58:13 <dkrol> let's talk about it next time
14:58:16 <dkrol> our time is up
14:58:22 <dkrol> thanks for participating
14:58:29 <mpiwowarczy> thanks, bye
14:58:31 <dkrol> and see you next week
14:58:33 <bzurkowski_> Thanks, bye
14:58:42 <cezary_zukowski> Thx
14:58:44 <dkrol> #endmeeting