13:58:07 #startmeeting glance 13:58:08 Meeting started Thu Jan 19 13:58:07 2017 UTC and is due to finish in 60 minutes. The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:58:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:58:11 The meeting name has been set to 'glance' 13:58:12 #chair rosmaita 13:58:13 Current chairs: rosmaita sigmavirus 13:58:44 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 13:58:54 o/ 13:59:00 Courtesy reminder ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishek, bunting, dshakhray, wxy, dhellmann, kairat, aavraham, alex_bash 13:59:06 #topic Roll Call 13:59:09 Hey abhishek_k :) 13:59:22 sigmavirus: your clock is a bit early 13:59:32 My clock says it's 8:01:45 13:59:43 mine says 13:59:41 13:59:54 One of us has clock drift (or both) =P 13:59:54 hey sigmavirus :), mine too 14:00:10 o/ 14:00:17 ok, def 14:00 now 14:00:20 o/ 14:00:22 \o 14:00:33 o/ 14:00:50 o/ 14:00:54 sigmavirus: anyway, thanks for noticing and getting the meeting started 14:01:09 looks like a decent turnout 14:01:46 ok, so i was going to say i want to keep things short today because i'm not feeling well, but something happened at 13:17utc today to make me feel much better 14:01:52 #topic updates 14:01:54 rosmaita: looks like my other laptop is two minutes in the past 14:01:55 o/ 14:02:12 #info community images status 14:02:34 ok, at 13:17utc stevelle 's tempest patch was approved 14:02:47 \o/ 14:02:57 that clears the way for us to merge community images as soon as stevelle 's patch is merged 14:03:24 the test change will, i think, make all other glance changes fail until CI is merged 14:03:41 it shoudn't 14:03:50 even better! 14:04:02 even so, we want to get CI merged today 14:04:11 (or at least I do, and hence, all of you do, too!) 14:04:16 o/ 14:04:37 rosmaita: this is good news =) 14:04:39 hemanthm had put a +2 with some minor corrections, so he's checking CI over again 14:04:45 i have already +2'd it 14:04:50 sigmavirus: indeed! 14:05:06 so we should be ready to go, let's hope the gate cooperates 14:05:10 \\o \o/ o// o/7 14:06:05 next steps are i will put up a patch for the CI release notes and promote it on the operators list 14:06:21 i want to make sure everyone is clear about the changes 14:06:37 and, i'll put up a patch to update the api-ref 14:06:53 After almost a month when all the issue starterd, CI is going to merge :) 14:07:04 that's all about CI for the moment ... any questions, comments? 14:07:11 If they are not they will have to be at some point of time (aware) 14:07:45 aware==clear 14:07:48 nikhil: we have communicated about the change to the ops list, even took a survey 14:08:06 i'd like to get some actual operators reviewing the release notes patch, though 14:08:14 Cool 14:08:15 since they are the intended audience 14:08:17 yeah 14:08:33 I expect we will hear from surprised operators ~1y from now 14:08:40 no matter what we do 14:08:58 yes, when they upgrade from kilo :) 14:09:06 ok, moving along 14:09:15 #info acceptable API changes discussion 14:09:39 so CI wasn't the only issue we've had to discuss with the QA team recently 14:09:50 #link https://review.openstack.org/#/c/420038/ 14:10:05 that's a sigmavirus patch that has caused some controversy 14:10:24 and has resulted in ken (the qa ptl) proposing a patch to the api-wg guidelines 14:10:35 #link https://review.openstack.org/#/c/422264/ 14:11:05 just for awareness, if you are interested in that kind of thing 14:11:09 Okay.. 14:11:22 Yeah, since you brought that up 14:11:27 I was gonna suggest we do it but he has done it already 14:11:28 also, cdent put up something on the ML, a proposal for an "api compatability" tag 14:11:30 I'm just going to change our API Ref docs 14:11:47 sigmavirus: just hold off for now 14:12:00 API compatibility tag may mean a lot of things 14:12:14 i don't have a link to the ML discussion ATM 14:12:24 nikhil: yes indeed, it's intentionally vague at this point 14:12:30 :) 14:12:34 but, it will be refined 14:13:05 and we will have to live with the result ... so, again, just a point of information if you are interested in that kind of thing 14:13:13 #info priorities 14:13:40 #link http://lists.openstack.org/pipermail/openstack-dev/2017-January/110141.html 14:13:51 sigmavirus: IMO your patch is accurate. We are correcting a bug in our response that has been documented correctly. That is outright bug and should not need discussion 14:14:09 jokke_: i agree 14:14:27 since you brought it up, there is an issue here about what counts as the "API contract" 14:14:42 that's why i think it's important that this be addressed directly by the api-wg 14:14:58 so, sigmavirus, i respectfully ask that you not cave on this yet 14:15:06 as much as I'm against changing the api once it's published, but in this case the documentation points to the correct behaviour and any testing done toward that response should have flagged that the response code is wrong 14:16:03 jokke_: be sure to join the discussion on the patches (links above) 14:16:31 fwiw I have a vote, but no harm if that change doesn't go the way I voted. it's clear this is a bug and test coverage was missed on it so I understand that reasoning. 14:16:55 I haven't made up my mind yet on this, so maybe I'm just playing devil's advocate here. But, once an API is published, there isn't a more explicit contract than that. 14:16:55 ok, glance coresec: i will update you-know-what today, the proposed patches will not work, i will outline how i think this issue needs to be handled 14:17:15 that was priority 0, it will carry over 14:17:41 priority 1 was glance_store release, ian will discuss a bit later 14:17:50 rosmaita: will do 14:18:25 priority 2 was port glance migrations to alembic, which is part of the rolling upgrades effort 14:19:00 as soon as CI is merged, the database work for rolling upgrades can get moving faster 14:19:26 and since that's an ocata priority, they'll move up in the list for the coming week 14:20:11 priority 3 was abhishek_k 's request-id patch for glanceclient 14:20:30 and, no movement on that, still needs reviews 14:20:44 yes, new patch is up for review, waiting :) 14:20:52 hopefully with the CI stuff out of the way, there will be some more bandwidth 14:21:02 abhishek_k: i will commit to review it tomorrow 14:21:13 no issues, thank you 14:21:23 glance cores: need a volunteer to review https://review.openstack.org/#/c/352892/ 14:21:33 i mean, someone to volunteer right now 14:21:52 it's kind of embarrassing that this has been on the list so long 14:21:53 Can we volunteer another core? =P 14:21:59 I lost track of it. 14:22:06 #action sigmavirus to review https://review.openstack.org/#/c/352892/ 14:22:15 ^Volunteered rosmaita 14:22:15 sigmavirus: i salute you! 14:22:26 Am I about to rock? 14:22:42 #action rosmaita review https://review.openstack.org/#/c/352892/ 14:22:53 do people still listen to ac/dc? 14:23:07 thank you rosmaita, sigmavirus 14:23:07 Only the best people still listen to them 14:23:12 touche! 14:23:14 only their old things 14:23:15 rosmaita: in nursing homes yes 14:23:27 stevelle: I've still got a hip! 14:23:30 I mean, I'm still hip 14:23:38 stevelle: iron prostate! 14:23:51 :) 14:24:06 (that was actually a band in the 90s, i have a vinyl LP to prove it) 14:24:13 "rock 'n' roll nursing home" 14:24:19 ok, i am wandering 14:24:31 Yeah. Back on topic rosmaita 14:24:50 anyone have any new priorities for the week that we should consider? 14:25:23 actually, i need to: 14:25:34 #action rosmaita comminity images release notes patch 14:25:45 #action rosmaita api-ref CI update patch 14:26:00 rosmaita: from a release schedule perspective, we need to focus on glanceclient priority reviews and then on glance O-3 deadliens 14:26:21 sigmavirus: i salute you again 14:26:58 and then strings / docs ? 14:27:07 the weekly priority list, by the way, has a link in the "topic" in teh openstack-glance channel 14:27:39 Just so everyone's aware 14:27:41 soft string freese is next week 14:27:55 #action nikhil to review https://review.openstack.org/#/c/352892/ 14:27:57 hard string freeze is week of jan 30 14:28:04 #info next week is O-3 milestone; feature freeze; final release for client libraries; requirements freeze 14:28:07 #link https://releases.openstack.org/ocata/schedule.html 14:28:28 the end is fast approaching 14:28:28 So please let's gather our priorities for glanceclient and feature priorities for glance 14:28:34 After O-3 we can focus on bugs 14:28:44 any client and store releases pending for ocata? 14:28:47 All Ocata bug priorities should be decided at next week's meeting 14:28:56 nikhil: client's final release freeze is next week 14:29:03 nikhil: glance store was tagged adn bagged yesterday 14:29:14 ++ 14:29:24 I'm wondering if we should freeze on client asap too? 14:29:32 nikhil: I think we have a bit of time 14:29:45 as soon as this is done 352892 ? 14:29:45 nikhil: we need to get CI changes into client, i think 14:29:46 I would say our feature freeze should be 4 or 5 days from now 14:29:56 gotcha 14:29:58 rosmaita: has anyone actually started that? 14:29:59 there is a patch up for CI in glanceclient 14:30:06 alex_bash 14:30:17 rosmaita: Alex's not in here 14:30:18 client has tendency to break the world 14:30:30 rosmaita: also not in #openstack-glance 14:30:39 given it's used by million other projects, better safe than sorry 14:30:39 rosmaita: someone else should be prepared to take that over 14:30:39 sigmavirus: he's on paternity leave 14:30:47 so CI changes and the request-id changes expected for client. any others known? 14:30:49 only reason for me being a pain to freeze soon 14:30:58 nikhil: yep 14:30:58 i'll put it on the priority list so that it can be reviewed 14:31:14 ++ rosmaita 14:31:19 stevelle: there are some patches related to 'ploop' support 14:31:31 ok, lets get those on the list too 14:31:37 I can focus on CI and req id 14:31:48 rosmaita: those are lowish priority imo 14:31:48 #action rosmaita make list of glanceclient patches for priority list 14:31:54 but I will be away tomorrow and monday travelling 14:32:15 nikhil: Thanks for that head's up :) 14:32:20 Safe travels 14:32:25 thank you :) 14:32:39 sigmavirus: you are right, they only affect "offline" ploop support 14:32:52 and help strings 14:32:54 otherwise, 'ploop' is already in the images schema 14:32:58 so they're good to get in for the soft string freeze 14:32:58 but 14:33:13 that's not as high prio to me as CI and Req ID 14:33:47 agreed, plus my comments on those reviews are not helping, they will make the patches more complicated 14:33:52 rosmaita: yeah 14:34:33 #action rosmaita make clear the priority ordering of glanceclient patches 14:34:44 ok, next topic 14:34:53 #topic reminder about disallowed minor code changes 14:35:12 i saw a bunch of patches earlier this week for minor changes 14:35:19 -2'd them all 14:35:30 rosmaita++ 14:36:08 so if you see such, feel free to minus wiht the strongest integer you have, and refer the patch author to: 14:36:27 #link http://docs.openstack.org/developer/glance/contributing/minor-code-changes.html 14:36:38 that's all about that 14:37:20 except to say, it would be a good idea to look over the minor code changes doc to remind yourself what's in it 14:37:31 #topic Glare 14:37:32 ++ 14:37:37 mfedosin: you have the floor 14:37:49 hey! nice to meet all of you 14:38:03 so, I think you saw my message in ml 14:38:13 that is it :) 14:38:43 rosmaita asked me to prepare small document about next plans for Glare 14:38:57 https://etherpad.openstack.org/p/glare-plans 14:39:18 I separate all tasks in 3 groups: 14:39:34 1. What Nokia (my current employer) is required 14:39:52 2. Other cool and important things 14:40:11 3. Small tasks and improvements 14:40:37 So, what Nokia's required and I'll do first 14:41:08 they need an artifact type for their package 14:41:19 for Nokia-#4, are you talking about blobs in the DB? 14:41:44 nope, it's like it's done in Glance 14:41:56 add-location 14:41:57 ok, so blobs in the backend 14:42:29 in Glare there are external locations and internal (from upload) 14:42:49 looking at your list quickly, that seems to be the place where glare/glance would interesct in Pike, namely, in the glance_store 14:42:55 sometimes it's useful to upload some file to store directly and set this location to blob 14:43:40 otherwise, it looks mostly like Glare work ATM 14:44:08 yeah, glance_store 14:44:33 I want to fix a lot of things there, but I'm not sure that you allow me :) 14:44:46 well, that's why we're having this discussion! 14:45:24 afair kairat wanted to join this initiative as well 14:45:27 i did send something to the ML asking about the quality of the internet connections at the PTG, but have not got a clear answer yet 14:45:42 my point being, we need to discuss glance_store at the PTG 14:46:16 and get some specificity about what we can do in Pike 14:46:17 someone can use their 4G hotspot 14:46:18 lol 14:46:27 okay, I'll prepare a doc that my wishlist 14:46:39 mfedosin: that would be helpful 14:46:40 i.e. what exactly we want to improve in glance_store 14:47:02 and next week we'll be able to discuss it more detailed 14:47:12 #action mfedosin prepare doc with glare glance_store wishlist 14:47:22 ok, great 14:47:26 mfedosin: will Nokia bribe contributors with phones perhaps? 14:47:37 I could use a new one =P 14:47:59 I'll ask them 14:48:22 sigmavirus: they haven't done phones for years :P 14:48:22 I'll have 1/1 with my manager right after this meeting :) 14:48:32 ok, we'll hold any questions for next week, and move on to open discussion 14:48:36 #topic open discussion 14:48:40 they'll be back soon 14:48:40 jokke_: the old ones could survive a nuclear detonation so, I'm cool with that 14:48:57 sigmavirus: they may have to, after this week 14:49:22 /cue ominous music 14:49:23 btw, have you seen my demos? 14:49:33 mfedosin: demolitions? 14:49:43 I like turtles 14:49:54 turtles all the way 'down' 14:49:54 interruption: stevelle 's tempest patch merged 3 min ago 14:50:27 like this https://asciinema.org/a/97986 14:50:40 #action hemanthm complete his CI review as soon as possible 14:50:42 if you want you may call it demolition 14:51:46 * sigmavirus throws a party for stevelle 14:51:51 all 4 demos are here https://asciinema.org/a/97985 https://asciinema.org/a/97986 https://asciinema.org/a/97987 https://asciinema.org/a/99771 14:52:22 it feels a little anticlimactic tbh. that isn't CI merging yet 14:52:41 stevelle: tell hemanthm to review faster! 14:53:02 * hemanthm feels the pressure 14:53:06 I would but I don't want to distract him 14:55:14 it's gone pretty quiet in here ... any final comments? 14:55:30 I like turtles still 14:55:36 I prefer crickets 14:55:40 we can close 5 mins short and make it a glance style short meeting :) 14:55:45 nikhil: true 14:55:51 make everyone spend that time reviewing CI 14:56:00 by the way, i did ask on the ML about the glance logo 14:56:13 saw that, no response sofar 14:56:17 reply was that a new one is almost ready for us to evaluate 14:56:24 I'm good calling early 14:56:53 anyway, i will notify the ML if the new logo comes in before the next meeting 14:57:01 ok, let's end early 14:57:23 sigmavirus: want to do the honors? by your clock, we are at ending time anyway! 14:58:38 * nikhil runs ahead of speed of light to catch up with the clock 14:59:02 #endmeeting