Tuesday, 2014-07-15

*** Azher has joined #openstack-relmgr-office02:41
*** markwash has joined #openstack-relmgr-office02:55
*** jgriffith has quit IRC03:12
*** anteaya has quit IRC03:12
*** morganfainberg has quit IRC03:12
*** Azher has quit IRC03:12
*** zaneb has quit IRC03:12
*** zz_johnthetubagu has quit IRC03:12
*** SergeyLukjanov has quit IRC03:12
*** mikal has quit IRC03:12
*** ttx has quit IRC03:12
*** russellb has quit IRC03:12
*** dolphm has quit IRC03:12
*** stevebaker has quit IRC03:12
*** notmyname has quit IRC03:12
*** mestery has quit IRC03:12
*** jraim has quit IRC03:12
*** ChanServ has quit IRC03:12
*** Azher has joined #openstack-relmgr-office03:20
*** jgriffith has joined #openstack-relmgr-office03:20
*** mestery has joined #openstack-relmgr-office03:20
*** morganfainberg has joined #openstack-relmgr-office03:20
*** zaneb has joined #openstack-relmgr-office03:20
*** russellb has joined #openstack-relmgr-office03:20
*** zz_johnthetubagu has joined #openstack-relmgr-office03:20
*** SergeyLukjanov has joined #openstack-relmgr-office03:20
*** mikal has joined #openstack-relmgr-office03:20
*** ttx has joined #openstack-relmgr-office03:20
*** notmyname has joined #openstack-relmgr-office03:20
*** stevebaker has joined #openstack-relmgr-office03:20
*** dolphm has joined #openstack-relmgr-office03:20
*** jraim has joined #openstack-relmgr-office03:20
*** anteaya has joined #openstack-relmgr-office03:20
*** ChanServ has joined #openstack-relmgr-office03:23
*** dickson.freenode.net sets mode: +o ChanServ03:23
*** markwash has quit IRC03:38
*** zz_johnthetubagu is now known as johnthetubaguy07:44
* ttx grabs coffee, brb07:58
* johnthetubaguy copies ttx07:59
ttxmikal: around?08:02
* johnthetubaguy waves, but has little to say08:03
ttxlet's wait a bit more08:04
ttxjohnthetubaguy: we'll have a quick discussion at 09:00 UTC if mikal is still missing. Want to see if he got the wrong hour (happens to me too)08:43
johnthetubaguyttx: sure, sounds good08:44
ttxjohnthetubaguy: ok, I guess he won't join, let's quickly discuss state09:01
ttx#startmeeting ptl_sync09:01
openstackMeeting started Tue Jul 15 09:01:35 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
johnthetubaguyttx: sure09:01
openstackThe meeting name has been set to 'ptl_sync'09:01
ttx#topic Nova09:01
ttx#link https://launchpad.net/nova/+milestone/juno-209:01
ttxAbout 2 thirds of it is under review09:02
johnthetubaguyyeah, lots needs code review I guess, which is good and bad :)09:02
johnthetubaguyI guess we should start punting stuff to juno-3 soon09:03
ttxserver-count-api is marked Not started, sounds like a good candidate for punting09:03
ttxjohnthetubaguy: yes, punt early... and try to convert those that are 99% there09:03
johnthetubaguyyeah, the slow and not-started should probably all get punted09:03
johnthetubaguyyeah, how long do we have now its just over a week I guess?09:03
ttxyeah, about one week left, +0..2 days09:04
ttxbut it's better to let that 0..2 handle unexpected gate delays09:04
ttxso I'd expect anything not approved in one week to be deferred09:05
johnthetubaguyright, good point09:05
ttx#info Punt early, especially Not started / Slow progress09:05
ttx#info Concentrate on those that are almost there, to increase completion rate09:06
johnthetubaguysounds good09:06
johnthetubaguythanks, will try sort that out09:06
ttxjohnthetubaguy, mikal: note that russellb will be handling the J2 tag -- please communicate with him next week09:06
johnthetubaguyand will send a rallying call around reviews09:06
johnthetubaguyttx: ah, cool, thanks for the heads up09:07
ttxHe will probably skip the 1:1 usual times and just talk to you09:07
johnthetubaguyyeah, I guess we need a more US friendly slot next week09:07
johnthetubaguyI will try seek out mikal and chat to him about that09:07
ttx#info spec backlog at 10509:08
ttxjohnthetubaguy: remind me when is your SPD/SAD ?09:08
johnthetubaguyyeah, so in theory we should −2 all of those now09:08
johnthetubaguythe date has passed, but I feel bad about the review backlog, so haven't really closed it off as such yet09:08
johnthetubaguywe had a communication issue someone09:09
ttxjohnthetubaguy: right... trick is, until it's clearly closed, people will continue to spend time on them, which kind of defeats the purpose of those deadlines09:09
johnthetubaguylots of reviewers seemed to have thought the proposal freeze date was the merge freeze date, despite all emails saying the opposite09:09
johnthetubaguyttx: yeah, I have been trying to catch up with mikal but failing so far09:09
johnthetubaguyreally I want to understand what we are delaying, and go through that backlog, but not had chance since the freeze date, so there is an action on me too there09:10
ttxDo you have anything for the cross-project meetign agenda later today?09:11
johnthetubaguyin the nova meeting, there was push back on the freeze before we decide about J, and we decided to discuss that at the midcycle, so I kinda punted that09:11
johnthetubaguyI don't think anything major has come up09:11
johnthetubaguyI would like to get more discussion of blueprints we are doing for "consistency" there, like the tagging API, just for visibility09:12
johnthetubaguybut not really chased down a list of those things, that might be the only one so far09:12
johnthetubaguythe big elephant in the room is the API.NEXT work09:12
johnthetubaguywe still haven't actually agreed on a plan09:12
ttxjohnthetubaguy: ok.. we should probably talk again before the end of the week, when the j2 list will have been... sanitized09:12
johnthetubaguymikal is trying to chase down some agreement09:12
johnthetubaguyttx: cool, sounds good09:12
johnthetubaguythats all from me really09:12
ttxack, talk to you later09:13
*** ChanServ has quit IRC09:55
*** jgriffith has quit IRC09:55
*** anteaya has quit IRC09:55
*** morganfainberg has quit IRC09:56
*** Azher has quit IRC09:56
*** zaneb has quit IRC09:56
*** johnthetubaguy has quit IRC09:56
*** SergeyLukjanov has quit IRC09:56
*** mikal has quit IRC09:56
*** ttx has quit IRC09:56
*** russellb has quit IRC09:56
*** dolphm has quit IRC09:56
*** stevebaker has quit IRC09:56
*** notmyname has quit IRC09:56
*** mestery has quit IRC09:56
*** jraim has quit IRC09:56
*** dhellmann has quit IRC09:56
*** sdague has quit IRC09:56
*** devananda has quit IRC09:56
*** Kiall has quit IRC09:56
*** dhellmann has joined #openstack-relmgr-office10:03
*** ChanServ has joined #openstack-relmgr-office10:03
*** anteaya has joined #openstack-relmgr-office10:03
*** jraim has joined #openstack-relmgr-office10:03
*** dolphm has joined #openstack-relmgr-office10:03
*** stevebaker has joined #openstack-relmgr-office10:03
*** notmyname has joined #openstack-relmgr-office10:03
*** ttx has joined #openstack-relmgr-office10:03
*** mikal has joined #openstack-relmgr-office10:03
*** SergeyLukjanov has joined #openstack-relmgr-office10:03
*** johnthetubaguy has joined #openstack-relmgr-office10:03
*** russellb has joined #openstack-relmgr-office10:03
*** zaneb has joined #openstack-relmgr-office10:03
*** morganfainberg has joined #openstack-relmgr-office10:03
*** mestery has joined #openstack-relmgr-office10:03
*** jgriffith has joined #openstack-relmgr-office10:03
*** Azher has joined #openstack-relmgr-office10:03
*** dickson.freenode.net sets mode: +o ChanServ10:03
*** sdague has joined #openstack-relmgr-office10:03
*** Kiall has joined #openstack-relmgr-office10:03
*** devananda has joined #openstack-relmgr-office10:03
*** Azher has quit IRC10:59
*** eglynn has joined #openstack-relmgr-office11:43
eglynnttx: ready when you are11:45
ttxeglynn: o/11:45
ttx#topic Ceilometer11:45
ttx#link https://launchpad.net/ceilometer/+milestone/juno-211:46
ttxStill a long way to go in one week11:46
ttxdo you think all of those are still likely to make it?11:46
eglynnyeah, I've actually got 3 more specs that look likely to land11:46
eglynnVPNaaS: https://review.openstack.org/9578111:47
eglynnFWaaS: https://review.openstack.org/9577911:47
eglynnSNMP++: https://review.openstack.org/10411311:47
eglynnVPNaaS and FWaaS patches should land11:47
eglynnon SNMP, Lianhao isn't sure but is striving to get it in11:47
ttxthe code review has been going on in parallel ?11:47
eglynnthe other question mark is on the grenade resource surviviability11:48
eglynnthe javelin2 stuff in tempest is looking like a non-solid basis for that11:48
ttxhmm. I feel like we are not getting the clarity we expected from the specs process, if specs fly below radar and blueprints just appear on the final week11:48
eglynnmtreinish characterizes it a WIP11:48
ttxeglynn: do you think this late appearance is just due to spec backlog, or more a permanent feature of using -specs?11:49
eglynnyeap, BTW the specs process is being "subverted" somewhat by folks just coding in parallel11:49
eglynnI think it's partially due to the process still being bedded in11:49
eglynnwe will have to strictly prioritize reviewing efforts next time round11:50
eglynni.e. don't go off reviewing loads of code patches if there are pending reviews in the specs repo11:50
eglynnttx: are you seeing similar patterns on other projects?11:50
ttxok -- if that trends is also present in other projects we might have to have a discussion about that11:50
ttxI'll see by the end of the day11:50
ttxNova and Neutron kind of avoid that with the specs freezes11:51
ttxeglynn: so you may have 3 more specs appearing on that page11:51
eglynnyeah, for ceilo I feel that'll have to be more a specs slush this time round11:51
eglynnyes, two at the very least, most likely 311:51
ttxand you think everything can make it in one week?11:52
ttxthe 5 already there + 311:52
ttxor are you likely to defer some of those 5?11:52
eglynneverything should land I think except possibly SNMP++ and grenade11:52
eglynngrenade is the first one I'll bump11:53
eglynnprobably by EoD tmrw11:53
eglynnother big concern on my radar is this test timeout that I mentioned before ... https://bugs.launchpad.net/bugs/133619311:53
eglynnsileht is not yet back, so I've asked nsaje to look at it11:53
eglynn(nsaje just started as a short-term contractor with Red Hat)11:54
ttxYou also have https://bugs.launchpad.net/bugs/1327076 targeted, with no assignee11:54
eglynnNejc has a definite line of inquiry on the oslo-messaging side11:54
ttxis anyone working on that?11:54
eglynnmeant to assign that to myself11:55
eglynndone so now11:55
ttx#info 3 more blueprints expected to appear on the j2 plans as their specs get approved (code been developed in parallel)11:55
ttxeglynn: in other news, note that russellb will be doing the tag next week11:55
eglynnand in other other news, I'll be taking some half days off next week for family reasons11:56
ttx#info Spec backlog: 2711:56
eglynnbut will be contactable and making all my scheduled meetings11:56
ttxthere won't be 1:1s next week, at least not at usual times, and without me11:57
eglynnttx: so same process as j1, declare to russellb when ready to tag?11:57
russellbwe just need to sync on when you think j2 is ready11:57
russellbyep :)11:57
eglynnrussellb: cool :)11:58
ttxeglynn: yes, he will probably chase you down to make sure the blueprints are aligned11:58
* eglynn prepares to be chased ... ;)11:58
russellbgold stars awarded if no chasing required11:58
ttxeglynn: anything you wanted to add to project meeting agenda for today?11:58
ttxrussellb: o/11:59
eglynnttx: nope that's all from me11:59
ttxeglynn: cool, thx!11:59
eglynnlaters :)11:59
ttxSergeyLukjanov: around?11:59
ttxdhellmann: if you're already available, you can steal Sergey's slot12:01
dhellmannttx: here12:02
ttxok, let's do this12:02
ttx#topic Oslo12:02
dhellmannyou might want to hit reload, I've been updating bps this morning12:02
ttxdhellmann: I no longer look in advance :)12:03
ttxthis looks good12:03
ttxThe last 3 are still likely to land ?12:03
dhellmannwe have a few reviews for oslo.utils, so it might be tight but none of that work is really big12:04
dhellmannthe infra team is in germany at their sprint, so I don't know about the test job changes, that might have to wait for after j212:04
ttxAnything j2-worthy flying below radar, like a specs almost there with code reviewed in parallel?12:05
dhellmannI think the configfilter wrapper is actually done, but I want to check with markmc before closing that one12:05
ttxhttps://launchpad.net/oslo.messaging/+milestone/juno-2 doesn't have blueprints in it anymore12:06
ttx2 in j312:06
dhellmannthose are new approvals12:06
dhellmannI wonder what happened to the others in j212:06
ttxdhellmann: russellb will push the tag for oslo-incubator and mark the milestone "released" for oslo.messaging next week, so he wil be your point of contact that week12:07
ttxrussellb: fwiw I usually do oslo when everything else is out of the way12:07
ttxsince it's not really blocking the j2 announcements12:08
russellbdhellmann: o/12:08
russellbttx: makes sense12:08
dhellmannrussellb: o/12:08
ttxdhellmann: the release scripts now should know how to handle oslo, so it will be a lot less manual12:08
ttxand thanks for tagging that rootwrap alpha12:09
dhellmannno trouble at all12:10
dhellmannI need to automate the email step from that process :-)12:10
ttx#info spec backlog: 1012:10
dhellmannmaybe I could write a script for infra to do it12:10
dhellmannI can't find those missing oslo.messaging blueprints :-/12:10
ttxdhellmann: yeah, we need to work on streamlining library announcements12:11
ttxhave a clear source to find them12:11
dhellmannI'll bring it up at the meeting this week and see if anyone wants to take that on12:11
dhellmanna clear source to find the release notices, or the libraries?12:12
ttxdhellmann: it's not just oslo, client libs should follow it as well12:12
ttxrelease notices12:12
ttxdhellmann: only trick is.. raw git changelog really fails to highlight stuff12:12
dhellmannyeah, the client library announcements should go to python-announce, too12:12
SergeyLukjanovttx, I'm sorry, /me been on internal meeting, now ready12:12
dhellmannyeah, true12:12
ttxdhellmann: I've been thinking about it from a Storyboard perspective. and the role of Launchpad in building "release pages"12:13
dhellmannlooking at the open specs, I really only anticipate the oslo.cache work and service-status-interface to have a high likelihood of seeing any real work this cycle12:13
ttxWe can replicate that "feature" in Storyboard, but it's a bit out of the pure "task tracking" function12:13
ttxwe could use smarter commit messages and leverage git changelog to build a list of features and bugs12:14
ttxand security fixes12:14
dhellmannyeah, it seems like we will have the information available between git, specs, and blueprints, but we have to tie it all together12:14
ttxbut not sure everyone would follow the rules12:15
dhellmanna couple of jobs back we had a special field in the bug tracker for "release note" that could be updated after the ticket was closed so the doc team could generate notes automatically12:15
ttxso if we can build something good for oslo libraries, we are likely to reuse that for releases and milestones12:15
russellbif there's enough obvious benefit to the rules (awesome auto release summary) then that would provide motivation12:15
ttxrussellb: it's just that in LP, the milestone field actually has two purposes12:16
dhellmannmaybe a field like that in storyboard would work, and the person doing the release could update it before generating the release?12:16
ttxit's when you want to deliver it, then it's when you did deliver it12:16
* russellb nods12:16
ttxand we have plenty of scripts to try to gover for that slight gap in meaning12:16
ttxthe ultimate source of what's IN the release is really the git thing, not what LP or Storyboard thinks is in there12:17
dhellmannwon't storyboard have the git commit ids?12:17
ttxdhellmann: it will probably have some, but just like LP it will miss some work12:18
ttxthat just landed without ref12:18
ttxanyway, separate discussion12:18
dhellmannoh, I thought we were going to add items to storyboard automatically12:18
dhellmannmaybe that was nixed12:18
ttxdhellmann: no, it's still a possibility... but that also requires people to ref a storyboard ID in the commit message12:19
dhellmannah, true12:19
ttxso if you add rules to commit messages...12:19
ttxanyway, offtopic12:19
dhellmannyeah, sorry :-)12:20
ttxdhellmann: anything you wanted to add to meeting agenda for today?12:20
dhellmannnot today12:20
ttxSergeyLukjanov: still around?12:20
ttxdhellmann: ok, ttyl12:20
SergeyLukjanovttx, yup12:20
ttx#topic Sahara12:20
SergeyLukjanov#link https://launchpad.net/sahara/+milestone/juno-212:20
ttxLooks pretty good12:20
SergeyLukjanovso, everything looks good12:21
ttxAt this point, it's good if targeted bugs have assignees12:21
SergeyLukjanovttx, ok, I'll ask folks to grab the issues12:21
SergeyLukjanovttx, there is some good progress on merging sahara-dashboard to horizon12:21
SergeyLukjanovttx, only 4 changes left12:21
ttxSergeyLukjanov: is that blueprint list complete, or do you have things to add there ?12:21
ttxSergeyLukjanov: how many were there originally?12:22
SergeyLukjanovttx, it depends on specs review, probable +1-212:22
SergeyLukjanovttx, and I12:22
SergeyLukjanovttx, and I'll check that we're not missed some already done work12:23
ttxok, good12:23
ttxSo you have code that has been developed in parallel with specs and is rady for review as soon as the spec is approved?12:23
SergeyLukjanovttx, yup, we have several such specs12:24
ttxSergeyLukjanov: russellb will be handling the tag next week12:24
SergeyLukjanovttx, ack12:24
ttxthere won't be formal 1:1s at the usual times12:24
ttx#info spec backlog: 412:24
ttx#info maybe one or two blueprints will be added in j212:25
russellbSergeyLukjanov: so let's just stay in touch, and just let me know when you feel j2 is ready to go12:25
SergeyLukjanovrussellb, okay, I think it'll be July 22-2412:25
ttxand russellb will chase you down if it appears you are missing the launch window12:25
SergeyLukjanovrussellb, for sahara we're usually ready in -1..-2 days before the dev milestone12:26
russellbthat's when i'll start looking at projects and tagging when ready12:26
ttxrussellb: so yeah, most of the job is to maximize the chances that everything happens in the same time window, be aligning the milestone page content with what is still likely to make it in time12:27
ttxif you just check on Tuesday you get a very long list and it's hard to cut. By removing things that have no chance of making it, you actually increase the chances that the rest will make it12:28
SergeyLukjanovttx, I'd like to add just reminder for today's meeting re merging -dashboard to horizon12:28
SergeyLukjanovttx, nothing specific to discuss12:28
ttxbut it's hard, because nobody really knows what will make it or miss12:28
ttxSergeyLukjanov: ok12:29
SergeyLukjanovttx, thx12:29
SergeyLukjanovttx, I'm usually moving all < High to the next milestone on Tue12:29
ttxSergeyLukjanov: good :)12:30
ttxSergeyLukjanov: that's all I had, thanks!12:30
SergeyLukjanovttx, thank you12:30
jgriffithttx: lemme know if you have time to go early13:04
ttxjgriffith: I do13:04
ttx#topic Cinder13:04
*** eglynn has quit IRC13:04
ttxjgriffith: I suspect a few of those definitely won't make it in one week13:05
jgriffithttx: Nope, probably not13:05
ttxjgriffith: so defer as soon as you're relatively sure they won't make it13:05
jgriffithttx: will do13:05
ttxon the other hand, is theer anything that might get added at the last minute?13:06
jgriffithttx: I don't plan on adding anything that doesn't have a review ready/complete at this point13:06
ttxjgriffith: but nothing comes to mind?13:06
jgriffithThere is likely to be a few specs pop up, but they're J3 or untargetted until I have completed code13:06
ttx#info Spec backlog: 2813:06
jgriffithttx: well, boat load of drivers13:07
jgriffithttx: problem is I don't see anybody with anything "close"13:07
ttxjgriffith: keep on refining. russellb will be your host for J2 tagging13:07
jgriffithttx: k13:08
jgriffithlucky russellb13:08
ttxjgriffith: did you have anything for the meeting today?13:08
jgriffithrussellb: that was only two... you don't appear until three13:08
jgriffithttx: nope13:09
jgriffithttx: just need to get these features buttoned up13:09
ttxjgriffith: we'll skip 1:1s next week, since I won't be arond13:09
russellbjgriffith: i'll be in touch early next week to identify when j2 is ready13:09
jgriffithttx: yeah... see ya in Portland13:09
ttxah cool, see you there!13:09
jgriffithrussellb: I'll be on and off IRC but I'll be sure to synch up with you13:10
russellbjgriffith: perfect.  feel free to drop an email if that's easier for you13:10
jgriffithrussellb: sounds good13:10
ttxrussellb: i can physically push him to connect if needed13:10
russellbjgriffith: you've been through this several times, so i know you know the drill :)13:10
russellbttx: wooo13:10
jgriffithttx: haha!!  Literally even13:10
jgriffithrussellb: should be smooth, just getting everything through13:11
russellbsounds good13:11
ttxjgriffith: ok, ttyl!13:11
jgriffithttx: cya.. thanks13:12
ttxrussellb: the autokick script dramatically reduced the need for those 1:1s13:12
ttxalthough I guess talking once a week with people can't hurt13:13
russellbttx: yep, i think it's good to make sure these things stay top of mind week to week13:13
*** johnthetubaguy is now known as zz_johnthetubagu13:36
*** zz_johnthetubagu is now known as johnthetubaguy13:46
ttxdolphm: around?14:15
dolphmttx: o/14:15
ttx#topic Keystone14:15
ttxLooks reasonable14:16
ttxdolphm: any possible last-minute addition, fresh from -specs approval?14:16
dolphmwe did approve ~5 specs last week at our hackathon - i don't *think* any of them will be implemented in j2 though14:17
ttx#info spec backlog: 1814:17
ttxdolphm: russellb will handle J2 tagging14:17
ttxand we'll skip the usual 1:1s next week14:18
russellbi'll be in touch next week to confirm when J2 is ready14:18
russellbfeel free to ping me anytime to discuss14:18
dolphmjson-home is a spec we approved last week & has an implementation available - if it's close to being ready, that one would be an easy j2 target14:19
dolphmbut that looks like the only one14:19
dolphmttx: russellb: tagging sounds good14:19
ttxdolphm: any agenda addition for the meeting today?14:19
dolphmttx: a quick announcement regarding keystoneclient.middleware.auth_token -> keystonemiddleware.auth_token14:19
dolphmlet me do an #info here..14:20
ttxyes, #info it and feel free to insist on it when we go over the 1:1s notes at the meeting14:20
dolphm#info keystoneclient.middleware.auth_token has been split into a new package, keystonemiddleware.auth_token - we'll need to update every project's default pipeline to adopt the new middleware14:21
ttxdolphm: you could use a bug number to track all corresponding tasks14:21
dolphm#info keystoneclient.middleware.auth_token will continue to receive security updates14:21
ttxthat will facilitate making sure all bases are covered14:22
dolphmmorganfainberg: do we have a bug number to track the above change? ^14:22
ttxdolphm: ok, that's all I had14:22
dolphmme too - i'll make sure there's a bug if not14:23
ttxdolphm: ok, ttyl14:24
russellbdolphm: doing something to enable backwards compat for that change?14:30
*** david-lyle has joined #openstack-relmgr-office14:30
dolphmrussellb: yes, we're leaving keystoneclient.middlware.auth_token alone :)14:31
ttxdavid-lyle: o/14:31
dolphmrussellb: we can't import from keystonemiddleware.auth_token because that would create a circular dep14:31
russellbdolphm: cool.  could eventually make it a trivial import of the new thing.14:31
david-lylettx: o/14:31
russellbdolphm: ah.14:31
* russellb shuts up to clear the room for david-lyle's time14:31
ttx#topic Horizon14:31
ttx37 blueprints left14:32
ttxLots of them in review14:32
david-lylealmost all are up for review14:32
david-lylesomeone added another after I cleaned up yesterday14:33
david-lyleI'll boot that14:33
ttxdavid-lyle: i would suggest focusing on those that are almost there, to maximize the number of completed blueprints14:33
ttxalso merging early is a good idea as I expect the load on gate to ramp up pretty soon14:34
david-lylewe have been, the Sahara one has been the top priority and eating up a lot of review bandwidth14:34
david-lylea lot14:34
ttxdavid-lyle: yes, Sergey was mentioning good progress on that front14:34
david-lylewe have several more of the Sahara patches that are very close14:34
ttxalso don't hesitate to defer stuff that's unlikely to make it, that can help in prioritizing as well14:35
SergeyLukjanovdavid-lyle, thank you for bumping the sahara reviews prio!14:35
ttxyes, https://blueprints.launchpad.net/horizon/+spec/mac-learning-knobs was just added14:35
ttxrussellb: Nb: Horizon is not using autokick.py yet14:35
david-lylesure, I did some paring yesterday and will get more status in the Horizon team meeting14:35
russellbttx: why not?14:35
ttxrussellb: so it is vulnerable to random additions by bystanders14:35
ttxrussellb: it's not using -specs14:36
ttxrussellb: so the blueprint is still the correct way to propose a feature14:36
russellband actually i think i missed what autokick.py was ...14:36
ttxrussellb: it's a script I have running (in the cloud!) that removes milestone targts for blueprints without a priority14:36
russellbttx: ah, cool.14:37
ttxso that we can use the priority field to also mean "approved"14:37
russellbttx: and that includes also checking for an approved spec or something?14:37
david-lylenow I want to move to a specs repo just for that14:37
ttxsince it's one of the very few LP restricts14:37
russellbor just that projects with specs repos have less people doing random LP edits14:37
ttxrussellb: no, random people just can't set the priority field. So when a spec is approved, you set priority and target milestone14:37
ttxif random people just set target milestone, the script will boot them off14:38
ttx(it's a workaround the fact that LP just lets anyone set the target milestone)14:38
russellbbut people could do that for a specs using project too presumably ..14:38
ttxrussellb: they could, but then there is no way for people to "propose" a feature14:39
ttxthe workflow for proposing features is to file a blueprint and set the target milestone. Then the PTL just triages all the undefined-priority BPs14:39
ttxrussellb: pretty sure you remember how much that is14:39
ttxhow much fun that is, I mean14:39
russellboh yes.14:40
russellbdavid-lyle: so the reason i'm around today is that i'm handling the J2 tag next week14:40
david-lylerussellb: excellent14:40
russellbdavid-lyle: so we'll need to stay in touch early next week to confirm when your J2 is ready to go14:40
david-lylesounds good14:40
ttxdavid-lyle: so yes, keep on refining the list14:40
david-lylewill do14:41
ttxdavid-lyle: any specific topic you wanted to discuss at meeting today?14:41
david-lylettx: no, I think we're set14:41
ttxdavid-lyle: ok, back to reviewing then :)14:41
ttxthat's a pretty impressive list of BPs14:42
david-lylettx: it's an honest living14:42
david-lylereviewing all day14:42
ttxmestery: ready when you are14:42
mesteryttx: o/14:42
ttx#topic Neutron14:43
mesteryI spent yesterday and this morning pruning this list a bit.14:43
ttxa bit late, but not completely crazy14:43
mesteryWe have a LOT of things in flight at the moment.14:43
mesteryttx: ++14:44
ttxthere are two "unknown" in there14:44
mesteryYes, I need to move one out to J3 and the other one I need to talk to the committer14:44
mesteryExpect those to be resolved within the hour14:44
ttxmestery: ok, just keep on refining, and merge those taht are nearly complete as soon as possible...14:45
mesteryttx: Yes sir, that's the plan, been working with the other cores on that this week.14:45
ttxmestery: as previously said, russellb will handle j2 tagging next week14:46
mesteryOK, cool!14:46
mesteryWill keep in contact with you over the next week russellb.14:46
russellbmestery: great14:46
ttxmestery: how is the SPD deadline working for you ?14:46
mesteryttx: SPD worked quite well, SAD also is going ok.14:47
mesteryI've spent hours pouring over specs, moving some to K, etc.14:47
ttxoh, you're past SAD now?14:47
* ttx checks14:47
mesterySAD is this weekend, almost quite literally14:47
ttxah ok14:47
mesteryBut, I'm premptively working to close out things before that.14:47
mesteryAnd narrowing thigns down.14:47
mesteryOverall, I've been happy with SPD/SAD, and would recommend it to other projects that are looking at the same sort of thing.14:48
ttxmestery: when do you plan to reopen specs for K? after feature freeze ? or at RC1 ?14:48
mesteryttx: I think closer to RC1 to try to focus people on J3 issues and bugs near the end of J.14:48
ttxmestery: do you still expect some late approvals to sneak into j2, or that would be definitely j3 material ?14:49
mesteryttx: I don't expect anything else to be added to J2.14:49
mesteryIt's all J3 from here on out.14:49
ttx#info no addition expected to j214:50
ttx#info spec backlog: 14014:50
ttxmestery: so we won't have our usual 1:1 discussion next week14:51
mesteryttx: Got it, have fun at OSCON!14:51
ttxwill try!14:51
ttxmestery: anything to add to meeting agenda for today?14:51
mesteryttx: Not much, if you want, I could talk about SPD/SAD since there weren't many projects which did this to my knowledge.14:52
mesteryOther than that, I'm good.14:52
ttxmestery: I already added a topic to discuss if specs is increasing or decreasing the predictability of features14:52
mesteryttx: perfect14:53
ttxand SPD/SAD definitely helps in that area, so on topic :)14:53
ttxmestery: ok, talk to you then14:53
mesteryttx: later!14:53
notmynamettx: ready whenever you are15:05
ttxnotmyname: on a call, will ping you as soon as I'm out of it15:23
ttxnotmyname: readynow15:27
notmynamettx: good morning15:27
ttx#topic Swift15:27
notmynamettx: I think all I've got is the gap analysis15:27
notmynamefor the TC15:28
ttxnotmyname: good reception for Swift 2.0.0 so far?15:28
notmynamettx: yes, I think so. several articles written. even had a new deployer come to us (swiftstack) with a specific use case for storage policies15:28
ttxnotmyname: we'll likely have that gap analysis on July 29 or August 5, unless the meeting is not cancelled next week15:29
* notmyname checks calendar15:29
ttxbut I expect OSCON will make us cancel it15:30
ttxWe'll see better when we discuss it today15:30
notmynamettx: the 29th I have an on-site customer meeting. unlikely to be available by meeting time (1pm pacific). the 5th I'm free15:30
notmynamealso, next week is good for me too, if the meeting happens15:31
ttxSounds good to me -- on Jul 29 we need to go through progress on the existing gap coverage plans anyway15:31
ttxnotmyname: so next week if that's happening, or August 5th15:31
notmynameI took the doc you sent me an filled out short answers (mostly "done" or "N/A")15:32
ttxnotmyname: ack15:33
notmynameshould I send my draft to you first to review? would that help anything go smoother in the meeting?15:33
ttxnotmyname: do you think you'll have one or two more juno releases ?15:33
ttxnotmyname: we can post the link to the etherpad in advance of that TC meeting15:34
ttxnotmyname: discussion usually quickly focuses on a few key points15:34
notmynamedoes juno RC start in september or october?15:34
ttxnotmyname: the etherpad lets us go fast on obvious stuff15:34
ttxFinal release October 1615:34
ttxRCs start last week of Sept15:35
ttxso an intermediary release would be ~ end of August15:36
notmynameok, I'll shoot for 2 releases then...ya, exactly that :-)15:36
notmynameie in about a month, and then another right at the RC15:36
ttxnotmyname: ack15:37
ttxnotmyname: that's all I had15:37
ttxanything you want to talk about at meeting today?15:37
notmynamegreat. me too. if you look over the etherpad, you'll see that there is one section with ??? as the answer15:38
notmyname* The lifecycle of resources managed by the project should be externalized15:38
notmyname  via notifications so that they can be consumed by other integrated15:38
notmyname  projects15:38
notmynameI don't know what that means15:38
notmyname(no I don't have anything to bring up in the meeting)15:38
ttxit might be a n/a in your case15:40
ttxI think what it's calling for is integration with ceilometer15:40
ttxbut you'll be able to raise it at that meeting15:41
notmynameok. that was covered in another question ("done"), but it almost sounds like some sort of queue/message bus/notification system15:41
ttxok, that's all I had15:41
notmynameme too15:43
ttx#info current plan is to shoot for another release before the final synced one, rough eta end of August15:43
ttxnotmyname: thanks!15:43
ttxzaneb: ready when you are15:43
ttx#topic Heat15:44
ttxzaneb: is that current ? makes it look like the bottleneck is development and not review in heat15:45
ttx(other projects have much more "needs code review" at this stage15:45
zanebthe bottleneck is that everyone is too busy reviewing to develop :D15:45
zanebI just changed the status on Randall's bp to 'needs code review'15:46
ttxzaneb: ok -- are all those still likely to get completed this week? Or is it time for early deferrals ?15:46
zanebmine probably should be deferred15:47
ttxzaneb: any last minute surprise likely to be added, or is that plan final?15:47
ttx#info spec backlog: 1715:47
zanebI can't imagine any additions at this stage15:48
ttx#info no last minute addition expected to j215:48
ttxyou ahve a number of unassigned bugs on the j2 target. I fear that if they are not assigned very soon, they will likely miss15:48
ttxso maybe use the next Heat meeting to get them assigned or deferred15:49
ttxzaneb: note that russellb will be handling next week juno-2 tagging15:49
russellbzaneb: o/15:49
zanebrussellb: \o15:49
russellbzaneb: so, i'll be in touch next week to confirm when you're ready to go with j215:50
ttxso when you're happy with a tag, communicate that to him. And he will be the one chasing you down so that you fall in the launch window15:50
zanebrussellb: ok, cool15:50
zanebI will follow up on the unassigned high priority bugs15:51
ttxzaneb: any topic you want to discuss at the cross-project meeting later ?15:51
zaneband make sure someone is on them15:51
zanebttx: nope15:51
ttxok then, talk to you later!15:51
zanebthanks, see you later!15:51
*** SlickNik has joined #openstack-relmgr-office16:07
ttxSlickNik: o/16:09
SlickNikHey ttx16:10
ttx#topic Trove16:10
*** markwash has joined #openstack-relmgr-office16:10
ttx#link https://launchpad.net/trove/+milestone/juno-216:10
ttxmarkwash: missed your turn :)16:10
ttxSlickNik: status looks good, although one week from juno-2 you can probably start to defer things16:11
SlickNikttx: Lots of BPs in review. Trying to get those done and implemented.16:11
ttxSlickNik: try to push those that are 99% there in priority. that will maximize the number of them you get "implemented"16:11
ttxwill also help with gate load next week16:12
ttxtalkign abot next week, russellb will be handling the juno-2 milestone release process, so he will be your point of contact16:12
SlickNikttx: Yes. Also, I need to defer some of the unstarted bugs to juno-3.16:12
SlickNikttx: will do that today.16:12
russellbSlickNik: o/16:12
ttxgoal is still to tag sometimes between Tuesday and Thursday16:12
russellbi'll be in touch next week to confirm when juno-2 is wrapped up16:12
SlickNikAwesome, thanks for the help with the tagging russellb16:13
russellbyep np16:13
russellbas long as things get deferred, my job is super easy :)16:13
russellbcompleted or deferred, rather16:14
ttxSlickNik: that's allk I had -- any topic for the meeting today ?16:14
SlickNikttx: nope, that's all I had as well. Just chugging along towards juno-2. :)16:15
ttxyay, that's the spirit16:15
ttxmarkwash: ready?16:15
markwashttx: yup!16:15
SlickNikttx: Thanks. see you in a bit!16:15
ttx#topic Glance16:15
ttx#link https://launchpad.net/glance/+milestone/juno-216:16
ttxLooks a bit... late16:16
markwashyes it does16:16
ttxStill think they can all make it ?16:16
markwashwe can probably land gpfs and bump the other two16:17
ttxmarkwash: well, better have 1 done than try to land the 3 and get nothing16:17
ttxso feel free to defer early16:17
markwashsounds about right16:18
ttx#info spec backlog: 1216:18
ttxanything is there likely to make a surprise last-minute rush to j2 ?16:18
markwashno I don't think so16:19
ttxmarkwash: ok. Note that russellb will be your host for j2 tagging next week16:19
russellbmarkwash: o/16:19
ttxso he will be the one chasing you down and deferring all your missed blueprints16:19
markwashwe'll be aiming to tag on tuesday?16:20
markwashor thursday?16:20
* ttx steps back and lets russellb answer16:20
markwashglance mini summit is thursday and friday16:20
russellbthe earlier the better16:20
russellbif you can be ready tuesday, that'd be great16:20
markwashI'll aim for that16:21
ttxmarkwash: ok, anything to add to the meeting agenda ?16:21
markwashnothing from me16:21
ttxmarkwash: we'll skip the 1:1s next week, btw16:21
ttxSlickNik: ^ same16:21
SlickNikttx: got it16:22
ttxnotmyname: ^ same16:22
* ttx realizes he missed a few notifications16:22
ttxmarkwash: that's all I had16:22
markwashttx: thanks! sorry I was late16:22
ttxmarkwash: no problem, SlickNik was early ;)16:23
ttxthat concludes the syncs for today, thanks everyone16:23
openstackMeeting ended Tue Jul 15 16:23:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-07-15-09.01.html16:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-07-15-09.01.txt16:23
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-07-15-09.01.log.html16:23
*** markwash_ has joined #openstack-relmgr-office16:59
*** markwash has quit IRC17:01
*** markwash_ is now known as markwash17:01
*** markwash has quit IRC17:35
*** markwash has joined #openstack-relmgr-office17:48
johnthetubaguyttx: bit late for today, but made some updates to the milestone: https://launchpad.net/nova/+milestone/juno-218:09
johnthetubaguyttx: need to sort out juno-3 a little too really18:09
-openstackstatus- NOTICE: python2.6 jobs are failing due to bug 1342262 "virtualenv>=1.9.1 not found" A fix is out but there are still nodes built on the old stale images18:23
*** ChanServ changes topic to "python2.6 jobs are failing due to bug 1342262 "virtualenv>=1.9.1 not found" A fix is out but there are still nodes built on the old stale images"18:23
*** david-lyle has quit IRC18:34
*** david-lyle has joined #openstack-relmgr-office18:45
*** johnthetubaguy is now known as zz_johnthetubagu18:54
*** markmcclain has joined #openstack-relmgr-office20:00
*** markmcclain1 has joined #openstack-relmgr-office20:04
*** markmcclain has quit IRC20:04
russellbzz_johnthetubagu: updates look good ... still probably too much to get reviewed in time, but we'll just see what makes it by early next week20:08
*** dhellman_ has joined #openstack-relmgr-office20:32
*** david-lyle has quit IRC20:32
*** markmcclain1 has quit IRC20:33
*** markmcclain has joined #openstack-relmgr-office20:33
*** david-lyle has joined #openstack-relmgr-office20:44
*** david-lyle has quit IRC20:44
*** david-lyle has joined #openstack-relmgr-office20:44
*** markmcclain has quit IRC21:06
*** russellb has quit IRC21:07
*** dolphm has quit IRC21:07
*** stevebaker has quit IRC21:07
*** notmyname has quit IRC21:07
*** stevebaker has joined #openstack-relmgr-office21:07
*** russellb has joined #openstack-relmgr-office21:07
*** notmyname has joined #openstack-relmgr-office21:07
*** dolphm has joined #openstack-relmgr-office21:07
*** dhellman_ has quit IRC21:47
*** david-lyle has quit IRC22:39

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