| *** david-lyle has joined #openstack-relmgr-office | 03:11 | |
| *** david-lyle has quit IRC | 04:33 | |
| johnthetubaguy | ttx: mikal: what time is the nova catch up these days? | 08:40 |
|---|---|---|
| ttx | rhaa dammit | 08:40 |
| mikal | Heh | 08:40 |
| mikal | I said the same thing | 08:40 |
| ttx | That would be 40min ago | 08:40 |
| mikal | I was lost in this gate fix thing | 08:40 |
| mikal | ttx: do it now? | 08:41 |
| ttx | sure | 08:41 |
| ttx | sorry I haven't adjusted yet to the "oh and I have one early in morning" thing | 08:41 |
| mikal | Its ok, I didn't ping you either | 08:41 |
| ttx | #startmeeting ptl_sync | 08:41 |
| openstack | Meeting started Tue Jun 10 08:41:33 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:41 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:41 |
| openstack | The meeting name has been set to 'ptl_sync' | 08:41 |
| ttx | #topic Nova | 08:41 |
| ttx | #link https://launchpad.net/nova/+milestone/juno-1 | 08:41 |
| ttx | Page looks good, progress -- not so good | 08:42 |
| mikal | So, we've had some gate problems which are making things more exciting | 08:42 |
| ttx | no kidding | 08:42 |
| johnthetubaguy | yeah, agreed, its not so different from last week | 08:42 |
| mikal | I see "needs code review" as a good sign there | 08:42 |
| ttx | At this point we should probably reduce to the stuff that is already approved an in flight | 08:42 |
| mikal | i.e. at least there's some code | 08:42 |
| ttx | and* | 08:43 |
| johnthetubaguy | yeah, I think its trimming time | 08:43 |
| mikal | sdague asked for some more logging in nova-network, so I've been working on that | 08:43 |
| mikal | It _might_ help nail down some gate problems | 08:43 |
| ttx | mikal: We need to tag sometimes between now and Thursday | 08:43 |
| johnthetubaguy | there are lots of −1ed (for a good reason) patches | 08:43 |
| johnthetubaguy | so those go to j-2 right? | 08:43 |
| mikal | Yeah | 08:43 |
| ttx | If we trim the list to the "good ones that just need a bit more hours to pass the gate I think that's a resasonable objective | 08:43 |
| mikal | Given the state of the gate, I feel like if things aren't reviewing well they're not going to make it | 08:44 |
| ttx | agreed | 08:44 |
| johnthetubaguy | agreed | 08:44 |
| johnthetubaguy | OK, I can sort out the list | 08:44 |
| mikal | Unless the j-1 date might move because of the gate? | 08:44 |
| mikal | Thanks johnthetubaguy | 08:44 |
| ttx | mikal: no, I don't think that would change anything | 08:44 |
| mikal | Ok, just checking | 08:44 |
| ttx | johnthetubaguy: so let's just keep in list stuff that is approved and in-flight, or almost approved | 08:45 |
| ttx | that way we can trigger the tag when all those merge | 08:45 |
| mikal | ttx: what's the process for tagging? | 08:45 |
| mikal | Do you do that or do I? | 08:45 |
| johnthetubaguy | ttx: sounds good, will sort that | 08:45 |
| ttx | mikal: I do it, you just give me a SHA (or an algorithm to determine it) | 08:46 |
| ttx | like "when that merges" | 08:46 |
| mikal | Ok | 08:46 |
| mikal | We can do that interactively on IRC | 08:46 |
| ttx | yes we can | 08:46 |
| ttx | mikal: on the bugs side... | 08:47 |
| mikal | Yeah, I got a bit upset about that last week | 08:47 |
| ttx | I guess we should applythe same logic | 08:47 |
| mikal | I'm going to assume you didn't see the nova meeting last week | 08:47 |
| ttx | let's keep only stuff that is already in-flight + milestone-critical stuff | 08:47 |
| mikal | I agree for targetted bugs for j-1 | 08:47 |
| ttx | and move everything else to j-2 | 08:47 |
| johnthetubaguy | mikal: correctly upset though | 08:47 |
| mikal | However, we have a pretty big bug problem in general, with our 1,200 bugs | 08:47 |
| johnthetubaguy | mikal: we need to teach people to stop targeting bugs, people do it to get more reviews it seems? | 08:48 |
| mikal | Oh, that hadn't occurred to me as a thing people would do, but it makes sense now that you say it | 08:48 |
| johnthetubaguy | I kinda like reserving targeting for these last few days, and major bloopers | 08:48 |
| ttx | mikal: so, about bugs | 08:48 |
| mikal | There was some brain storming in the nova meeting last week about bug automation | 08:49 |
| ttx | once issue is that they serve two purposes: task tracking (for devs) and bug report (for users) | 08:49 |
| mikal | Which you probably have thoughts on | 08:49 |
| ttx | the first category usually is well-maintained | 08:49 |
| ttx | the other category is usually mostly ignored | 08:49 |
| mikal | Yeah, I feel like ignoring user bugs is a really bad user experience | 08:49 |
| mikal | But we do it a lot | 08:49 |
| mikal | And digging out of this backlog is going to be hard | 08:50 |
| ttx | Quite often, devs file bug when they fix something, but the bug actually was reported before by a user, and then if we are lucky we find the dupe | 08:50 |
| johnthetubaguy | (sub category: bugs a dev raise because a user reported it to them) | 08:50 |
| ttx | and then there is the targeting issue | 08:50 |
| mikal | ttx: that is true | 08:50 |
| johnthetubaguy | ttx: +1 | 08:50 |
| mikal | I am very sure there are dupes and already fixed things in there | 08:50 |
| mikal | But we can't find them because there's so many | 08:51 |
| ttx | Which is mostly because we have a single-dimensional priority/targeting system | 08:51 |
| ttx | so there is no way for, say, the vmware folks to have their priority list | 08:51 |
| mikal | I think its also because we have a cultural problem to be honest | 08:51 |
| mikal | We have a lot of work on features, but not a lot on bug fixes | 08:51 |
| ttx | so they abuse the milestone target to do it | 08:51 |
| mikal | I think we need to talk about how to incent the behaviour we want | 08:51 |
| ttx | we are trying to fid ways to have multiple priorities/targeting/tasklists in storyboard so that parallel groups can all express that | 08:52 |
| mikal | I think we're talking about two different things here | 08:52 |
| ttx | but it's more complex than it seems | 08:52 |
| johnthetubaguy | mikal: quite a few "features" are looking to fix "systemic" bugs, but it does feel that way | 08:52 |
| mikal | But I agree with you that something richer than LP would help | 08:52 |
| ttx | mikal: basically we need people to be able to create arbitrary, sorted lists of bugs/tasks | 08:52 |
| mikal | johnthetubaguy: sure, but those need to go and close the reported bugs they resolve as well | 08:52 |
| ttx | the "release" one (which corresponds to the milestone target list) would just be one | 08:53 |
| mikal | ttx: that would be nice | 08:53 |
| ttx | anyway, that's long-term | 08:53 |
| mikal | Although it doesn't help actually close bugs faster than we do now | 08:53 |
| johnthetubaguy | mikal: need to go? agreed, the bugs should get closed that are related, but they are hard to find now, but lets take this offline | 08:53 |
| mikal | It just makes them more organized | 08:53 |
| ttx | in the short term, you should own the milestone target | 08:53 |
| ttx | if someone else's use of it renders it useless for you... | 08:53 |
| mikal | Agreed | 08:53 |
| ttx | then you should encourage them to use a tag instead | 08:54 |
| * johnthetubaguy nods with approval | 08:54 | |
| ttx | like vmware-j1-list | 08:54 |
| ttx | it's a bit dirty but will do the trick | 08:54 |
| mikal | Ok | 08:54 |
| ttx | that said, i'm fine with keeping them in the milestone list, at least until we near milestone tag | 08:54 |
| * johnthetubaguy likes the tag alternative | 08:55 | |
| ttx | it's just a bit painful to clean up now | 08:55 |
| mikal | johnthetubaguy: are you happy to do the cleanup or shall I? | 08:55 |
| johnthetubaguy | mikal: you should sleep, and fix logging, I can take the first stab | 08:55 |
| mikal | johnthetubaguy: ok, thanks | 08:56 |
| ttx | #info milestone and bugs should be reduced to in-flight stuff (with reviews already approved) and we plan to tag when all that backlog merges | 08:56 |
| johnthetubaguy | mikal: assuming you check the j-1 list tomorrow, to keep me honest | 08:56 |
| mikal | johnthetubaguy: I can do that | 08:56 |
| * mikal makes a note | 08:56 | |
| ttx | If anything is just shy of one core review, it might make sense to do it now to keep it in list | 08:56 |
| johnthetubaguy | ttx: you are reading my mind | 08:56 |
| johnthetubaguy | at least that was my plan yesterday, but I ran out of work hours | 08:57 |
| ttx | Once the list is refined we'll track how fast we burn it | 08:59 |
| johnthetubaguy | ttx: duno if you have anything more from your side, but how is *-specs looking to you at this point? | 08:59 |
| mikal | Do we want to have a quick meeting 24 hours or so before the deadline to review state of play? | 08:59 |
| ttx | johnthetubaguy: it seems to result in cleaner objectives | 08:59 |
| johnthetubaguy | ttx: thats true, just worried about the speed, we now have a specs backlog, so the quick spec reviews are hard to find, sigh | 09:00 |
| ttx | Looking at the juno roadmap now... | 09:01 |
| johnthetubaguy | looking forward to those multi-dimentional priorities, so we have spec review priority | 09:01 |
| ttx | juno-2 and juno-3 are full with unprioritized blueprints | 09:01 |
| johnthetubaguy | ttx: they are not approved, should be no unapproved that have been accepted into juno | 09:01 |
| ttx | so if I were to enable my autokick script it would remove most of them | 09:01 |
| johnthetubaguy | ah, thats a good point | 09:02 |
| ttx | trying to see what would work best | 09:02 |
| johnthetubaguy | I was looking at this list: https://blueprints.launchpad.net/nova/juno | 09:02 |
| mikal | johnthetubaguy: priority of undefined == unapproved? | 09:02 |
| johnthetubaguy | the unapproved ones just don't have code yet | 09:02 |
| mikal | i.e. you always set a priority? | 09:02 |
| johnthetubaguy | mikal: well, not been setting a priority until the get approved, unless its super high priority | 09:03 |
| ttx | mikal: we use priority as a way to say that you blessed it | 09:03 |
| mikal | Ok | 09:03 |
| johnthetubaguy | mikal: talking of which, we need to be better at setting those, I am being a bit arbitrary at the moment | 09:03 |
| ttx | which is why my script proposes to remove target milestone from anythign that has no prio | 09:03 |
| mikal | j-2 also has way too much from one developer | 09:03 |
| johnthetubaguy | mikal: but lets take that offline | 09:03 |
| mikal | johnthetubaguy: ok | 09:03 |
| ttx | johnthetubaguy: it seems your workflow is slightly different though | 09:04 |
| ttx | you use unprioritized as a queue of stuff that might get approved | 09:04 |
| johnthetubaguy | ttx: I was doing, I gave up, people keep adding stuff into milestones, maybe just run your script? | 09:05 |
| ttx | let me pastebin what it would do | 09:05 |
| mikal | Yeah, if you're setting values which stop the script from kicking the stuff we've approved, then run the script | 09:05 |
| ttx | the script just removes unprioritized stuff (assumes it's been added by someone else) and just adjusts series goal to match | 09:06 |
| ttx | http://paste.ubuntu.com/7622514/ | 09:06 |
| mikal | A quick scan makes me think those changes would be ok? | 09:07 |
| johnthetubaguy | the setgoal, I guess we approved those specs now? | 09:07 |
| ttx | I can run it now, then I'll enable it to ru every ~2 hours to keep it ok | 09:07 |
| ttx | "setgoal" is when the spec is targeted to juno-X but has no series goal (juno) set. So it's missing from the https://blueprints.launchpad.net/nova/juno page | 09:08 |
| ttx | yay LP consistency | 09:08 |
| ttx | the script enforces that consistency | 09:08 |
| johnthetubaguy | ah, I see, cool | 09:08 |
| johnthetubaguy | ttx: go for it I think | 09:09 |
| ttx | mikal: you ok with all these ? | 09:09 |
| mikal | Yes | 09:09 |
| * ttx removes --dryrun | 09:09 | |
| johnthetubaguy | sweet, thanks | 09:09 |
| ttx | we'll see how many people complain | 09:10 |
| ttx | the script leaves a note in the whiteboard when it kicks a blueprint out | 09:10 |
| mikal | Heh | 09:10 |
| mikal | Someone will always complain | 09:10 |
| johnthetubaguy | +1 | 09:10 |
| johnthetubaguy | well the fourth time it gets kicked out they may ask questions | 09:11 |
| johnthetubaguy | ttx: you can tell them to bug me in the message, if thats helpful? | 09:11 |
| ttx | fixing a small bug in my script, sorry for the wait | 09:13 |
| ttx | johnthetubaguy: no that's fine | 09:13 |
| ttx | mikal: anything else ? | 09:14 |
| johnthetubaguy | ttx: no problem, nothing like our crazy work queue to test things :) | 09:14 |
| mikal | Not that I can think of | 09:14 |
| ttx | example message: https://blueprints.launchpad.net/nova/+spec/remove-compute-flavors-to-flavor-object | 09:14 |
| mikal | I'd like to talk one day about general ways to get more bugs fixed in nova | 09:14 |
| mikal | But that doesn't have to be today | 09:14 |
| mikal | j-1 is a bigger priority this week | 09:14 |
| ttx | (see whiteboard) | 09:14 |
| ttx | mikal: agreed | 09:14 |
| johnthetubaguy | ttx: perfect | 09:15 |
| ttx | johnthetubaguy: ping me when you cleaned up the j-1 lists | 09:15 |
| johnthetubaguy | ttx: will do | 09:15 |
| ttx | so that I get an idea of how much we are waiting on | 09:15 |
| johnthetubaguy | cool | 09:15 |
| mikal | Sounds good | 09:15 |
| mikal | And I will take a look at j-1 tomorrow as well | 09:15 |
| mikal | But I really appreciate your effort johnthetubaguy | 09:15 |
| ttx | we might need to readjust goals depending on how today runs in the gate | 09:15 |
| ttx | johnthetubaguy is the awesome | 09:16 |
| johnthetubaguy | mikal: thanks, appreciated | 09:16 |
| mikal | Yeah, I am assuming the gate will be a mess this week | 09:16 |
| mikal | :) | 09:16 |
| johnthetubaguy | ttx: :) | 09:16 |
| mikal | (To johnthetubaguy, not the gate) | 09:16 |
| johnthetubaguy | lol | 09:16 |
| mikal | So, I guess that's it for this week's 1:1 | 09:17 |
| mikal | Well, really 1:2 | 09:17 |
| mikal | We're ganging up on you | 09:17 |
| johnthetubaguy | ttx: catch you in a bit once j-1 is cleaned up | 09:18 |
| mikal | ttx: do you endmeeting these, or is this done and I can wander off? | 09:19 |
| ttx | mikal: you can wander. We'll close it when all ptl syncs are done today | 09:21 |
| mikal | OK cool | 09:21 |
| mikal | Thanks guys | 09:21 |
| mikal | Talk more later | 09:21 |
| johnthetubaguy | aww, juno-2 looks much better now :) | 09:21 |
| johnthetubaguy | catch you later | 09:21 |
| *** eglynn has joined #openstack-relmgr-office | 10:45 | |
| johnthetubaguy | ttx: quick heads up, juno-1 list is in better shape now, in some ways, in other ways it looks empty, https://launchpad.net/nova/+milestone/juno-1 | 11:27 |
| johnthetubaguy | we may need to punt more, but there is still some hope the remaining bits might get reviewed in time | 11:29 |
| ttx | johnthetubaguy: if anything accidentally makes it, we can switch the target back to j-1 | 11:30 |
| sdague | johnthetubaguy: realistically consider it a 12 hr minimum delay after approve to land | 11:39 |
| eglynn | ttx: o/ | 11:44 |
| eglynn | ttx: ... ceilo up now? | 11:44 |
| eglynn | #link https://launchpad.net/ceilometer/+milestone/juno-1 | 11:45 |
| eglynn | we're not in too bad a shape for juno-1 | 11:45 |
| eglynn | hbase-events-feature should land, modulo the gate slowness that sdague refers to above ^^^ | 11:45 |
| ttx | eglynn: o/ | 11:45 |
| ttx | #topic Ceilometer | 11:45 |
| ttx | #link https://launchpad.net/ceilometer/+milestone/juno-1 | 11:45 |
| * eglynn pastes ... | 11:46 | |
| eglynn | we're not in too bad a shape for juno-1 | 11:46 |
| eglynn | hbase-events-feature should land, modulo the gate slowness that sdague refers to above ^^^ | 11:46 |
| eglynn | (... two patches just landed BTW that should help with the high failure rate in the ceilo units) | 11:46 |
| eglynn | concerned about hbase-resource-rowkey-enhancement BP | 11:46 |
| ttx | eglynn: are the 3 remaining blueprints approved and in-flight, or still needing approvals ? | 11:46 |
| eglynn | one related patch already landed for hbase-resource-rowkey-enhancement ... https://review.openstack.org/78244 | 11:47 |
| eglynn | but the main one is a bit stalled https://review.openstack.org/87249 | 11:47 |
| eglynn | will prolly have to bump the BP if there isn't significant traction by EoD | 11:47 |
| eglynn | concerned also about grenade-upgrade-testing | 11:47 |
| eglynn | ... it turns out all the changes are on the grenade side | 11:47 |
| ttx | yeah, ideally we should only have in-flight stuff ny eod, given the gate backlog | 11:47 |
| eglynn | k ... the grenade review is stalled due to lack of reviewer bandwidth | 11:48 |
| eglynn | ... I've reached out to sdague and dtroyer about this, and Sean is fully loaded with gate fire-fighting | 11:48 |
| sdague | eglynn: I just approved it through | 11:48 |
| eglynn | ... Dean *may* be able to help though when he comes on-line | 11:48 |
| ttx | can be early j-2 | 11:48 |
| eglynn | sdague: good man! :) | 11:48 |
| eglynn | sdague: thank you sir! | 11:48 |
| sdague | no prob | 11:49 |
| ttx | eglynn: OK, let's keep those last 3 in | 11:49 |
| ttx | and we'll adjust early tomorrow | 11:49 |
| ttx | let's try to tag sometimes tomorrow to not stretch on Thursday | 11:49 |
| eglynn | ... so the main concern is then really only hbase-resource-rowkey-enhancement, I'll circle back with Nadya on that | 11:49 |
| eglynn | yep aggred | 11:49 |
| eglynn | *agreed | 11:49 |
| ttx | eglynn: on the bugs side... | 11:49 |
| eglynn | bugs are mainly good, I gave the commit log another sweep for untarget'd bugs that have fixes already landed | 11:50 |
| eglynn | ... I think the 3 in-progress bugs should be landable | 11:50 |
| ttx | #info 3 remaining BPs, hbase-events-feature in-flight, hbase-resource-rowkey-enhancement a bit stalled, grenade-upgrade-testing dependent on grenade resources | 11:50 |
| ttx | eglynn: how are their reveiws looking ? | 11:51 |
| eglynn | this bug is low priority, so would not loose sleep if I had to punt it ... https://bugs.launchpad.net/ceilometer/+bug/1293337 | 11:51 |
| eglynn | on reviews, I'm pushing the cores to concentrate on juno-1 target'd stuff today | 11:51 |
| ttx | OK, I propose we punt to j-2 anything that's not approved and in-flight in gate by EOD | 11:52 |
| eglynn | ... the backlog of post-juno1 reviews can wait until after the j1 tag is cut | 11:52 |
| eglynn | yep, agreed on that | 11:52 |
| ttx | #info Will punt to j-2 anything that's not approved and in-flight in gate by EOD | 11:52 |
| ttx | #Shooting for tagging on Wednesday | 11:52 |
| ttx | #info Shooting for tagging on Wednesday | 11:52 |
| eglynn | cool, juno-2 planning starts at weekly meeting on Thurs | 11:53 |
| eglynn | ... so would be good to have juno-1 in the bag on Wednesday | 11:53 |
| ttx | Looking at what would happen if I ran my autokick script on juno BPs now | 11:53 |
| eglynn | k | 11:53 |
| ttx | eglynn: http://paste.ubuntu.com/7623122/ | 11:53 |
| eglynn | SETGOAL means? | 11:54 |
| ttx | so there would be two juno-3 BPs that we would remove from milestone target | 11:54 |
| ttx | *GOAL means adjusting series goal | 11:54 |
| ttx | i.e. the "series goal" field in the BP | 11:54 |
| eglynn | a-ha I see | 11:54 |
| ttx | which can be out of sync with milestone, due to lack of LP consistency between those fields | 11:55 |
| ttx | so the *GOAL actions just adjust series goal based on milestone target value | 11:55 |
| eglynn | OK I'll chase down those BPs, get my i's dotted and t's crossed | 11:55 |
| ttx | eglynn: should I run the script now ? It will remove the milestone target and add a message on the whiteboard about removal of unprioritized BPs | 11:55 |
| eglynn | ttx: yep, let's give it a whirl | 11:56 |
| eglynn | ttx: ... only the BPs in your paste will be impacted, right? | 11:56 |
| ttx | yes | 11:56 |
| eglynn | BTW I just fixed the series goal on grenade-upgrade-testing | 11:56 |
| ttx | See for example now: https://blueprints.launchpad.net/ceilometer/+spec/instance-per-disk-measurement | 11:57 |
| ttx | milestone was cleared and message was added to Bp whiteboard | 11:57 |
| eglynn | cool, looks reasonable | 11:58 |
| ttx | OK, we'll discuss automating the script run every 2/3 hours at the meeting today | 11:58 |
| ttx | Anything you'd like to add to the meetign agenda for today ? | 11:58 |
| eglynn | yep, that sounds like a plan | 11:58 |
| eglynn | nothing specific | 11:58 |
| ttx | eglynn: basically, te script ensures that only the BPs that you blessed (with a priority set) show up in those milestone plans | 11:59 |
| * SergeyLukjanov lurking | 11:59 | |
| ttx | hence tuyrning them into real project drivers roadmap, rather than a mix-and-match for stuff loosely proposed by people | 11:59 |
| ttx | ideally that should result in way less time spent fixing those | 12:00 |
| ttx | eglynn: anything else ? | 12:00 |
| eglynn | ttx: so effectively we need to start seeding the practice of folks ... | 12:00 |
| eglynn | (a) not filing BPs in LP until the corresponding spec has landed | 12:00 |
| eglynn | and: | 12:00 |
| eglynn | (b) not setting the "milestone target unless the blueprint has been properly prioritized by the project drivers" | 12:01 |
| ttx | eglynn: right. i actually work on a script to automate blueprint creation from spec -- so that you (the project drivers) can do it with limited work | 12:01 |
| eglynn | ^^^ are those the two main process changes that'll be visible to most folks? | 12:01 |
| eglynn | ttx: excellent! | 12:01 |
| ttx | you could even consider that filing a BP is a drivers job | 12:01 |
| ttx | all people should have to do is file a spec | 12:01 |
| eglynn | yeah, that would make sense | 12:01 |
| ttx | eglynn: work is a bit delayed since damn Lp doesn't have an API for creating BPs | 12:02 |
| ttx | so I have to leverage the webclient | 12:02 |
| ttx | fun. | 12:02 |
| ttx | ok, shara time | 12:02 |
| eglynn | sounds messy ;) | 12:02 |
| ttx | #topic Sahara | 12:02 |
| ttx | eglynn: thx! | 12:02 |
| ttx | SergeyLukjanov: o/ | 12:02 |
| SergeyLukjanov | ttx, hey! | 12:02 |
| SergeyLukjanov | #link https://launchpad.net/sahara/+milestone/juno-1 | 12:03 |
| ttx | #info 2 blueprints left | 12:03 |
| SergeyLukjanov | so, only changes that are now in gate are in the mp | 12:03 |
| SergeyLukjanov | milestone* | 12:03 |
| ttx | cool | 12:03 |
| ttx | SergeyLukjanov: including for bugs ? | 12:03 |
| SergeyLukjanov | yup | 12:03 |
| ttx | that's how I like it | 12:03 |
| ttx | Let's shoot for tagging when that is merged | 12:04 |
| ttx | #info All targeted changes are in-flight in the gate | 12:04 |
| ttx | SergeyLukjanov: so let me see what autokick would do to your blueprints | 12:05 |
| SergeyLukjanov | ttx, I'm monitoring their progress and send you confirmation when all changes will be landed | 12:05 |
| SergeyLukjanov | ttx, ok | 12:05 |
| ttx | http://paste.ubuntu.com/7623169/ | 12:05 |
| ttx | It would kick 4 blueprints out of j-2 | 12:05 |
| ttx | You migth want to check if those are covered by approved specs or if you want to let them fly in below radar | 12:06 |
| ttx | and/or let me just run the script now | 12:07 |
| SergeyLukjanov | ttx, okay, I'll check them | 12:07 |
| ttx | Goal being to try to enable te script to run automatically every 2/3hours | 12:07 |
| ttx | #action Sergey to check the 4 j-2 blueprints that would get kicked out of j-2 if autokick was enabled | 12:08 |
| ttx | SergeyLukjanov: anything you'd like to add to the meeting agenda ? | 12:08 |
| SergeyLukjanov | ttx, you could start the script, I'll return back bps to j2 if needed | 12:08 |
| SergeyLukjanov | our specs-related stuff is on review | 12:09 |
| ttx | ok, running script | 12:09 |
| ttx | See effect at: https://blueprints.launchpad.net/sahara/+spec/cluster-secgroups | 12:09 |
| SergeyLukjanov | it's not going very fast, the prev. week was hadoop summit => decreasing review speed and not so good quorum | 12:09 |
| SergeyLukjanov | ttx, ack | 12:09 |
| SergeyLukjanov | ttx, so, it resets milestone and series | 12:10 |
| ttx | yes | 12:10 |
| ttx | I shall add it to the release tools at some point | 12:10 |
| ttx | hmm, that makes me think... | 12:10 |
| ttx | Could use your quick review on https://review.openstack.org/#/c/98123/ | 12:11 |
| ttx | Before I self-approve myself | 12:11 |
| SergeyLukjanov | ttx, looking | 12:11 |
| ttx | SergeyLukjanov: it's the script I'll use for milestone tagging this week | 12:12 |
| SergeyLukjanov | ttx, now parsing (((release_date.month % 11) + 2) / 7) + 1 | 12:13 |
| ttx | fun uh | 12:14 |
| ttx | I'll probably wait for at least one tag to be successfully run with it before APRVing it | 12:14 |
| SergeyLukjanov | ttx, what's about testing it on sandbox? | 12:14 |
| ttx | SergeyLukjanov: I'll probably change it so that it parses 'J' as the a year.seq thing, rather than the milestone date | 12:15 |
| ttx | it seems less error-prone | 12:15 |
| SergeyLukjanov | sounds good | 12:15 |
| SergeyLukjanov | the scripts looks good so far | 12:15 |
| ttx | SergeyLukjanov: yeah, i'll ping you again when ms2version uses alphabet rather than publication dates | 12:15 |
| SergeyLukjanov | ttx, ok, I'll take a look on it after change | 12:16 |
| ttx | SergeyLukjanov: which TZ are yo uin currently ? | 12:16 |
| ttx | dhellmann: around? | 12:17 |
| SergeyLukjanov | ttx, UTC+4 | 12:17 |
| ttx | ok, back home I see | 12:17 |
| SergeyLukjanov | ttx, yup | 12:18 |
| ttx | SergeyLukjanov: cool. Anything else ? | 12:18 |
| SergeyLukjanov | ttx, oh, one more thing | 12:18 |
| SergeyLukjanov | we're now in progress of merging sahara-dashboard to horizon | 12:19 |
| SergeyLukjanov | mostly all needed patches are on review, but it's lack of review to make it merged | 12:19 |
| SergeyLukjanov | so, we're now blocked by lack of reviews, I hope that it'll be better during the juno-2 or we'll need to rollback to the sahara-dashboard for juno | 12:20 |
| SergeyLukjanov | #link https://review.openstack.org/#/q/topic:bp/merge-sahara-dashboard,n,z | 12:21 |
| ttx | SergeyLukjanov: I think it's fair to raise that in the meeting | 12:23 |
| ttx | Cross-project priority communication is what it's for | 12:23 |
| SergeyLukjanov | ttx, yup, thanks | 12:23 |
| SergeyLukjanov | oh, last 3 changes failed in gate with not sahara-related issues, rechecking now... | 12:24 |
| ttx | SergeyLukjanov: add it just before "open Discussion" at https://wiki.openstack.org/wiki/Meetings/ProjectMeeting#Agenda_for_next_meeting | 12:24 |
| SergeyLukjanov | ttx, ack | 12:24 |
| *** dhellmann has quit IRC | 12:28 | |
| SergeyLukjanov | ttx, btw, we should have 2014.1.1 today, final testing atm | 12:29 |
| SergeyLukjanov | ttx, I've updated the lp page for sahara j1 | 12:30 |
| SergeyLukjanov | ttx, we're only waiting for https://review.openstack.org/#/c/94460/ to be landed | 12:30 |
| ttx | ok | 12:31 |
| ttx | SergeyLukjanov: OK, simplified version @ https://review.openstack.org/#/c/98123 | 12:46 |
| SergeyLukjanov | ttx, looking | 12:47 |
| ttx | This version of ms2version.py will work even if the release date is not defined, and for RCs | 12:48 |
| SergeyLukjanov | ttx, yup, I've tested it on sahara milestones and works good | 12:51 |
| SergeyLukjanov | ttx, +1 from me | 12:51 |
| ttx | coolthx | 12:52 |
| *** jpich has joined #openstack-relmgr-office | 13:05 | |
| ttx | dolphm: ready when you are | 14:00 |
| dolphm | ttx: o/ | 14:00 |
| ttx | #topic Keystone | 14:00 |
| ttx | #link https://launchpad.net/keystone/+milestone/juno-1 | 14:00 |
| ttx | #info 2 blueprints left | 14:01 |
| ttx | dolphm: are they both in-flight and waiting for the gate to process them ? Or do they need more reviews ? | 14:01 |
| dolphm | yes and no - we have 3 patches left to land. one i have yet to propose myself :( one is ready to gate, and the other needs reviews | 14:02 |
| ttx | dolphm: hmm, given the gate backlog, I think by EOD we should restrict juno-& targets to stuff that is queued | 14:02 |
| ttx | juno-1* | 14:02 |
| dolphm | the one i need to propose is an additional topic to round out document-v2-to-v3-transition | 14:02 |
| dolphm | that sounds fair | 14:03 |
| ttx | dolphm: you think you can propose and get it reviewed by EOD ? | 14:03 |
| dolphm | ttx: yes | 14:03 |
| ttx | OK, then just adjust at the end of your day so that it reflects review state | 14:03 |
| dolphm | ttx: will do | 14:03 |
| ttx | ideally we want to tag tomorrow, and use Thursday as a safety valve | 14:03 |
| ttx | for stuff that will get caught in gate retries | 14:04 |
| ttx | Looking at what my BP autokick script would do for keystone: | 14:05 |
| ttx | http://paste.ubuntu.com/7623707/ | 14:05 |
| ttx | That means you don't have any unprioritized blueprint | 14:05 |
| ttx | we just need to set the series goal for 3 blueprints | 14:05 |
| dolphm | yay! i tried to clean up a few last week in prep for that | 14:05 |
| ttx | so it looks like it's safe to enable the script to run for keystone ? | 14:05 |
| dolphm | ttx: ++ | 14:06 |
| ttx | coolbeans | 14:06 |
| ttx | looking at targeted bugs | 14:07 |
| ttx | https://bugs.launchpad.net/keystone/+bug/1226171 | 14:07 |
| ttx | The only thing I can find linked in there would be: | 14:07 |
| ttx | https://review.openstack.org/#/c/74214/ | 14:07 |
| ttx | Which doesn't look like a bugfix at all | 14:08 |
| dolphm | ttx: it's a juno-1 targeted bp as well | 14:08 |
| ttx | ah ok, so both are linked | 14:08 |
| ttx | I suspect that's one of the "needs reviews" ? | 14:08 |
| dolphm | ttx: yes | 14:08 |
| ttx | At this point I think it's unlikely to make it, but let's give it until EOD | 14:09 |
| dolphm | ttx: and i actually just +A'd one of the three, so we're down to 2 | 14:09 |
| ttx | This one + the one you have to propose ? | 14:09 |
| dolphm | ttx: yes | 14:09 |
| ttx | OK | 14:09 |
| ttx | #info One blueprint in flight, 2 still needing proposal/review (will be punt by EOD if not approved by then). Bug is actually covered by targeted BP | 14:10 |
| ttx | Anything you'd like to add to the meeting agenda ? | 14:10 |
| dolphm | ttx: no sir | 14:10 |
| ttx | OK ten, i'll let you work on that code | 14:10 |
| ttx | +h | 14:10 |
| dolphm | ttx: ttyl! | 14:11 |
| * dolphm puts head back into the sand | 14:11 | |
| ttx | jgriffith: ready if you're already around | 14:11 |
| *** dhellmann has joined #openstack-relmgr-office | 14:20 | |
| ttx | dhellmann: looks like jgriffith is not around, so you could fit now if you want | 14:20 |
| dhellmann | ttx: sure, sorry, my znc instance died and I didn't realize | 14:22 |
| dhellmann | I was actually online 2 hrs ago, but my irc client wasn't | 14:22 |
| ttx | that happens | 14:22 |
| ttx | dhellmann: got time now ? | 14:22 |
| dhellmann | sure | 14:23 |
| ttx | #topic Oslo | 14:23 |
| ttx | #link https://launchpad.net/oslo/+milestone/juno-1 | 14:23 |
| ttx | #link https://launchpad.net/oslo.messaging/+milestone/juno-1 | 14:23 |
| ttx | First one has 4 "undefined" blueprints, I suspect you're holding on prioritizing them on spec approval ? | 14:24 |
| dhellmann | yeah, I should go ahead and toss those to j2 as well | 14:25 |
| dhellmann | or should I move them out altogether until the specs are approved? | 14:25 |
| ttx | So the trick is, my automated script would remove those (milestoned but not prioritized) | 14:25 |
| ttx | remove == clear the milestone target field | 14:25 |
| dhellmann | that's fine | 14:25 |
| ttx | OK, just making sure that wouldn't kill your workflow | 14:25 |
| ttx | dhellmann: I think at this point you can move to j-2 anything that's not in-flight, or almost approved | 14:26 |
| ttx | given the gate backlog | 14:26 |
| dhellmann | I've been focusing on the specs, so I can bring the blueprints in as part of the approval process | 14:26 |
| dhellmann | yeah, that's going to be a lot of it | 14:26 |
| ttx | dhellmann: that's the idea yes, still working on a script to mostly automate that for yoy | 14:26 |
| dhellmann | we got a slow start on specs, since we didn't agree to do it until right before the summit | 14:26 |
| dhellmann | would the script bring blueprints in, too, or just take them out? | 14:27 |
| ttx | just take them out. The CLI tool would help you bring them in | 14:27 |
| dhellmann | cli tool? | 14:27 |
| ttx | but the automated script would just take them out | 14:27 |
| ttx | working on a spec2bp CLI that will do most of the Launchpad blueprint-filing work for you | 14:28 |
| ttx | when you approve a spec | 14:28 |
| dhellmann | oh, nice | 14:28 |
| ttx | you'd just run the tool to get that spec into LP | 14:28 |
| ttx | nice, except Lp doesn't have an API for creating specs | 14:29 |
| ttx | so it takes longer than expected | 14:29 |
| ttx | and will likely require manual steps | 14:29 |
| ttx | anyway | 14:29 |
| ttx | so you have 3 prioritized ones still in progress in that j-1 page | 14:29 |
| ttx | +1 on the oslo.messaging page | 14:29 |
| dhellmann | yeah, I'll move those to j2 by hand | 14:30 |
| ttx | If they are not already in the gate pipe to get merged, i suggest you defer them yes | 14:30 |
| ttx | same for targeted bugs | 14:30 |
| ttx | dhellmann: here is what would happen if I ran the autokick script for oslo now: | 14:31 |
| ttx | http://paste.ubuntu.com/7623815/ | 14:31 |
| ttx | basically it would kick those 4 unprioritized ones from juno-1 | 14:31 |
| ttx | If that sounds good I can run it now | 14:31 |
| dhellmann | what is "cleargoal"? | 14:31 |
| ttx | it removes the "juno" series goal to match the target milestone | 14:32 |
| dhellmann | ah, ok | 14:32 |
| ttx | (LP doesn't enforce consistency between those 2 fields) | 14:32 |
| dhellmann | sure, that all looks fine | 14:32 |
| dhellmann | and then I'll fix up the others by hand | 14:32 |
| ttx | ok, running | 14:32 |
| ttx | Let's see what would happen to oslo.messaging... | 14:32 |
| ttx | nothing there | 14:33 |
| ttx | OK, so I should be able to run that script on cron, as far as you're concerned | 14:33 |
| ttx | dhellmann: anything you'd like to add to meeting agenda ? | 14:33 |
| dhellmann | there's no juno-2 for oslo.messaging, yet, do you have a script to create those or should I do it by hand? | 14:34 |
| ttx | dhellmann: I haz script | 14:34 |
| ttx | #action ttx to create oslo.messaging milestones | 14:34 |
| dhellmann | ah, mark created a "1.4.0" milestone | 14:34 |
| dhellmann | we can keep that, but we should add the intermediate ones | 14:35 |
| ttx | dhellmann: ok | 14:35 |
| dhellmann | so a little cleanup work for me, is there anything else we need to talk about this week? | 14:36 |
| ttx | nope | 14:36 |
| dhellmann | cool, sorry for the time snafu | 14:36 |
| ttx | unless you have something to add to meeting agenda, we are done | 14:36 |
| ttx | We'll try to tag tomorrow | 14:36 |
| * mestery is ready when ttx is ready. | 14:37 | |
| ttx | if what's in-flight by EOD makes it by then | 14:37 |
| ttx | yep, david-lyle is not around, so skipping Horizon | 14:37 |
| ttx | #topic Neutron | 14:37 |
| ttx | mestery: o/ | 14:37 |
| dhellmann | ttx: ok, thanks | 14:37 |
| ttx | #link https://launchpad.net/neutron/+milestone/juno-1 | 14:37 |
| mestery | hi! | 14:37 |
| mestery | Yes, that should be accurate now. | 14:37 |
| ttx | #info 4 blueprints still in progress on that page | 14:37 |
| *** kgriffs|afk is now known as kgriffs | 14:38 | |
| mestery | I think we can land 2 of them by Thursday, maybe 3. | 14:38 |
| ttx | mestery: as I suggested to others, I think given the gate backlog we should restrict targets to stuff already approved and in flight | 14:38 |
| mestery | ttx: OK, that makes sense, no issues on my part then. | 14:38 |
| ttx | except milestone-critical issues | 14:38 |
| ttx | mestery: maybe give the reviews until EOD and then punt anything that's not in the pipe ? | 14:38 |
| mestery | This one (https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac) has a patch which is in re-check, and can then be merged. | 14:38 |
| mestery | ttx: Perfect | 14:39 |
| mestery | I'll send a note to the ML to let the neutron know the plan for Juno-1 then. | 14:39 |
| ttx | You can start scrubbing the list if anything will definitely not make it | 14:39 |
| mestery | Yes, I will do that. | 14:39 |
| ttx | and then by EOD we reduce to what's in-flight | 14:39 |
| ttx | then hopefully it merges tomorrow and we tag | 14:39 |
| ttx | and then we have Thursday to handle Murphy's law | 14:40 |
| mestery | Cool, pperfect | 14:40 |
| mestery | ttx: :P | 14:40 |
| ttx | mestery: on the bugs side... | 14:40 |
| ttx | That's a lot of targeted bugs | 14:40 |
| ttx | I think same rules apply | 14:40 |
| mestery | I agree, that makes sense. | 14:40 |
| ttx | remove now those that are far away in review, reduce list to in-flight stuff by EOD | 14:41 |
| mestery | I'll scrub the bugs today as well and do the same thing as for BPs: Only things in flight by EOD have a chance at Juno-1. | 14:41 |
| ttx | ack | 14:41 |
| ttx | Looking at what my autokick cleanup script would do to neutron Bps now | 14:41 |
| * mestery has been grooming his milestones in LP like a freshly cut lawn. :) | 14:42 | |
| ttx | http://paste.ubuntu.com/7623860/ | 14:43 |
| mestery | I think it would kick nothing out, I was looking at Juno-2 (and even Juno-3) this week yet. | 14:43 |
| ttx | most of those are just series goal alignment | 14:43 |
| ttx | only one kick | 14:43 |
| * mestery looks. | 14:43 | |
| ttx | tenant-delete (from juno-3) | 14:43 |
| mestery | I think that makes sense. | 14:43 |
| mestery | That one may have snuck in. :) | 14:43 |
| ttx | If you approve I can run the script now | 14:43 |
| ttx | and then start making it a cron starting tomorrow morning | 14:43 |
| mestery | It looks good to me, thanks for writing it! | 14:44 |
| ttx | ok, processing | 14:44 |
| ttx | Anything you'd like to add to meetign agenda for today ? | 14:44 |
| mestery | Possibly something around the "ssh timeout" bug from the gate. | 14:45 |
| mestery | I've debugged this, and it actually looks like a nova issue: https://bugs.launchpad.net/neutron/+bug/1323658 | 14:45 |
| ttx | mestery: sounds like a good topic | 14:45 |
| mestery | I alerted nova team in-channel, but would be good to get broader eyes on this one. | 14:45 |
| ttx | mestery: just edit https://wiki.openstack.org/wiki/Meetings/ProjectMeeting | 14:45 |
| mestery | jogo eyeballed it quickly last night. | 14:45 |
| mestery | ttx: Will do, and thanks! | 14:45 |
| ttx | great thx! | 14:45 |
| ttx | jpich: around ? | 14:45 |
| jpich | yep | 14:45 |
| ttx | #topic Horizon | 14:45 |
| * mestery wanders off. :) | 14:46 | |
| ttx | #link https://launchpad.net/horizon/+milestone/juno-1 | 14:46 |
| ttx | 19 (!) blueprints still targeted | 14:46 |
| jpich | I removed the stuff that wasn't started but I take it it's not sufficient at this stage? | 14:46 |
| ttx | jpich: at this point it's unlikely to make it to juno-1 if it's not aready approved and in the gate pipe | 14:47 |
| jpich | I see | 14:47 |
| ttx | so I would suggest you remove anything that's not nearing final approval | 14:47 |
| jpich | I think there's a couple that might be approved today but probably not many | 14:47 |
| ttx | well, push it back to j-2 | 14:47 |
| jpich | Ok, will do | 14:47 |
| ttx | then by the end of the day just remove anything that is not queued in the gate | 14:48 |
| ttx | goal being to tag sometimes tomorrow, Thursday if things go wrong | 14:48 |
| jpich | Ok | 14:48 |
| ttx | While you're at it you can set a priority for the two "undefined" ones and add an assignee to the unassigned one | 14:48 |
| ttx | jpich: same for the bugs; you still have 5 targeted | 14:49 |
| jpich | Sure, didn't noticed the unassigned one | 14:49 |
| ttx | by the end of the day it would be good to only have those that are in the queue | 14:49 |
| jpich | Makes sense | 14:49 |
| ttx | jpich: "end of day" can include early tomorrow morning, since you seem to be in France right now | 14:50 |
| jpich | Indeed :) Cheers | 14:50 |
| ttx | basically tomorrow we need to have the list reflect the picture of what's approved and waiting in the gate pipe | 14:51 |
| ttx | and then pray it all makes it soon enough* | 14:51 |
| jpich | heh | 14:51 |
| ttx | jpich: are you or mrunge being present at the cross-project meeting at 21:00 UTC ? | 14:51 |
| jpich | lcheng should be there | 14:52 |
| ttx | SergeyLukjanov had a topic to discuss with Horizon folk | 14:52 |
| ttx | ok, good | 14:52 |
| jpich | Ok I'll let him know | 14:52 |
| ttx | Anything you'd like to add to the agenda yourself ? | 14:52 |
| jpich | No, though I'm curious about that script that removed blueprint with no priority you mentioned earlier? | 14:53 |
| ttx | jpich: it's for projects using -specs repos | 14:53 |
| ttx | and if my book is correct Horizon doesn't | 14:53 |
| jpich | Aah! Ok | 14:53 |
| jpich | Yup, that's my understanding too | 14:53 |
| jpich | Is there an agenda somewhere for these PTL syncs? | 14:54 |
| ttx | jpich: the idea being, not asking contributors to file a spec AND a blueprint as the entry point for submitting features | 14:54 |
| jpich | That totally makes sense | 14:54 |
| ttx | and use blueprints as a PTL-only tool | 14:54 |
| ttx | (or at least the milestone view) | 14:54 |
| ttx | so we remove anythign not prioritized (blessed by PTL) from BP milestone views | 14:54 |
| ttx | For non-specs using projects, the script only adjusts the series goal | 14:55 |
| ttx | which is mostly harmless | 14:55 |
| ttx | (script makes sure it's coherent with what's in the "milestone target" field) | 14:55 |
| jpich | Yup, cool, thank you for the explanation | 14:56 |
| ttx | no there isn't an agenda for the sync. We publish logs though :) | 14:56 |
| ttx | ok, ttyl, thanks for covering Horizon here | 14:56 |
| jpich | Ok! Thanks | 14:56 |
| notmyname | ttx: can we do our sync early? | 15:04 |
| ttx | on a call | 15:05 |
| ttx | notmyname: ^ | 15:05 |
| ttx | will ping you if I escape early | 15:05 |
| notmyname | ack | 15:05 |
| notmyname | ttx I've got to commute. I'll be back online ASAP | 15:17 |
| *** markwash has joined #openstack-relmgr-office | 15:18 | |
| *** jpich has left #openstack-relmgr-office | 15:27 | |
| ttx | notmyname: ready when you are | 15:30 |
| ttx | (still on my call but parallelizing) | 15:30 |
| ttx | zaneb: if you're around now, we can switch, notmyname is apparently lost in commute | 15:42 |
| zaneb | sure, np | 15:42 |
| ttx | #topic Heat | 15:42 |
| ttx | #link https://launchpad.net/heat/+milestone/juno-1 | 15:42 |
| ttx | 6 blueprints still open | 15:43 |
| zaneb | I did some gardening :) | 15:43 |
| ttx | zaneb: given gate backlog, I think it will be more realistic to only keep stuff that's in-flight or that will be approved by the end of the day | 15:43 |
| zaneb | these have mostly been delayed by the gate issues | 15:43 |
| ttx | that way we cna tag tomorrow, Thursday in the worst case | 15:43 |
| zaneb | actually, I suspect that first one has been merged, I will check on it | 15:44 |
| ttx | zaneb: do you think only keeping stuff that is in-flight on the target milestone by EOD is agreeable ? | 15:44 |
| zaneb | that sounds fine | 15:44 |
| ttx | same for bugs | 15:44 |
| zaneb | I think most of this stuff actually is in-flight | 15:45 |
| zaneb | but it's all low-priority anyway | 15:45 |
| ttx | I doubt all those bugs are in flight :) | 15:45 |
| ttx | just defer to j-2 anything that doesn't have an approved review | 15:45 |
| zaneb | no, the bugs are not | 15:45 |
| zaneb | ok | 15:45 |
| * ttx looks at what the autokick script would do to your blueprints | 15:46 | |
| ttx | http://paste.ubuntu.com/7624117/ | 15:46 |
| ttx | it would adjust series goal on a number of things | 15:46 |
| ttx | and remove 3 BPs from j-2 | 15:47 |
| ttx | does that sounds acceptable ? If yes I can run it now | 15:47 |
| zaneb | yep, that all looks reasonable | 15:48 |
| ttx | (goal being to only keep blessed blueprints on those targeted lists, and avoid asking contributors to file a spec AND a blueprint) | 15:48 |
| ttx | zaneb: ok, I'll run the script now and add you to the cron starting tomorrow | 15:48 |
| zaneb | cool, thanks | 15:48 |
| ttx | it should result in a lot less manual scrubbing and maintenance of that list | 15:49 |
| zaneb | +1 for that :) | 15:49 |
| ttx | Ok, that's all I had -- basically by EOD try to reduce the juno-1 list to in-flight stuff, then we plan to tag on Wednesday when all that finally merges | 15:50 |
| ttx | anything you wanted to discuss in the meeting today ? | 15:50 |
| zaneb | nope, that all sounds good | 15:50 |
| notmyname | ttx: here now | 15:50 |
| zaneb | thanks ttx | 15:50 |
| ttx | great timing | 15:50 |
| ttx | zaneb: thx! | 15:51 |
| ttx | #topic Swift | 15:51 |
| notmyname | hello | 15:51 |
| ttx | notmyname: hi! | 15:51 |
| ttx | Can't do a more direct medium today, I can do that early tomorrow though if you want | 15:51 |
| notmyname | hmm... | 15:51 |
| ttx | (PST) | 15:51 |
| ttx | Or we can just talk here | 15:51 |
| notmyname | ok. so let's cover the high level today, and you can determine if you want something else tomorrow | 15:52 |
| ttx | so... next swift release? | 15:52 |
| notmyname | yes. | 15:52 |
| notmyname | ...just getting in...trying to organize my thoughts... | 15:52 |
| notmyname | storage policies is going well. last couple of things should be finished today | 15:53 |
| notmyname | which gives us the goal of merging to master this week | 15:53 |
| notmyname | and I'm working with mordred to figure out how to make that happen in a reasonable time frame, given the status of the gate | 15:53 |
| notmyname | ie with the current 27-29 patches, the current gate would take weeks to months to merge | 15:54 |
| notmyname | so, let's assume all that's solved | 15:54 |
| notmyname | so from there, we will land a couple of other pending, non-SP patches and then have a release | 15:55 |
| notmyname | well, actually an RC | 15:55 |
| ttx | got disconnected, missing any message between "master this week" and "ie with the current" | 15:55 |
| notmyname | just on: "and I'm working with mordred to figure out how to make that happen in a reasonable time frame, given the status of the gate" | 15:55 |
| notmyname | *one | 15:56 |
| ttx | ok | 15:56 |
| ttx | notmyname: IIRC we would have an RC tagged on master, rather than do the milestone-proposed dance like for the "coordinated" release, right ? | 15:56 |
| notmyname | so assuming those are all landed, then we need an extended RC period for this release, given the scope of what's in it. and I've already got soft commitments from at least 3 companies to do QA | 15:56 |
| notmyname | correct. RC tagged on master, but would need a branch if things are found that need to be in the release | 15:57 |
| ttx | notmyname: ack | 15:57 |
| ttx | #info Swift RC tagged on master, but would need a branch if things are found that need to be in the release | 15:57 |
| notmyname | so what I'm thinking now is RC this week (assuming gating issues solved), then a 2 week RC. assuming things are good, then formal release at the end of the two weeks | 15:58 |
| ttx | notmyname: sounds good | 15:58 |
| notmyname | note that this could change depending on what, if anything is found in the RC period | 15:58 |
| ttx | notmyname: do you have a version number in your head ? | 15:58 |
| notmyname | with me so far? :-) | 15:58 |
| *** markwash has quit IRC | 15:58 | |
| notmyname | ok. as to the version number (please don't info this yet) ;-) | 15:59 |
| ttx | (so that I can create a $VERSION-rc1 milestone) | 15:59 |
| notmyname | the next release with storage policies will be 2.0 | 15:59 |
| ttx | ooooh. | 15:59 |
| ttx | That will be our secret. | 15:59 |
| notmyname | and since that carries some bigger meaning, you can imagine that it will garner some additional marketing efforts outside of the dev community | 16:00 |
| notmyname | and I'm working on coordinating those things now | 16:00 |
| notmyname | so for you and me, this is a release like normal | 16:00 |
| ttx | notmyname: do you prefer me to hold on 2.0.0-rc1 milestone creation ? | 16:00 |
| notmyname | ttx: yes. I'd prefer that we create that when it's ready to happen. the reality of the gate is that we'll have some time to kill there ;-) | 16:01 |
| notmyname | ie instead of doing it today | 16:01 |
| ttx | notmyname: ok | 16:01 |
| notmyname | ok, one last thing there | 16:01 |
| notmyname | one more confounding factor | 16:01 |
| ttx | #info Next Swift release hopefully in RC at end of week (depending on gate health) | 16:01 |
| notmyname | I'm having surgery on my collar bone on thursday, so I'm not sure about my ability to click buttons. but I will, or get someone (prob clayg or torgomatic) to proxy for me if necessary | 16:02 |
| notmyname | I have no idea what recovery time will be | 16:02 |
| ttx | notmyname: OK. Get well soon! | 16:02 |
| notmyname | thanks | 16:03 |
| ttx | #action ttx to buy a bike helmet on Amazon | 16:03 |
| notmyname | I think that's the summary. obviously there are a lot of details there yet to be worked out. do you need anything else from me right now? | 16:03 |
| notmyname | yes!!! | 16:03 |
| ttx | notmyname: nope, sounds good. Anything you wanted to add to meeting agenda for tonight ? | 16:04 |
| notmyname | I'm good | 16:04 |
| ttx | ok, ttyl then | 16:04 |
| ttx | SlickNik: if you're around you can jump the queue | 16:04 |
| ttx | as we lost markwash | 16:05 |
| *** markwash has joined #openstack-relmgr-office | 16:07 | |
| ttx | markwash: o/ | 16:08 |
| markwash | ttx: hi sorry didn't realize my connection had dropped | 16:08 |
| ttx | #topic Glance | 16:08 |
| ttx | markwash: that happens | 16:08 |
| ttx | dhellmann had the same excuse :) | 16:08 |
| markwash | especially when you're fumbling with a laptop and vpn and not paying attention :-) | 16:08 |
| * dhellmann is a trend-setter | 16:08 | |
| ttx | https://launchpad.net/glance/+milestone/juno-1 | 16:08 |
| * markwash covers his eyes | 16:08 | |
| ttx | 2 blueprints still up there | 16:09 |
| markwash | looks like some bumping is in order :-( | 16:09 |
| ttx | markwash: are any of them likely to merge before we need to tag stuff ? | 16:09 |
| ttx | i.e. ~ tomorrow ? | 16:09 |
| markwash | no | 16:09 |
| ttx | markwash: ok, you should probably bump everything then | 16:10 |
| ttx | and if you're not waiting on something specific to get merged, we cna probably tag soon | 16:10 |
| markwash | no wait | 16:10 |
| * ttx searches the gate pipe for glance changes | 16:11 | |
| * ttx waits | 16:12 | |
| * markwash chuckles | 16:12 | |
| ttx | markwash: just send me a SHA to tag "juno-1" before EOD tomorrow and I'll make it happen ? | 16:13 |
| markwash | okay sounds good | 16:13 |
| ttx | markwash: you should also clean up the bugs list | 16:13 |
| markwash | ah good point | 16:13 |
| markwash | ttx based on my look at gerrit there is nothing in the queue at all right now | 16:13 |
| ttx | markwash: I'm fine with keeping anything that you think you can get approved before EOD in the list | 16:14 |
| markwash | so we can just go with tagging 9c87169c78a01f7c057734f641d428a8804334f9 | 16:14 |
| ttx | but I don't see anything | 16:15 |
| ttx | #info Glance juno-1 can be tagged on 9c87169c78a01f7c057734f641d428a8804334f9 | 16:15 |
| ttx | markwash: OK, will do it before the TC meeting, that gives you some time to cancel :) | 16:15 |
| ttx | so let's see what the autokick script would do to your BPs | 16:16 |
| ttx | http://paste.ubuntu.com/7624251/ | 16:16 |
| ttx | markwash: apart from adjusting a few series goals, it would just remove te juno-2 target milestone from storage-policies-vmware-store | 16:16 |
| ttx | (because that spec is not prioritized) | 16:17 |
| markwash | okay I'm going to have a second look at that one to decide if it should go ahead and be prioritized | 16:17 |
| ttx | markwash: OK, ideally do it before the project meeting as I'd like to set up that script in cron soon | 16:18 |
| markwash | yeah, we just missed prioritization in our previous discussions | 16:18 |
| * markwash has a cat that is trying to contribute to the conversation | 16:18 | |
| ttx | #action markwash to figure out what to do with storage-policies-vmware-store | 16:18 |
| markwash | done | 16:18 |
| markwash | I already prioritized it | 16:18 |
| ttx | oh. ok | 16:18 |
| ttx | so I can run the script now | 16:18 |
| markwash | absolutely | 16:18 |
| ttx | let's do that | 16:18 |
| ttx | anything you'd liek to add to meetign agenda today ? | 16:19 |
| ttx | damn fingers | 16:19 |
| ttx | your hands should be full with the TC items already | 16:19 |
| markwash | I don't think so, I'm curious if PTL ish folks are concerned about the catalog or graffiti stuff but I guess I should just rely on the ML and them raising their own points | 16:19 |
| markwash | yeah, speaking of TC | 16:20 |
| markwash | and specifically glance gap analysis | 16:20 |
| ttx | you can informally raise it in open discussion, if you're still around by then | 16:20 |
| markwash | I *think* I'm ready for that discussion | 16:20 |
| ttx | markwash: I'm sure you are | 16:20 |
| markwash | it looks like we don't really have any gaps, except maybe with docs | 16:20 |
| markwash | is the format just: folks ask me questions about gaps they think might be there? | 16:21 |
| ttx | markwash: yeah, just a formality | 16:21 |
| markwash | or do I need a more formal input to the process | 16:21 |
| markwash | s/need/need to provide/ | 16:21 |
| ttx | nope, we'll just go through the list and ask questions if we have doubts | 16:21 |
| markwash | okay great | 16:21 |
| markwash | then bring it on! | 16:21 |
| markwash | :-) | 16:21 |
| ttx | I don't expect we'll have that many, but we need to check | 16:21 |
| ttx | cool | 16:21 |
| ttx | SlickNik: around? | 16:21 |
| ttx | markwash: thx! | 16:22 |
| SlickNik | ttx here | 16:22 |
| ttx | #topic Trove | 16:22 |
| markwash | thank you! | 16:22 |
| ttx | https://launchpad.net/trove/+milestone/juno-1 | 16:22 |
| ttx | 5 BPs still on the map | 16:22 |
| SlickNik | Yup, 1 or 2 are really close to merging. | 16:22 |
| ttx | SlickNik: so I think we need to reduce that list to stuff that has all apporvals lined up, by EOD | 16:23 |
| SlickNik | And I'm going to bump the other 3. | 16:23 |
| ttx | SlickNik: sounds good | 16:23 |
| SlickNik | I can do that. | 16:23 |
| ttx | Same thing for bugs | 16:23 |
| ttx | Get them approved and in the gate pipe by end of day, or bump them | 16:23 |
| ttx | so that we have a clear view of the last milestone tag blockers | 16:23 |
| SlickNik | Actually let me bump the ones I know won't make it right now. | 16:23 |
| ttx | even better! | 16:24 |
| ttx | Goal being to tag sometimes tomorrow, and keep Thursday as a safety net | 16:24 |
| ttx | Just email or IRC me a SHA when you have all you want in, and I'll push the tag to master | 16:24 |
| SlickNik | Okay, will send you the SHA on IRC by EOD today | 16:25 |
| ttx | SlickNik: it's fine if you still have a few in-flight and we tag on Wednesday | 16:26 |
| ttx | but if you've got all you think you'll have, then yes, let's tag | 16:26 |
| SlickNik | There's a couple in flight. Gonna get core to close on the reviews for them today. | 16:27 |
| SlickNik | Will send you the SHA once that's done. | 16:27 |
| ttx | SlickNik: OK, as long as that happens before EOD tomorrow we're good | 16:27 |
| ttx | SlickNik: anything you wanted to add to meeting agenda for today ? | 16:27 |
| ttx | jgriffith: around? | 16:28 |
| SlickNik | Nope. | 16:28 |
| ttx | SlickNik: ok, thx! | 16:28 |
| SlickNik | ttx , Thank you! | 16:29 |
| SlickNik | Will catch you later. :) | 16:29 |
| ttx | And that concludes our 1:1 syncs for today | 16:29 |
| ttx | Thanks everyone | 16:29 |
| ttx | #endmeeting | 16:29 |
| openstack | Meeting ended Tue Jun 10 16:29:44 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:29 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-10-08.41.html | 16:29 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-10-08.41.txt | 16:29 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-06-10-08.41.log.html | 16:29 |
| *** markmcclain has joined #openstack-relmgr-office | 16:36 | |
| *** eglynn has quit IRC | 17:06 | |
| *** markmcclain has quit IRC | 17:25 | |
| *** markmcclain has joined #openstack-relmgr-office | 17:29 | |
| *** markwash_ has joined #openstack-relmgr-office | 17:41 | |
| *** markwash has quit IRC | 17:43 | |
| *** markwash_ is now known as markwash | 17:43 | |
| *** kgriffs is now known as kgriffs|afk | 18:35 | |
| *** markmcclain has quit IRC | 18:56 | |
| jgriffith | ttx: still about? | 19:00 |
| *** SlickN1k has quit IRC | 19:01 | |
| SergeyLukjanov | ttx, last j1 sahara change failed to be merged due to the not sahara-related issue, I've just send it to recheck (https://review.openstack.org/#/c/94460/) | 19:06 |
| SergeyLukjanov | ttx, it's ok to make cut w/o this change and we'll backport it when it'll be landed | 19:07 |
| ttx | jgriffith: o/ | 19:33 |
| ttx | SergeyLukjanov: still has time to land | 19:34 |
| jgriffith | ttx: hola | 19:35 |
| jgriffith | ttx: sorry... playing tag today | 19:35 |
| ttx | jgriffith: quick look at https://launchpad.net/cinder/+milestone/juno-1 | 19:36 |
| jgriffith | ttx: oi | 19:36 |
| ttx | jgriffith: we need to refine it to only contain stuff likely to land in the next day | 19:36 |
| ttx | the rest you can push to j-2 | 19:36 |
| ttx | that includes bugs | 19:36 |
| jgriffith | Yeah, I started that effort | 19:36 |
| jgriffith | I'll finish it here now | 19:37 |
| ttx | + | 19:37 |
| SergeyLukjanov | ttx, ok | 19:37 |
| ttx | jgriffith: ok, would be awesoe if you can complete that before the meeting | 19:37 |
| jgriffith | ttx: doing it right now | 19:38 |
| jgriffith | ttx: thanks | 19:38 |
| ttx | Also looking at the autokick/autoclean script for the clueprints | 19:38 |
| ttx | if I ran it now here is what it would do: | 19:38 |
| ttx | http://paste.ubuntu.com/7625146/ | 19:38 |
| ttx | it would adjust series goal for a boatload of BPs, but also remove milestones from a number of j2 blueprints | 19:39 |
| jgriffith | hmm | 19:39 |
| ttx | (the unprioritized ones) | 19:39 |
| jgriffith | That's actually looking fairly in line with my current view of the world | 19:39 |
| ttx | If those 6 milestone target removals are OK with you i can run te script now and set it to run on cron | 19:40 |
| jgriffith | the KICK's in J-2 I need to fix | 19:40 |
| jgriffith | ttx: yeah, I think that's fine | 19:40 |
| jgriffith | ttx: and I can adjust the ones that I need to fix in J2 | 19:40 |
| ttx | jgriffith: so shallI wait until you're done with adjusting, before I run script ? | 19:40 |
| jgriffith | I kinda want you to run it TBH | 19:41 |
| ttx | jgriffith: now? | 19:41 |
| jgriffith | and then adjust if necessary, test your script so to speak | 19:41 |
| jgriffith | and like I said based on memory this looks pretty good to me | 19:41 |
| ttx | OK, running it then. You have the list of affected BPs | 19:41 |
| jgriffith | ie what I was going to do anyway | 19:41 |
| jgriffith | ttx: thanks, I'll let you know if something awfully unexpected happens from my point of view | 19:42 |
| jgriffith | and I'll give everything a once over prior to our meeting this afternoon | 19:42 |
| ttx | jgriffith: ack, talk to you then | 19:42 |
| jgriffith | ttx: appreciate it | 19:42 |
| *** markmcclain has joined #openstack-relmgr-office | 20:02 | |
| *** dhellman_ has joined #openstack-relmgr-office | 20:37 | |
| *** dhellmann_ has joined #openstack-relmgr-office | 20:41 | |
| *** kgriffs|afk is now known as kgriffs | 20:46 | |
| *** dhellmann_ has quit IRC | 20:48 | |
| *** dhellmann_ has joined #openstack-relmgr-office | 20:48 | |
| *** dhellmann has quit IRC | 20:54 | |
| *** dhellmann_ is now known as dhellmann | 20:54 | |
| *** dhellmann has quit IRC | 20:56 | |
| *** dhellman_ is now known as dhellmann | 20:56 | |
| *** zaneb has quit IRC | 21:35 | |
| *** dhellmann has quit IRC | 21:55 | |
| *** dhellmann has joined #openstack-relmgr-office | 21:55 | |
| *** zaneb has joined #openstack-relmgr-office | 23:17 | |
| *** kgriffs is now known as kgriffs|afk | 23:35 | |
| *** zaneb has quit IRC | 23:37 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!