18:00:09 #startmeeting trove 18:00:10 Meeting started Wed Jun 8 18:00:09 2016 UTC and is due to finish in 60 minutes. The chair is amrith. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:14 The meeting name has been set to 'trove' 18:01:27 hello 18:01:35 hey craig 18:01:37 Hi 18:01:44 was getting a bit lonely here 18:01:51 hi peterstac-m 18:01:55 what's the -m? 18:01:57 \_o_/ 18:02:19 Mobile 18:02:22 ah 18:03:14 courtesy reminder for johnma, SlickNik 18:03:27 o/ 18:03:32 ? 18:03:37 hey folks! 18:03:37 ?/ 18:03:51 let's get started; hi SlickNik 18:03:54 we have a quorum 18:04:16 I spoke with johnma this morning, she said she'd be here; maybe got tied up in something 18:04:23 Here's the agenda 18:04:29 #agenda https://wiki.openstack.org/wiki/Meetings/TroveMeeting 18:04:38 #topic Action items from last week 18:04:43 I don't have any 18:04:54 We didn't have a meeting last week 18:05:02 and the week before that we finished all our action items 18:05:10 so unless someone else has something, ... 18:05:57 moving on ... 18:06:00 #topic Trove pulse update 18:06:08 #link http://bit.ly/1VQyg00 18:06:51 the pace has slowed a bit 18:07:10 but we didn't get many new changes last week 18:07:18 and the queue growth was small 18:07:28 the backlog is, however, quite significant 18:08:13 hmm, I forgot to fill some columns; I'll fix that later today 18:08:21 the last 3 columns 18:09:26 there ... fixed that 18:10:06 also https://gist.github.com/amrith/3454ca929bf58d783e00c70746e7c5f0 18:10:29 I fell a bit behind this week, have to pick up again this week 18:10:45 anyone have anything else to add ... 18:11:18 does the open reviews signify the backlog? 18:11:37 looking 18:12:12 it is column N 18:12:18 which is the number of reviews in backlog 18:12:20 johnma, yes 18:12:50 ok, thanks amrith. I need to pick up the pace as well. will do that 18:13:04 thanks johnma we all have to 18:13:18 ++ Looks like we all need to pick up the pace on reviews. :) 18:13:24 yup 18:13:36 so, with that 18:13:42 moving on to 18:13:46 #topic Announcements 18:14:02 So, the first is something that isn't on the agenda. 18:14:11 Last week (June 2nd I believe) 18:14:17 was the deadline for Newton 1 release 18:14:21 it is a drop for a beta 18:14:26 I missed that drop 18:14:56 i misread the email from dhellmann and interpreted the text in the release schedule page to imply that we could release it with our proposed freeze of specs 18:14:58 apparently not 18:15:13 So, I will keep a closer eye on that and make sure we do the newton b2 drop 18:15:33 we are a release:cycle-with-milestones project 18:15:39 and should've done a June 2 drop 18:15:46 anyway, newton-2 is July 12-14 18:15:50 I'll make sure to do that 18:16:06 The other is something that I did put on the agenda 18:16:22 Jun 13-17, R-16 is the trove spec proposal deadline 18:16:35 that's next week 18:16:46 this is the proposal deadline, not the review and close deadline 18:16:47 #link http://releases.openstack.org/newton/schedule.html 18:16:52 thanks SlickNik 18:16:54 should've done that 18:17:07 I'm refering to http://releases.openstack.org/newton/schedule.html#n-trove-spec-prop 18:17:27 and the one after that is R-12 which has 18:17:34 #link http://releases.openstack.org/newton/schedule.html#n-2 18:17:41 #link http://releases.openstack.org/newton/schedule.html#n-trove-spec-freeze 18:17:56 is there anyone who has to still put in a spec for something? 18:18:08 I have 2 specs amrith 18:18:21 1 will go in today 18:18:31 thx johnma what are these for? 18:18:48 both are pretty straight forward - db2 online backups & configuration management 18:18:56 cool, thanks! 18:19:10 I may/ may not do one for couchdb clustering - 2.0 has been released which has clustering support 18:19:18 but 2 for sure 18:19:33 ok, thanks. 18:19:35 anyone else? 18:19:59 Nothing else from my side. 18:20:16 nope 18:20:29 before moving on to the next thing; I'll assume that everyone saw the email from vkmc yesterday. 18:20:31 #link http://markmail.org/thread/ddobuj25eitqweyq 18:20:50 we should therefore figure out what we want to do with RPC API Versioning 18:21:09 as the upgrade issue(s) are something that would be good to deal with 18:22:07 thx SlickNik cp16net 18:22:18 dougshelley66, peterstac-m any other specs that you know of that are still to come? 18:22:51 I'd like to propose that at next week's meeting we try and get a firm handle on the actual things we feel we can get into Newton 18:23:03 factoring new features + bug fixes + backlog 18:23:25 so could everyone please think about that and be prepared to discuss at next weeks meeting 18:23:39 #action prepare for next weeks meeting; things that we can get into Newton 18:25:18 will do 18:25:21 ok, I'll follow up with both of them offline 18:25:38 I don't think I have anything else 18:26:02 amrith ^^^ specs that is 18:26:15 ok 18:26:15 thx 18:26:27 so, moving along (unless anyone else has other announcements) 18:26:53 vkmc: thanks for your contributions to trove :) 18:27:10 +1 18:27:42 #topic open discussion 18:27:44 ++a big thanks to vkmc 18:28:19 vkmc — it's been a pleasure and an honor! We will miss you :) 18:29:05 amrith: i have a small comment about the utc timezone patch you have 18:29:07 vkmc Yes, thanks!! 18:29:36 cp16net, go ahead 18:29:52 * amrith hands baton to cp16net 18:30:20 i just want to make sure you and others know why we use the 'Z' at the end of the times in the api responses 18:30:23 and yes, thanks vkmc for your contribution to trove 18:30:39 ha 18:30:46 sorry 18:30:48 the Z 18:31:08 i meant to say - what is the issue with the "Z" 18:31:09 this was a requirement that horizon needed to make sure to have a standard time format so that it could display these times 18:31:21 yes I think it would be good for everyone to understand that 18:31:33 Z is Zulu time 18:31:42 and when referencing times UTC 18:31:43 right so that is being deprecated? 18:31:51 it is often the case that you refer to it as 18:32:01 zulu/gmt/any other strange name you want to call the +/-0 timezone 18:32:03 YYYY-MM-DDTHH:MM:SS+00:00 18:32:16 or YYYY-MM-DDTHH:MM:SSZ 18:32:23 Z is ~ +00:00 18:32:33 Z ~ +00 18:32:42 it is NOT the same as GMT 18:32:44 i wasnt sure from reading over the change if that was removed or now 18:32:48 s/now/not/ 18:32:50 GMT has a daylight savings adjustment 18:32:57 UTC and Z do not 18:33:09 amrith: oh i didnt realize that.. but that makes sense. 18:33:12 So strictly speaking, GMT (Greenwich Mean Time) does have a DST 18:34:04 amrith: so you werent changing that in the patch right? 18:34:06 so Historically, pre 1972, GMT had no DST 18:34:28 After 1972, GMT ~ does have a daylight savings adjustment and UTC does not 18:34:35 TO answer your specific question cp16net 18:34:38 YES, I retain the Z 18:34:59 i assume if the example generating tests are still running then it would not be affected :) 18:35:09 See: https://review.openstack.org/#/c/326655/2/trove/common/timeutils.py 18:35:11 ok 18:35:11 line 79 18:35:20 Yes, the example tests work 18:35:29 also there are new unit tests proposed that ensure taht we retain the Z 18:35:38 See: https://review.openstack.org/#/c/326655/2/trove/tests/unittests/common/test_timeutils.py 18:36:10 k 18:36:12 sounds good 18:36:18 thats the only comment i wanted to make 18:36:25 cp16net, would you like me to add a clarification about that? 18:38:34 cp16net, ^^ 18:39:01 i dont think so 18:39:14 unless you think it warrants a clarifications 18:39:20 ok, does it look good otherwise? 18:39:52 i just remember discussions that required the Z at the end wanted to share that info 18:39:56 i think so 18:40:35 I have to rebase anyway (there's now a merge conflict) so I'll add a blurb about it in the commit message and near the new code. 18:40:38 thx cp16net 18:40:45 np 18:41:20 SlickNik, did you see the comments from kevinfox re: ssh and superconductor? 18:42:33 I saw that he had replied, but haven't had a chance to look into it as yet. 18:42:57 Actually looking into it as we speak :) 18:43:41 maybe we can discuss later 18:44:52 that's all I had for the meeting 18:44:58 anyone have anything else ... 18:47:21 ... a motion to adjourn? ... 18:47:38 I think so 18:47:45 #endmeeting