14:10:19 #startmeeting glance 14:10:20 Meeting started Thu Jul 17 14:10:19 2014 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:10:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:10:23 The meeting name has been set to 'glance' 14:10:36 roll call! 14:10:41 o/ 14:10:43 haha o/ 14:10:46 o/ 14:10:46 o/ 14:10:47 hi 14:10:51 o/ 14:11:14 #topic bugfixing days 14:11:36 sorry i wasn't available the past 2 days, any comments on how things went? 14:11:45 (the agenda is not up to date) 14:12:14 we fixed some bugs, now we have 260 bugs there 14:12:36 some triage has been done as well 14:12:43 but we tagged some bugs, they probably can be closed safely 14:12:48 and tagging of bugs 14:12:54 and reviews 14:13:01 which actually merged L=:) 14:13:41 sounds good, thanks for all your work (to everyone who participated) 14:14:26 i think we need to discuss mid-cycle meetup, but that may take some time, anyone got something they'd like to discuss first? 14:14:38 my concerns is that , seems there are some frozen "in-progress" items there, most of them have higher importance 14:14:42 I think we need to focus on reviews now, because our review queue is getting bigger and bigger 14:14:52 indeed 14:15:00 o/ 14:15:38 at some point, we had a review day, do we need to do that again? 14:15:46 +1 14:16:01 so probably we can send a mail to raise a asking, and take and fix them as needed 14:16:12 ad-hoc review requests many times lead to semi-pending MPs 14:16:13 +1 for review day 14:16:26 #action get markwash to schedule a review day 14:16:56 hi guys=) 14:17:48 d0ugal, boris-42: hi 14:18:01 anything else before mid-cycle agenda discussion? 14:18:27 Hi! not from me :) 14:19:24 #topic mid-cycle meet-up 14:19:41 #link https://etherpad.openstack.org/p/glance-juno-mid-cycle-meeting 14:20:05 arnaud has added directions to the etherpad 14:20:22 still figuring out for remote people 14:20:39 I will give an update on that asap 14:20:56 zhiyan: you attended last meetup remotely, do you have any suggestions? 14:21:34 rosmaita: arnaud__ if it could, i think make a test before is necessary 14:21:39 to verify it works well 14:21:58 yes 14:22:49 I think being in a company and not an hotel, should make things a bit easier this time 14:23:00 +1 14:23:25 ping me when you want to test it, i can access it remotely as a verification/ 14:23:35 will do 14:23:38 so it looks like we have 9 topics now 14:23:40 today or tomorrow 14:23:41 cool 14:23:44 how do you typically organize the agenda? do you just vote at the beginning of the first day? 14:23:57 thanks arnaud__ 14:23:59 timing wise, that is. 14:24:01 np! 14:24:13 last time, markwash just assigned times 14:24:34 but looking at the topics, some will require more time than others 14:24:51 it also seems we will be very busy 14:25:09 and i personally am in favor of maybe revisiting some topics at the end after we've had time to think and discuss 14:25:25 arnaud__: do you think there is too much on the agenda now? 14:25:27 should we have an individual etherpads for each topic (possible re-using old ones) ? 14:25:46 +1 nikhil___ 14:25:55 nikhil___: +1 14:26:02 can the v1/v2 performance one be removed? zhiyan pushed up a couple of fixes 14:26:11 :) 14:26:14 good point 14:26:21 boris-42: any inputs on that? 14:26:42 nikhil___ where?) 14:26:44 nikhil___ reading 14:26:46 rosmaita: arnaud__ : may be then each topic leader would create one or do you all need a volunteer? 14:26:50 looks like it already got removed! 14:27:05 so 8 topics 14:27:09 ify, those only covered "image-list" case, but others probably could be handled case by case. 14:27:12 nikhil___ guys btw sorry for interrupting but 14:27:21 what about profiling stuff?) 14:27:31 it can really reduce a lot of time 14:27:37 actually 14:27:39 I was thinking 14:27:49 and it's quite ready 14:27:50 what about a demo of the profiling stuff with glance? 14:27:51 :) 14:27:59 arnaud__ in any time 14:28:05 +1 14:28:07 arnaud__ we can make hangout call 14:28:08 +1 14:28:17 arnaud__ and I'll share my screen 14:28:18 ok sounds boris-42 14:28:24 arnaud__ could we pick some date? 14:28:27 would it make sense to do it as part of glance diagnostics, or own session? 14:28:36 would it help if folks updated their items with a time estimate of what they'll need? Eg some folks may only need 1/2 a session 14:28:51 rosmaita I think it's enough to make hangout call=) 14:28:57 rosmaita and not spend time of summit for this 14:29:30 wow that was quick :-) 14:29:32 boris-42: that sounds good, maybe we should do it during glance meeting in 2 weeks? 14:29:43 rosmaita maybe faster? 14:29:49 mclaren cause patches are ready for merge 14:29:53 rosmaita ^ 14:30:21 boris-42: when would you like to do it? 14:30:32 rosmaita it depends on you guys 14:30:49 I have added an "Estimated time" section in the ether pad, if you are leader on a section please add how much time you think you need 14:31:04 nikhil___: you put time estimate of 1 session. Can we put in minutes? 14:31:08 s/on a section/of a topic 14:31:28 1 session = 40 minutes? 14:31:51 I think we should try to put in minutes 14:32:05 TravT: discussions usually tend to go a little over time 14:32:08 arnaud__: ^ 14:32:33 arnaud__: is the schedule not split into equal sized sessions? 14:32:57 initially it should 14:33:01 based on arrangements for lunch and other such breaks? 14:33:15 but I think we have sessions that need more and sessions that need less than 1hour... 14:33:37 first, does 9AM-6PM sounds reasonable? 14:34:09 9-5? 14:34:10 TravT: ok, put the session time even more explicitly :) 14:34:34 ok let's go with 5:30 14:34:37 then 14:34:39 ok :-) 14:35:10 does that "schedule" look ok? 14:35:18 do we need morning break? 14:35:35 I think we will need 10/15min breaks 14:35:50 in the middle of morning especially 14:35:51 :) 14:36:10 and evening too else the brain would be fried with too many ideas :) 14:36:19 10-10:10 14:36:25 well, the evening is wide-open 14:36:26 and jetlag :-) 14:36:41 oh, yeah. that 14:38:22 ok, so we could do 2 30 min sessions before first break, or is that unrealistic? 14:38:24 rosmaita: do we have a open-discuss section in this meeting ? 14:38:25 I will talk to markwash later today and see if we need a wiki page like we had last time 14:38:46 zhiyan: +1 14:38:52 do we have more time than sessions? 14:39:08 mclaren: depends on how we schedule! 14:39:31 i guess the key thing is: does anyone have a topic that is NOT on the agenda? 14:41:09 ok, hearing none, let's stick with what's on the agenda 14:41:18 not all the topics have leaders yet 14:41:46 ok. I think last time we did some ad hoc stuff aswell, which worked quite well. (remember the ideas on post-it notes?) 14:41:59 I don't see anything specific to the artifacts work by ativelkov 14:42:19 mclaren: +1 14:42:34 The "Artifacts and Metadata service" seems related 14:42:38 there's something called Artifacts and Metadata service, but it looks different. 14:42:42 +1 mclaren 14:42:55 will markwash be there? I'd nominate him for the image transfer one... 14:43:03 +1 14:43:04 It is probably about implementing the existing feature requests with artifact plugins 14:43:18 mclaren, yep he is coming 14:43:19 TravT: i was thinking the "Artifacts and Metadata Service" would cover artifacts, who proposed it? 14:43:35 rosmaita: i don't know. 14:43:49 it talks about Grafiti, though. 14:43:49 ativelkov: ? 14:44:36 not me. 14:44:38 ativelkov: do you want to lead that discussion (and make sure artifacts work gets discussed)? 14:44:42 I will 14:44:50 cool, feel free to rewrite the description 14:44:55 If the initial author of this description does not object 14:44:59 I nominated markwash for the Transfer one -- unless someone here wants it 14:45:07 maybe we need a field "requestor" 14:45:17 so we know who put it up there? 14:45:19 TravT: +1 14:45:22 I'm sure he'll thank me :-) 14:45:49 #action remember to put "requestor" field on agenda next time 14:46:17 ativelkov: i would like to ensure we can discuss on what the relationship is between the artifact service and the metadata catalog we are working on. 14:46:38 TravT: right. We do not want any overlaps 14:47:14 I think also, it would be nice to have a session, we select a couple of bugs and we discuss them 14:47:15 nikhil___ : did you want to do transfer sevice? i think you proposed it 14:47:46 (if we have enough time) 14:48:00 rosmaita: well, it's going to be a cross project discussion 14:48:17 arnaud__: how about we use glance drivers meeting tomorrow to work with markwash to make an agenda, put out announce on mailing list, and people can comment/revise before wednesday? 14:48:33 that's what I was thinking 14:48:34 sure 14:48:38 if mark does not prefer taking it, I can. Had left it for thim or inputs from John B.'s work which Mark would be more familiar with 14:49:12 nikhil___: John B's work? 14:49:21 rosmaita: arnaud__ : we "may" need a tiny session for discussing testing moved out of glance 14:49:24 #action arnaud, rosmaita, markwash to create agenda with times tomorrow, will post for comments/revisions 14:49:44 mclaren: https://github.com/stackforge/staccato/commits/master 14:49:47 #action include time for post-it notes, open discussion, and testing 14:49:51 thanks 14:50:33 (i don't think i am using #action correctly) 14:50:50 anything else about minisummit? 14:51:24 rosmaita: adding the testing item to agenda 14:51:39 seems like there is a cross project discussion going on in ML 14:54:26 there were some rest api discussions on ML. if there was a conclusion, getting a summary would be good. 14:56:54 rosmaita: are we in open discussion? 14:58:38 netsplit? 14:58:52 guess so, what did i miss? 14:59:05 well, i asked if we are in open discussion? 14:59:15 1min left, I think we are TravT 14:59:19 we had a question on files for the schemas. 14:59:33 #topic open discussion 14:59:39 basically, are we supposed to create a single file per table in the schema files? 14:59:49 or is it okay to lump them together? 15:00:10 you mean the json schemas? 15:00:25 migrate_repo versions 15:00:25 the sql alchemy migrate files 15:00:37 like : � 001_add_images_table.py 15:01:14 looks like we are out of time today, though. 15:01:28 TravT: maybe send to ML ? 15:01:36 ok. 15:01:42 it is also in code review 15:01:59 boris-42: could you send proposal for google hangout time for demo? 15:02:08 we are over time 15:02:11 #endmeeting 15:02:12 rosmaita_ in meeting by I will 15:02:16 TravT, I think it should be per table 15:02:39 cknight: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 15:03:00 #endmeeting