14:01:00 <rosmaita> #startmeeting glance
14:01:00 <openstack> Meeting started Thu Sep  7 14:01:00 2017 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:04 <openstack> The meeting name has been set to 'glance'
14:01:11 <rosmaita> #topic roll call
14:01:15 <abhishek_k> o/
14:01:19 * smcginnis is partly here
14:01:29 <jokke_> o/
14:01:47 <jokke_> still on other call but I'll be fully yours in a bit
14:03:07 <rosmaita> ok
14:03:42 <rosmaita> might as well get started
14:03:50 <rosmaita> (just finished the proposed ptg schedule)
14:03:59 <rosmaita> #topic updates
14:04:20 <rosmaita> #info no meeting next week due to PTG
14:04:35 <rosmaita> (i thought that was supposed to do something)
14:04:52 <jokke_> :)
14:05:13 <rosmaita> also, i have taken the liberty of scheduling 2 events for us at the PTG
14:05:31 <rosmaita> #info glance team photo, tuesday at 11:20 am
14:05:45 <rosmaita> not sure where the location is, will update the ptg schedule when I know
14:05:55 <abhishek_k> great
14:06:10 <rosmaita> also, for abhishek_k and jokke_ , i have signed us up for a video interview
14:06:18 <rosmaita> tuesday at 11:30 am
14:06:23 <rosmaita> (so right before lunch)
14:06:39 <abhishek_k> good to know
14:06:45 <rosmaita> take a quick look at this email for more info:
14:06:56 <rosmaita> #link http://lists.openstack.org/pipermail/openstack-dev/2017-August/121369.html
14:07:20 <rosmaita> it's a kind of "get to know some glance devs and what they did in pike" kind of thing
14:07:36 <rosmaita> the email has a link to a spreadsheet that has a page outlining some questions to be ready for
14:07:40 <abhishek_k> going through previous interviews on YouTube :D
14:07:48 <rosmaita> so please take a look when you have some time
14:08:05 <rosmaita> ok, final update
14:08:31 <rosmaita> #info lbragstad has started work on the policy-in-code community goal for glance
14:08:59 <rosmaita> had a brief discussion with him yesterday in the #openstack-glance channel
14:09:03 <jokke_> oh crap :P
14:09:14 <rosmaita> you can take a look at the channel logs to see what we discussed
14:09:19 <jokke_> that was for the interview, not the policy work
14:09:38 <rosmaita> ok!
14:10:04 <rosmaita> well, you don't have to interview ... but it's a RH guy doing the interviews
14:10:15 <rosmaita> so sort of a home team thing for you
14:10:33 <rosmaita> yeah, so lance has some patches up already for the glance changes
14:10:36 <jokke_> Ok, finally fully yours
14:11:11 <rosmaita> i think we should look them over and can discuss at the PTG
14:11:23 <abhishek_k> ok
14:11:33 <jokke_> So anyone has a good TL;DR about this community goal, why are we doing this and what are we trying to achieve with it?
14:11:38 <rosmaita> he's having 2 sessions on monday and tuesday about the goal
14:11:49 <jokke_> ok
14:11:55 <jokke_> need to try to attend to those
14:12:02 <rosmaita> yeah, key thing is to be able to have oslo.policy generate what the default policy is
14:12:32 <rosmaita> and to make sure there are defaults in place for all policies
14:12:51 <jokke_> well we do have that as soon as you have 'default' defined :P
14:13:03 <rosmaita> well, sort of
14:13:16 <jokke_> anything else that is not specifically defined will use that
14:13:36 <rosmaita> unless the config option to change 'default' to 'freddy' has been used
14:13:40 <rosmaita> :)
14:14:20 <rosmaita> there's a little weirdness for glance because we also allow policy to be used to control image property protections
14:14:35 <jokke_> well that just makes freddy the default ... doesn't make it any less default what ever sting has been used to identify it
14:14:44 <jokke_> string
14:15:21 <jokke_> rosmaita: there is penty of weirdness in Glance and policies :P
14:15:22 <rosmaita> well, if the config opt is 'freddy' for the "default" rule, then having 'default': 'role:admin' in your file won't actually work
14:15:55 <rosmaita> i mean 'freddy' for the name of the rule that is used for default
14:16:05 <rosmaita> that is really hard to explain, let's discuss at the ptg
14:16:32 <rosmaita> ok that brings us to the next topic
14:16:39 <rosmaita> #topic PTG
14:16:51 <rosmaita> as you well know, the PTG is next week
14:16:52 <jokke_> rosmaita: no but it's not default value and if you change it you need to understand to change your 'default' string to 'freddy' string ... like said that's just key how to identify your default value and it won't change the defaultness behavior wise as long as it's identified correctly
14:17:00 <jokke_> sure
14:17:37 <rosmaita> here's my schedule proposal
14:17:47 <rosmaita> #link https://etherpad.openstack.org/p/glance-queens-ptg
14:18:11 <rosmaita> i haven't copied over the descriptions, so you'll have to look at the planning etherpad, too:
14:18:21 <rosmaita> #link https://etherpad.openstack.org/p/glance-queens-ptg-planning
14:18:36 <rosmaita> i will copy the discriptions over, though, so we have everything in one place
14:18:50 <rosmaita> key thing now is feedback on timing, etc
14:18:57 <rosmaita> and i was hoping mtreinish is here
14:19:16 <rosmaita> he's leading a session, but i want to make sure there's no conflict
14:19:48 <rosmaita> ok, so basically, as i said at the top of the pad, i planned for 9am to 5:30 pm
14:20:00 <jokke_> So only thing that really jumps on my face from there is the strategic planning
14:20:04 <rosmaita> we have rooms until 6pm, though, so we won't get kicked out if we go over
14:20:33 <rosmaita> yeah, there is no description for that one, i just threw it in
14:20:42 <rosmaita> but here's what i'm thinking
14:20:54 <jokke_> does it make sense to have strategic planning discussion before we have actually had discussions of the individual topics
14:21:09 <rosmaita> good question
14:21:33 <rosmaita> my idea is that this is a general thing, where we say what we would like to see glance going
14:21:45 <jokke_> I'd almost prefer to double session that with the Queens prioritization, kind of "This is what we try to achieve in Queens, now lets discuss longer term plan"
14:22:00 <rosmaita> like, i think we need to complete swift support and start thinking about more ceph support
14:22:29 <rosmaita> yeah, but my idea is that if we have some idea of where we want to go, it will help us in thinking about the queens-specific stuff
14:22:59 <rosmaita> because, i am well aware, that there' cannot *really* be a strategic plan
14:23:10 <rosmaita> the next PTL could change everything
14:23:10 <mtreinish> rosmaita: heh, I don't really have a fixed schedule for the ptg
14:23:36 <jokke_> So Wed morning we make strategic plan to free u half of the sessions as they're out of our long term planning already? :P
14:23:39 <rosmaita> mtreinish: hello, i have you down for wednesday 16:30-17:15 for your microversion thing
14:23:48 <jokke_> "free up"
14:24:32 <rosmaita> jokke_ well, it's more like this
14:24:35 <mtreinish> rosmaita: I probably can make that work
14:24:40 <rosmaita> we have dev-power problems right now
14:24:47 <rosmaita> so queens will fill up fastg
14:24:50 <rosmaita> *fast
14:24:55 <jokke_> yeap
14:25:10 <rosmaita> but i am curious what people have heard/are thinking for "the future" of glance
14:25:32 <rosmaita> also, this impacts the "replacement" issue
14:25:57 <rosmaita> which i scheduled before lunch on thursday so that therewill be a hard stop to the discussion
14:26:13 <jokke_> sure, so the Strategic plan session is kind of "Paint the perfect world with all the unicorns" and then we have 2 days of reality check after that? :D
14:26:22 <rosmaita> exactly
14:26:38 <rosmaita> but like doug's question on the ML yesterday
14:27:06 <rosmaita> do we see on-demand replication happening? what would come first? stuff like that
14:27:25 <rosmaita> anyway, i figured it will be an easy way to kick things off
14:27:46 <rosmaita> btw, i just noticed i have a blank slot on thursday morning
14:27:47 <jokke_> yeah ... I just had internal meeting before this one around what we want to achiee, what kind of road map we're planning etc. :D
14:27:56 <rosmaita> ha!
14:28:15 <jokke_> to see if there is something major from our customers that would need to try to fit into PTG discussions
14:29:14 <rosmaita> ok, no more blank spot on thursday am
14:30:06 <rosmaita> my thought is to deputize anyone appropriate to be able to discuss the sec bugs
14:30:17 <jokke_> I added fillup for Fri morning session for those glance folks who are not in -core-sec and want to use the time well for Glance ;)
14:30:30 <rosmaita> but yeah, i guess we should plan for the possibility of inappropriate people being there!
14:30:39 <rosmaita> ok, that's a good idea
14:30:52 <rosmaita> we'll go over the bugs thursday afternoon
14:31:04 <rosmaita> and they'll be ready for people to work on friday morning
14:31:15 <rosmaita> that's actually a good change, thanks
14:31:17 <jokke_> yeah
14:31:44 <rosmaita> cool
14:31:55 <jokke_> should we try to agree already day for Glance team night out?
14:31:55 <rosmaita> any other feedback about the schedule?
14:31:56 * smcginnis has been accused of being inappropriate
14:32:06 <jokke_> smcginnis: well done!
14:32:10 <smcginnis> :)
14:32:12 <rosmaita> smcginnis do tell!
14:32:15 <jokke_> smcginnis: keep doing it.
14:32:43 <rosmaita> i didn't put a team dinner on there, we should probably plan for one, though
14:33:17 <rosmaita> anyone have a preference for tues, wed, or thurs?
14:33:28 <rosmaita> or i guess monday for that matter
14:33:38 <jokke_> I've seen some teams already planning for Wed. Should we try to align with that?
14:33:58 <jokke_> or specifically rule that out so multi contributors can join both?
14:34:09 <smcginnis> Tuesday would probably work best for me. I'd love to meet up with you all, but shouldn't affect whatever works best for everyone else.
14:34:14 <abhishek_k> sounds good
14:34:15 <jokke_> the problem is that there will be likely company specifics as well etc.
14:34:17 <rosmaita> i think smcginnis and mtreinish are the ones most likely to have conflicts
14:34:39 <smcginnis> rosmaita: I'll be having a lot of dinners next week. ;)
14:34:39 <jokke_> yeah, but that's like 3rd of our active base atm.
14:34:46 <rosmaita> ok, let's shoot for Tuesday for a "formal" team dinner
14:34:56 <rosmaita> and then we can also have informal team dinners all the other days
14:35:04 <jokke_> Sounds good to me
14:35:16 <abhishek_k> works for me as well
14:35:17 <rosmaita> ok, anyone familiar with denver?
14:35:47 <jokke_> if we don't have first hand, I have some friends on the area so I can ask for suggestions
14:36:07 <abhishek_k> no, I only know vegas is 10 hours away by road :D
14:36:24 <jokke_> Just FYI I'll be flying in Sun and out Sun
14:36:26 <smcginnis> There was a wiki page started somewhere with recommendations.
14:36:35 <smcginnis> If I can find that, I'll paste into the -glance channel.
14:36:40 <rosmaita> smcginnis cool
14:36:58 <rosmaita> ok, i put team dinner on the etherpad for 18:30 tuesday
14:38:04 <rosmaita> sorry smcginnis i always want to spell your name like the beer
14:38:21 <smcginnis> It's a good mistake to make. :D
14:38:34 <rosmaita> ok, i'll update the schedule with the descriptions this afternoon
14:38:47 <jokke_> I think it's actually really good to sit down around food and drinks before the session :P
14:38:51 <rosmaita> and then update the wiki page of etherpads to make the new one our "official" etherpad
14:38:58 <jokke_> Less risk of fights at the dinner :D
14:39:16 <rosmaita> yeah, but more risk of being hung over for the strategic planning!
14:39:16 <abhishek_k> :D
14:39:34 <rosmaita> final thing
14:39:39 <jokke_> rosmaita: I think that might be beneficial as well
14:39:49 <rosmaita> monday and tuesday are open
14:40:04 <rosmaita> please add sessions of interest that you learn about to the etherpad
14:40:48 <rosmaita> ok, moving on
14:40:56 <rosmaita> #topic py35 goal report
14:41:11 <jokke_> Indeed ... and remember that Wed-Thu seems quite well packed so remember to leave sufficient time for hallway talks mon-tue, fri (and specially if you're scheduling some extra curricular activities)
14:41:32 <rosmaita> ok, so i looked over everything, and those 2 skipped tests (plus adding the PyPI classifier) in glance are all that's outstanding
14:41:56 <jokke_> so we really are almost there!
14:42:00 <rosmaita> what's weird is that the ssl handshake problem is reported for py27 in google, everyone thinks py35 is fine
14:42:10 <rosmaita> so i am doing a bit more research
14:42:20 <rosmaita> but yeah, we are almost there!
14:42:36 <rosmaita> i updated the etherpad with specifics about all our projects
14:42:48 <jokke_> nice
14:42:59 <jokke_> mind to link it here again for reference
14:43:08 <rosmaita> (looking
14:43:11 <rosmaita> )
14:43:16 <rosmaita> #link https://etherpad.openstack.org/p/glance-pike-python35-goal
14:43:39 <rosmaita> we need to plan a hallway discussion about the wsgi business
14:43:56 <rosmaita> maybe we can combine it with actual whiskey on tuesday evening
14:44:05 <jokke_> is the community wide tracking page up to date? (I can't remember was it wiki or etherpad or what was it)
14:44:24 <rosmaita> there is an etherpad, i'll have to find it
14:44:41 <rosmaita> when i do, i'll put a link on the one i linked above
14:44:57 <jokke_> ++
14:45:25 <rosmaita> ok, i lost the agenda
14:45:50 <rosmaita> oh, yeah, here's some light reading you may not have seen on the regular ML:
14:46:01 <rosmaita> #link http://lists.openstack.org/pipermail/openstack/2017-September/045448.html
14:46:15 <rosmaita> we should probably all read that before the strategic planning session
14:46:37 <rosmaita> #topic open discussion
14:47:01 <rosmaita> there's a patch up for changing the alembic db facades or something like that
14:47:10 <rosmaita> #link https://review.openstack.org/#/c/500889/
14:47:45 <rosmaita> it's part of one of those items where someone goes through all the projects cleaning things up or getting rid of deprecated stuff
14:47:59 <rosmaita> and apparently, it not being merged into glance is blocking something else
14:48:19 <rosmaita> i'll look at it this afternoon, but of course i am only one +2
14:48:45 <rosmaita> tbh, i have been ignoring it, didn't realize it was important
14:49:11 <jokke_> So looking that DbMigrationError change
14:50:11 <jokke_> it's really confusing for me as last change merged to oslo.db master is actually raising the DbMigrationError which is claimed to be deprecated on the change proposed to us
14:50:40 <rosmaita> also, this is not the oslo db facade change i was thinking of
14:51:14 <abhishek_k> We also need to look at https://review.openstack.org/#/c/493654/
14:51:30 <abhishek_k> #link https://review.openstack.org/#/c/493654/
14:52:23 <abhishek_k> i have tested it thoroughly and added my comment
14:52:34 <rosmaita> abhishek_k thanks for testing that out
14:53:37 <abhishek_k> yes, atleast for mentioned scenarios I haven't encountered any problems
14:54:22 <jokke_> abhishek_k: so that will unbreak image upload when deployed on uwsgi?
14:54:50 <abhishek_k> that will not break
14:56:47 <jokke_> I'm not that worried about the tests but you all know how much I hate unit tests anyways. What I am actually missing is some level of tracking (likely a bug) for why we are doing this so that it can be easily captured on the releasenotes
14:57:20 <mtreinish> jokke_: https://bugs.launchpad.net/glance/+bug/1703856
14:57:22 <openstack> Launchpad bug 1703856 in Glance "502 Bad gateway error on image-create" [High,Confirmed] - Assigned to Matthew Treinish (treinish)
14:57:27 <jokke_> the commit message is pretty clear explaining why this is actual bug on our code if we claim supporting wsgi
14:57:28 <abhishek_k> jokke_: yes we can add that as a bug is already reported for this
14:58:11 <jokke_> mtreinish: does the change close that bug? Can we just add Closes-Bug: to the commit message and be happy with it?
14:59:12 <mtreinish> jokke_: yes, that was my oversight. I'd do it except I don't want to take the gate hit adds like >2hours of wait time
14:59:31 <mtreinish> and also eats resources for no real gain when we're over capacity
15:00:33 <abhishek_k> we are out of time
15:00:44 <rosmaita> good point
15:00:51 <jokke_> Thanks all!
15:00:58 <rosmaita> let's continue in #openstack-glance
15:00:59 <abhishek_k> thank you all
15:01:04 <rosmaita> thanks!
15:01:07 <rosmaita> #endmeeting