17:59:52 #startmeeting trove 17:59:53 Meeting started Wed Jun 3 17:59:52 2015 UTC and is due to finish in 60 minutes. The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:59:56 The meeting name has been set to 'trove' 18:00:20 Giving folks a couple of minutes to trickle in. 18:00:30 * amrith trickles in slowly 18:00:33 ☺/ 18:00:38 o/ 18:00:39 |o| \o/ --o-- 18:01:00 o/ 18:01:04 atomic77, what's the third one? 18:01:07 o/ 18:01:13 \o 18:01:20 i'm stretching :) 18:01:22 Meeting Agenda at: https://wiki.openstack.org/wiki/Meetings/TroveMeeting 18:01:26 #link https://wiki.openstack.org/wiki/Meetings/TroveMeeting 18:01:44 atomic77 i thought you were being an aeroplane 18:01:51 i m in 18:02:57 ashleighfarnham, haha actually now that i look at it again, it seems that way 18:03:06 o/ 18:03:10 o/ 18:03:10 Okay — Let's get started. 18:03:12 o---- 18:03:24 #topic Trove Pulse Update 18:03:34 #link https://etherpad.openstack.org/p/trove-pulse-update 18:05:05 Looks like we're making good process on getting open specs reviewed for liberty — and they are moving. :) 18:06:35 Any questions / concerns with reviews? 18:06:44 o/ 18:06:51 trying to formulate one 18:06:56 there seems to be a lot of activity 18:07:03 I'm trying to get a sense for progress 18:07:55 So, what metric would you use for progress as opposed to activity? 18:08:10 I'm not sure 18:08:16 let me take an action item on that 18:08:29 no point having everyone watch me think (hint: it is boring, like paint drying) 18:08:45 I'm specifically looking at the "Changes merged in the last 7 days" for that. 18:09:05 yeah, 10 seems to be a fairly good number there 18:09:31 We're at 10 — which seems to be par for most weeks. 18:09:34 double the reviews (106 vs 213), double the reviewers (12 vs 21), yet total open reviews is about the same. 18:10:11 more substantial / controversial changes might explain that. 18:10:52 I don't know that we've had anything really that controvertial in the last week 18:11:09 Reviews come and go. There is a ton of -1 patchsets with no progress. 18:11:32 pmalik, may have the answer. 18:11:43 It just happens the net number of open reviews is roughly constant. 18:12:12 Also because the number of stale reviews is so large. 18:13:54 pmalik: There's only so much time folks have for updating patchsets — If a -1 patchset isn't updated / replied to it's going to stay that way. Not sure what the solution here is. 18:14:42 expire patchsets would be the answer 18:15:19 yup, the auto-job to abandon -1 patches does not works any more ... and the queue keeps up growing 18:15:51 #action SlickNik to follow up with Infra folks to see what happened to the auto-abandon job. 18:16:20 Okay, I'll take that action item. 18:17:05 Anything else before we move on? 18:17:07 So, the key seems to be the 1st quartile time 18:17:14 it is now 6 days 18:17:18 a week ago it was 11 hours. 18:17:40 Oddly enough, the 3rd quartile was 18 days but in a week it has become 35 days. 18:17:46 * SlickNik thinks there's only one more item on the agenda — so it's okay to spend a few more minutes on this. 18:18:33 what do you mean by 1st quartile time? 18:18:41 all set (for now). don't want to make everyone spend a lot of time on this. 18:18:48 amrith - a week ago it was 11 days, no? 18:18:50 better to think about it and post more details later. 18:19:01 dougshelley66, that was average. 18:19:08 10d 21h 18:19:35 Also there have been a couple of really old changes that were restored lately - that could be messing with the average times. 18:20:02 Okay, let's move on. 18:21:04 #topic Next steps on protected instance review. 18:21:10 moving right along ... 18:21:17 was wondering what we want to do with this 18:21:24 a couple of you have reviewed it (thanks). 18:21:34 shayneburgess_, has some good points 18:21:38 how does this mess with the spec from Bruno 18:21:45 but not something that gates our pushing it forward to Nova. 18:21:49 s/mess/mesh 18:21:53 then (as dougshelley66 points out) there's a note from Bruno 18:22:02 I think the next step is to take the discussion to the mailing list and have folks from other projects chime in. 18:22:09 I agree SlickNik 18:22:20 The question is this ... 18:22:34 I think Bruno's note is more prescriptive and a bit more opinionated than I like 18:22:38 but that's my point of view 18:22:46 * amrith realizes that some people are saying Bruno who? 18:23:02 Bruno is the guy from CatalystIT 18:23:02 why didn't he send that to the ML 18:23:20 Well, we've been pestering him 18:23:26 and he sent us a reply to an email thread. 18:23:41 I would like to take something (TBD) and hurl it at the ML today. 18:23:57 it has been two weeks since Vancouver and there are only 24 before the next release. 18:24:09 so if we want stuff to happen in Liberty, time is our enemy 18:24:13 amrith: I basically sent him a reply to the same effect. 18:24:22 I'd really like to get something on the ML asap 18:24:42 I'm sure that this will generate enough discussion once it's on the ML as well. 18:25:01 so, may I post my notes and a link to the trove review to the ML 18:25:08 that way, we get feedback in a structured way 18:25:36 rather than having to read the mail threads and de-multiplex them and the various ratholes that could result 18:25:42 Hi all 18:26:17 amrith: I'm good with that. 18:26:21 hi tobe 18:26:41 thx SlickNik ... hi tobe, go ahead. 18:27:38 Thansk amrith SlickNik . I'm a little late :) 18:28:25 Okay, anything more on this topic? 18:29:11 not for me, thanks all. 18:29:19 tobe: not a problem — better late than never :) 18:29:44 #topic Open Discussion 18:30:21 Anything for open discussion? 18:30:39 I have one and this is regarding nosql datastores 18:31:15 specifically related to database and user management functionalities we have specs for some of those datastores. 18:31:54 johnma: sure, go for it. 18:32:35 I remember last time (during Kilo) why none of these datastores implemented th database and user management functionalities 18:33:59 I dont remember the exact reason given for it but now with alot of specs to implement this for some nosql datastores, i am wondering whether this becomes a requirement to move them from experiemental to stable 18:34:53 I think the reason given then was there wasnt a need since these datastores already provided a UI for these functionalities 18:35:25 * amrith doesn't remember that explanation 18:35:48 johnma: user / db management have been considered API extensions, and I don't think this is currently a requirement for the move from experimental to stable. 18:35:49 johma I think experimental -> stable is more about the amount of testing (+ some minimal functionality) 18:35:51 also don't see the rationale for that; mysql also provides a UI for this. 18:36:03 i am trying to find the link to that 18:36:12 hi everyone 18:36:40 hi cp16net 18:36:46 hey 18:36:53 hi cp16net 18:37:23 :-D 18:37:37 * cp16net forgot the time of the meeting... 18:37:55 cp16net, can't you come up with something more original? 18:37:57 johnma: Okay — maybe this is something I can take offline with you and help clarify further. 18:38:04 That's fine, you are forgiven, you are the "new guy". 18:38:11 Welcome to Trove ;) 18:38:21 johnma: You mean providing a web UI to execute sql or other nosql operations, right? 18:38:45 amrith: you are going to have to help me understand what "trove" is since i'm the new guy 18:38:53 yeah, in the mean time I will try to find the link. I dont have any problems with implementing these features. Was just curious if something changed from last time in terms of implementing these features. Thats all 18:39:22 johnma, I think it has always been an issue of prioritization. 18:39:35 as people start using a datastore, they will progress along with the capabilities. 18:39:44 that makes sense to me. 18:39:45 initially a single instance is fine, later you need more capabilities. 18:39:50 one of the benefits of trove 18:39:53 is that it simplifies usage 18:40:00 giving you one interface to a plurality of databases. 18:40:11 the fact that you can create a user on mysql the same way you would on ibm/db2 18:40:15 is a great simplicity. 18:40:19 and people want that. 18:40:19 johnma: I think the user / db mgmt features are being added because folks are asking for them as datastores evolve. it's not born out of experimental -> stable graduation requirements. 18:40:28 but it won't be the thing that makes them want to use a particular datastore. 18:40:35 hence the rationale for the sequence. 18:40:47 ok, that sounds good to me 18:40:56 sorry if it wasn't clear 18:41:12 but if you'd like to clarify it in the document that describes the phases, that would be welcome. 18:41:35 Sounds good. 18:41:38 thanks Amrith & SlickNik. 18:41:45 Any other items for open discussion? 18:41:59 cp16net, I'm writing a book about it. Will send you a copy. It will help you get "up to speed". 18:42:16 . 18:42:26 #endmeeting