Tuesday, 2014-09-23

*** markwash__ has quit IRC00:35
*** david-lyle has quit IRC00:50
*** markwash__ has joined #openstack-relmgr-office01:48
*** markwash__ has quit IRC02:12
*** markwash__ has joined #openstack-relmgr-office03:06
*** markwash__ has quit IRC03:24
*** markwash__ has joined #openstack-relmgr-office04:19
*** markwash__ has quit IRC05:01
*** markwash__ has joined #openstack-relmgr-office05:06
*** markwash__ has quit IRC05:28
*** flaper87|afk is now known as flaper8706:05
*** markwash__ has joined #openstack-relmgr-office07:44
mikalttx: around?07:55
ttxmikal: yes07:56
mikalWe're on in about four minutes?07:56
ttxmikal: yes07:56
*** zz_johnthetubagu is now known as johnthetubaguy07:57
* ttx grabs coffee07:58
* johnthetubaguy grabs breakfast07:59
mikalHeh07:59
ttx#startmeeting ptl_sync08:02
openstackMeeting started Tue Sep 23 08:02:16 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
ttx#topic Nova08:02
openstackThe meeting name has been set to 'ptl_sync'08:02
mikalHi08:02
ttxohai08:02
ttx#link https://launchpad.net/nova/+milestone/juno-rc108:02
mikalYeah, that08:02
mikalSo... where to start?08:02
mikalI'm a bit worried about the unassigned bugs08:03
ttxThe curve is not really going down at http://old-wiki.openstack.org/rc/08:03
johnthetubaguymikal: yeah, had that issue a bit ago08:03
mikalHuh, no worse than many other projects though08:03
johnthetubaguyttx: so people are adding all sorts they find important-ish, rather than blockers08:03
mikalYeah, I was trying to review things associated with those bugs and ended up lost spending the last two days fixing a security vulnerability that was release critical08:04
ttxjohnthetubaguy: it's tricky because damn LP doesn't prevent anyone from doing that08:04
mikalBecause the proposed fix set off my bogo filter08:04
johnthetubaguymikal: some of those critical gate bugs are just not likely to get fixed in time, some people were digging08:04
johnthetubaguyttx: yeah08:04
mikalYeah, I feel that critical gate != critical release08:04
mikalThey're important08:04
ttxrigth, so they can stay criotical but not be release blockers08:05
mikalJust not important to the release per se08:05
mikalAgreed08:05
ttxjust remove the rc1 tag. If they get fixed, all th better, we'll take them08:05
johnthetubaguymikal: been chasing some nasty xenapi stabiity bugs that would have been embarrassing not to fix myself08:05
mikalHeh08:05
ttxbut if nobody is assigned to them at this point, no point in keeping them in list08:05
johnthetubaguyttx: when are we hoping to tag, before thursday I guess?08:05
mikaljohnthetubaguy: can you take a pass at untargetting gate bugs which aren't release critical today?08:05
mikalI thought we didn't tag until the rc bug list got to zero?08:06
johnthetubaguymikal: yeah, if we want to start drawing up the final list08:06
ttxjohnthetubaguy: before Tuesday next week.08:06
ttx"end of month"08:06
johnthetubaguyttx: gotcha08:06
ttxbut yeah, at least trying this week would be nice08:06
johnthetubaguymikal: thing is, people were kinda thinking, we just take the criticals as blockers, the rest are just an "aim"08:07
ttxmikal, johnthetubaguy: would you say the list contains all the true known blockers at this point ?08:07
mikalttx: all that I am aware of08:07
johnthetubaguyttx: "know" is a bit caveat, but yes I think so (minus security ones)08:07
mikalThere hasn't been a lot of conversation about it though08:07
mikalThe thread on -dev was pretty quiet08:07
mikalWhich surprised me to be honest08:08
johnthetubaguymikal: I think people just lobbed the tags on08:08
johnthetubaguywell, target I mean08:08
mikaljohnthetubaguy: yeah, that's what I figured in the end08:08
ttxSo yeah, as far as bug list is concerned, I would trim it to assigned bugs only, and those that have some chance to make it before end of month08:08
johnthetubaguyttx: cools, I can do that08:09
mikal"Dropping as unassigned" seems like a reasonable comment to leave on them08:09
mikaljohnthetubaguy: I can do that if you want me to be the bad guy08:09
ttxWould be good to get the security fix worked on though08:09
ttxsince fixing before release is always better than after08:09
mikalYou're thinking of 1369627?08:09
ttxbut we shouldn't block on that08:09
mikalFor the security fix?08:09
ttxno. Is 1369627 a security thing?08:10
johnthetubaguymikal: yeah, I don't mind, security stuff I probably just need to find people to work on them08:10
mikalYes, yes it is08:10
mikalThere's another I haven't noticed yet?08:10
mikalWe're fixing 1369627 by reverting three patches08:10
mikalOne done, one approved and in gate, the other needing review08:10
ttxmikal: see pm08:10
mikaljohnthetubaguy: if you could review https://review.openstack.org/#/c/123072/ that would be cool08:11
ttxHmm, you should set "Public security" if it's a security bug08:11
ttxotherwise it will never enter the OSSA realm08:11
ttxalthough... it's juno-specific ?08:11
mikalAhhh, I see08:11
mikalYeah, we've never "released" the bad code08:12
mikalOn the other one, that sounds like something we could ask Vishy to look at08:12
ttxso in that case we just need to fix it prerelease08:12
mikalHe's been playing there in the last couple of weeks08:12
ttxno need to get the OSSA team on it, no advisory needed08:12
mikalYeah, I don't know of any CD'ers running rbd, so we should be ok with those guys08:12
johnthetubaguymikal: continuous deployment is a bit odd though08:12
ttxas log as we fix it for rc108:12
mikalFor the other one I am emailing Vishy now to ask if he can help08:13
ttxOK, let's trim that list and start burning all targets down. We'll do another checkpoint on Thursday08:13
ttxmikal: did you release a final novaclient ?08:14
mikalYes, I did08:14
mikalOh, can we add johnthetubaguy to whatever group gives him access to the security bugs if we havne't already?08:14
mikalThat makes sense from his LP wrangling role08:14
johnthetubaguymikal: I have access08:14
mikalOh, cool08:14
johnthetubaguymikal: just ended up focusing more on blueprints really08:15
mikaljohnthetubaguy: yeah, that's fair08:15
mikalJust at the moment it makes sense to get you access if you don't alrady08:15
mikalWhich you do08:15
mikalSo ignore me08:15
johnthetubaguylol, no problem08:15
johnthetubaguyso the list, I don't mind trying to trim that after the meeting08:16
ttxok, so the client looks fine now08:16
mikalThat would be cool, thanks08:16
johnthetubaguyat least all unassigned ones that seem unlikely to make it08:16
ttxquestions ?08:16
mikalNot a question, but I am unsure if I will make the release meeting08:16
mikalI am hoping to08:16
mikalBut it depends on the school thing which is making me miss the TC meeting ending on time08:17
johnthetubaguywhat are the summit deadlines again, session wise?08:17
mikalSo we shall see...08:17
ttxmikal: as far as design summit is concerned, you would get 18 scheduled sessions and a full-day of contributors meetup (instead of 27 sessions)08:17
mikalttx: ok08:17
*** markwash__ has quit IRC08:17
mikaljohnthetubaguy: I think because we're not using the selection web site for sessions we're a bit more flexible with selection deadlines?08:18
johnthetubaguyI guess its all decided post PTL election08:18
mikalOr am I confused?08:18
mikalYeah, definitely new PTL territory08:18
mikalBut we can prime the pump for them, so to speak08:18
ttxwe just need a schedule 1 or 2 weeks before the thing starts08:18
johnthetubaguycools, that makes sense08:19
johnthetubaguyI am just thinking about specs08:19
ttxbut given it's collaboratively discussed now, that may mean start earlier08:19
mikalWell, we already have a brain storming etherpad08:19
johnthetubaguyttx: true, give people time to chime in08:19
mikalWe just need to start talking about it in meetings more08:19
mikalBut I think release should take most of our meeting time at the moment08:19
ttxmikal: ++08:19
mikalFor the next week at least08:19
ttxuntil RC1 is done, just talk release and RC bugs08:19
ttxafter RC1 is done we'll add bugs much more selectively08:20
mikalYeah, let's not confuse people08:20
ttxif needed08:20
mikalAlthough we promised to open kilo specs next week08:20
ttxso it's easier to switch minds to kilo08:20
mikalSo I need to remember to not forget that as well08:20
johnthetubaguygood good, sounds perfect08:20
johnthetubaguyjust wanted to make sure we are all on the same page08:20
mikalSo yeah, I think we're done here?08:21
mikalYeah, I think we are08:21
mikalWhich is good08:21
ttxyes we are08:21
ttxttyl!08:21
johnthetubaguythanks all08:21
mikalCool, well thank for both of your time yet again08:21
*** eglynn-office has joined #openstack-relmgr-office11:44
ttxeglynn: ready when you are11:44
eglynn-officettx: knock, knock :) ... ready when you are11:44
ttx#topic Ceilometer11:44
eglynn-office#link https://launchpad.net/ceilometer/+milestone/juno-rc111:44
eglynn-officeso fair progress in landing bug fixes11:45
ttx6 bugs left, we might be able to tag before end of week?11:45
eglynn-officewell, there are 2 that I'd like to wait on especially11:45
eglynn-officehttps://bugs.launchpad.net/bugs/130955511:45
eglynn-officehttps://bugs.launchpad.net/bugs/135786911:45
eglynn-officethe first has an incomplete fix proposed, needs more testing and a more complete fix11:46
ttxok, we'll see how it goes11:46
eglynn-officefor the second, I've a simple config workaround to fall back on but I'm also experimenting with a more complete fix11:46
ttxOK... On the client release side you did a 1.0.1111:46
eglynn-officeOK, so you're preference was EoW for RC1?11:46
eglynn-officeyep, I cut 1.0.11 on Monday11:46
eglynn-officeslightly delayed by lag in the gate getting the last couple patches merged11:47
ttxMy preference is by EoW yes, and before next Tuesday otherwise11:47
eglynn-office#link https://pypi.python.org/pypi/python-ceilometerclient/1.0.1111:47
eglynn-officeOK, got it11:47
ttxOK, you seem to be in good shape11:48
ttxI'll sync again on Thursday and see if we can do RC1 before eow11:48
eglynn-officecool, sounds like a plan :)11:48
ttxAs far as summit is concerned, you would get 5-6 scheduled sessions, and a full day of contributors meetup11:49
ttx(compare to 10 scheduled sessions in ATL)11:49
eglynn-officeOK, obviously I'd prefer 6 to 5 if possible11:50
ttxyeah, my current layout includes 6, but i'm waiting on feedback from some programs11:51
eglynn-officeI'd like to accomodate the Monasca folks with a design session on the ceilo track if poss11:51
eglynn-office(I've been chatting with RolandH about opportunities for collaboration)11:51
ttxok that works11:52
ttxanything to discuss at meeting . Any red flag wrt release ?11:52
eglynn-officenope, no red falg from me11:52
eglynn-office*flags11:52
ttxOK then, talk to you later!11:53
eglynn-officecool, laters11:53
*** eglynn-office is now known as eglynn-lunch11:59
ttxdhellmann: ready when you are12:14
dhellmannttx: here12:14
ttx#topic Oslo12:14
ttxAre we all set release-wise ?12:14
dhellmannyes, we should be set12:15
ttxhttps://launchpad.net/oslo/+milestone/next-juno12:15
dhellmannwe had one patch release of oslo.db to help stabilize the nova gate, but that's it12:15
ttxThis should in theory show all FixReleased at some point12:15
ttx(if we are indeed done)12:15
dhellmannwe never ran the script against the incubator. I can update those by hand. The others I'll move to kilo.12:16
dhellmannI was holding onto the idea of a pbr release, but I think at this point we should wait for the other releases to finish.12:16
ttxdhellmann: for oslo-incubator, maybe rename next-juno to 2014.212:16
dhellmannok12:16
ttxsince that's what we tagged12:17
ttxA few fixes were merged after that in master and should not get FixReleased, though12:17
dhellmannwe count master for the incubator as released, since the important tracking is when the merge happens in the apps12:18
ttx(bug 1372177)12:18
dhellmannat least that's how I've been treating it12:18
ttxdhellmann: hmm, but those fixes are post-2014.2 tag12:18
ttxso they should not appear FixReleased in 2014.212:19
dhellmannok, that one isn't targeted to the milestone yet, so I'll put it in a kilo milestone12:19
ttxthe others were without a bug ref12:20
dhellmann?12:20
ttxso that's the only one you could accidentally include12:20
ttxdhellmann: let me explain12:20
ttxif you run the script that turns FixCommitted bugs into FixReleased, you need to do it when you tag, otherwise you may catch bugs that were fixed after the tag ifs applied12:21
ttxhere I just checked the merges that happened after the tag to make sure we don't accidentally indlude them in 2104.212:21
dhellmannoh, yeah, I was going to just update all of those bugs by hand to avoid that12:21
ttxThere are 3 of them12:21
ttxwell, actually, 412:22
ttxhttps://review.openstack.org/#/c/122377/ references no bug12:22
ttxhttps://review.openstack.org/#/c/123017/ references 137217712:22
ttxhttps://review.openstack.org/#/c/115213/ references no bug12:23
* dhellmann nods12:23
ttxhttps://review.openstack.org/#/c/121305/ references related bug 136891012:24
ttxanyway, just me and my damn accuracy :)12:24
dhellmannI will make sure those bugs are targeted with kilo12:24
dhellmanns/with/to12:24
dhellmannI guess if I do that, I can use the script to update the bug settings instead of doing it by hand12:25
ttxso, on https://launchpad.net/oslo/+milestone/next-juno there are still oslo.concurrency PBR taskflow and oslo.vmware things12:25
ttxAre those all still waiting for a tag ?12:26
dhellmannoh, we didn't do a final release of those, that should all move to kilo, too12:26
dhellmannI'll spend the morning cleaning this up. I should have looked at it yesterday.12:26
ttxwe won't do a final release of those ?12:26
dhellmannwait, hang on, we did a release of concurrency12:26
dhellmannoh, no, that's serialization -- I keep mixing those up12:27
ttxETOOMANYLIBS12:27
dhellmannno, we had a few libs that were not quite ready and weren't going to be adopted, so we focused on fixing up the ones in use12:27
dhellmannI will move all of the unfinished work to kilo12:27
ttxdhellmann: OK, so once you are done with the juno cleanup let me know, i'll doublecheck and we can close Juno for good12:27
dhellmannyeah, seriously, we're up to something like 19 or 20 now12:27
dhellmannok, sounds good12:28
ttxdhellmann: as far as design summit is concerned... I think we can preserve ~7 oslo scheduled slots12:29
ttx(down from 11 in ATL)12:29
dhellmannwe should be able to make that work, esp. if we have pod space on friday12:29
ttxYou would get a dedicated "pod" on the Friday12:29
dhellmannreading my mind :-)12:29
ttxand we can also discuss major issues on the cross-project day, if any12:29
dhellmannI don't want oslo to be seen as the driver for those things. We may have one or two, but I want the TC to really run those as "all of openstack" rather than funnelling them through oslo12:30
ttxoh sure, that's what I meant12:30
dhellmannok12:31
ttxany release red flag on your side ?12:31
ttxanything to discuss at cross-project meeting today ?12:32
dhellmannI haven't heard anything. We looked into that keystoneclient issue on the stable branches, but it's going to have to be fixed in their client.12:32
dhellmannnothing this time around, I think12:32
dhellmannwell, I need to figure out the timing to remind everyone to prioritize adoption of libraries early in kilo12:33
ttxdhellmann: ok, great!12:33
dhellmannthey're probably not thinking about that yet, but I don't know if we'll have project meetings after the release is actually done?12:33
ttxdhellmann: if you have some time, you can help sdague and myself go through the requirements review12:33
dhellmannyeah, I was going to ask if there's anything you need help with12:33
ttxthe more the merrier12:33
dhellmannaren't we locked down for requirements changes?12:33
ttxdhellmann: yes, that's why I'd like to clean up the slack there12:34
dhellmannoh, so -2 things?12:34
ttx-2 what can be, abandon some12:34
dhellmannok12:34
ttxand discuss at release meeting today what still needs a final call12:34
ttxI triued to come up with a list for that and got confused by some12:34
dhellmannok, I'll look at that after I clean up our bug tracker12:35
ttxok, you will be able to find us on #openstack-dev12:35
dhellmannok12:35
*** eglynn-lunch is now known as eglynn13:26
ttxjgriffith: ready when you are14:00
jgriffithttx: ready14:06
ttx#topic Cinder14:06
ttxhttps://launchpad.net/cinder/+milestone/juno-rc114:06
ttxYour curve is one of the few going down at http://old-wiki.openstack.org/rc/14:07
ttxso you seem on a good trend14:07
jgriffithcool!14:07
ttxThere is one unassigned security issue though that we should at least try to get in the release rather than after14:07
ttx(it's the one unassigned bug in the list)14:07
ttxyou might want to privately get it assigned14:08
jgriffithttx: ahh14:08
jgriffithyeah, there's a patch proposed14:08
jgriffithI can mark it assigned14:08
ttxYou did release a client last week (1.1.0) and the global requirements bump is gating14:08
ttxso we are covered on that side14:08
jgriffithYeah, I'll do one more client bump after RC cut14:09
ttxWhen do you think you can empty the list ? Sometimes this week ?14:09
jgriffithI think this week yes14:09
jgriffithmost are in progress and doing "ok"14:09
ttxjgriffith: one more client bump after RC cut ?14:09
ttxWe wanted to freeze the clients.. last Friday14:09
jgriffithI'd like to if it doesn't make people freak out14:09
jgriffithahh...14:09
jgriffithhmm...14:09
ttxso unless you have some critical issue14:09
jgriffithso I have one issue14:09
jgriffithdebug output was broken by all the i8n shenanigans14:10
jgriffithpatch is on it's way through right now to fix14:10
jgriffithkinda of a big deal IMO14:10
ttxOK, I think it's fine to tag a new one, but maybe not bump the global requirements14:11
jgriffithttx: oh.. for sure14:11
ttxjust make sure everyone knows about it when you cut it14:11
jgriffithI'll avoid that at all costs14:11
jgriffithI will... in fact I'll send a note to dev today warning them if that helps14:11
ttxdo you have a bug reference for that issue ?14:11
jgriffithI do....14:11
jgriffithhttps://bugs.launchpad.net/python-cinderclient/+bug/113073014:12
jgriffithand it landed14:12
jgriffithso I'll push today and send an email to everyone14:12
ttx#info New Cinder client expected soon (1.1.1 ?) to fix bug 113073014:12
ttxok14:12
ttxAny red flag release-wise ? Anything you'd like to discuss at meeting today ?14:13
jgriffithNo red flags (as of yet)14:13
jgriffithand no, nothing I need to bring up at meeting14:13
ttxjgriffith: as far as summit goes, i'm still working on allocation but you should get 6-7 scheduled slots14:13
ttx+ the half-day meetup14:13
ttxin case there is room for it, would you be interested in a full-day thing ?14:14
jgriffithttx: always, but honestly I wouldn't rank us high priority for it14:14
jgriffithttx: and I'd rather see more cross-project interaction from Cinder team14:14
jgriffithttx: I'm realizing more and more that a lot of folks are really silo'd14:15
jgriffithwould like to prompt some change there14:15
ttxok.14:15
jgriffithKeep in mind I'm going to propose being very picky about session topics this time around14:15
jgriffithassuming my successor follows that plan14:15
ttxok, talk to you later then! Hope we can cut RC1 later this week14:16
jgriffithsounds good14:16
ttxmorganfainberg: ready when you are14:16
jgriffithI'll let you know if I think it's ready before Friday14:16
morganfainbergttx, o/14:17
ttx#topic Keystone14:17
ttxhttps://launchpad.net/keystone/+milestone/juno-rc114:17
ttx2 bugs left, looks like we should be able to cut this week14:17
morganfainbergttx, those are both addressed by the same fix, should gate today14:18
ttxOK, so I might be in touch soon :)14:18
morganfainbergttx, in fact, working with another core to get that reviewed right now as well :)14:18
ttxmorganfainberg: on another note, we might want a keystonemiddleware tag to catch the latest security issue in a release14:18
ttxbefore we issue an advisory for it14:18
morganfainbergttx, Keystone client is also ready for 0.11.1 release fixing the bug in config14:18
ttxwhich bug ?14:19
morganfainbergttx, keystonemiddleware is planned to get a new tag/release as soon as https://gist.github.com/dolph/651c6a1748f69637abd0 those 4 reviews merge.14:19
morganfainbergttx, https://launchpad.net/python-keystoneclient/+milestone/0.11.114:20
morganfainbergthe glance exploding one, #127242214:20
ttxah ok14:20
morganfainbergerm 137242214:20
morganfainbergi will either need to have you push the tag or wait for dolphm today.14:20
ttxok14:20
morganfainbergi do not have permission to push tags.14:20
ttxping me as needed14:21
*** david-lyle has joined #openstack-relmgr-office14:21
ttxany other thing release-wise ?14:21
morganfainbergttx, anytime today would be good to get 0.11.1 out.14:21
morganfainbergttx, no i think that is it. looking forward to getting Keystone tagged (hopefully minimal gate fighting for that last blocker)14:21
ttxAs far as summit goes, still working on allocation, but keystone could get 6-7 scheduled slots + a half-day meetup14:22
morganfainbergttx, that sounds about the same as last time, and fair.14:22
ttx(compared to 8 scheduled slotsin ATL)14:22
morganfainbergttx, right, the 1/2 day covers the extra.14:22
ttxmorganfainberg: that's all I had14:22
morganfainbergttx, cool. sounds good and i'll def. ping you as soon as we have the middleware reviews ready. My goal is for all of them to be done today / tomorrow morning14:23
morganfainbergttx, i expect it's just going to be gate rechecks to get things through14:23
morganfainbergttx, same with keystone.14:24
ttxok, I'll be a bit busy today so I may not be able to get back to you wrt: python-keystoneclient tag.14:24
ttxIf still needed by tomorrow, I should be much more available then14:24
ttxdavid-lyle: ready when you are14:24
ttxmorganfainberg: thx!14:24
morganfainbergttx, i'll ping dolphm if i see him.14:25
david-lylettx: ready14:25
ttx#topic Horizon14:25
morganfainbergttx, if not, will bug you tomorrow :)14:25
ttxhttps://launchpad.net/horizon/+milestone/juno-rc114:25
ttxSo... 44 opened RC1 bugs is way too much14:25
david-lyleyes, getting ready to prune that down14:26
ttxyou need to cut down the list to release blcokers only. If anything else gets in in the mean time, taht's fine14:26
ttxbut there is no way those 44 will get in and we still hit the release date :)14:26
david-lyleI think the list is actually about 4 for release blocking14:26
david-lyleat least that's what I've been tracking14:27
ttxIdeally we'd cut RC1 before end of week, worst case before end of month14:27
david-lylemy target was end of the week, unless something else comes up14:27
ttxok, you can use a tag to track the nice-to-have14:27
david-lylesure14:27
ttxwe'll discuss the last depfreeze exceptions at the meeting today14:28
david-lyleok14:28
ttxso that we can make the final call on them14:28
ttxany red flag wrt: release ? Or topic for the meeting today ?14:28
david-lyleno14:29
ttxAs far as design summit goes, my initial allocation gives horizon 6 slots + the half-day of meetup14:29
david-lylethat sounds reasonable14:30
ttxin case there is room for it, could you be interested in a full day ?14:30
david-lyleI'm not sure we'll need a whole day if there is pod space available14:31
ttxok.14:31
ttxdavid-lyle: that's all I had. Anything else ?14:31
david-lyleif no other teams speak up we do have some architecture work I'd like to get done there, but I think the number of participants may not warrant a whole room14:32
david-lylewant to make sure my recollection is correct, once RC1 is closed, master is Kilo14:32
david-lylecorrect?14:33
ttxyes14:33
david-lylealso a heads up, due to translations, we'll likely have an RC2 just for that, barring other issues14:33
david-lyleI think the translation team is targeting end of month14:34
david-lylethat's all I have14:35
ttxdavid-lyle: it would be good to merge relatively-recent translations for RC1 anyway14:36
ttxbut i agree14:36
ttxmestery: ready when you are, but you seem to have a conflict :)14:36
mesteryttx: Sorry, yes, in a neutron meeting. Can we push this a bit for today? Apologies.14:36
ttxsure14:36
mesteryttx: OK, I'll ping you if this gets done early.14:37
david-lylettx: they're automatic now, we merge as available14:37
david-lylethanks14:37
mesteryttx: Here if you're around.15:01
ttxmestery: on a call15:01
mesteryttx: OK. Any ETA?15:01
mesteryI may jump into a 15 minutes call myself if you'll be at least that long.15:01
*** flaper87 is now known as flaper87|afk15:01
ttxat least 15 min yes15:01
mesteryOK15:01
ttxnotmyname: around?15:29
ttxmestery: you can go now if you want15:30
mesteryttx: ack15:32
ttx#topic Neutron15:32
ttxhttps://launchpad.net/neutron/+milestone/juno-rc115:32
ttx33 targeted bugs, at this point it's too much15:32
ttxyou need to reduce to true release blockers15:32
mesteryttx: I agree.15:32
ttxso that we can hit RC1 sometimes before the end of the month15:32
mesteryYes, I spent some time in the meeting talking about that.15:32
mesteryI'll have this list culled down by tomorrow.15:33
ttxgreat15:33
mesteryWhen will you cut RC1?15:33
mesteryIs it this week?15:33
*** david-ly_ has joined #openstack-relmgr-office15:34
*** david-lyle has quit IRC15:36
mesteryttx: There?15:36
ttxsorry just a sec15:37
mesteryttx: ack15:37
notmynameI'm here (on my phone)15:39
mesteryttx: Apologies, I need to take off now.15:40
ttxmestery: ok15:40
mesteryttx: I will get the RC1 page under control, and I have nothing specific for today's cross-project meeting other than to go over the Kilo schedule if people want to.15:40
mesteryttx: Thanks!15:40
ttxsorry got interrupted15:40
ttxmestery: will talk to you again later15:41
ttx#topic Swift15:41
ttxnotmyname: how is your next release coming up ?15:41
notmynameOverall good.15:41
notmynameProbably won't land everything I want, but the important stuff will15:42
ttxnotmyname: what would be the updated ETA ?15:42
notmynameWe're still on track for next week. I'll work closely with you for the RC15:42
ttxnotmyname: ok, I'll be around15:42
notmynameI have 2 other things15:43
ttxdo you need to cut another swiftclient ?15:43
notmynameFirst, we found a regression in the last swiftclient15:43
notmynameYes15:43
notmynameThe last one we thought was good but into'd a keystone v3 reg15:43
ttxok, the sooner the better, especially if you want to bump the global-requirements15:43
notmynameWill cut a minor point release later this week15:43
notmynameNo requirements changes15:44
ttxok15:44
notmynameSecond, next week we have a kid cycle meetup thing in Boston15:44
ttx#info new swiftclient expected later this week to fix a regression15:44
ttxkid cycle?15:44
notmynameMid. Phone autocorrect15:45
ttxkilo maybe15:45
notmynameWe'll be looking at ec work and summit prep and etc15:45
ttxok15:46
ttxStill working on allocation, but looks like you would get 6 scheduled slots + half-day meetup15:47
ttxcompared to 8 slots in ATL15:47
ttxso more time overall15:47
ttxbut less cheduled ones (like everyone else)15:47
notmynameOk. I'll be starting the communal scheduling this week15:47
notmynameSounds good15:48
ttxnotmyname: ok, anything els e?15:48
ttxzaneb: around?15:48
notmynameNo. I'm good15:48
zanebo/15:48
notmynameThanks15:48
ttxnotmyname: thx!15:48
ttx#topic Heat15:50
ttxhttps://launchpad.net/heat/+milestone/juno-rc115:50
zanebwe got the FFEs in :)15:50
ttx14 targeted bugs left15:50
ttxzaneb: yep:)15:50
ttxare all those release vlockers ? Or could you refine the list so that only RC things are left in it ?15:51
ttxblockers*15:51
ttxI'd like to hit RC1 before the end of the month if possible15:51
zanebyeah, I definitely don't think all of those are release blockers15:52
zanebI think that's probably feasible15:52
ttxyou can use a tag for nice-to-have if you want to track them15:52
ttxI'd like to make sure we are burning down release-critical ones at an acceptable rate15:52
zanebI think the High priority ones are the most release-critical15:53
ttxSo I'll be in touch later this week to see how far we are from RC115:53
zanebfortunately we don't have a large number of those15:53
zanebok15:53
ttxYou did cut a 0.2.11 heatclient15:53
* zaneb needs to find time to scrub the whole bug list anyway15:53
zanebyes we did15:53
ttxand I had a question for you about https://review.openstack.org/#/c/122520/15:53
ttxis that bump *required* ?15:54
ttxi.eL. does it fix some release-critical bug somewhere ?15:54
ttxwe shouldn't bump the floor unless it's required15:54
zanebnot sure about that15:54
zanebI will check with stevebaker15:54
ttxwell, the review is -1ed until you do find a good reason why we should bump in those troubled times15:55
zanebfair enough :)15:55
ttxand we'll discuss it again at the release meeting tonight15:55
zanebok15:55
ttxLast thing I had is the provisional slot allocation for summit. Looks like you could get 7 scheduled sessions and a full day of meetup15:56
ttx(compared to 8 slots in ATL)15:56
zanebthat sounds really good15:56
ttxyou get a lot because your allocation was a bit behind compared to your activity15:56
zanebyeah, it's surprisingly busy around here ;)15:57
ttx(you are more active than Cinder but had 3 less slots)15:57
zanebI'm particularly looking forward to the day of meetup15:58
ttxanything you'd like to flag release-wise ? Any topic for the meeting today ?15:58
zanebnope, can't think of anything15:59
ttxok great, talk to you later15:59
ttxSergeyLukjanov, mestery: you can go now if you're around15:59
zanebthanks ttx15:59
*** SlickNik has joined #openstack-relmgr-office16:02
ttxSlickNik: ready when you are16:04
*** markwash__ has joined #openstack-relmgr-office16:04
ttxor markwash__ can beat you16:04
ttxsince 6pm is his slot16:04
SlickNiko/16:05
ttxgoing once16:05
ttxmarkwash__: going twice16:05
ttx#topic Trove16:05
ttxhttps://launchpad.net/trove/+milestone/juno-rc116:05
ttx33 bugs left targeted16:06
SlickNikLooked at all the bugs we have, and spent some time triaging the criticals into Juno, and the rest out.16:06
ttx33 is still way to much, I bet all those are not release blockers16:07
ttxany chance you could refine that list so that it only contains release blockers ?16:07
SlickNikAgreed — not all of them are.16:07
ttxand use a tag for the nice-to-fix-in-Juno ?16:07
ttxtaht way we can trigger a RC1 when we are done with the release blockers16:07
ttxideally this week, or early in the next16:08
SlickNikWill do that this week.16:08
SlickNikbtw, didn't know Launchpad did tags.16:08
ttxok, I'll be in touch later this week to see if we can push a tag16:08
ttxso if you could cull the list before then, that would be awesome16:09
ttxDo you need to cut another troveclient release before Juno release ?16:09
SlickNikI'll plan on spending some time to do that today.16:09
ttxor is 1.0.7 good enough16:09
ttxIf you do, the deadline for that was last Friday, unless you got some regression in :)16:10
SlickNik1.0.7 is good enough — it's pretty recent (I think a week and a half ago)16:10
ttxack16:10
SlickNikIt has all the juno-3 feature bps done.16:10
ttxThat's all I had release-wise. Any red flag you'd like to communicate ?16:10
ttxany topic for the meeting later ?16:10
SlickNikSad that we couldn't get the juno-3 functionality into horizon though. :(16:11
ttxcan't get everything16:11
SlickNikYup, understand.16:11
SlickNikAnd it'll come in Kilo16:11
SlickNik:)16:11
ttxAs far as design summit is concerned, looks like you could get 4 scheduled slots and a half-day meetup (compared to 6 scheduled slots in ATL)16:11
ttxso slight more time oevrall, but less scheduled slots (like everyone)16:12
ttxSlickNik: anything else ?16:13
SlickNikCool, are you planning on drawing up a tentative schedule for the slots and posting it on the wiki like you did last time?16:13
SlickNikThat was very helpful.16:13
ttxSlickNik: yes, waiting on some feedback before I can do that16:13
SlickNikOkay, sounds good.16:14
ttxTripleO needs to tell me if they eed scheduled slots or if they would rather have a full-day meetup instead16:14
ttxneed*16:14
SlickNikThat's all I had. Thank you ttx!16:14
ttxSlickNik: ok then, ttyl16:14
ttxmarkwash__: around?16:14
markwash__ttx hi there16:14
ttx#topic Glance16:14
ttxhttps://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging is still open16:15
ttxor appears to be16:15
ttxIt's time to close all FFEs I'm afraid16:15
ttxtime well passe16:15
ttxdd16:15
ttxwhat was there left ?16:15
markwash__just https://review.openstack.org/#/c/116626/816:16
markwash__which looks fine to land, unless you think its too too late16:16
ttxlet me look at it16:16
ttxno need for https://review.openstack.org/#/c/117204/ ?16:16
ttxmarkwash__: 116626 is only log info level changes ?16:17
markwash__ttx, actually sorry I spoke a little too soon16:17
markwash__I guess we should just defer16:18
ttxOK, I'll let you -2 the remaining reviews16:18
ttxkilo opens in a few days now16:18
ttxI'll mark the BP deferred16:18
markwash__thanks16:18
ttxOK, so I see no release blocker on that page16:19
markwash__I'm a little scared16:19
markwash__but its accurate TMK16:19
ttxdoes that mean you're ready for RC1 tag, or that you didn't go through all the bugs to spot RC ones yet ?16:19
ttxhmm, ok16:20
ttxmarkwash__: maybe do a last pass on those and if still none, we could tag tomorrow or Thursday16:20
markwash__will do16:20
ttxhttps://bugs.launchpad.net/glance/+bug/1366515 could be added, maybe16:20
ttxwith maybe https://review.openstack.org/#/c/119613/16:21
ttx(https://bugs.launchpad.net/glance/+bug/1366503)16:21
ttxOK... anything else release-related ?16:22
markwash__not from me16:22
ttxLooking at design summit, Glance would get 4 scheduled sessions and a half-day meetup (compared to 5 scheduled sessions in ATL)16:23
ttxmarkwash__: do we have candidates for Glance PTL position already ?16:23
markwash__ttx: I was just taking a look at that, and so far no16:24
markwash__I imagine 4 sessions and the meetup will be sufficient16:25
ttxmarkwash__: ok16:25
markwash__based on the past sessions16:25
ttxmarkwash__: talk to you later then !16:25
markwash__sayonara16:25
ttxmestery, SergeyLukjanov: time now for one more16:26
ttxfirst come first served16:26
SergeyLukjanovttx, hey16:27
ttx#topic Sahara16:27
SergeyLukjanovttx, if you're able16:27
SergeyLukjanov#link https://launchpad.net/sahara/+milestone/juno-rc116:28
ttxSo we need to close all remaining FFEs now16:28
ttxtime has passed16:28
ttxIf I remeber correctly those were technical FFEs though16:28
SergeyLukjanovheh, I forget to update statuses16:28
ttxi.e. one was actually done but you kept it open to track -extra work16:28
SergeyLukjanovboth are implemented16:28
ttxand the other was doc16:28
ttxok16:28
ttx11 bugs on the RC list16:29
ttxwould be good to refine to releae blockers16:29
ttxI suspect the "undecided" unassigned one isn't16:29
SergeyLukjanovttx, most of the are doc ones16:29
ttxs othose are more nice-to-have than release blockers, right ?16:30
ttxmaybe use a tag to track doc nice-to-haves for Juno release16:31
ttxand keep the list for true release blockers16:31
ttxso that we know how far we are16:32
ttxideally we would tag thiws week, or before Tuesday next week16:32
SergeyLukjanovI think we're able to have a tag later this week16:32
SergeyLukjanovwe have only several blockers16:32
ttxdo you need to tag a client release to catch up with final oslo versions ?16:33
SergeyLukjanovI will cleanup the list and share you the list of blockers16:33
SergeyLukjanovttx, yup16:33
ttxok, would be good to do it asap16:33
SergeyLukjanovttx, it'll be with only one change - oslo versions update16:33
SergeyLukjanovI will do it today16:33
ttxright16:33
SergeyLukjanovdo we need to bump version in global req?16:33
ttxthat's all I had releasewise16:33
ttxSergeyLukjanov: no16:33
SergeyLukjanovttx, ack16:34
ttxnot unless that fixes a critical bug somewhere16:34
SergeyLukjanovok16:34
ttxLooking at the design summit, Sahara would get 5 scheduled sessions and a half-day meetup (compared to 7 sessions in ATL)16:34
SergeyLukjanovso, action items on me - release sahara client w/ updated oslo libs and cleanup list of issues that are blockers for release, mark doc issues with tag16:34
ttxso more time overall, but less scheduled slots.16:35
SergeyLukjanovttx, that's great16:35
SergeyLukjanovttx, meetup time will make us able to discuss internalls much better than always16:35
ttxagree on actions. I'll be in touch for a potential RC1 tag later this week if you make good progress16:35
ttxanything for meeting tonight ?16:36
SergeyLukjanovnote: we have several sahara-related fixes in horizon still on review16:36
SergeyLukjanovbut it's not a topic for meeting I think16:36
SergeyLukjanovso, I think nothing more from my side16:37
ttxmaybe just make sure they stay on their RC1 list16:37
ttxok, ttyl16:37
SergeyLukjanovthank you16:37
ttxmestery: i'll ping you around 19:30 UTC for more sync16:37
* ttx takes a break16:37
*** markwash__ has quit IRC16:48
*** david-ly_ is now known as david-lyle17:04
*** markwash__ has joined #openstack-relmgr-office18:06
*** arnaud has joined #openstack-relmgr-office18:18
*** Azher has joined #openstack-relmgr-office18:25
dhellmannttx: I've cleaned up all of the oslo next-juno milestones (renamed the one for oslo-incubator and closed all of the others). The juno series is still open for all and I don't know how to close that, but if you let me know I can do it.18:31
*** arnaud has quit IRC18:32
*** arnaud has joined #openstack-relmgr-office18:33
sdaguettx: the requirements readme from this morning is updated - https://review.openstack.org/#/c/116708/18:43
SergeyLukjanovttx, sahara client w/ fresh req just released18:56
*** johnthetubaguy is now known as zz_johnthetubagu19:02
mesteryttx: I'll be here, thanks!19:08
*** flaper87|afk is now known as flaper8719:14
*** markwash__ has quit IRC19:16
*** Azher has quit IRC19:25
*** markwash__ has joined #openstack-relmgr-office19:26
ttxmestery: around?19:35
mesteryttx: o/19:35
ttx#topic Neutron19:35
ttxso you asked, when is RC119:36
ttxideally some time this week19:36
ttxif not, early next week19:36
mesteryOK, makse sense19:36
ttxso the goal is to cut down the buglist so that it only contains release blockers19:36
mesteryYes, I've been working on that19:37
mesteryI should have it under control by tomorrow19:37
mesteryOr even toinight19:37
ttxYou're fine with 2.3.9 as client release ?19:38
mesteryYes, unless someone tells me otherwise19:38
ttxok, anything else about release ?19:38
ttxI'll be in touch later this week to see if we can tag19:38
mesteryNothing at this time nope19:39
mesteryThanks ttx!19:39
ttxOK, summit-wise, Neutron will get a full day of meetup + 9-11 scheduled sessions19:39
ttxso you can start planning19:39
mesteryOK, that sounds about perfect19:39
mesteryWe are doing that on an etherpad19:39
ttxok great19:40
mesteryhttps://etherpad.openstack.org/p/kilo-neutron-summit-topics19:40
ttxmestery: anything else ?19:40
mesteryttx: That's it, thanks!19:40
ttxalright then.19:40
ttx#endmeeting19:40
openstackMeeting ended Tue Sep 23 19:40:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-23-08.02.html19:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-23-08.02.txt19:40
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-09-23-08.02.log.html19:40
mesteryGood night ttx19:40
ttxunfortunately, not yet :)19:40
mestery:)19:41
*** arnaud has quit IRC20:27
*** SlickNik has left #openstack-relmgr-office20:38
*** markwash__ has quit IRC20:46
*** markwash__ has joined #openstack-relmgr-office20:48
*** flaper87 is now known as flaper87|afk22:07
*** markwash__ has quit IRC22:40
SergeyLukjanovttx, david-lyle, here is an etherpad with patches we need in J in Horizon22:46
SergeyLukjanovttx, david-lyle https://etherpad.openstack.org/p/sahara-horizon-remaining-changes-for-juno22:46
SergeyLukjanovttx, david-lyle, now all of them have a bug22:47
*** markwash__ has joined #openstack-relmgr-office22:50
SergeyLukjanovttx, I've cleaned up the rc1 launchpad page for sahara - https://launchpad.net/sahara/+milestone/juno-rc122:51
*** markwash__ has quit IRC22:54
*** dansmith has quit IRC23:06
*** dansmith has joined #openstack-relmgr-office23:10
david-lyleSergeyLukjanov: all have been targeted to RC-123:12
*** david-lyle has quit IRC23:20
*** dhellmann has quit IRC23:21
*** dhellmann has joined #openstack-relmgr-office23:21
*** david-lyle has joined #openstack-relmgr-office23:21
SergeyLukjanovdavid-lyle, thank you, that23:24
SergeyLukjanovthat's great23:24
*** david-lyle has quit IRC23:26

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