Tuesday, 2014-12-09

*** mestery has quit IRC01:18
*** mestery has joined #openstack-relmgr-office01:20
*** mestery has quit IRC01:23
*** mestery has joined #openstack-relmgr-office02:57
*** david-lyle is now known as david-lyle_afk03:24
*** mestery has quit IRC04:00
*** mestery has joined #openstack-relmgr-office04:22
*** mestery has quit IRC05:57
*** russellb has quit IRC06:43
*** russellb has joined #openstack-relmgr-office06:44
*** SlickNik has joined #openstack-relmgr-office08:46
SlickNikttx: around?08:47
ttxSlickNik: yes08:48
SlickNikIt looks like I'm double booked again for our 1:1 slot today. :(08:48
ttxSlickNik: want to do it now ?08:48
SlickNikCan we? That sounds good.08:49
ttx#startmeeting ptl_sync08:49
openstackMeeting started Tue Dec  9 08:49: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:49
ttxWe can08:49
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:49
openstackThe meeting name has been set to 'ptl_sync'08:49
ttx#topic Trove08:49
ttxSo.. next week we have kilo-108:49
SlickNikSo I spent some time getting https://bugs.launchpad.net/trove/+milestone/kilo-1 in shape.08:49
ttxThe goal being to tag sometimes between the 16th and the 18th08:49
ttxso on thos days, as soon as you're happy with the sahpe of master we can push the tag08:50
SlickNikYes. Working towards getting all the BPs that are on track reviewed and through.08:50
ttxjust send me a SHA and I'll make it happen08:50
ttx7 in-progress blueprints to get in08:51
ttxand 12 bugfixes still targeted08:51
ttxnext week we'll refine that list to cover true milestone blockers08:51
ttxbut the current list sounds reasonable to me08:51
SlickNikMost of them are pretty close.08:52
SlickNikWill sync with you on them again next week to check what we need to move out (if any).08:52
ttxNo questions from me, you look in good shape08:52
SlickNikSounds good. That's pretty much all I had.08:53
SlickNikThanks for being flexible with the timing.08:53
ttxno pb!08:54
ttxtalk to you next week08:54
SlickNikThank you — see you later at the x-project meeting.08:54
ttxasalkeld: o/09:00
asalkeldhi ttx09:00
ttx#topic Heat09:00
asalkeld#link https://launchpad.net/heat/+milestone/kilo-109:00
ttxasalkeld: same comment, kilo-1 is next week, so the idea is to tag sometimes between the 16th and the 18th09:00
asalkeldi might need to move one or two bp to k209:01
ttxOn those days, as soon as you're happy with the shape of master you send me a SHA and we can push the tag09:01
asalkeldok ttx sounds09:01
ttx(and defer the missed Bps to k2)09:01
asalkeldsounds easy ;)09:01
ttxit is easy09:01
ttxespecially since the milestone itself is not that important09:02
asalkeldok, yeah just intermediate09:02
ttxthe goal is just to avoid picking the wrong SHA, like if you wait for the last patch in a series implementing a feature, better wait a few more minutes :)09:02
asalkeldsure, makes sense09:03
ttxhttps://blueprints.launchpad.net/heat/+spec/cinder-custom-constraints has no priority ?09:03
asalkeldttx, checking09:03
ttx(is implemented already)09:04
ttxand yes, depending how complex they are, decouple-nested lazy-load-outputs and multi-region-support might need to get pushed09:04
asalkeldyeah, it was a very small bp09:04
asalkelddecouple-nested - is looking big09:04
asalkeldneeds heaps of test code rework09:04
ttxkeep them in as long as you sincerely think they are likely to get in09:04
ttxbut defer them if you think they won't09:05
asalkeldsure, makes sense09:05
ttxNext week we'll refine again to only list milestone blockers09:05
ttxso that we know what we are waiting on09:05
ttxDo you need to merge anything more on the topic of env-nested-usability ?09:06
asalkeldi just marked it done09:07
ttxalright then09:07
ttxquestions on your side ?09:07
asalkeldno, all good09:07
ttxalright, have a good week!09:07
asalkeldyou too09:08
ttxmikal: are you standing in for john, or should we just skip this week ?09:08
mikalI am hot spare John09:09
mikalNot that we've managed to overlap beforehand to brief09:09
mikalBut I am here for your release questioning needs09:09
ttxlet's try :)09:09
mikalAlso, I have questions about your bot09:09
ttx#topic Nova09:09
ttxok let's start with the bot question09:09
mikalOk, so I approved four BPs Friday last week as part of our meeting09:10
mikalI assigned a milestone etc09:10
ttxdid you set a priority ?09:10
mikalAnd then your bot removed the milestone and slapped my wrist09:10
mikalObviously I've missed a step09:10
mikalAhhh, probably not?09:10
mikalhttps://blueprints.launchpad.net/nova/+spec/hyperv-serial-ports is an example09:10
ttxSo the problem is... anybody can set a milestone.09:10
ttxbut only drivers can set a priority09:10
ttxso we use the milestone+priority comboi to mean "approve"09:11
mikalFair enough09:11
ttxand slap the wrists of anyone who dares to set milestone without priority09:11
mikalI will retry with priorities set then09:11
ttxit's an ugly workaround for Launchpad weird permission model around milestone targets09:11
ttxI understand it can be surprising, that's why it's opt in and I explain it to people before they accept or reject it09:12
mikalOk, all fixed09:12
mikalSo all is well09:12
ttxsorry about the "slap"09:12
mikalYeah, I think its because John has always done this for me09:12
mikalI was just trying to help out while he was distracted09:13
mikalIts all good, fixed now09:13
mikalNext topic!09:13
ttxWe'll tag kilo-1 between the 16th and 18th next week09:13
ttxso the list if probably a bit optimistic at this point09:13
mikalA lot of that is going to get bumped I think09:13
mikalWhich is pretty normal09:13
ttxit's good to refine it so that it represents your best guess as to what should make it09:14
mikalWe've also said that we will impose a spec approval deadline of kilo-1 as well09:14
ttxbut I expect John will do it09:14
mikalSo I need to remind people of that09:14
ttxThere are a few "unknown" status there that are probably not in good shape for next week09:14
mikalI think if its not in "needs code review" or "implemented" its probably safe to bump09:14
mikalBut I will leave that to John09:14
ttxyeah, usually at this point, not proposed = not in09:15
ttxso I would remove at least 1009:15
mikalThere's only 5 things in k-2 as well09:15
mikalSo being a bit more realistic there would be good09:15
ttxand in the unlikely case they make it, we can put them back in k109:16
mikalSo, are things moved manually?09:16
mikalOr is there a script for that?09:16
* mikal wonders if I should do some of it for John09:16
ttxI don't have a script for that. I could make one. But to be fair, only Nova has the volume of specs that makes such a "defer" script needed :)09:16
mikalHeh, fair enough09:17
* mikal will move all the ones in "unknown" or "not started" as a first pass09:17
ttxwell, horizon has an habit of targeting hundreds of bugs09:17
ttxI may already have that script somewhere let me check09:17
ttxhmm, no09:18
mikalIts ok, I can just grind through09:18
mikalIts only about ten09:18
ttxlast thing is https://bugs.launchpad.net/nova/+bug/126626209:18
ttxtargeted to k1 but no assignee09:18
ttxprobably unlikely to make it09:18
* mikal looks09:19
ttxbut may be worth finding someone09:19
mikalSean Dague might have an opinion there09:19
mikalI can ping him09:19
ttxIf you plan to try finding someone, you can keep it in09:19
ttxwe can clean up next week with "last minute blockers"09:20
mikalLet's keep it for now09:20
mikalWorks for me09:20
ttxvmware-vsan-support might be completed with https://review.openstack.org/#/c/74300/09:20
* mikal looks09:21
ttxquiesced-image-snapshots-with-qemu-guest-agent might have been completed with https://review.openstack.org/#/c/72038/09:21
mikalHow are you deciding which ones to call out like this?09:21
ttxand hyper-v-smbfs-volume-support might have been completed with https://review.openstack.org/#/c/129235/09:21
ttxI'm using this ^09:21
ttxshows merged reviews attached to blueprints.09:22
ttxWhen one in-progress BP only shows merged stuff, I check the review to see if it looks like it's multipart of single-review09:22
mikalOk, well I shall ask people about those as well then09:23
ttxIn those cases those are recent merged, so might just be completed09:23
mikalWhat else do we need to cover tonight?09:24
ttxAlright, I think we are good..; questions on your side ?09:24
mikalNup, I think I am good09:24
ttxthx for stepping in!09:24
mikalNo problem!09:24
mikalCool, see you at the TC thing then!09:24
*** SergeyLukjanov has quit IRC10:48
*** SergeyLukjanov has joined #openstack-relmgr-office10:50
*** asalkeld has quit IRC11:28
SergeyLukjanovttx, hello, /me ready when you are12:56
*** eglynn has joined #openstack-relmgr-office12:57
ttxSergeyLukjanov: will do eglynn first12:57
ttxfwiw schedule is now at https://wiki.openstack.org/wiki/Release_Cycle_Management/1:1_Syncs12:57
SergeyLukjanovttx, yeah, just defining that I'm online :)12:57
ttxeglynn: eady when you are12:58
ttx#topic Ceilometer12:58
eglynn#link https://launchpad.net/ceilometer/+milestone/kilo-112:58
eglynnI bumped the instance-restart BP to k2 due to lack of traction on the code reviews12:59
ttxeglynn: we'll tag and publish kilo-1 next week, seomteimes between the 16th and 18th -- just give me a SHA when you're happy with the state of master12:59
ttxeglynn: those last 5 are still on track for k1 ?12:59
eglynnonly slight concern is declarative-http-tests since we've seen no code yet12:59
ttxok, defer it early if you learn more12:59
eglynnI'll have a 1:1 with cdent later on today and make a call on whether it's still realistic13:00
eglynnotherwise the rest are all on target13:00
ttxnext week we'll refien the list to only contain milestone blockers13:00
ttxOK, looks all good and reasonable13:00
ttxquestions on your side ?13:01
eglynnnope all good ... I'll start populating the kilo-2 roster by EoW13:01
ttxhave a great day then13:01
ttxSergeyLukjanov: ready?13:01
eglynnyou too ... thanks for your time! :)13:01
ttxThis is becoming too easy13:02
*** Kiall has quit IRC13:11
*** Kiall has joined #openstack-relmgr-office13:11
dhellmannttx: ready when you are13:11
ttxdhellmann: ok, let's do it now13:12
ttx#topic Oslo13:12
ttxdhellmann: so next week we'll tag the incubator at some point and park kilo-1 over13:12
ttxJust let me know of a time/SHA that seems appropriate, sometimes between the 16th and the 18th13:13
ttxAre those two still in progress ? I think tooz is mostly done now, was renmaed13:14
*** eglynn is now known as eglynn-lunch13:14
dhellmannyeah, we need to update the review team settings in gerrit but that's it13:14
dhellmannI'll get jd to do that today13:14
dhellmannoh, and probably the launchpad settings, too13:14
ttxwhat about the other one, graduate oslo.context ?13:14
dhellmanndims is making good progress on that13:15
dhellmannthe code is ready, there are just a few release management things to do13:15
dhellmannI think we can finish both by next week13:15
ttxIn other news, I reworked spec2bp to address your remarks, hopefully13:16
ttxit's now oslo-projectgroup-aware13:16
dhellmannok, I'll take a look at the latest version13:16
ttxand lets you specify the path to the spec when it's nonstandard and not stored in the UTL bp field13:16
ttxthat's all I had I think -- questions on your side ?13:17
dhellmannI added some stuff to the oslo-specs repo last week to refuse specs that don't have matching blueprints in launchpad13:18
dhellmannso those names should always match now :-)13:18
ttxoh, interesting. We could mention it at the specs cross-project meeting today13:18
dhellmannI could put it in oslosphinx, to make it easier to share13:19
dhellmannturn it on/off with some options13:19
ttxOK, anything else ?13:19
dhellmannnothing from me13:19
ttxdhellmann: ok then, talk to you later!13:19
SergeyLukjanovttx, sorry, internet issue13:19
dhellmannttx: thanks!13:20
ttxSergeyLukjanov: is it better now ?13:20
SergeyLukjanovttx, I hope so13:20
ttx#topic Sahara13:20
ttxSergeyLukjanov: so, same drill, k1 next week, tag between Tue and Thu13:20
SergeyLukjanov#link https://launchpad.net/sahara/+milestone/kilo-113:20
* SergeyLukjanov going to cleanup plans before the 1-1 meeting next week13:21
ttxindirect-vm-access still likely to make it ?13:21
SergeyLukjanovsounds like we have a few features that should be moved to k213:21
SergeyLukjanovttx, I think so, the spec was just approved13:21
SergeyLukjanovttx, moving to "needs code review"13:22
ttxso we'll revisit the list next week to lmimit to last-minute milestone blockers13:22
SergeyLukjanovttx, yeah13:22
ttxOn the bugs side, would be good to refine the list at this point too13:23
ttxNot enough assignees to make it13:23
SergeyLukjanovttx, yup, agree, will cleanup the list13:24
ttxany reason why you use publish-to-pypi for sahara proper ?13:25
SergeyLukjanovttx, hm, I'm looking now13:25
SergeyLukjanovttx, actually I don't remember any objectives for it13:25
SergeyLukjanovttx, no py3X support, but it's like in all other projects :)13:25
ttxok, I'll propose a fix for it13:26
SergeyLukjanovttx, thanks13:26
ttxhmm, what else...13:26
SergeyLukjanovttx, oh, one moment13:26
SergeyLukjanovttx, what's the issue of using publish-to-pypi?13:27
ttxwe only publish to pypi the libraries13:27
ttxserver code is signed/published to LP and tarballs.o.o13:28
SergeyLukjanovttx, okay, so, probably we should remove it from pypi13:28
ttxso it's more a consistency thing13:28
ttxthso that people don't start complaining about https://pypi.python.org/pypi/nova being stale13:28
SergeyLukjanovttx, we've been publishing sahara to pypi starting from the first release13:28
ttxyes, was a convenient way to inherit the tarball jobs :)13:28
ttxSergeyLukjanov: ok, that's all I had -- questions ?13:29
SergeyLukjanovnope, thank you!13:29
*** mestery has joined #openstack-relmgr-office13:59
mesteryttx: Just FYI, I'm in Utah this week for Neutron, I am planning to be at our 1:1, but if you're around now, I'm available now as well.14:14
mesteryFor 10 minutes at least :)14:14
mesteryOtherwise, I'll catch you in 50 minutes14:15
ttxmestery: o/14:15
ttxWe can do it now14:15
ttx#topic Neutron14:16
ttxSo we'll tag k1 next week, sometimes between the &6th and the 18th14:16
ttxerr 16th14:16
ttxjust let me know when you're happy with the state of master14:16
mesteryYEs, we're at the sprint14:16
mesterybreaking services out this week14:16
mesteryI assume we'll tag those repositories too?14:17
mesteryIt will be new for all of us14:17
ttxso that's a good question14:17
ttxwe can tag them alright. The question is more, what release model will apply to them14:17
ttxis it more library like ?14:17
ttxi.e. semver versioning, publish to pypi14:17
mesteryYes, that's about right. They still depend on Neutron itself.14:18
ttxor more companion tarballs14:18
mesteryLet me think about this though14:18
mesteryI will figure it out today and let you know14:18
ttxwe need to check which jenkins jobs will apply to those, that's part of the split14:18
mesteryYes, it's on our list of things to do today.14:19
mesteryAnd we need the co-gating jobs setup too, which will happen today as well14:19
ttxFrom my perspective both options are on the table, we can certainly upload multiple tarballs in the "k1" milestone page on LP14:19
mesteryWe have the new repos up with code, and reviews out to get them passing basic tests14:19
mesteryOK, cool14:19
ttxand share versioning14:19
ttxI think it boils down to how tightly integrated thsoe will be with neutron14:19
ttxif they need synced releae, let's just share versioning and release all as components14:20
ttxif the link between them is more loose... you could use a semver contract14:20
mesteryMy gut feeling says lets do it that way for Kilo, post-Kilo we can think about separating them even more14:20
ttxjust keep me posted so that I can do a few checks in advance14:21
mesteryAck, will do sir14:21
ttxmestery: from a launchpad perspective, are those all tracked in same project, or different projects ?14:21
mesterySame project, we're sharing both LP and neutron-specs for these14:22
ttxok, then it makes sense to share release14:22
ttxit's just a production artifact that they are released in separate tarballs instead of one14:22
ttxat least for kilo.14:23
mesteryYes, makes sense14:23
ttxso yes, we'll tag them all, and should have -tarball jobs lined up to pick them up14:23
ttxI'll check that my release scripts can handle that14:23
ttx#action ttx to check that release scripts can handle the multi-tarball neutron split case14:24
ttx4 specs still in progress, all likely to make it by next week ?14:24
mesteryMy guess is we land 4 of those, maybe 5, but next week.14:25
mestery2 of the 4 in progress, maybe 314:25
mesteryTotal of 4-514:25
mesteryThe split spec will be approved and done in K1 too14:25
ttxOK, we'll refine the list next ween so that only last-minute milestone blockers are left14:25
mesteryIt's a formality we need to get done today14:25
ttxok, maybe add it to k1 as "Blocked" ?14:26
mesteryYes, the sprint has been super useful this week with regards to getting coding done in person, thanks also to infra and QA over IRC!14:26
mesteryWill do14:26
ttxOK, that's all the urgent stuff I had. Questions on your side ?14:26
mesteryNothing else, the split was the main thing on my mind now.14:27
mesteryThanks ttx!14:27
ttxalright, have a good sprint!14:27
*** mestery has quit IRC14:29
*** eglynn-lunch is now known as eglynn14:32
dhellmannttx: +1 on the new spec2bp, thanks for making it work with oslo14:45
ttxCool, will let it bake for others comment for a few daysthen will merge it14:46
ttxnikhil_k: around?15:20
nikhil_kttx: o/15:20
ttx#topic Glance15:20
ttxnikhil_k: kilo-1 strikes next week15:20
ttxthat means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA15:21
*** david-lyle has joined #openstack-relmgr-office15:21
nikhil_kok, sounds good15:21
ttxI see two "unknown" statuses there15:21
nikhil_kttx: they'r yet to be picked up15:22
ttxnikhil_k: still likely to make it before next week ?15:22
nikhil_kttx: had given them a chance to get in k1. may be we can push them to k2 early next week15:22
nikhil_kit's a small chance15:22
ttxyes, we'll refine the list next week15:22
ttxso that it only includes the last-minute milestone blockers15:23
nikhil_kcool, that works!15:23
nikhil_kttx: was that all for me?15:25
ttxsorry phone rang15:25
nikhil_kah k15:25
ttxbut sounds all good15:26
ttxquestions from you ?15:26
nikhil_khad one smal one15:26
ttxshall take a bit more time next week as we finally cull the list :)15:26
nikhil_kwhat to do with the stable/icehouse review requests?15:26
ttxnikhil_k: we'll set up the glance-stable-maint group tomorrow15:27
nikhil_kok nice15:27
ttxso you shall be able to approve those yourself, as long as you follow stable policy15:27
nikhil_kah cool15:28
ttxI'll keep you posted. We were waiting to get 2014.2.1 out of the way15:28
ttxI booked tomorrow afternoon with fungi to set that up15:28
nikhil_kttx: how is that group getting formed?15:28
ttxstarts with stable liaison15:28
ttxlet me check the proposed group15:28
ttxwould be you and Erno15:29
ttxto start15:29
nikhil_kttx: ok and we've liberty to add people15:29
nikhil_kthere are a few who we would like to be in there15:29
ttxyes, the stable-maint-core group just needs to make sure they know stable policy before adding them15:30
ttxso once we lectured them, we can add them15:30
nikhil_ksounds good!15:30
ttxreference: http://lists.openstack.org/pipermail/openstack-dev/2014-November/050390.html15:31
ttxnikhil_k: note that there is a glance-oriented topic at meeting today15:31
ttxosprofiler options naming15:31
nikhil_kttx: ah yes, I'd recommended that15:31
nikhil_kwill be there in the meeting15:32
ttxnikhil_k: thx!15:32
ttxthingee: around?15:32
nikhil_kthanks too!15:32
thingeettx: o/15:32
ttx#topic Cinder15:32
ttxSo yeah, same warning...15:32
ttxkilo-1 strikes next week15:32
ttxthat means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA15:32
ttxquestions on that process ?15:33
thingeettx: a few of these are waiting for one more +2. I wasn't able to approve other merges since they were in bad shape for other reasons.15:33
thingeettx: nope15:33
ttxcinder-drbd-volume-driver still likely to make it ?15:33
thingeeyes, just spoke with the assignee to have code for me today15:33
ttxWe'll refine the list next week so that only last-minute milestone tag blockers are left15:34
thingeettx: sure15:35
ttxon the bugs side, one of them is targeted but not assigned: https://bugs.launchpad.net/cinder/+bug/138346015:35
ttxStill liekly to make it ?15:35
ttxI guess that's simple enough :)15:35
thingeettx: That can be closed likely. sample config is gone.15:35
thingeettx: I check it out15:35
ttxok, mark it invalid if that makes sense15:36
ttxOK, looks all good. How is the "all drivers on k1" initiative working out so far ?15:36
thingeegreat, I really do have code reviews for all and cert tests passing... drbd being my only special case :)15:37
ttxSounds all good to me. Questions on your side ?15:38
thingeenothing. looking forward to core issues being taken care of in the next couple of milestones :)15:38
ttxthingee: heh yes.15:38
ttxthingee: ok then, have a good day!15:38
ttxdavid-lyle: ready when you are15:38
thingeettx: have a good evening!15:39
david-lylettx: ready15:39
ttx#topic Horizon15:39
ttxsame warning about k1 striking next week15:39
david-lyleWe're in good shape for K-115:39
ttxI see one "not started", still likely to make it ?15:40
ttxI guess https://review.openstack.org/#/c/103627/ makes it "started" at least15:40
david-lyleIt's ready for review actually15:40
ttxok, updating15:41
david-lyleoops, stomped on your change I think15:41
ttxthose last 8 still stand a good chance of getting in before next week ?15:41
ttxyou win!15:41
david-lyleput it as good progress, there's still a little discussion around the how15:42
david-lyleI think we're in good shape15:42
ttxOK, we'll readjust the list next week anyway so that it only contains the last-minute tag blockers15:42
ttxOn the bugs side, a couple unassigned targeted issues15:42
david-lyleI won't block k-1 on any of them15:42
ttxwill you have people working on those, or is it better to just defer those to k2 now ?15:43
david-lylelet's move to k-215:44
david-lyleI need to find owners15:44
ttxok, I'll let you do that15:44
ttxalright, questions on your side ?15:44
david-lyleno, I'm set15:45
ttxcool, have a good day then, talk to you later!15:45
david-lyleSounds good, thanks!15:45
*** mestery has joined #openstack-relmgr-office15:55
*** david-lyle has quit IRC16:20
ttxnotmyname: ready when you are16:49
notmynamettx: good morning16:49
ttx#topic Swift16:49
notmynamewe're on track for the dates we discussed last week16:50
notmynametracking some things at16:50
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews16:50
notmynamethat's really all I've got16:50
ttx2.2.1 RC between dec 11 and 15 and final by the end of the week ?16:50
ttxnice long url16:51
notmynamethank gerrit for that ;-)16:51
ttxcan I set up a 2.2.1 milestone in LP ?16:52
notmynameand I'll put stuff into it as we get closer16:52
ttxok doing it now16:52
ttxYou can start pushing stuff to it: https://launchpad.net/swift/+milestone/2.2.116:53
ttxAlright, should be all set for next week16:54
ttxnotmyname: have a great day16:54
notmynameyou too16:54
ttxSkipping keystone this week16:54
ttxdevananda: ready when you are17:03
devanandattx: hi! still working on my first cup of coffee17:04
devanandattx: so proceed at your own risk :)17:05
ttxthat... is fine17:05
* ttx treads carefully17:05
ttx#topic Ironic17:05
ttxso... kilo-1 strikes next week17:05
devanandawe reviewed k1 plans last night17:05
ttxthat means we'll push a k1 tag sometimes between the 16th and the 18th, whenevr you're happy enough with the state of master to send me a SHA17:05
devanandabumped one proposal, the rest are getting increased attentiona nd folks think they will make it17:06
ttxwhat's up on new-ironic-state-machine ?17:06
devanandaalso, the elephant from last week -- https://review.openstack.org/#/c/133828/17:06
devanandashould be landing today17:06
devanandathat spec is representative of our -intention-17:06
devanandanot a specific piece of code17:06
ttxso no real implementation yet ?17:06
devanandaI am doing the work, for now, of migrating the code to a state machine17:07
devanandaand then others will divy up the new aspects which that spec outlines17:07
ttxOK, maybe you can close it as "informational" when done then, I think that communicates what it is quite well17:07
devanandasounds good17:07
ttxthe other 3 are in good shape ?17:08
devanandaother news, I've been stalled a bit in planning our midcycle17:08
devanandaand need to get back on that this week17:08
devanandai'll update the ML and wiki with details17:08
ttxnext week we'll refine the list to reduce it to milestone tag last minute blockers17:08
ttxso should be slightly busier17:09
ttxfor today, nothing else from me. Questions from you ?17:09
devanandacheers :)17:09
ttxalright then, have a good day. Drink coffee17:10
ttxthat's all for today!17:10
openstackMeeting ended Tue Dec  9 17:10:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-09-08.49.html17:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-09-08.49.txt17:10
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-12-09-08.49.log.html17:10
*** david-lyle_afk is now known as david-lyle17:58
*** eglynn has quit IRC18:29
*** eglynn has joined #openstack-relmgr-office18:48
*** eglynn has quit IRC19:01
*** eglynn has joined #openstack-relmgr-office19:26
*** SlickNik has left #openstack-relmgr-office19:57
*** asalkeld has joined #openstack-relmgr-office20:50
*** mestery_ has joined #openstack-relmgr-office21:37
*** mestery has quit IRC21:38
*** mestery_ is now known as mestery21:51
*** eglynn has quit IRC22:10
*** asalkeld_ has joined #openstack-relmgr-office22:44
*** asalkeld has quit IRC22:46
*** asalkeld_ is now known as asalkeld23:07
*** mestery has quit IRC23:50
*** mestery has joined #openstack-relmgr-office23:59

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