| ttx | nikhil_k: around now | 07:48 |
|---|---|---|
| *** flaper87 has quit IRC | 07:56 | |
| *** flaper87 has joined #openstack-relmgr-office | 07:56 | |
| ttx | asalkeld: around? | 08:59 |
| asalkeld | ttx: hi | 09:01 |
| ttx | asalkeld: hey, so 4 left, of which only convergence-push-data seems really close | 09:02 |
| asalkeld | so: breakpoint we might try FFE | 09:03 |
| ttx | I suspect we'll need FFE or defer for the others | 09:03 |
| asalkeld | not sure what the proceedure for that is | 09:03 |
| ttx | We can discuss it here and now | 09:03 |
| ttx | asalkeld: basically FFE is a question with 3 dimensions | 09:03 |
| asalkeld | ttx: ok | 09:03 |
| ttx | depends on how disruptive the change is (and therefore likely to break other teams that try to test k3) | 09:04 |
| asalkeld | not very | 09:04 |
| ttx | depends on how much time it will take (and therefore likely to disrupt other teams for a longer time) | 09:04 |
| asalkeld | there are 3 patches i think - 1 should go in soon | 09:04 |
| asalkeld | one is struggling with tests | 09:04 |
| ttx | and depends on how many there are (since that will distract reviewers from RC bugfixing/testing) | 09:04 |
| asalkeld | and the other is a functional test | 09:05 |
| ttx | Basaiclly, if there is only one, it's a no-brainer | 09:05 |
| asalkeld | zane and shardy and shadower are all helping out | 09:05 |
| asalkeld | so i have good confidence it will be done well | 09:05 |
| ttx | if you add more, you need to make sure (1) they are very close from being finalized and (2) they won't change the world | 09:05 |
| asalkeld | ok | 09:06 |
| asalkeld | ttx: where do i need to "register" them? | 09:06 |
| ttx | The test can be added without FFE (i.e. consider the spec done and log a RC1 bug to cover for missing test) | 09:06 |
| asalkeld | will do | 09:06 |
| ttx | Just add them to RC1 | 09:06 |
| asalkeld | ok | 09:06 |
| asalkeld | ttx: one more question the mistral resoruces | 09:06 |
| asalkeld | they go into contrib/ | 09:07 |
| asalkeld | (not really a part of the realease) | 09:07 |
| asalkeld | can we merge that when every we want? | 09:07 |
| asalkeld | should not effect strings | 09:07 |
| ttx | hmm, yeah, taht's probably very low in the second dimension I mentioned above, so ok | 09:07 |
| asalkeld | k | 09:07 |
| ttx | I mean first dimension (disruption) | 09:08 |
| asalkeld | so i just target those blueprints to rc1 | 09:08 |
| ttx | So to summarize... | 09:08 |
| ttx | convergence-push-data should merge later today | 09:08 |
| asalkeld | yip | 09:08 |
| ttx | if you can ghet a second +2 on it | 09:08 |
| ttx | stack-breakpoint will FFE | 09:09 |
| asalkeld | i am hopeful with the breakpoints too | 09:09 |
| asalkeld | ttx: what is the deadline for k3? | 09:09 |
| ttx | mistral-resources-for-heat will FFE | 09:09 |
| asalkeld | (actual time ) | 09:09 |
| ttx | convergence-lightweight-stack will defer to Liberty | 09:09 |
| asalkeld | ttx: agree - sounds right | 09:09 |
| ttx | did I get it right ? | 09:09 |
| asalkeld | yip | 09:10 |
| ttx | asalkeld: the sooner the better -- in all cases before 21:00 utc today | 09:10 |
| asalkeld | ok, that's what i needed | 09:10 |
| asalkeld | thanks | 09:10 |
| ttx | how about I cut it when convergence-push-data is in | 09:10 |
| asalkeld | sure, could do that | 09:10 |
| ttx | and then apply above decisions on the others if they missed it | 09:10 |
| asalkeld | ok | 09:11 |
| asalkeld | i'll let everyone know | 09:11 |
| asalkeld | re-targetting now | 09:11 |
| ttx | so priority is https://review.openstack.org/#/c/161306/ | 09:12 |
| ttx | you can keep them in k3 right now, one never knows | 09:12 |
| ttx | but I'll move them out when I tag if necessary | 09:12 |
| asalkeld | ok | 09:13 |
| asalkeld | thanks ttx | 09:13 |
| ttx | asalkeld: should be all set by the time you get up tomorrow | 09:13 |
| asalkeld | nice :-) | 09:14 |
| ttx | just give me some +2s on https://review.openstack.org/#/c/161306/ and I'll do the rest | 09:14 |
| asalkeld | someone looking at it now | 09:15 |
| asalkeld | ttx: what's the exact date of rc1? | 09:16 |
| ttx | there is no date | 09:16 |
| ttx | you ahve a list of bugs | 09:16 |
| ttx | and we tag when you fix them all | 09:16 |
| asalkeld | ok | 09:16 |
| ttx | (or accept them as known bugs) | 09:16 |
| asalkeld | roughly begining of april? | 09:17 |
| ttx | To be in good shape, you generally have to hit RC1 2-3 weeks after FF | 09:17 |
| asalkeld | ok should be doable | 09:17 |
| ttx | See for example http://ttx.re/images/havana-rcs.png for how it went in havana | 09:18 |
| ttx | *that graph is the number of bugs targeted to the next RC | 09:18 |
| ttx | You can see that most projects hit RC1 around the same date | 09:19 |
| ttx | (or week) | 09:19 |
| asalkeld | all the bugs just disapear;) | 09:19 |
| ttx | then most discovered enough issues to warrant a RC2 | 09:19 |
| ttx | then a few RC3s and RC4s as-needed | 09:19 |
| ttx | bugs don't disappear, at one point we just need to accept to live with them | 09:20 |
| asalkeld | thanks that's useful | 09:20 |
| asalkeld | i know, just kidding | 09:20 |
| ttx | so you just remove bugs from the RC-blocking list | 09:20 |
| ttx | or fix them :) | 09:20 |
| *** zz_johnthetubagu is now known as johnthetubaguy | 09:20 | |
| asalkeld | ttx: got anything else to cover? | 09:21 |
| ttx | asalkeld: nope | 09:21 |
| asalkeld | cool, time for an ale | 09:21 |
| ttx | I'll grab coffee now | 09:21 |
| asalkeld | :-) | 09:21 |
| ttx | johnthetubaguy: I'll be back in 5min | 09:22 |
| *** asalkeld has left #openstack-relmgr-office | 09:22 | |
| johnthetubaguy | I am going to head for some coffee too, I will be in a better mood that way | 09:23 |
| ttx | back | 09:27 |
| ttx | cells-v2-mapping looks complete to me | 09:30 |
| johnthetubaguy | Sorry, that sounds possible, double checking... | 09:32 |
| ttx | isolate-scheduler-db looks very close | 09:32 |
| johnthetubaguy | I think thats the one patch now | 09:33 |
| ttx | yes | 09:33 |
| ttx | servicegroup-api-is-up-host-topic looks pretty close too | 09:33 |
| ttx | v2-on-v3-api and kilo-objects might squeeze a couple more patches in today too | 09:34 |
| ttx | but won't "complete" | 09:34 |
| johnthetubaguy | v2 on v3 has a hit list they care about, let me check that | 09:35 |
| ttx | So in summary... we could tag later today, hopefully when servicegroup-api-is-up-host-topic and isolate-scheduler-db merge their last patches | 09:35 |
| ttx | At that point v2-on-v3-api and kilo-objects should have a couple merged more as well | 09:36 |
| johnthetubaguy | that sounds like a good plan | 09:36 |
| ttx | For the others, I think the road goes to FFE or defer | 09:36 |
| johnthetubaguy | I will go try push a few over the line now | 09:36 |
| johnthetubaguy | I think thats fair | 09:37 |
| johnthetubaguy | we should discuss which ones you would want to veto a Feature Freeze on, but we can catch up tomorrow morning on that if you like? | 09:37 |
| johnthetubaguy | well, agree the ones that sounds too scary for a FFE, anyways | 09:37 |
| ttx | that means the critical list is: https://review.openstack.org/#/c/149923/ https://review.openstack.org/#/c/149924/ https://review.openstack.org/#/c/160513/ | 09:38 |
| ttx | We can discuss FFEs vs. defer now if you prefer | 09:38 |
| johnthetubaguy | OK, I will go through and make sure we don't need to add to that, but that looks good for now | 09:39 |
| johnthetubaguy | OK | 09:39 |
| johnthetubaguy | so the aim is to reduce risk, and reduce distractions I guess? | 09:39 |
| ttx | as some of them might just be considered "partial" and completed | 09:39 |
| ttx | I posted the rationale above, 3 dimensions: | 09:39 |
| ttx | depends on how disruptive the change is (and therefore likely to break other teams that try to test k3) | 09:39 |
| ttx | depends on how much time it will take (and therefore likely to disrupt other teams for a longer time) | 09:39 |
| ttx | and depends on how many there are (since that will distract reviewers from RC bugfixing/testing) | 09:40 |
| johnthetubaguy | perfect | 09:40 |
| ttx | basically, if one is obviously open-ended, no point in FFEing it at all | 09:40 |
| ttx | since it will have no end anyway | 09:40 |
| ttx | so let's see, assuming we wait for servicegroup-api-is-up-host-topic and isolate-scheduler-db to complete (and grant them automatic exceptions if they don't) | 09:41 |
| ttx | * https://blueprints.launchpad.net/nova/+spec/v2-on-v3-api | 09:41 |
| johnthetubaguy | this is an interesting one, we really want this in, and its blocked waiting for jay to do a review, which he promised yesterday: https://review.openstack.org/#/c/154521/ | 09:41 |
| ttx | isn't that https://blueprints.launchpad.net/nova/+spec/online-schema-changes ? | 09:42 |
| johnthetubaguy | yes, sorry, thats the one | 09:42 |
| ttx | ok, let's talk v2-on-v3 first | 09:42 |
| johnthetubaguy | sure, sorry, lets go in order | 09:43 |
| ttx | could this one be considered "complete" wherever it stands at tag time ? | 09:43 |
| johnthetubaguy | so some of this is now just clean up, we have the guts of what we need, as I understand it | 09:43 |
| johnthetubaguy | there is a risk around the policy stuff, we don't what the upgrade impact of people using the wrong policy, but we have a lot of that merged now I think | 09:43 |
| ttx | COuld use RC bugs to cover the cleanup | 09:43 |
| johnthetubaguy | yes, that would track it better | 09:44 |
| ttx | as long as the meat of the feature is in | 09:44 |
| ttx | ok, so let's mark "implemented" at tag time | 09:44 |
| johnthetubaguy | yeah, +1 | 09:44 |
| ttx | * https://blueprints.launchpad.net/nova/+spec/api-microversions | 09:44 |
| johnthetubaguy | I think thats a similar state | 09:45 |
| johnthetubaguy | honestly it not clear where the patches land between those two now | 09:45 |
| ttx | TI think there is some impact on ironic there though | 09:45 |
| ttx | could be covered by RC bugs for the "needed" stuff | 09:46 |
| ttx | so yeah, similar state | 09:46 |
| johnthetubaguy | OK, true, they snook some stuff into that blueprint | 09:46 |
| johnthetubaguy | hoenstly, the ironic stuff did sound like a bug fix | 09:46 |
| ttx | Kilo objects, same | 09:46 |
| ttx | mark complete and cover critical missing parts if any as RC bugs (which they would be) | 09:47 |
| johnthetubaguy | yeah, objects has some risk, so we need to stop moving that target, but the bug like stuff, yes | 09:47 |
| ttx | So... https://blueprints.launchpad.net/nova/+spec/online-schema-changes | 09:47 |
| ttx | I think that one would FFE | 09:48 |
| johnthetubaguy | right | 09:48 |
| johnthetubaguy | the nice thing… its a parallel path, that is experimental | 09:48 |
| ttx | * https://blueprints.launchpad.net/nova/+spec/make-resource-tracker-use-objects | 09:48 |
| johnthetubaguy | it seems odd to push for it, but we want people to try it out sooner rather than later | 09:48 |
| ttx | That one looks a bit far away still | 09:48 |
| johnthetubaguy | I think we pushed that one out of juno, sigh, but yes, its just not had the attention it needs | 09:49 |
| ttx | it's unlikely that an extra week would change that | 09:49 |
| ttx | * https://blueprints.launchpad.net/nova/+spec/keypair-x509-certificates | 09:49 |
| ttx | hmm, could be considered complete | 09:50 |
| johnthetubaguy | that one is actually just a load of bugs at this point | 09:50 |
| ttx | yeah, mark compleet and file RC1 bugs | 09:50 |
| johnthetubaguy | yeah, I will sort that in the next hour or so | 09:50 |
| ttx | * https://blueprints.launchpad.net/nova/+spec/v3-api-policy | 09:51 |
| ttx | hmm.. lots of patches | 09:51 |
| ttx | how much of a leg does it stand on if we defer the rest ? | 09:52 |
| johnthetubaguy | yes, I hope we actually have the meat of this merged already, but I need to double check that today | 09:52 |
| ttx | I guess if those are simple patches we could FFE it | 09:52 |
| johnthetubaguy | this we might FFE, because of the upgrade impact of not merging | 09:52 |
| johnthetubaguy | yeah | 09:52 |
| ttx | oh right, that would be the 4th dimension... how broken the release is without the rest of the patches | 09:52 |
| ttx | * https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring | 09:53 |
| johnthetubaguy | this isn't really a blueprint as such, its tidy up tracking | 09:53 |
| ttx | That one could be granted FFE on the grounds it touches only tests, but then it's never finished and generates review distraction | 09:54 |
| johnthetubaguy | I know the team wanted this one, because of backporting patches | 09:54 |
| johnthetubaguy | yeah | 09:54 |
| johnthetubaguy | they have all the patches up, apparently, just no one has got that far down the list I guess | 09:54 |
| johnthetubaguy | distraction is a big worry though | 09:54 |
| ttx | especially if we pile up RC1 bugs to tidy the "mark complete" features | 09:54 |
| johnthetubaguy | yes, true | 09:55 |
| johnthetubaguy | I think I lean towards a no on that | 09:55 |
| ttx | yeah. If they can come down to a clear list of when that would be finished... we might reconsider | 09:55 |
| johnthetubaguy | seems like a good plan | 09:55 |
| ttx | ok, I think we have a plan. Now let's get as many of those in thye critical path merged in the next hours | 09:56 |
| johnthetubaguy | +1 | 09:56 |
| ttx | critical path being now: servicegroup-api-is-up-host-topic, isolate-scheduler-db, online-schema-changes and v3-api-policy | 09:57 |
| ttx | which would all be granted FFE if they miss the window | 09:57 |
| ttx | johnthetubaguy: I'd like to tag while you're still around (so that we can FFE/defer/mark-complete together), some early in your afternoon if that sounds good | 09:58 |
| johnthetubaguy | ah, understood, +1 | 09:58 |
| johnthetubaguy | I can pop on later if needed, but lets try avoid that | 09:59 |
| ttx | yeah, same here | 09:59 |
| ttx | I mean, if there are some in the merge pipe, I can wait for those but we defer/FFE early | 09:59 |
| johnthetubaguy | cool | 10:00 |
| ttx | SergeyLukjanov: around ? | 10:02 |
| SergeyLukjanov | ttx, yup | 10:02 |
| SergeyLukjanov | ttx, good morning | 10:02 |
| ttx | how are we doing | 10:03 |
| ttx | anything in the merge pipe we should wait on ? | 10:03 |
| SergeyLukjanov | ttx, now writing up the summary, few CRs are in gate atm, several FFEs needed | 10:03 |
| SergeyLukjanov | ttx, yup | 10:03 |
| ttx | are the 3 patches in the pipe the 3 we are waiting on ? | 10:04 |
| SergeyLukjanov | ttx, let me write it up and I'll return back in 3 mins with a list | 10:04 |
| ttx | I can track them and ping you when they are landed | 10:04 |
| ttx | sure | 10:04 |
| SergeyLukjanov | ttx, https://etherpad.openstack.org/p/sahara-kilo-3-prep | 10:12 |
| SergeyLukjanov | ttx, so, we're waiting only for two CRs | 10:12 |
| SergeyLukjanov | ttx, both of them are in the gate | 10:13 |
| ttx | sounds good to me | 10:13 |
| ttx | Those 3 FFEs are likely to be complete by end of next week, right ? | 10:14 |
| ttx | Let's cut when those 2 patches merge. | 10:15 |
| ttx | I'll track them and ping you when ready | 10:15 |
| ttx | (or the other way around) | 10:15 |
| SergeyLukjanov | ttx, okay, thx | 10:15 |
| SergeyLukjanov | ttx, re FFEs - I think all of them will be completed by Mon-Tue | 10:16 |
| ttx | ok | 10:16 |
| SergeyLukjanov | ttx, I've opened https://wiki.openstack.org/wiki/FeatureFreeze#Exception_procedure to ensure FFE procedure and there is no more FFE request emails | 10:16 |
| ttx | breaking for lunch | 11:03 |
| SergeyLukjanov | ttx, one saahra CR is already merged and another should be in 7 mins | 11:08 |
| johnthetubaguy | ttx: found another nova patch I would like in before we release: https://review.openstack.org/#/c/150267 | 12:50 |
| johnthetubaguy | ttx: we are pushing on getting the devstack dependency ready | 12:51 |
| ttx | johnthetubaguy: if it's part of v3-api-policy it would get the FFE we decided... Any reason why we'd want it in k3 ? | 13:00 |
| ttx | SergeyLukjanov: shara looks ready, I can defer/FFE/tag if you confirm | 13:01 |
| johnthetubaguy | ttx: it makes v2.1 policy testable in the same way we will release it, I think we could probably punt the rest till liberty, but I could be wrong | 13:01 |
| johnthetubaguy | but lets see how it goes I guess | 13:01 |
| ttx | johnthetubaguy: ack | 13:02 |
| ttx | SergeyLukjanov: you there , | 13:39 |
| SergeyLukjanov | ttx, yeah | 13:42 |
| ttx | SergeyLukjanov: ready to go ? | 13:42 |
| SergeyLukjanov | ttx, yup! | 13:42 |
| SergeyLukjanov | ttx, about FFE, how it'll be done this time? previously it was by emails and now it's not very clear for me honestly | 13:43 |
| ttx | SergeyLukjanov: however you want | 13:44 |
| ttx | arguably you already have plenty enough | 13:44 |
| ttx | SergeyLukjanov: should I move specs out of k3 or are you doing it ? | 13:45 |
| ttx | (to kilo-rc1 and liberty-1) | 13:45 |
| ttx | bah, I'll do it | 13:47 |
| ttx | done | 13:49 |
| SergeyLukjanov | ttx, oh, thx, sorry, I've been doing coffee ;) | 13:49 |
| SergeyLukjanov | ttx, re spec files, I'll move 'em | 13:50 |
| ttx | SergeyLukjanov: tag in progress | 13:52 |
| SergeyLukjanov | ttx, great! | 13:52 |
| SergeyLukjanov | ttx, re FFEs, do you need to do anything else or they are approved? | 13:53 |
| ttx | the ones you requested ? Approved | 13:54 |
| SergeyLukjanov | ttx, yup, thx, just to clarify :) | 13:54 |
| ttx | SergeyLukjanov: done | 14:01 |
| SergeyLukjanov | ttx, yay! thank you! | 14:02 |
| morganfainberg | ttx: keystone should be good to tag. | 14:04 |
| morganfainberg | ttx: there is a test-adding patch in gate, but it can land post k3 | 14:04 |
| ttx | morganfainberg: looking | 14:04 |
| ttx | deferring the last two bugs to rc1 | 14:05 |
| ttx | morganfainberg: ok, tag on its way | 14:06 |
| morganfainberg | Yay! | 14:06 |
| *** dhellmann has quit IRC | 14:19 | |
| *** dhellmann has joined #openstack-relmgr-office | 14:19 | |
| ttx | morganfainberg: done | 14:27 |
| mestery | ttx: Ready to chat when you are. | 14:28 |
| ttx | mestery: I am here | 14:28 |
| mestery | ttx: Neutron K3 is looking good. | 14:28 |
| mestery | We have one patch in the merge queue, and one in the check queue which will then hit the merge queue | 14:28 |
| mestery | LP is all cleaned up | 14:28 |
| mestery | Please tkae a look | 14:28 |
| mestery | https://launchpad.net/neutron/+milestone/kilo-3 | 14:28 |
| ttx | links to the patches ? I'll star them | 14:28 |
| * mestery goes and grabs them | 14:29 | |
| mestery | First one: https://review.openstack.org/152093 | 14:29 |
| ttx | that way I can tag when they hit the ground | 14:29 |
| mestery | Second one: https://review.openstack.org/#/c/152761/ | 14:29 |
| ttx | or recheck them if needed | 14:29 |
| mestery | Although that one failed py27 again, need to sync on it | 14:29 |
| ttx | ok, waiting on those two | 14:30 |
| mestery | I'm working with the patch owner on https://review.openstack.org/#/c/152761/ now to understand the py27 failrue | 14:30 |
| mestery | ttx: Thanks! If we can't figure out the issue iwth the second one, I'll move it to RC1, I'll let you know in the next hour | 14:30 |
| ttx | will tag later, once they are in | 14:30 |
| mestery | thanks! | 14:30 |
| ttx | wfm | 14:30 |
| mestery | sweet! Thanks ttx! | 14:30 |
| ttx | nikhil_k: ping me when around | 14:31 |
| ttx | same for david-lyle | 14:33 |
| david-lyle | ttx: doing final k-3 cleanup | 14:34 |
| ttx | ok, standing by | 14:34 |
| david-lyle | ok ready | 14:36 |
| david-lyle | one in the gate and a few RC-1s that are very close and high priority | 14:36 |
| ttx | So.. pending on https://review.openstack.org/#/c/143139/ ? | 14:37 |
| david-lyle | yes, not a good start on the check job though :( | 14:38 |
| ttx | Should I move all the other bugs to rc1? | 14:38 |
| david-lyle | doesn't look related to the change | 14:38 |
| david-lyle | yes | 14:38 |
| david-lyle | I'll cull some off that list | 14:38 |
| ttx | ok, moving now | 14:38 |
| ttx | you can cull once they are moved to rc1 | 14:39 |
| david-lyle | sure | 14:39 |
| ttx | ok moved | 14:39 |
| ttx | let's babysit that last one through gate and tag | 14:40 |
| david-lyle | ok, sounds good | 14:40 |
| nikhil_k | ttx: hi | 14:51 |
| nikhil_k | (just done with weekly meeting) | 14:52 |
| ttx | nikhil_k: are the 3 Bps still on the k3 page the ones we want to FFE ? | 14:52 |
| nikhil_k | ttx: yeah | 14:52 |
| nikhil_k | ttx: I just announced in the meeting for getting one of them reviewed today | 14:53 |
| nikhil_k | ttx: It's in really good share and I wanted to be extra sure before merging. | 14:53 |
| ttx | nikhil_k: any reason to wait ? | 14:53 |
| nikhil_k | ttx: this one https://blueprints.launchpad.net/glance/+spec/pass-targets-to-policy-enforcer | 14:54 |
| ttx | any particular patch I should wait on ? | 14:54 |
| nikhil_k | oh | 14:54 |
| nikhil_k | actually, there are two https://review.openstack.org/#/c/146651/ and https://review.openstack.org/#/c/149112/ | 14:55 |
| nikhil_k | the second one being more important | 14:55 |
| nikhil_k | ttx: I think we'd be done in next 4 hours or so. Any chance you would be available then? | 14:56 |
| ttx | sure | 14:56 |
| ttx | just get them reviewed so that they enter queue early | 14:56 |
| nikhil_k | ttx: sounds good. | 14:57 |
| nikhil_k | ttx: A question | 14:57 |
| nikhil_k | The documentation freeze happens today | 14:57 |
| nikhil_k | so, would that be applicable for the FFEs | 14:57 |
| nikhil_k | ? | 14:57 |
| ttx | that means that patches should stop changing strings | 14:58 |
| ttx | if really needed, raise a thread on -dev so that docs /translators know | 14:58 |
| nikhil_k | gotcha | 14:58 |
| * ttx needs to run an errand, back in 60/80min | 14:58 | |
| nikhil_k | ttx: sure. thanks | 14:58 |
| ttx | Let's block on those last two reviews for glance k3 | 14:58 |
| nikhil_k | awesome. | 14:58 |
| ttx | the other two BPs would get FFE, right ? | 14:58 |
| nikhil_k | yes | 14:59 |
| ttx | alright | 14:59 |
| ttx | ttyl | 14:59 |
| nikhil_k | cya | 14:59 |
| mestery | ttx: Neutron Kilo-3 is locked and loaded and ready for a tag: https://launchpad.net/neutron/+milestone/kilo-3 | 15:13 |
| *** bswartz has joined #openstack-relmgr-office | 16:08 | |
| bswartz | ttx: no meeting today? | 16:10 |
| ttx | bswartz: well, we do k3, and you're already done :) | 16:11 |
| bswartz | =D | 16:11 |
| bswartz | anything you wanted to mention about RC1? | 16:12 |
| bswartz | we aim for 2-3 weeks from now right? | 16:12 |
| ttx | bswartz: not really... you should add RC-blocking bugs to the milestone | 16:12 |
| ttx | yeah, 2 weeks is the rigth target | 16:12 |
| bswartz | cool | 16:12 |
| ttx | can be earlier... we tag RC1 when the bug list is empty | 16:12 |
| bswartz | that was my only question | 16:12 |
| ttx | cheers | 16:12 |
| bswartz | I would love for it to be earlier | 16:13 |
| ttx | mestery: ok, tagging | 16:13 |
| mestery | ttx: Thanks! | 16:14 |
| mestery | ttx: Going afk for a bit, I'll be back in 30 minutes or so. | 16:17 |
| Kiall | Hey ttx | 16:30 |
| Kiall | About? | 16:30 |
| Kiall | Designate k3 tag should be eaa914489d3cb93e42ae0d98682953a5700b9a69 - Currently checking bugs etc for things not marked k3 that should be.. | 16:31 |
| ttx | Kiall: hey | 16:31 |
| Kiall | Hey :) | 16:32 |
| ttx | If it's ready you should clean up https://launchpad.net/designate/+milestone/kilo-3 | 16:32 |
| ttx | moving stuff to -rc1 or liberty-1 | 16:32 |
| Kiall | Yep, cleaning up as we speak :) | 16:32 |
| ttx | ok, ping me when done | 16:32 |
| Kiall | K | 16:32 |
| ttx | redrobot: around? | 16:35 |
| redrobot | ttx o/ | 16:35 |
| ttx | redrobot: how close are you from the tag ? | 16:36 |
| ttx | Looks ready if I'm to trust your milestone page | 16:36 |
| redrobot | ttx I cleaned up the milestone page to be able to tag now. Unfortunately a few BPs slipped past the deadline. | 16:36 |
| redrobot | ttx they're all in review, so I expect them to land in the next few days. :-\ | 16:36 |
| ttx | that's fine | 16:37 |
| ttx | ok, will tag when I'm done with neutron& friends | 16:37 |
| redrobot | ttx thanks! much appreciated. | 16:37 |
| ttx | SlickNik: around? | 16:37 |
| ttx | redrobot: hah, just read your email | 16:38 |
| redrobot | ttx yeah, I wasn't sure if we had a 1:1 today :) | 16:38 |
| SlickNik | ttx: here | 16:39 |
| ttx | SlickNik: anything in the pipe I should wait for ? Or should we FFe/defer now ? | 16:40 |
| SlickNik | There's one patch in the pipeline. | 16:40 |
| ttx | link? | 16:41 |
| SlickNik | https://review.openstack.org/#/c/156486/ | 16:41 |
| SlickNik | corresponding to https://blueprints.launchpad.net/trove/+spec/vertica-db-support | 16:41 |
| ttx | ack, I can tag when that is in | 16:42 |
| SlickNik | Looking to FFE https://blueprints.launchpad.net/trove/+spec/replication-v2 | 16:42 |
| ttx | if that's the only one you can target it to rc1 now | 16:43 |
| SlickNik | THere's also https://blueprints.launchpad.net/trove/+spec/implement-vertica-cluster | 16:44 |
| ttx | if it's likely to land in the comin week, +1 | 16:44 |
| SlickNik | But I'm inclined to move that to Liberty — not many reviews on that one at all | 16:45 |
| SlickNik | I'll keep an eye out on it. | 16:45 |
| ttx | yeah, that was my impression too | 16:45 |
| ttx | also a large feature, likely to disrupt testing if it lands late | 16:45 |
| SlickNik | +1 | 16:45 |
| SlickNik | Will reevaluate early next week and make a final call on that. | 16:45 |
| ttx | in the mean time move both to rc1 | 16:46 |
| SlickNik | Sounds good, doing that now | 16:46 |
| Kiall | ttx: Okay, good to go :) | 16:46 |
| ttx | nikhil_k: we need another +2 on your blocking patches | 16:47 |
| ttx | nikhil_k: otherwise they will miss the window | 16:47 |
| SlickNik | ttx: done | 16:48 |
| SlickNik | ttx: We also got another FFE request on the mailing list: https://blueprints.launchpad.net/trove/+spec/db2-plugin-for-trove | 16:48 |
| SlickNik | ttx: It's currently marked for liberty, but it looks like the code is ready (from the emailO | 16:49 |
| SlickNik | Hasn't had many reviews though. | 16:49 |
| ttx | yeah, probably bad idea to add in the pipe right now | 16:50 |
| ttx | flaper87: around? | 16:51 |
| SlickNik | ttx: It's a bit of an isolated change — adding a new experimental datastore, so I will talk with Miriam (the author) to see if she can get more reviews on it. | 16:52 |
| SlickNik | Unless that changes over the next couple of days, I'm incline to leave it for Liberty and not FFE it. | 16:52 |
| ttx | ok, we can rediscuss it on Tuesday | 16:53 |
| SlickNik | ttx: okay, sounds good. Thanks! | 16:54 |
| ttx | redrobot: barbican done | 16:57 |
| ttx | mestery: neutron done | 16:57 |
| redrobot | ttx thanks! | 16:58 |
| ttx | johnthetubaguy: a bit confused with the state of your last patch | 16:59 |
| ttx | https://review.openstack.org/#/c/150267/ | 16:59 |
| ttx | seems to be nowhere in zuul | 17:00 |
| johnthetubaguy | ttx: its actually waiting on this one, sorry: https://review.openstack.org/#/c/160068/ using depends on | 17:00 |
| ttx | I'll ask on infra | 17:00 |
| ttx | oh | 17:00 |
| ttx | right | 17:00 |
| ttx | johnthetubaguy: should we get people to +2 it ? | 17:01 |
| ttx | because otherwise it will miss the window | 17:01 |
| johnthetubaguy | yes, I got agreement to give it an exception if we need to | 17:02 |
| ttx | Kiall: designate done | 17:02 |
| Kiall | ttx: excellent :) | 17:02 |
| ttx | johnthetubaguy: either we get +2s on it now, or we FFE it and tag just now | 17:02 |
| johnthetubaguy | sdague: what do you think about https://review.openstack.org/#/c/160068/? | 17:02 |
| mestery | ttx: Thanks! | 17:05 |
| nikhil_k | ttx: I've got +2s on all the patches, going to +A them now | 17:14 |
| ttx | nikhil_k: cool | 17:14 |
| ttx | johnthetubaguy: how about I come back in a few hours and if the patch is not there, I can FFE v3-api-policy and tag | 17:20 |
| ttx | that way you don't need to be around | 17:20 |
| nikhil_k | ttx: (just fyi) these are reviews waiting for gate: https://review.openstack.org/#/c/149112/ , https://review.openstack.org/#/c/146651/ , https://review.openstack.org/#/c/162368/ | 17:20 |
| ttx | nikhil_k: awesome | 17:22 |
| ttx | back in two hours | 17:27 |
| sdague | johnthetubaguy: yeh, I'm jut double checking with dtroyer on that one now | 17:28 |
| sdague | if I don't hear back shortly, I'll just kick it through | 17:28 |
| *** mestery_ has joined #openstack-relmgr-office | 17:31 | |
| *** mestery has quit IRC | 17:33 | |
| sdague | johnthetubaguy: ok, it's in the gate now | 17:33 |
| *** mestery_ is now known as mestery | 17:39 | |
| david-lyle | ttx: last bp merged for horizon, tag at will | 17:59 |
| johnthetubaguy | sdague: thank you | 18:06 |
| johnthetubaguy | ttx: looks like 160068 is in the merge queue now, but if it drops out, then its probably time to just cut, as you said | 18:08 |
| sdague | johnthetubaguy: 160068 is going to merge, but the nova patch seems to be failing unit tests | 18:13 |
| johnthetubaguy | sdague: maybe its the race we have in the gate, arse | 18:13 |
| johnthetubaguy | oh, is see now | 18:13 |
| sdague | no, it's bugs | 18:14 |
| sdague | I'm going to fix | 18:14 |
| johnthetubaguy | oh | 18:14 |
| johnthetubaguy | appreciated though, but it might be too later for kilo-3, but assume you have an exception in terms of approving it, given the discussion at the nova-meeting | 18:15 |
| johnthetubaguy | sdague: thanks for pushing on this, as always! | 18:15 |
| sdague | yeh, it looks like possible merge conflict on policy names | 18:15 |
| sdague | it's 3 strings that need updating | 18:15 |
| sdague | no prob | 18:15 |
| *** johnthetubaguy is now known as zz_johnthetubagu | 18:19 | |
| sdague | zz_johnthetubagu: we've reapproved the patch | 18:42 |
| sdague | but that's probably still 3 - 4 hrs from merge if we're lucky | 18:42 |
| nikhil_k | ttx: all the reviews we were waiting for have been merged. | 18:59 |
| nikhil_k | ttx: any objections for cutting a glance_store and python-glanceclient release at this point in the cycle | 19:00 |
| nikhil_k | ? | 19:00 |
| ttx | nikhil_k: maybe wait until all k3 is done, so tag tomorrow? | 19:04 |
| ttx | don't want to take the chance to break gate today :) | 19:05 |
| nikhil_k | ttx: sure thing | 19:05 |
| ttx | tagging horizon | 19:05 |
| nikhil_k | ttx: tomorrow is friday though :) | 19:05 |
| nikhil_k | (no worries in any case) | 19:05 |
| david-lyle | \o/ | 19:05 |
| ttx | nikhil_k: you could tag today after I'm done :) | 19:05 |
| nikhil_k | ttx: sounds good :) | 19:06 |
| ttx | david-lyle: horizon done | 19:19 |
| ttx | tagging glance | 19:19 |
| david-lyle | ttx: thanks! | 19:19 |
| ttx | SlickNik: some issues on your trove paches in the merge pipe | 19:24 |
| ttx | nikhil_k: glance tagged | 19:26 |
| ttx | I'll be back in an hour | 19:26 |
| SlickNik | ttx: looking into it. | 19:27 |
| nikhil_k | ttx: thanks! | 19:46 |
| nikhil_k | will release the lib and client later today (if things generally look ok) | 19:46 |
| ttx | devananda: looks like ironic is a go | 20:27 |
| ttx | devananda: marked https://bugs.launchpad.net/ironic/+bug/1174153 and https://blueprints.launchpad.net/ironic/+spec/implement-cleaning-states done, tagging now | 20:42 |
| openstack | Launchpad bug 1174153 in OpenStack Compute (nova) "data from previous tenants accessible with nova baremetal" [High,In progress] - Assigned to Jim Rollenhagen (jim-rollenhagen) | 20:42 |
| ttx | If I shouldn't have, please revert | 20:42 |
| ttx | SlickNik: https://review.openstack.org/#/c/156486/ failed | 20:47 |
| SlickNik | ttx: I saw :( Looks like a flaky assert in the system caused it. I've pushed out a change to remove the assert for now. https://review.openstack.org/#/c/165995/ | 20:49 |
| ttx | I rechecked 156486 | 20:49 |
| ttx | SlickNik: it's unlikely to pass in the next hours though. So we can either wait until my tomorrow morning to tag, or FFE it | 20:51 |
| ttx | Loks like I'll have to wait on some Cinder stuff anyway | 20:51 |
| ttx | devananda: ironic done | 20:52 |
| SlickNik | ttx: Let's wait until your tomorrow morning to tag it in that case. If it doesn't make it through this run, we can FFE it. | 20:54 |
| SlickNik | ttx: I'll keep an eye on it and see how it goes. | 20:54 |
| ttx | SlickNik: ok, please babysit it all day :) | 20:54 |
| SlickNik | I will :) | 20:55 |
| ttx | back in 50min to catch that last nova change | 21:05 |
| *** bswartz has quit IRC | 21:10 | |
| devananda | ttx: \o/ | 21:31 |
| *** asalkeld has joined #openstack-relmgr-office | 21:34 | |
| ttx | asalkeld: around? | 21:54 |
| ttx | OK, looks like I'll have to tag Nova, Cinder and Trove after my sleep, early tomorrow morning | 21:55 |
| asalkeld | hi | 22:11 |
| asalkeld | ok | 22:11 |
| asalkeld | (sorry was making breaky) | 22:12 |
| *** SlickNik has left #openstack-relmgr-office | 23:30 | |
| *** SlickNik has joined #openstack-relmgr-office | 23:30 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!
