08:28:41 <ttx> #startmeeting ptl_sync
08:28:41 <openstack> Meeting started Tue Oct  7 08:28:41 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:28:42 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:28:45 <openstack> The meeting name has been set to 'ptl_sync'
08:28:48 <ttx> #topic Nova
08:28:58 <mikal> ttx: sorry, my son was at the hospital with an arm injury
08:29:00 <mikal> Just got back now
08:29:18 <ttx> mikal: would you prefer we wait?
08:29:28 <mikal> No, let's go now
08:29:55 <ttx> https://bugs.launchpad.net/nova/+bugs?field.tag=juno-rc-potential
08:30:16 <ttx> anything in particular that would trigger the RC2 ? Some regression ?
08:30:21 <ttx> Some embarassing fail ?
08:30:22 <johnthetubaguy> mikal: eek, nasty
08:30:30 <mikal> Nothing that I've heard about...
08:30:39 <johnthetubaguy> the libvirt one was a bit nasty
08:30:40 <mikal> johnthetubaguy: it turns out to be a bad sprain, not a break, so that's good at least
08:30:49 <johnthetubaguy> mikal: ah, some good news
08:30:56 <mikal> johnthetubaguy: what was the bug number for that one?
08:31:02 <ttx> https://review.openstack.org/#/c/126299/ was proposed for backport, I blocked it while we decide
08:31:06 <johnthetubaguy> mikal: sorry, just digging
08:31:10 <mikal> NP
08:31:17 <johnthetubaguy> ah, yeah, thats the one
08:31:29 <johnthetubaguy> lp1376307
08:31:36 <mikal> Sigh. Numa.
08:31:39 <ttx> https://review.openstack.org/#/q/branch:proposed/juno+project:openstack/nova,n,z
08:31:40 <johnthetubaguy> yeah...
08:31:46 <ttx> those are the already-proposed backports ^
08:31:55 <mikal> Ok yeah, that's a nova-doesnt-work scale bug, right?
08:32:23 <johnthetubaguy> mikal: which one is that?
08:32:35 <mikal> 126299
08:32:43 <mikal> nova-compute wont start if libvirt is too old
08:33:00 <ttx> err... some backports are not even juno-rc-potential, fixing
08:34:05 <ttx> https://review.openstack.org/#/c/126138/ doesn't realkly hjave a specific bug attached to it
08:34:07 <johnthetubaguy> mikal: so technically, 126299 only affects a subset of users, but it feels bad
08:34:29 <mikal> johnthetubaguy: well, including anyone using Ubuntu 12.04 which is still supported
08:34:35 <mikal> johnthetubaguy: even with cloud archive enabled
08:35:01 <johnthetubaguy> mikal: OK, thats quite bad
08:35:21 <mikal> So, I think that means we get to do a rc2
08:35:35 <ttx> sure, we seem to have reached critical mass in annoying bugs
08:35:45 <johnthetubaguy> yeah, I think the vmware fix should go into rc2 if we are doing one
08:35:49 <ttx> Let me open the milestone
08:35:55 <ttx> and we can discuss what goes into it
08:35:58 <mikal> Ok
08:36:00 <johnthetubaguy> cool
08:36:19 <johnthetubaguy> https://review.openstack.org/#/c/126177/ comes to mind
08:36:30 <ttx> https://launchpad.net/nova/+milestone/juno-rc2
08:36:54 <ttx> So, let's first have a look at https://bugs.launchpad.net/nova/+bugs?field.tag=juno-rc-potential
08:37:02 * mikal targets that libvirt bug
08:37:04 <ttx> top to bottom
08:37:07 <johnthetubaguy> ttx: but is already committed on trunk, what do we do to it for the milesone?
08:37:10 <mikal> Ok, lets' do that instead
08:37:28 <ttx> johnthetubaguy: you set the milestone to RC2.
08:37:51 <johnthetubaguy> ttx: ah, ok, simples
08:37:52 <ttx> until we reach release, FixCommitted means "fixed in master", and FixReleased means "fixed in master and juno branch"
08:37:55 <ttx> https://bugs.launchpad.net/nova/+bug/1373993
08:38:16 <johnthetubaguy> feels like a yes
08:38:24 <mikal> This one doesn't sound like it had an urgent need?
08:38:24 <ttx> can't hurt
08:38:30 <mikal> But yeah, can't hurt
08:38:36 <ttx> It's difficult to do post-release
08:38:47 <mikal> Agreed
08:38:50 <mikal> Ok, put it in
08:39:25 <ttx> https://bugs.launchpad.net/nova/+bug/1376307
08:39:41 <ttx> Looks like a regression
08:39:49 <johnthetubaguy> +1 lets take that
08:40:02 <mikal> Yep
08:40:12 <ttx> ok added
08:40:23 <ttx> https://bugs.launchpad.net/nova/+bug/1376368
08:40:28 <ttx> This one is a security issue
08:40:35 <johnthetubaguy> its not got a commit, so leave it I supose
08:40:40 <ttx> as long as we fix it pre-release we don't need to OSSA it, so +1 from me
08:40:50 <johnthetubaguy> well, no code though
08:41:01 <mikal> Sounds realitively easy to fix?
08:41:05 <ttx> yes should be
08:41:06 <mikal> He says without reading the code...
08:41:17 <johnthetubaguy> well, OK, I guess
08:41:20 <mikal> How long can we take to get a rc2 out the door?
08:41:25 <ttx> I think that won't delay it that much
08:41:29 <ttx> couple days
08:41:30 <mikal> Can we take a little while to get a fix for that?
08:41:34 <mikal> Ok, that's enough time
08:41:37 <mikal> Put it in
08:41:39 <johnthetubaguy> just we don't check certs, so it feels like a meta issue that revocation isn't checked, but sure
08:41:40 <ttx> +1
08:42:05 <ttx> https://bugs.launchpad.net/nova/+bug/1376492
08:42:21 <johnthetubaguy> I think we take that one
08:42:25 <ttx> regression
08:42:26 <mikal> Yep
08:42:35 <mikal> I don't agree its critical, but let's not split hairs
08:42:39 <johnthetubaguy> rigth
08:42:44 <ttx> https://bugs.launchpad.net/nova/+bug/1377447
08:43:05 <johnthetubaguy> (its critical because it broke the CI only, previous one)
08:43:09 <ttx> looks like a regression too
08:43:35 <ttx> fix looks relatively simple too
08:43:42 <mikal> 1377447 doesn't have a patch
08:43:53 <ttx> https://review.openstack.org/#/c/126144/ ?
08:44:08 <ttx> not merged in master yet, but has a patch :)
08:44:09 <mikal> Oh right, my bad
08:44:28 <ttx> upgarde bug, so +1 on my side
08:44:32 <ttx> upgrade*
08:44:39 <johnthetubaguy> yeah
08:44:39 <mikal> Yep
08:44:56 <ttx> https://bugs.launchpad.net/nova/+bug/1376945
08:45:10 <johnthetubaguy> (wonders why grenade didn't catch it, but thats for later)
08:45:30 <mikal> Take that one
08:45:38 <johnthetubaguy> +1
08:45:43 <johnthetubaguy> we broke the API, lets fix it
08:45:52 <ttx> always easier prerelease, yes
08:46:04 <ttx> https://bugs.launchpad.net/nova/+bug/1370348
08:46:36 <ttx> looks like a corner case
08:47:00 <ttx> maybe we could consider it when we do the last check on FixCommitted things
08:47:11 <ttx> to see easy/safe last-minute backports
08:47:11 <johnthetubaguy> its quite a bit change
08:47:15 <ttx> yeah
08:47:16 <mikal> Yeah, no core reviews yet
08:47:22 <ttx> not sure it would pass the "safe" bar anyway
08:47:33 <ttx> let's keep it in rc-potential list
08:47:39 <johnthetubaguy> +1
08:47:41 <mikal> Agreed
08:47:41 <ttx> https://bugs.launchpad.net/nova/+bug/1377644
08:48:15 <mikal> Failure to report an error correctly
08:48:26 <ttx> this one might be worth it
08:48:42 <ttx> espeically because of its "icehouse to juno" nature
08:48:50 <ttx> which makes it release-sensitive
08:48:54 <johnthetubaguy> yeah
08:49:03 <mikal> Although
08:49:04 <johnthetubaguy> the patch needs work mind, but yeah
08:49:10 <ttx> depends on how much the patch can make it though
08:49:11 <mikal> What should happen is we say "no, don't do that"
08:49:23 <mikal> So its not really an upgrade story apart from it crashing instead of saying no
08:49:28 <ttx> if we mark it in release notes, sure
08:49:32 <johnthetubaguy> ah, true
08:49:36 <mikal> Very small change though
08:49:42 <mikal> I say we take it if it lands in time
08:49:46 <ttx> hmm, let's keep it in rc-potential then
08:50:04 <ttx> and we'll consider the ones that get to FixCommitted in that list once we get all the targets in
08:50:11 <johnthetubaguy> sounds like someone "fixed" it by adding an exception, it should work really :(
08:50:13 <johnthetubaguy> anyways
08:50:14 <ttx> https://bugs.launchpad.net/nova/+bug/1377981
08:50:31 <mikal> Ahh this one
08:50:36 <mikal> I helped Tristan with this one last week
08:50:46 <ttx> security, so +1 from me :)
08:50:48 <mikal> Its only a problem in ssh_execute is only used in baremetal
08:50:55 <mikal> Which never passes a password on the command line
08:50:59 <mikal> So this is not a security bug in juno
08:51:02 <mikal> It is in icehouse though
08:51:06 <ttx> oh, ok
08:51:21 <mikal> I don't see a juno patch proposed either
08:51:27 <johnthetubaguy> crazy stuff, OK then
08:51:32 <mikal> I'd check with Tristan, but I don't think we need to do anything for juno with this one
08:51:46 <ttx> ok, let's keep it in -potential for now
08:52:12 * ttx removes tag from the ones we targeted to rc2 for clarity
08:53:08 <ttx> https://launchpad.net/nova/+milestone/juno-rc2
08:53:26 <ttx> I'll approve the corresponding backports
08:53:38 <mikal> Ok
08:53:40 <johnthetubaguy> cool
08:53:44 <ttx> would be good to fast-track the 1376368 and 1377447 patches
08:53:47 <mikal> I shall pay attention to the two not-fixed bugs tomorrow
08:53:54 <ttx> let's have a quick look at other FixCommitted bugs
08:53:54 <mikal> Its been a pretty long day, so I wont be doing much more tonight
08:53:58 <johnthetubaguy> I can try take a look at those now ish
08:54:06 <ttx> https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=FIXCOMMITTED
08:54:42 <mikal> We;ve already covered the first three there I think
08:55:08 <ttx> the 4th is a leftover from ancient times, I fixed it
08:55:24 <mikal> You mean 1275256?
08:55:46 <ttx> yes
08:55:47 <ttx> https://bugs.launchpad.net/nova/+bug/1370265
08:55:55 <mikal> Oh, the fix was ages ago
08:56:24 <johnthetubaguy> Date: Sat Sep 6 18:41:51 2014 +0800 ?
08:56:27 <ttx> 1370265 could make a good backport candidate
08:56:30 <mikal> I think we might want 1370265
08:56:39 <ttx> I like one-line patches
08:56:53 <mikal> ec2 is also pretty popular with some people
08:56:58 <ttx> +1 from me
08:57:03 <mikal> Agreed
08:57:10 <ttx> adding to rc2
08:57:27 <mikal> I think we can skip anything for API v3
08:57:52 * ttx skims through the rest of the list
08:58:01 <mikal> 1244918 is ancient too
08:58:23 <mikal> Ditto 1270573
08:58:34 <mikal> and 1257726
08:58:34 <johnthetubaguy> nothing massively popped out at me
08:58:45 <ttx> yeah, all the ones targeted to next or ongoing should be marked fixreleased and removed from those milestones
08:58:52 <ttx> I'll clean it up
08:59:03 <ttx> I think we are good
08:59:07 <mikal> Yeah, nothing else jumps out at me either
08:59:18 <ttx> I'll process the backports
08:59:27 <ttx> You can get the missing backports proposed
08:59:36 <ttx> (like for 1370265)
09:00:16 <mikal> How do I tell which ones have missing backports without going through them all?
09:00:28 <mikal> https://launchpad.net/nova/+milestone/juno-rc2 says "fix committed" for that one for example
09:00:38 <ttx> that means merged in master
09:00:50 <ttx> you can't tell if the backport was proposed yet or not
09:01:00 <ttx> unless you check the reviews or bug
09:01:14 <mikal> Ok, so etherpad tracking time then
09:01:27 <ttx> mikal: bah, not sure
09:01:38 <ttx> it's easy to go through the RC2 bugs and propose the missing ones
09:01:45 <ttx> and then you don't need to track it anymore :)
09:02:28 <mikal> Heh, ok
09:02:33 <johnthetubaguy> sounds like a plan
09:02:40 <mikal> Another thing for tomorrow
09:02:40 <johnthetubaguy> I was going to say add a tag, but yeah
09:02:45 <mikal> Unless johnthetubaguy beats me to it
09:02:52 <ttx> don't worry, will ping you if I miss one ( or propose it myself)
09:05:08 <ttx> OK, cleaned up stale ones from https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=FIXCOMMITTED
09:05:12 <mikal> Thanks
09:05:27 <ttx> Looks good to me
09:05:30 <ttx> Thx!
09:05:34 <johnthetubaguy> cool, which were the two we wanted reviewing now?
09:05:42 <mikal> We're done for the night?
09:05:55 <mikal> johnthetubaguy: 1376368 and 1377447
09:06:29 * ttx approves the backports that are targeted
09:06:57 <ttx> oh ,just a sec
09:07:12 <mikal> Holding
09:07:18 <ttx> What about https://review.openstack.org/#/c/126138/
09:07:50 <ttx> Looks like it's only tests, but has no clear bug linked to it, so I thought I'd rather ask
09:07:56 <johnthetubaguy> its just tests, so I guess I don't mind either way
09:08:09 <johnthetubaguy> sean through it was good, so I am willing to side with him
09:08:11 <mikal> Yeah, just tests makes sense to land I think
09:08:16 <ttx> ok, will approve
09:08:30 <johnthetubaguy> cools
09:08:32 <mikal> Cool
09:08:33 <ttx> that's all, we can discuss in your morning :)
09:08:35 <johnthetubaguy> thanks all, I will go do some reviews
09:08:37 <ttx> mikal: no TC meeting tomorrow
09:08:41 <mikal> Yay!
09:08:43 <mikal> Sleep in!
09:08:56 <mikal> I need to finish writing up my thoughts on tents
09:09:05 <ttx> camping frenzy
09:09:07 <mikal> One last release thing...
09:09:13 <mikal> When do I need to panic about release notes?
09:09:14 <mikal> Now?
09:09:29 <ttx> generally one week before release, so plenty of t... oh wait
09:09:56 <ttx> we usually work on release notes in the last week
09:10:02 <mikal> And we generally use landed blueprints and fixed critical bugs as the things to cover?
09:10:23 <mikal> http://www.stillhq.com/openstack/juno/000018.html might give me a head start...
09:10:40 <ttx> right, the essential being to cover any upgrade oddity or known bug that we won't fix
09:11:50 <mikal> Ok
09:12:02 <johnthetubaguy> mikal: yeah, often get subteams to fill in their own sections, if I remember correctly
09:12:12 <mikal> johnthetubaguy: oh, that's a good idea
09:12:25 <mikal> I also want to include the versions of things we used in CI
09:12:32 <mikal> To give operators a guide as to what we trust
09:12:39 <mikal> So I should start collecting that soon
09:12:58 <johnthetubaguy> cools
09:13:09 <johnthetubaguy> and versions in the driver CI systems
09:13:15 <ttx> https://review.openstack.org/#/q/branch:proposed/juno+project:openstack/nova,n,z on their way
09:14:38 <mikal> johnthetubaguy: yeah, third party CI included
09:17:05 <ttx> mikal: getting a recent translations in master and backporting it before RC2 wouldn't hurt, too
09:17:29 <mikal> ttx: makes sense
09:17:39 <ttx> mikal: https://review.openstack.org/#/c/125558/
09:17:45 <ttx> if you get that in, I can backport it
09:17:59 <mikal> Ok
09:18:10 <mikal> johnthetubaguy and I can review now?
09:18:23 <johnthetubaguy> mikal: I have added a +2
09:18:36 <mikal> Me tto
09:18:38 <mikal> Too even
09:18:39 <mikal> Approved
09:18:41 <ttx> I'll backport it once it's in
09:21:11 <mikal> We're done now?
09:21:16 <ttx> yep
09:21:24 <johnthetubaguy> mikal: sleep well
09:21:39 <mikal> Well, now to pack for a three day trip to Sydney
09:21:41 <mikal> But yeah
09:21:43 <mikal> Talk later
09:24:21 <johnthetubaguy> eek
10:09:28 <ttx> jraim: cutting barbican rc1 now thet the open-kilo merge is in
10:22:12 <ttx> jraim: https://launchpad.net/barbican/juno/juno-rc1
10:22:19 <ttx> redrobot: ^
11:27:30 <ttx> johnthetubaguy: would welcome your +2 on https://review.openstack.org/#/c/126520/ and https://review.openstack.org/#/c/126522/
11:27:37 <ttx> (backports from master)
11:28:38 <johnthetubaguy> ttx: I don't have +2 rights I am afraid
11:28:59 <ttx> I'll take a +1, it's just so that I don't appear to self-approve without any check
11:29:06 <johnthetubaguy> sure
11:29:17 <ttx> FTR I should have used -x while cherrypicking
11:29:43 <johnthetubaguy> ttx: I was going to say, should we list the commit has you cherry picked in the commit?
11:30:03 <ttx> johnthetubaguy: yeah, I'll redo them
11:30:20 <johnthetubaguy> ah, no worries, couldn't remember if that was still the norm or not
11:30:31 <ttx> It's better if we do
11:30:38 <ttx> But then the ChangeID is the same
11:30:44 <ttx> so I guess that works
11:31:08 <johnthetubaguy> yeah, its good to reference the commit I guess, but duno really
11:45:04 <eglynn> ttx: knock, knock ... ready when you are
11:45:13 <ttx> #topic Ceilometer
11:45:15 <ttx> ready now
11:45:25 <eglynn> bad news: I'm thinking we'll need an RC2
11:45:32 <eglynn> https://bugs.launchpad.net/ceilometer/+bugs?field.tag=juno-rc-potential
11:45:36 <ttx> you're not the only one.
11:45:41 <ttx> Let's see that
11:45:50 <eglynn> BTW the medium bug on that list was supposed to have been fixed in juno-rc1
11:45:51 <ttx> any particular bug/regression triggering it �?
11:46:29 <eglynn> the two high priority bugs on that list above
11:46:53 <ttx> yeah, saw those... ok, let's open one
11:46:55 <ttx> just a sec
11:46:59 <eglynn> also, awkwardly, it looks like we'll need to rev the ceiloclient too
11:47:10 <eglynn> for https://bugs.launchpad.net/python-ceilometerclient/+bug/1357343
11:47:35 <eglynn> (token expiry not being handled)
11:48:12 <ttx> https://bugs.launchpad.net/ceilometer/+milestone/juno-rc2
11:48:26 <ttx> OK, you can propose backports
11:48:35 <eglynn> cool, thanks!
11:48:45 <ttx> https://wiki.openstack.org/wiki/GerritJenkinsGit#Submit_Changes_in_master_to_proposed.2F.2A
11:48:53 <ttx> eglynn: let's see if anything else is worth it
11:48:57 <eglynn> on the client, what are the implication of rev'ing that this late in day
11:49:00 <eglynn> ?
11:49:27 <ttx> it's a pain for distros
11:49:38 <ttx> so it just needs to be very worth it
11:49:43 <ttx> https://bugs.launchpad.net/ceilometer/+bugs?field.status%3Alist=FIXCOMMITTED
11:50:14 <eglynn> this too I think https://bugs.launchpad.net/ceilometer/+bug/1377157
11:50:36 <ttx> yeah, was looking into it
11:50:53 <ttx> it's definitely better to post it prerelease than postrelease
11:51:24 <ttx> adding
11:51:42 <ttx> anything else worth it in that fixcommitted list?
11:52:03 <eglynn> I don't think so
11:52:18 <eglynn> on the client, I'll go ahead and cut python-ceilometerclient 1.0.12, I think it is worth is
11:52:23 <ttx> two other things...
11:52:26 <eglynn> shoot
11:52:40 <ttx> what do you think of https://review.openstack.org/#/c/126336/ ?
11:53:34 <ttx> it's an alignment with current requirements for proposed/juno, so probably worth it ?
11:53:42 <eglynn> yeah I think so
11:53:52 <ttx> ok, you can +2/APRV it then
11:54:28 <ttx> the other question is about the translations, we should take the RC respin opportunity to refresh them with latest
11:54:43 <ttx> So maybe approve https://review.openstack.org/#/c/126121/ in master
11:54:50 <ttx> then I can propose a backport for that
11:55:02 <eglynn> yep, that's fair
11:55:12 <ttx> actually I also need to backport the previous update
11:55:22 <ttx> but yeah, approve in master first
11:56:01 <eglynn> cool, I'll backport the three bug fixes to proposed/juno
11:56:20 <ttx> I'll hunt down the previous tranbslations update and get it proposed.
11:56:39 <ttx> eglynn: ok, I think we are good.
11:57:02 <eglynn> quick question ... what's the deadline for finalizing the summit design session tracks?
11:57:20 <ttx> we need the agenda set one week before summit
11:57:38 <eglynn> cool
11:58:36 <eglynn> we've already 9 proposals for the ceilo track, but I've a feeling there a few more hinding in the long grass
11:58:56 <eglynn> ... so I wanted to give it another week before deciding which topics to include
11:59:26 <ttx> you need to pick which ones you want to get advertised on the schedule, vs. the ones you can decide in the meetup
11:59:53 <ttx> eglynn: translations step 1 backport: https://review.openstack.org/#/c/126536/
12:00:03 <ttx> since I proposed it, you can +2/APRV it for me
12:00:24 <eglynn> cool, done
12:00:36 <ttx> I'll propose step 2 once it merges in master.
12:01:27 <eglynn> cool
12:01:54 <ttx> ping me when you have the other backports up, will approve them
12:02:21 <eglynn> will do, thanks!
12:06:42 <ttx> johnthetubaguy: ok, updated https://review.openstack.org/#/c/126520/ & https://review.openstack.org/#/c/126522/ (now includes cherrypicked SHA)
12:08:44 <eglynn> ttx: here are the other backports https://review.openstack.org/#/q/status:open+project:openstack/ceilometer+branch:proposed/juno,n,z
12:09:27 <ttx> eglynn: all set
12:09:34 <eglynn> thank you sir!
12:13:46 <dhellmann> ttx: ready when you are
12:13:57 <ttx> #topic Oslo
12:14:22 <ttx> dhellmann: hi!
12:14:33 <dhellmann> ttx: good afternoon
12:14:44 <ttx> Was wonering about the recent taskflow bump, and if we need to do anything about it requirements-wise
12:15:18 <dhellmann> that was primarily a bug fix, so as long as we're not capping we should be ok internally
12:15:27 <ttx> ok
12:15:49 <dhellmann> do we generally assume the distros package new versions of libs without us explicitly updating requirements?
12:16:14 <dhellmann> I guess I have been assuming that, so I'm really asking if I should :-)
12:17:32 <ttx> hmm
12:18:03 <ttx> no we can't. capping really depends how much 0.4.0 was broken
12:18:11 <ttx> if it's solving a distro corner case, then it's fine
12:18:18 <ttx> which I think is the case here
12:18:42 <ttx> basically the distros know 0.5.0 solves the issue for them so they update it
12:18:54 <ttx> while those who don't care happily live with 0.4.0
12:19:39 <dhellmann> yeah, I don't know if this was a corner case. The primary issue was for six.moves poor threading support, IIRC
12:20:33 <dhellmann> https://bitbucket.org/gutworth/six/issue/98/
12:20:36 <ttx> should we discuss that at the meeting later today ?
12:20:58 <dhellmann> that might be a good idea
12:21:01 <ttx> it's an all-bump or noone-bump thing -- and may trigger respins
12:21:19 * ttx wonders which project depends on taskflow right now
12:21:32 * ttx quickchecks
12:21:53 <dhellmann> looks like just cinder, but that doesn't seem right
12:23:26 <ttx> yes, I arive at same conclusion
12:23:28 <ttx> +r
12:23:47 <ttx> If it's just cinder we can discuss it with jgriffith
12:24:02 <dhellmann> ok. I posted the question in #openstack-oslo for josh
12:24:15 <dhellmann> he won't be online for a few hours, but it should be before the meeting this afternoon
12:24:18 <ttx> ok then.. anything else ?
12:24:55 <dhellmann> I need the other PTLs to provide liaisons for kilo. I was going to mention that today in case they missed the message to the ML
12:24:58 <johnthetubaguy> ttx: I am good with those nova patches, +1ed them
12:27:00 <ttx> ok, approved them
12:27:23 <ttx> dhellmann: ok, just reiterate it during the meeting
12:27:31 <dhellmann> ttx: sounds good
12:27:34 <ttx> dhellmann: I think we are good
12:27:46 <dhellmann> ttx: ok, thanks and ttyl
13:57:12 <ttx> jgriffith: ready when you are
13:58:53 <nikhil_k> ttx: thanks for adding the tag
14:04:57 <ttx> dolphm: ready when you are
14:05:05 <dolphm> ttx: o/
14:05:20 <ttx> #topic Keystone
14:05:24 <ttx> https://launchpad.net/keystone/+milestone/juno-rc2
14:05:27 <ttx> All set
14:05:29 <morganfainberg> o/
14:05:47 * morganfainberg looks
14:05:52 <dolphm> ttx: thanks for the +A's, i don't think we're missing anything
14:05:54 <ttx> dolphm, morganfainberg: would like to refresh the translations before we cut RC2 though
14:06:02 <ttx> So get https://review.openstack.org/#/c/124950/ in master
14:06:06 <dolphm> ttx: ah, alrighty
14:06:07 <ttx> and then I can backport it
14:06:11 <morganfainberg> sounds good
14:06:31 <ttx> Once that merges, unless there is a red flag, I'll cut RC2
14:06:48 <dolphm> ttx: can we regenerate it for proposed/juno?
14:07:11 <ttx> ah. hm.
14:07:21 <dolphm> ttx: otherwise line numbers may be off
14:07:30 <dolphm> ttx: and might have unused strings
14:07:30 <ttx> Been doing straight backports so far, but you're right
14:07:38 <ttx> hrm.
14:08:27 <ttx> I have no idea how we would do that though
14:08:54 <morganfainberg> ttx, i think we'd need to add a job via infra to do it
14:09:16 <ttx> Sounds like a good topic for today's meeting
14:09:33 <dolphm> morganfainberg: it'd be useful if it generally picked up any proposed/* branches
14:09:34 <morganfainberg> not sure how much work/difficult it would be... or someone might be able to run the command(s) directly to generate, just not sure what those would be
14:09:45 <morganfainberg> dolphm, yeah.
14:10:30 <dolphm> even stable/*, now that i think about it. as we backport stuff, we're going to have the same issue with translations falling out of sync
14:10:32 <ttx> hmmkay. I'll probaly hold cutting RC2s until we have a good answer for that
14:10:42 <ttx> and we can discuss it at meeting today
14:10:53 <ttx> that's of interest to david-lyle as well
14:10:58 <dolphm> ttx: ++
14:11:33 <ttx> (david-lyle: we are discussing how to refresh translations on proposed/juno without importing unused/offset translations from master)
14:12:06 <ttx> dolphm: ok, anything else ?
14:12:10 <dolphm> ttx: not from me
14:12:28 <ttx> dolphm: good ctach there!
14:12:31 <ttx> catch, even
14:13:13 <david-lyle> Our translations will be proposed to juno independently of master I believe
14:13:44 <david-lyle> Daisy set up transfer to go to juno, I believe
14:13:57 <david-lyle> *transifex
14:14:19 <ttx> david-lyle: if that's the case we would have seen proposals coming
14:14:28 <ttx> they still refresh master
14:14:52 <ttx> might be a milestone-proposed vs. proposed/juno glitch, though
14:14:58 <morganfainberg> ah
14:15:00 <morganfainberg> that might be it.
14:15:31 <ttx> we'll see
14:15:35 <dolphm> morganfainberg: know which repo the transifex proposals come from?
14:15:39 <ttx> david-lyle: ready to go now ?
14:15:57 * dolphm steps into -infra
14:16:04 <david-lyle> You are correct still going to master
14:16:22 <david-lyle> Might be based on a private fork
14:16:36 <david-lyle> Bought to take off but we can try
14:16:43 <david-lyle> About
14:17:03 <david-lyle> +1 for phone irc
14:17:10 <ttx> #topic Horizon
14:17:11 <morganfainberg> david-lyle, yay phone irc :)
14:17:36 <ttx> no RC2 window opened yet -- I think we can still wait a bit
14:17:46 <ttx> we know we'll do one , if only to update translations
14:18:04 <ttx> any critical bug that warrants us opening a RC2 window just now ?
14:18:18 <david-lyle> Sure, we have on doc patch merged that would be nice but nothing critical
14:18:38 <ttx> https://bugs.launchpad.net/horizon/+bugs?field.tag=juno-rc-potential
14:18:38 <david-lyle> We can wait on the doc patch
14:18:52 <ttx> yeah, I think that can wait for tomorrow. I want people to shake the RC1 a bit more
14:19:04 <david-lyle> I guess both doc patches have merged
14:19:10 <david-lyle> Sure
14:19:31 <david-lyle> No rush translations are slated for the 9th
14:19:40 <ttx> anything to discuss today, apart from abovementioned translations issue ?
14:19:56 <david-lyle> No, that should cover it
14:20:16 <david-lyle> You want final summit schedules when?
14:20:25 <ttx> alright then, you can take off, will talk to you tomorrow
14:20:32 <ttx> at least one week before summit starts
14:20:45 <david-lyle> Ok on target for that
14:20:54 <david-lyle> Talk to you later today
14:21:01 <ttx> until release we are a bit too busy :=
14:21:11 <david-lyle> Agreed
14:21:23 <david-lyle> Thanks
14:21:27 <ttx> jgriffith: around now ?
14:21:47 <ttx> SergeyLukjanov: around now ?
14:35:44 <ttx> mestery: ready when you are
14:36:12 <mestery> ttx: o/
14:36:17 <mestery> ttx: In neutron meeting but can multi-task
14:36:48 <ttx> #topic Neutron
14:37:02 <ttx> https://bugs.launchpad.net/neutron/+bugs?field.tag=juno-rc-potential
14:37:15 <ttx> Anything that would trigger a RC2 for sure in there ?
14:37:25 <mestery> https://bugs.launchpad.net/neutron/+bug/1357055
14:37:35 <mestery> And https://bugs.launchpad.net/neutron/+bug/1367892
14:37:41 <ttx> well, if it gets fixed, why not
14:37:54 <mestery> :)
14:38:12 <mestery> ttx: I need to talk to markmcclain today, there was some DB migration thing which we need.
14:39:00 <mestery> ttx: Otherwise, this list has grown in the 10 minutes since we discussed in the neutron meeting!
14:39:08 <mestery> So I need to verify the new ones which were added in that time by the team. :)
14:39:14 <ttx> mestery: how about we discuss opening a RC2 window tomorrow ?
14:39:22 <ttx> in the mean time, pile up fixes in master
14:39:24 <mestery> ttx: Perfect for me.
14:39:27 <mestery> ttx: Ack
14:39:31 <ttx> no need to push backports right now
14:39:32 <mestery> ttx: Anyone else doing an RC2, or are we it?
14:39:37 <ttx> only makes me -2 them
14:39:43 <mestery> :P
14:39:54 <ttx> so far keystone glance nova sahara ceilo
14:40:00 <ttx> I expect most will do one
14:40:15 <ttx> the question is, you want RC1 to live a bit before you say you'll scrap it
14:40:19 <ttx> so that it gets tested
14:40:26 <mestery> Agreed
14:41:14 <ttx> What do you think of https://review.openstack.org/#/c/126340/ ? Would make RC2 too, right ?
14:41:21 * mestery looks
14:41:36 <mestery> I think so yes
14:41:53 <ttx> hmm
14:42:10 <ttx> That would be https://review.openstack.org/#/c/122646/ in master
14:42:18 <ttx> so probably better to approve that first
14:42:22 * mestery looks again
14:42:34 <mestery> Yes, I see that one.
14:42:44 <mestery> I can rebase that patch today for master
14:42:51 <ttx> would be great
14:43:14 * mestery notes an action to do that right after this meeting.
14:43:40 <ttx> You can also review https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=FIXCOMMITTED for other juno-rc-potential baclport candidates
14:44:04 <ttx> that should be all the bugfixes that have made it master recently
14:44:12 <ttx> Pick the safe ones
14:44:16 <mestery> Agreed.
14:44:25 <mestery> It's on my list of things to do today
14:44:32 <ttx> and we'll talk tomorow
14:44:38 <mestery> Cool
14:44:42 <mestery> You know where to find me ;)
14:45:04 <ttx> I do.
14:45:45 <mestery> The firehose from starting the new job has died down a bit, so I am able to focus more this week which has helped.
14:47:55 <mestery> I'm hoping to sync with mikal this week and sort out if we can claim nova-network is deprecated in Juno now. More to come on that next week.
14:47:59 <mestery> Otherwise, that's all I've got this week.
14:49:49 <ttx> ok
15:06:10 <SergeyLukjanov> ttx, I'm here
15:06:30 <ttx> #topic Sahara
15:07:00 <ttx> https://launchpad.net/sahara/+milestone/juno-rc2
15:07:04 <ttx> SergeyLukjanov: looks all set
15:07:13 <ttx> SergeyLukjanov: was wondering about your translations update
15:07:23 <ttx> did you "adapt" it to match proposed/juno ?
15:07:35 <ttx> see recent discussion with dolphm and AJaeger in -infra
15:07:57 <ttx> because importing from master may result in line numbers drift/ extra messages
15:08:10 <ttx> so was wondering if we didn't need an extra fix there
15:08:42 <ttx> SergeyLukjanov: ^
15:09:07 <SergeyLukjanov> yeah, I'm looking
15:10:53 <SergeyLukjanov> ttx, hm
15:11:30 <SergeyLukjanov> ttx, /me need some time to ensure that it's ok
15:12:12 <SergeyLukjanov> ttx, only https://github.com/openstack/sahara/commit/dfdd0bdb23f8f70a45a9da463a8e5be73585f109 was not backported and it was before the translations update
15:12:58 <SergeyLukjanov> ttx, everything else looks good
15:14:13 <SergeyLukjanov> ttx, is there any process to pull latest translations for release?
15:15:08 <ttx> SergeyLukjanov: no
15:15:13 <ttx> we just update them at every RC
15:15:40 <ttx> they are supposed to be completed now (we said before Oct 1 originally)
15:15:52 <ttx> but then if we do new RCs we just update them
15:16:20 <ttx> SergeyLukjanov: ok, so looks like we have a winner
15:16:32 <ttx> SergeyLukjanov: I'll tag it later today, beore the release meeting
15:16:40 <ttx> since we don't have TC meeting today
15:16:43 <SergeyLukjanov> okay, thank you
15:16:53 <ttx> SergeyLukjanov: let me know if I should hold for any reason
15:17:00 <SergeyLukjanov> ttx, ack
15:17:07 <ttx> It *will* be the final unless deep shit happens
15:17:16 <ttx> so time to shake it
15:17:23 <ttx> (and check it)
15:17:28 <SergeyLukjanov> ttx, we're shaking it last two weeks ;)
15:17:53 * SergeyLukjanov needs to grab coffee...
15:18:26 <ttx> SergeyLukjanov: ok, ttyl then
15:18:34 <ttx> jgriffith: got time now ?
15:21:29 <ttx> notmyname: ready when you are
15:21:49 <mestery> ttx: https://review.openstack.org/#/c/122646/12
15:21:51 <mestery> ttx: rebased, FYI.
15:22:13 <ttx> ack, push it!
15:22:27 <ttx> shoud probably have been in RC1
15:29:15 <notmyname> ttx: here
15:31:19 <ttx> #topic Swift
15:31:21 <ttx> notmyname: o/
15:31:24 <notmyname> hello
15:31:34 <ttx> So, how is your RC1 doing so far ?
15:31:41 <notmyname> so far so good
15:31:54 <notmyname> nothing has come up yet, that I'm aware of
15:32:03 <ttx> I wanted to talk quickly about https://bugs.launchpad.net/ossa/+bug/1365350
15:32:13 <ttx> and disucss if we should backport it to stable/icehouse
15:32:26 <ttx> (or if it makes sense to backport it to stable/icehouse)
15:32:41 <ttx> since that blocks ourt releasing of an advisory right now
15:32:48 <notmyname> good question
15:33:10 <ttx> I would lean towards yes, but you know if it's an easy backport or not
15:33:22 <notmyname> I'm not sure either, but I'd lean the same way
15:33:29 <ttx> we don't necesarily need to cut a 1.13.2 release for that
15:33:39 <ttx> just make the patch available if someone is for some reason stuck on icehouse
15:33:50 <ttx> and publish it in stable/icehouse branch
15:34:17 <ttx> if you agree, I'd welcome your help (or some other Swift team member) to propose backport to stable/icehouse
15:34:28 <ttx> then we can get CVE assigned and publish advisory
15:35:03 <notmyname> ok, I'll look at how tricky a backport will be
15:35:12 <ttx> notmyname: great, thx
15:35:31 <ttx> other question is about https://review.openstack.org/#/c/126341/ -- I suppose we should ignore it ?
15:35:45 <ttx> It's the automated proposal to sync requirements to proposed/juno branch
15:35:59 <ttx> If yes, put your -2 on there as well :)
15:36:30 <notmyname> hadn't seen it yet
15:36:44 <notmyname> so what is the proposed/juno branch?
15:36:53 <ttx> it's the release branch for 2.2.0
15:37:03 <ttx> where we would do aRC2, should it be necessary
15:37:10 <ttx> while master is on kilo already
15:37:29 <notmyname> ah, got it. I hadn't realized there had been a branch instead of just a tag. I thought we only did the branch after a patch was necessary
15:37:41 <ttx> notmyname: for intermediary releases yes
15:37:48 <notmyname> ok
15:37:49 <ttx> for the final, I align with the other's process
15:38:15 <ttx> proposed/juno becomes stable/juno at release time
15:38:21 <notmyname> ok
15:38:45 <ttx> so my guess is that requirements update should know the same fate as the master ones
15:39:17 <notmyname> yes
15:39:25 <ttx> i.e. https://review.openstack.org/#/c/88736/
15:39:37 <notmyname> still waiting on that simple solver monty promised me ;-)
15:39:45 <ttx> ok, so you can -2 it to make sure I don't include it after drinking too much
15:39:50 <notmyname> yes
15:39:59 <ttx> notmyname: that's all I had
15:40:20 <notmyname> ok, great. I'll get stuff added to LP this week. and check on the backport
15:40:23 <ttx> notmyname: anything on your side ?
15:40:40 <notmyname> I'm good
15:40:47 <ttx> great, thx! Talk to you later
15:41:02 <ttx> zaneb: ready when you are
15:41:20 <zaneb> ttx: go ahead :)
15:41:26 <ttx> #topic Heat
15:41:38 <ttx> https://bugs.launchpad.net/heat/+bugs?field.tag=juno-rc-potential
15:41:57 <ttx> Anything worth respinning RCs in there ?
15:42:30 <zaneb> 1376857 is a (small) memory leak, which worries me a little
15:42:54 <zaneb> not sure what the threshold is for respinning RCs?
15:43:11 <ttx> zaneb: at the moment it's low, but it's growing fast
15:43:32 <ttx> respinning is relatively fast once we decided it
15:43:46 <ttx> zaneb: how about we let one more day of RC1 testing and we make the call tomorrow ?
15:44:12 <ttx> We'll probably do a RC2 over the requirements sync
15:44:24 <ttx> https://review.openstack.org/#/c/126339/
15:44:46 <ttx> so that you're aligned on the juno openstack/requirements values
15:44:46 <zaneb> ok, in that case I would like to get bug #1376857 in too
15:44:58 <zaneb> makes sense
15:45:14 <zaneb> and I'll check with folks about the others to see if they're needed
15:45:18 <ttx> zaneb: would you rather open the RC2 now (and start the backport) or let it be tested for one more day ?
15:45:25 <ttx> When we open a RC2 everyone stops testing RC1 :)
15:45:47 <ttx> I'm fine with either
15:45:49 <zaneb> one more day then ;)
15:46:16 <zaneb> probably you could go months without the memory leak blowing up in your face
15:46:35 <ttx> ok, that sounds good
15:47:13 <ttx> zaneb: you can review (+2) https://review.openstack.org/#/c/126339/ in the mean time
15:47:21 <ttx> I'll unblock it when we open the RC2 window
15:47:54 <zaneb> I can only +1, but it's done
15:47:56 <ttx> we'll also update the most recent translations, as that would probably be our final RC (fingers crossed)
15:48:07 <ttx> ah? /me checks perms
15:48:32 <ttx> ah https://review.openstack.org/#/admin/groups/113,members
15:48:51 <zaneb> ah, I am only in https://review.openstack.org/#/admin/groups/152,members
15:48:52 <ttx> ok fixed
15:49:09 <ttx> basically you and I can approved proposed/juno fixes
15:49:25 <zaneb> why do we have heat-milestone and heat-release groups?
15:49:43 <ttx> not sure
15:49:53 <ttx> hmm
15:49:55 * zaneb goes to update his PTL guide
15:50:02 <ttx> reelease must be to tag clients
15:50:10 <ttx> milestone to approve patches to proposed/*
15:50:24 <ttx> could probably be same group
15:50:29 <zaneb> heat-release is for stable backports
15:50:32 <zaneb> that much I know :)
15:50:50 <zaneb> yeah, seems like one group for both would be easiest
15:51:04 <ttx> bah, we'll fix that another day
15:51:10 <zaneb> :D
15:51:27 <ttx> zaneb: OK, i'll talk to you later then
15:51:37 <zaneb> ttx: cool, thank you!
15:51:42 <ttx> maybe before release meeting
15:51:57 <ttx> nikhil_k: ready when you are
15:56:46 <ttx> jgriffith: if you're around you can steal the spot now
15:57:00 <nikhil_k> ttx: hi
15:57:09 <ttx> ah, nikhil wins
15:57:14 <ttx> #topic Glance
15:57:25 <ttx> https://launchpad.net/glance/+milestone/juno-rc2
15:57:36 <ttx> Still missing 5 bugfixes in master
15:57:45 <ttx> unless we decide to not wait for them
15:57:55 * ttx brings up reviews
15:58:03 <ttx> https://review.openstack.org/122266
15:58:05 <nikhil_k> ttx: was hoping that we still have one more day
15:58:28 <ttx> Looks like this one could be approved
15:58:36 <ttx> nikhil_k: you can
15:59:12 <ttx> https://review.openstack.org/#/c/120957/
15:59:17 <ttx> needs another +2
15:59:47 <ttx> https://review.openstack.org/#/c/121188/
15:59:56 <ttx> needs two +2s so seems rather far away
16:00:14 <ttx> https://review.openstack.org/#/c/120432/
16:00:20 <ttx> is -2ed, should we remove it from RC2 ?
16:00:38 <nikhil_k> ttx: ah that one
16:00:43 <nikhil_k> I was going to ask
16:00:44 <ttx> Also not so sure about where the fix for https://bugs.launchpad.net/glance/+bug/1368965 lives
16:00:59 <ttx> ok, let's decide on https://review.openstack.org/#/c/120432/ first
16:01:03 <nikhil_k> basically, Travis said that he was debugging the 'correctness' of that one
16:01:31 <ttx> that one feels dangerous
16:01:49 <nikhil_k> hmm
16:02:11 <nikhil_k> not sure how dangerous though, it's basically trying to remove ID generation and relying on DB
16:02:28 <nikhil_k> remove ID generation on Glance
16:02:31 <ttx> feels like something that could be backported to stable/juno postrelease though
16:02:41 <ttx> you might not want to rush it in one week before release
16:02:49 <nikhil_k> does it have a possibility for post-release?
16:03:40 <ttx> a bit unclear.. does the patch change the DB ?
16:03:57 <nikhil_k> no, it changes the interaction with the ORM
16:04:03 <nikhil_k> basically, while creating a row
16:04:32 <nikhil_k> they specified if the ID should NOT be passed in from Glance sqlalchemy code
16:05:02 <nikhil_k> and rahter create the row and let the DB create the UUID for resp. ID
16:05:14 <nikhil_k> return value to the API is fetch of the row from DB
16:05:14 <ttx> hmm, just have no idea how common the isage of this command is
16:05:27 <nikhil_k> yeah, it's rather off hand
16:05:38 <ttx> nikhil_k: I think we shouldn't block RC2 on that one
16:05:46 <ttx> let's put it back to juno-rc-potential
16:05:48 <nikhil_k> ohk sure
16:05:59 <ttx> if it makes it to master very soon, we'll reconsider it
16:06:25 <ttx> https://bugs.launchpad.net/glance/+bug/1368965 now
16:07:15 <ttx> oh that would be https://review.openstack.org/#/c/121998/
16:07:51 <ttx> still needs two +2s
16:07:52 <nikhil_k> should be straightforward
16:08:01 <nikhil_k> yeah
16:08:10 <ttx> do youy think you can get the remaining ones in before tomorrow ?
16:08:15 <ttx> then I think we are still good
16:08:35 <nikhil_k> I was going to email the core reviewers to look at this list on priority
16:08:55 <nikhil_k> hopefully, we can clear most of these by tomorrow. I will review them soon too
16:09:10 <ttx> The other two things would be:
16:09:12 <ttx> https://review.openstack.org/#/c/123698/
16:09:17 <ttx> requirements update for master
16:09:31 <ttx> to match current common requiremenrs
16:09:45 <nikhil_k> tricky but doeable
16:09:46 <ttx> and https://review.openstack.org/#/c/126338/ for propsoed/juno
16:09:56 <nikhil_k> sure
16:09:57 <ttx> why tricky ?
16:10:20 <nikhil_k> sometimes the tests fail if requirements are updated however, for that particular one seems rather safe
16:11:09 <ttx> We'll also want updated translations, so you can start by approving https://review.openstack.org/#/c/124565/ in master
16:11:19 <nikhil_k> ttx: do you need someone to approve all of the proposed/juno patches or if it is merged in master it would be fine?
16:11:31 <nikhil_k> sure about the translations patch
16:11:34 <ttx> then we'll work on a backport for that -- we'll discuss a script in the release meeting at 21:00 UTC
16:11:48 <ttx> nikhil_k: if merged in master I can approve them
16:11:53 <nikhil_k> ohk sure
16:11:57 <nikhil_k> ah great
16:12:06 <ttx> ok, that's all I had
16:12:28 <ttx> We can talk more in a few hours and see where we stand
16:12:29 <nikhil_k> sync up tomorrow same time for rc2?
16:12:36 <nikhil_k> sure
16:12:41 <ttx> Lots of stuff that need to merge in master at this point
16:12:53 <ttx> nikhil_k: ok
16:13:01 <ttx> SlickNik: ready?
16:13:10 <SlickNik> ttx: yup o/
16:13:11 <ttx> #topic Trove
16:13:36 <ttx> https://bugs.launchpad.net/trove/+bugs?field.status%3Alist=FIXCOMMITTED
16:13:55 <ttx> ANything in there that will trigger a RC2 for sure ?
16:14:34 <SlickNik> Nope.
16:15:08 <ttx> OK, I'll ping you again tomorrow, but I think RC1 can live for another day at least
16:15:36 <ttx> SlickNik: anything on your mind ?
16:15:39 <SlickNik> Are there plans for a second RC if RC1 still holds good?
16:15:59 <SlickNik> ttx: updated Trove status on the Gap Coverage.
16:16:00 <ttx> SlickNik: not really. Your requirements are ok, and you had recent translations merged for RC1
16:16:14 <ttx> so it looks good to go afaict
16:16:28 <SlickNik> ttx: That's what I figured — cool, thanks.
16:16:49 <ttx> SlickNik: well, talk to you later, then
16:16:55 <ttx> jgriffith: still not around?
16:17:00 <SlickNik> ttx: thanks!
16:17:03 <SlickNik> tty later.
16:19:34 <jgriffith> ttx: yo
16:19:47 <ttx> #topic Cinder
16:19:50 <ttx> jgriffith: o/
16:19:57 <jgriffith> ttx: goooood morning
16:20:05 <ttx> https://bugs.launchpad.net/cinder/+bugs?field.status%3Alist=FIXCOMMITTED
16:20:28 <ttx> I think we want a RC2 for 1350504 at least
16:20:44 <ttx> Also you need a requirements adjustment
16:20:51 <jgriffith> ttx: yeah
16:21:30 <ttx> Any reason to oppose https://review.openstack.org/#/c/122559/ in master ?
16:21:34 <jgriffith> ttx: all of those are safe IMO to go ahead and ommit
16:21:54 <jgriffith> ttx: I get nervous on those as they've bitten us in the past
16:22:07 <jgriffith> ttx: but I'm ok with it if everyone is syncing
16:22:14 <ttx> yeah
16:22:24 <ttx> Then we should be able to unblock https://review.openstack.org/#/c/126337/
16:22:56 <jgriffith> ttx: yes, I'm good with that
16:23:00 <ttx> So how about I open a RC2 with all the juno-rc-potential stauff in
16:23:12 <ttx> and you can get busy backporting
16:23:18 <jgriffith> ttx: yeah that sounds good
16:23:26 <jgriffith> ttx: I can get those done pretty quick
16:23:31 <ttx> ok let me open that quick
16:23:44 <jgriffith> ttx: alright, and I'll start the backports
16:23:59 <jgriffith> ttx: so the global req's...
16:24:12 <jgriffith> ttx: you want to unblock and we'll get that merged so I can bp once it lands
16:24:41 <jgriffith> ttx: oh... you've got Juno branch set on that one
16:24:42 <jgriffith> NM
16:24:54 <jgriffith> that one will just sort itself I'm assuming
16:26:09 <ttx> ok: https://launchpad.net/cinder/+milestone/juno-rc2
16:26:23 <ttx> One more bug at https://bugs.launchpad.net/cinder/+bugs?field.tag=juno-rc-potential
16:26:48 <ttx> Looks like a regression ?
16:27:04 <jgriffith> added
16:27:05 <jgriffith> yes
16:28:07 <ttx> hmm, we'll need a fix for that one, quick
16:28:15 <jgriffith> ttx: I'll just patch that to catch the exception and continue
16:28:23 <jgriffith> ttx: I'll work on it right now
16:28:23 <ttx> ok great, get that in master fast
16:28:26 <jgriffith> then roll the backports
16:28:55 <ttx> We'llalso refresh translations, so you can get https://review.openstack.org/#/c/123944/ in
16:29:16 <ttx> once in master, we'll run some script to import it for proposed/juno
16:29:22 <ttx> (tbfd at release meeting today)
16:29:45 <jgriffith> ttx: so to clarify, I "will not" run my bp script on that one
16:29:46 <jgriffith> ?
16:29:55 <ttx> your bp script ?
16:30:02 <jgriffith> backport
16:30:24 <ttx> jgriffith: apparently that can screw things over, a specific backport needs to be made
16:30:31 <ttx> that's the topic of todays meeting discussion
16:30:35 <jgriffith> :)
16:30:39 <jgriffith> preview eh
16:30:40 <jgriffith> ok
16:30:40 <ttx> jgriffith: last thing I wanted to discuss is the need to bump your requirements to taskflow>=0.5.0
16:31:01 <ttx> that was bumped recently and you're the only project to use it
16:31:05 <ttx> (apparently)
16:31:21 <jgriffith> ttx: yes, I don't think anybody else has picked up taskflow yet
16:31:27 <jgriffith> ttx: and it was a bug that we needed fixed
16:31:52 <ttx> so we could in theory get that bumped in master and proposed/juno openstack/requirements
16:32:03 <ttx> and synced in master and proposed/juno cinder
16:32:10 <ttx> jgriffith: think it's worth it ?
16:32:22 <ttx> dhellmann: ^
16:32:33 <jgriffith> ttx: would be good
16:32:43 <dhellmann> ttx, jgriffith : wfm
16:32:48 <ttx> jgriffith: care to propose the bump to master requirements ?
16:32:56 <jgriffith> ttx: will do right now
16:32:56 <ttx> dhellmann and myself could approve it
16:33:21 <ttx> dhellmann: we should warn the distros... how about a thread on -dev ?
16:33:25 <dhellmann> ++
16:33:34 <ttx> replying to the announcement
16:33:44 <jgriffith> ttx: wait...
16:33:50 <jgriffith> ttx: we're at >=0.4
16:33:54 <jgriffith> in global
16:34:09 <jgriffith> and cinder
16:34:13 <ttx> jgriffith: yes, and we would bump to 0.5.0 ?
16:34:20 <jgriffith> 0.4 was the need for our fix....
16:34:26 <ttx> oh?
16:34:31 <jgriffith> IIRC yes
16:34:41 <ttx> dhellmann: hmm, we should confirm that
16:34:57 <ttx> I'll just add it to the meeting agenda. jgriffith: you'll be around at 21:00 UTC ?
16:35:01 <dhellmann> the fix for the six issue is in 0.5.0, but if that wasn't a problem for cinder I'm not sure we need to worry about it
16:35:02 <jgriffith> ttx: dhellmann I can also check with harlow to make sure
16:35:08 <dhellmann> ttx: yeah, I haven't heard from josh yet
16:35:11 <jgriffith> ttx: yeah, I'll be sure to be there
16:35:18 <ttx> jgriffith: ok, let's all sync there
16:35:19 <jgriffith> ttx: and see if I can drag thingee along
16:35:25 <jgriffith> sounds good
16:35:36 <ttx> adding to agenda
16:36:13 <ttx> ok, I think that is all.
16:36:13 <jgriffith> works for me, pinged harlow
16:36:20 <jgriffith> I'll go back to working up that patch
16:37:43 <ttx> #endmeeting