Tuesday, 2014-01-21

*** markwash has quit IRC00:16
*** markwash has joined #openstack-relmgr-office00:18
*** SergeyLukjanov_ is now known as SergeyLukjanov05:06
*** SergeyLukjanov is now known as SergeyLukjanov_a06:12
*** SergeyLukjanov_a is now known as SergeyLukjanov_06:13
*** SergeyLukjanov_ is now known as SergeyLukjanov06:42
*** SergeyLukjanov is now known as SergeyLukjanov_07:29
*** SergeyLukjanov_ is now known as SergeyLukjanov08:37
*** markwash has quit IRC08:56
*** SergeyLukjanov is now known as SergeyLukjanov_11:15
*** SergeyLukjanov_ is now known as SergeyLukjanov11:19
*** markmcclain has joined #openstack-relmgr-office12:59
markmcclainttx: ping me when you're ready13:02
*** SergeyLukjanov is now known as SergeyLukjanov_a13:02
*** SergeyLukjanov_a is now known as SergeyLukjanov_13:03
*** SergeyLukjanov_ is now known as SergeyLukjanov13:09
*** markmcclain has quit IRC13:22
jd__I think ttx is traveling or something?13:31
ttxhey13:37
ttxjd__: yes, the 1:1s will be a bit shuffled around this morning, I'm on Mountain time13:38
jd__ttx: let me know when you're done with your breakfast then :)13:38
ttxjust a sec13:39
anteayattx markmcclain is in PST this week and has gone back to bed13:41
anteaya*on PST13:41
ttxanteaya: ok13:42
ttxI'm on MST so we can talk later13:42
anteayak13:43
ttxjd__: will do John now and then jd13:46
jd__ttx: k13:46
* ttx tries to catch up with regular times13:46
*** jgriffith has joined #openstack-relmgr-office13:47
jgriffithttx: hola13:47
ttxhi!13:47
jgriffithttx: so not much movement13:47
jgriffithttx: but I think it's understandable what's going on there13:47
ttxyeah, I fear that will be the same for everyone13:47
jgriffithsadly yes13:47
jgriffiththe week-end trick didn't even work this time around :(13:47
jgriffithttx: so what are your thoughts...13:48
jgriffithttx: defer mp or defer eveything in them?13:48
ttxI'm considering pushing back one week13:48
ttxbecause one or two days won't help13:48
jgriffithassuming things get sorted you're correct13:48
jgriffithcurrently takes 3 days (63 hours) for a +2/A to merge13:48
jgriffithon average at any rate13:49
ttxhmm, we'll make the final decision at meeting today13:49
jgriffithsounds reasonable13:49
ttxbut even with an additional week I think it's safe to say if it's not in the pipe right now it won't likely make it13:50
ttxhttps://launchpad.net/cinder/+milestone/icehouse-213:50
jgriffithttx: I'd agree on that13:50
ttxso should we defer the "started" oe on top of that list ?13:50
jgriffithttx: sure, doing that now13:50
ttxeverything else is in the queue right now. Right ?13:51
jgriffithcorrect13:51
jgriffithexcept for those two bugs13:52
ttxok. Sounds good. We basically have two options and must choose the less absurd one13:52
jgriffithttx: not a fun place / choice13:52
ttxjgriffith: on the bugs side13:52
ttxI'd only keep the oes that are in the pipe + the regressions13:52
jgriffithttx: agreed13:52
ttxcould you clean that up ?13:53
jgriffithttx: I will right now, ys13:53
jgriffithyes13:53
ttxI'll ask the same for everyone I think13:53
ttxthat will give us a good view of the in-flight stuff13:53
jgriffithprobably a reasonable approach13:53
ttxwhich in turn should let us come to a conclusion13:53
jgriffithttx: alright, that should be all of them13:55
jgriffithttx: only things left are in the pipe13:55
ttxhttps://blueprints.launchpad.net/cinder/+spec/vmdk-storage-policy-volume-type13:55
ttxthat one was probably recently added. Should we set a prio or defer to i3 ?13:56
jgriffithwtf is that :)13:56
ttxheh13:56
ttxif the review on that just started, it's fair to move it to i313:57
jgriffithOk, targetted to I2 since it's in progress13:57
ttxhmm13:57
jgriffithttx: I did, then changed my mind ;(13:57
ttxlooks like it's not really all there is13:57
jgriffithsince it's low it's irrelevant I think13:57
ttxhmm, ok13:58
ttxit is all there is so fine13:58
ttxjgriffith: ok thx!13:58
ttxtalk to you at meeting later13:58
jgriffithttx: thank you.. see ya this afternoon/evening13:58
ttxstill have to decide if we keep the TC meeting today13:58
jgriffithI think I'm going to be spending my time looking at the gate again13:59
jgriffithso the extra time is always nice13:59
jgriffithbut I multi-task anyway :)13:59
ttxjd__: around?14:00
jd__ttx: o/14:00
ttxlooks like https://launchpad.net/ceilometer/+milestone/icehouse-2 shows inflight stuff already14:01
* jd__ nods14:01
ttxso I think you're good14:02
jd__yeaaah! :)14:02
ttxyour i-2 would probably also like to get an extra week of feature in14:02
jd__our main problem is the gate, obviously14:02
ttxack14:03
ttxdhellmann: still around?14:03
jd__nothing else otherwise sir14:03
ttxnope nothing either14:03
ttxjd__: I suspect apart from gate and i2 deferral you don't have anything else urgent to discuss at meeting today ?14:04
ttxjgriffith: same question ^14:04
jd__ttx: nop14:04
ttxok, grabbing shower/breakfast now14:14
ttxExpect some disruption around 1:1s meeting times this morning14:15
*** SergeyLukjanov is now known as SergeyLukjanov_a14:42
*** SergeyLukjanov_a is now known as SergeyLukjanov_14:43
notmynamettx: I've got to go to the airport in about an hour. swift status is that we're still waiting on patches to get through the gate for swift 1.12.14:49
ttxnotmyname: workd for me14:50
notmynamefor some definition of "works" ;-)14:50
*** SergeyLukjanov_ is now known as SergeyLukjanov14:50
ttxnotmyname: If I can be reasonably sure things will actually be better in a week ,makes sense to just push back one week on milestones and versions14:51
ttxlike you realized earlier14:51
ttxIf things are not loking better in a week, we've got more... definitive calls to make14:51
notmynamettx: I'm not sure you can be reasonably sure things will be better next week. I'm not currently worried about a certain date for 1.12 (although I'm frustrated that I still don't know when it will be done). I'll send you the SHA when I have it14:52
ttxnotmyname: ack, safe flights14:53
notmynamettx: thanks. enjoy UT :-)14:54
russellbyeah, i'm not sure there's a clear outlook that it will be better next week14:58
russellbsome of it has been bugs, but some of it sheer volume14:59
dolphm(o/)15:03
russellbdolphm: a bit above ttx said ...15:04
russellb<ttx> ok, grabbing shower/breakfast now15:04
russellb<ttx> Expect some disruption around 1:1s meeting times this morning15:04
russellbfyi15:04
dolphmrussellb: ah, danke15:05
russellbnp15:05
ttxdolphm: o/15:05
ttxdolphm: I'M HERE15:05
dolphmttx: YAY15:05
ttxhttps://launchpad.net/keystone/+milestone/icehouse-215:06
ttxdoes that represent to currently-in-flight stuff ?15:06
ttxs/to/the15:06
dolphmonly two of those are currently gating: filtering-backend-support, user-locale-api15:06
ttxdamn this mountain is tempting15:06
dolphmidentity-providers and mapping are likely to be gating this morning15:06
ttxdolphm: should we refine list to only include stuff in-flight ?15:06
dolphmrevocation-events only just went into review in the last 24 hours, and key-distribution-server has a few patchsets to go (but many merged) -- both seem more realistic for i3 week 115:07
ttxyes, you should defer them15:08
ttxanything not already +2/aprv15:08
ttx(by meeting time)15:09
ttxdolphm: what about those two bugs. Also in the gate ?15:09
ttxrussellb: around ? Available to multiplex ?15:11
dolphmone is -- i'll get the other moving15:11
russellbyep15:11
ttxdolphm: try to keep only stuff already gating in the list by meeting time15:11
dolphmttx: will do15:11
ttxI'd like to have an accurate view of what's in-flight15:11
russellbi'm currently deferring most blueprints15:11
russellbunless it's already approved15:11
ttxso that we can make a call15:11
ttxrussellb: yep15:12
russellbother than that, gate fire fighting15:12
ttxrussellb: A tthis point we need to decide if it makes sense to cut milstone this week, we'll discuss that at meeting today15:12
ttxdolphm: anything else you want to discuss today ?15:13
dolphmttx: nope!15:13
ttxok, see you there15:13
russellbttx: makes sense15:13
russellbi think we just cut it15:13
russellbwith whatever got done15:13
dolphmttx: ooh, we were blocking heat until recently -- we got the last of the 4 patchsets on our side gating yesterday15:13
ttxrussellb: I'm fine with deferring, but that requires reasonable confidence an extra week wil actually make things better15:13
ttxbut that's the topic of meeting discussion15:14
russellbsounds good15:14
ttxI think there is a lot of bad timing in this current situation15:14
ttxbut if the problem is more systemic...15:14
ttxrussellb: on the bugs side15:15
russellbneed to defer those too, nothing we need to block on15:15
ttxrussellb: right, keep the in-flight and the regressions in15:15
ttxI just added one15:15
russellbk15:15
ttxhttps://bugs.launchpad.net/nova/+bug/127084515:15
ttxlooks like a regression at first glance, haven't diged into it15:16
russellback15:16
russellbwill look before deferring15:16
ttxhttps://blueprints.launchpad.net/nova/+spec/ec2-volume-type needs triage15:17
ttxprob i315:17
russellbyes15:18
russellbi2 deadline for blueprints was ages ago :)15:18
ttxack15:19
ttxanything to discuss besides the urgent gate issues ?15:20
russellbno ... gate taking most of my attention the last couple weeks15:20
ttxack15:21
ttxdavid-lyle: ready when you are15:21
david-lylettx: here15:29
ttxdavid-lyle: hi!15:30
david-lylettx: hello15:30
ttxdavid-lyle: https://launchpad.net/horizon/+milestone/icehouse-215:30
ttxlike I said to others, the idea would be to refine the list to show what's actually approved and stuck in gate15:31
ttxrather than stuff actually still under review rounds, which ca nbe deffered to i315:31
david-lyleok, I can do that, I think 2-3 are stuck, the rest didn't make it15:31
david-lyleI will move the non-stuck ones to i315:31
ttxdavid-lyle: great, move the others to i3. If by miracle they make it we can put them back in15:31
david-lylesure15:32
ttxdavid-lyle: same for bugs. Would be great to defer to i3 anything that's not currently in-gate15:32
david-lylewill do15:32
ttx(or a critical regression)15:32
ttxdavid-lyle: please do before meeting today so that we get a global and accurate picture15:33
david-lyleI'll move them right after we're done15:33
ttxas we are considering pushing back the milestone cut by one week15:33
ttx(to be discussed today)15:33
david-lyledue to the gate, I assume?15:33
ttxyes15:33
ttxanything else you'd like to discuss today ?15:33
david-lylenot really, would like a clear status on the stable/havana gate too15:34
ttxright15:34
david-lyleI thought that was fixed, but we're still seeing grenade job failures15:34
ttxwill add to agenda15:35
david-lylethanks15:35
ttxdavid-lyle: you might want to keep 1270764 in icehouse-215:35
ttxso that it stays on radar15:35
ttxhttps://bugs.launchpad.net/horizon/+bug/127076415:36
david-lyleyeah, that's a problem15:36
david-lylewe need to address quickly15:36
ttxagree, I'll remilestone it, don't defer it15:37
david-lyleok15:37
ttxdavid-lyle: ok, thx!15:37
david-lylethank you15:37
*** markwash has joined #openstack-relmgr-office15:52
*** SergeyLukjanov is now known as SergeyLukjanov_15:57
*** flaper87 has joined #openstack-relmgr-office15:59
flaper87ttx: yo15:59
ttxflaper87: o/16:10
flaper87ttx: hey16:10
ttxflaper87: so, the idea is to reduce https://launchpad.net/oslo/+milestone/icehouse-2 and https://launchpad.net/oslo.messaging/+milestone/icehouse-2 to what's currently stuck in gate16:10
ttxand defer to iechouse-3 anything that are farther away16:11
flaper87ttx: kk, I already have an idea about what should be deferred16:11
flaper87ttx: from oslo-inc, this one should be moved to i-3: https://blueprints.launchpad.net/oslo.messaging/+spec/notification-subscriber-server16:11
flaper87it requires some patches to be approved before it's complete16:12
ttxflaper87: on it16:12
ttxanything else ?16:12
ttxthe two open bugs in oslo.messaging, maybe ?16:12
flaper87the 2 bugs that don't have "Fix Commited" were merged in oslo-inc but not in oslo.messaging. So I'll move the oslo.messaging ones to i-316:13
flaper87ttx: yeah, what you sai16:13
flaper87ttx: yeah, what you said16:13
flaper87:D16:13
flaper87that's it16:14
ttxok done16:14
flaper87cool16:14
ttxthe patch for bug 1266690 is in the queue already, right ?16:14
flaper87ttx: correct16:15
ttxsame for the 3 blueprints left in https://launchpad.net/oslo/+milestone/icehouse-216:15
ttxok16:15
*** markwash has quit IRC16:15
ttxanything you'd like to see discussed at meeting today, except frozen gate conditions ?16:15
flaper87ttx: the release of oslo.messaging but that's already moving forward so no, nothing for now16:16
ttxok, maybe see you at meeting later16:17
flaper87ttx: will be there! cheers16:17
*** markwash has joined #openstack-relmgr-office16:41
markwashttx: hello16:47
ttxmarkwash: hola!16:48
ttxhttps://launchpad.net/glance/+milestone/icehouse-216:48
ttxso, the idea for today would be to restrict that list to the currently-approved-but-stuck-in-gate stuff16:49
ttxand defer to i3 anything else16:49
*** hub_cap has joined #openstack-relmgr-office16:49
ttxmarkwash: does that work for you ?16:49
markwashthat's pretty close to where we're at, except there are a few things that just need that last approval16:49
markwashit works for me16:49
ttxif you can get them approved before meeting, you can keep them in (in Needs code review state)16:49
markwashokay16:50
ttxhttps://blueprints.launchpad.net/glance/+spec/glance-cmd+unittests is marked "started" so mihgt be a safe defer16:50
ttxsame for bugs, just keep the in-gate stuff, + any critical regressoin you might want to consider for backporting16:50
ttxmarkwash: at meeting today we'll discuss if it makes sense to defer milestone by one week, due to current gate backlog16:51
markwashokay cool16:51
markwashin that case, would we be able to pull some stuff back in? or is that just making the problem worse?16:51
ttxI think that makes the problem worse16:51
ttxbut if something makes it we'll retroactively add it16:52
ttxI'd like to keep i-2 focused on "stuff that should have made it if the gate wasn't so slow"16:52
markwashunderstood16:52
ttxrather than just add a week to the backlog16:52
ttxmarkwash: so, by meetig time, please only keep stuff that is already gating16:52
ttxthat way we'll have an accurate picture of in-flight stuff16:53
markwashnod16:53
ttxwhich will help us make a decision16:53
markwashany chance we can talk about the common openstack client stuff in the meeting today? (or did we cover that last week and I just didn't notice?)16:53
ttxwe didn't last week, we can try today, time permitting16:54
ttxplease add it to https://wiki.openstack.org/wiki/Meetings/ProjectMeeting#Agenda_for_next_meeting16:54
ttxmarkwash: anything else ?16:54
markwashnope that's it16:55
ttxcool, thx, see you there16:55
ttxhub_cap: around already ?16:56
hub_capaye16:56
hub_caplets do this16:56
ttxok, so same drill for you16:56
hub_capso the lows, i think will slip16:56
hub_capok hit me16:56
ttxreduce https://launchpad.net/trove/+milestone/icehouse-2 to the currently approved but stuck in gate stuff16:56
* hub_cap wasnt paying attn to the last meeting ;)16:56
hub_cap:o16:56
ttxremove anything that's not already gating16:56
ttx(defer to i3)16:57
hub_capk16:57
ttxsame thing for bugs -- except you may keep a critical regression  inthe list16:57
ttxotherwise defer to i3 stuff htat's not gating already16:57
hub_capis this to help alleviate the gate a bit? :)16:57
ttxNo, it is to help making a decision about deferring i2 by one week16:58
hub_capoh heh, its in 2 days16:58
ttxthe branch cut is today16:58
hub_capoh ic16:58
ttxso that way we can see how much is stuck due to gate16:58
ttxand if deferring the milestone cut by one week might not make sense16:58
ttx(if we have reasons to hope things will be getting better)16:58
hub_capk16:59
hub_capill clean it up16:59
ttxMy guess is that incremental-backups is not there yet16:59
ttxand I'll let you sort out which ones are approved and which ones are still under review16:59
hub_capyup16:59
hub_capill have it sorted in the next few16:59
ttxplease do so before meeting time16:59
hub_capyessir16:59
hub_capand no qs for me wrt the meeting this aftn17:00
ttxok, meeting is overloaded anyway :)17:00
hub_caphaha17:00
ttxstevebaker: might be having lunch during our regular 1:1 time, so feel free to ping me whenever you're around17:01
hub_capoh yes it will be interesting, i just looked at the situation17:01
ttxhub_cap: see you there17:01
hub_caperr the wiki17:01
hub_capyessir ttx, cu17:01
ttxmarkwash: added openstack common client topic to meeting agenda17:03
*** markwash has quit IRC17:03
hub_capttx: quick q17:14
ttxhub_cap: sure17:15
hub_capif i have a implemented stuck-in-gate review, do i mark that as implemented?17:15
hub_capfor a bp, sry17:15
ttxno, keep it needs code review17:16
ttxit's inaccurate but better than thinking it's all merged17:16
ttxin a sense, it needs the code review fro mthe gate system to pass17:16
hub_capsure, thx17:17
*** SergeyLukjanov_ is now known as SergeyLukjanov17:22
hub_capttx all clean, only 2 in flight (1 bp, 1 bug)17:28
ttxhub_cap: lucky you17:32
hub_capheh yea17:32
*** markwash has joined #openstack-relmgr-office18:15
*** markwash has quit IRC18:38
*** markwash has joined #openstack-relmgr-office18:41
*** markmcclain has joined #openstack-relmgr-office19:12
stevebakerttx: I'm about19:20
*** markmcclain has quit IRC19:32
ttxstevebaker: o/19:36
stevebaker\o19:37
ttxstevebaker: so.. given the gate situation the trick today is to defer stuff hat's not stuck in gate yet19:37
ttxso defer to i-3 things tha tare not already approved19:37
stevebakerIf there is a change that needs one more +2, can I give it?19:38
ttxyou may keep some one-off critical regression bug in19:38
ttxstevebaker: if you can get that second +2 in by meeting time, sure :)19:38
stevebakerok19:38
ttxI'd like an accurate representation of in-flight stuff19:38
ttxso that we make a final call on deferring the milestone or not19:38
stevebakerI'll go through them all and defer19:39
ttxstevebaker: is stack-check done, or is there more to it ?19:39
ttxalso https://blueprints.launchpad.net/heat/+spec/allowed-address-pairs was marked implemented. if that was doe recently you might consider adding it to icehouse-219:40
ttxdone*19:40
stevebakerit looks like no for stack-check19:40
ttxack19:40
ttxanything you'd like to discuss at meeting today ? We alrady have a few things (incl. gate situation) on hte agenda19:41
stevebakerI don't think so, just the gate ;)19:42
stevebakerthat critical bug looks ready to approve19:42
ttxok, then see you there!19:43
stevebakeroki later19:43
*** hub_cap has left #openstack-relmgr-office20:11
*** markwash has quit IRC20:12
*** markmcclain has joined #openstack-relmgr-office20:54
*** markwash has joined #openstack-relmgr-office21:07
*** markwash_ has joined #openstack-relmgr-office21:10
*** markwash has quit IRC21:12
*** markwash_ is now known as markwash21:12
*** markmcclain has quit IRC21:23
*** markmcclain has joined #openstack-relmgr-office21:24
*** SergeyLukjanov is now known as SergeyLukjanov_a22:50
*** SergeyLukjanov_a is now known as SergeyLukjanov_22:51
ttxmarkmcclain: back now23:28
ttxlet me know when done with your meeting23:28
*** markmcclain has quit IRC23:41

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!