08:02:03 <ttx> #startmeeting ptl_sync
08:02:04 <openstack> Meeting started Tue Oct 14 08:02:03 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:02:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:08 <openstack> The meeting name has been set to 'ptl_sync'
08:02:11 <ttx> #topic Nova
08:02:13 <mikal> Heya
08:02:37 <mikal> John is fighting technology, so he might be late
08:02:55 <ttx> hah
08:03:01 <ttx> so, RC2 out
08:03:09 <mikal> Hurrah
08:03:21 <ttx> https://bugs.launchpad.net/nova/+bugs?field.tag=juno-rc-potential
08:03:38 <ttx> A few bugs there, but nothing mature enough to justify RC3 I'd say
08:04:15 <mikal> I should read the live migrate one
08:04:20 <mikal> 1377644
08:04:38 <ttx> How up to date are you on the release notes ? https://wiki.openstack.org/wiki/ReleaseNotes/Juno
08:04:45 <mikal> Oh, that's the exception thing
08:04:54 <mikal> So, I need to start on the release notes
08:04:58 <mikal> Its basically not attempted yet
08:05:18 <mikal> I do have a summary of landed BPs though
08:05:37 <ttx> ok, the sooner the better for the release notes, to avoid last-minute edit conflicts
08:05:38 <mikal> http://www.stillhq.com/openstack/juno/000018.html
08:05:58 <mikal> So, the "Key New Features" section is just that blog post, right?
08:06:04 <mikal> Or do I need to stick with the headings there?
08:06:31 <ttx> no, thta blogpost with a few edits should do
08:06:36 <mikal> Excellent
08:06:39 <mikal> I was hopign that was the case
08:06:46 <ttx> not sure our users care about the migration reserve
08:06:47 <mikal> I will cut and paste that in now then
08:06:53 <mikal> Yeah, fair point
08:06:56 <ttx> and some titles could use a bit of elaboration
08:07:02 <mikal> That's the problem with including literally all
08:07:03 <ttx> but the structure should be the same
08:07:12 <mikal> Well, I shall dump and then iterate
08:07:17 <ttx> exactly
08:07:25 <ttx> it's a good first draft :)
08:08:09 <ttx> starting EOD today we won't respin unless there is some critical issue like catastrophic data loss, or legal problems
08:08:12 <ttx> or missing files
08:08:23 <mikal> Ok
08:08:31 <ttx> "regular" bugs will be documented as known issues
08:08:45 <ttx> so that leaves today to do a RC3 over normal regressions
08:09:07 <ttx> but I wouldn't consider bugs that are not already fixed in master
08:09:13 <mikal> I have seen zero discussion of requiring a rc3
08:09:15 <mikal> So I think we're ok
08:09:22 <ttx> right
08:09:55 <ttx> johnthetubaguy: we were saying nothing justifies a late respin at this point
08:10:27 * johnthetubaguy grumpy that IRC forced him to use webchat
08:10:49 <johnthetubaguy> ttx: mikal: yeah, I haven't seen anyone screaming about something
08:11:09 <ttx> johnthetubaguy: we'll keep an eye on that today. Like I told mikal:
08:11:38 <ttx> starting EOD today we won't respin unless catastrophic dataloss, legal issues, missing files
08:11:56 <johnthetubaguy> ttx: cool, makes sense
08:12:06 <ttx> so that leaves today for "normal" respin -- but we wouldn't consider any backport that's not already in master
08:12:16 <ttx> and lookgin at the list right now, nothing jumps out
08:12:38 <ttx> https://bugs.launchpad.net/nova/+bugs?field.status%3Alist=FIXCOMMITTED
08:13:02 <ttx> we'll keep an eye on that list today just in case
08:13:26 <ttx> OK, anything else ?
08:13:40 <mikal> For the release or in general?
08:13:47 <ttx> in general
08:14:02 <mikal> So, I feel like I need to start paying more attention to the summit schedule
08:14:07 <mikal> But I will get on that ASAP
08:14:25 <johnthetubaguy> mikal: are we going to cover that in some nova-meeting?
08:14:39 <mikal> johnthetubaguy: so, we have a page of ideas
08:14:46 <mikal> johnthetubaguy: we now need to work out how to turn that into a thing
08:14:57 <mikal> johnthetubaguy: which I guess does involve our meetings
08:15:00 <ttx> you need to split the topics between scheduled slots and the meetup basically
08:15:05 <mikal> Yeah
08:15:06 <johnthetubaguy> mikal: yeah, I am thinking we discuss the proposed thing in the nova-meeting, see if people agree
08:15:12 <mikal> Kyle pinged me about the nova-net upgrade path
08:15:17 <mikal> I suggested some shared time on Friday
08:15:24 <mikal> Insteafd of trying to clash with another nova session
08:15:36 <ttx> scheduled slots are good when the discussion is easily timeboxed and would benefit from being advertised on the schedule (needs nova-external input)
08:15:53 <mikal> I am not sure the nova-net thing can be timeboxed
08:16:04 <mikal> I don't have a good read on that
08:16:21 <ttx> "meetup" slots are good for project process discussion, setting cycle priorities at the end of the week etc
08:16:33 <johnthetubaguy> mikal: some shared nova + neutron meet up time sounds good though, even if its a slot where we have nova sessions and no neutron sessions, or something like that
08:16:47 <ttx> a number of things obviously fall in the middle between those two extremes
08:17:07 <mikal> ttx: is neutron two full days of sessions too?
08:17:12 <ttx> so I would split the ideas between 3 groups
08:17:18 <mikal> Or is there a gap we could schedule the upgrade thing into?
08:17:27 <ttx> there is a gap
08:17:33 * ttx shares
08:17:42 <mikal> Last summit there was a spreadsheet of doom
08:17:46 <mikal> Do we have one of those again?
08:18:26 <ttx> yes, see pm
08:18:41 <mikal> Thanks
08:18:52 <ttx> from Wed 1:50pm to Thu 10:30 am, no Neutron session
08:18:53 <mikal> Oh, so Wed arvo might work for example
08:18:54 <mikal> Cool
08:19:42 <ttx> the canonical layout is at http://kilodesignsummit.sched.org/ now
08:19:56 * ttx spots a few errors in the spreadsheet
08:20:06 <mikal> Oh, nice
08:20:10 <mikal> Fixy fixy
08:20:53 * johnthetubaguy_w lets hope the french don't ban me
08:21:09 <mikal> Why would they?
08:21:12 <mikal> Did you hurt their feelings?
08:21:28 <johnthetubaguy> lol, no idea
08:21:49 <mikal> So, I think we sound like we're done?
08:21:58 <mikal> Apart from me promising to think more on the summit?
08:22:08 <mikal> I also intend to announce a mid-cycle meetup real soon now [tm]
08:22:23 <johnthetubaguy> mikal: let us driver folks know how we can help with that
08:23:16 <mikal> johnthetubaguy: yrp
08:23:19 <ttx> mikal: yes done
08:23:31 <mikal> Basically two companies offered, and then one backed down
08:23:35 <mikal> So the other wins!
08:23:39 <ttx> mikal: does your meetup include skiing ?
08:23:57 <mikal> ttx: no, that's why Company One backed down, too much snow
08:24:08 <mikal> ttx: so we're going somewhere warm and will revisit Company One in Lemming
08:25:11 * johnthetubaguy looks forward to mid-cycle announcement
08:25:13 <ttx> alright then, ttyl
08:25:17 <mikal> Laters!
08:25:20 <johnthetubaguy> bye
11:23:09 <SergeyLukjanov> ttx, hey, will any projects have rc3?
11:23:25 <ttx> Heat already had one
11:23:32 <ttx> Trove will likely have one too
11:23:44 <SergeyLukjanov> ttx, heh
11:45:02 <eglynn> ttx: knock, knock ...
11:45:27 <ttx> #topic Ceilometer
11:45:42 * ttx is busy looking up fine restaurants
11:45:56 <ttx> eglynn: howdy
11:46:14 <ttx> RC2 is out, a few candidates up for RC3 respin
11:46:15 <eglynn> no shortage of those in Paris :)
11:46:35 <eglynn> cool, I've no reason to think we'll need a ceilo RC3
11:46:42 <eglynn> ... famous last words :)
11:46:45 <ttx> https://bugs.launchpad.net/ceilometer/+bugs?field.tag=juno-rc-potential
11:47:00 <ttx> 1379808 was proposed for backport by jd__
11:47:38 <ttx> not sure how blocking it is. It's ont of those that we can't easily backport post-release
11:47:56 <eglynn> yeah he mentioned it to me also
11:48:13 <ttx> we can certainly respin quickly in the next hour(s)
11:48:18 <ttx> if that one is wanted
11:48:34 <ttx> It's certainly self-contained enough and low risk
11:48:55 <eglynn> actually now that I'm giving https://bugs.launchpad.net/ceilometer/+bug/1378742 a second look
11:49:31 <eglynn> hmmm, that one might actually justify respining
11:50:11 <eglynn> OK, let's go for it since both are very self contained
11:50:26 <ttx> hmm, ok, let's do it fast
11:50:32 <eglynn> cool, thanks!
11:50:34 <ttx> anything else critical in https://bugs.launchpad.net/ceilometer/+bugs?field.status%3Alist=FIXCOMMITTED ?
11:51:52 <eglynn> nope, we can live without those
11:52:18 <ttx> eglynn: ok, propose backport for https://review.openstack.org/#/c/126871 now
11:52:21 <ttx> and we'll push it
11:52:31 <eglynn> cool, I'm on it
11:52:39 <ttx> approving julien's one
11:53:54 <ttx> eglynn: after this one, we'll respin only on showstoppers that can't possibly be documented as known issues
11:54:00 <ttx> like a legal issue
11:54:06 <ttx> or a missing file in the tarball
11:54:13 <ttx> or some catastrophic failure
11:54:17 <eglynn> got it
11:54:32 <ttx> so after that backport you should finalize https://wiki.openstack.org/wiki/ReleaseNotes/Juno
11:54:42 <ttx> and then safely proceed to Kilo design summit session planning :)
11:54:52 <ttx> questions ?
11:55:30 <eglynn> yeah I've already done a first cut on the release notes
11:55:41 <eglynn> https://wiki.openstack.org/wiki/ReleaseNotes/Juno#OpenStack_Telemetry_.28Ceilometer.29
11:55:51 <eglynn> nothing else from me
11:56:03 <ttx> cool, ping me when you have the backport up
11:57:55 <eglynn> https://review.openstack.org/128249
12:05:49 <ttx> SergeyLukjanov: around?
12:06:57 <ttx> dhellmann: ready when you are
12:24:52 <dhellmann> ttx: sorry, running late this morning but ready now
12:26:39 <ttx> #topic Oslo
12:26:44 <ttx> dhellmann: o/
12:26:49 <dhellmann> ttx: o/
12:26:50 <ttx> Any red flag from your side ?
12:27:33 <dhellmann> I think we're fully in Kilo mode. I'm not aware of any major issues.
12:27:38 <ttx> dhellmann: I actually had a question for you about openstack/requirements
12:27:43 <dhellmann> k
12:27:55 <ttx> there seems to be some confusion about the use of it by non-integrated projects
12:28:17 <ttx> random projects asking for additional requirements that are not actually wanted by integrated projects
12:28:43 <ttx> It feels like we supported that in the past but are clamping down
12:28:51 <dhellmann> yeah, they used to need to be included for the mirror
12:29:07 <ttx> but they don't anymore ?
12:29:16 <dhellmann> no, we have a full pypi mirror now
12:29:25 <dhellmann> I forget which package we're using, bandersnatch maybe?
12:29:31 <ttx> so why are they asking ?
12:29:31 <dhellmann> we had built our own before
12:29:43 <dhellmann> there are a couple of reasons
12:29:46 <ttx> do they have some stale requirements check job ?
12:29:58 <dhellmann> the doc team wants to sync requirements into their projects
12:30:08 <dhellmann> they have 10+ repos
12:30:40 <dhellmann> fungi, AJaeger, and I sort of decided yesterday that would be ok to keep doing, since debian at least does build the docs
12:30:41 <ttx> so ideally a project could "consume" common requirements and add extra ones on their side
12:30:54 <dhellmann> well, the way it is built now, it's all or nothing
12:31:05 <dhellmann> hrm, maybe that's not true
12:31:20 <dhellmann> we could have the sync job run but leave the check job out of the project
12:31:34 <ttx> dhellmann: how about we abuse the crossproject meeting today to discuss that a bit ? Unless the release is on fire
12:31:36 <dhellmann> of course that means they couldn't have a different version of anything than we have globally
12:31:56 <dhellmann> that works, although I think the projects that care won't necessarily be in the meeting
12:32:09 <dhellmann> solum was another one that came up
12:32:18 <ttx> sure, it's more so that infra/QA/us are all on the same page before we push that down their throats
12:32:47 <dhellmann> makes sense -- I thought the decision was already more or less agreed to, but let's confirm that instead of me assuming it
12:32:53 <ttx> currently I'm not even sure what to answer them ;)
12:33:01 <ttx> cool.
12:33:04 <ttx> Anything else ?
12:33:37 <SergeyLukjanov> ttx, I'm here, sorry for the delay, forgot to enable notifications :(
12:33:45 <dhellmann> I'll remind everyone to send liaisons, but otherwise nothing
12:34:01 <ttx> dhellmann: ok, have a good day then
12:34:05 <ttx> SergeyLukjanov: hi!
12:34:07 <dhellmann> ttx: ditto
12:34:12 <ttx> #topic Sahara
12:34:28 <ttx> SergeyLukjanov: haven't seen anything justifying a RC3 ?
12:34:53 <ttx> Nothing in rc-potential, a few bugs fixed in master but nothing stand out: https://bugs.launchpad.net/sahara/+bugs?field.status%3Alist=FIXCOMMITTED
12:35:01 <SergeyLukjanov> ttx, we have a regression with direct engine and nova-network, but I don't think that we need to delay release because of it
12:35:18 <SergeyLukjanov> ttx, I think we'll test and bacl port it to stable/juno
12:35:27 <ttx> SergeyLukjanov: is that fixed in master already?
12:35:34 <SergeyLukjanov> ttx, not yet
12:35:48 <ttx> SergeyLukjanov: ok, then it shall be documented as a known issue in the release notes
12:36:02 <ttx> https://wiki.openstack.org/wiki/ReleaseNotes/Juno
12:36:07 <SergeyLukjanov> ttx, the fix will be not very safe, so, yeah, we'll document it
12:36:21 <SergeyLukjanov> ttx, we have release notes draft https://wiki.openstack.org/wiki/Sahara/ReleaseNotes/Juno
12:36:31 <SergeyLukjanov> ttx, will move it today to https://wiki.openstack.org/wiki/ReleaseNotes/Juno
12:36:38 <ttx> sounds good
12:36:51 <ttx> SergeyLukjanov: anything else ?
12:37:02 <SergeyLukjanov> ttx, I think nope, everything going well
12:37:21 <ttx> SergeyLukjanov: you'll have to start working on summit agenda
12:37:35 <ttx> dhellmann: that's true for you as well ^
12:37:39 <SergeyLukjanov> ttx, in fact this regression is with the deprecated non-heat engine with custom configs, so, non critical
12:37:53 <SergeyLukjanov> ttx, already working on it, should have a good results for the next meeting
12:37:55 <dhellmann> ttx: we've started
12:38:08 <ttx> ok, let me know if you have questions
12:38:34 <ttx> I'll send you all an email with the link to the website where you can update the (tbd) sessions
12:38:49 <SergeyLukjanov> ttx, ack, thx
12:38:51 <ttx> when the final schedule is ready
12:40:49 <ttx> mestery, nikhil_k: ping me when around so that we anticipate your need for RC3
13:24:44 <mestery> ttx: pong
13:27:19 <ttx> mestery: hey, wanted to ask you in advance of our sync if you think we'll need a RC3
13:27:31 <ttx> if yes, we want to push it to gate asap
13:27:40 <mestery> It's not looking likely, there were no release critical bugs we as a team could find in our meeting yesterday
13:27:46 <mestery> I think we're good with RC2 being Juno final.
13:28:04 <mestery> A quick search this morning didn't turn anything up either.
13:28:06 <ttx> Someone proposed https://bugs.launchpad.net/neutron/+bug/1378525 for backport
13:28:18 <ttx> should we still ignore that ?
13:28:22 <mestery> Yes, we spoke about that one, and we determined it can be release noted.
13:28:25 <mestery> I'll comment in the bug
13:28:51 <ttx> mestery: ok then
13:29:01 <ttx> mestery: we can formally do our sync now if that suits you
13:29:17 <mestery> ttx: Actually, one sec, looking at the bug.
13:29:20 <mestery> It's a 1 line change.
13:29:28 <mestery> Hmmm ....
13:29:38 <mestery> Still not sure it's worth spinning a new release for.
13:29:43 <mestery> And yes, lets sync now.
13:29:48 <ttx> #topic Neutron
13:30:11 <ttx> It's sufficiently self-contained that we can respin on that, if you think it's a critical issue
13:30:47 <mestery> Let me talk to Akihiro, he made a comment about Horizon.
13:30:53 <mestery> I will know in < 1 hour I think once I get a hold of him.
13:31:02 <mestery> I agree, it may be worth respinning just for this bug since it's contained.
13:31:11 <mestery> Shall I propose the cherry-pick in anticipation?
13:31:19 <ttx> it's already cherrypicked
13:31:26 <mestery> Ah, cool. :)
13:31:28 <ttx> https://review.openstack.org/#/c/126711/
13:31:54 <mestery> Perfect.
13:32:02 <ttx> so it's not too disruptive as long as we push it now
13:32:06 <mestery> Right.
13:32:08 <mestery> I'll know soon.
13:32:13 <ttx> <1 hour is probably ok
13:32:26 <ttx> checking https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=FIXCOMMITTED for other easy ones
13:33:06 <mestery> Me too
13:33:39 <mestery> Sukhdev asked me to consider this one: https://bugs.launchpad.net/neutron/+bug/1373652
13:33:45 <mestery> It's a larger change, but contained to the Arista driver
13:34:03 <mestery> I'm inclined to include that one if you are ok with it.
13:34:07 <ttx> looking
13:34:55 <ttx> more risky
13:35:05 <ttx> also easily backportable imho
13:35:14 <ttx> and documenatble
13:35:17 <mestery> Yeah, lets leave it.
13:35:19 <mestery> I agree
13:35:23 <mestery> and .1 is 6 weeks out or so?
13:35:26 <mestery> So it's fine to land then.
13:35:29 <mestery> With more testing, etc.
13:35:59 <ttx> yeah
13:36:19 <ttx> https://bugs.launchpad.net/neutron/+bug/1232525 maybe
13:36:35 <mestery> https://bugs.launchpad.net/neutron/+bug/1365226 also
13:36:39 <ttx> although it's probably just cosmetic
13:37:09 <mestery> Yes to 1232525, it may make backports easier
13:37:13 <mestery> What about 1365226?
13:38:11 <ttx> hmm, was never merged to master ?
13:38:18 * mestery checks again
13:38:34 <mestery> Right
13:38:35 <mestery> Sorry
13:38:36 <mestery> :)
13:38:43 <ttx> bit weird
13:38:57 <ttx> oh, driver removed
13:38:58 <ttx> bah
13:39:05 <ttx> so just one, if you confirm it
13:39:10 <mestery> Yeah
13:39:19 <ttx> unless we also do 1232525
13:39:28 <mestery> Yes, I think 1232525 is good as well
13:39:37 <mestery> I am ok with that one, and I can propose the cherry-pick this morning yet
13:39:53 <ttx> propose it now, add the bug reference to the commit message
13:40:02 <ttx> if it's ready when the other is, it won't delay
13:40:10 <mestery> Ack
13:40:51 <ttx> #info Potential RC3 over 1378525 and 1232525, to be confirmed in the next hour
13:41:48 <ttx> mestery: what's the state of your release notes ?
13:42:11 <mestery> ttx: I was going to release note the L3 HA bug, but now we're merging it. Otherwise, I'll take another run at them today.
13:42:19 <mestery> They are in good shape, but I'll confirm today.
13:43:00 <ttx> ok, then you need to start working on the design summit agenda
13:43:06 <ttx> once the release is mostly done
13:43:21 <mestery> Way ahead of you :)
13:43:25 <mestery> We have that almost wrapped too
13:43:27 <mestery> On an etherpad
13:43:36 <mestery> By end of tomorrow it will be finalized I think
13:43:37 <mestery> :)
13:44:19 <mestery> ttx: https://review.openstack.org/128288
13:45:15 <ttx> mestery: OK, let's wait until we confirm the RC3
13:45:32 <mestery> ttx: Ack
13:45:37 <mestery> But it's in the queue now at least
13:45:48 <ttx> ok then, let me know when you've come to a decision about it
13:46:25 <mestery> ttx: Will do, email out to amotoki.
13:46:31 <mestery> ttx: The default is we don't do it, which is fine too.
13:46:54 <ttx> agreed
13:47:34 <ttx> jgriffith: ready when you are
13:47:39 <mestery> ttx: Thanks!
13:58:33 <mestery> ttx: amotoki just confirmed, RC3 is good to go, lets merge those two fixes.
13:58:59 <ttx> ok, opening
13:59:24 <mestery> ttx: ACK
14:00:57 <ttx> https://bugs.launchpad.net/neutron/+milestone/juno-rc3
14:01:23 <mestery> Looks good ttx, thanks!
14:01:49 <mestery> ttx: https://review.openstack.org/#/c/126711/ you can merge this one now or remove your -2.
14:02:02 <mestery> ttx: jinx ;)
14:02:12 <ttx> gating
14:02:24 <ttx> jgriffith: around?
14:02:36 <mestery> ttx: Thanks!
14:02:48 <ttx> will tag as soon as those two merge
14:03:11 <ttx> although there is quite a bit of delay in the post queue right now
14:05:19 <mestery> ttx: Lets hope it makes the journey safely.
14:14:01 <ttx> dolphm: ready when you are
14:14:12 <morganfainberg> ttx, o/ here as well.
14:14:19 <dolphm> ttx: o/
14:14:22 <ttx> morganfainberg: o/
14:14:23 <ttx> #topic Keystone
14:14:30 <ttx> Looks like you're good?
14:14:36 <dolphm> i believe so!
14:14:55 <dolphm> no reason for an rc3 at this point
14:15:23 <ttx> so.. by EOD today we'll only respin on show stoppers, like legal issues, missing files in tarballs etc
14:15:50 <ttx> everything else will go to known issues in the release notes
14:16:10 <ttx> Looks like your release notes are mostly ready ?
14:18:58 <ttx> dolphm ? morganfainberg ?
14:19:09 <morganfainberg> ttx, looking at release notes, but i think so
14:19:16 <ttx> OK. How is summit planning going ?
14:19:38 <morganfainberg> ttx, have most of the sessions lined up wiht one open slot to be discussed at the keystone meeting today
14:20:20 <morganfainberg> ttx, descriptions and specific time slots are still variable, at the top of https://etherpad.openstack.org/p/kilo-keystone-summit-topics i've added a tentative list/schedule
14:21:01 <morganfainberg> when is the "move this stuff to the actual schedule" date?
14:21:01 <ttx> I'll send info on how to push updates to the schedule
14:21:03 <morganfainberg> k
14:21:29 <ttx> date would be between reception of email and one week before summit starts
14:21:41 <morganfainberg> ttx, ack
14:21:55 <ttx> any other question ?
14:22:04 <morganfainberg> i think thats it for me.
14:22:04 <ttx> anything you'd like to discuss at the meeting today ?
14:22:17 <ttx> ok then, talk to you later!
14:22:20 <morganfainberg> oh, once we move to kilo, mind changing this time slot?
14:22:26 <ttx> not at all.
14:22:34 <morganfainberg> it's going to be 0615 for me once we timeshift
14:22:40 <morganfainberg> a bit early :)
14:22:47 <ttx> we'll discuss the reshuffle them all with the DST end anyway
14:22:53 <morganfainberg> sounds good!
14:24:16 <morganfainberg> I'll bring up that keystone team should do a once over on the release notes today at the meeting, but thye look complete to me.
14:25:15 <ttx> david-lyle: ready when you are
14:25:21 <david-lyle> ttx: ready
14:25:26 <ttx> #topic Horizon
14:25:39 <ttx> RC2 is out
14:26:05 <ttx> rc-potential has https://bugs.launchpad.net/horizon/+bug/1379761
14:26:31 <david-lyle> yes, this has to be fixed
14:26:59 <ttx> or documented, if we can't get it fixed in time
14:26:59 <david-lyle> can't run Horizon without DEBUG=True in the settings for Django, which is bad
14:27:15 <ttx> david-lyle: how is the fix looking so far ?
14:27:37 <david-lyle> complicating factor is that the broken code is in a dependency
14:27:53 <ttx> I prefer to wait for the fix to land in master before opening formally an RC3 window (prefer not to open windows I don't know how to close)
14:28:07 <david-lyle> may require a monkey patch to get Juno released and fix appropriately upstream
14:28:39 <dolphm> ttx: (bah, sorry for dissappearing, but everything sounds good. thanks morganfainberg!)
14:28:40 <david-lyle> I don't have a fix yet, still working through cleaner ways of working around upstream bug
14:29:22 <david-lyle> I don't mind waiting on the RC3 window until we have a fix
14:29:31 <ttx> hmm, ok
14:29:55 <david-lyle> we can't really release without a fix
14:30:07 <david-lyle> unfortunately
14:30:16 <ttx> is that something we could have detected earlier ?
14:30:40 <david-lyle> most likely, but it's an odd issue
14:30:55 <david-lyle> we needed to run this as a production release
14:31:31 <david-lyle> the upstream code just punted when they didn't really understand django settings
14:32:01 <ttx> david-lyle: ok, so ideally we need that fix propoesed, reviewed and merged today
14:32:11 <ttx> does that look even doable ?
14:32:14 <david-lyle> that's my hope
14:32:33 <david-lyle> it may not be elegant, but we should have something that works
14:32:37 <ttx> that's for some large definition of "today" -- meaning I can get up tomorrow morning and get the backport in
14:33:04 <ttx> so getting it proposed and reviewed by your EOD should be enough
14:33:52 <david-lyle> ok
14:34:10 <ttx> anythign else ? How are your release notes coming up ?
14:34:35 <ttx> hmm, more work needed there but if everything goes ok today you should have time for that tomorrow
14:34:42 <ttx> or find someone to delegate that to
14:34:43 <david-lyle> I have them mostly completed, just a little cleanup and I can add them
14:34:48 <ttx> ok, cool
14:35:02 <ttx> then post-release you can focus on yoru design summit session schedule :)
14:35:07 <ttx> your*
14:35:29 <david-lyle> maybe we'll have that figured out by Nov ;)
14:35:46 <ttx> ok, questions?
14:36:01 <david-lyle> nope
14:36:07 <david-lyle> going to go tackle a bug
14:36:16 <ttx> go go go
14:36:19 <david-lyle> talk to you later
14:36:26 <ttx> ack
14:36:31 <ttx> jgriffith: around now ?
14:51:34 <nikhil_k|afk> ttx: hi
14:51:47 <ttx> nikhil_k: hi!
14:52:05 <ttx> nikhil_k: could we sync early to discuss a potential Glance RC3 ?
14:52:12 <ttx> (i.e. now ?)
14:52:15 <nikhil_k> yeah sure
14:52:21 <nikhil_k> was just saying..
14:52:24 <ttx> #topic Glance
14:52:26 <nikhil_k> I'm a bit uncertain either way about
14:52:35 <nikhil_k> oh ok :)
14:52:42 <nikhil_k> RC3 !
14:52:47 <ttx> https://bugs.launchpad.net/glance/+bugs?field.tag=juno-rc-potential
14:53:05 <ttx> there aren't so many fixed bugs in that list
14:53:20 <ttx> anything that would make it worth our effort ?
14:54:01 <ttx> 1361613 is a doc fix that we could add IF we respinned for other reasons
14:54:47 <nikhil_k> hmm
14:54:48 <ttx> nikhil_k: today is the last day to respin over bugs
14:54:58 <ttx> after that ikt's show stoppers onlyu
14:55:02 <ttx> err
14:55:11 <ttx> "after that it's show stoopers only"
14:55:19 <ttx> damn it :)
14:55:25 <ttx> "after that it's show stoppers only"
14:55:41 <nikhil_k> heh, np
14:55:50 <nikhil_k> we need this one 1380689
14:55:55 <ttx> everything else shall be documented as "known issues" in the release notes
14:55:56 <nikhil_k> https://bugs.launchpad.net/glance/+bug/1380689
14:56:04 <nikhil_k> oh hmm
14:56:51 <ttx> we need it in master asap
14:57:01 <ttx> then if it makes it, we can discuss backporting
14:57:42 <nikhil_k> ttx: ok, let me see if we can make it today
14:57:50 <ttx> So at this point I'd work to get 1361613 and 1380689 in
14:57:52 <nikhil_k> am not sure if people would like to argue over it
14:58:21 <nikhil_k> ttx: sounds good
14:58:31 <nikhil_k> reconvene in a couple of hours?
14:58:46 <ttx> if done in a few hours (merged by the project meeting today) then we could do a respin with 1380552 1361613 1380689
14:59:20 <ttx> (https://bugs.launchpad.net/glance/+bug/1380552 has a proposed backport already)
15:00:40 <ttx> hmm although it might not be warranted at this point
15:01:09 <ttx> bah, we'll see once you get 1361613 and 1380689 approved and merged
15:01:21 <ttx> #info Potential RC3 over 1361613 and 1380689
15:01:43 <ttx> nikhil_k: yes, will ping you later
15:02:02 <nikhil_k> ttx: thanks for the info! cya in a bit
15:02:06 <ttx> nikhil_k: thx!
15:34:15 <notmyname> ttx: are we on today?
15:34:23 <ttx> notmyname: we are
15:34:26 <ttx> #topic Swift
15:34:31 <notmyname> hello!
15:34:36 <ttx> sorry was busy announcing ceilo rc3
15:34:43 <ttx> How is you RC1 doing
15:34:45 <notmyname> no worries. I don't actually have much
15:34:46 <ttx> your*
15:34:51 <notmyname> other than mea culpa on LP stuff
15:34:58 <ttx> 2 days left :)
15:35:06 <notmyname> everything looks good from what I've seen
15:35:09 <notmyname> for the RC
15:35:12 <ttx> also your release notes section could use some extra love
15:35:15 <notmyname> nothing has come up
15:35:24 <notmyname> ah? what's the link there?
15:35:30 <ttx> https://wiki.openstack.org/wiki/ReleaseNotes/Juno#OpenStack_Object_Storage_.28Swift.29
15:35:43 <ttx> Key new feature section is a bit empty
15:35:47 <notmyname> oh yeah. that's easy to do
15:35:57 <ttx> that's about it
15:36:14 <ttx> Will promote RC1 on Thursdau morning unless you yell
15:36:24 <notmyname> our plan for the summit is to continue to gather topics this week and start scheduling next
15:36:28 <notmyname> ack
15:36:35 <ttx> sounds good
15:36:53 <ttx> anything you'd like to discuss at the meeting today ?
15:37:12 <notmyname> nothing comes to mind
15:37:27 <ttx> notmyname: alright then
15:37:31 <ttx> talk to you later!
15:37:38 <ttx> jgriffith: around now ?
15:37:38 <notmyname> :-)
15:38:06 <ttx> zaneb: ready when you are
15:51:52 <ttx> no zaneb, no jgriffith ?
15:52:03 <zaneb> I'm here
15:52:09 <zaneb> sorry
15:52:15 <ttx> oh here he is
15:52:18 <ttx> #topic Heat
15:52:19 <zaneb> not sure how I missed that notification
15:52:30 <ttx> Nothing in rc-potential
15:52:37 <zaneb> \o/
15:52:46 <ttx> https://review.openstack.org/#/c/128159/ was proposed for backport, without a bug reference
15:53:16 <ttx> feels like a bit overkill for juno, good to land early i nkilo
15:53:45 <zaneb> yeah, I'm not aware of a reason to rush it
15:53:57 <zaneb> unless it is going to break tests or something
15:54:05 <ttx> anything critical elsewhere justifying a late RC4 ?
15:54:18 <ttx> Note that by EOD today we'll only respin for show stoppers
15:54:31 <ttx> everything else will just be documented as known issue in release note
15:54:36 <zaneb> not that I know of
15:54:46 <zaneb> I think rc3 should be final
15:54:56 <ttx> I'll take that answer and run with it. I have more than enough RC3s baking right now
15:55:23 <ttx> You started working on the release notes, though I suspect they could use extra info
15:55:27 <ttx> https://wiki.openstack.org/wiki/ReleaseNotes/Juno#OpenStack_Orchestration_.28Heat.29
15:55:39 <ttx> Questions on the release ?
15:56:00 <zaneb> hmm, *I* didn't start that :D
15:56:09 <zaneb> nope, no questions
15:56:34 <ttx> zaneb: ok, so spend some time on release notes asap
15:56:43 <zaneb> will do
15:56:46 <ttx> before you get into locking conflicts
15:56:47 <ttx> Anything you'd like to discuss at meeting today ?
15:56:57 <zaneb> no
15:57:15 <ttx> Once the release is past us, we should work on finalizing the design summit agenda, but that's more for asaskeld
15:57:34 <ttx> zaneb: ok, thx!
15:57:46 <zaneb> yeah, he started an etherpad but there's a bunch more discussion needed
15:57:56 <zaneb> cool, thanks ttx
15:58:28 <ttx> markwash__: I discussed Glance release with nikhil_k earlier
15:58:51 <ttx> considering a RC3 over bugs 1361613 and 1380689
15:59:10 <ttx> but some progress is needed on master instead -- so i'll sync again with Nikhil in a few hours
15:59:24 <ttx> SlickNik, jgriffith: ready when you are
16:03:50 <SlickNik> ttx o/
16:04:01 <ttx> #topic Trove
16:04:18 <ttx> https://bugs.launchpad.net/trove/+bugs?field.tag=juno-rc-potential
16:04:52 <ttx> so the second bug is gating
16:04:54 <SlickNik> Just the two I was talking to you earlier about.
16:05:17 <ttx> I think we have time for a RC3 then
16:05:30 <ttx> SlickNik: could you propose both backports ?
16:05:53 <SlickNik> Yup, working on the cherry picks now.
16:05:56 <ttx> that way they will run through check while the last change merges in master
16:05:59 <ttx> cool
16:06:03 <ttx> Let me open RC3
16:07:10 <ttx> It's up https://launchpad.net/trove/+milestone/juno-rc3
16:07:40 <SlickNik> Let me target the bugs to that.
16:07:52 <ttx> done already
16:08:13 <SlickNik> Awesome, thank you!
16:08:41 <ttx> ok, so get the backports up and I'll take it from there. Keep an eye on https://review.openstack.org/#/c/128150/ just in case it needs a recheck
16:09:05 <ttx> then you can switch to updating https://wiki.openstack.org/wiki/ReleaseNotes/Juno#OpenStack_Database_service_.28Trove.29
16:09:57 <SlickNik> Cool, sounds good. Thanks so much for your help with this ttx!
16:10:23 <ttx> no problem! cheers
16:10:40 <ttx> SlickNik: hmm wait
16:10:58 <ttx> SlickNik: what about https://bugs.launchpad.net/trove/+bug/1333852
16:11:49 <ttx> feels like this bug has been flying under the radar
16:12:11 <ttx> anything we can do at this point apart from documenting it as a known issue ?
16:12:22 <ttx> jgriffith: last call
16:13:15 <ttx> jgriffith: I'll be back in a few hours, we can talk then
16:13:22 <SlickNik> ttx: that's a tricky issue. We've talked about it before, but looks like we don't yet have a fix ready.
16:13:53 <SlickNik> ttx: It has API compat implications which make it a bit tricky.
16:14:01 <ttx> SlickNik: ok, so I propose the following: explain why it's a tricky issue, maybe raise priority, and document it as known issue in release notes ?
16:14:18 <ttx> (explanation and raise prio would happen on the LP bug)
16:14:31 <SlickNik> ttx: That sounds good. I will do that.
16:14:57 <SlickNik> ttx: I'll also follow up to see that someone is working on fixing it early in Kilo.
16:15:00 <ttx> ok
16:15:17 <ttx> I think part of the issue here is users feeling like they are not getting any attention
16:15:28 <ttx> due to lack of feedback on that bug
16:15:36 <ttx> SlickNik: thx!
16:15:40 <ttx> #endmeeting