Tuesday, 2014-02-04

*** markwash has joined #openstack-relmgr-office00:06
*** david-lyle has quit IRC00:16
*** david-lyle has joined #openstack-relmgr-office00:20
*** david_lyle_ has joined #openstack-relmgr-office00:55
*** david-lyle has quit IRC00:59
*** david-lyle has joined #openstack-relmgr-office01:40
*** david_lyle_ has quit IRC01:44
*** markmcclain1 has joined #openstack-relmgr-office01:54
*** markmcclain has quit IRC01:54
*** markmcclain1 has quit IRC01:56
*** markmcclain has joined #openstack-relmgr-office02:01
*** david-lyle has quit IRC02:29
*** markmcclain has quit IRC02:56
*** markwash has quit IRC02:59
*** david-lyle has joined #openstack-relmgr-office03:57
*** jgriffith has quit IRC04:24
*** jgriffith has joined #openstack-relmgr-office04:29
*** markmcclain has joined #openstack-relmgr-office05:28
*** markwash has joined #openstack-relmgr-office05:40
*** markwash has quit IRC06:02
*** jd__` has joined #openstack-relmgr-office06:37
*** mattoliverau has quit IRC06:38
*** jd__ has quit IRC06:38
*** jd__` is now known as jd__06:38
*** mattoliverau has joined #openstack-relmgr-office06:45
*** markmcclain has quit IRC07:10
*** russellb has joined #openstack-relmgr-office11:00
*** david-lyle has quit IRC11:29
*** markmcclain has joined #openstack-relmgr-office12:59
markmcclainttx: ready when you are12:59
ttxmarkmcclain: o/12:59
ttxhttps://launchpad.net/neutron/+milestone/icehouse-313:00
ttxmerging still blocked at this point, right13:00
markmcclainyes13:01
ttxyou mentioned some progress in working around the kernel issue ?13:02
markmcclainyes so we're working on only running the neutron tests with either metadata or config_drive13:02
markmcclainwhen key injection is activated the problem gets triggered easily13:03
ttxand that's what triggers the kernel crash ? (sorry, did not follow recent progress on that bug)13:04
ttxthought it was some process kill13:04
ttxin namespaces13:04
ttx(or is that a different issue)13:04
markmcclainthe kernel could not handle concurrent nbd and namespace usage13:05
markmcclainit triggered a race inside of the kernel13:05
ttxah.13:05
markmcclainand nova's key injection was using nbd13:05
ttxyeah, then metadata/config_dirve looks like a saner workaround that hacking kernel patches13:06
ttxthan*13:06
markmcclainyeah.. the kernel team also has more data to fix the kernel problem long term13:06
ttxmarkmcclain: <hen do you hope to have that .. test specialization ready ?13:07
ttxw*13:07
markmcclainwe've been making changes, but part of the problem is that devstack gate does not run all of the neutron gate tests13:07
markmcclainso we had to fix a few items first to allow us to get better data from the devstack check13:08
ttxcould you use the experimental pipeline to gather results ?13:08
markmcclainthat's what we ended up doing13:08
ttxmarkmcclain: so... progress sometimes this week ?13:08
markmcclainyeah I was really hoping to have it solve Friday, but turning off key injection has been a bit of chase13:09
ttxmarkmcclain: ok. In other news, ttx.py noticed a dependency issue in i3:13:09
ttx ml2-qos (Medium, scollins, icehouse-3) depends on quantum-qos-api-db (Low, scollins, next)13:09
ttxmight just be the other way around ?13:10
ttxhttps://blueprints.launchpad.net/neutron/+spec/ml2-qos13:10
markmcclainah… I'll go pull the bp out next make both medium13:10
ttxhttps://blueprints.launchpad.net/neutron/+spec/quantum-qos-api-db13:10
ttxit's more, the other one might need to go from next to icehouse-313:10
ttxand to medium13:11
markmcclainright.. I just pulled qos-api into I-3 and made it med13:11
ttxmarkmcclain: otherwise things don't look to bad. Your stuff is in order, and apart from landing, progress looks good13:11
markmcclainyeah…I'll be happy once we can reliably merge just get the backlog cleared13:12
ttxanything you'd like to discuss at project meeting later ?13:12
markmcclainalso not sure if you saw it, but the kernel bug is affecting stable too13:12
ttxmarkmcclain: yes, not really surprising13:13
markmcclainotherwise that's all I have13:13
ttxok, thx!13:14
ttxdhellmann: ready when you are13:15
dhellmannhere13:16
dhellmanngood morning/afternoon13:16
ttxdhellmann: aloha!13:16
ttxhttps://launchpad.net/oslo/+milestone/icehouse-313:16
ttxYou have to BPs to triage in there13:16
ttxtwo*13:16
dhellmannyeah, those snuck in very recently13:16
dhellmannI was just reviewing priorities on a few others with the owners13:17
dhellmannI'll take care of those 2 today13:17
dhellmanncan anyone set the milestone on a bp?13:17
ttxdhellmann: yes13:17
dhellmannthat explains it13:18
ttxdhellmann: you control only the priority and series goal field13:18
* dhellmann hopes storyboard provides email notifications for those sorts of changes on blueprints as well as tickets13:18
ttxand I have series goal set according to the value of target milestone, for coherence reasons13:18
dhellmannsure13:18
dhellmannI'll contact the owners and see what's what13:18
ttxotherwise progress looks good, wouldn't hurt to start completing stuff13:18
dhellmannheh13:18
ttxcongestion control :)13:19
dhellmannwe worked out the issues around log translation in our meeting last week, so that just needs review13:19
ttxhttps://launchpad.net/oslo.messaging/+milestone/icehouse-313:19
ttxsame comments13:19
dhellmannthat un-owned bug is mark's13:20
dhellmannjust got that confirmed via email, and the bug is now updated13:20
ttxShould we add https://bugs.launchpad.net/bugs/1272271 to icehouse-3 as well ?13:20
dhellmannyes, done13:21
ttxSaw you added one topic to meeting already. Anything else on your mind ?13:21
dhellmannno, I think that covers it13:22
ttxok, thanks!13:22
dhellmannthanks!13:22
ttxjd__: ready when you are13:29
ttxno jd__ ?13:37
jd__sorry, in a call13:38
ttxjd__: available later ?13:38
jd__ttx: yes13:42
ttxok ping me13:42
jd__ttx: ping13:45
ttxok, let's do this quickly13:45
ttxhttps://launchpad.net/ceilometer/+milestone/icehouse-313:45
ttxYou're good on the landing side, but not so many things under review13:46
ttxwanted to review those two "slow progress"13:46
jd__yeah I need to sync up with sileht but we did made some progress13:46
ttxok, so still likely to make it, right ?13:47
jd__at least on the oslo.messaging side, and sileht has a working port13:47
jd__yes!13:47
jd__replace-rpc-cast-with-notifications may slip but switch-to-oslo.messaging looks good13:47
ttxyes, that other one does not sound that critical to me13:47
ttxwhereas oslo.messaging would be a great win13:48
jd__yeah, I've changed to 'good progress' based on sileht feedback I got a few minutes ago13:48
ttxok that's all I had. Anything you want to discuss later ?13:48
jd__nop13:48
ttxok, thanks and see you then13:49
ttxjgriffith: ready when you are13:49
jgriffithttx good morning13:50
ttxjgriffith: hi!13:50
ttxhttps://launchpad.net/cinder/+milestone/icehouse-313:50
ttxlots of stuff to triage13:50
jgriffithttx:yeah, noticed all the new stuff last night13:51
jgriffithttx: it's like the mail... keeps showing up at my door13:51
ttxThe guys behind nimble-iscsi-volume-driver asked me about status, fwiw13:51
ttxhttps://blueprints.launchpad.net/cinder/+spec/nimble-iscsi-volume-driver13:51
ttxthey pretend to have code almost there13:52
ttxyou probably got their emails too13:52
jgriffithsame old story, I hear every week13:52
jgriffithemails, phone calls and even an in person meet13:52
jgriffithmeat13:52
jgriffithwhatever13:52
jgriffithmy response is still, great, submit the patch13:52
ttxYou can use "Low" liberally for stuff you have no idea about13:52
jgriffithI suppose that's nicer than kicking it out as I had planned :)13:53
ttxso that they submit the patch and you can decide based on that13:53
jgriffithYep, perfect13:53
ttxYou still have room in the high priority if you want to give your current "Low" more importance13:53
jgriffithYeah, I"ll rebalance some things this morning I think13:54
jgriffiththe landscape has changed a bit in the past couple weeks13:54
ttxjgriffith: was wondering about the 2 "not started" ones at the top of the list13:54
jgriffithThe oslo one I"m not planning to take13:55
jgriffithgiven what I've been looking at in Nova13:55
jgriffithunless the logfiles are fixed13:55
ttxif the port to oslo.messaging wasn't started yet it may be better to defer13:55
ttxnot exactly the sort of thing you want to land late13:55
jgriffithI agree13:56
ttxor get into a freeze exception with13:56
jgriffithMy V6 item... I'll make low13:56
jgriffithit may not be important13:56
jgriffithttx: it's not a big patch or hard to do, just need some things to settle in core-cinder first13:56
ttxagreed13:57
ttxgood to free some time for core reviewers as drivers requests pile up, too13:57
ttxthat's why planning your own work to -1 and -2 is better, since so many things are proposed for -313:57
jgriffithYeah... another on-slaught :)13:57
ttxyou have to make time for handling those13:57
ttxthat's all I had13:58
ttxanything you'd like to discuss at meeting later ? anything blocking you ?13:58
jgriffithI think that's it from me on the rlease side13:58
jgriffithNahh.. nothing blocking13:58
ttxok, so triage + reprioritize a bit and we should be good13:58
ttxsee you then13:59
jgriffithYeah, I'll have it done by the meeting13:59
jgriffiththanks..cya13:59
ttxnice. gate queue down to 5 at 1400 UTC13:59
ttxpretty rare13:59
*** mattoliverau has quit IRC14:09
*** markmcclain has quit IRC14:15
ttxdolphm: ready when you are15:01
dolphmttx: o/15:01
ttxhttps://launchpad.net/keystone/+milestone/icehouse-315:02
ttxstatus looks sane and on track15:03
ttxWas work on ephemeral-pki-tokens started ?15:03
dolphmi don't believe so15:04
ttxit's light IIRC though15:04
dolphmcorrect15:04
ttxthe sooner you push it, the better15:04
ttxgood to get important things while the queue is empty15:04
ttxok, you look in pretty good shape15:05
ttxanything you wanted to discuss at meeting ?15:05
dolphmfair enough -- it can probably be in review soon, based on the revocation events patch15:05
dolphmfor the meeting, yes15:05
dolphmannegentle requested on the -dev list that we discuss the move to unversioned endpoints in the service catalog15:06
dolphmi'm certainly happy to do so, as i'm not terribly happy with the versioned service types that slipped into havana (computev3, etc)15:06
ttxok adding. Do you have a link to the ML post ?15:06
ttxgot it15:07
ttxhttp://lists.openstack.org/pipermail/openstack-dev/2014-February/026079.html15:08
ttxadded15:08
ttxdolphm: anything else ?15:08
dolphmthat's it!15:08
ttxok, thx!15:08
russellbfwiw, computev3 can be ripped out anytime IMO, it's not supported yet15:08
dolphmrussellb: pleeeeease15:09
russellbjust need to coordinate it with novaclient probably15:09
russellbbut no backwards compat concerns since it's unsupported at this point15:09
dolphmrussellb: exactly, and i'm hoping keystoneclient can set the precedent on proper discovery15:09
russellbcool15:09
russellbttx: on nova, good news is today was blueprint approval deadline, so i can start deferring a ton of stuff :-)15:11
ttxrussellb: heh15:11
russellball day meetings yesterday and today, so haven't had a chance to start deferring, but will asap (tonight and/or tomorrow)15:12
ttxhttps://launchpad.net/nova/+milestone/icehouse-315:12
ttxhttps://bugs.launchpad.net/nova/+bug/1273556 is critical, should I target to i3 ?15:14
russellbsure, might as ewll15:14
russellbhelp raise visibility15:15
russellbi'm still not convinced that "mark all bugs that occur in gate as critical" is not insane15:15
ttxfwiw we are looking into expressing "priority" in a smarter way in storyboard15:15
ttxsomething more personal and multi-dimensional15:16
russellbthat'd be great15:16
russellbwe're going to have to revisit our plan again for juno15:16
ttxyep15:16
russellbi'm not sure what the plan should be yet ...15:16
russellbcouple of ideas15:17
ttxI'll revisit the i3 map once you clean it up15:17
ttxlet me know when you're done15:17
ttxdoesn't have to be today... sometime this week15:17
russellb1) go back to more arbitrary prioritization ... and 2) use the nova-core sponsor thing, but add that we won't even let something get prioritized at all or targeted at all until it's sponsored15:17
russellbsure, will get on it asap15:17
russellbso on this, i have another thing i wanted to mention to you15:17
russellbon the whole ... scaling nova leadership area15:17
russellbthis cycle, getting more help from nova-drivers in reviewing blueprints was helpful15:18
russellbi think the next thing I (or whoever the nova PTL is) needs is a person that helps manage the roadmap as their primary task15:18
russellbit's too big for me to be able to keep on top of it, and actually do technical leadership too15:18
ttxrelease management liaison ?15:18
russellbyes15:18
ttxright, like you did for vishy back then15:19
ttxmakes sense to me15:19
ttxif you can find your Russell15:19
russellbso i want to try to find someone, but also wanted it on your radar too, because obviously it would impact nova - release interaction15:19
russellbif anyone comes to mind for you, let me know :)15:20
russellbotherwise i'll be searching15:20
ttxheh15:20
ttx!me15:20
openstackttx: Error: "me" is not a valid command.15:20
russellbright, don't expect it from you15:20
ttxok, anything you want to discuss at meeting ?15:21
ttxwas wondering about the novanet/v3 thing15:21
ttxor is that settled15:21
russellbi'll be in a car heading to an airport at that time, should be able to join from the car though...15:21
russellbi think it's roughly settled15:21
ttxok then see you there ?15:22
russellbsure15:22
russellboh, thanks for your velocity blog post15:22
russellbgood points in there15:22
russellbdidn't think to compare back to grizzly15:22
russellband hadn't looked at bugs15:22
russellbother big nova project thing is review bandwidth (not that new) ... need to revisit nova-core i think, some current folks not as active15:23
russellbwe need to pick up review bandwidth15:23
russellbanyway, just random thoughts i guess15:23
russellbthings affecting quality / velocity of roadmap :)15:24
ttxyeah, i wanted to look at reviews as well15:24
russellbi've done a lot of review stats, but i've never done historical analysis15:26
russellblast 90 days versus a 90 day period a while ago, for example15:26
russellbalways more to analyze ...15:26
ttxlyle: around?15:34
*** david-lyle has joined #openstack-relmgr-office15:34
ttxdavid-lyle: howdy15:34
david-lylehello15:34
ttxhttps://launchpad.net/horizon/+milestone/icehouse-315:35
ttxlooks sane to me15:35
ttxdjango-angular-integration needs an assignee or be removed15:35
david-lyleyes, will likely remove15:36
ttxseparate-horizon-from-dashboard (Medium, mrunge, icehouse-3) depends on remove-javascript-bundling (Undefined, mrunge, No milestone) -- maybe add it to icehouse-3 ?15:36
ttxotherwise progress looks good15:36
david-lyleI think both may be early juno, the javascript split was a late addition15:37
david-lylelots of work15:37
david-lyleI think we're on target otherwise15:37
ttxyep15:37
ttxanything blocking you ? Anything you'd like to discuss at meeting ?15:38
david-lyleno, I think we're good.  With the gate back in order, we just need to land some patches15:38
ttxack15:39
ttxsee you there15:39
david-lylesounds good15:39
notmynamettx: ready when you are16:20
ttxnotmyname: o/16:31
notmynamehello16:31
notmynameI don't think I have a lot to report. 1.12 is out, progress is being made towards some changes in swiftclient16:31
notmynamegood progress is being made on storage policies for icehouse16:31
notmynamestill undetermined if we'll have 1 or 2 releases before icehouse16:32
ttxyep16:32
ttxlooks like I haven't created milestone 1.13.0 yet. Want me to ?16:32
notmynameyes, please16:32
ttxdone. you can move next-icehouse stuff to it: https://launchpad.net/swift/+milestone/1.13.016:33
notmynameok, will do16:33
ttxany topic for meeting later ?16:33
notmynamethings currently keeping me up at night include the depth of the review queue and effective ways to tackle that16:33
notmynameI don't htink that's a project-wide meeting topic, so I don't have anything for the meeting today16:34
ttxnotmyname: the swift review queue ?16:34
* ttx checks16:34
notmynameya. https://review.openstack.org/#/q/-status:workinprogress+AND+status:open+AND+(project:openstack/swift-bench+OR+project:openstack/object-api+OR+project:openstack/swift+OR+project:openstack/python-swiftclient),n,z16:34
ttximpressive indeed16:35
notmynameI don't know how that compares in other projects (but I'm not trying to compare)16:35
notmynameI simply want it to be shorter16:35
ttxlooking at your reviewer stats16:36
ttxhttp://russellbryant.net/openstack-stats/swift-reviewers-60.txt16:36
notmynameya, I've been looking there too. anyway, just what I've been thinking on lately16:37
ttxyour core group seems to match review activity16:37
notmynameyes16:37
ttxcschwede / rahmu could be considered added if you think you could use more bandwidth16:37
ttx(no idea how good they are in reviews though)16:37
ttxok well... see you at meeting later16:38
notmynameI'm not looking to add new people, necessarily. I'd prefer something more structural. but I don't have too many ideas now.16:38
notmynameok. later16:38
*** markwash has joined #openstack-relmgr-office16:41
*** markmcclain has joined #openstack-relmgr-office16:42
ttxmarkwash: o/16:45
markwashttx hi there16:46
*** SergeyLukjanov is now known as SergeyLukjanov_a16:46
ttxhttps://launchpad.net/glance/+milestone/icehouse-316:46
ttxone untriaged blueprint16:47
ttxhttps://blueprints.launchpad.net/glance/+spec/replace-mox-with-mock16:47
ttx+ 2 unassigned ones:16:47
ttxhttps://blueprints.launchpad.net/glance/+spec/expose-owner-in-v216:47
ttxhttps://blueprints.launchpad.net/glance/+spec/expose-owner-in-v216:47
ttxerr16:47
ttxhttps://blueprints.launchpad.net/glance/+spec/expose-owner-in-v216:47
ttxdamn copy paste16:47
ttxhttps://blueprints.launchpad.net/glance/+spec/community-level-v2-image-sharing16:47
markwashI just assigned expose-owner-in-v2 to flwang since he already has a review up for it16:48
* ttx marks it started then16:48
markwashI will ask rosmaita for an owner for "community-level-…" when we meet for bp triage here in a few minutes16:49
markwashand the untriaged one. . I'm still thinking about it :-)16:49
ttxok16:49
markwashI thought we had a plan for mox packages for python 3, no?16:50
ttxI thought so yes16:50
markwashnot that I'm a fan of mox16:50
markwashhmm16:50
markwashoh well16:50
ttxmox3 or mock16:51
ttxAs far as progress goes, this is slightly behind...16:51
*** hub_cap has joined #openstack-relmgr-office16:51
ttxwould be good to have more stuff ready for review, and more stuff completed16:51
markwashyes16:51
ttxbut you're not too far behind either16:51
markwashwe will kick some more stuff out as well16:51
markwashtoday16:52
ttxhttps://bugs.launchpad.net/bugs/1272136 is "critical", should I add it to the i3 list ?16:52
markwashmaybe we should make it "high" instead16:52
ttxok, making high16:53
ttxthat's all I had. Anything you want to discuss at meeting later ?16:53
markwashpossibly16:53
hub_capttx: s/making/getting ?16:53
markwashI have a quick question for  you16:53
markwashat the Glance summit we discussed the general murano / heat artifact repository idea16:53
markwashand in general thought it was the right direction16:54
markwashI'm just a little bit worried that this is a scope expansion for the Images program16:54
markwashwhich would mean we'd need some cross project or TC interaction perhaps?16:54
markwashwho do we need to talk to? or just go for it?16:54
markwashI think the images program currently lacks a mission statement, it could be a discussion around adding one16:55
ttxmarkwash: you will definitely need to have some TC discussion about it16:55
ttxmarkwash: that said, raising it at cross-project meeting first might be a good idea16:55
ttxmake sure the others are comfortable with that scope expansion before you start pushing it16:56
markwashhows the agenda for today?16:56
ttxso I would add it for meeting today to judge the temperature, then start a thread on -dev about expanded scope and mission statement16:56
markwashall right, let's give that a shot16:57
ttxthen it could appear on the TC radar as a governance repo change16:57
ttxadding to today's agenda16:57
markwashI'll try to prepare a few lines to present it adequately16:59
ttxhub_cap: o/17:02
hub_caphowdy ttx17:02
ttxhttps://launchpad.net/trove/+milestone/icehouse-317:02
hub_capso just so u know, ive put another bp into i317:02
hub_capits a sub-feature of configuration mgmt17:03
ttx2 non-prioritized BPs in there17:03
hub_capaka, a shift in the wa i wanted some data represented17:03
hub_capyup ill fix them now17:03
ttxok17:03
hub_capk17:04
hub_capat this point, the big ones are getting c*, mongo, and config mgmt in17:04
* ttx refreshes17:04
hub_capand xml removal17:04
hub_capso if the others slip, im fine w/ that17:04
hub_capwe might need a FFE For config mgmt, and possibly some mgmt api stuff17:05
hub_capbut we can cross that bridge when we get closer to our cutoff17:05
ttxok17:05
ttxprogress looks good, although you could "complete" more things17:06
hub_capi still feel confident everything will merge tho17:06
hub_capyea17:06
hub_capthe break nuked our productivity17:06
ttxhttps://bugs.launchpad.net/bugs/1252897 is critical17:06
hub_capso those are still in progress17:06
ttxshould it appear on the i3 list ?17:06
* hub_cap checks17:06
hub_capfixed17:06
ttxit's on the "trove next" list17:06
hub_capits a nebulous bug that had one "Case" fixed17:06
hub_capso i put it to wishlist17:07
ttxmaybe downgrade to "high" ?17:07
ttxotherwise I'll keep forgetting about it :)17:07
hub_capk, its not something ive seen in a long while17:07
hub_capi almost suspect it just needs to be cleaned up at this point17:07
ttxand ask again and again17:07
hub_caphahaha17:07
ttxok, anything you'd like to see discussed later ?17:08
hub_capok fixef again17:08
hub_capnot at present.. just still trying to find a good way to do blueprints that make our developers effective heh17:08
hub_capany progress on the replacement?17:08
ttxslow progress.17:09
ttxbut should go faster once the basics are nailed17:09
ttxwe have CD now17:09
hub_caphell yea17:09
hub_capprolly still lookin at a full cycle before we can adopt ya?17:10
hub_capeven early adopters ;)17:10
ttxyeah. infra is expected to start dogfooding soon17:10
ttxhope to have a good story to sell by next summit17:10
hub_capgreat! id love to help out w/ early adoption17:11
ttxfamous last words17:11
hub_capim _sure_ the trove team will be happy w/ it :)17:11
hub_capdude can it be worse than bps??17:11
hub_cap;)17:11
hub_caplook, give me 3 textboxes, 2 "search/tag" fields17:12
ttxwell. ATL it doesn't have AUTHENTICATION.17:12
hub_capand u have bluepritnts LOL17:12
ttxATM*17:12
ttxso it's pretty bare :P17:12
hub_capoh ill wait till auth ;)17:12
hub_capbut great to know its comin along17:12
ttxok, ttyl17:13
hub_capcu17:13
*** hub_cap has left #openstack-relmgr-office17:14
*** SergeyLukjanov_a is now known as SergeyLukjanov18:05
*** markmcclain has quit IRC18:40
*** markmcclain1 has joined #openstack-relmgr-office19:00
*** markmcclain1 has quit IRC19:01
*** markmcclain has joined #openstack-relmgr-office19:06
*** zaneb has joined #openstack-relmgr-office19:30
zanebttx: o/ I am proxy-stevebaker for the week19:30
ttxzaneb: o/19:34
* ttx refreshes19:35
ttxhttps://launchpad.net/heat/+milestone/icehouse-319:35
zanebso I was just discussing some of the autoscaling ones today with radix19:36
ttxTwo blueprints without a priority19:36
ttxhttps://blueprints.launchpad.net/heat/+spec/i18n-messages19:36
zaneband it looks like a few of those need to get bumped19:36
ttxhttps://blueprints.launchpad.net/heat/+spec/send-notification-autoscaling19:36
ttxone of them being marked already implemented19:36
ttxshould I just give a low prio to the last one so that it doesn't send anymore alerts ?19:37
zaneblet's call that one high-priority then ;)19:37
ttxhah19:37
ttxI'll make it "medium" sounds fair enough19:37
zanebsplit the difference :D19:37
ttxIs the other one (i18) something wanted or not ?19:38
ttxi18n19:38
zanebyes, I think it is19:38
ttxok, let's make it low and see19:38
zaneband I know that's an area that Liang focuses on19:38
ttxso yeah.. there are 3 without assignee, including one autoscaling one19:39
ttxwas that what you wanted to discuss ?19:39
zanebno, but I definitely don't see that one happening in icehouse19:40
ttxso.. radix's "high" ones ?19:40
zanebwe're short on time even for the ones that do have assignees19:40
zanebhttps://blueprints.launchpad.net/heat/+spec/as-engine should be bumped to Juno19:41
ttxagreed -- you should start deferring19:41
ttxzaneb: want me to do it ?19:41
zanebI just moved that one to 'next'19:41
ttxack19:41
zanebditto for https://blueprints.launchpad.net/heat/+spec/autoscaling-api19:42
ttxzaneb: we don't need to go through them right now. But I agree you need to trim the plan down significantly at this point19:42
zanebok, cool19:42
ttxas soon as you're reasonably sure it won't make it, move to next19:42
ttxthat will allow to focus review resources on stuff that might make it19:43
zanebsure, will do19:43
ttxrather than chasing red herrings19:43
ttxI'd suggest to defer those without assignees too19:43
ttxI noticed a few dep issues19:43
ttxupdate-failure-recovery (High, zaneb, icehouse-3) depends on resource-template-api (Undefined, No assignee, No milestone) and retry-failed-update (Low, clint-fewbar, icehouse-3)19:44
zanebI just bumped update-failure-recover to next19:44
ttxah19:44
* ttx refreshes again19:44
ttxok, looks better now19:45
zanebI'll assign myself to resource-template-api19:45
ttxx-auth-trust depends on an untargeted keystone blueprint (trusts-chained-delegation)19:45
zaneband set low priority19:45
ttxwant us to raise that one at the meeting ?19:46
zanebyes, that's probably a good idea19:46
ttxok, added19:46
zanebI just ping shardy for an update19:47
ttxright -- no need to discuss it if he plans to drop it19:47
zanebhopefully I can say something intelligent about it at the meeting ;)19:47
ttxok, I think that's all I had19:48
ttxanytyhing else you wanted to discuss at meeting ?19:48
ttxanything blocking you ?19:48
zanebnot that I know of :)19:48
ttxOK then. Go and aggressively defer.19:48
ttxSee you later :)19:48
ttxoh. wait19:48
ttxzaneb: was wondering if https://blueprints.launchpad.net/heat/+spec/hot-select wasn't completed with the merging of https://review.openstack.org/#/c/67562/19:49
zanebyep, looks like it is done19:50
ttxzaneb: ok, you can set it to implemented then19:50
ttxthat is all19:50
zanebwill do, thanks :)19:50
dolphmttx: what's the scoop on hudson not linking bp & bugs to code reviews anymore?19:59
ttxno idea19:59
zanebdolphm: https://review.openstack.org/#/c/64738/20:06
*** markmcclain has quit IRC20:38
*** markmcclain has joined #openstack-relmgr-office20:45
*** mattoliverau has joined #openstack-relmgr-office21:17
dolphmregarding our 1v1 this morning and annegentle's request to discuss versioned endpoints in today's meeting; there's a second thread on list that has been very active today, and frankly i'm not caught up on it yet21:18
dolphmi'm guessing it addresses/discusses what anne was looking for21:19
dolphmttx: ^21:20
ttxack21:25
ttxzaneb: question in  #openstack-meeting21:51
ttxon that keystone/heat dep21:51
*** david-lyle has quit IRC22:04
*** markmcclain has quit IRC22:26
*** markmcclain has joined #openstack-relmgr-office22:33
*** markmcclain has quit IRC23:25
*** markmcclain has joined #openstack-relmgr-office23:54

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