| ttx | notmyname: We can do 13:45 UTC, that should be 6:45am if my calculation is correct | 07:00 |
|---|---|---|
| mikal | ttx: we're on in about 15 minutes? | 07:47 |
| ttx | mikal: yes | 07:49 |
| ttx | 11min | 07:49 |
| * ttx grabs coffee | 07:50 | |
| * mikal grabs wine | 07:52 | |
| mikal | johnthetubaguy: ^-- grab a drink | 07:52 |
| ttx | #startmeeting ptl_sync | 08:00 |
| openstack | ttx: Error: Can't start another meeting, one is in progress. Use #endmeeting first. | 08:00 |
| ttx | uh | 08:00 |
| ttx | #endmeeting | 08:00 |
| openstack | Meeting ended Tue Jun 17 08:00:29 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-06-12-15.29.html | 08:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-06-12-15.29.txt | 08:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-06-12-15.29.log.html | 08:00 |
| ttx | oops. | 08:00 |
| ttx | #startmeeting ptl_sync | 08:00 |
| openstack | Meeting started Tue Jun 17 08:00:37 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:00 |
| mikal | Heh | 08:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:00 |
| openstack | The meeting name has been set to 'ptl_sync' | 08:00 |
| ttx | #topic Nova | 08:00 |
| mikal | Hello | 08:00 |
| ttx | mikal: yay, I didn't forget this time. | 08:01 |
| mikal | Neither did I | 08:01 |
| mikal | Its like a personal best for the both of us | 08:01 |
| ttx | #link https://launchpad.net/nova/+milestone/juno-2 | 08:01 |
| ttx | As it stands it looks quite good, but i suspect the autokick script has been busy keeping crap entries out | 08:04 |
| ttx | mikal: how.. representative is it of what you expect to land during the next 5 weeks ? | 08:04 |
| ttx | I certainly like that most of those show up as "under review" already | 08:04 |
| mikal | So, there's a pleasing amount of "needs code review" there | 08:05 |
| mikal | We do need to start reviewing specs more actively again though, there's a lot blocked up in that process | 08:05 |
| mikal | Although, review bandwidth is our obvious problem once again | 08:05 |
| mikal | Its a little hard to tell | 08:05 |
| * johnthetubaguy waves | 08:06 | |
| mikal | I agree that needs code review is good, although it remains to be seen if that's all the code for each of those bps | 08:06 |
| *** sdague has quit IRC | 08:16 | |
| *** morganfainberg has quit IRC | 08:16 | |
| *** kgriffs|afk has quit IRC | 08:16 | |
| *** dolphm has quit IRC | 08:16 | |
| *** stevebaker has quit IRC | 08:16 | |
| *** jgriffith has quit IRC | 08:16 | |
| *** notmyname has quit IRC | 08:16 | |
| *** ttx has quit IRC | 08:16 | |
| *** mattoliverau has quit IRC | 08:16 | |
| *** johnthetubaguy has quit IRC | 08:16 | |
| *** dhellmann has quit IRC | 08:16 | |
| *** anteaya has quit IRC | 08:16 | |
| *** zaneb has quit IRC | 08:16 | |
| *** devananda has quit IRC | 08:16 | |
| *** ChanServ has quit IRC | 08:16 | |
| *** dansmith has quit IRC | 08:16 | |
| *** SergeyLukjanov has quit IRC | 08:17 | |
| *** mikal has quit IRC | 08:17 | |
| *** dhellmann has joined #openstack-relmgr-office | 08:21 | |
| *** zaneb has joined #openstack-relmgr-office | 08:21 | |
| *** mattoliverau has joined #openstack-relmgr-office | 08:21 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 08:21 | |
| *** devananda has joined #openstack-relmgr-office | 08:21 | |
| *** anteaya has joined #openstack-relmgr-office | 08:21 | |
| *** mikal has joined #openstack-relmgr-office | 08:21 | |
| *** dansmith has joined #openstack-relmgr-office | 08:21 | |
| *** ChanServ has joined #openstack-relmgr-office | 08:21 | |
| *** SergeyLukjanov has joined #openstack-relmgr-office | 08:21 | |
| *** dickson.freenode.net sets mode: +o ChanServ | 08:21 | |
| *** sdague has joined #openstack-relmgr-office | 08:22 | |
| *** kgriffs|afk has joined #openstack-relmgr-office | 08:22 | |
| *** dolphm has joined #openstack-relmgr-office | 08:22 | |
| *** stevebaker has joined #openstack-relmgr-office | 08:22 | |
| *** jgriffith has joined #openstack-relmgr-office | 08:22 | |
| *** notmyname has joined #openstack-relmgr-office | 08:22 | |
| *** ttx has joined #openstack-relmgr-office | 08:22 | |
| mikal | Yeah, in some cases its pretty obvious why they're taking a break | 08:22 |
| *** morganfainberg has joined #openstack-relmgr-office | 08:22 | |
| mikal | Is that an unsplit? | 08:22 |
| mikal | ttx: we decided you're doing all of nova | 08:22 |
| johnthetubaguy | mikal: maybe, I think we just joined back with the rest of the world | 08:22 |
| mikal | ttx: you there? | 08:22 |
| * ttx emerges from the other side of the netsplit | 08:23 | |
| mikal | Heh, we had a nice meeting without you | 08:23 |
| ttx | mikal: yt? | 08:23 |
| mikal | Basically we're code talking review backlog and spec review backlog | 08:23 |
| mikal | talking code even | 08:23 |
| mikal | ttx: can you hear me? | 08:23 |
| ttx | o/ | 08:24 |
| mikal | Hi! | 08:24 |
| ttx | So I was saying... | 08:24 |
| ttx | <mikal> I agree that needs code review is good, although it remains to be seen if that's all the code for each of those bps | 08:24 |
| ttx | <ttx> it should be. If it's just that intermediary code is in review, it should be set to Good progress | 08:24 |
| ttx | <ttx> Basically "needs code review" means "all code is now up for review" | 08:24 |
| ttx | <ttx> otherwise you keep going back to good progress and it's a bit useless as a progress marker | 08:24 |
| johnthetubaguy | mikal: so, we might want to try little blueprints without specs at somepoint soon, but lets just see how its going | 08:24 |
| ttx | <ttx> mikal: how do you want to address that? | 08:24 |
| ttx | <ttx> I was pretty sure that adding a formal spec approval would just make the pipe longer, not faster | 08:24 |
| ttx | <ttx> since the same resources are used in both reviews | 08:24 |
| ttx | <ttx> At the start it will trigger a slowdown as people adjust to the new shape of the tube | 08:24 |
| ttx | <ttx> In the end it should be slightly faster since you should spend less time reviewing the whole idea at code review time | 08:24 |
| ttx | <ttx> mikal: Do you think a specific "spec review day" at the start of a milestone would help fast-approving a pack of them ? | 08:24 |
| mikal | Oh, a spec review day is an interesting idea | 08:25 |
| ttx | I think it would give a fast feedback loop | 08:25 |
| mikal | Although to be honest I think our biggest problem is we rely on a small number of very busy people | 08:25 |
| johnthetubaguy | ah, cool, we spoke about a spec proposal freeze for Juno-2 and Juno-3 on 3rd July | 08:25 |
| ttx | you could ask BP proposers to handg out | 08:25 |
| mikal | I think the idea of a spec review day should be included in the spec proposal freeze announcement | 08:26 |
| mikal | And having a faster feedback loop sounds good to me | 08:26 |
| johnthetubaguy | A combination sounds good | 08:26 |
| ttx | mikal: it's not a magic bullet, but I think having multiple people fast-iterating on them could help fast-approving a few | 08:26 |
| johnthetubaguy | people often catch me on IRC, and it does help resolve things quicker | 08:26 |
| mikal | I think we also need to remind -drivers to be reviewing specs | 08:26 |
| mikal | I know I haven't been doing enough of it | 08:26 |
| ttx | mikal: it's a bit tricky to prioritize. Been struggling with it myself | 08:27 |
| johnthetubaguy | mikal: we did stop doing it that last few weeks on purpose | 08:27 |
| ttx | I guess we'll get used to it | 08:27 |
| mikal | I think its the "very busy person" problem to be honest | 08:27 |
| ttx | mikal: OK, that's all I had. j2 status looks in sync with what you know of today , which is good | 08:27 |
| johnthetubaguy | mikal: that was the Juno-1 push, but yeah, we need to get back on the wagon with that stuff | 08:27 |
| mikal | But anyways, yes. We should refocus on specs for a while and then freeze new proposals | 08:28 |
| johnthetubaguy | yeah, my only worry is the stuff we want that is not yet through spec reviews, so not on the lp radar yet really | 08:28 |
| johnthetubaguy | but the freeze date, and a review day should help that | 08:28 |
| ttx | mikal: e might need to be a bit less strict in spec review approval. There might be a middle ground between "no spec review at all" and "spend 72 patchsets for every spec" | 08:28 |
| mikal | johnthetubaguy: do you think it would help if we pulled out a list of stuff we really want from -specs and ask drivers to focus on it? | 08:28 |
| johnthetubaguy | ttx: +1 I think the little guys need to get through faster | 08:29 |
| ttx | just having the doc around at code review time is useful | 08:29 |
| johnthetubaguy | mikal: I plan to create that as part of the priority setting | 08:29 |
| mikal | I agree that we don't need absolute perfection in specs | 08:29 |
| ttx | so in theory even if we accepted them all directly it would be better than what we were doing with BPs | 08:29 |
| mikal | ttx: agreed | 08:29 |
| ttx | so I wouldn't nitpick them to death | 08:29 |
| ttx | OK, I need to run | 08:29 |
| ttx | Anything you wanted to discuss at meeting later/tomorrow ? | 08:30 |
| mikal | No, I think I am good | 08:30 |
| mikal | johnthetubaguy: thanks for being awesome once again | 08:30 |
| johnthetubaguy | :) | 08:31 |
| johnthetubaguy | no problem | 08:31 |
| ttx | OK then, ttyl | 08:31 |
| mikal | Laters | 08:31 |
| mikal | johnthetubaguy: I'm going to wander off to cook dinner, talk more later | 08:31 |
| johnthetubaguy | mikal: sounds good, enjoy dinner | 08:31 |
| johnthetubaguy | mikal: thinking June 26th for spec review day | 08:31 |
| mikal | What day of the week is that? | 08:32 |
| mikal | I'd avoid Mondays and Fridays | 08:32 |
| johnthetubaguy | release day, so thursday I think | 08:32 |
| mikal | Sounds good to me | 08:32 |
| johnthetubaguy | cool, gives a week for loose ends | 08:32 |
| mikal | Works for me | 08:33 |
| *** sdague has quit IRC | 08:33 | |
| *** kgriffs|afk has quit IRC | 08:33 | |
| *** dolphm has quit IRC | 08:33 | |
| *** stevebaker has quit IRC | 08:33 | |
| *** jgriffith has quit IRC | 08:33 | |
| *** notmyname has quit IRC | 08:33 | |
| *** ttx has quit IRC | 08:33 | |
| mikal | Ok, dinner time for me | 08:33 |
| mikal | Bye! | 08:33 |
| johnthetubaguy | bye | 08:34 |
| johnthetubaguy | seems internet broke again anyways | 08:34 |
| *** johnthetubaguy has quit IRC | 08:35 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 08:36 | |
| *** stevebaker has joined #openstack-relmgr-office | 08:43 | |
| *** jgriffith has joined #openstack-relmgr-office | 08:43 | |
| *** notmyname has joined #openstack-relmgr-office | 08:43 | |
| *** ttx has joined #openstack-relmgr-office | 08:43 | |
| *** dolphm has joined #openstack-relmgr-office | 08:43 | |
| *** kgriffs|afk has joined #openstack-relmgr-office | 08:43 | |
| *** sdague has joined #openstack-relmgr-office | 08:43 | |
| *** eglynn has joined #openstack-relmgr-office | 10:03 | |
| eglynn | ttx: o/ | 11:44 |
| ttx | eglynn: o. | 11:44 |
| ttx | #topic Ceilometer | 11:44 |
| eglynn | hey | 11:45 |
| ttx | #link https://launchpad.net/ceilometer/+milestone/juno-2 | 11:45 |
| eglynn | so almost everything we bumped from juno-1 has now landed | 11:45 |
| ttx | Looks good, if not a bit empty | 11:45 |
| eglynn | yeah the cupboard is still relatively bare for j2 | 11:45 |
| eglynn | as planning is still in progress | 11:45 |
| eglynn | filing of BP specs discussed at last week's upstream meeting | 11:45 |
| ttx | There might have been a few things that got autokicked that you might want to push back in | 11:46 |
| eglynn | cool enough I'll check that | 11:46 |
| ttx | The trick with the new system is that some features may just land without appearing on the release radar at all | 11:46 |
| eglynn | yeah I'll keep an eye on that | 11:46 |
| ttx | so it's good to check that most major ones are accounted for | 11:46 |
| eglynn | BTW we've a long laundry list of possible work items for j2, so no shortage of possibilities | 11:47 |
| eglynn | we have a few in-flight specs reviews ... | 11:47 |
| eglynn | https://review.openstack.org/#/q/status:open+project:openstack/ceilometer-specs,n,z | 11:47 |
| eglynn | but I'm expecting a lot more by EoW | 11:47 |
| ttx | indeed | 11:47 |
| eglynn | BTW we've had persistent gate problems the past few days with a timing issue in the py26 build | 11:47 |
| ttx | I'd like us to look into the gap coverage plan and progress there | 11:48 |
| eglynn | I've curated the wiki page a bit | 11:48 |
| ttx | https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Ceilometer_Gap_Coverage | 11:48 |
| eglynn | #link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Ceilometer_Gap_Coverage | 11:48 |
| eglynn | yeap | 11:48 |
| eglynn | should be good for review I think | 11:48 |
| ttx | I think you're in good shape there | 11:48 |
| eglynn | should I plan to be on-hand during the TC meeting this evening for this topic? | 11:48 |
| ttx | No, I can report back | 11:48 |
| eglynn | cool enough | 11:49 |
| ttx | I mean, you can come, of course | 11:49 |
| ttx | but I'll report back on progress | 11:49 |
| eglynn | the progress reported on the wiki is up-to-date, I've sanity-checked my updates with each of the "drivers" | 11:49 |
| ttx | OK, no significant delay compared to the initial plan, right ? | 11:50 |
| eglynn | nope, good front-loaded progress for juno-1 as agreed with the TC | 11:50 |
| ttx | #info Gap coverage is on track, expected to be finished by j2 | 11:50 |
| eglynn | and all remaining action is good shape to for juno-2 | 11:50 |
| eglynn | shape to *land | 11:50 |
| ttx | Do you expect a lot of the -specs might be j2 material ? or more of j3 material ? | 11:51 |
| eglynn | some will definitely be j2, which is why I'm eager to get that stuff proposed ASAP | 11:51 |
| ttx | agreed. | 11:51 |
| ttx | We built a backlog when we switched to specs (with people retroactively filing specs for stuff they already worked on)but I suspect this will be less of an issue | 11:52 |
| ttx | as we go on | 11:52 |
| eglynn | the -specs process is working ok I think, with just some minor compalining about the Kafkaesque bureaucracy ;) | 11:52 |
| ttx | You're free to place the cursor where it makes the most sense | 11:53 |
| ttx | i.e. only require specs for high-profile changes if that makes more sense | 11:53 |
| ttx | but having multiple entry points makes the process more complex | 11:54 |
| ttx | so I would rather have a light template for basic stuff and fasttrack them through | 11:54 |
| eglynn | yeap, I'm erring on the side of requiring a spec in general to get folks used to the idea | 11:54 |
| eglynn | but defo open to fasttracking the non-contraversial/simpler stuff | 11:54 |
| ttx | Not everything should require endless nitpicking and two +2 | 11:54 |
| ttx | OK, anthing you want to discuss at cross-project meeting tonight ? | 11:55 |
| eglynn | yeap, I've also tried to minimzie spelling/grammar nitpicks for -specs reviews | 11:55 |
| eglynn | nothing specific I guess | 11:55 |
| ttx | OK, questions? | 11:55 |
| eglynn | quick heads-up on the ceilo mid-cycle July 2-4, many of us will be kinda off-grid for those 3 days | 11:55 |
| eglynn | #link https://wiki.openstack.org/wiki/Sprints/ParisJuno2014#Ceilometer | 11:55 |
| eglynn | mid-cycle attendence shaping up OK so far ... | 11:55 |
| eglynn | ... at least another two attendees in the pipeline, which would make 7 for ceilo in total | 11:56 |
| ttx | cool | 11:56 |
| eglynn | not huge, but definitely reaches quorum | 11:56 |
| eglynn | that's all I got for today ... | 11:57 |
| ttx | ok, great ttyl | 11:57 |
| ttx | SergeyLukjanov: around? | 11:57 |
| SergeyLukjanov | ttx, yup | 12:04 |
| SergeyLukjanov | ttx, sorry, I've been sending documents for visa | 12:04 |
| ttx | #topic Sahara | 12:04 |
| ttx | fun | 12:04 |
| ttx | https://launchpad.net/sahara/+milestone/juno-2 | 12:05 |
| SergeyLukjanov | #link https://launchpad.net/sahara/+milestone/juno-2 | 12:05 |
| ttx | Looks good, a bit ambitious maybe | 12:05 |
| SergeyLukjanov | ttx, it's not final/clean yet | 12:05 |
| ttx | just evolve it as reality changes | 12:05 |
| ttx | SergeyLukjanov: I wanted to attrct your attention to https://review.openstack.org/#/c/97872/2 | 12:06 |
| SergeyLukjanov | ttx, I think it's already looks liek our plans for j2 | 12:06 |
| ttx | proposal to require some sort of translations support in integrated projects | 12:06 |
| ttx | If I'm not mistaken, that would create an instant gap for Sahara | 12:07 |
| ttx | do you have plans in that area ? | 12:07 |
| SergeyLukjanov | ttx, yup, I've seen it, we already have everything needed configred in sahara (babel, scripts, traslation jobs, transifex project and etc.) | 12:07 |
| SergeyLukjanov | ttx, the only gap is lack of the _(..) wrapped strings | 12:07 |
| ttx | SergeyLukjanov: ok | 12:08 |
| SergeyLukjanov | ttx, last two assignments doesn't complete this work :( | 12:08 |
| SergeyLukjanov | ttx, so, it could be prioritized and done in j2 | 12:08 |
| ttx | OK, just trying to see if that would place you in some impossible spot | 12:09 |
| ttx | but apparently, not really | 12:09 |
| ttx | How is the removal of extra repositories going ? | 12:09 |
| SergeyLukjanov | ttx, yup, just wrap lines with _ | 12:09 |
| SergeyLukjanov | ttx, we have tasks to move sample jobs out of it | 12:10 |
| ttx | dashboard move is ready and pending on horizon devs, as we saw last week | 12:10 |
| ttx | what about the other two? | 12:11 |
| SergeyLukjanov | ttx, and then we'll have only hadoop swift fs in extra, but we're still not sure about the future of it | 12:11 |
| ttx | image-elemnets was merged already ? | 12:11 |
| SergeyLukjanov | ttx, nope, we decided to keep it as is | 12:11 |
| SergeyLukjanov | ttx, I was thinking that we already discuss it with you several weeks ago... | 12:12 |
| ttx | yes, certainly :) | 12:12 |
| ttx | i just need to remember | 12:12 |
| ttx | So in the end, only -dashboard will get merged | 12:12 |
| SergeyLukjanov | so, summary status: keep -image-elements as is, merge -dashboard to horizon, keep only hadoop swift fs in -extra (no releases) | 12:13 |
| ttx | ok, so the only risk is with -image-elements ... IIRC you said that it had to be in sync with the release | 12:13 |
| SergeyLukjanov | ttx, we're thinking about moving hadoop swift fs to separated repo but we're now in the progress of endless discussions | 12:14 |
| ttx | so having it outside the release management but still kept in sync with official releases sounds a bit brittle to me | 12:14 |
| SergeyLukjanov | ttx, we'll push the same tags to it and we'll have docs about buidling corresponding images | 12:14 |
| SergeyLukjanov | ttx, and we're planning to publish a base set of images for each release | 12:14 |
| ttx | can the main software work without the corresponding image-elements ? | 12:15 |
| SergeyLukjanov | ttx, yup, if you have correctly prepared image (with installed hadoop) | 12:15 |
| ttx | i.e. can we put ourselves in a strange corner if for some reason we publish one without the other ? | 12:15 |
| SergeyLukjanov | ttx, and for some plugins you just need the centos image w/o any preparations | 12:15 |
| ttx | because today you're around and I trust you to be around when we'll need to push -image-elements | 12:16 |
| ttx | but we need to plan for the worst and make sure that the integrated release can continue to work even if you lose interest in release management | 12:16 |
| SergeyLukjanov | ttx, it's fair | 12:17 |
| ttx | but then, if the image-elements can be rebuilt from instructions that are provided with the main software... | 12:17 |
| SergeyLukjanov | ttx, in fact we need tag in -image-elements just to mark the version of scripts | 12:18 |
| dhellmann | ttx: I'm ready when you are | 12:18 |
| ttx | I guess that's less of an issue | 12:18 |
| ttx | SergeyLukjanov: could you remind me why they can't be put in sahara itself ? It's a size issue, right ? | 12:18 |
| ttx | SergeyLukjanov: I think it's fine to ship separately as long as they can be regenerated from a script that we ship in sahara itself | 12:19 |
| ttx | we clos ethe loophole then | 12:19 |
| ttx | dhellmann: o/ | 12:19 |
| dhellmann | o/ | 12:19 |
| SergeyLukjanov | ttx, it was very long discussions with tons of pros and cons and eventually the pros number for keeping it as is were much bigger than others | 12:20 |
| ttx | SergeyLukjanov: ok, we'll talk again about it -- I just want to make sure the integrated release is self-sufficient | 12:20 |
| ttx | and not depending on something that nobody knows how to release | 12:20 |
| ttx | except you :) | 12:20 |
| SergeyLukjanov | ttx, yup, I got your point, I'll take a look on how could we couple sahara integrated release to -image-elements | 12:21 |
| ttx | SergeyLukjanov: did you have a topic for today's meeting? | 12:21 |
| SergeyLukjanov | ttx, I'm just pushing the tag to the repo :) | 12:21 |
| SergeyLukjanov | ttx, I think no topics from my side for today | 12:21 |
| ttx | ack | 12:21 |
| SergeyLukjanov | ttx, thank you | 12:21 |
| ttx | #topic Oslo | 12:22 |
| ttx | dhellmann: sorry for the lateness | 12:22 |
| ttx | https://launchpad.net/oslo/+milestone/juno-2 | 12:22 |
| dhellmann | ttx: no problem | 12:23 |
| ttx | dhellmann: Looks good, expecting a lot more to emerge from -specs, or mostly complete ? | 12:23 |
| dhellmann | we're a little slow approving our specs, but I think we have the process down now | 12:23 |
| dhellmann | I have a list of a few of them to propose we accept at the meeting friday | 12:23 |
| ttx | dhellmann: which makes me thing we need to decide on that rootwrap spec | 12:23 |
| ttx | think* | 12:24 |
| dhellmann | there are 2 rootwrap specs, do you mean the daemon mode one? | 12:24 |
| ttx | tthe daemon one is not ready | 12:24 |
| ttx | the ionice one I think is good to go as long as the doc clearly expresses the security tradeoff | 12:25 |
| ttx | but that's slightly off-topic | 12:25 |
| dhellmann | it looks like there has been an update on that one since you left your request | 12:25 |
| ttx | dhellmann: yes, probably just waiting on me | 12:25 |
| dhellmann | although there's a promise of more detail to come, as well, so that makes me think it's not done | 12:25 |
| ttx | https://launchpad.net/oslo.messaging/+milestone/juno-2 | 12:25 |
| dhellmann | oh, no, that's "in the" implementation not "on the" | 12:26 |
| ttx | same, looks good, if not a bit empty | 12:26 |
| ttx | like i said earlier, with autokick removing stuff, we need to make sure no major feature flies under the release radar | 12:26 |
| ttx | since we can't really rely on people adding them back to the milestone page anymore | 12:27 |
| ttx | that's the downside of this approach | 12:27 |
| dhellmann | yeah, I'll make sure as specs are approved their bps are updated with priority and target | 12:27 |
| ttx | so.. would you say that the current state of the j2 pages shows 50% of what will finally get done ? 75% ? | 12:28 |
| dhellmann | it is about 50% of what we said we would do, but we combined a few libraries so it may be closer to 75% | 12:29 |
| dhellmann | some of the specs we have up for review weren't discussed at the summit, and some may not be approved | 12:29 |
| ttx | No, I mean... not compared to summit plans. Do you think you'll add a lot of extra BPs to match late-approved specs, or not that much ? | 12:30 |
| dhellmann | I expect to approve 3 more this week | 12:30 |
| ttx | ok | 12:30 |
| dhellmann | oh, yeah, we have a lot of specs that I expect to approve | 12:30 |
| ttx | and those may still fall in j2, right | 12:31 |
| dhellmann | like I said, we got a late start on that | 12:31 |
| dhellmann | a few, yes | 12:31 |
| dhellmann | the 3 certainly | 12:31 |
| ttx | ok | 12:31 |
| dhellmann | anything we approve for j3 will be a library we don't expect anyone to use this cycle | 12:31 |
| ttx | ok | 12:31 |
| dhellmann | I want to keep pushing ahead, so they are ready to be adopted early in k | 12:31 |
| ttx | Anything you'd like to discuss at meeting today ? | 12:32 |
| dhellmann | I have 4 alpha releases planned for early next week | 12:32 |
| dhellmann | all are for libraries already in requirements, but I thought it would be good to give everyone a heads-up that they are coming | 12:32 |
| ttx | does that mean that existing libs should have their juno features nailed by j-2 ? | 12:32 |
| dhellmann | I'll tag them early monday, unless someone objects in the oslo meeting friday | 12:32 |
| dhellmann | that's a good question | 12:33 |
| ttx | It would kind of make sense overall | 12:33 |
| ttx | if you expect consumers to use those new features... | 12:33 |
| dhellmann | I'd like that. I'm not sure if I would cut anyone off, given the fact that we're always running a little ahead of the rest of the project. | 12:33 |
| dhellmann | major features I could see holding | 12:34 |
| ttx | #info Ideally, existing libraries should have their Juno featureset completed by j2 | 12:34 |
| ttx | OK, thats all I had | 12:35 |
| ttx | anything on your side ? | 12:35 |
| dhellmann | #info alpha releases of stevedore, oslo.config, oslotest, and oslosphinx planned for 23 June | 12:35 |
| dhellmann | no, that's it | 12:35 |
| ttx | cool! thx | 12:35 |
| ttx | ttyl | 12:35 |
| dhellmann | thanks! | 12:35 |
| ttx | notmyname: as noted earlier, you can go at 13:45 UTC if you're interested. that's in 70min? | 12:36 |
| notmyname | ttx: my alarm just went off. 13:45 (ie 6:45am pacific) is good with me | 13:02 |
| *** jpich has joined #openstack-relmgr-office | 13:44 | |
| ttx | notmyname: o/ | 13:45 |
| notmyname | ttx: hello | 13:46 |
| ttx | #topic Swift | 13:46 |
| ttx | notmyname: how are you doing ? | 13:46 |
| notmyname | ttx: thanks for being flexible with the time | 13:46 |
| notmyname | ttx: I'm mostly ok. surgery recovery is going pretty well so far :-) | 13:46 |
| notmyname | ttx: I have the goal of merging storage policy patches today. reviews seem to be looking pretty good, and I'm hopeful that with today's time we can get it done | 13:47 |
| ttx | notmyname: ok, you might want to push those security fixes in as well | 13:48 |
| ttx | the VMT will just do a public OSSA once the patch is public | 13:48 |
| notmyname | ttx: right. I expect those to be included as well. I've been working with tristanC on the right time | 13:48 |
| notmyname | ttx: ah ok | 13:48 |
| notmyname | ttx: so then it looks like I should be able to do that this afternoon | 13:49 |
| ttx | there might be a few hours gap but I don't think that's critical in this specific case | 13:49 |
| ttx | OK, I'll let tristanC know | 13:49 |
| ttx | so you might have a RC1 SHA ready for tagging by eod ? | 13:49 |
| ttx | fwiw I adjusted tools so that we support 2-step tagging in master for such Swift intermediary releases | 13:50 |
| notmyname | that's the goal. at least working its way through jenkins | 13:50 |
| notmyname | ok | 13:50 |
| notmyname | ttx: meaning that we can do an RC tag and then a final | 13:50 |
| notmyname | ? | 13:50 |
| ttx | https://review.openstack.org/#/c/99892/ | 13:50 |
| ttx | swiftrc.sh pushes a RC1 tag and marks all bugs fixreleased on the final milestone | 13:51 |
| notmyname | ok | 13:51 |
| ttx | then milestone.sh specialcases swift and just tags/uploads tarball without going over bugs again | 13:51 |
| ttx | (at final approval time) | 13:51 |
| notmyname | ok | 13:51 |
| ttx | the only difference with a classic milestone being, we push the RC1 tag and mark bugs fixreleased earlier | 13:52 |
| ttx | a sort of lightweight milestone-proposed | 13:52 |
| notmyname | ok. I think I follow that | 13:53 |
| ttx | so if all goes well, we have a 2.0 milestone page, we tag 2.0-rc1 on master, push all FixCommitted bugs to FixReleased/2.0 | 13:53 |
| ttx | then when you bless it, we tag 2.0 on master, and upload the resulting tarball on that milestone page | 13:54 |
| notmyname | ok | 13:54 |
| ttx | If you need to fix something, we get fancy with a release branch, cut out of the RC1 tag | 13:54 |
| notmyname | ok | 13:55 |
| notmyname | that makes sense | 13:55 |
| ttx | probably calling it milestone-proposed so that we get back on our feet with infra scripts | 13:55 |
| ttx | but I shall soon push the patch so that we can call it proposed/* | 13:55 |
| ttx | I think that works. | 13:56 |
| ttx | so I'll wait for your SHA and run swiftrc.sh when I have it | 13:56 |
| ttx | notmyname: we should probably create the milestone page now | 13:56 |
| notmyname | I will get it to you as soon as I have it | 13:56 |
| ttx | so you can start retroactively target BP to it | 13:56 |
| notmyname | yes. can you create it in LP? | 13:56 |
| ttx | 2.0.0 ? | 13:56 |
| notmyname | yes | 13:57 |
| ttx | i'll do it now | 13:57 |
| notmyname | thanks | 13:57 |
| ttx | https://launchpad.net/swift/+milestone/2.0.0 | 13:57 |
| ttx | so the tag would be 2.0.0.rc1 | 13:58 |
| notmyname | ok | 13:58 |
| ttx | notmyname: anything else you wanted to discuss ? | 13:58 |
| notmyname | nope. that's what I've got | 13:58 |
| ttx | i'll complain about missing blueprints, but we can do that between RC1 and final :) | 13:58 |
| notmyname | :_) | 13:58 |
| ttx | anything you want to add to meeting agenda for today ? | 13:59 |
| ttx | #info Swift 2.0.0.rc1 hopefully today or tomorrow | 13:59 |
| notmyname | nothing specific | 13:59 |
| ttx | notmyname: ok, cool. Do you get up early because you can't sleep ? | 13:59 |
| ttx | Or some new routine? | 14:00 |
| ttx | dolphm: around? | 14:00 |
| notmyname | unfortunately today the answer is yes. normally its because of kids, though. I'm normally up between 6:30 and 7:00 on most days | 14:00 |
| ttx | notmyname: ok, get better soon! | 14:00 |
| notmyname | thanks :-) | 14:00 |
| dolphm | ttx: o/ | 14:01 |
| ttx | #topic Keystone | 14:01 |
| ttx | https://launchpad.net/keystone/+milestone/juno-2 | 14:02 |
| ttx | That's pretty raw | 14:02 |
| ttx | Do you have more still baking in the -specs repo ? | 14:02 |
| dolphm | juno-2 will be our first milestone which requires proposals to keystone-specs first | 14:02 |
| ttx | do you think they will get out of there fast enough ? | 14:02 |
| ttx | (to make j2) ? | 14:02 |
| dolphm | i believe so | 14:03 |
| dolphm | we have a 5 or 6 that are well rounded at this point | 14:03 |
| dolphm | https://review.openstack.org/#/q/project:openstack/keystone-specs,n,z | 14:03 |
| dolphm | last week we discussed how we want to work the approval process on that repo, which i think we'll finalize today and see a few land | 14:04 |
| ttx | OK well, add them as they are approved, if they still make sense for j2. | 14:04 |
| ttx | I /think/ in the end we'll have a one-milestone delay, like specs that are approved during j1 can be targetted to j2 | 14:04 |
| ttx | (except low-flying objects obviously) | 14:05 |
| dolphm | i think we were thinking in that direction as well, but we're off to a later start than nova, for example | 14:05 |
| ttx | yes, starting the process will always craete a delay/backlog/mess | 14:05 |
| ttx | OK, so just add them as they are approved | 14:05 |
| ttx | My script doesn't do miracles yet, since LP doesn't have a blueprint-cration API yet | 14:06 |
| dolphm | s/yet// ? | 14:06 |
| ttx | lifless convinced someone to work on that | 14:06 |
| dolphm | oh alrighty then | 14:06 |
| ttx | I think he is embarassed that it sucks so much :) | 14:07 |
| ttx | or surprised. | 14:07 |
| ttx | anyway | 14:07 |
| ttx | i didn't have much in store for you. That autokick script basically makes sure the blueprint page looks good :) | 14:08 |
| ttx | The trick being, to make sure it contains everything it should | 14:08 |
| ttx | so keep an eye for feature sflying below the radar | 14:08 |
| ttx | and make sure major ones are mentioned in the milestone page... even if they bypassed the spec process somehow | 14:09 |
| ttx | dolphm: anything you wanted to add to today's meeting agenda ? | 14:09 |
| dolphm | #info Support for compressed PKI tokens landed in keystone; we'd like to make them the default in keystone & devstack during Juno | 14:10 |
| dolphm | just that ^ | 14:10 |
| ttx | ok, great! | 14:11 |
| ttx | that's just for #info right, not for a discussion item ? | 14:11 |
| dolphm | i don't believe so; if we suspect we might cause any pain (which i don't think is the case), i'll raise a discussion item | 14:12 |
| ttx | dolphm: ack. ttyl then! | 14:13 |
| dolphm | /salute | 14:13 |
| ttx | jgriffith: ready when you are | 14:14 |
| *** markmcclain has joined #openstack-relmgr-office | 14:24 | |
| *** mestery has joined #openstack-relmgr-office | 14:27 | |
| ttx | jpich: representing david today ? | 14:33 |
| jpich | ttx: Yes, if needed! | 14:33 |
| * ttx doesn't see mrunge around | 14:33 | |
| ttx | jpich: you're in! | 14:33 |
| ttx | #topic Horizon | 14:33 |
| ttx | https://launchpad.net/horizon/+milestone/juno-2 | 14:33 |
| ttx | looks a bit too big and heavily needs prioritization and other improvements, but i'll annoy david with it rather than you | 14:34 |
| *** mestery has quit IRC | 14:34 | |
| jpich | I'm lucky :-) On the plus side a lot of it is up for review | 14:34 |
| *** mestery has joined #openstack-relmgr-office | 14:35 | |
| ttx | jpich: i wanted to go over the Gap coverage plan progress quickly | 14:35 |
| ttx | https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Horizon_Gap_Coverage | 14:36 |
| jpich | Ok | 14:36 |
| ttx | Looking at it, only the misison statement is late | 14:36 |
| ttx | is the horizon split still doable within juno-2 ? | 14:36 |
| jpich | I think the mission statement has a proposal in it, not sure if it needs to be vetted before the item can be marked as complete? | 14:37 |
| jpich | rdopieralski is currently doing a lot of work on the split, I think we're still hopeful it'll be doable within juno-2 | 14:38 |
| ttx | it should be proposed to the governance repo at some point | 14:38 |
| ttx | ok | 14:38 |
| jpich | Probably there'll be fresher news during the Horizon meeting later today | 14:38 |
| ttx | what about your piece, "Integration Framework Tied to Gate" ? | 14:38 |
| ttx | Is it still on track for j3 ? | 14:39 |
| jpich | There's several folks currently submitting tests for review so I think it's chugging along nicely | 14:39 |
| ttx | ok cool | 14:40 |
| jpich | (we'd agreed with the Tempest folks back in HK to start this in our own repo since the tests will be very different from the API tests) | 14:40 |
| ttx | That's all I had | 14:40 |
| jpich | now I don't know when a testing effort can be considered "complete" | 14:40 |
| ttx | yes, agreed | 14:40 |
| jpich | So there'll be more by Juno-3 for sure :) | 14:40 |
| jpich | I didn't have anything to bring up myself | 14:40 |
| ttx | Anthing you or someone else on the Horizon team wanted to discuss at the cross-project meeting today ? | 14:41 |
| jpich | Not that I'm aware of | 14:41 |
| ttx | jpich: ok, let me know if that changes | 14:41 |
| jpich | Ok | 14:41 |
| ttx | jpich: thx for standing in ! | 14:41 |
| jpich | No problems! Cheers | 14:41 |
| ttx | mestery: ready when you are | 14:41 |
| mestery | ttx: o/ | 14:42 |
| ttx | #topic Neutron | 14:42 |
| ttx | https://launchpad.net/neutron/+milestone/juno-2 | 14:42 |
| ttx | Looks good | 14:42 |
| ttx | Did most of those go throug the -specs process ? | 14:43 |
| mestery | thanks | 14:43 |
| mestery | Yes, some are not approved and we're working on it | 14:43 |
| *** markmcclain has quit IRC | 14:43 | |
| mestery | I will bump those not approved over the next week | 14:43 |
| ttx | mestery: wanted to quickly go though the Gap coverage plan, wince I will report progress at the TC meeting today | 14:43 |
| mestery | ttx: Cool, I'm ready! | 14:43 |
| ttx | https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Neutron_Gap_Coverage | 14:44 |
| mestery | Want me to walk through each item? | 14:44 |
| mestery | I was going to prepare an etherpad with progress, but traveling for LBaaS this week | 14:44 |
| ttx | yes, quick walkthrough of progress maybe | 14:45 |
| mestery | So, Gap 0 has a spec ready for approval: https://review.openstack.org/#/c/95738 | 14:45 |
| mestery | We have converged there, and coding has also started. | 14:46 |
| ttx | ok | 14:46 |
| mestery | Gap1: We have 1 API test left to merge, and new scenario tests are being written now (spec is in tempest -specs repo). | 14:46 |
| mestery | Gap2 is being worked at the moment, I need to sync with the developer who's assigned to that this week. | 14:46 |
| mestery | Gap3 has a patch waiting to be merged (Juno-3) | 14:46 |
| mestery | Gap4: There was only one API call which was needed, a WIP patch is out for it. | 14:47 |
| mestery | Gap5: We merged a few DVR patches, and more are being reviewed now. We should be landing the majority of them over the new few weeks. | 14:47 |
| ttx | ok, so gap4 is late but it's shallow | 14:47 |
| mestery | Gap4: Correct | 14:47 |
| mestery | Gap6: We have a WIP patch in nova for an API there, and a spec for that should be proposed this week yet on the neutron side. | 14:47 |
| ttx | gap5 should probably be retargeted to j2 then | 14:48 |
| mestery | Gap7: I'll start that later in Juno-2. | 14:48 |
| mestery | Correct | 14:48 |
| ttx | feel free to edit that page | 14:48 |
| mestery | So, that's a whirlwind update. | 14:48 |
| mestery | OK, will do | 14:48 |
| ttx | OK, looks like it's taking slightly more time, but still on track | 14:48 |
| mestery | That's a fair assessment, yes. | 14:49 |
| ttx | next on our busy 15-min, i wanted to talk about https://wiki.openstack.org/wiki/Blueprints#Neutron | 14:49 |
| mestery | OK | 14:49 |
| ttx | There is something there (and in nova and Oslo instructions) that doesn't work with autokick | 14:49 |
| ttx | "Once your design specification has been committed to neutron-specs: " | 14:49 |
| ttx | "Propose your blueprint, as above, by selecting the milestone in which you plan to complete the blueprint " | 14:50 |
| mestery | OK, shall I remove that part? | 14:50 |
| ttx | That will result in them getting punished by autokick | 14:50 |
| mestery | :) | 14:50 |
| ttx | My proposal is... | 14:50 |
| ttx | we get rid of the whole "Once your design specification has been committed to neutron-specs: " section | 14:50 |
| *** markmcclain has joined #openstack-relmgr-office | 14:50 | |
| ttx | You as driver put the BP on the radar by adding milestone and priority | 14:50 |
| mestery | Makes sense to me. | 14:51 |
| ttx | then the assignee can update milestone and implementation status to reflect progress | 14:51 |
| mestery | I've been doing that already anyways. :) | 14:51 |
| ttx | i'll provide a script to do that in one step | 14:51 |
| ttx | (including updating the link) | 14:51 |
| mestery | OK | 14:51 |
| ttx | so that shoud not be that much of a hassle | 14:51 |
| ttx | Also would you mind if we collapsed the instructions for Nova/Oslo/Neutron ? they don't seem that much different now | 14:52 |
| mestery | I am all for that actually, makes perfect sense. | 14:52 |
| ttx | I'm rewriting the page following numerous complains that it advocates a behavior that I seem to punishg | 14:52 |
| mestery | :) | 14:52 |
| ttx | We'll still ask them to register the blueprint themselves though | 14:53 |
| ttx | even if that's a bit bureaucratic | 14:53 |
| ttx | it makes them the owner of the spec, which seems right | 14:53 |
| ttx | (err... owner of the Bp) | 14:53 |
| ttx | OK, tat went faster than I thought. That's all I had | 14:54 |
| mestery | :) | 14:54 |
| mestery | Same here, thanks ttx! | 14:54 |
| ttx | anything you want to add to meeting agenda for today ? | 14:54 |
| mestery | Nothing at this time, no. | 14:54 |
| ttx | since we have a couple more minutes, could you quickly explain what the two essential blueprints are about ? | 14:54 |
| ttx | Neturon Distributed Virtual Router for OVS | 14:54 |
| *** markmcclain has quit IRC | 14:55 | |
| ttx | Neutron DB Migration Refactor | 14:55 |
| mestery | DVR is the functionality equivalent for nova multi-host | 14:55 |
| ttx | the first one is the DVR thing that we ask in gap coverage right | 14:55 |
| ttx | ok | 14:55 |
| mestery | Right | 14:55 |
| mestery | And the second one covers Gap0 | 14:55 |
| mestery | It's the spec for how we will move forward with DB migrations in neutron, the healing migration, etc. | 14:55 |
| ttx | OK, that's clear | 14:55 |
| mestery | cool | 14:55 |
| ttx | I could have figured it out by reading them, but since we had one minute left... | 14:56 |
| mestery | ;) | 14:56 |
| * ttx gets lazy with age | 14:56 | |
| * mestery is the same way. | 14:56 | |
| ttx | mestery: thanks! ttyl | 14:56 |
| mestery | thanks! Later. | 14:56 |
| ttx | jgriffith: around now ? | 14:56 |
| jgriffith | ttx: hola | 14:58 |
| jgriffith | ttx: we should probably change my time :( | 14:58 |
| ttx | #topic Cinder | 14:58 |
| ttx | we should :) | 14:58 |
| jgriffith | ttx: I'm driving in to the office more lately | 14:59 |
| ttx | I have 2 minutes, let's be quick | 14:59 |
| jgriffith | ttx: and it's screwing up our system | 14:59 |
| jgriffith | k | 14:59 |
| jgriffith | I'm good :) | 14:59 |
| jgriffith | all set :) | 14:59 |
| ttx | https://launchpad.net/cinder/+milestone/juno-2 | 14:59 |
| ttx | https://blueprints.launchpad.net/cinder/+spec/task-logging has no assignee ? | 14:59 |
| jgriffith | harlow is working on it | 14:59 |
| jgriffith | I'll update it to reflect correctly | 14:59 |
| ttx | ok, you should assign it to him then | 14:59 |
| ttx | ok | 14:59 |
| *** markmcclain has joined #openstack-relmgr-office | 14:59 | |
| ttx | Otherwise that's all cinder-specs-approved stuff ? Or there are a few direct adds ? | 15:00 |
| jgriffith | Some are still direct carry overs from the pre-spec days | 15:00 |
| ttx | Are you expecting much more to make it out of cinder-specs in time for j2 ? | 15:00 |
| jgriffith | but I've been actively swatting those that have come in after | 15:00 |
| jgriffith | ttx: I'm hoping for at least two more | 15:01 |
| ttx | ok | 15:01 |
| jgriffith | ttx: but honestly my prio right now is catch up on what's in the queue | 15:01 |
| ttx | anything you want to add to meeting agenda ? | 15:01 |
| jgriffith | if that doesn't happen I'll just stop accepting new things altogether | 15:01 |
| jgriffith | nope, I"m good thanks | 15:01 |
| ttx | ok, talk to you more next week | 15:01 |
| ttx | we can discuss a better time for you too | 15:02 |
| jgriffith | ttx: cool, sorry about that | 15:02 |
| *** kgriffs|afk is now known as kgriffs | 15:06 | |
| zaneb | o/ | 15:46 |
| ttx | zaneb: o/ | 15:47 |
| ttx | #topic Heat | 15:47 |
| ttx | https://launchpad.net/heat/+milestone/juno-2 | 15:48 |
| zaneb | looks like we got through j-1 relatively unscathed :) | 15:48 |
| ttx | The page looks good, but the autokick script might have been hard at work | 15:49 |
| zaneb | I suspect so | 15:49 |
| zaneb | ooh, I'm gonna move my first one to implemented | 15:49 |
| ttx | zaneb: do you have a lot of work still stranded in -specs approval that you expect will be added here ? | 15:49 |
| zaneb | patches finally merged | 15:49 |
| *** jpich has left #openstack-relmgr-office | 15:49 | |
| zaneb | I don't think there's much, if anything, for j-2 | 15:50 |
| ttx | ok | 15:51 |
| zaneb | https://review.openstack.org/#/q/status:open+project:openstack/heat-specs,n,z | 15:51 |
| zaneb | actually, that's a longer list than I thought | 15:51 |
| * zaneb needs to do more reviews | 15:51 | |
| zaneb | but most of it is more long-term | 15:51 |
| ttx | i was wondering... do you ask people to file a blueprint in parallel to filing a spec ? | 15:51 |
| ttx | (like nova/neutron do ?) | 15:52 |
| zaneb | no, I haven't been | 15:52 |
| zaneb | and we haven't had any approved yet, so it's a bit academic at this point ;) | 15:52 |
| ttx | hah | 15:53 |
| zaneb | but I did have a question about that the other day, w.r.t. a Keystone spec | 15:53 |
| zaneb | is it likely that a script will handle this in the future? or should I be encouraging people to create bps as well? | 15:53 |
| ttx | Well the benefit of asking them to file the BP is... they are rightly marked as owning it, and then we can use a script to update all relevant fields at approval time | 15:54 |
| ttx | I planned to ahve a BP-creation script but it's stalled due to lack of BP creation API in Launchpad | 15:54 |
| ttx | so at this point, asking them to create the original BP is not a bad idea | 15:54 |
| ttx | since THEN you can update all fields via the script i'll be providing :) | 15:54 |
| zaneb | ok, cool. I'll go with that answer next time ;) | 15:55 |
| ttx | It just.. feels wrong to ask them to file in two places. | 15:55 |
| zaneb | yeah, it does a bit | 15:55 |
| ttx | But then, their time is more expandable than yours, generally | 15:55 |
| zaneb | specs repo should be _less_ work, ideally | 15:55 |
| ttx | if someone needs to do it manually, better be them | 15:56 |
| zaneb | I support that :D | 15:56 |
| ttx | I just rewrote https://wiki.openstack.org/wiki/Blueprints | 15:56 |
| ttx | to account for the new process, autokick script included | 15:56 |
| zaneb | oh, nice | 15:56 |
| zaneb | so when can we kill launchpad? ;) | 15:57 |
| ttx | Working on it | 15:57 |
| ttx | zaneb: anything you want to add to meeting agenda for today ? | 15:58 |
| zaneb | nope, I'm good | 15:58 |
| ttx | OK then, ttyl | 15:58 |
| zaneb | thanks ttx o/ | 15:58 |
| ttx | no markwash yet | 15:58 |
| ttx | no Nikhil either. Beer time! | 15:59 |
| *** markwash has joined #openstack-relmgr-office | 16:00 | |
| ttx | markwash: o/ | 16:02 |
| markwash | hi there | 16:02 |
| ttx | #topic Glance | 16:02 |
| ttx | https://launchpad.net/glance/+milestone/juno-2 | 16:02 |
| ttx | Small but consistent | 16:03 |
| ttx | markwash: do you have a lot queued in -specs ? | 16:03 |
| markwash | yeah, about 7 at this point | 16:03 |
| ttx | Any of them likely to make juno-2 ? | 16:04 |
| markwash | yes, at least one | 16:04 |
| ttx | Do you have a stop date after which you'll stop considering them ? | 16:04 |
| markwash | we didn't plan on anything like that | 16:04 |
| ttx | ok | 16:04 |
| ttx | that's fine | 16:04 |
| markwash | we've just been trying to build our glance-specs review momentum so far | 16:04 |
| ttx | markwash: i put the "gap coverage plan" on the TC agenda for today -- that's just about how you think you can address the small integartion testing gap that was called out last week | 16:05 |
| ttx | we can delay it to next week, agenda is busy | 16:05 |
| markwash | yes please, I was going to ask actually | 16:05 |
| ttx | but it should be 3 lines on a wiki page | 16:05 |
| markwash | oh | 16:05 |
| ttx | markwash: OK, that works | 16:06 |
| ttx | you might want to have a plan first (with an assignee) before you write those 3 lines :) | 16:06 |
| markwash | I think those 3 lines are basically: add more glance tests to tempest in juno-2 | 16:06 |
| markwash | and then two lines of squiggles :-) | 16:06 |
| ttx | yeah, something like that. With a "task owner" :) | 16:06 |
| markwash | and hearts | 16:06 |
| markwash | okay | 16:06 |
| ttx | markwash: your call, we can defer to next week | 16:07 |
| markwash | I asked around for volunteers at last team meeting, but made it sound like people needed to do it immediately and no one had time | 16:07 |
| markwash | yeah, let's do next week | 16:07 |
| ttx | immediately, no. Within juno would be good | 16:07 |
| ttx | ok, moving to next meetign agenda | 16:07 |
| ttx | what else... | 16:08 |
| ttx | anything you'd like to put on cross-project meeting agenda ? | 16:09 |
| markwash | I need to update the mission statement proposal again | 16:09 |
| markwash | nothing for cross-project from me | 16:09 |
| ttx | yes, we'll talk about it at the TC meeting | 16:09 |
| ttx | so if you have a new version, better post it before | 16:09 |
| ttx | i'l try to ask to cut the nitpikcing | 16:09 |
| markwash | I'll see if I can take a pass, I didn't realize it was on the agenda for this week but I suppose that was very silly | 16:10 |
| markwash | I have to prep for the ptl webinar as well | 16:10 |
| ttx | it's up on the governance change list, so we try to cover it asap | 16:10 |
| ttx | but as I said, it will be a busy meeting | 16:10 |
| markwash | yeah, that's exactly what I should have expected | 16:10 |
| ttx | so we might just skip it anyway | 16:10 |
| ttx | we'll see how it goes | 16:11 |
| markwash | that might also be best, I'll put in an update to the language sometime tomorrow or thursday in any case | 16:11 |
| ttx | That's all I had. The -specs driven workflow certainly makes it simpler to sync between us. | 16:11 |
| * ttx hugs autokick.py | 16:11 | |
| markwash | haha | 16:12 |
| ttx | markwash: ttyl! | 16:12 |
| markwash | thanks | 16:12 |
| *** SlickNik has joined #openstack-relmgr-office | 16:14 | |
| ttx | SlickNik: o/ | 16:17 |
| SlickNik | o/ | 16:17 |
| ttx | #topic Trove | 16:17 |
| ttx | https://launchpad.net/trove/+milestone/juno-2 | 16:17 |
| ttx | SlickNik: so you should set a priority for those 4 "undefined" things, if you want to bless them | 16:17 |
| ttx | if not, you should clear their milestone target field so that they don't mess up our view | 16:18 |
| ttx | Otherwise looks good | 16:18 |
| SlickNik | ttx: Okay will probably do that today. | 16:18 |
| SlickNik | Along with bug triage, which I haven't had a chance to do this week, as yet. | 16:19 |
| SlickNik | Lot more BPs, and we're making some good progress in juno-2. | 16:19 |
| ttx | would you say your j-2 plans is accurately representing what you plan to accomplish for j2 ? | 16:20 |
| SlickNik | A couple of them marked not-started have actually begun, so I'll take an action to update the list to better mirror actual progress. | 16:20 |
| ttx | OK, wanted to talk about progress on your gap coverage plan | 16:21 |
| ttx | https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Trove_Gap_Coverage | 16:21 |
| ttx | Could you quickly go through it and tell me about progress, if any ? | 16:21 |
| SlickNik | We've made really good progress to Concern #1. | 16:22 |
| SlickNik | We're looking at integration tests right now, and neutron support might actually merge early (in Juno 2). | 16:22 |
| ttx | cool! | 16:23 |
| SlickNik | We made a bit of progress on the doc front (i.e. updates to the deploy doc), but we still have more work to do here. | 16:23 |
| SlickNik | I'm going to take on some of it, and get a couple of other cores to help. | 16:24 |
| SlickNik | Will try to get a good chunk done in Juno-2, but I suspect we'll probably need to keep working on docs even past that (through Juno 3) | 16:24 |
| SlickNik | For concern #3: We've got a patch for an experimental job in CI infra out already. | 16:25 |
| SlickNik | Once that merges, we're going to iron out kinks in it, and look to make it gating. | 16:25 |
| SlickNik | And once that happens, we can turn off the old reddwarf-ci | 16:26 |
| SlickNik | Review for the experimental job I mentioned | 16:26 |
| SlickNik | #link https://review.openstack.org/#/c/98517/ | 16:26 |
| SlickNik | For Concern #4, I've been working with amcrn and cp16net and we've been doing a good job on staying on top of triage, and process. | 16:28 |
| SlickNik | So a couple of main pushes for Juno 2 for us will be around focusing on Concerns #1, and #2. | 16:29 |
| ttx | ok | 16:30 |
| ttx | I think we can consider #4 done | 16:31 |
| ttx | it's more of a policy thiung | 16:31 |
| ttx | what about #5 ? | 16:32 |
| SlickNik | I alluded to #5 earlier, out of order (sorry!). | 16:33 |
| SlickNik | #link https://review.openstack.org/#/c/88349/ | 16:33 |
| SlickNik | It's close to being done. | 16:33 |
| SlickNik | annashen is debugging a couple of failing tests | 16:34 |
| SlickNik | But once that's fixed (i.e. the tests are passing) the patch looks in good shape, and we're on track to get that merged for Juno 2 | 16:35 |
| ttx | oops sorry | 16:36 |
| ttx | parallelizing discussions. | 16:36 |
| ttx | OK so overall, takes more time than expected but still on track for Juno | 16:37 |
| SlickNik | Not a problem. :) | 16:37 |
| ttx | SlickNik: feel free to adjust milestone targets on that wiki page | 16:37 |
| SlickNik | Yes, that's a good summary. | 16:37 |
| ttx | SlickNik: i'll report on your behalf to the TC | 16:37 |
| ttx | SlickNik: anything you want to add to meetign agenda for today ? | 16:37 |
| SlickNik | ttx: Awesome, thanks. When will the report be? I'll try and be there too, in case anything something comes up. | 16:38 |
| ttx | 20:00 utc meeting | 16:38 |
| ttx | (TC meeting) | 16:39 |
| SlickNik | Ah, today. sounds good! | 16:39 |
| SlickNik | ttx: Nope. I'm trying to push out a client release sometime this week with all the bugfixes we've done for juno-1. | 16:39 |
| ttx | #info trying to push out a client release sometime this week with all the bugfixes we've done for juno-1 | 16:39 |
| ttx | ok then... releasing you. ttyl :) | 16:40 |
| ttx | #endmeeting | 16:40 |
| openstack | Meeting ended Tue Jun 17 16:40:17 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:40 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-17-08.00.html | 16:40 |
| SlickNik | Thanks much! Catch you later! | 16:40 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-17-08.00.txt | 16:40 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-17-08.00.log.html | 16:40 |
| *** mestery_ has joined #openstack-relmgr-office | 17:05 | |
| *** mestery_ has quit IRC | 17:05 | |
| *** mestery_ has joined #openstack-relmgr-office | 17:06 | |
| *** mestery has quit IRC | 17:07 | |
| *** mestery_ is now known as mestery | 17:07 | |
| *** kgriffs is now known as kgriffs|afk | 17:23 | |
| *** kgriffs|afk is now known as kgriffs | 17:44 | |
| *** johnthetubaguy is now known as zz_johnthetubagu | 17:52 | |
| *** kgriffs is now known as kgriffs|afk | 17:54 | |
| *** kgriffs|afk is now known as kgriffs | 18:07 | |
| *** kgriffs is now known as kgriffs|afk | 18:17 | |
| *** eglynn has quit IRC | 18:43 | |
| *** kgriffs|afk is now known as kgriffs | 19:08 | |
| *** kgriffs is now known as kgriffs|afk | 19:17 | |
| *** eglynn has joined #openstack-relmgr-office | 19:18 | |
| *** kgriffs|afk is now known as kgriffs | 19:24 | |
| *** eglynn is now known as eglynn-afk | 19:51 | |
| *** dhellman_ has joined #openstack-relmgr-office | 20:12 | |
| *** sdague has quit IRC | 20:19 | |
| *** kgriffs has quit IRC | 20:19 | |
| *** dolphm has quit IRC | 20:19 | |
| *** stevebaker has quit IRC | 20:19 | |
| *** jgriffith has quit IRC | 20:19 | |
| *** notmyname has quit IRC | 20:19 | |
| *** ttx has quit IRC | 20:19 | |
| *** sdague has joined #openstack-relmgr-office | 20:20 | |
| *** kgriffs has joined #openstack-relmgr-office | 20:20 | |
| *** dolphm has joined #openstack-relmgr-office | 20:20 | |
| *** ttx has joined #openstack-relmgr-office | 20:20 | |
| *** notmyname has joined #openstack-relmgr-office | 20:20 | |
| *** jgriffith has joined #openstack-relmgr-office | 20:20 | |
| *** stevebaker has joined #openstack-relmgr-office | 20:20 | |
| *** eglynn-afk is now known as eglynn | 20:46 | |
| *** dhellman_ has quit IRC | 21:26 | |
| *** morganfainberg has quit IRC | 21:50 | |
| *** morganfainberg has joined #openstack-relmgr-office | 21:50 | |
| *** eglynn has quit IRC | 22:05 | |
| *** zaneb has quit IRC | 22:36 | |
| *** markmcclain has quit IRC | 22:52 | |
| *** markmcclain has joined #openstack-relmgr-office | 23:00 | |
| *** mestery has quit IRC | 23:06 | |
| *** markmcclain has quit IRC | 23:14 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!