Tuesday, 2015-04-07

*** asalkeld is now known as asalkeld_afk06:26
ttxdhellmann; sorry was away all weekend + Easter Monday06:54
ttxdhellmann: you have to be on oslo.policy (so loading https://bugs.launchpad.net/oslo.policy/+bug/1437992) and then click "Target to Series". If you don't have the "Target to Series" link while on the oslo.policy bug, means there is a rights issue we need to fix (like Adam Young is the only driver there)06:57
openstackLaunchpad bug 1437992 in oslo-incubator "policy file in policy.d will be reloaded every rest api call" [Critical,In progress] - Assigned to Eli Qiao (taget-9)06:57
*** asalkeld_afk is now known as asalkeld07:21
*** zz_johnthetubagu is now known as johnthetubaguy08:00
asalkeldttx: here when you need me08:00
ttxasalkeld: I do!08:00
ttx#startmeeting ptl_sync08:00
openstackMeeting started Tue Apr  7 08:00:36 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
openstackThe meeting name has been set to 'ptl_sync'08:00
ttx#topic Heat08:00
asalkeldall looks green08:00
asalkeldand ready for rc108:01
ttxasalkeld: Alright, if you don't have any bugfix in the queue, now is as good as anytime08:01
asalkeldcool, let's do it08:01
* ttx warms up his scripts08:01
ttxlet me seee if we can merge translations or requirements08:02
asalkeldttx: both done08:03
ttxgood!08:03
asalkeldhttps://github.com/openstack/heat/commits/master08:03
asalkeldwithin the last ~10 commits08:03
ttxIt's my first one for kilo so I have to remember how to do it08:04
asalkeld:-)08:04
ttxOK, we need to push the version bump on master, let me propose that08:05
asalkeldok08:05
ttxhttps://review.openstack.org/17107508:07
ttxApprove if you're happy.08:07
ttxI'll cut the Kilo proposed branch from the commit just before that one08:07
asalkeldok08:07
ttx(and then tag RC1 on the created proposed branch)08:08
asalkeldttx: we are suddenlly getting heaps of this: http://logs.openstack.org/14/170814/2/check/check-tempest-dsvm-full/86acaad/logs/devstacklog.txt.gz#_2015-04-07_06_14_46_46408:08
asalkeld AttributeError: 'InstallRequirement' object has no attribute 'url'08:09
asalkeldi hope that review of yours is ok08:09
ttxasalkeld: well, we'll see...08:09
ttxsuddenly = since when ?08:09
asalkeldlast hour?08:10
ttxhm, ok, will keep an eye on it08:10
asalkeldyeah08:10
asalkeldhttps://bugs.launchpad.net/tempest/+bug/144098408:11
openstackLaunchpad bug 1440984 in tempest "AttributeError: 'InstallRequirement' when running update.py" [Undecided,New]08:11
ttxasalkeld: if you approve the bump I can babysit the fix in the queue and tag when ready08:11
ttxasalkeld: once we cut RC1 we'll use the kilo-rc-potential tag as a list of bugs that may or may not trigger a RC2 window08:12
ttxso you can refine the list of potential show-stoppers there08:12
ttxand we'll evaluate it regularly08:12
stevebakerasalkeld: were you going to be on leave this week?08:12
asalkeldttx: done08:12
asalkeldstevebaker: next week08:12
asalkeldstevebaker: you off this week or next?08:13
stevebakerok, cool08:13
stevebakerthis Friday and Monday08:13
asalkeldttx: i am taking  a holiday next week08:13
ttxasalkeld: we'll let the RC1 be used un-troubled for a few days anyway, to encourage testing08:13
stevebakermy monday, so should be no problem for this ptl_sync08:13
asalkeldttx: stevebaker has agreed to cover for next week08:13
ttxasalkeld: I'll sync with stevebaker to see if we need a RC2 next week08:13
asalkeldthanks08:14
ttxin the mean time if you discover critical issues, just get them fixed on master08:14
asalkeldstevebaker: thanks again for covering08:14
stevebakernp.08:14
ttxso that we can fast-track backports if we need to08:14
asalkeldttx: ok, thanks08:14
ttxasalkeld: That's all I had. Will cut RC1 in the next hours, time for that bump patch to land08:15
ttxasalkeld: thx, and congrats !08:15
asalkeldok, thanks08:15
ttxNice work by the Heat team.08:15
* asalkeld heads off to enjoy a beer08:15
ttxjohnthetubaguy: around?08:16
johnthetubaguyttx: good morning08:16
ttx#info Heat RC1 to be cut asap08:16
ttx#topic Nova08:16
ttx#link https://launchpad.net/nova/+milestone/kilo-rc108:16
ttx#info 7 release-critical bugs on the list, all assigned and in progress08:17
ttxChecking that they are all actually in progress08:17
johnthetubaguyyeah, there are a few dubious ones I just pushed out, I suspect there are more08:18
ttxhttps://bugs.launchpad.net/nova/+bug/1438183 -- some fix merged there, is the bug still needing more ?08:18
openstackLaunchpad bug 1438183 in OpenStack Compute (nova) "Graceful shutdown of nova-compute service fails" [Medium,In progress] - Assigned to Dan Smith (danms)08:18
ttxOh, https://review.openstack.org/#/c/169057/ probably08:18
johnthetubaguyah, yes08:19
ttxSame for https://bugs.launchpad.net/nova/+bug/131357308:19
openstackLaunchpad bug 1313573 in OpenStack Compute (nova) "nova backup fails to backup an instance with attached volume (libvirt, LVM backed)" [Medium,In progress] - Assigned to Fei Long Wang (flwang)08:19
ttxhttps://bugs.launchpad.net/nova/+bug/1430239 looks a bit stale08:19
openstackLaunchpad bug 1430239 in OpenStack Compute (nova) "Hyper-V: *DataRoot paths are not set for instances" [High,In progress] - Assigned to Dorin Paslaru (dpaslaru)08:19
johnthetubaguyyeah, some of these look at lot like the super critical bit for kilo is done08:20
johnthetubaguyI am thinking we tag them as potential and add a note, I can do that after the meeting08:20
ttxyes, but all in all, looks like the RC1 could benefit from a few more days of fixes08:20
ttxand target end of week08:20
ttxat the earliest08:21
ttxjohnthetubaguy: so let's give it a few more days, and reevaluate the criticality of the leftovers by the end of the week08:21
johnthetubaguyyeah, I think thats a good assessment08:21
johnthetubaguymaybe a quick catch up on thursday?08:22
ttxIf nothing critical is left in the pipe, we'll tag. Then if those fixes merge in master and we have enough to justify a RC2, we'll do one08:22
ttxjohnthetubaguy: works for me08:22
johnthetubaguycool08:22
johnthetubaguyquick general question, I am wondering what you take is on "federating" the code review more in Nova?08:23
ttxjohnthetubaguy: While you're around, let me push a open-liberty patch so that you can -2 it08:23
johnthetubaguyttx: ah, cool, thats a good plan08:23
ttxjohnthetubaguy: I think it's really necessary to split nova reviewing along smaller domains of expertise. It's the only way to scale development and avoid critical resources burning out08:24
johnthetubaguyyeah, at this point we have little choice08:24
johnthetubaguyI just worry about loosing consistency across the code base08:24
johnthetubaguybut that not totally worth the cost of slowing everything down08:24
ttxso we kind of had the same problem in stable08:25
ttxjohnthetubaguy: please -2 : https://review.openstack.org/17107808:25
johnthetubaguyI am kinda thinking of a way sub groups can prove themselves worthy, etc, and graduate to have some level of merge ability08:25
johnthetubaguyyeah, thats true, I hadn't thought of stable like that08:25
ttxIn the stable team we could not review everythijng and were lacking local expertise08:26
ttxWhat we put in place is the following08:26
ttxWe have local review teams (per project)08:26
ttxBut we vet the members there to make sure they have the basics rules08:26
ttxWe ask them to ask around when unsure08:27
ttx(escalate to the "core" stable maint)08:27
ttxand then we try to keep an eye on them and check they don't do crazy stuff08:27
johnthetubaguyright, that makes sense08:27
ttxSo stable-maint-core became the guardians of the stable policy, more than reviewers08:27
ttxtransposed to nova, you could have a core group that maintains consistency and quality standards08:28
johnthetubaguyI am just thinking we need a way for a subteam to gain the trust of the core team, like a graduation flow08:28
ttxbut still let subteams go wild08:28
ttxIt's tricky, because you have to fiond a way to communicate the "standards"08:28
johnthetubaguythats true08:28
ttxfor stable policy it's relatively simple08:29
ttxsince you have a few rules and you can call them out when they fail to apply them08:29
ttxFor "consistency" and "quality" it's a bit harder08:29
johnthetubaguyyeah, less subjective08:29
johnthetubaguyright08:29
ttxbut I still think it's the only way to scale08:29
ttxletting go of a bit of control to gain a bit of sanity08:30
johnthetubaguyI mean the other approach is splitting more out of nova, but I think we need both at this point08:30
ttxBut yes, ideally each subteam would grow around a strong nucleus that has the consistency/quality mindset already08:30
johnthetubaguymostly as there is only so much you can sanely split out, and it takes years to do it properly08:30
johnthetubaguyluckily, I think some of that is already happening08:30
ttxso that the subteam doesn't grow it's own culture08:31
johnthetubaguyyeah, thats the worry, subteam X don't do unit tests, they hate those, etc08:31
ttxjohnthetubaguy: yes we won't split out enough and fast enough to avoid losing our sanity08:31
ttxand splitting should make sense technically too08:31
johnthetubaguyttx: thats totally true, well, we have proven that quite well the last 12 months08:32
johnthetubaguyttx: if you do it wrong, you get two competing network stacks…08:32
ttxthe only reason we split is because it's the most convenient way to make Gerrit support the case08:32
johnthetubaguyyeah, there is some truth in that08:32
ttxIf you had magic ways to split reviews across subteams in a single repo, we would do that more often than splitting08:32
johnthetubaguyyeah, not sure we can wait for tooling, but agreed08:33
ttx(splitting still makes sense in a lot of cases, but it's a trade-off with consistency/quality as said above)08:33
johnthetubaguyyeah08:33
johnthetubaguywe were struggling with, if we split it off, they do crazy things, nova dies because the scheduler is broken, boom08:33
johnthetubaguybut you totally captured that above08:33
ttxEven if tooling doesn't support it, you can add a bit of procedures. Like reviews by default are for the core team, but can be tagged so that they are a subteams decision08:34
ttxand at that point subteam +2ers can just go with it08:34
johnthetubaguyttx: agreed, thats my current preference actually08:34
johnthetubaguywell, something like that08:34
ttxand if someone abuses their rights, just revoke the privs08:34
johnthetubaguyright08:34
ttxand backtrack08:34
ttxwe shoudln't limit ourselves to what Gerrit lets us do08:35
johnthetubaguyso the problem we have with nova-core, is its very political to drop people, so it just doesn't happen, we need to be more fluid, then the right things just happen08:35
johnthetubaguyanyways, I think there is enough for me to chew on there, really appreciate your thoughts on that08:35
ttxright -- which is why I don't want to pile up more rights/duties around core reviewing08:35
ttxwill make it harder to drop people08:36
johnthetubaguyah, I get you now08:36
ttxthe core review group should just be the ones with +2, not the "project maintainers"08:36
johnthetubaguyyeah, the current people who have time for +2, etc08:36
ttxbecause removing people from the latter is harder than removing people from the former08:36
ttxsince it implies "you're someone in Nova"08:37
johnthetubaguyyeah, fluidity is important here08:37
johnthetubaguyI think we fail to add people as its hard to remove them08:37
ttxNot opposed in having the latter, just opposed to tie +2 Gerrit rights to it :)08:37
johnthetubaguyright08:37
ttxI want people with +2 be the ones that spens all their time reviewing, basically08:37
ttxdevananda had an interesting strawman: what if you gave Workflow+1 to a separate group from Review+208:38
johnthetubaguyah, not read that bit, I should take a look08:38
ttxI don't think he publicly suggested that08:38
ttxyet08:38
ttxI haven't read the thread you're talking about fwiw, just came back from holiday :)08:39
johnthetubaguyyeah, similar, well a long weekend anyways08:39
ttxthat way you could give review rights to a subgroup, but still quick-vet for change sanity08:39
johnthetubaguyyeah, thats very attractive08:40
ttx(his suggestion was to only let PTL Workflow+1, which might not scale well, but the concept of separating code review from change desirability is interesting)08:40
ttxAlso serves as checks & balances08:41
johnthetubaguyyeah, some small group08:41
johnthetubaguyI think you would want at least one person in each timezone, and bigger projects, two or more, but yes, I like that08:41
ttxmight create botlenecks at the Workflow+1 and merge conflicts, but still worth considering08:41
johnthetubaguyyeah08:41
johnthetubaguywell, even a loose, policy, where you can +W only for merge conflicts, could work08:42
ttxThe fear in giving +2/aprv to subgroups is to lose touch with what theu are doing and discover insanity too late08:42
ttxdeva's strawman kind of addresses that fear08:42
johnthetubaguyyeah, its a nice touch08:42
johnthetubaguynot considered splitting those before, fancy08:43
ttxright, correctness and desirability are actually 2 different things08:43
johnthetubaguyits similar to the adding a +3 that owns +W, but its less… crazy08:43
ttxexcept you don't give +2 to the people who do Workflow+108:44
johnthetubaguyttx: totally true, its a battle we have reguarly08:44
ttx(they can still +1 alright)08:44
ttxbut it takes into accoutn that the pTl is often too busy to maintain crazy review levels08:44
johnthetubaguyttx: yeah, true, or at least, if they have +2, thats independent and not assumed08:44
johnthetubaguygood point, not thought about it that way08:45
ttxYou basically have two groups -- domain experts who vet the code makes sense and is correct08:45
ttxandd rivers who decide that the change is welcome at this time in the cycle08:45
ttxdrivers*08:45
* anteaya likes rivers08:45
ttxfrankly when I review I only ever do the latter, since I'm not an expert anywhere anymore08:46
ttxbut I can still judge the impact of a change and the rationale08:46
johnthetubaguyttx: yeah, I am liking that idea, it has great promise08:47
ttxanyway, i'll let you run. Will comment on that thread when I get to there08:47
* ttx has a lot of ML reading to do08:47
johnthetubaguyttx: cool, thanks for your time, appreciate that08:47
*** eglynn has joined #openstack-relmgr-office11:57
eglynnttx: knock, knock, ready when you are ...12:00
ttxeglynn: hi!12:00
ttx#topic Ceilometer12:00
eglynn#link https://launchpad.net/ceilometer/+milestone/kilo-rc112:00
eglynna few things came up mid/late- last week12:00
ttx#info 3 RC bugs, all in progress and assigned12:00
ttxlooking how far they are12:01
eglynnnothing major, patches for all under review12:01
eglynnthe main one was https://bugs.launchpad.net/bugs/1435855 discussed on the ML etc.12:01
openstackLaunchpad bug 1435855 in Ceilometer "Default rule does not work in ceilometer policy.json" [High,In progress] - Assigned to Divya K Konoor (dikonoor)12:01
eglynnthe approach to resolving while keeping the desired backward compat is agreed12:01
eglynnjust some style issues in the review and we're good to go12:02
ttxrechecking those that were stuck with gate state this morning12:02
eglynncool12:02
ttxOK, looks like we could have a RC1 tomorrow or Thursday12:02
eglynnso no major red flags or alarms12:02
eglynnyep, let's chat again thurs12:03
ttxDid you merge recent requirements and translations ?12:03
eglynnlemme check that12:03
ttxhttps://review.openstack.org/#/c/170388/ could use a +212:03
eglynncool12:04
ttxys, translations were merged12:05
ttxSo let me propose the version bump -- you can -2 it temporarily and approve it when you're happy with things12:06
eglynnsounds like a plan12:06
ttxhttps://review.openstack.org/171152 -- please -2 for the moment to avoid errors12:07
* eglynn looks12:08
eglynn-2'd while we close out the rc1 queue12:09
eglynncool, thanks12:09
ttxso when ready, just approve it and ping me12:09
ttxI'll make things happen from the commit just before that one12:09
eglynnwill do, thanks!12:09
ttxQuestions ? Urgent matters ?12:10
eglynnnope, all good otherwise12:10
ttxalright, let's do this!12:10
* SergeyLukjanov ready12:10
ttxSergeyLukjanov: hi!12:10
eglynnttx: thanks for your time! :)12:10
SergeyLukjanovttx, hey!12:10
ttx#topic Sahara12:10
ttx#link https://launchpad.net/sahara/+milestone/kilo-rc112:10
ttx#info 3 RC bugs, all in progress and assigned12:11
ttxchecking how far and active they are12:11
SergeyLukjanovwe have two issues on board + bunch of doc CR that are nice to have12:11
SergeyLukjanovMapR related just uploaded to review, but it's simple12:11
ttxOK, so you seem pretty close too12:12
* ttx runs a couple checks12:12
SergeyLukjanovyeah, I think tomorrow we'll be fully ready for tag12:12
ttxTranslations & requirements are in12:12
SergeyLukjanovyup12:13
ttxSergeyLukjanov: so I'll propose the version bump so that it's ready for your approval when ready12:13
SergeyLukjanovack12:13
SergeyLukjanovso, I will ensure all needed CRs merged (till the end of tomorrow), than merge version bump and notify you12:14
ttxhttps://review.openstack.org/171155 -- please -2 for the time being12:14
SergeyLukjanovttx, done, thx12:15
SergeyLukjanovno urgent questions or issues12:15
ttxAlright! Have a nice day then12:16
SergeyLukjanovttx, thank you! have a nice day too!12:16
ttxdhellmann: ready when you are12:16
dhellmannttx: here12:16
ttx#topic Oslo12:16
SergeyLukjanovttx, btw how is the RC-1 going for projects?12:16
ttxSergeyLukjanov: pretty good so far12:16
SergeyLukjanovttx, awesome!12:16
ttxhttp://old-wiki.openstack.org/rc/12:17
ttxMost projects under 10 bugs12:17
ttxwhich makes them likely to hit target sometimes this week12:17
ttxThere will be the occasional straggler although I can't predict who that will be12:17
ttxdhellmann: Not sure we have anything to discuss12:17
dhellmannttx: I can't think of anything either :-)12:18
ttxdhellmann: Do we have anything left to d release-wide as far as Oslo is concerned ?12:18
ttxI mean "release-wise"12:18
dhellmannwe need a stable branch in the incubator repository, but that's it12:18
* ttx checks12:18
ttxyes, and a final tag12:19
*** fesp has joined #openstack-relmgr-office12:19
*** fesp has quit IRC12:19
ttxMaybe when all the RC1s are cut, just before we branch requirements ?12:19
dhellmannI found a few issues with some of the library release tools that weren't prepared to work with stable branches, but I've made notes and will be working on fixes12:19
dhellmannyeah, that sounds about right12:19
ttxok then, that should happen early next week12:20
dhellmannsounds good12:20
dhellmannI'm going to pycon this week, so I'll be online but only sporadically12:20
ttxack12:20
* ttx hopes to get most RC1s in before everyone bumps libs12:20
dhellmannoh, and the TC meeting today will be during my flight, so I *think* I'll be there, but that depends on how the wifi holds out12:21
dhellmanndo you mean the clients?12:21
ttxdhellmann: ok, you might want to make sure you voted on stuff before then12:21
dhellmannyeah, I'll do that this morning12:21
ttxdhellmann: no, genera py libs12:21
ttxPycon usually is when people randomly bump their libs12:21
ttxand break the world12:21
dhellmannoh, I see12:21
ttxthe pip bump this morning was just the first sign12:22
dhellmannoh, I missed that12:22
ttxgate all stuck because pip changed API12:22
ttxwhich is according to pip authors not a public API12:22
ttx(only the CLI is public API)12:22
ttxanyway, fun12:23
ttxdhellmann: have a good day and travel!12:23
dhellmannnice12:23
dhellmannthanks, ttyl!12:23
Kiallgate is fixed BTW - Just got a change to pass12:23
ttxyes, We ninjafixed it12:24
*** asalkeld has quit IRC12:40
dhellmannttx: I can't remember how to make launchpad let me associate a bug with more than one release of a project. For example, https://bugs.launchpad.net/oslo.messaging/+bug/1440755 needs to be backported13:10
openstackLaunchpad bug 1440755 in oslo.messaging "NoneType 'retry' parameter causes TypeError in impl_rabbit" [High,Fix committed] - Assigned to Dan Prince (dan-prince)13:11
ttxdhellmann: do you see "target to series" there ?13:11
dhellmannttx: no13:11
ttxok, that is probably what needs fixing13:11
dhellmannoh, hmm, I do on that one13:11
dhellmannI had one on the policy lib the other day and didn't see it there13:12
dhellmannis that a permission setting?13:12
ttx*yeah,; looks like ayoung is the only driver there13:12
ttxyes, need to be a driver I think13:12
dhellmannoh, right13:12
ttxoh, so there is another issue on oslo.messaging13:12
ttxresulting oin the "status tracked in" mess13:13
dhellmann?13:13
ttxproblem is, liberty should be the "active development" series13:13
ttxthat's something you need to switch to match what "master" means13:13
ttxhttps://launchpad.net/oslo.messaging -- see "development focus" there13:14
ttxthat needs to be liberty, if master switched to liberty13:14
ttxotherwise you can't backport to kilo, since master = kilo13:14
ttxlet me fix that13:14
ttxhere13:15
ttxso you should check that all libs that had their kilo branch cut also switched "dev focus" in LP13:16
ttxotherwise you won't be able to create kilo backport tasks there13:16
dhellmannI did a bunch of them, but I guess I missed a few. I'll double-check13:16
ttxI do that as part of the proposed/$SERIES branching process13:16
dhellmannis that scripted, then?13:16
ttxhttps://wiki.openstack.org/wiki/ReleaseTeam/How_To_Release#proposed.2F.24SERIES_branch_cut_.28switch_master_to_next_version.2913:16
ttxno, I do it manually13:17
dhellmannah, ok13:17
ttxnot sure there ius even an API for that. Checking13:17
ttxyes there is, so I could script it in theory13:17
ttxNever had the need for it because doing it for 10 projects is not that painful13:18
ttxbut with oslo libs in mix, might make sense13:18
dhellmannyeah, I have more than that just in oslo now13:18
dhellmannttx: now for https://bugs.launchpad.net/oslo.policy/+bug/1437992 I can see the "target to series" link but it only shows me the liberty series, no kilo13:21
openstackLaunchpad bug 1437992 in oslo-incubator "policy file in policy.d will be reloaded every rest api call" [Critical,In progress] - Assigned to Eli Qiao (taget-9)13:21
ttxIt's because I already added kilo ?13:21
ttxhmm, weird though13:22
ttxno, that must be the reason13:22
dhellmannoh, duh, I didn't notice that13:38
mesteryttx: Here when you're ready!13:45
ttxmestery: hi!13:45
ttx#topic Neutron13:45
ttx#link https://launchpad.net/neutron/+milestone/kilo-rc113:46
ttx#info 6 in-progress bugs, all assigned13:46
mestery6 left, but one of those is in the merge queue13:46
ttxchecking that they are all actively worked on13:46
mesteryhttps://bugs.launchpad.net/bugs/143981713:46
openstackLaunchpad bug 1439817 in neutron "IP set full error in kernel log" [High,In progress] - Assigned to Brian Haley (brian-haley)13:46
mesteryThat's the one in the merge queue13:46
mesteryAck, they should be, I just looked myself this morning13:46
mesteryI had hoped we would have been down to 3 or so this morning, but some of them saw issues during review last night and one needed a unit test written which turned out to be challenging :)13:47
ttxack confirmed13:47
ttxrunnign a few checks13:47
mesterycool13:48
ttxok, requirements & translations all merged13:48
mesteryExcellent!13:48
ttxchecking for missing files in tarballs...13:49
ttxlooks like you are a couple of days away from your rc1 tag(s)13:49
mesteryYes sir, we're getting close!13:49
ttxI propose to upload the reviews for the version bumps, so that they are ready for your approval when all is ready13:49
mesteryAck, sounds good, please proceed with that.13:50
ttxok, I'll ping you with review numbers in a sec, so that you can temporarily -2 them13:50
mesteryPerfect!13:50
ttxneutron -> https://review.openstack.org/17120013:51
mestery-2 :)13:52
ttxexcellent.13:52
mesteryI think we just need to close out these last bugs and then we're good!13:52
ttxneutron-fwaas -> https://review.openstack.org/17120213:53
mestery-2 :)13:53
ttxneutron-lbaas -> https://review.openstack.org/17120513:54
mestery-2 :)13:55
ttxneutron-vpnaas -> https://review.openstack.org/17120613:56
mesteryAlso -2 :)13:56
mesteryThanks for those!13:56
ttxLet's target around Thursday to tag13:56
ttxQuestions ?13:57
mesteryNope, I think we're good, thanks for all the help as usual, you make doing these releases a pain free experience :)13:57
ttxnp, business as usual :)13:58
mestery:)13:58
mesteryThanks ttx, we'll sync thursday then!13:58
mesteryNow, time to run the Neutron meeting :)13:58
ttxcheers13:59
*** thingee has joined #openstack-relmgr-office14:14
ttxnikhil_k: ready when you are14:21
nikhil_kttx: hey, another meeting carried over14:26
nikhil_ksorry about that14:26
ttxnp14:26
ttx#topic Glance14:26
ttx#link https://launchpad.net/glance/+milestone/kilo-rc114:27
ttxI see 3 bugs on the RC list14:27
ttx#info 3 RC bugs, all assigned and in progress14:27
nikhil_kttx: yeah, waiting on gate14:27
nikhil_kthis, https://launchpad.net/bugs/1434237 https://review.openstack.org/#/c/166909/14:28
openstackLaunchpad bug 1434237 in Glance "glance-manage db_export_metadefs fails with NoSuchColumnError" [High,In progress] - Assigned to Ashish (ashish-jain14)14:28
ttxack14:28
nikhil_kI think it has some discussion going14:28
ttxSo it looks like you're pretty close14:28
nikhil_kwe can mark k2 to give it some time14:28
nikhil_kyes14:28
nikhil_kwe should be good14:28
nikhil_kone question though14:28
* ttx runs a few tests14:28
nikhil_kdo we need a stable branch for store and client before RC1?14:29
nikhil_kwe don't have one last time I checked14:29
ttxnot before, but certainly not far after14:29
ttxdhellmann: ^ ?14:29
nikhil_ksure14:29
nikhil_ksometime close to RC2 , or beginning or RC314:29
nikhil_ks/or/of/14:30
ttxwell in theory you won't have a RC2 :)14:30
nikhil_kttx: please do not say that14:30
nikhil_kone sec14:30
nikhil_khttps://bugs.launchpad.net/glance/+bugs?field.tag=kilo-rc-potential14:30
nikhil_kthat's why I say ^14:31
ttxnikhil_k: if you have things you can't release without fixing them, we should delay RC1 a bit14:31
ttxno point in making a release candidate we already know is broken14:31
nikhil_kHow long can we wait?14:31
ttxI'd say one more week14:32
nikhil_kThat would be better14:32
ttxif you have show stoppers they should be on the RC list14:32
nikhil_kI feel we should have stable branch for store and client14:32
nikhil_kyes, all show stoppers are on the list14:32
nikhil_kBut I feel that better to have small bugs fixed too14:32
ttxnikhil_k: master uses capped dependencies anyway, so the stable branch is noly needed if you have to backport stuff there14:32
ttxbut yeah, we should have stable branches cut from the last releases14:33
ttxI'll come back to you on that14:33
nikhil_kyeah, so I'm okay with moving on RC1 for now14:33
ttxWe might want to do that in a more..; systematic way14:33
nikhil_kso that people do some testing and find any more bugs if applicable14:33
nikhil_kand then get RC2 in a better shape14:34
nikhil_kbut either works for me, waiting for RC1 one week too14:34
ttxok, let's target later this week then14:34
ttxand we'll decide14:34
nikhil_ksure14:34
ttxin the mean time let's get the ones on the list in14:34
nikhil_kYeah, today hopefully14:34
ttxalright, let me propose a version bump that will open master to liberty14:35
ttxyou can -2 it until you are happy with your RC114:35
nikhil_kttx: sounds like a plan14:36
nikhil_kthanks14:36
ttxnikhil_k: please -2 temporarily: https://review.openstack.org/17122714:36
ttxapprove when you're happy with state of things14:37
ttxIdeally when all showstopper fixes are in14:37
nikhil_kdone14:37
nikhil_kthanks14:37
ttxI'll talk to you tomorrow, probably, or when that merged14:37
ttxthingee: around?14:37
thingeettx: o/14:37
ttx#topic Cinder14:38
thingeewhat I can't live without https://etherpad.openstack.org/p/cinder-kilo-rc-priorities14:38
ttx#link https://launchpad.net/cinder/+milestone/kilo-rc114:38
thingeeunfortunately a bunch of these would've merged earlier, but we're hitting some jenkins issues.14:38
thingeerechecks are in place14:38
ttx#info status at https://etherpad.openstack.org/p/cinder-kilo-rc-priorities14:38
ttxyep, things need rechecks if they hit the pip issues earlier today14:39
ttxLooks like you could hit the RC1 target.. Thursday ?14:39
thingeeseems more than enough time to me, but I won't complain :)14:39
* ttx runs a few checks14:39
ttxwell, I'll upload the liberty version bump for you to merge when happy14:40
thingeesure14:40
ttxplease -2 temporarily: https://review.openstack.org/17122914:40
thingeedone14:41
ttxSo just approve it when you're happy and I'll make stuff happen14:41
thingeeare we fine with continuing with Kilo once that merges?14:42
ttxthen you should pile up bugs that may be interesting to fix in kilo-rc-potential, fix them in master... and when we have a bunch, we could respin14:42
thingeeerrr14:42
thingeeliberty14:42
ttxyes, once that merges, master switches to liberty14:42
ttxso no more freezes14:43
thingeeok!14:43
ttxI cut the kilo release branch from the previous commit14:43
ttxOK then, I'll talk to you later14:43
thingeeone last question, cinderclient.14:43
ttxyes?14:43
thingeeis it too late to do a cut from there?14:43
thingeeI know that depends on me14:43
ttxIt's too late to bump requirements for sure14:44
thingeeok14:44
thingeeThat's all14:44
ttxI'm not totally clear on the effect of cutting a release there now14:44
ttxI need to speak with dhellmann on that14:44
ttxI'll get back to you14:45
thingeewell the pin for cinderclient would just ignore it14:45
thingeepython-cinderclient>=1.1.014:45
ttxright14:45
ttxdavid-lyle: ready when you are14:45
thingeettx: thanks14:45
david-lylettx: ready14:48
ttx#topic Horizon14:49
ttx#link https://launchpad.net/horizon/+milestone/kilo-rc114:49
ttxI see 6 bugs on the list, one of them unassigned and one of them not up for review yet14:49
ttxchecking how active they are14:49
ttxhttps://review.openstack.org/#/c/165800/ is a bit stale14:50
ttxhttps://bugs.launchpad.net/horizon/+bug/1435869 looks partially fixed, no idea where the second half of the fix (if any) is14:50
openstackLaunchpad bug 1435869 in OpenStack Dashboard (Horizon) "[Launch Instance Fix] Establish Baseline Unit Tests" [High,In progress] - Assigned to Matt Borland (palecrow)14:50
david-lylehhttps://review.openstack.org/#/c/165800/ I'll move out of RC-114:51
ttxhttps://bugs.launchpad.net/horizon/+bug/1436903 slightly unclear state as well14:51
openstackLaunchpad bug 1436903 in OpenStack Dashboard (Horizon) "integration tests failing blocking gate" [Critical,Confirmed] - Assigned to David Lyle (david-lyle)14:51
ttxsame for https://bugs.launchpad.net/horizon/+bug/143882214:51
openstackLaunchpad bug 1438822 in OpenStack Dashboard (Horizon) "Table widget should show a default message when filtering yields no items" [Medium,New]14:52
david-lyleintegration tests are still failing and I've yet to find a fix14:52
ttxok, so that one is a blocker14:52
david-lylewe can ship without it fixed, but would like to work on it until we cut RC-114:52
ttxoh ok14:52
david-lyleall of these are individually not truly a blocker14:53
ttxso yes, you might want to push a few non-critical out of RC1 if they can't get a fix in the next few days14:53
ttxmaybe we should reconvene on Thursday and see if we should just tag14:53
ttxsince none of those sounds critical nor close14:54
ttxbut a few more days shaking it wouldn't hurt14:54
david-lyleyeah, if these aren't complete by thursday we can cut RC-114:54
ttxlet's do that14:54
david-lyleI think a couple of these will have commits by then14:54
ttxLet me propose a liberty bump that you can -214:54
ttxtemporarily14:54
ttxuntil RC1 is ready for you14:54
david-lyleok, sounds good14:55
ttxquestions?14:55
david-lylejust approve that patch when ready and you'll branch from the last commit14:55
david-lyle?14:55
ttxyes14:55
ttxand -2 it in the mean time14:55
david-lyleok, that works14:55
ttxto make sure nobody gets triggerhappy14:55
david-lyleyeah we had one of those yesterday we reverted14:55
ttxPlease -2  https://review.openstack.org/17124114:56
david-lyledone14:56
ttxOK, that is all. I'll talk to you again on Thursday!14:56
david-lylesounds great14:57
david-lylethanks14:57
ttxhave a great day14:57
*** thingee has quit IRC15:01
ttxmorganfainberg: ready when you are15:49
morganfainbergo/15:50
ttx#topic Keystone15:50
ttx#link https://launchpad.net/keystone/+milestone/kilo-rc115:50
ttx#info 1 RC bug, assigned and in progress15:50
morganfainbergRefresh15:50
morganfainbergJust punted that to l115:51
ttxah-ah.15:51
* morganfainberg gave up on the argument to keep it in kilo.15:51
ttxDoes that mean you're comfortable with a RC1 tag now ?15:51
morganfainbergSure15:51
ttxOK, let me propose the version bump15:51
morganfainbergGoing to wait for the one patch that is dating (will run through and make sure all fix committed bugs are tagged to rc)15:52
ttxok, so when https://review.openstack.org/171260 merges, I cut proposed/kilo from the previous commit15:52
morganfainbergAnd I'll approve.15:52
ttxmaybe -2 it until that other patch lands15:52
ttxOr I can mark it as depending if you want15:52
* ttx runs a few checks first15:52
morganfainbergNah ill wip yours15:52
morganfainbergDone. Marked wip. Will make sure no outstanding translations etc are ready and will approve today hopefully.15:53
ttxok, so just approve it and ping me, and i'll branch/tag from there15:53
ttxanything that merges after the version bump is liberty-only15:54
morganfainberg++15:54
morganfainbergthe critical security bug we can rc2 if needed15:54
ttxalright15:55
morganfainbergI moved it off rc blocking due to ossa/OSSN discussion.15:55
ttxyeah, we need to run that in parallel, too hard to sync15:55
morganfainbergExactly.15:55
ttxQuestions?15:55
morganfainbergNope. Besides asking myself if it was a good idea to run for PTL again :P15:56
ttxheh15:56
morganfainbergttx: thanks! :)15:56
ttxlet me know when you approved the bump and I'll keep an eye on it15:57
morganfainbergack15:59
ttxnotmyname: ready when you are15:59
notmynameYo16:00
ttx#topic Swift16:00
ttx#link https://launchpad.net/swift/+milestone/2.3.0-rc116:00
ttxnotmyname: how are things going with your megamerge ?16:00
notmynameWell. That's the focus for this week16:01
notmynameStill targeting Friday for landing it16:01
notmynameAnd I'm working on release notes, etc for the rc16:01
notmynameI'll be sending some stuff the to ml about it16:02
ttxnotmyname: ok16:02
notmynameThis feature has been a huge collaboration from global devs. It's been really cool to see and be a part of16:02
ttxNot sure we have much to discuss until the merge is completed16:03
ttxso I'll let you go back to it16:03
ttxunless you have questions16:03
notmyname:)16:04
ttx#info Still targeting Friday for landing the feature branch16:04
ttx#info Open source is kinda cool16:04
notmynameSummit scheduling will kick off this week for us16:04
notmynameLol16:04
ttxnotmyname: yes, should be able to confirm your allocation by April 1016:04
notmynameGreat. Thanks16:05
ttxThe 6 fishbowl sessions are very likely. The 12 work sessions slightly less (depend on what projects we need to include)16:05
notmynameOk16:05
notmynameWe'll take all we can get :)16:06
ttxcould be 6/8 or 6/10 instead of 6/12, but not really lower16:06
ttxso you can count on 6/8 already16:06
notmynameOk16:06
notmynamePlus Friday sessions?16:07
ttxyes16:07
notmynameAck16:07
ttxOther questions or announcements ?16:07
notmynameI'm good. Thanks16:07
ttxalright, have a great week!16:08
ttxdevananda: ready when you are16:08
*** SlickNik has joined #openstack-relmgr-office16:12
devanandattx: o/16:14
devanandaroofers are making so much noise i can't hear my notification s...16:14
ttx#topic Ironic16:14
ttx#link https://launchpad.net/ironic/+milestone/kilo-rc116:15
ttxThat RC1 list is a bit confusing to me... how current is it with your own tracking tools ?16:15
devanandafairly current16:15
devanandathough i'm about to bump the not-in-progress ones16:16
ttx#info 10 RC bugs, 4 unassigned and 3 in progress16:16
ttxyeah, unless they are showstoppers, sounds like a good tradeoff16:16
devanandaI raised them in the meeting yesterday morning, and apparently no one took them on16:16
devanandathe 4 in progress should be landed soon16:16
devanandawe've also just found a backwards-incompatible change in the client lib, so I plan to fix that before tomorrow as well16:18
ttxok, let me push a liberty version bump for you to approve when all is ready16:18
devanandaack16:18
devanandaI will be on vacation thursday and friday, btw16:18
ttxplease -2 temporarily: https://review.openstack.org/17127416:19
ttxok, so let's cut RC1 before then16:19
ttxLet's target tomorrow16:19
devanandaindeed16:19
ttxrunning a few checks16:19
ttxCould we get that one merged as well: https://review.openstack.org/#/c/169184/16:20
ttxso that we include relatively recent ones in RC1 ? They are likely to be dropped in future RCs fwiw16:20
ttxif they don't reach the %16:21
devanandanothing is above 15% translated yet, iirc16:21
ttxyeah, so that is probably a useless merge, but still good so that we can judge on current adta16:21
devanandak k16:22
ttxok, so when all your bockers merge, just approve that version bump and ping me16:22
ttxand I'll make stuff happen16:23
ttxquestions ?16:23
* devananda grumbles about slow network16:24
devanandawe have a couple related projects (ipa, discoverd, dib) which aren't being release-managed at this time16:25
devanandaso folks will be doing those releases independently16:25
devanandaany thing they should know about that?16:25
devanandaor just follow the same approach that I am with python-ironicclent16:25
ttxI'd say just follow the same approach. We want to cut stable branches for those asap though, so that we can cap16:26
* ttx is still e bit fuzzy on that part and needs to sync with dhellmann16:27
devanandayea... i am fuzzy on that too16:27
devanandai thnk discoverd plans to tag a stable point around April 3016:27
ttxbasically we need to follow that recent spec16:27
devanandabecause it will be based on what is in RC of ironic16:27
devanandanot the other way around16:27
devanandammm. have a link handy? I'll make sure it gets to the right people in ironic16:28
devanandaalso, launchpad tracking page has now been updated16:28
ttxhttp://specs.openstack.org/openstack/openstack-specs/specs/library-stable-branches.html16:28
ttxI'll clarify and get back to you on that16:28
devanandacheers16:28
ttxSlickNik: around?16:29
SlickNikttx: here16:29
ttx#topic Trove16:29
ttx#link https://launchpad.net/trove/+milestone/kilo-rc116:29
ttx#info 3 RC bugs left, all assigned and in progress16:30
ttxchecking that they are all active16:30
ttxNo patch yet for https://bugs.launchpad.net/trove/+bug/1430586 ?16:30
openstackLaunchpad bug 1430586 in Trove "Trove fails to send notification event using oslo.messaging" [High,In progress] - Assigned to Nikhil Manchanda (slicknik)16:30
SlickNikttx: 2 of them have patchsets up already.16:30
SlickNikI'm working on https://bugs.launchpad.net/trove/+bug/1430586 so I should be able to push up a patchset today.16:30
ttxhttps://review.openstack.org/#/c/155555/ looks a bit stale16:31
* ttx doesn't like to depend on stale patches16:31
SlickNikActually, that one isn't super important — so I think we can punt that one to liberty in case it doesn't land in the next couple of days.16:32
ttxok16:33
ttxLet me upload a review that you can approve when all is ready from your pov16:33
ttxPlease -2 it temporarily: https://review.openstack.org/17128216:33
ttxMerging this one will open master for Liberty development, so only merge when you're ready for RC116:33
ttxPing me when you approve it and i'll make magic happen16:34
SlickNikttx: awesome. Just -2'ed it. Will ping you once ready and approved.16:34
ttxAlright looks like you're all set. We could cut RC1 on Wed/Thu16:35
ttxQuestions ?16:35
SlickNikNope, sounds good to me.16:35
ttxAlright, that concludes our syncs for today16:36
ttxThanks !16:36
ttx#endmeeting16:36
SlickNikAs always, thanks for your help!16:36
openstackMeeting ended Tue Apr  7 16:36:15 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-07-08.00.html16:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-07-08.00.txt16:36
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-07-08.00.log.html16:36
SlickNikTalk to you later.16:36
ttxcheers!16:36
morganfainbergttx, updated the RC1 list to cover all "fixed released" patches for keystone and the in-flight [actively gating] ones16:51
morganfainbergttx, so we have a few more that are added. but i wont hold up if something bounces out of gate.16:52
devanandattx: question -- i'll be on vacation thu - sun. at the moment, no other cores can approve changes to stable or proposed branches of ironic.18:04
devanandattx: that is currently shared by our maintenance team (me + adam_g)18:04
devanandattx: is there a potentially negative impact on other projects during that window? Eg, if some issue is found in ironic proposed/kilo and neither of us are around to approve it before monday18:05
*** johnthetubaguy is now known as zz_johnthetubagu18:08
*** eglynn has quit IRC18:52
ttxdevananda: I can approve backports21:20
ttxdevananda: as long as they are approved by the core team on master and merged there21:20
devanandattx: oh. cool.  I forget about your superpowers :)21:20
ttxThat is my proposed/* superpowers21:21
ttxmorganfainberg: https://review.openstack.org/#/c/171260/ almost there21:21
morganfainbergttx, yep21:21
morganfainbergttx, we will need an RC2, minor things and something up in the air still21:21
morganfainbergttx, but i didn't want to reset the gate and make lots of people angry21:22
morganfainbergrc2 seems likely anyway21:22
morganfainbergjust based on past history21:22
ttxmorganfainberg: we'll keep RC1 up for a few days before opening up a RC2 window21:22
ttxdon't want to discourage testersd21:22
morganfainbergttx, the only thing confirmed for RC2 will be man page update, possibly sample config21:22
ttxso just pile up fixes on master, ready to be backported21:23
morganfainbergttx, so +10021:23
morganfainbergon holding a couple days21:23
ttxand we'll open a RC2 window next week21:23
* ttx gives that Neutron thing 2 more minutes to clear the queue21:23
ttxor else I'll go to bed21:24
ttxah, completed21:24
ttxI'll stay up then21:24
* ttx nudges zuul21:27
ttxbranch cutting in progress21:37
nikhil_kttx: no meeting today, wanna make sure I did not miss it :) (I realize that I'm very late)21:47
nikhil_k?21:48
ttxright, skipped it21:48
nikhil_kthanks21:48
ttxmorganfainberg: ok, it's in21:58
morganfainbergyep :)21:58
ttxGoing to bed21:58
ttxcheers!21:58
*** mestery has quit IRC22:11
*** mestery has joined #openstack-relmgr-office22:12
*** asalkeld has joined #openstack-relmgr-office22:53

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