07:57:26 <ttx> #startmeeting ptl_sync
07:57:27 <openstack> Meeting started Tue Sep 30 07:57:26 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:57:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:57:30 <openstack> The meeting name has been set to 'ptl_sync'
07:57:48 <ttx> #topic Nova
07:58:02 <ttx> #link https://launchpad.net/nova/+milestone/juno-rc1
07:58:13 <mikal> Yep
07:58:21 <ttx> mikal: I count 5 bugs left
07:58:28 <mikal> When I went to bed on Friday, I think all of those remaining bugs had fixes propsed
07:58:33 <mikal> Obviously they haven't merged
07:59:01 <mikal> How do you want to proceed here
07:59:08 <mikal> Walk through the five and discuss the state of each?
07:59:10 <ttx> hard to blame the gate, it's empty this morning
07:59:15 <ttx> mikal: yes please
07:59:17 <mikal> Oh, I'm not
07:59:25 <mikal> I was off sick over the weekend, and am explaining my lack of state
07:59:28 <mikal> Ok, so...
07:59:33 <mikal> #link https://bugs.launchpad.net/nova/+bug/1373950
08:00:15 <mikal> The fix at https://review.openstack.org/#/c/124063/ proposes to "roll forwards" instead of revert
08:00:21 <mikal> Which I think is the wrong call at this point in the release
08:00:30 <mikal> It also doesn't link to the alternate patch
08:00:39 <johnthetubaguy> morning
08:00:44 <mikal> johnthetubaguy: hey
08:00:49 <mikal> Just walking through the bugs left in rc1
08:00:52 <ttx> yeah, couln't find it
08:00:54 <mikal> We're on the first one still
08:00:59 <ttx> (alternate patch)
08:01:00 <johnthetubaguy> I tried to review all those yesterday
08:01:04 <mikal> https://review.openstack.org/#/c/124384/ seems to be the alternate patch
08:01:11 <johnthetubaguy> basically, fix it, or revert it
08:01:18 <johnthetubaguy> there are two fix it patches I think
08:01:44 <ttx> and it's gating
08:01:53 <mikal> johnthetubaguy: I see two reverts on the bug, but only one "fix" patch?
08:01:58 <mikal> johnthetubaguy: I think its too late for a fix
08:02:02 <mikal> I think we _have_ to revert
08:02:18 <mikal> Given the bug is "this implementation doesn't make sense"
08:02:30 <johnthetubaguy> let me check those patches, yeah
08:02:40 <mikal> Nikola has WIP'ed his reverts
08:03:06 <ttx> it's going to be added to gate queue anytime now
08:03:17 <ttx> hmm, actually, it's in gate now
08:03:26 <mikal> The fix patch you mean?
08:03:30 <johnthetubaguy> I think nikola just added another RC1 bug
08:03:30 <ttx> yes
08:03:55 <mikal> OMG, yes now there are six
08:04:36 <mikal> Shall we drag Nikola in here to talk through this bug?
08:04:51 <ttx> why not
08:04:53 <johnthetubaguy> yeah
08:04:56 * mikal does that thing
08:04:57 <johnthetubaguy> I think we need to nuke it
08:05:04 <johnthetubaguy> there is too much up for review
08:05:07 <johnthetubaguy> its like a new feature
08:05:32 <ttx> yes, from the sound of the bug it's a bit of a shot in the dark
08:05:59 <johnthetubaguy> well, its quite well reasoned, just no chance of merging it now :(
08:06:11 <mikal> Hi ndipanov
08:06:12 <ndipanov> o/
08:06:15 <mikal> Thanks for joining us
08:06:19 <ndipanov> np
08:06:23 <mikal> We're just walking through the remaining RC bugs for juno
08:06:30 <mikal> https://bugs.launchpad.net/nova/+bug/1373950 is the current victim
08:06:37 * ndipanov looks
08:06:39 <mikal> The serial console stuff
08:06:42 <ndipanov> ah yes
08:06:49 <ndipanov> so I like sahid's fix
08:06:54 <ndipanov> no reason not to ship it imho
08:07:01 <mikal> I feel given we're meant to release like today, that its too late to roll forwards
08:07:08 <johnthetubaguy> how can we merge it yesterday, is the issue really
08:07:30 <ndipanov> mikal, well one patch failed CI
08:07:45 <ndipanov> and the other one has a -1 from Jay but I responded to that
08:07:45 <mikal> ndipanov: what patches are needed to roll forwards?
08:07:50 <mikal> The bug doesn't make that obvious
08:07:51 <ndipanov> one sec
08:07:58 <ttx> mikal: if https://review.openstack.org/#/c/124384 is all thgere is to it, it's closer to roll forward than revert
08:08:14 <ttx> or is there more ?
08:08:17 <ndipanov> https://review.openstack.org/#/c/124385/ and the one it depends on
08:08:28 <ndipanov> which was approved but failed jenkins
08:09:18 <mikal> There are five patches in that topic on gerrit though
08:09:21 <johnthetubaguy> ndipanov: did you see the following three patches?
08:09:22 <mikal> https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bug/1373950,n,z
08:09:27 <ttx> Oh, it's a patchseries of 5
08:09:33 <johnthetubaguy> looks like there are a load of bugs around exceptions too
08:09:35 <ndipanov> oh wow I missed that
08:09:42 <ttx> mikal: agree it's very featury
08:09:45 <johnthetubaguy> ndipanov: me too till just now
08:10:14 <johnthetubaguy> ndipanov: I think we have to nuke the broken thing, and get it up for review again in a week
08:10:18 <ndipanov> can you guys five me a sec
08:10:34 <ttx> johnthetubaguy: +1
08:10:36 <mikal> johnthetubaguy: I agree, but let's give ndipanov a sec
08:10:39 <ndipanov> I think the first 2 patches are enough but want to confirm
08:10:48 <johnthetubaguy> ndipanov: gotcha
08:10:56 <ndipanov> I think the rest was just nova reviewers reviewing
08:10:58 <ttx> maybe we can look at the others, that will give us a better idea of how far we are from rc1
08:10:59 <johnthetubaguy> lets go to the next one
08:11:08 <mikal> Ok, fair enough
08:11:14 <ttx> which may affect our final decision
08:11:24 <mikal> #link https://bugs.launchpad.net/ironic/+bug/1310135
08:11:54 <ttx> https://review.openstack.org/#/c/124162/ ?
08:12:27 <johnthetubaguy> I guess, this is new since I last looked at the list
08:12:28 <mikal> Yeah, that seems to be the only outstanding patch in that bug
08:12:40 <ndipanov> so just after looking at the next patch in the series it is absolutely not critical
08:12:52 <ndipanov> plus it actually does not reference the bug
08:12:58 <johnthetubaguy> ndipanov: its just tidying up error cases?
08:13:16 <ndipanov> yeah needlesly imho - I want to -1 it :)
08:13:27 <ndipanov> so if we just slam in the first 2 we can call it a bug
08:13:33 <ttx> ndipanov: so it's a series of 4 ?
08:13:50 <ndipanov> 2
08:13:59 <ndipanov> only first 2 patches are relevant to the bug
08:14:00 <mikal> ttx: I think he's saying its a series of two with some random stuff on the end
08:14:06 <ndipanov> yes
08:14:07 <ttx> ah ok
08:14:08 <ndipanov> this
08:14:21 <mikal> Are both of those two approved?
08:14:25 <mikal> Only the first is, right?
08:14:41 <ndipanov> mikal, yes
08:14:47 <johnthetubaguy> I need to get my head around Jay's API comment, but the other could be approved soon
08:14:50 <ndipanov> the second one has a -1 from jay
08:14:54 <mikal> For clarity, what other one needs to merge?
08:14:58 <ndipanov> but I think he missunderstood it
08:15:11 <johnthetubaguy> ndipanov: next one on the list we need to approve too: https://review.openstack.org/#/c/110319/
08:15:30 <ndipanov> so:
08:15:40 <ndipanov> https://review.openstack.org/#/c/124384/
08:15:44 <ndipanov> and
08:15:50 <ndipanov> https://review.openstack.org/#/c/124385/
08:15:55 <ndipanov> is needed for the bug
08:16:00 <johnthetubaguy> ndipanov: sorry, that was a different list, the rc1 list
08:16:02 <ndipanov> all else is cleanup
08:16:07 <mikal> And 124384 is approved
08:16:13 <ttx> and gating
08:16:29 <mikal> 124385 is only 15 lines of delta
08:16:50 <mikal> And only 1 line of actual code change, the rest is test implications
08:17:05 <mikal> Oh I lie
08:17:06 <johnthetubaguy> mikal: I just getting my head around if I like it or not
08:17:09 <mikal> The serial proxy as well
08:17:24 <ttx> also I think it's fine to change now, since the serial stuff is new iiuc
08:17:27 <ndipanov> it removes the web option so we don't attempt to serve static content as there is non
08:17:33 <ttx> whereas fixing postrelease would be a pita
08:17:37 <ndipanov> ttx, yeah
08:17:45 <johnthetubaguy> ttx: thats a good way of looking at it
08:17:46 <ndipanov> my point exactly hence the critical bug
08:18:03 <mikal> johnthetubaguy: I think I'd be ok with +2'ing that patch, what about you?
08:18:06 <ttx> I vote for pushing it in rc1
08:18:10 <johnthetubaguy> ndipanov: I don't disagree, its just where we draw the line
08:18:14 <johnthetubaguy> mikal: yeah, I think so
08:18:17 <ttx> and if it's a big bag of fail, we nuke it in rc2
08:18:19 <johnthetubaguy> mikal: do it
08:18:27 <mikal> johnthetubaguy: wanna +2 and +A then?
08:18:30 <ndipanov> johnthetubaguy, btw I acked that patch
08:18:39 <johnthetubaguy> mikal: I figured I would let you do that
08:18:40 <ndipanov> ttx, it is a big bag of fail ...
08:18:44 <ndipanov> :)
08:18:47 <mikal> I live having three +2's there, it makes it clear we talkeda bout it
08:18:54 <johnthetubaguy> OK
08:19:01 <mikal> But sure, I can +A if you want
08:19:29 <mikal> So, sounds like bug 1373950 is not a big problem for us now
08:20:22 <ttx> next?
08:20:37 * mikal was just waiting for the +A to appear before moving on
08:20:44 <johnthetubaguy> mikal: I went all "english" on jay with an appology, and felt better about it
08:20:45 <mikal> Ok, back to bug 1310135
08:21:04 <ttx> so is that just https://review.openstack.org/#/c/124162/ ?
08:21:06 <mikal> That needs https://review.openstack.org/#/c/124162/2
08:21:19 <mikal> Yes, with Jay's -1 having ben addressed as a misunderstanding
08:21:26 <mikal> But no +2's yet
08:21:28 <ttx> so can be overruled imho
08:21:42 <mikal> Agreed. I think johnthetubaguy and I should agree to review that one after the meeting
08:21:50 <johnthetubaguy> sure
08:21:54 <mikal> Move on?
08:21:58 <ttx> yesd
08:22:04 <mikal> #link https://bugs.launchpad.net/nova/+bug/1349888
08:22:15 <johnthetubaguy> next one I think is good
08:22:25 <ttx> https://review.openstack.org/#/c/110319/ gating
08:22:26 <johnthetubaguy> https://review.openstack.org/#/c/114548/
08:22:30 <mikal> Its approved, so I asume in the gate
08:22:38 <johnthetubaguy> oh wait, wrong order
08:22:49 <ttx> johnthetubaguy: refresh
08:22:54 <mikal> Its my fault
08:22:59 <johnthetubaguy> lol
08:22:59 <mikal> I opened the tabs before the list changed
08:23:10 <mikal> Bug 1349888 has https://review.openstack.org/#/c/110319/
08:23:14 <mikal> Which is approved and gating
08:23:21 <mikal> So let's move on from it
08:23:29 <mikal> #link https://bugs.launchpad.net/nova/+bug/1357372
08:23:57 <ttx> https://review.openstack.org/#/c/114548/
08:23:59 <mikal> Ahhh, garky pinged me about this one earlier today
08:24:04 <mikal> My -1 has been addressed
08:24:05 <johnthetubaguy> https://review.openstack.org/#/c/114548/
08:24:06 <ttx> needs 2nd +2
08:24:10 <mikal> So, I can change that to an approve
08:24:14 <johnthetubaguy> cool, thanks
08:24:24 <ttx> potential security issue, but that won't block the bug being fixed anyway
08:24:30 <ttx> ack
08:24:34 <mikal> Ok, approved
08:24:38 <mikal> So now gating (ish)
08:24:43 <ttx> next
08:24:48 <mikal> #link https://bugs.launchpad.net/nova/+bug/1359138
08:25:11 <mikal> https://review.openstack.org/#/c/118595/
08:25:19 <mikal> Basically unreviewed?
08:25:22 <johnthetubaguy> OK, so I reviewed that, its super close
08:25:22 <ttx> same case, probably a security issue
08:25:41 <ttx> so would trigger a rc2 if we left it out
08:25:41 <mikal> johnthetubaguy: I don't see youre review on 118595?
08:26:04 <johnthetubaguy> see patchset 6
08:26:26 <mikal> Ah, I see
08:26:43 <mikal> Ok, so that's another one johnthetubaguy and I promise to review?
08:26:56 <johnthetubaguy> sure, although that list is getting big agin
08:27:04 <johnthetubaguy> i just +2ed it though
08:27:07 <mikal> Well, there's two we've promised to review so far
08:27:17 <mikal> So waht was the one which got added while we were in this meeting?
08:27:23 <johnthetubaguy> ndipanov: https://review.openstack.org/#/c/118595/7 if you have a sec
08:27:31 <ttx> I think those are all in the same timeframe, so probably not delaying anything
08:27:46 <mikal> Ahhh, here it is
08:27:48 <mikal> #link https://bugs.launchpad.net/nova/+bug/1374902
08:27:53 * ndipanov looks
08:27:54 <ttx> especially if we can enqueue them while queue is empty
08:27:55 <mikal> The last one in our list
08:28:02 <ttx> https://review.openstack.org/#/c/124612/
08:28:19 <mikal> Fix needs one more review
08:28:20 <johnthetubaguy> I promised to review that
08:28:26 <mikal> I can tto
08:28:28 <mikal> Too even
08:28:36 <mikal> So, we have three bugs which are gating
08:28:40 <mikal> And three where we need to review the fix
08:28:51 <mikal> But I think we could knock out those reviews really quickly if needed
08:29:02 <mikal> So, I think we could have all of these bugs gating with say an hour
08:29:10 <ttx> mikal: when you're satisfied with the state of master, you should push something like https://review.openstack.org/#/q/status:open+branch:master+topic:open-kilo,n,z on top of nova master
08:29:18 <ttx> and I'll cut the branch from the previous commit
08:29:26 <ndipanov> mikal, can you post the reviews I'll look at them
08:29:37 <mikal> ndipanov: sure, in a sec
08:29:53 <mikal> ttx: as in just ptl fiat a +A on a patch like that?
08:30:01 <johnthetubaguy> ndipanov:  mikal: yeah, over in #openstack-nova and we can pile on
08:30:02 <ttx> yes, that's fine
08:30:08 <mikal> Or you'll use the dependant sha from gerrit?
08:30:10 <ttx> serves as sugnoff
08:30:13 <ttx> signoff
08:30:38 <ttx> dependant sha ?
08:30:39 <mikal> Ok, so do self-approve in gerrit so it merges?
08:30:57 <mikal> The gerrit review will have a parent sha
08:31:05 <ttx> mikal: I can also push the change and you just -2 it until you're ready to +2/APRV it
08:31:08 <mikal> I'm just clarifying that I should self merge that change
08:31:11 <ttx> let me do that
08:31:16 <mikal> Ok, that sounds better
08:31:21 <mikal> In case I fat finger it or something
08:31:31 <ttx> just a sec
08:32:14 <ttx> hah, first nova repo clone on my new laptop. Stay put.
08:32:19 <mikal> Heh
08:32:34 <ttx> mikal: anything else ?
08:32:46 <ttx> would be good to keep an eye on the rc1 list and make sure nobody adds stragglers
08:33:03 <ttx> also you can start using juno-rc-potential tag
08:33:03 <mikal> Yep, I can do that until I go to sleep
08:33:12 <mikal> I will hand off to johnthetubaguy when I go night night
08:33:17 <ttx> for stuff that could be interesting to backport in case we do an RC2
08:33:20 <johnthetubaguy> cool, I will keep an eye out
08:33:27 <mikal> But I'd like to stay up for these last merges if possible
08:33:32 <mikal> It depends how horribly the gate fails us
08:33:34 <ttx> I think we are on track for a RC1 in less than 24 hours
08:33:39 <mikal> Yay!
08:33:43 <johnthetubaguy> mikal: you going to email the list about the tag, and open of specs, once we cut?
08:33:58 <mikal> johnthetubaguy: so, there's some paperwork to do before we open specs
08:34:07 <mikal> johnthetubaguy: but I will mail about the cutting of rc1 once we're ready
08:34:20 <mikal> johnthetubaguy: jogo wants to chagne the spec template for kilo for example
08:34:34 <ttx> https://review.openstack.org/124981
08:34:39 <johnthetubaguy> mikal: yeah, I was wondering what we were going to change about that
08:34:40 <ttx> mika: pleas e-2 ^
08:35:18 <mikal> ttx: done
08:35:20 <mikal> Thanks
08:35:43 <ttx> great
08:35:49 <ttx> anything else ?
08:35:49 <johnthetubaguy> cool, review time
08:35:57 * ttx grabs some coffee
08:35:57 <mikal> ttx: I think we're good for now?
08:36:02 <ttx> mikal: yes we are
08:36:21 <johnthetubaguy> ttx: enjoy the coffee
08:36:28 <mikal> johnthetubaguy: let's move this over to openstack-nova then, as this is being meeting logged
08:36:29 <ttx> mikal: also, anythig that makes it before that commit will obviously be in
08:36:40 <ttx> we just won't wait on it to cut
08:36:42 <mikal> Yep, I will send an "approve nothing" to the list now
08:36:52 <johnthetubaguy> mikal: thanks
08:36:54 <mikal> Unless you think that's overkill
08:37:02 <ttx> that may be overkill
08:37:29 <mikal> Ok, I shall calm down then
08:37:32 <ttx> things which make it while we wait for the last blockers are generally fine
08:37:40 <ttx> unless they are the first of a 10-patch series
08:37:41 <mikal> I don't think much is being approved anyways from the state of the gate
08:38:05 <johnthetubaguy> yeah, its the UK morning
08:39:08 <ttx> oh, let me check translations status
08:39:35 <ttx> not too bad, last one merged on Sep 26
08:40:02 <ttx> mikal: you may want to approve https://review.openstack.org/#/c/124295/ to have fresh ones
08:40:07 <ttx> in the rc
08:41:08 * mikal looks
11:44:55 <eglynn> ttx: knock, knock ... ready when you are
11:46:35 <ttx> #topic Ceilometer
11:46:40 <ttx> eglynn: o/
11:46:46 <eglynn> #link https://launchpad.net/ceilometer/+milestone/juno-rc1
11:47:01 <eglynn> so we're looking in good shape to go with that
11:47:19 <ttx> If you merge https://review.openstack.org/#/c/124958/ then I'll tag RC1 on the previous commit
11:47:57 <eglynn> cool, that's approved
11:48:16 <ttx> great, will cut proposed/juno and tag rc1 once that's gets in
11:48:31 <eglynn> excellent :)
11:49:02 <ttx> I don't think there is much more to discuss
11:49:11 <ttx> Oh, final summit slot allocation perhaps
11:49:31 <eglynn> yeah that would be good to know
11:49:35 <ttx> 6 scheduled slots + a full-day meetup on Friday
11:49:57 <ttx> I'll publish the layout this week
11:50:24 <eglynn> OK, I presume there's an across-the-board cut of circa 33% of the ATL slots per project
11:51:01 <ttx> in general yes. there is also an adjustment based on project activity
11:51:36 <eglynn> a-ha, k ... activity == number of BPs landed in juno?
11:51:58 <ttx> rough metric based on number of reviews/commits/patchsets/BPs yes
11:52:09 <ttx> to try to be fair
11:52:36 <ttx> only 6 programs got a full-day meetup, too
11:53:15 <eglynn> fair enough, sounds reasonable
11:53:20 <eglynn> I'll bring that info back to the team
11:53:43 <ttx> ok, questions at that point ?
11:53:51 <ttx> any topic for the meeting tonight ?
11:55:23 <eglynn> well, the relatively low number of PTL nominations is a concern
11:55:29 <eglynn> ... but probably shouldn't be discussed til after the cinder & tripleO elections play out
11:56:12 <eglynn> ... so I'll punt that to a later discussion
11:57:33 <eglynn> that's it from me
12:06:22 <ttx> ack
12:06:34 <ttx> SergeyLukjanov: I assume you're not around
12:15:46 <ttx> dhellmann: ready when you are
12:15:52 <dhellmann> ttx: o/
12:15:53 <ttx> #topic Oslo
12:16:08 <ttx> dhellmann: I think we are doe as far as Oslo is concerned. Any remaining question ?
12:16:11 <ttx> done*
12:16:24 <dhellmann> we have one bug for which we will need a patch release of oslo.db soon
12:16:39 <ttx> ok
12:16:52 <dhellmann> #link https://bugs.launchpad.net/oslo.db/+bug/1374497
12:17:15 <dhellmann> I'll need to get you to make the branch, I think, since I didn't seem to have permissions when we tried that for the incubator
12:17:48 <ttx> so how do you want to do that... on master or on a stable/juno branch ?
12:18:08 <dhellmann> we'll merge the fix on master and then backport to stable/juno
12:18:16 <dhellmann> I guess you could go ahead and create the branch now, let me find the hash
12:18:25 <ttx> yes I can do that probably
12:18:34 <ttx> I'll create a juno task on the bug as well
12:18:46 <dhellmann> ooo, how do you do that?
12:18:56 <ttx> arh, wait
12:19:36 <ttx> I need to adjust "version under development" for solo.db first
12:20:06 <ttx> when you get a chance you should set "development focus" to kilo for all oslo things :)
12:20:10 <dhellmann> it looks like 1.0.1 was our last release, so we would want to branch from that point so we can make 1.0.2
12:20:13 <dhellmann> ok, I'll do that
12:20:25 <ttx> that allows to create backport tasks for juno
12:20:41 <ttx> like that: https://bugs.launchpad.net/oslo.db/+bug/1374497
12:21:02 <ttx> we alsoprobably want to create a milestone target for oslo.db
12:21:18 <dhellmann> ok, after that's done, where do I click to add the juno task?
12:21:23 <ttx> next-juno ? or some version number?
12:21:37 <ttx> do you have "target to series" below the bug tasks ?
12:21:38 <dhellmann> let's call it next-juno and let the script rename it
12:21:49 <dhellmann> ah, I see that now
12:21:50 <ttx> the script might tag off master though
12:22:00 <dhellmann> oh, true
12:22:06 <dhellmann> ok, let's call it 1.0.2 then
12:22:12 <ttx> ok creating
12:22:54 <ttx> so that way it's clear you need to backport
12:23:00 <ttx> https://bugs.launchpad.net/oslo.db/+bug/1374497
12:23:05 <dhellmann> yeah, I wanted to do that yesterday but didn't know how
12:23:49 <ttx> I think it may be simpler to do it by hand for a 1.0.2 (tag and fixrelease the only bug)
12:23:49 <dhellmann> it looks like the master version of the patch is committed, so if you make the branch I think we can get that release done today
12:23:59 <dhellmann> yeah, I'll do all of the lp stuff by hand
12:24:04 <ttx> oh, branch. right.
12:24:30 <ttx> which commit should I start from ?
12:24:47 <dhellmann> the one tagged 1.0.1 is 2849f1bdca0c39b342d434c06cdc23dc6cf946f4
12:25:27 <ttx> dhellmann: http://git.openstack.org/cgit/openstack/oslo.db/
12:25:30 <ttx> should be all set
12:25:40 <dhellmann> excellent, thanks
12:25:55 <ttx> ok, anything else ?
12:26:16 <dhellmann> do you have an opinion on whether or not we should keep using alpha version numbers for oslo releases?
12:26:41 <dhellmann> there was a ML thread about testing libraries that has been focusing on the versioning
12:26:54 <ttx> No strong opinion. I kinda liked the wheel hack that was making alpha semi-invisible
12:27:10 <dhellmann> you and I seem to be in the minority there :-)
12:27:40 <dhellmann> that's the only thing I had to bring up
12:27:45 <ttx> so, here is an example
12:27:58 <ttx> while we were working on rootwrap 1.3
12:28:20 <ttx> there was some fix that was necessary for a cinder feature to land (required a new rootwrap filter class)
12:28:29 <ttx> we could publish an alpha and make cinder use it
12:28:40 <ttx> without affecting the others which could just wait for the final
12:29:00 <ttx> I felt like it was kind of cool, but I can survive release number inflation I guess
12:29:03 <dhellmann> that's another good case
12:29:10 <dhellmann> I've been focusing on the stable branches
12:29:36 <ttx> basically, some oslo lib changes are requested by consumers, while some others are general improvements
12:29:50 <ttx> in the first case, alphas let those pioneer projects consume that extra feature they requested
12:30:18 <ttx> while the others would consume the "general improvements" when we demm them ready and finished
12:30:23 <ttx> deem*
12:31:04 <ttx> all other things equal I think it's a good thing to have... but if that creates problems then we can do without those.
12:31:07 <dhellmann> would that work with our global requirements syncing?
12:31:42 <dhellmann> yeah, the only problems we seem to have are people not liking the fact that we're calling them alphas -- I'm not aware of any actual technical issues we've had
12:31:57 <ttx> it did work, because global would have >=1.2.0 and cinder would have >=1.3.0.0a2
12:32:11 <dhellmann> ah, ok
12:32:48 <dhellmann> well, wait, that's what I mean -- how would you make cinder's requirements different from the global list? I thought we had a check job that prevented that.
12:33:12 <ttx> hmm, I think it worked. Maybe it doesn't ;)
12:33:37 <dhellmann> something to experiment with :-)
12:33:57 <ttx> ok well, let's continue the discussion on the ml
12:34:07 <dhellmann> yeah, I just wanted to make sure you'd seen the thread
12:35:28 <dhellmann> ttx: that's all I had for today, so unless there's anything else I'm going to see about finding some breakfast
12:35:41 <ttx> go go go breakfast
12:35:44 <ttx> ttyl
12:40:58 <dhellmann> ttx: thanks, ttyl
13:59:13 <ttx> jgriffith: ready when you are
14:02:02 <jgriffith> ttx: okie
14:02:26 <ttx> #topic Cinder
14:02:41 <ttx> last time I looked you were ready
14:02:55 <jgriffith> Yeah
14:03:06 <jgriffith> holding steady
14:03:11 <ttx> you just need to approve https://review.openstack.org/#/c/124960/
14:03:15 <jgriffith> go the last VMWare patch merged last night
14:03:27 <ttx> and I'll cut the proposed juno branch from the previous commit
14:03:31 <jgriffith> Okie Dokie
14:04:09 <jgriffith> +2/A'd
14:04:28 <ttx> ok, will push soon
14:04:41 <jgriffith> great, thx as always
14:04:43 <ttx> let me know if you have something big warranting opening a RC2 window
14:04:50 <jgriffith> Will do
14:04:52 <ttx> anything to discuss at meeting ?
14:05:08 <jgriffith> Nope, not from my side
14:05:12 <jgriffith> just a push for testing
14:05:27 <ttx> jgriffith: cinder has 7 scheduled slots and a half-day meetup in paris in my proposed layout
14:05:48 <jgriffith> ttx: thnking
14:05:58 <jgriffith> I think I"m fine with that
14:05:58 <ttx> as requested after ATL, I avoided conflicts with Swift, and you don't go last for once
14:06:06 <jgriffith> particularly with the 1/2 day meetup added to it
14:06:28 <jgriffith> ttx: haha... people sure did whine about being last
14:06:39 <jgriffith> ttx: I just thought it was "best for last" type thing
14:06:52 <ttx> well, with all meetups happening on Friday you still have some activity on Friday
14:07:01 <jgriffith> Yeah... I think this is good
14:07:04 <ttx> but I got you a morning space
14:07:17 <jgriffith> It'll be interesting to see how the new format works
14:07:23 <ttx> indeed
14:07:26 <jgriffith> It'll be nice to have a morning space
14:07:32 <jgriffith> I am looking forward to it
14:07:43 <jgriffith> By Friday afternoons I"m usually pretty much toast
14:07:54 <ttx> any question ?
14:07:57 <jgriffith> none
14:08:05 <ttx> ok then, enjoy your day!
14:08:10 <jgriffith> thanks... you as well
14:08:15 <ttx> will ping you when I start tagging
14:08:24 <jgriffith> I'll be here :)
14:11:09 <ttx> dolphm: ready when you are
14:15:11 <dolphm> ttx: o/
14:15:19 * morganfainberg lurks as well.
14:15:26 <ttx> #topic Keystone
14:15:32 <ttx> we got the RC1 out this morning
14:16:00 <ttx> so now the focus is on keeping track of new bugs, especially those filed with the juno-rc-potential tag
14:16:28 <ttx> we usually open a RC2 window in case of a new release blocker (regression, security issue, etc...)
14:16:36 <dolphm> ttx: should it not deprecate the juno-rc-potential tag in favor of juno-backport-potential now?
14:16:58 <ttx> no, we use juno-backport-potential after release
14:17:05 <ttx> for stable/juno backports
14:17:15 <ttx> rc-potential are for things that may trigger a new rc
14:17:29 <dolphm> in that case, we have one new medium/high bug since RC1 https://bugs.launchpad.net/keystone/+bug/1375772
14:18:19 <ttx> err, got dropped
14:18:21 <ttx> what was the last thing you got from me ?
14:18:28 <dolphm> <ttx> rc-potential are for things that may trigger a new rc
14:18:39 <ttx> ok, you got everything then ;)
14:18:45 <ttx> questions on that ?
14:19:02 <dolphm> no, just that we have one bug since RC that potentially falls in that bucket
14:19:05 <dolphm> https://bugs.launchpad.net/keystone/+bug/1375772
14:19:25 <ttx> ok -- first step is to get it fixed in master anyway
14:19:48 <ttx> we'll let the bugs pile up for a couple days at least
14:19:58 <ttx> otherwise nobody will test the rc1
14:20:48 <dolphm> ack
14:20:52 <ttx> in other news, keystone has 7 scheduled slots and a half-day meetup in Paris
14:21:18 <dolphm> ttx: noted!
14:21:27 <ttx> I'll publish the proposed layout soon
14:21:42 <ttx> anything you'd liek to discuss at meeting later today ?
14:22:23 <dolphm> i don't believe so
14:22:31 <ttx> ok, then talk to you both later
14:22:44 <morganfainberg> ttx, thanks
14:24:30 <ttx> notmyname: you can go now if that's convenient
14:24:40 <notmyname> ttx: good morning
14:24:56 <ttx> notmyname: some bird told me you were in a meetup those days
14:25:00 <ttx> #topic Swift
14:25:00 <notmyname> :-)
14:25:06 <notmyname> east coast mornings come early
14:25:20 <ttx> notmyname: so, how close are we from a rc1 in swiftland ?
14:25:32 <notmyname> still thinking early next week
14:25:45 <notmyname> we've got 3 things we're tracking right now https://wiki.openstack.org/wiki/Swift/PriorityReviews
14:26:01 <notmyname> and we'll get at least two of them done this week
14:26:04 <notmyname> hopefully all three
14:26:36 <ttx> ok -- would be good if we could do it before end of week
14:26:45 <ttx> if not, very early next week
14:26:46 <notmyname> yup. hackathon ends on thursday :-)
14:26:51 <ttx> so that we get a full week to prove it out
14:27:09 <notmyname> today we're working on the metadata one and have a collaborative review of the ring-builder patch
14:27:39 <ttx> sounds good
14:27:51 <notmyname> err..have a review today of that patch
14:28:03 <notmyname> that "today" word is important in that sentence :-)
14:28:28 <ttx> as far as summit goes, like I told last week, you get 6 scheduled slots and a half-day meetup
14:28:34 <notmyname> sounds good
14:28:38 <ttx> I avoided the conflicts with the summit talks you have on Wed
14:28:45 <notmyname> I'll be working on getting the scheduling today
14:28:48 <notmyname> ah, thanks :-)
14:28:56 <ttx> which places the swift scheduled sessions on Thursday
14:29:08 <notmyname> ok. and then half-day on friday?
14:29:18 <ttx> yes, friday morning
14:29:25 <notmyname> ok, great
14:29:28 <ttx> will publish the proposed layout later this week
14:30:05 <ttx> questions ? things you'd like to discuss at meeting today ?
14:30:18 <notmyname> yes, one question
14:30:31 <notmyname> I saw your TC agenda email. anything I need to know about for today's TC meeting?
14:30:41 <notmyname> wrt swift
14:31:04 <ttx> not really. We need to decide if it's worth having TC meetings during the TC election season
14:31:16 <notmyname> okk
14:31:27 <notmyname> oh, just one more question
14:31:30 <notmyname> about requirements
14:31:38 <notmyname> global-requirements is frozen, right?
14:31:40 <ttx> but I think we need to make progress on the big tent questions before going into swift potential alignment on some of the "differences"
14:31:45 <notmyname> ok
14:31:48 <notmyname> agreed
14:32:24 <ttx> we can't say "adopt common release" one week, only to say that most projects should follow the swift model the next week.
14:32:32 <notmyname> heh
14:32:40 <notmyname> when does global reqs get unfrozen? oct 17?
14:32:42 <ttx> global-requirements is frozen yes
14:32:49 <ttx> when all projects do RC1s
14:32:53 <notmyname> ah ok
14:32:58 <ttx> then we cut the stable/juno requirements branch
14:33:03 <notmyname> ok
14:33:15 <ttx> so the exact date might be under your control :)
14:33:34 <ttx> since I expect all other projects to be done in the next 2 days
14:33:41 <notmyname> swift will need a new version of eventlet very soon. not for juno, but asap to keep dev work flowing
14:33:52 <notmyname> ok :-)
14:34:11 <ttx> I don't think you'll have to wait long between your RC1 and that requirement unfreeze
14:34:15 <notmyname> ok
14:34:30 <ttx> notmyname: ok then, have a good hackathon
14:34:39 <notmyname> thanks
14:34:57 <ttx> #link Swift 2.2.0 blockers at https://wiki.openstack.org/wiki/Swift/PriorityReviews
14:35:03 <ttx> err
14:35:08 <ttx> #info Swift 2.2.0 blockers at https://wiki.openstack.org/wiki/Swift/PriorityReviews
14:35:22 <ttx> mestery: ready when you are
14:35:30 <mestery> ttx: o/
14:35:36 <ttx> #topic Neutron
14:36:22 <ttx> 5 bugs left @
14:36:25 <ttx> https://launchpad.net/neutron/+milestone/juno-rc1
14:36:33 <ttx> let's go through them
14:36:42 <ttx> https://bugs.launchpad.net/bugs/1357055
14:37:03 <ttx> not sure that qualifies as RC1 blocker
14:37:11 <mestery> I agree, and I will remove this one.
14:37:18 <ttx> critical, maybe, but can be fixed in master and/or backported
14:37:22 <mestery> Ack
14:37:30 <ttx> https://bugs.launchpad.net/neutron/+bug/1374573
14:37:45 <ttx> that one qualifies, nice regression
14:38:00 <mestery> Ack
14:38:02 <ttx> That would be https://review.openstack.org/#/c/124975/ ?
14:38:19 * mestery looks
14:38:32 <mestery> Apologies for being slow, new computer today so still sorting things out.
14:38:35 <ttx> if yes, could use some review
14:38:43 <ttx> HP computers, beh
14:38:46 <mestery> :)
14:38:50 <mestery> Actually a Mac ;)
14:38:53 <mestery> But just not setup yet
14:38:56 <ttx> even WORSE
14:39:04 <mestery> Hhahahaha
14:39:12 <mestery> So, that review is for but 1374573
14:39:19 <mestery> I'll sort that out with kevinbenton and armax today
14:39:22 <mestery> This one is a release blocker I think
14:39:29 <ttx> agreed
14:39:31 <mestery> Per discussion in the neutron meeting yesterday
14:39:35 <ttx> https://bugs.launchpad.net/neutron/+bug/1323729
14:39:36 <mestery> So hopefully we can wrap this today
14:40:05 <mestery> We would really like to land this one today, I'll sync with markmcclain on it.
14:40:06 <ttx> https://review.openstack.org/#/c/123624/ + https://review.openstack.org/#/c/123625/
14:40:55 <mestery> Last I checked, markmcclain was still doing some testing. Not sure if this is a release blocker or not though.
14:41:01 <ttx> that's the things which were moved to ML2, right ?
14:41:11 <mestery> Yes
14:41:17 <mestery> We're removing the plugins and keeping the agents
14:41:28 <ttx> I think it should be a release blocker, you don't really want to maintain that fcode for one more release :)
14:41:39 <mestery> hahahah
14:41:40 <mestery> agreed
14:41:43 <mestery> so lets leave this one
14:41:45 <ttx> https://bugs.launchpad.net/bugs/1348309
14:42:17 <ttx> so that one is a bit more mysterious
14:42:20 <mestery> Agreed
14:42:23 <mestery> There are lots of reviews on there.
14:42:25 <mestery> Like this one: https://review.openstack.org/#/c/123273/
14:42:42 <mestery> And this one: https://review.openstack.org/#/c/119253/
14:42:46 <mestery> Both need to merge to close it I think
14:42:47 <ttx> "This was a know backlog item when DVR code merged"
14:42:59 <mestery> Yeah, carl_baldwin was tracking these, and this is the last one.
14:43:39 <mestery> Let me verify with carl_baldwin today if this really is a release blocker or not.
14:43:47 <mestery> I suspect it can be backported, but I'll verify.
14:43:53 <ttx> feels like the BP did beat the FF clock but left out half the implementation to do so
14:44:00 <mestery> Could be yes :)
14:44:14 <ttx> ok, and the last one:
14:44:19 <ttx> https://bugs.launchpad.net/neutron/+bug/1346444
14:44:28 <mestery> I don't know how htis one got in there
14:44:32 <mestery> It must have snuck in yesterday
14:44:55 <mestery> Yes, looks like salv added it yesterday.
14:45:01 <ttx> I think it's fine if it gets in... but I wouldn't block on it
14:45:07 <mestery> Agreed.
14:45:35 <ttx> so let's remove it from list
14:45:39 <mestery> Got it.
14:45:56 <mestery> Done
14:46:12 <mestery> Down to 3 now, much better.
14:46:14 <ttx> mestery: So.. I can post an open-kilo change that you can -2 until you're ready to tag
14:46:36 <mestery> ttx: Sounds good, thanks!
14:46:47 <mestery> ttx: Tagging the neutron release is the same as tagging the clients, right?
14:46:53 <mestery> I may have some questions for you when I get to that ;)
14:47:18 <ttx> mestery: I'll do it
14:47:23 <mestery> OK, thanks :)
14:47:30 <ttx> on the commit just before that open-kilo merge
14:47:39 <ttx> so that review serves as a signoff
14:47:44 <ttx> https://review.openstack.org/125081
14:47:55 <ttx> please -2 it for the time being
14:48:04 <ttx> so that it doesn't get accidentally merged
14:48:17 <ttx> (that's the first kilo commit basically)
14:48:29 <ttx> (we cut proposed/juno branch from the commit just before that)
14:48:30 <mestery> Done, added -2.
14:48:34 <mestery> Ack
14:48:53 <ttx> mestery: ok, hat's all I had. Let's get those stragglers in
14:49:02 <mestery> Thanks ttx!
14:49:04 <ttx> mestery: anything to discuss at meeting ?
14:49:21 <mestery> Not much from my side. I will attend, but will slightly distracted, HP has me in meetings most of the day today meeting new people :)
14:49:29 <ttx> Oh, and neutron gets 11 scheduled slots and a full-day meetup in Paris.
14:49:34 <mestery> Yay! Awesome!
14:49:41 <mestery> So, have you heard that I won't be in Paris
14:49:42 <mestery> ?
14:49:48 <mestery> My wife is pregnant and due date is November 7.
14:49:48 <ttx> no i haven't
14:49:57 <mestery> Can't risk travelign with baby due date that week.
14:50:07 <ttx> yeah, that qualifies
14:50:07 <mestery> Will rely on markmcclain and the rest of the team to run the summit for me.
14:50:09 <mestery> :)
14:50:20 <mestery> Bummed I will miss folks in person.
14:50:29 <mestery> But we have a strong team and I will rely on them in my abscense.
14:50:55 <ttx> mestery: ok, will miss you though
14:51:01 <mestery> Sam here, thanks ttx!
14:51:02 <ttx> david-lyle: ready ?
14:51:22 <david-lyle> ttx yeah
14:51:45 <ttx> #topci Horizon
14:51:49 <ttx> #topic Horizon
14:52:00 <ttx> https://launchpad.net/horizon/+milestone/juno-rc1
14:52:02 <ttx> 3 bugs left
14:52:09 <ttx> https://bugs.launchpad.net/nova/+bug/1299517
14:52:40 <ttx> Is that https://review.openstack.org/#/c/96766/ ?
14:53:01 <david-lyle> Yes
14:53:15 <ttx> ok, one more +2
14:53:21 <david-lyle> I need to do final pass on that today and it should be in
14:53:21 <ttx> https://bugs.launchpad.net/horizon/+bug/1367720
14:53:51 <ttx> blocked on https://review.openstack.org/#/c/120411
14:54:05 <ttx> which may need a nudge
14:54:19 <ttx> and https://bugs.launchpad.net/horizon/+bug/1252403
14:54:33 <ttx> which hinges on https://review.openstack.org/#/c/116596/
14:54:39 <ttx> which could also use a nudge
14:55:03 <ttx> david-lyle: I'll push a "first kilo" change, for you to approve when you're all god with juno
14:55:16 <david-lyle> Sure
14:55:17 <ttx> good*
14:55:26 <ttx> let me do that now so that you can -2 it
14:55:41 <ttx> david-lyle: anything you wanted to discuss at meeting today ?
14:56:01 <david-lyle> No we're set
14:56:31 <ttx> david-lyle: https://review.openstack.org/125088
14:56:37 <ttx> please -2 it for the time being
14:56:55 <ttx> and approve when you're all happy and all blockers are in
14:57:09 <david-lyle> -2 applied
14:57:17 <ttx> david-lyle: horizon gets 6 scheduled slots and a half-day meetup in Paris
14:57:24 <david-lyle> Excellent
14:57:48 <ttx> ok, so please get all those last reviews in... we need to cut RC1 asap now :)
14:57:54 <ttx> david-lyle: talk to you later!
14:58:00 <david-lyle> Will try to wrap today
14:58:06 <david-lyle> Later
14:59:07 <ttx> david-lyle: feel free to approve the open-kilo when ready, I'll use that as a signal that I can tag and branch.
15:34:57 <ttx> SergeyLukjanov: ready when you are
15:44:25 <ttx> zaneb: ready when you are
15:44:32 <zaneb> ttx: o/
15:44:37 <ttx> #topic Heat
15:44:51 <zaneb> it's going the right direction now :)
15:44:53 <ttx> https://launchpad.net/heat/+milestone/juno-rc1
15:44:57 <ttx> 3 bugs left!
15:45:04 <ttx> https://bugs.launchpad.net/heat/+bug/1374128
15:45:09 <zaneb> I just approved the patch for one of them
15:45:34 <ttx> do we really need to block release on that one ^
15:46:02 <zaneb> I'm not sure, but it is looking like a candidate to be dropped
15:46:29 <ttx> zaneb: it's fine to include it if it makes it in time, just maybe not worth it to block on it
15:46:40 <zaneb> the abandon/adopt one is not being worked on, so it will have to be dropped
15:46:49 <ttx> would also make a decent thing to include if we ever did another rc
15:46:57 <zaneb> the question is whether to replace it with one to disable that whole feature by default
15:46:58 <ttx> zaneb: agreed
15:47:20 <zaneb> which I started a discussion about on the ML
15:47:26 <ttx> ok
15:47:37 <ttx> let's keep that bug in as a tracker
15:47:44 <ttx> https://bugs.launchpad.net/heat/+bug/1347571
15:48:01 <ttx> that would be the one you just approved
15:48:05 <zaneb> correct
15:48:44 <ttx> zaneb: ok, so... I would untarget 1374128 (tag it juno-rc-potential instead)
15:48:57 <ttx> wait for some closure on 1301314
15:49:10 <ttx> and wait for 1347571 to make it through gate
15:49:28 <ttx> if the fix for 1374128 makes it while we wait for the other two, that's fine :)
15:50:10 <zaneb> ok, I just tagged + untargeted it
15:50:34 <ttx> Let me push an open-kilo change that you can -1 while we wait for the last fixes
15:50:38 <ttx> err -2.
15:51:54 <ttx> zaneb: please temporarily -2: https://review.openstack.org/125104
15:52:30 <ttx> when all targeted bugs are fixed, you can approve that one. It will serve as a signoff: I'll branch and tag from the previous commit in log
15:52:41 <zaneb> done
15:53:10 <ttx> OK. I think that covers everything
15:53:30 <zaneb> cool
15:53:35 <zaneb> just spoke to therve
15:53:47 <ttx> Proposed design summit layout gives Heat 7 scheduled sessions and a full-day meetup in Paris
15:53:47 <zaneb> expecting a patch within the next hour on the Barbican one
15:53:57 <ttx> zaneb: cool
15:53:58 <zaneb> excellent :)
15:54:18 <ttx> anything you'd like to discuss at meeting tonight ?
15:54:30 <ttx> questions on rc1/anything ?
15:55:01 <zaneb> so after rc1 we just wait for bugs to come in to decide whether to do further rcs?
15:55:35 <ttx> yes... we ask people to tag rc wanabbes with "juno-rc-potential" so that we reviw them
15:55:55 <ttx> a new RC window is usually triggered by some regression or some security issue
15:56:05 <zaneb> ok, cool. that's what I thought I remembered
15:56:05 <ttx> but hen we pile up a few other easy backports
15:56:19 <ttx> the idea being to fix all in master asap, and to backport during the RC window
15:56:26 * zaneb is feeling almost like a competent PTL this week
15:56:49 <ttx> you finally get it, but then we change !
15:56:57 <zaneb> lol
15:57:07 <ttx> It's to keep me on my toes I see
15:57:21 <ttx> zaneb: ok, talk to you later!
15:57:30 <zaneb> got to keep it interesting ;)
15:57:35 <zaneb> will do, cheers!
15:58:09 <ttx> SergeyLukjanov: you can go now if you're around
16:05:37 <SergeyLukjanov> ttx, I'm ready
16:05:47 <ttx> #topic Sahara
16:06:11 <ttx> One bug left https://bugs.launchpad.net/bugs/1375773
16:06:22 <SergeyLukjanov> #link https://launchpad.net/sahara/+milestone/juno-rc1
16:06:23 <SergeyLukjanov> yup
16:06:26 <ttx> gating now
16:06:27 <SergeyLukjanov> it's in the gate I think
16:06:30 <SergeyLukjanov> let me check
16:06:39 <ttx> then you canb approve https://review.openstack.org/#/c/124959/
16:07:00 <SergeyLukjanov> okay
16:07:11 <SergeyLukjanov> and you'll tag the prev. commit?
16:07:23 <ttx> yes
16:07:32 <ttx> maybe wait for that last commit to merge before approving
16:07:49 <SergeyLukjanov> ttx, yeah, it's much more safe
16:07:53 <ttx> i.e. wait for 125032 to merge before +2ing 124959
16:08:05 <ttx> I'll pick it up once it merged, and branch/tag
16:08:15 <ttx> probably tomorrow morning at this point
16:08:27 <ttx> together with cinder and nova
16:08:28 <SergeyLukjanov> yeah, gotcha
16:08:50 <ttx> then we'll pile up bugs with juno-rc-potential
16:08:54 <ttx> tag
16:09:10 <ttx> and see if we have anythiong worth the hassle of a respin
16:09:28 <ttx> if any bug is found, just fix it on kilo/master
16:09:44 <ttx> so that it's ready to backport in case we want it
16:09:54 <SergeyLukjanov> ttx, ack
16:10:00 <ttx> Questions on that ?
16:10:05 <SergeyLukjanov> we've been doning the same for icehouse release
16:10:13 <ttx> Anything you'd like us to discuss at meeting today ?
16:10:19 <SergeyLukjanov> nope
16:10:21 <SergeyLukjanov> thank you
16:10:33 <ttx> At design summit, you can count on 5 scheduled sessions and a half-day meetup
16:11:27 <SergeyLukjanov> ok, that's great
16:11:47 <ttx> ok then, talk to you later. Will ping you when I tag
16:13:15 <SergeyLukjanov> thanks
16:13:32 <ttx> #endmeeting