18:00:37 <johnma> #startmeeting trove
18:00:38 <openstack> Meeting started Wed May 17 18:00:37 2017 UTC and is due to finish in 60 minutes.  The chair is johnma. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:41 <openstack> The meeting name has been set to 'trove'
18:00:45 <trevormc> o/
18:01:06 <songjian> o/
18:01:19 <johnma> hello trevormc, songjian
18:01:31 <trevormc> is anyone else here for the trove meeting?
18:03:05 <johnma> I need to remind the IBM folks about this meeting time. I am not sure they know
18:04:00 <johnma> will give it another minute and we can get started. We can atleast go through the agenda quickly and add notes to it at the end of the meeting so that we have something to loop back to next week
18:04:02 <trevormc> smaztek mention he had conflicts
18:04:33 <johnma> right, we will update the agenda with any action items so that folks who are not on this call can take a look
18:04:49 <johnma> ok , so let's get started then
18:04:54 <johnma> #agenda https://wiki.openstack.org/wiki/Meetings/TroveMeeting
18:05:44 <johnma> The first one is regarding coming up with a new time for Trove meeting. Unfortunately with just the 3 of us we can't come to a decision.
18:06:43 <johnma> songjian, since you were not there in Boston last week, will update you on this one. There are a number of new contributors who would like to contribute to Trove and they are in different timezones - Paris, Germany, UK, China, US
18:07:18 <songjian> thanks
18:07:28 <johnma> so there was a proposal to come up with  a different time for the Trove meeting
18:07:30 <songjian> this really a nice topic
18:07:42 <johnma> do you have any preferences
18:08:09 <johnma> is wednesday still a good day?
18:08:32 <johnma> whatabout you trevormc. Not sure if we came up with any date/time last week?
18:08:34 <kumarmn> yes
18:08:51 <trevormc> johnma, im flexible
18:09:04 <kumarmn> We came up with Wednesday
18:09:05 <trevormc> so pretty much anytime that fits in the CT work week
18:09:09 <johnma> Hi kumarmn
18:09:38 <trevormc> wednesday 9am I think was the agreement from the meeting, I can watch the video lol
18:09:46 <johnma> yeah, same with me. Wednesday works for me as well, anytime
18:10:17 <songjian> Look at the time of other contributors to balance it. Beijing here is now 2 o'clock. If I can be 2 hours ahead of time would be better. But still want to balance the time of other people
18:10:40 <johnma> ok, lets put that time under that agenda time and we can confirm with Amrith
18:11:09 <kumarmn> @songjian: Our proposal was 4 hours earlier
18:11:53 <trevormc> 10am central was the decided time
18:12:25 <trevormc> 23:50 in https://youtu.be/g8tKXn_Axhs?t=23m50s
18:12:49 <johnma> very nice trevormc. Thanks for digging that :)
18:13:02 <kumarmn> ok, so three hours earlier
18:14:00 <johnma> hope that time is ok with songjian
18:14:11 <songjian> Three hours ahead of time, no better than this
18:14:43 <trevormc> We can shoot for something later instead
18:16:00 <johnma> so 10am CT is about 11pm in China I believe, not sure if I got the math right
18:16:31 <johnma> so songjian can you update the wiki and add your preferences there
18:16:33 <trevormc> looks like the UK and china are opposities
18:17:02 <johnma> and we can try to resolve it over there
18:17:17 <trevormc> 1100-1200 UTC looks like the best time to meet
18:17:18 <johnma> I would like to move on the next agenda item
18:17:31 <trevormc> which is 6am-7am central lol
18:17:37 <johnma> that would be what time central?
18:17:38 <songjian> ok,I'll update it
18:18:11 <trevormc> ok, how about this, we alternate team meetings
18:18:18 <johnma> that's quite early for us and even earlier for those in eastern timezone
18:18:56 <trevormc> beijing, paris, china only have 11-1300 UTC where someon is not sleeping
18:19:06 <trevormc> so besides that, we need to alternate.
18:20:02 <trevormc> paris and beijing can meet without the US during UTC 700-1200
18:20:51 <johnma> I am just wondering how many people actually plan on attending these meetings. I dont mind 6-7am as long as folks from these different timezones attend these meetings
18:21:06 <trevormc> then 1500-1800 UTC for the other times... I like using this website https://www.worldtimebuddy.com/
18:21:18 <trevormc> johnma, yeah I agree.
18:21:19 <johnma> anyways lets add these comments in the agenda. trevormc,can you update the wiki with these suggestions
18:21:39 <trevormc> yes I will.
18:21:50 <johnma> thanks trevormc
18:21:57 <johnma> moving on to the next topic in the agenda
18:23:42 <johnma> 2) Trove reboot - This was about providing a new/renewed focus to Trove project and improving code contributions/ reviews, going through features to work on for this release, addressing technical debt, etc
18:25:12 <trevormc> excellent topic! I was thinking about starting with the installation documentation, for those who can't install the service. We have bugs filed at the moment and it kind of feels like a silo of knowledge on how trovestack runs
18:25:14 <johnma> so we discussed during last week's summit at Boston that it would be nice to have some sort of the virtual meetup where all of us planning to contribute to the project this release could get together and hash out the list of things we wanted to work on
18:25:50 <trevormc> - oh right, lets focus on the meeting time again. sorry
18:26:31 <trevormc> does anyone have thoughts on the virtual meetings?
18:26:42 <trevormc> s/meetings/meeting
18:26:47 <johnma> trevormc: I agree with you . I think this is the best chance for us to update our docs if we really want to call it a reboot.
18:27:15 <trevormc> - thanks a little off topic but I have a patch im trying to push up lol, facing some auth issues atm
18:27:53 <trevormc> I think we will have the same problem about the trove reboot as we will with the weekly meetings. Given this is a one time thing, I think we can wake up early for this.
18:28:09 <trevormc> UTC 1200?
18:29:08 <trevormc> and amrith said we should schedule the meeting for this week or next.
18:29:10 <johnma> again I think we need to come up with a date and time that works for those wishing to contribute. So as a starting point, let us put some dates in there that works for us. I think there is a tool - like a survey tool which we can use to get the time and dates. Amrith should know more about this. We have used it before
18:29:26 <johnma> right
18:29:54 <johnma> I will send a note to amrith about this and we can send out a mail to the mailing list
18:30:24 <trevormc> http://doodle.com/ works nicely
18:30:32 <johnma> #action johnma to talk to amrith about scheduling a day/time for Trove reboot
18:30:44 <johnma> yes that's what I believe we used last time
18:31:33 <johnma> great, thanks trevormc. Will add that to the agenda as well. We need to schedule a time slot for this week/next
18:32:07 <trevormc> does this work? https://doodle.com/poll/s36ywdz5mfwqkdvu
18:32:34 <trevormc> ahh i gotta add times somehow lol
18:33:33 <johnma> worked for me. You should see my updates.
18:33:46 <johnma> yes you need to add times. Right now it shows all day
18:34:35 <trevormc> ok well ill fix this up in the meantime we can talk about other things
18:35:14 <johnma> thats all I had about that topic. Lets add this link to the meeting agenda
18:35:21 <johnma> moving on
18:35:33 <johnma> #topic Open Discussion
18:35:45 <johnma> trevormc: you had something to share
18:36:06 <trevormc> Should we prioritize any of the changes in the backlog? https://etherpad.openstack.org/p/trove-backlog-changes
18:36:19 <trevormc> ^ these are changes made by employees that no longer contribute
18:36:29 <trevormc> or at least not as much as they were.
18:36:52 <trevormc> I just wanted to ask, does anyone have interest in these?
18:37:24 <trevormc> because if not, we can just forget about them and move on. I for one would like to review the datstore specific API controllers patch by pmalik
18:37:33 <trevormc> rpittau also commented the same.
18:37:53 <trevormc> https://review.openstack.org/#/c/406395/
18:38:02 <kumarmn> The MySQL 5.7 not starting after restore seems important.
18:38:30 <trevormc> kumarmn yes these are worthy changes but how worthy is the question.
18:38:54 <trevormc> and if we choose to move any forward, which ones and why
18:38:54 <johnma> yes kumarmn. we should fix that one
18:39:24 <johnma> trevormc: I think this would be a good topic to discuss during the Reboot meetup
18:40:05 <trevormc> ok, so everyone just review the content and be prepared to talk about which ones you would like to review
18:40:18 <johnma> there are alot of patches sitting out there which we need to go through and prioritize. I am not sure how relevant some of the topics in that etherpad are anymore
18:40:47 <johnma> some of the things I think we discussed last week which we need to work on this release are:
18:41:21 <johnma> 1) support the latest version of datastores - like mysql 5.7, mongo 3. 4, etc on ubuntu-xenial
18:42:01 <johnma> 2) we need more contributors to work on the trove dashboard portion - to add new features that exist in the command line but not the UI
18:42:24 <johnma> 3) documentation of course
18:42:52 <kumarmn> 4) Resolve gate issues
18:43:03 <johnma> 4) update the tempest plugin - add new tests
18:43:17 <johnma> yes kumarmn
18:43:54 <trevormc> more specifically, identify gate issues.
18:44:00 <johnma> so trevormc, I think we can add these items into the etherpad as the items we want to discuss during the reboot meetup
18:44:27 <trevormc> ok, ill create a seperate one.
18:45:06 <johnma> is that going to be a seperate etherpad?
18:45:27 <johnma> I think we can start a new etherpad for Trove-Reboot and can link the backlog etherpad in there
18:45:34 <trevormc> https://etherpad.openstack.org/p/trove-reboot
18:46:01 <johnma> cool, thanks trevormc
18:46:27 <johnma> so, thats all I had. anyone have anything else to discuss.
18:48:04 <trevormc> I also added the ptg topics https://etherpad.openstack.org/p/trove-pike-ptg-topics
18:48:14 <trevormc> - not sure if those went anywhere
18:48:54 <johnma> that sounds good trevormc. It is a good chance to go over those topics as well.
18:49:01 <trevormc> umm just please review !
18:49:25 <trevormc> I want to incourage 0 comments that inquire about more details on a change
18:50:13 <trevormc> encourage*
18:50:34 <trevormc> my reasoning is that we have new contributors learning about the code, and most of us probably have the same question.
18:51:23 <johnma> yes, agree
18:51:32 <trevormc> I just don't see anyone reviewing lately, I was going through the reviews with no updates for 3-4 weeks
18:51:43 <trevormc> ^ those are the most active ones lol
18:52:06 <trevormc> https://review.openstack.org/#/projects/openstack/trove,dashboards/important-changes:review-inbox-dashboard
18:52:47 <trevormc> is the dashboard I use, I click on the middle header that says passed jenkins no feedback and it gives me a link that requires auth
18:52:48 <trevormc> https://review.openstack.org/#/q/status:open+NOT+label:Code-Review%253E%253D0%252Cself+label:Verified%253E%253D1%252Cjenkins+NOT+label:Code-Review%253C%253D-1+NOT+label:Workflow%253C%253D-1+project:openstack/trove
18:53:43 <trevormc> so those are the changes we should review just to get our feet wet in the code, some are wayward changes and we can pass on those but for the most part we should spend sometime giving some kind of feedback.
18:54:20 <trevormc> review bandwidth is a problem, I know, but the amount of active reviews reflect that so it shouldnt be too much of an ask,
18:54:35 <kumarmn> ok, I can start looking at some of them
18:55:15 <trevormc> cool! its important to show trove has some kind of heart beat left lol
18:55:44 <trevormc> - i personally got turned away because of the lack of reviews. I had a list of changes with no feedback on.
18:55:47 <johnma> yes, i agree. We need to become more active in doing reviews. There was a sharp decrease in the number of reviews last release and we need to get up to speed in this release and get the momentum going
18:56:52 <johnma> alright, anything else?
18:57:02 <johnma> we are almost at the top of the hour.
18:57:12 <trevormc> yeah I think I said enough :)
18:57:20 <songjian> Well, we seem to need more review feedback
18:57:33 <johnma> :) , very good feedback and thoughts trevormc. Appreciate it
18:57:48 <trevormc> shamless plug for OSC changes https://review.openstack.org/#/q/status:open+project:openstack/python-troveclient+branch:master+topic:bp/trove-support-in-python-openstackclient
18:58:06 <trevormc> - should be pretty easy to test given its just the client.
18:58:20 <johnma> yes songjian. I think that is going to a a renewed focus this release. It was encouraging to see the renewed interest in the project at the Boston Summit
18:58:27 <trevormc> but i should update those, just need people to let me know they are going to review em.
18:59:00 <trevormc> songjian, I feel your concern as well
18:59:05 <johnma> trevormc, please add me as a reviewer. Songjian, please add me as a reviewer to the ones that you would like me to review
18:59:29 <johnma> that way its easier for me to figure out the ones that are ready for review
18:59:38 <trevormc> ok that makes sense
18:59:50 <trevormc> thats what the workflow -1 is for
19:00:05 <trevormc> - i guess we can move into the main channel if we want to keep discussinong
19:00:15 <johnma> well , there are some that have been sitting out there for some time
19:00:48 <songjian> Well, I will clean up some unnecessary patches, leave some useful, and then please review
19:00:49 <johnma> yes, sounds good. So let's call it a wrap for this week's meeting. Thank you all for joining today's meeting and the great discussions.
19:01:44 <johnma> yes songjian, please add me as a reviewer - mariamj@us.ibm.com
19:01:57 <songjian> ok
19:02:02 <johnma> thanks guys and have a good rest of the day.
19:02:09 <johnma> #endmeeting