14:00:15 <rosmaita> #startmeeting glance
14:00:16 <openstack> Meeting started Thu Feb  2 14:00:15 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:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:19 <openstack> The meeting name has been set to 'glance'
14:00:22 <rosmaita> #topic roll call
14:00:27 <hemanthm> \o
14:01:07 <rosmaita> hello hemanthm
14:01:11 <sigmavirus> o/
14:01:16 <hemanthm> morning rosmaita
14:01:26 <rosmaita> hello ian, glad you are here, you have the first item
14:01:32 <alex_bash> o/
14:01:36 <rosmaita> but looks like we should wait a minute or two
14:01:39 <rosmaita> hi alex
14:01:40 * sigmavirus checks agena
14:01:45 <alex_bash> hey
14:01:52 <stevelle> o/
14:02:05 <nikhil> o/
14:02:25 <rosmaita> hello steve and nikhil ... i think we have a quorum, let's get started
14:02:55 <dharinic> \o
14:02:55 <rosmaita> #topic release updates (sigmavirus)
14:03:05 <sigmavirus> Hey yinz
14:03:45 <rosmaita> sigmavirus: before you get started, i will give a quick update
14:03:52 <sigmavirus> So some announcements: 1. Ocata-b3 was released last week. So far no bugs are filed against it (but distros seem stuck on O-2)
14:03:55 <sigmavirus> 2. Once we tag RC-1 (today) we will be in a *hard* feature freeze and a *hard* string freeze
14:03:59 <rosmaita> (ok, i will wait)
14:04:15 <sigmavirus> (sorry rosmaita you were too slow)
14:04:21 <sigmavirus> I'll only be a couple more seconds
14:04:27 <rosmaita> (not the first time i've heard that)
14:04:44 <sigmavirus> 3. It looks like Rolling Upgrades will be in RC-1
14:04:52 <sigmavirus> (Good work hemanthm dhellmann stevelle rosmaita alex_bash et. all)
14:05:20 <rosmaita> and sigmavirus did some reviewing in there, too
14:05:31 <sigmavirus> 4. I would love everyone to start testing RC-1 once it's released. If you find bugs, report them and nominate them for stable/ocata (whose branch and release series will be created with RC-1)
14:05:58 <sigmavirus> If you find bugs, mention the bug in #openstack-glance so one of us can appropriately approve the nomination to the ocata series
14:06:13 <sigmavirus> 5. RC-1 *may* be the last RC if we dont' find bugs
14:06:24 <sigmavirus> If that's the case, we'll release Ocata (14.0.0) from the RC-1 tag
14:06:58 <sigmavirus> And finally, 6. If you're a stable branch core reviewer: Requirements updates, Zanata translation imports, etc. are all capable of being approved by a single person, so please don't wait on a second +2
14:07:14 <sigmavirus> Actually, one addendum, please let me know if there are priority backports to mitaka or newton
14:07:22 <sigmavirus> I'd like to release stable versions of those soon
14:07:31 <sigmavirus> </end>
14:07:36 <hemanthm> sigmavirus: how much time do we have to get the rolling upgrade patches through the gate?
14:07:43 <nikhil> (the rc potential bug usually (when I've set it) have a tag - release-rc-potential eg. newton-rc-potential)
14:07:48 <sigmavirus> hemanthm: I'd like to get the patch in this afternoon
14:07:52 <rosmaita> two of the alembic/rolling upgrades patches have merged
14:07:52 <rosmaita> two more are in the gate now:
14:07:52 <rosmaita> https://review.openstack.org/#/c/392993/
14:07:53 <rosmaita> https://review.openstack.org/#/c/424774/
14:07:58 <sigmavirus> nikhil: those tags exist already ;)
14:08:04 <rosmaita> plus, the release notes for the change to using alembic as the database migration tool:
14:08:07 <rosmaita> https://review.openstack.org/#/c/427971/
14:08:08 <nikhil> sigmavirus: indeed
14:08:10 <rosmaita> (i am revising that now)
14:09:26 <rosmaita> so except for the release notes, it's just a matter of the gates cooperating
14:09:33 <nikhil> sigmavirus: I am happy that one exists for ocata already https://bugs.launchpad.net/glance/+bugs?field.tag=ocata-rc-potential
14:10:06 <rosmaita> is everyone here clear on how to use the tags?
14:10:50 <alex_bash> no
14:10:54 <jokke__> o/
14:11:29 <rosmaita> sigmavirus: want to explain?
14:12:19 <rosmaita> here is an example bug
14:12:22 <rosmaita> https://bugs.launchpad.net/glance/+bug/1656183
14:12:22 <openstack> Launchpad bug 1656183 in Glance "Delete tags return 200 status code but api-ref says 204" [High,In progress] - Assigned to Ian Cordasco (icordasc)
14:12:26 <sigmavirus> So, if you find an issue that affects ocata (in a release candidate) then you can use that tag to explain that it might have release candidate potential
14:12:40 <rosmaita> under the description, there's an "add tags" widget
14:12:50 <rosmaita> it pops open a text box, just start typing
14:12:50 <sigmavirus> There is a link at the top of the page, however, beneath the table with status/assignee/etc. and it allows you to nominate it for a series
14:14:19 <sigmavirus> If you can nominate something for a specific series, that's better than tagging it, but you can also tag it to be safe
14:14:39 <sigmavirus> Also to be clear, the bugs that should be nominated should be critical user-facing bugs
14:14:52 <rosmaita> so, to summarize: if you find a bug that you think shoud go into ocata, do the following:
14:15:01 <rosmaita> (1) target to series -> ocata
14:15:12 <rosmaita> (2) add tag "ocata-rc-potential"
14:15:30 <alex_bash> Ok, I've used the "add tags" link before, thought it was something different. I don't see the "target to series" link though
14:15:52 <alex_bash> Milestone?
14:15:59 <nikhil> alex_bash: only specific people have that access
14:15:59 <rosmaita> underneath that
14:16:02 <rosmaita> oops
14:16:13 <rosmaita> ok, then forget step (1)
14:16:23 <nikhil> we use tags to propose the bug against a series
14:16:30 <alex_bash> ah, I see, I'm not specific enough
14:16:37 <sigmavirus> nikhil: so most people should be able to nominate to series
14:16:49 <nikhil> alex_bash: it may just that you are not part of the glance-bug-team
14:16:49 <sigmavirus> Only drivers/release managers can actually target it or approve a nomination
14:17:24 <nikhil> or what sigmavirus said, I haven't user-tested this before
14:17:30 <rosmaita> we will have to fix that, alex_bash is actually good about digging up bugs and triaging
14:17:32 * sigmavirus has
14:17:42 * sigmavirus has done too much investigation
14:17:48 * sigmavirus is too curious for his own good
14:17:56 * sigmavirus will stop referring to himself in the third person now
14:18:00 <rosmaita> ok, so key thing, please tag bugs you see/want to work on that you think should go into Ocata
14:18:09 <rosmaita> they must be approved first before they get merged
14:18:15 <rosmaita> so don't work first, then ask
14:18:34 <rosmaita> tag the bug and put a shout into #openstack-glance to let us know to look at it
14:18:43 <nikhil> alex_bash: you may want to join https://launchpad.net/~glance-bugs (irrespective of the access level it has)
14:19:28 <rosmaita> ok, let's move along, i want to keep this meeting short (need to revise a release note before sigmavirus closes RC-1)
14:19:28 <alex_bash> joined, thanks Nikhil
14:20:07 <rosmaita> #topic mascot: new draft available
14:20:23 <rosmaita> new mascot attached to this email: ttp://lists.openstack.org/pipermail/openstack-dev/2017-January/111151.html
14:20:37 <nikhil> (so, yeah from memory of an old bug what sigmavirus said about release team in lp glance project has access to target against a series)
14:20:40 <rosmaita> i think it's what we asked for (even though i voted for the saber-toothed tiger)
14:20:53 <sigmavirus> rosmaita: it is what we asked for
14:21:03 <rosmaita> and, at least it isn't obscene, like the new ironic draft
14:21:05 <sigmavirus> nikhil: yeah, but the release team is intentionally kept on the small side
14:21:12 <sigmavirus> rosmaita: v3 is less obscene
14:21:14 <nikhil> http://lists.openstack.org/pipermail/openstack-dev/2017-January/111151.html
14:21:20 <sigmavirus> still offensive to italians and south americans, but yolo
14:21:26 <nikhil> nods to sigmavirus
14:22:08 <jokke__> yeap
14:22:24 <rosmaita> #topic pike ptg planning
14:22:50 <rosmaita> everyone should take a look at the proposed community goals for pike
14:22:53 <rosmaita> https://github.com/openstack/governance/tree/master/goals/pike
14:23:05 <rosmaita> and start thinking about what we need to do in glance to accomplish them
14:23:18 <rosmaita> i'll propose some sessions based on that
14:23:46 <rosmaita> we'll also have a session wiht the new docs PTL about our docs and openstack docs in general
14:24:28 <rosmaita> also, plenty of room for sessions to be proposed:
14:24:29 <rosmaita> https://etherpad.openstack.org/p/glance-pike-ptg-planning
14:24:39 <rosmaita> we'll discuss more next week
14:25:05 <sigmavirus> ^ asettle
14:25:13 <asettle> I WAS PINGED
14:25:16 * asettle arrives with cape
14:25:30 <rosmaita> everyone, meet Alexandra Settle, new docs PTL
14:25:30 <asettle> Oh okay, yep, docs :)
14:25:36 * asettle waves overly enthusiastically
14:25:44 * sigmavirus was documenting the IRC nick of the new docs PTL
14:25:46 <sigmavirus> ;)
14:25:57 <rosmaita> we were just saying that you have graciously agreed to discuss docs with us at the PTG
14:25:59 <asettle> Hi, I'm Alex. I like long walks on the beach, online shopping, and really hate long sentences.
14:26:15 <asettle> rosmaita: why but of course! Happy to come help.
14:26:17 <sigmavirus> oh we've got run on sentences in our docs
14:26:24 <asettle> sigmavirus: ugh
14:26:30 <asettle> Well, we'll come up with a plan :)
14:26:31 <sigmavirus> yw
14:26:32 <hemanthm> o/ asettle
14:26:32 <rosmaita> well, you can't beat an intro like that
14:26:55 <asettle> I figure if I just let my personality fly via text, actually meeting me in person is 10% less frightening.
14:27:18 <asettle> In all seriousness, I'll be taking a look at the glance docs, reviewing what you guys have, and coming up with an action plan
14:27:28 <sigmavirus> Having never met asettle in person despite having worked with her for ~3 years, I cannot confirm this
14:27:39 <asettle> sigmavirus: I always forget that.
14:27:47 <asettle> I've hung out with rosmaita for dinner so he's welllll aware :p
14:28:29 <jokke__> asettle: \o
14:28:33 <asettle> But, if anyone is interested in getting a bit more involved and has ideas about the way 'docs should look like' - hit me up
14:29:04 <asettle> I'm happy to discuss options, one shoe size doesn't fit all :)
14:29:06 <rosmaita> it will be great for us to know the directions docs are going
14:29:24 <asettle> I can definitely let you know we have some big movements coming up. Some renewed focus on HA and operations.
14:29:34 <asettle> And some tech debt to be *removed*.
14:29:47 <sigmavirus> asettle: I'll be happy to delete docs for you =P
14:29:54 <asettle> We'll be focusing heavily on our install guides and user/admin after that. So we'll want glance and other projects to be sparkly.
14:29:55 <rosmaita> awesome ... we need to get a handle on what you expect from the glance team
14:30:09 <asettle> sigmavirus: dude don't take this from me, I am literally too excited.
14:30:10 <asettle> :p
14:30:15 <sigmavirus> :D
14:30:20 <rosmaita> ok, so this should be a fun and informative session at the PTG!
14:30:23 <asettle> Hope so!
14:30:36 <rosmaita> ok, moving along
14:30:42 <rosmaita> #topic priorities
14:30:54 <rosmaita> key things will be:
14:30:59 <rosmaita> testing RC-1
14:31:14 <rosmaita> nominating bugs for ocata-rc-potential
14:31:23 <rosmaita> and then working on said bugs if htey are approved
14:31:34 <rosmaita> but testing RC-1 is key
14:31:42 <rosmaita> so that you can find some bugs to work on :)
14:32:12 <rosmaita> anything else we should consider?
14:33:19 <rosmaita> guess not
14:33:24 <rosmaita> #topic open discussion
14:33:59 <rosmaita> i will be going to the api-wg meeting at 16:00utc to discuss the situation with https://bugs.launchpad.net/glance/+bug/1656183
14:33:59 <openstack> Launchpad bug 1656183 in Glance "Delete tags return 200 status code but api-ref says 204" [High,In progress] - Assigned to Ian Cordasco (icordasc)
14:34:22 <hemanthm> gate failed on a rolling upgrade patch :(
14:34:25 <sigmavirus> rosmaita: the situation on that is quite cut and dry
14:34:31 <rosmaita> hoping to get some closure and then ocata-rc-potential that bug
14:34:40 <sigmavirus> either we want to be part of the cross-project api stability tags or we don't
14:34:49 <sigmavirus> If we don't, we can do whatever we want to fix up v2
14:34:57 <sigmavirus> hemanthm: link?
14:35:15 <hemanthm> https://review.openstack.org/#/c/392993/
14:35:20 <sigmavirus> Thank you :)
14:35:28 <rosmaita> sigmavirus: it depends on what that tag is going to mean, really
14:35:50 <sigmavirus> rosmaita: right, that's still not set in stone
14:36:06 <sigmavirus> tl;dr, we'd be able to do this if we had real microversions
14:36:20 * sigmavirus shrugs
14:37:30 <jokke__> sigmavirus: which is even more f'd up :|
14:38:06 * nikhil has to leave
14:38:14 <sigmavirus> jokke__: no it's not actually
14:38:15 <nikhil> have a nice day folks.
14:38:25 <rosmaita> bye nikhil
14:38:30 <sigmavirus> People who have had programmed in a 200 response code, would then be able to stick to a version that uses that
14:38:40 <sigmavirus> Meanwhile people who never did that, would get the *correct* code
14:39:30 <rosmaita> yeah, but if those people who want 200s ever want any other features past that microversion, they'll have to do somethign anyway
14:39:47 <sigmavirus> rosmaita: right, but they get to do that when they want
14:40:02 <sigmavirus> And when they change version they acknowledge something tiny may have changed (e.g., a status code)
14:40:18 <sigmavirus> But we have a vocal minority that is very opposed to microversions that do not provide reasoning against it
14:41:05 <sigmavirus> We frequently deny the user visible value in them, and frankly, I'm tired of the situation where we're bickering with other teams over tiny changes like this
14:41:52 * sigmavirus throws his hands up and walks away
14:42:28 <rosmaita> i guess my question is, how long do we have to support "old" microversions?
14:42:38 <rosmaita> 2 cycles and then we can remove them?
14:43:02 <sigmavirus> rosmaita: I don't think that's defined
14:43:49 <sigmavirus> And guess what, this is a topic for a cross-project goal in Queens iirc so we could influence that if we were to participate in those discussions
14:43:59 <jokke__> sigmavirus: I've explained numerous times why I'm against them
14:44:41 <sigmavirus> jokke__: I've never seen you provide reasoning beyond "they're terrible and I'll quit if we use them"
14:44:56 <sigmavirus> So perhaps putting together your reasoning in a durable format, e.g., a mailing list post on this topic would be valuabe
14:45:21 <sigmavirus> (valuable as well)
14:46:00 <rosmaita> or maybe let's discuss this at the PTG
14:46:20 <sigmavirus> rosmaita: durable means available for all Glance members, not just those whose companies are sending them to the PTG
14:46:21 <rosmaita> we'll need to formulate a position anyway if we want to have input into the Queens community goal
14:46:53 <rosmaita> i think it would be helpful to have a discussion first, then take it to the ML
14:48:22 <rosmaita> anyway, if we do discuss at the PTG we'll have notes on an etherpad that can be sent to the ml
14:49:29 <rosmaita> hemanthm: so was that gate failure because of us, or did it just happen to us?
14:50:47 <hemanthm> rosmaita: not because of us
14:51:10 <hemanthm> this showed up last night too
14:51:10 <rosmaita> well, that's ... nice
14:51:38 <rosmaita> looks like discussion has tailed off
14:51:58 <rosmaita> ok, let's stay tuned in #openstack-glance for RC-1 news
14:52:26 <rosmaita> and that's all for today ... unless anyone has something to say?
14:53:10 * jokke__ will be in Fosdem this weekend if anyone else happens to be there and wants to meet up :)
14:53:54 <rosmaita> i like how the first thing they mention on the web page is "beer"
14:54:27 <jokke__> ++
14:54:41 <dharinic> I had a Q on this stable/newton proposed backport: https://review.openstack.org/#/c/417197/
14:55:15 <dharinic> Jenkins was failing repeatedly on the releasenote. Not sure as to why.
14:55:55 <dharinic> http://logs.openstack.org/97/417197/3/check/gate-glance_store-releasenotes/762764f/console.html#_2017-01-31_17_26_32_410254
14:56:50 <alex_bash> Looks like translations failure
14:57:11 <alex_bash> 'Translations exist and locale_dirs missing in source/conf.py'
14:57:31 <dharinic> yeah, but this is cherry picked. So was not sure ..
14:58:47 <rosmaita> let's look some more in #openstack-glance ... we're just about out of time
14:59:18 <dharinic> Sure. :)
14:59:23 <rosmaita> #endmeeting