14:00:03 #startmeeting glance 14:00:04 Meeting started Thu Jan 26 14:00:03 2017 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:07 The meeting name has been set to 'glance' 14:00:11 #topic roll call 14:00:37 o/ 14:00:52 \o 14:00:53 o/ 14:00:55 o/ 14:01:00 rosmaita: we should trim that list 14:01:14 which list is that? 14:01:23 courtesy meeting reminder 14:01:29 or ask people to voluntarily remove themselves? 14:01:37 should totally remove sigmavirus24 14:01:43 lol 14:01:45 stevelle++ 14:01:46 i guess i am being overly optimistic about who might show up 14:01:59 esp since that nick doesn't match 14:02:00 (doesn't hurt to have superset) 14:02:01 I'm just looking at how many of those nicks aren't here or in #openstack-glance 14:02:20 * sigmavirus shrugs 14:02:25 we don't have removal criteria 14:02:47 anyway 14:02:49 it has always been voluntary removal 14:02:51 you could put something like, nicks are removed after 6 months of no activity, or something like that 14:02:55 moving along so we don't spend too much time 14:03:06 we can bring this back up in open discussion 14:03:10 (because it is for those who want to be notified) 14:03:10 (we can discuss removal on ML) 14:03:17 ok, kind of a light agenda today 14:03:24 #topic updates 14:03:25 link? 14:03:45 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:04:02 thanks (I'm on a new system) 14:04:20 np, i should add that to the canned stuff we have at the top of the etherpad 14:04:25 * nikhil likes to click than type in etherpad links 14:04:34 #info glanceclient 14:04:41 o/ 14:04:54 thanks to the good graces of sigmavirus, we have an ocata release of glanceclient 14:05:11 o_O 14:05:22 * nikhil claps 14:05:33 i guess we need to see if there are any bugs that have backport potential? 14:05:46 (sorry, didn't mean to step on the applause there) 14:05:50 rosmaita: I'd wait for O-3 to be tagged to start looking at client backport potential bugs 14:06:03 sigmavirus: good point, so let's move on 14:06:18 I need to clean up our series targets in launchpad anyway 14:06:21 Give me an action for that =P 14:06:37 #action sigmavirus clean up series targets in launchpad 14:06:44 (so that folks can nominate bugs for ackport) 14:06:59 #info glance O-3 release today begins the Feature Freeze 14:07:01 also an action to follow up with tonyb about liberty branch 14:07:16 #action sigmavirus follow up with tonyb about the liberty branch 14:07:28 this meeting practically runs itself! 14:07:32 =P 14:07:38 I haven't proposed O-3 tag yet 14:07:47 #info glance O-3 release today begins the Feature Freeze 14:07:49 Does anyone have anything in the gate queue for O-3? 14:07:57 i think you were planning to do it today, though? 14:08:06 I would rather today than tomorrow 14:08:31 If we have stuff in the queue that needs shepherding we have the ability to wait until tomorrow 14:08:31 btw, the various freezes and stuff are defined here, along wiht the timeline: 14:08:36 #link https://releases.openstack.org/ocata/schedule.html 14:08:41 But if it's stuff that doesn't even have a +2 I'd rather not hold us up 14:09:06 hemanthm: stevelle: what's the status of the alembic stuff? 14:09:32 sqlparse was merged, need an update to the alembic review 14:09:55 sigmavirus: what time today are you thinking of proposing O-3 ? 14:10:19 rosmaita: so iirc those reviews don't have a +2 (as of right now0 14:10:28 So I'd rather not wait for those to be have to contend for gate availability 14:10:35 You can FFE them if hemanthm or stevelle requests it 14:10:44 ok, sounds good 14:10:58 I'm more concerned about things currently in the gate queue getting merged and cutting a release after those which are identified are completely merged 14:11:09 ok, the release of O-3 marks the start of the Feature Freeze 14:11:09 I'm not aware of glance things in the gate 14:11:15 Correct 14:11:23 nothing featureful can be landed unless it specifically has an FFE 14:11:29 (feature freeze exception) 14:11:43 and there's one proposal, we will discuss it later in the meeting 14:12:01 is the string freeze directly linked to o-3? 14:12:09 or just matching schedule 14:12:11 stevelle: that's a soft string freeze, and yes 14:12:22 I think it's a soft freeze 14:12:26 ok, good point, that wasn't obvious to me 14:12:33 I'd be worried to propose big stuff after O-3 (but open to debate) 14:12:37 Hard Freeze is next week 14:12:57 ok, just thinking about my replication change 14:12:59 nikhil: I think stevelle is worried about his current patch to change some controversial/insensitive language in glance 14:13:03 Yeah, that 14:13:21 so hard string is when RC-1 is released 14:13:27 *hard string freeze 14:14:00 which changes need strings manipulations ? 14:14:01 yes 14:14:06 (targeted for O) 14:14:13 nikhil: the string freeze is for strings being translated 14:14:14 so if stevelle 's replication change can happen before RC-1, they can get in 14:14:21 So anything using i18n needs to be frozen at that point 14:14:32 Release notes are now included in that FWIW 14:14:40 (Release notes are now being translated) 14:14:52 I am curious if there are any features (is what I meant to ask) 14:15:23 #info when RC-1 is tagged, stable/ocata will be created. At that point Zanata translations will be imported. Stable-maint cores should feel comfortable approving those without a second +2 14:15:26 I need to look through again carefully but most of the rolling upgrades stuff is pretty low-impact to strings 14:15:33 ok, I can take that action item to verify if release notes are complete (sanity check by another person if that's req) 14:15:48 there could be some error messages 14:15:57 #action nikhil review release notes 14:16:01 nikhil: so, what stevelle said + rosmaita's in review patch to update for CI 14:16:16 the visibility release notes need more review 14:16:38 and now does release notes work for FFE work? 14:16:52 stevelle: how so? 14:17:01 yeah, i wasn't aware of a freeze for release notes 14:17:05 that question made little sense to me? 14:17:12 just with the patch should be fine stevelle 14:17:21 release notes are part of the Hard String Freeze only because they're translated now 14:17:34 nikhil: correct. I thought all changes were supposed to include the relnote anyway 14:17:36 I guess I'm thikning about the hard string freeze locking the release notes up 14:17:55 stevelle: they will 14:18:00 *be locked up 14:18:14 so FFE really just gives 1 more week, but no real news there 14:18:40 all good 14:18:41 sigmavirus: I think 'most' rather than 'all'. sometimes features are introduced by series of patches and could have outer deps. in which case we do allow independent rel note patch (like the CI case for Ocata) 14:19:09 yeah, let's deal with that if it happens 14:19:14 * sigmavirus nods 14:19:28 i think it's better to have accurate release notes that aren't translated than inaccurate notes in many languages 14:19:38 ++ 14:20:00 rosmaita: we can double check that ours are being translated, but I think all of them are 14:20:11 and I'm not going to be the person to annoy our i18n team 14:20:15 o/ 14:20:24 rosmaita: I will go over them today and tomorrow and bug people if something shows up 14:20:25 They do fantastic work, I see no reason to move goal posts on them 14:20:27 #action rosmaita annoy i18n team with question about release notes 14:20:55 +1 to i18n team doing fantastic work 14:21:08 ok, one more update 14:21:21 * nikhil would ack but doesn't know any currently translated language :P 14:21:21 #info PTL self-nomination period closes 29 Jan at 23:45 UTC 14:22:07 who is running this time? 14:22:10 i am standing for election again, but don't want to discourage anyone else 14:22:13 s/is/are/ 14:22:33 s/discourage/encourage/ :P 14:23:07 (jk) 14:23:09 ok, that's all for updates 14:23:22 #topic FFE requests for Ocata 14:23:42 i think there's only one request, but i will check my email in a minute 14:23:53 #link http://lists.openstack.org/pipermail/openstack-dev/2017-January/111030.html 14:24:56 ok, don't see anything else on the ML 14:25:00 how much RA do we expect to land in O? 14:25:24 RA==? 14:25:52 Refactoring Antics? 14:25:52 rosmaita: yeah, I think we need to just accept that IIR went to Pike .. I hopefully still have the changes up latest tomorrow 14:25:54 sorry, distracted typo. meant RU = rolling upgrades 14:26:11 jokke__: np, i discuss that in my candidacy statement, btw 14:26:26 jokke__++ 14:26:30 I rather see it landing Early Pike than very last minute 14:26:37 nikhil: ok, thanks ... i have not had coffee yet and am kind of slow 14:26:43 If we can get RU into Ocata, that allows us to focus on IIR early in PIke 14:26:50 jokke__: ++ i am with you on that 100% 14:26:50 Or 90% of RU 14:27:02 wow 14:27:20 nikhil: I think RU is really close to being ready for O 14:27:24 what is IIR image import? 14:27:25 * nikhil plans to catch up on ru 14:27:26 It just needs touch-ups 14:27:32 jcook: yes, IIR is Image Import Refactor 14:27:40 right on, thanks 14:27:51 my feeling is that RU is close enough that we should keep working on it 14:27:57 _but_ that said, I'd really like to see it land early pike and not keeping rebasing it until end of P-2 or something ;) 14:28:03 definitely want the alembic migration changes in 14:28:22 and as much other stuff as we can safely merge 14:29:07 i think the plan is carefully thought out and a lot of the work is done 14:29:10 jokke__: that assumes another OpenSTack team doesn't step in and block us again 14:29:11 ;) 14:29:19 no api changes on this one 14:29:26 we have to assume they will :P 14:29:42 stevelle: always the cynic... just like me =P 14:29:44 why is everyone so glass-half-empty this morning? 14:29:52 rosmaita: because my coffee mug is empty 14:30:03 anyway, we are keeping people distracted with sigmavirus 's 204 patch 14:30:13 :) 14:30:13 * sigmavirus creates smokescreen 14:30:22 you saw there was a tempest test for that added? 14:30:32 smokescreen engaged 14:30:34 ken'ichi put up a rival patch to change the api-ref 14:30:49 who is primary POC for RU? 14:30:54 i am going to ask him to add unit tests to prevent a regression 14:30:56 sigmavirus: I'd say we don't care about them at this point anymore ... they had 2 years to chip in :) 14:30:56 nikhil: hemanthm 14:31:00 cool 14:31:03 The tempest PTL changed the status code in the doc for us, putting up a patch 14:31:17 dharinic: yes, that's the one i meant 14:31:30 rival patch :D 14:31:31 i am going to require a unit test to make sure that call returns 200 instead of 204 14:31:46 because it's the kind of thing someone might fix inadvertently 14:31:59 I'm still in Favor of sigmavirus's patch as that's the correcting one 14:32:00 plus, i'm still not convinced it the correct thing to do in this case 14:32:19 (is this all part of the FFE?) 14:32:25 * nikhil bit confused 14:32:28 yeah, i left some more comments on sigmavirus 's patch 14:32:31 nikhil: bugfix 14:32:43 sorry, we got distracted, we can discuss this in open discussion 14:32:51 gotcha 14:32:56 ok, so i am inclined to grant FFE for rolling upgrades 14:33:10 that seems to be the general trend of this discussion, too 14:33:20 do we want to take a vote? or just go for it? 14:33:48 (i got some feedback that i need to be more assertive, so i am asserting let's go for it) 14:34:06 I'd like to learn a bit about it 14:34:13 nikhil: you can read the specs 14:34:13 especially since IBM is interested 14:34:20 yup 14:34:23 lots of good info in there 14:34:40 read and follow up is the Action item for me 14:34:40 Ok, hearing no objections, i declare: 14:34:51 #info FFE granted for rolling upgrades work 14:35:01 ok, next topic 14:35:06 I object to the fact that no one has objected. Glance is behaving too efficiently! 14:35:10 #topic Pike PTG planning 14:35:23 nothing to say other than to remind you about the etherpad 14:35:38 we'll pay more attention after RC-1 14:35:44 :) 14:36:32 couldn't find the link, here it is: 14:36:36 #link https://etherpad.openstack.org/p/glance-pike-ptg-planning 14:37:05 ok, one non-agenda item 14:37:10 #link https://wiki.openstack.org/wiki/PTG/Pike/Etherpads 14:37:22 #topic priorities 14:37:34 ok, so priorities will be the FFE work, obviously 14:37:55 and proposing backport-potential glanceclient bugs 14:38:19 there's an outstanding metadefs patch that i need to follow up on 14:38:53 #link https://review.openstack.org/#/c/367161/ 14:40:04 and coresec team, there is still The Bug outstanding 14:40:20 ok, that's all for our regularly scheduled show 14:40:25 #topic open discussion 14:40:46 I don't get the change description , quite sparsely written (367161) 14:41:13 rosmaita: a couple questions regarding priorities 14:41:18 1. release notes? 14:41:23 yes, and i am not clear on the horizon implications 14:42:03 that change needs a lot more work at least in terms of communicating the intent 14:42:11 yes, we should add release notes since it looks like they need to be done early 14:42:35 (as a priority, i mean) 14:42:42 commit description, lite-spec and much more explicit rel notes with upgrade impact 14:42:54 s/with/in 14:43:05 rosmaita: yep, thank 14:43:07 you 14:43:23 rosmaita: (on priority item) 2. deprecation path (and removals) 14:43:55 yes, there are some config options slated for deprecation that i am concerned about 14:43:59 I saw sigmavirus has a -2 on one of the review so thought we all can discuss the same 14:44:41 we have a the asset tag for deprecation path and in the past we've been relaxed about removals 14:44:55 some of the deprecated stuff in glance doesn't even mention the cycle name 14:45:07 well, the tag says we remove nothing before it's time 14:45:16 doesn't guarantee that we'll actually remove it 14:45:17 nikhil: I suspect we don't because we were not using debtcollector/deprecation cycle features 14:45:18 :) 14:45:18 so, what do we want to do? indicate on or after Ocata (if it suggests Ocata)? 14:45:44 nikhil: if it suggests on or after Ocata, let's remove all those deprecated items for Pike-1 14:45:51 i think we should always write these in "on or after" mode 14:45:52 I -2'd a bunch of stuff to help cores focus on our actual priorities 14:46:02 I saw "horizon" and got pinged, so I'm here if I can offer any advice from the Horizon side :) 14:46:07 yeah 14:46:16 sigmavirus: thanks for bringing that up 14:46:24 we are having a good discussion :) 14:46:30 (that == -2) 14:46:33 i'm worried about the show_multiple_locations removal, that may actuall need a lite spec 14:46:51 robcresswell: thanks , let me get you a link to look at 14:46:53 the config option you mean? 14:47:00 https://review.openstack.org/#/c/367161/ 14:47:03 robcresswell: ^^ 14:47:21 Ah, yes 14:47:25 yes, the option, not the feature 14:47:30 sure (on a lite spec) 14:47:34 the feature is quite popular, it turns out 14:47:38 indeed 14:47:46 it's gunna get even more 14:48:24 alright then, I will keep the removal stuff aside and focus on rel notes 14:48:28 we need to get some security people to look at specs before we add anything to the locations stuff 14:48:30 We already have the depends-on. The change itself seems pretty inoffensive, though that patch will need a release note 14:48:34 in case plugins are using it 14:48:34 we can target them for Pike-1 as a priority then 14:50:06 i just realized i have been linking to the wrong review 14:50:10 here's the one on the glance side: 14:50:17 https://review.openstack.org/#/c/359742/ 14:51:34 this line in particular needs elaboration:- 14:51:36 "but does not align with Heat or Searchlight. It should be noted that Heat added the resource type after Glance had metadefs." 14:52:11 and needs to have technical ramifications before and after in the release notes 14:52:45 so i guess my question to robcresswell is how bad is it for horizon if this glance change doesn't go into ocata? 14:53:08 (good question) 14:53:24 i'm pretty sure operators can make the change themselves 14:53:32 i mean if they want it now 14:53:41 though, that wouldn't help horizon, nevermind 14:53:51 I'm just catching up on the bug report 14:54:00 robcresswell: sorry, don't mean to rush you 14:54:20 Honestly, from what I can tell, it doesn't really seem to impact us either way 14:54:33 It seems more of a consistency improvement than an actual requirement for us 14:54:41 ok, great 14:55:05 * robcresswell may regret those words when everything is on fire next week 14:55:05 Hi all, I would like to thank all for merging request_id patch on behalf of abhishekk as he is on vacation 14:55:20 rosmaita: LOL 14:55:24 robcresswell: ^ 14:55:49 DineshB_: thanks, and we all hope abhishekk is having a good vacation 14:56:11 rosmaita: yes 14:56:18 i do have one more news item, dharinic was nominated for glance core 14:56:42 there have only been affirmative responses, so she'll be added to the glance core team right after this meeting 14:56:52 so, congratulations to dharinic 14:56:57 Thank you to all the cores. :) 14:56:57 * nikhil claps 14:57:13 congrats to dharinic 14:57:26 well done dharinic 14:57:34 GZ dharinic well deserved 14:57:43 Specially hemanthm, my OSIC mentor :) 14:57:55 Thanks all. 14:58:04 dharinic: the cores didn't do anything. you did =) 14:58:14 well, we did recognize her excellence 14:58:20 * sigmavirus hits rosmaita 14:58:23 :) 14:58:39 sigmavirus: The cores inspired, motivated and recognized. 14:58:52 haha 14:59:08 well, that ends our meeting on a high note 14:59:18 i will close before sigmavirus says anything else 14:59:20 :) 14:59:25 #endmeeting