Tuesday, 2015-02-03

*** jraim has quit IRC01:09
*** jraim has joined #openstack-relmgr-office01:14
*** asalkeld has joined #openstack-relmgr-office08:35
ttxasalkeld: I'll be 5 min late09:00
asalkeldnp09:00
ttxsorry bout that09:06
ttx#startmeeting ptl_sync09:06
openstackMeeting started Tue Feb  3 09:06:31 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:06
ttx#topic Heat09:06
openstackThe meeting name has been set to 'ptl_sync'09:06
ttxasalkeld: o/09:06
asalkeldhi09:06
ttx#link https://launchpad.net/heat/+milestone/kilo-209:07
asalkeldi think it's in ok shape09:07
asalkeldthere are 2 bugs and 2 bps soon to go in09:07
ttxStill have 2 open BPs and 2 open bugs, are we trying to get those in before the tag ?09:07
asalkeldttx, just to be clear, the tag is in 2 days?09:07
asalkeldon the 5th09:07
ttxThe tag window is Tuesday-Thursday09:08
ttxso anytime during the window is fine09:08
* ttx checks the Bp<->review mapping09:08
asalkeldmy wed-frid09:08
asalkeldttx, i'll keep that in mind09:08
ttxdecouple-nested is waiting on the 3 at https://review.openstack.org/#/q/topic:bp/decouple-nested,n,z ?09:08
asalkeldall those *should* be ok09:08
asalkeldttx, yeah i have taken that one over09:09
ttxstack-breakpoint waiting on https://review.openstack.org/#/c/146123/09:09
asalkeldif it can't make it, i'll move to k309:09
asalkeldbreakpoint should be fine09:09
asalkeldjust one patch09:09
ttxbug 1411103 on https://review.openstack.org/#/c/147463/09:09
ttx140669209:09
ttxdoesn't seem to have areview up yet09:10
ttxis that correct ?09:10
asalkeldbut you just point out the review?09:10
asalkeldooo, different numbre09:11
ttxbug 140669209:11
asalkeldwe can move that one09:11
ttxok, moving09:11
asalkeldpushed to k309:11
ttxOK, that sounds like a reasonable number of things to wait on09:12
asalkeldcool, i'll try my best to get all that in09:12
ttxI'll track progress against those reviews09:12
ttxand will confirm itr's good to go once they are in09:12
asalkeldthx!09:12
ttx(and ping you if they obviously won't make it during the tag window)09:12
ttxasalkeld: looks good to me... questions on your side ?09:13
asalkeldttx, when you ideally like to tag09:13
asalkeldso i can gauge when this should be in09:13
ttxI like to tag on my Wednesday morning, your Wednesday evening09:13
asalkeldutc09:13
asalkeldok09:13
ttxbut it's fine to do Thursday morning too09:13
asalkeldthat's all godd09:13
ttxI don't like Thursday evening that much09:14
ttxbut you should be sleeping then :)09:14
asalkeldlol09:14
asalkeldok, all good from my end09:14
ttxok, if you don't have other questions, have a good week!09:14
asalkeldyou too09:14
* ttx waits for johnthetubaguy09:15
*** zz_johnthetubagu is now known as johnthetubaguy09:27
johnthetubaguyttx: hey, sorry for the wait09:27
ttxjohnthetubaguy: o/09:28
ttx#topic Nova09:28
ttx#link https://launchpad.net/nova/+milestone/kilo-209:28
johnthetubaguycool09:28
ttxpretty impressive list of stuff under review here09:28
johnthetubaguyyeah, its gone a bit mad09:29
johnthetubaguypeople actually got their code up for review, which is nice09:29
ttxjohnthetubaguy: what do you expect will happen ? a few of them merge and we defer the others ?09:29
johnthetubaguyI actually expect to defer all the low ones, that have no patches merged yet09:30
ttxOr do you plan to start pushing back to L ?09:30
johnthetubaguyyeah09:30
johnthetubaguydefer to L for those09:30
ttxWould deferring now help in prioritizing reviews, or not so much ?09:30
johnthetubaguyso, possibly, I was going to check through the list, and see if there are BPs with old −1s on the reviews, etc09:31
ttxI'm a bit concerned with this multi-month feature freeze for non-priority stuff09:31
ttxHistorically, feature freeze was relatively well accepted because it's onlt a couple weeks before we open the next dev branch09:31
ttxWill be a harder sell if it's a couple months away09:32
johnthetubaguyyes, its basically us trying to do the slots things, just only for one sprint09:32
ttxpeople with those patches will have to rebase against master and keep them in the fridge09:32
johnthetubaguyjust we don't see how we can get the priority stuff merged otherwise09:32
ttxright, not saying you shouldn't do it09:33
ttxjust wondering how well that would be accepted, given how many patches fall into that group09:33
johnthetubaguyyeah, I mean, lets be honest, its a massive experiment09:33
johnthetubaguypeople seemed to agree on the priorities as being important, and bug fixes09:33
ttxA number of them have been asking for exceptions right09:33
johnthetubaguyyes, but those where mostly the specs we didn't get merged09:34
johnthetubaguyat least up until this point09:34
ttxhmm, ok09:34
johnthetubaguyyeah, its madness, we have way more code than we can review at this point, this is our attempt at being honest and telling people its no going to happen09:35
ttxjohnthetubaguy: so I guess we should wait as much as we can before we tag09:35
ttxwhatever gets in is in09:35
johnthetubaguyyes, thats fair09:35
ttxhow about we have this same discussion on Thursday and see if there is value in waiting a feqw more hours ?09:35
johnthetubaguyI think, the stuff thats almost, but not quite in, I might let slide into the first week of kilo-3, without too much process, but lets see how it looks I guess09:35
johnthetubaguyI am good with that, I mean, maybe we catch up tomorrow morning, so see how the burn down is looking?09:36
ttxjohnthetubaguy: sounds good09:36
ttxjohnthetubaguy: I have been discussing recently the value of milestone targeting... It's a lot of effort to maintain and we consistently miss our predictions09:37
johnthetubaguyI mean, we spoke about actually aiming for zero exceptions this time, possibly over-roating though09:37
johnthetubaguyyes, that came up at the midcycle actually09:37
ttxjohnthetubaguy: we could technically take the linux approach and not even try to predict. Just collect whatever is landed09:37
johnthetubaguycan't say we had any great ideas, yeah, thats the only one that came up09:37
ttxThe milestone is still useful as a reference date, the tag is still useful as a way to exercise the machinery09:38
ttxbut as a promise, it's not that great09:38
ttxjohnthetubaguy: and not having to maintain it would free us to do more useful things09:39
ttxlike focus on priority tasks09:39
johnthetubaguyvery true, I am keen on the idea09:39
johnthetubaguyI guess we have to try it to know how it looks09:39
ttxI will think about it a bit more... and probably start a thread on the ML09:39
johnthetubaguywe should be able to have tooling to automatically fill in the milestone after we tag, I guess09:39
ttxI know some projects are attached to producing meaningful milestones09:40
ttxthe milestone in LP always had two meanings09:40
johnthetubaguyttx: appreciated, it should make things more scalable09:40
ttxthe promise and the actual delivery09:40
ttxusing the same damn field09:40
johnthetubaguyah, thats true09:40
ttxwhich causes all sort of pain09:40
ttxThe delivery is still very useful09:40
johnthetubaguyyeah, we sorta stopped bothering with the promise, mostly, without telling people09:41
johnthetubaguyyeah, if we can automate that, then awesome :)09:41
ttxcollecting what was merged when we tag and add it as a delivery milestone to the bug, very good09:41
ttxusing a single list of things to track, not so good09:41
ttxthat tension shows in how we use those milestone pages09:42
johnthetubaguyyeah09:42
ttxsometimes those are targets of opprtunity, sometimes those are milestone tag blockers09:42
ttxand then suddenly we purge it and it becomes the list of stuff actually landed09:42
johnthetubaguypriority is better for, this should go in first, then defer it if its too late for this release09:42
ttx(fwiw in storyboard we don't really replicate the concept of "promised milestone")09:43
johnthetubaguyyeah, thats a good way of talking about the problem, not thought about it as clearly as that before09:43
ttx(and you should be able to use multiple "priority lists" to track random stuff)09:43
ttxone could be milestone blockers, another could be targets of opportunity etc)09:43
ttxTargeting tasks against a future milestone is still useful for RC tracking09:43
johnthetubaguythats true09:44
ttxbut that's actaully the exception rather than the rule09:44
johnthetubaguyyeah09:44
ttxanyway, random thoughts09:44
johnthetubaguyI mean the discussion we had before was interesting09:44
ttxjust wanted to check where you stood on that09:44
johnthetubaguyfeature freeze time, we are really good at merging things09:44
johnthetubaguybecause we have a smaller list to focus on09:44
johnthetubaguyso keeping that, maybe using priorities, sounds good09:45
johnthetubaguyignoring milestones, for want of a better word, should free up more time to set priorities better, etc09:45
ttxjohnthetubaguy: identifying those BPs which are 99% there could be a useful way to prioritize reviews09:45
ttx(for k2)09:46
johnthetubaguyyeah, I think I am going to go do that09:46
ttxbecause those 99% there won't take a two-months wait that gracefully09:46
johnthetubaguythis stuff has some +2s, lets finish it off, etc09:46
johnthetubaguyagreed09:46
ttxeven if it's Low.09:46
johnthetubaguyyeah, that makes them more angry, honestly09:47
ttxso yes, identifying a few things that could easily make it with some focus could help09:47
ttxalright, I'll talk to you later this week as we approach the fatidic tag09:47
ttxjohnthetubaguy: did you have any question ?09:49
johnthetubaguyttx: I am good, thanks for your help09:49
johnthetubaguylooking forward to the thoughts on milestones09:49
ttxjohnthetubaguy: ack, have a good day!09:49
johnthetubaguyany you!09:50
johnthetubaguyops09:50
johnthetubaguyand you!09:50
*** asalkeld has left #openstack-relmgr-office11:12
ttxeglynn: around?13:00
*** eglynn has joined #openstack-relmgr-office13:00
eglynnttx: hey13:00
ttx#topic Ceilometer13:00
ttxeglynn: hi!13:00
ttx#link https://launchpad.net/ceilometer/+milestone/kilo-213:01
eglynn#link https://launchpad.net/ceilometer/+milestone/kilo-213:01
ttxI see 4 BPs and one bug.13:01
eglynnI've already bumped the BP that won't make it13:01
ttxAll things you'd like to wait on before we tag ?13:01
eglynnthe others are likely to hand later today or early tmrw13:01
eglynn*land13:01
ttxchecking blocking reviews13:01
eglynnjust minor nits in tests etc.13:02
ttxdisk-info-meters pending on https://review.openstack.org/#/c/145819/13:02
eglynnyeap, that's the only one I'm slightly concerned about13:02
ttxhyper-v-disk-latency-metrics pending on .. ? all merged?13:02
eglynna-ha yes, updating status13:03
ttxdeclarative-http-tests pending on https://review.openstack.org/#/c/146187/13:03
eglynnyep, cdent is working on the last test nit as we speak13:03
ttxelasticsearch-driver pending on ... https://review.openstack.org/#/c/137131/ ?13:04
eglynnyep gordc will be online soon to get that over the line today13:04
ttxcan't find the change in Gerrit for https://bugs.launchpad.net/ceilometer/+bug/140378713:04
eglynndarn, I mean to bump that13:05
ttxAlso ceilometermiddleware is marked completed but https://review.openstack.org/#/c/151744/ is still in flight13:05
eglynndone now13:05
ttxshould it be reverted to NeedsCodeReview?13:06
eglynnyeap, we were looking that just now ... I've +A'd the patch13:07
ttxok, let's mark it NeedsCodeReview until patch makes it ?13:07
eglynnok, done13:08
ttxOK, so I'll keep track of those last things and ping you when I think we can tag. If they don't burn down in time, I'll ping you to remove blockers13:08
eglynnsounds like a plan13:08
ttxor just contact me when the page is all set :)13:08
eglynncool, will do13:08
ttxalright. Questions on your side ?13:09
eglynnnope13:09
ttxalrighy then13:09
ttx+t13:09
ttxSergeyLukjanov: you around?13:09
eglynnthank you for your time!13:09
ttxeglynn: have a good week13:09
SergeyLukjanovttx, hello!13:09
ttx#topic Sahara13:09
SergeyLukjanov#link https://launchpad.net/sahara/+milestone/kilo-213:09
ttx2 BPs left13:10
SergeyLukjanovwe have two blueprints on the go13:10
*** eglynn is now known as eglynn-sick13:10
SergeyLukjanovedp-spark-swift-integration waits for https://review.openstack.org/#/c/146659/ (-1’d for nit thing, will be updated and re-approved today)13:10
SergeyLukjanovand indirect-vm-access with https://review.openstack.org/#/c/133590/ in the gate13:10
ttxsounds good13:10
SergeyLukjanovso, should be delivered before tomorrow13:11
ttxheh, you pmake my job easy I see13:11
SergeyLukjanovhope so :)13:11
ttxnote that we'll discuss reviews of Horizon panels at the cross-project meeting later13:11
ttxyou might want to stay around13:11
ttxotherwise I'll bring the topic up anyway13:11
SergeyLukjanovyup, I remember13:12
ttxNo other questions13:12
SergeyLukjanovI don't have a story for it, just want to discuss what's the best approach for doing it13:12
ttxit's a good discussion to have13:12
ttxit won't get any better i the future13:12
SergeyLukjanovI'm always on cross-project meetings, not aleays active due to the very late time :(13:12
ttxyep13:13
SergeyLukjanovnothing more from my side too13:13
ttxSergeyLukjanov: have a good day then!13:13
SergeyLukjanovttx, thanks13:13
SergeyLukjanovttx, you too13:13
ttxdhellmann: ready when you are13:13
dhellmannttx: hi!13:13
ttx#topic Oslo13:13
ttx#link https://launchpad.net/oslo/+milestone/kilo-213:14
ttxLooks all set for oslo-incubator tagging13:14
dhellmannyep, I think we're clear13:14
ttxdhellmann: anything we should wait on before we tag the incubator with the kilo-2 tag ?13:14
ttxusually we do it late, we can as well do it early13:14
ttxI think13:14
* dhellmann checks the queue quickly13:14
dhellmannnothing in the queue looks like it's critical, so we could go ahead13:15
ttxok, will do just after our discussion13:16
ttxQuick glance at https://launchpad.net/oslo/+milestone/next-kilo13:16
ttxany other library release this week?13:16
dhellmannno, we decided to hold off until next week because of the deadline13:16
dhellmannwe'll have several on monday morning13:16
ttxyes, it's not a week where breakage is appreciated13:16
dhellmannutils, test, and db at least next week13:16
dhellmannyeah, I thought josh was going to wait to do the taskflow release, too -- bad communication there on my part13:17
ttx"I don't always break OpenSTack by releasing an Oslo library, but when I do, I do it after the milestone week"13:17
dhellmannno that's a t-shirt slogan13:17
dhellmann*now13:17
ttxOK, anything more before I start running script13:18
ttx?13:18
dhellmannnothing to report, and nothing for the meeting agenda13:18
ttxalright then, tag on its way.13:18
* dhellmann ducks13:19
ttxheh, you aren't the one running the experimental neutron-aaS-friends-supporting branch of release-tools now13:20
ttxok done13:21
ttxdhellmann: It's so awesome to see so little work being done in the incubator those days :)13:21
*** eglynn-sick has quit IRC13:24
*** eglynn-sick has joined #openstack-relmgr-office13:24
dhellmannttx: yeah, that'll change again next cycle when we shift back into "acquisition" mode, but I want us to set a goal of 1-2 cycles for incubation before graduation13:35
*** eglynn-sick has quit IRC14:02
*** eglynn has joined #openstack-relmgr-office14:02
*** eglynn has quit IRC14:53
*** eglynn has joined #openstack-relmgr-office14:54
mesteryttx: I'm ready whenever you're ready.14:54
ttxmestery: ok, let's do this14:57
ttx#topic Neutron14:57
ttx#link https://launchpad.net/neutron/+milestone/kilo-214:58
ttx7 Bps still up14:58
ttxand 18 bugs14:58
mesteryttx: Ack, all those BPs have a shot still.14:58
mesteryThey have patches in flight.14:58
ttxShould I treat any of those bugs as a milestone blocker ?14:58
mesteryBut I've told people that if they aren't in the merge queue by Wednesday morning they're out.14:58
ttxor just defer whatever doesn't make it ?14:58
mesteryI don't think any are blockers at this point.14:59
*** eglynn has quit IRC14:59
ttxok, so let's see if I can map those BPs to reviews14:59
*** eglynn has joined #openstack-relmgr-office14:59
ttxrefactor-iptables-firewall-driver > https://review.openstack.org/#/c/152512/ says it partially implements -- so are more patches coming ?14:59
* mestery looks15:00
mesteryThat's the last patch for that BP.15:00
mesteryI'm confirming with ajo now, but that's what he told me Friday.15:01
ttxlbaas-api-and-objmodel-improvement > https://review.openstack.org/#/c/152171/ https://review.openstack.org/#/c/144834/ https://review.openstack.org/#/c/144832/15:01
mesteryJust got confirmation on https://review.openstack.org/#/c/152512/, it closed out refactor-iptables-firewall-driver15:01
mestery*closes15:01
mesteryttx: The LBaaS folks are having a sprint this week, I expect a lot of merges from them today/tomorrow.15:01
mesterydougwig has indicated that LBaaS V2 BP will be done before Kilo-2, barring merge issues15:01
ttxrootwrap-daemon-mode > https://review.openstack.org/#/c/84667/ https://review.openstack.org/#/c/82787/ https://review.openstack.org/#/c/145829/15:02
ttxlooks a bit far away15:02
mesteryttx: If otherwiseguy doesn't propose a new patch by this morning, I'll move it out.15:02
ttxextra-dhcp-opts-ipv4-ipv6 > https://review.openstack.org/#/c/136713/15:03
ttxallow-mac-to-be-updated > https://review.openstack.org/#/c/112129/15:03
mesteryThis one should merge today15:03
ttxyes those two are looking good15:04
mestery++15:04
ttxofagent-flow-based-tunneling > https://review.openstack.org/#/c/130677/ https://review.openstack.org/#/c/130676/15:04
mesteryThat one is a little further away than the prior too, but still close15:04
ttxrpc-docs-and-namespaces > https://review.openstack.org/#/c/149735/15:05
ttxOK, if that is correct I can track completion and help updating BP status15:05
mesteryI have an ask out to russellb on the status there, I suspect it may not be complete, but there's a lot of patches so it's hard to know :)15:05
mesteryThanks ttx!15:05
ttxsanity-checking the repos to see if tarballs are complete15:06
*** thingee has joined #openstack-relmgr-office15:06
mesterycool15:06
ttxtakes a bit of time15:06
ttxwhile I wait, other questions ?15:07
mesteryI'm going to spend some time post our 1:1 going through the remaining bugs that are open yet15:07
mesteryI'll have those cleaned up this morning with only ones realistically having a chance at Kilo-2 targeted15:07
ttxI'll ping you if it seems headed to the wall or if it looks ready15:07
mesteryOne more thing15:07
mestery#link https://docs.google.com/spreadsheets/d/1OQN0VlKzKC1gYlxgalQXKDTGGWogWFRtD3S5OpepsX4/edit?pli=1#gid=015:07
mesteryThat's the tracking page for our plugin decomposition status15:07
mesteryIt's looking quite good actually!15:07
ttxYou can ping me if it looks ready from where you're standing15:08
mesteryWe'll keep that updated as we go.15:08
mesteryttx: Ack15:08
ttxmestery: so those repos contains each vendor plugin15:08
ttx?15:08
mesteryCorrect15:09
mesteryThe backend logic for the plugin, a thin shim is still in the neutron tree.15:09
ttxok15:09
mesteryThe process has gone quite smooth actually, kudos to armax for leading this15:09
ttxok, so we'll be in touch for the tag(s)15:09
mesteryThanks ttx!15:10
ttxI evolved the release scripts, they should support uploading neutron-*aas to same LP page now15:10
ttxfingers crossed15:10
mestery++, awesome!15:10
mestery;)15:10
ttxmestery: alright, have a nice day!15:10
mesteryttx: Thank you! You have a great evening!15:10
ttxnikhil_k: ready when you are15:11
*** eglynn has quit IRC15:12
*** eglynn has joined #openstack-relmgr-office15:13
nikhil_kttx: o/15:20
ttx#topic Glance15:21
ttx#link https://launchpad.net/glance/+milestone/kilo-215:21
ttxnikhil_k: o/15:21
ttxI see 4 Bps still in progress15:21
ttxAll likely to make it in the coming days ?15:21
nikhil_kttx: so, there was some confusion on some of them15:21
nikhil_ka couple of them are ready15:21
nikhil_khttps://blueprints.launchpad.net/glance/+spec/replace-snet-config-with-endpoint-config and15:22
nikhil_khttps://blueprints.launchpad.net/glance/+spec/software-metadefs15:22
* ttx looks at those15:22
nikhil_kthis is being tested and needs a small change15:22
nikhil_khttps://blueprints.launchpad.net/glance/+spec/taskflow-integration15:22
nikhil_kthis looks unlikely https://blueprints.launchpad.net/glance/+spec/swift-retry-wait15:22
ttxreplace-snet-config-with-endpoint-config pending on https://review.openstack.org/#/c/150144/ IIUC15:22
ttxsoftware-metadefs pending on https://review.openstack.org/#/c/148007/15:23
ttxtaskflow-integration...15:23
nikhil_kttx: yeah, I heard back just gunna review it15:23
nikhil_kabout replace-snet-config15:23
ttxis it just https://review.openstack.org/#/c/85211/ ?15:23
nikhil_kyes15:23
ttxok15:24
ttxswift-retry-wait...15:24
nikhil_kttx: the main blocker is https://bugs.launchpad.net/bugs/141280215:24
* nikhil_k waits15:24
ttxyeah, it looks way farther away, better concentrate on the other 315:24
ttxhow about we move this one to k3 already, to signal reviewers should focus on the other 3 ?15:24
nikhil_kttx: that sounds fine15:25
ttxok, doing it now15:25
ttxAbout the bugs, anything we should block the milestone on ?15:25
ttxOr I should just defer whichever are not merged when the BPs are done ?15:26
nikhil_kthe main blocker is https://bugs.launchpad.net/bugs/141280215:26
ttxright15:26
ttxwe should keep this one as blocker15:26
nikhil_kand may be we should let this one slide https://bugs.launchpad.net/glance/+bug/122127415:26
ttxfeels featury rather than buggy too15:27
ttxHow about I mogve out of the milestone all but the critical one ?15:27
ttxIf those get merged they will be reincluded anyway15:27
nikhil_kyeah, feature related is https://review.openstack.org/#/c/145544/615:27
nikhil_kttx: sure, if you have to. I was going to suggest to wait until tomorrow however, either way is fine15:28
nikhil_kI think focusing on k3 and wrapping stuff up should like a better scenario15:28
nikhil_ks/should/sounds/15:28
ttxI prefer to use the k2 list as the blocker list at this point15:29
nikhil_kok, sure15:29
ttxOK, it's clean now15:29
nikhil_k:)15:29
nikhil_kAppreciate it.15:30
ttxI'll track those in the coming days and ping when if we won't hit the window or if all seem ready15:30
ttxping me the other way around if you feel it's good to go too15:30
nikhil_kSure thing15:30
ttxQuestions ?15:30
nikhil_kNothing for now :)15:30
ttxalright, you know where to find me15:30
ttxHave a good day15:30
nikhil_kHave a good one, yourself!15:30
ttxthingee: ready when you are15:31
thingeettx: hi!15:31
ttx#topic Cinder15:31
ttx#link https://launchpad.net/cinder/+milestone/kilo-215:31
ttxI see 5 open BPs in my crystal ball15:31
ttxAll still likely to make it ?15:32
thingeeI moved out a lot of stuff that have little to no consensus. If anything is going to make it, it's these.15:32
ttxOK, let's map them to the corresponding reviews then15:32
ttxover-subscription-in-thin-provisioning seems to be waiting on https://review.openstack.org/#/c/142171/15:33
ttxremotefs-share-cfg-improvements on https://review.openstack.org/#/c/149765/15:33
ttxdatabase-purge on https://review.openstack.org/#/c/146766/15:34
thingeehttps://etherpad.openstack.org/p/cinder-k2-priorities15:34
ttxchiscsi-iscsi-helper > https://review.openstack.org/#/c/147758/15:34
ttxadding them for the log15:34
ttxnfs-manage-unmanage > https://review.openstack.org/#/c/138125/15:35
ttxAll sounds doable15:35
ttxTheer are also 3 bugs. Are those blockers of just targets of opprtunity that I can defer to k3 if they miss ?15:35
thingeeyes15:36
ttx(the latter)15:36
thingeeyea latter15:36
thingeesorry15:36
ttxAlright, I'm all clear15:37
thingeelast thing15:37
thingeehttp://lists.openstack.org/pipermail/openstack-dev/2015-January/055719.html15:37
ttxI'll track those15:37
thingeesorry for switching this on you15:37
ttx#info Cidner Blueprint/Spec approval deadline - February 15th15:37
thingeenot sure if it's doable for something cross project next time on deadlines? Or a table somewhere? I can't imagine this is easy for contributors to keep track of15:37
ttx#info Cinder Code freeze for all features - March 10th15:38
ttxI posted most of them on https://wiki.openstack.org/wiki/Kilo_Release_Schedule15:38
thingeeyou're way ahead of me, thanks :)15:38
ttxbut I need to adjust dates it seems15:38
thingeethat's all for me15:39
ttxthingee: code freeze for all features -- what does that mean15:39
ttxfeatures must be proposed ?15:39
ttx(as in, in code review ?15:40
ttxor merged ?)15:40
thingeeno accepting anymore code unless they're bug fixes15:40
thingeenot*15:40
ttxso you're basically moving Feature Freeze up 9 days15:40
ttx(normally on March 19th)15:40
thingeecorrect15:41
ttxOK, I'll add that to page15:41
ttxnow15:41
ttxthingee: done15:43
thingeettx: thank you15:43
ttx#link https://wiki.openstack.org/wiki/Kilo_Release_Schedule15:43
ttxWe'll probably evolve the format of that15:43
ttxdoesn't scale that beautifully15:43
ttxdavid-lyle: you around ?15:44
david-lylettx: here15:44
ttxthingee: thx!15:44
ttx#topic Horizon15:44
ttxSorry for the lateness15:44
david-lyleno worries15:44
ttx#link https://launchpad.net/horizon/+milestone/kilo-215:44
ttx5 Bps up15:44
ttxAll still in the race to make the window ?15:44
david-lyletop one will miss, just about to move15:45
ttxwas wondering if https://review.openstack.org/#/c/148031/ didn't complete it15:45
ttxI guess not :)15:45
david-lyleno, that's just a part of it15:46
ttxheat-topology-display-improvement pending on https://review.openstack.org/#/c/110888/15:46
david-lylegoing to ping reviewers on that one15:46
ttxmigrate-all-instances-from-hosts-in-maintenance-mode on https://review.openstack.org/#/c/109586/15:46
david-lylesmaller change, been sitting a while15:46
ttxadd-manage-unmanage-volume > https://review.openstack.org/#/c/129652/15:47
ttxsettings-migration-script > https://review.openstack.org/#/c/81255/15:47
ttxview-volume-encryption-metadata > https://review.openstack.org/#/c/134341/15:47
ttxAll seem in good shape15:47
david-lylemost of those look in really good shape, just need to get cores looking at them15:47
ttxyes15:48
david-lyle2 of those I have on my list for after this15:48
ttxLots of bugs in the buglist, anything critical or can I just move the ones which don't make it to k3 ?15:48
david-lyleall that don't land can move15:48
david-lyleI already moved anything that wasn't in progress15:48
ttxOK, sound all good15:48
ttxNote that we'll discuss project-specific panels reviews at the cross-project meeting today15:49
ttxif you can attend15:49
david-lylesure15:49
ttxin particular it's interesting to see how that would scale in a bigger tent15:49
david-lyleshort answer, I don't think it does15:50
david-lylenot with the current model at least15:50
ttxagree, which is why we need to discuss/brainstorm how to solve that15:50
ttxanyway, talk about that later15:50
david-lylesure15:50
ttxquestions on your side ?15:50
david-lylemy only concern is I haven't seen anything new for ironic15:51
david-lylefor horizon15:51
ttxhmm, we could talk about it as part of that meeting topic15:51
david-lyletuskar-ui has some ironic support that we can pull in, but that's not the full story15:51
david-lyleI can ping devananda directly as well15:51
david-lylewas just looking through the bps today and didn't see anything15:52
devanandao/15:52
ttxdevananda: oh right, you're in my timezone15:52
devanandattx: yah15:52
david-lyledevananda: know of any efforts for ironic support in horizon for kilo?15:52
ttxdevananda: can you still make the regular 1:1 time ?15:52
devanandanope15:52
david-lylewe have tuskar-ui support, but that's only a fraction of the real use cases I believe15:53
david-lyleif you don't know of any efforts, I'll try to motivate someone15:53
ttxdavid-lyle: ok, if no other issues to report, ttyl15:53
devanandaI've had a few conversations with folks about doing it, but have not seen anything tangible yet15:53
david-lylethanks ttx15:54
david-lyledevananda: let me know if any materialize, otherwise, I'll try to take a look15:54
david-lylewould like to have support in kilo15:55
SlickNikttx: hi — got a minute?16:12
ttxon a call16:12
SlickNikokay, can wait.16:14
ttxSlickNik: done16:17
ttxwant to sync now ?16:18
SlickNikttx: yes, please — since we will be busy with the mid cycle in a few.16:19
ttxalright16:19
ttx#topic Trove16:19
ttx#link https://launchpad.net/trove/+milestone/kilo-216:19
ttxThat looks pretty complete from where I stand16:19
SlickNikYes, have it pretty complete for kilo-2.16:19
ttxWant to wait a bit more to see if anything else makes it ?16:19
ttxOr shall I tag now ?16:19
SlickNikFeel free to tag now — most folks are at the mid-cycle and there's no outstanding blockers.16:20
SlickNikHash: 4d31433b1e67acbba1932ba1b032fe55f2dfd00d16:20
ttxOK, will do in a few16:20
ttxand ping you when done16:20
ttxI don't have more questions then ;)16:21
SlickNikThanks, tag at your convenience!16:21
SlickNikI'll get back to prepp'ing for the mid-cycle then.16:21
SlickNikCatch you later.16:21
ttxSlickNik: all set at https://launchpad.net/trove/kilo/kilo-216:29
ttxdevananda: want to run your sync now ?16:29
devanandattx: nope. having a delightful argument with jaypipes about whether or not Nova should have any support for Ironic16:35
ttxah :)16:36
devanandattx: tldr; the midcyucle is going on, we're updating LP as we land things, and I'll send you a SHA at some point16:36
devanandattx: and if not, you're free to tag on thursday :)16:36
ttxok, let's skip the regular time too then16:37
ttxnotmyname: around ? Nothing special to cover, so we can skip16:53
notmynamettx: I'm here16:53
ttx#topic Swift16:53
ttx#info 2.2.2 released16:53
notmyname2.2.2 was released yesterday16:53
notmynamethanks16:53
ttx#link https://launchpad.net/swift/kilo/2.2.216:53
notmyname#info next week is the swift midcycle/hackathon16:54
ttxnotmyname: where is that ?16:54
notmynameat the swiftstack office in san francisco16:54
ttxYou might want to add it to https://wiki.openstack.org/wiki/Sprints16:54
notmynameshould be about 30 people (from at least 5 countries)16:54
ttx(or do it next time)16:54
* notmyname didn't know that page existed16:54
ttxwhich is why I advocate its use :)16:55
ttxnot very successful at that16:55
ttxbut some people have been complaining that midcycle things suck because nobody knows they happen16:55
ttxand that was the answer we gavce the board16:55
ttxI'd argue the people who need to know know16:56
ttxbut then that feels a bit elitist16:56
ttxnotmyname: any other thing you wanted to cover ?16:57
notmynamenope. I'm good16:58
ttxnotmyname: have a good week16:58
ttxmorganfainberg: ready when you are16:58
morganfainbergO/17:02
ttx#topic Keystone17:02
morganfainbergSorry was being chased17:02
ttx#link https://launchpad.net/keystone/+milestone/kilo-217:02
morganfainbergBy people in irc ;)17:02
ttxI'm chased too, so don't worry if I go mute :)17:03
morganfainbergWill be pairing that down today to anything that is not in flight17:03
morganfainbergOr merged17:03
ttxOK, today :)17:03
morganfainbergBugs might increase if a fix has been committed.17:03
ttxjust keep blockers in17:03
morganfainbergThe federation one might get one more patch.17:03
ttxI mean, keep only blockers in17:03
morganfainbergBugs won't be reduced at this point I think. All should have code in flight.17:04
morganfainbergFederation Bp that is. We are looking at the ietf don't use x prefixed headers17:04
ttxOK, I might ping you when you are done if I spot a dark/incoherent area17:05
morganfainbergMeaning a rename of 2 headers or elimination of it.17:05
ttxping me when you're done cleaning up17:05
morganfainbergSounds good. Will ping.17:05
morganfainberg2 new headers that is*17:05
morganfainbergBut I spent a chunk of time last night getting things pushed through.17:05
ttxok17:06
morganfainbergKeystone client will be released on Monday same as middleware to prevent accidentally breaking gate this week for you.17:06
morganfainberg;)17:06
ttxawesome!17:06
morganfainbergNot that I expect to break gate. But...17:06
ttxWill track the things you keep in the page and ping you if I think we won't make it, or if we made it :)17:06
ttxmorganfainberg: anything else ?17:07
morganfainbergYep. I hope to have a sha for you today.17:07
morganfainbergNope that's it.17:07
ttxalrighty, ttyl17:07
ttx#endmeeting17:07
morganfainbergAt x-project will raise no downgrade spec17:07
openstackMeeting ended Tue Feb  3 17:07:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-02-03-09.06.html17:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-02-03-09.06.txt17:07
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-02-03-09.06.log.html17:07
morganfainbergBut that is more open topic stuff.17:08
ttxack17:08
morganfainbergNot keystone specific.17:08
*** johnthetubaguy is now known as zz_johnthetubagu19:11
*** mestery_ has joined #openstack-relmgr-office19:14
*** mestery has quit IRC19:15
morganfainbergttx: should have the SHA for you [i hope] by 23:59 tonight (pacific time)19:54
morganfainbergso uh...19:54
morganfainberg0659 UTC19:55
ttxOK, can tag around one hour later when I start work19:56
morganfainbergdown tot he last couple things gating but doing a once-over on new bugs to make sure nothing major has been identified today19:59
*** mestery_ is now known as mestery20:09
*** anteaya has quit IRC20:34
*** anteaya has joined #openstack-relmgr-office20:53
*** eglynn has quit IRC22:05
*** eglynn has joined #openstack-relmgr-office22:20
*** jraim has quit IRC23:10
*** jraim has joined #openstack-relmgr-office23:21

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