| *** david-lyle is now known as david-lyle_afk | 03:35 | |
| * ttx yawns | 09:00 | |
| asalkeld | hi ttx | 09:00 |
|---|---|---|
| ttx | asalkeld: hi! | 09:00 |
| ttx | #startmeeting ptl_sync | 09:00 |
| openstack | Meeting started Tue Mar 17 09:00:28 2015 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| openstack | The meeting name has been set to 'ptl_sync' | 09:00 |
| ttx | #topic Heat | 09:00 |
| asalkeld | ttx sorry, i missed last weeks | 09:00 |
| ttx | #link https://launchpad.net/heat/+milestone/kilo-3 | 09:00 |
| ttx | asalkeld: not a problem, I skipped most of them anyway | 09:00 |
| ttx | So... crunch time | 09:01 |
| ttx | 6 BPs up | 09:01 |
| asalkeld | so most are very close to getting merged | 09:01 |
| ttx | Let's go through them one by one | 09:01 |
| asalkeld | so i am not very stressed about them | 09:01 |
| asalkeld | ok | 09:01 |
| ttx | https://blueprints.launchpad.net/heat/+spec/convergence-resource-table | 09:01 |
| ttx | Only needing https://review.openstack.org/#/c/156693/ ? | 09:01 |
| asalkeld | that's a one patch spec | 09:01 |
| asalkeld | yip | 09:02 |
| asalkeld | should get in soon | 09:02 |
| ttx | https://blueprints.launchpad.net/heat/+spec/decouple-nested | 09:02 |
| asalkeld | that's mine | 09:02 |
| asalkeld | *should* get it in time | 09:02 |
| asalkeld | 3 patches up, all working well | 09:02 |
| asalkeld | some disent amounst the minions;) | 09:02 |
| ttx | https://blueprints.launchpad.net/heat/+spec/convergence-lightweight-stack | 09:03 |
| asalkeld | that might well miss | 09:03 |
| asalkeld | but it't only one patch | 09:03 |
| asalkeld | so willing to wait until the death | 09:03 |
| ttx | I see two patches | 09:03 |
| ttx | If that one misses, do you intend to request FFE for it ? | 09:04 |
| asalkeld | ttx: it can just wait | 09:04 |
| ttx | If not, maybe prioritize to Medium | 09:04 |
| asalkeld | ok | 09:04 |
| ttx | I assume the first two would get exceptions | 09:04 |
| ttx | if they missed | 09:04 |
| ttx | https://blueprints.launchpad.net/heat/+spec/convergence-push-data | 09:04 |
| asalkeld | that should be ok | 09:05 |
| asalkeld | again one patch | 09:05 |
| ttx | OK, it's linked to the other | 09:05 |
| ttx | https://blueprints.launchpad.net/heat/+spec/mistral-resources-for-heat | 09:05 |
| ttx | Looks like 2 patches | 09:06 |
| asalkeld | so this is a bp for code that goes into contrib/ | 09:06 |
| asalkeld | so IMO it can go in any time | 09:06 |
| asalkeld | (does not effect strings or deps) | 09:06 |
| ttx | yeah, at least could get an exception as "self-contained" | 09:06 |
| asalkeld | and gets installed seperately | 09:07 |
| ttx | https://blueprints.launchpad.net/heat/+spec/stack-breakpoint | 09:07 |
| asalkeld | there are 2 or 3 guys trying hard to get that in | 09:07 |
| asalkeld | it should make it | 09:07 |
| asalkeld | needed for tripelo | 09:07 |
| ttx | ok we'll see how it goes | 09:07 |
| asalkeld | yeah, we can wait | 09:08 |
| ttx | On the bugs side... anything k3-critical that we would not just defer to rc1 ? | 09:08 |
| asalkeld | they are all on the edge of getting merged | 09:08 |
| asalkeld | i think just defer everything that's not merged | 09:08 |
| ttx | #info k3 bugs can be deferred to rc1 if incomplete | 09:09 |
| ttx | #info 6 BPs left, all still standing a reasonable chance of making it | 09:09 |
| * asalkeld is hopeful | 09:09 | |
| ttx | OK, that's all I guess. We'll make a new status point on Thursday (your evening, my morning) | 09:10 |
| ttx | hopefully for the final tag / early FFE decisions | 09:10 |
| asalkeld | ok - same time? | 09:10 |
| asalkeld | (just want to make a reminder) | 09:10 |
| ttx | sounds good. Ping me if I don't talk | 09:10 |
| asalkeld | ok, chat then | 09:10 |
| ttx | see you! | 09:11 |
| ttx | zz_johnthetubagu: around? | 09:11 |
| *** asalkeld has left #openstack-relmgr-office | 09:13 | |
| *** zz_johnthetubagu is now known as johnthetubaguy | 09:14 | |
| ttx | johnthetubaguy: o/ | 09:17 |
| johnthetubaguy | ttx: hi | 09:17 |
| ttx | #topic Nova | 09:17 |
| ttx | #link https://launchpad.net/nova/+milestone/kilo-3 | 09:17 |
| ttx | That's still 12 BPs in progress | 09:17 |
| ttx | Let's see how far they are | 09:18 |
| ttx | https://blueprints.launchpad.net/nova/+spec/v2-on-v3-api | 09:18 |
| ttx | I see 4 patches on https://review.openstack.org/#/q/topic:bp/v2-on-v3-api,n,z | 09:18 |
| ttx | But the last says it partially implements so it looks like there is more to it | 09:18 |
| johnthetubaguy | hmm, I thought they were done there now, pretty much, but I am rarely online the same time as those folks so its tricky relaying info | 09:19 |
| ttx | Those might be add-ons patches | 09:20 |
| johnthetubaguy | ah, yes, I think a lot of this is now unit test clean up | 09:20 |
| ttx | ok, if that's the case it would be good to stop mentioning the BP in the patches at some point and consider it "finished" | 09:20 |
| johnthetubaguy | well, general cleanups anyways | 09:20 |
| ttx | https://blueprints.launchpad.net/nova/+spec/api-microversions | 09:21 |
| johnthetubaguy | agreed, but folks do like the tracking | 09:21 |
| ttx | seems to be in the same situation | 09:21 |
| johnthetubaguy | yes | 09:21 |
| ttx | #info v2-on-v3-api and api-microversions are "mostly finished" | 09:21 |
| ttx | https://blueprints.launchpad.net/nova/+spec/cells-v2-mapping | 09:21 |
| ttx | This one will be partial IIUC | 09:22 |
| ttx | in which case it is "mostly finished" too, I suspect | 09:22 |
| johnthetubaguy | yes, there are a few patches, I think they wanted, but as you say, its kinda partial anyways | 09:22 |
| ttx | https://blueprints.launchpad.net/nova/+spec/kilo-objects | 09:23 |
| johnthetubaguy | this one is basically tracking cleanups | 09:23 |
| ttx | Feels like another "what's in kilo is kilo" | 09:23 |
| johnthetubaguy | right | 09:23 |
| johnthetubaguy | its a tracking placeholder to help with reviews more than anything | 09:23 |
| ttx | #info cells-v2-mapping and kilo-objects are partial work anyway, so what's in kilo is kilo | 09:23 |
| ttx | https://blueprints.launchpad.net/nova/+spec/online-schema-changes | 09:24 |
| johnthetubaguy | one last patch there I think | 09:24 |
| ttx | pending on https://review.openstack.org/#/c/154521/ | 09:24 |
| ttx | #info online-schema-changes pending on https://review.openstack.org/#/c/154521/ -- looking good | 09:24 |
| ttx | it says "partially implements" though | 09:24 |
| ttx | https://blueprints.launchpad.net/nova/+spec/make-resource-tracker-use-objects | 09:25 |
| johnthetubaguy | yeah, thats true, I will check, but I thought that was it | 09:26 |
| ttx | Lots of patches up | 09:26 |
| ttx | This one sounds more at risk | 09:26 |
| ttx | although it's marked partial too | 09:27 |
| johnthetubaguy | oh yes, I think you are right, that one was close to getting kicked out already | 09:27 |
| ttx | #info make-resource-tracker-use-objects might be so partial it could be considered deferred | 09:27 |
| ttx | https://blueprints.launchpad.net/nova/+spec/detach-service-from-computenode | 09:27 |
| johnthetubaguy | I will check out that one closer after the meeting | 09:28 |
| ttx | Not sure what's waiting on | 09:28 |
| johnthetubaguy | it might be done now, as much as it will be in kilo, let me check | 09:28 |
| ttx | you can check after meeting, no worry | 09:29 |
| johnthetubaguy | yep is done, although its technically, a bit partial | 09:29 |
| ttx | #info detach-service-from-computenode might be considered finished | 09:29 |
| ttx | OK, medium stuff now | 09:29 |
| ttx | https://blueprints.launchpad.net/nova/+spec/keypair-x509-certificates | 09:29 |
| ttx | Remaining patches are novaclient and a bug fix | 09:30 |
| johnthetubaguy | yes, they need work really | 09:30 |
| ttx | so we could move them to RC1 if necessary | 09:30 |
| ttx | and consider this finished | 09:30 |
| johnthetubaguy | yes, I think thats probably easiest, I might open bugs for those patches | 09:31 |
| ttx | #info keypair-x509-certificates could just be considered finished and remaining bugs pushed to RC1 if need be | 09:31 |
| ttx | https://blueprints.launchpad.net/nova/+spec/v3-api-policy | 09:31 |
| ttx | This one is marked partial, so probably another of those "what's in kilo is kilo" | 09:31 |
| johnthetubaguy | possibly, there are a few patches they really want in kilo, its on the etherpad I think | 09:32 |
| ttx | Loads of patches there | 09:32 |
| johnthetubaguy | yeah, its a streatch to get those all in | 09:32 |
| ttx | #info v3-api-policy needs work, will be partial | 09:32 |
| ttx | https://blueprints.launchpad.net/nova/+spec/ec2-api | 09:32 |
| ttx | Isn't that finished? | 09:33 |
| johnthetubaguy | I think it is | 09:33 |
| ttx | #info ec2-api is probably finished | 09:33 |
| ttx | https://blueprints.launchpad.net/nova/+spec/servicegroup-api-is-up-host-topic | 09:34 |
| ttx | A bit unclear what it's waiting on | 09:34 |
| ttx | also marked partial | 09:34 |
| johnthetubaguy | I think its this one: https://review.openstack.org/#/c/149924/ | 09:35 |
| ttx | #info servicegroup-api-is-up-host-topic pending on https://review.openstack.org/#/c/149924/ | 09:36 |
| johnthetubaguy | its a clean up though, so I might just remove the blueprint tag, lets see | 09:36 |
| ttx | https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring | 09:36 |
| ttx | That one looks forever partial | 09:36 |
| ttx | and candidate for deferral | 09:37 |
| ttx | #info hyper-v-test-refactoring may or may not make it | 09:37 |
| johnthetubaguy | yeah, I vote we defer the BP, I mean its unit tests, so they can merge later if needed I guess | 09:37 |
| ttx | yeah, I'm more afraid of the distration than of the impact | 09:37 |
| ttx | distraction | 09:37 |
| ttx | #info 10 blueprints left, mostly partial & "what's in kilo will be kilo" work anyway | 09:38 |
| ttx | Quick look on the bugs side, see if any of those "critical" are actually k3-critical | 09:38 |
| ttx | like regressions | 09:39 |
| ttx | or showstoppers | 09:39 |
| ttx | https://bugs.launchpad.net/nova/+bug/1383465 is unlikely to be solved in the next two days | 09:40 |
| openstack | Launchpad bug 1383465 in OpenStack Compute (nova) "[pci-passthrough] nova-compute fails to start" [Critical,In progress] - Assigned to Yongli He (yongli-he) | 09:40 |
| johnthetubaguy | nothing that stops kilo-3 from a quick look, right, thats the only big one | 09:40 |
| johnthetubaguy | it got discussed in the nova meeting again | 09:40 |
| johnthetubaguy | trying to move that forward before kilo ships | 09:40 |
| johnthetubaguy | it was targeted to kilo-1 I think | 09:40 |
| ttx | and passed forward | 09:41 |
| ttx | https://bugs.launchpad.net/nova/+bug/1296414 is another of those long-standing issues | 09:41 |
| openstack | Launchpad bug 1296414 in OpenStack Compute (nova) "quotas not updated when periodic tasks or startup finish deletes" [Critical,In progress] - Assigned to Rajesh Tailor (rajesh-tailor) | 09:41 |
| ttx | ok, so I'll push to RC1 anything not merged by tag time | 09:42 |
| ttx | #info Bugs to be deferred if not merged | 09:42 |
| johnthetubaguy | sounds good | 09:42 |
| johnthetubaguy | I will ask around to see if there are any exceptions to that | 09:42 |
| ttx | johnthetubaguy: how about we meet again on Thursday and formally close all those partial things, then see if anything in the pipe justifies waiting ? | 09:42 |
| johnthetubaguy | that sounds like a plan | 09:42 |
| ttx | same time ? | 09:43 |
| johnthetubaguy | yes, I will pop that in my calendar now | 09:43 |
| ttx | sounds good, have a good day! | 09:43 |
| johnthetubaguy | you too! | 09:43 |
| dhellmann | ttx: ready when you are | 12:24 |
| ttx | dhellmann: you might be one hour early, but we can probably do it nevertheless | 12:25 |
| dhellmann | ttx: oh, right, forgot you're not on dst yet | 12:25 |
| ttx | no pb, if you're available now, let's do this | 12:25 |
| dhellmann | sure thing | 12:26 |
| ttx | #topic Oslo | 12:26 |
| ttx | A quick look at milestone pages | 12:26 |
| ttx | #link https://launchpad.net/oslo/+milestone/kilo-3 | 12:26 |
| ttx | there is a bug targeted: https://bugs.launchpad.net/cinder/+bug/1417018 | 12:26 |
| openstack | Launchpad bug 1417018 in oslo.db "Cinder encounters dbapi error: NoSuchColumnError: "Could not locate column in row for column '%(140070887032400 anon)s.volumes_id'"" [Medium,In progress] | 12:26 |
| ttx | is that something we want to fix and sync in kilo ? | 12:27 |
| dhellmann | yeah, that one is actually done in oslo.db -- I'll be making a release later today | 12:27 |
| dhellmann | we haven't settled on the best way to fix it in the incubator, but the oslo.db fix should remove the issue from cinder | 12:27 |
| dhellmann | I'll update the targets | 12:27 |
| ttx | ok cool | 12:27 |
| ttx | https://launchpad.net/oslo/+milestone/next-kilo shows a bunch of PBR bugfixes | 12:28 |
| ttx | is there a PBR release planned ? | 12:28 |
| ttx | or would those actually appear in next-liberty ? | 12:28 |
| dhellmann | ttx: not to include those items. I'll retarget them too | 12:28 |
| ttx | ok | 12:28 |
| ttx | Looking at https://review.openstack.org/#/c/162656/ | 12:29 |
| dhellmann | actually, I don't think whoever has been doing pbr releases has been using the script, so I'll verify that they're not already done | 12:29 |
| ttx | do you think we should collect more +2s ? Or should I just W+1 it ? | 12:29 |
| ttx | not sure why the subsequent reviewers didn't w+1 | 12:30 |
| dhellmann | yeah, sdague expressed some reservations and that may have made people hold off on the w+1 | 12:30 |
| dhellmann | I would like to get that in asap so we can also land the subsequent requirements updates to the projects | 12:30 |
| dhellmann | the requirements freeze is this week, right? | 12:31 |
| ttx | yeah, timing is tight | 12:31 |
| sdague | jogo is +1 on that now, I'll approve | 12:31 |
| dhellmann | sdague: thanks, I was going to check in with you on that in a bit anyway | 12:31 |
| sdague | that's going to trigger a ton of patch / test churn, btw | 12:31 |
| ttx | requirements freeze is same as feature freeze yes | 12:31 |
| dhellmann | sdague: yeah, that's why I did it all in one patch :-) | 12:31 |
| sdague | :) | 12:31 |
| ttx | sdague: should we generally try do those one week earlier ? | 12:31 |
| sdague | ttx: probably | 12:31 |
| sdague | I expect we'll consume all the test nodes on the proposal bot changes for that one | 12:32 |
| ttx | note that those could technically land post-requirements freeze, since requirements freeze is mostly to guard against additions | 12:32 |
| dhellmann | I think we would have been ready a week earlier this cycle except for the deprecation warning issue | 12:32 |
| dhellmann | ttx: ok, as long as it lands before the branches are made I think we're ok | 12:32 |
| ttx | so I'm fine with those landing post-FF pre-RC1 | 12:32 |
| dhellmann | I'm OK with that if we want to preserve test nodes | 12:33 |
| ttx | if we think approving this now is a bad idea | 12:33 |
| dhellmann | I can update the policy document to reflect that change, too | 12:33 |
| ttx | (requirements sync is part of the RC1 process) | 12:33 |
| sdague | zuul still has capacity this morning | 12:33 |
| sdague | so anyway, it's approved | 12:33 |
| dhellmann | ok, thanks, sdague | 12:33 |
| ttx | dhellmann: I also wanted to pick your brains on which projects actually could be considered havign a final release per cycle (for the release:at-6mo-cycle-end tag application) | 12:34 |
| ttx | First, looking at Oslo libs | 12:34 |
| ttx | I suspect some of them don't really apply | 12:35 |
| ttx | for example openstack-dev/pbr | 12:35 |
| dhellmann | I want them all to be considered as following that plan, although we had a couple of stragglers this time. pbr and taskflow, I think. | 12:35 |
| dhellmann | I need to get the pbr team inline with the rest of oslo | 12:35 |
| ttx | what about openstack-dev/cookiecutter ? | 12:35 |
| ttx | (and openstack-dev/oslo-cookiecutter) | 12:36 |
| dhellmann | oh, we don't release that, that's just a template for making new projects | 12:36 |
| dhellmann | you use it straight from the git url | 12:36 |
| ttx | right, so those would not have release:* tags | 12:36 |
| dhellmann | right | 12:36 |
| ttx | so what should I do about taskflow/pbr ? Consider them in ? | 12:37 |
| dhellmann | yes, let's consider them in and I'll talk to the maintainers | 12:37 |
| ttx | Second question is about python-*client, to piggyback on your discussion with David Lyle recently | 12:37 |
| ttx | I'm a bit confused if we should consider them in (as in having stable branches) | 12:38 |
| ttx | I think they might be release:independent, really | 12:38 |
| dhellmann | well, we need to start doing that, I think. We're capping the versions we use in the stable branches, so if we have to fix something the only want to release a new version would be to have a stable branch of the client | 12:38 |
| dhellmann | I believe the d-g tests are already installing the services and tempest in separate site-packages (one is in a virtualenv, I'm not sure which) | 12:39 |
| dhellmann | that lets us test new clients from the outside of the cloud while using stable clients inside the cloud | 12:39 |
| ttx | hmm, ok. So they should be at-6mo-end | 12:39 |
| ttx | even if technically they don't have stable branches until needed | 12:39 |
| dhellmann | yes, unless someone else comes up with an alternative to my stable-library spec | 12:40 |
| ttx | Applying tags results in uncovering interesting corner cases to say the least | 12:40 |
| dhellmann | true | 12:40 |
| ttx | at the very least helps clarify things, even for us | 12:41 |
| ttx | ok, I think that's all I had in store for you | 12:41 |
| dhellmann | ok, I had a couple for you | 12:41 |
| ttx | do we have any lib left to release for kilo ? You mentioned pbr ? | 12:41 |
| dhellmann | that policy on stable branches for libs should be prioritized: https://review.openstack.org/155072 | 12:42 |
| ttx | yeah, I added it to todays meeting agenda | 12:42 |
| dhellmann | I have a backported fix for oslo.db that I will release today, but I don't anticipate any other releases | 12:42 |
| dhellmann | ok, good | 12:42 |
| ttx | (cross-project meeting) | 12:42 |
| dhellmann | and do we know the dates for the fall summit yet? | 12:42 |
| ttx | in silence is consent mode | 12:42 |
| ttx | I think we do, let me check | 12:43 |
| dhellmann | I didn't see them on the event calendar on openstack.org, but I don't know how far out that actually goes | 12:43 |
| ttx | https://www.openstack.org/summit/tokyo-2015/ | 12:43 |
| ttx | October 26 - 30, 2015 | 12:43 |
| dhellmann | ah, ok thanks | 12:43 |
| ttx | That may not be linked to yet, but the page is public | 12:43 |
| ttx | and the URL is not that hard to guess | 12:44 |
| dhellmann | yeah, I should have tried that :-) | 12:44 |
| ttx | actually it's linked | 12:44 |
| ttx | https://www.openstack.org/summit/ | 12:44 |
| ttx | so consider it public :) | 12:44 |
| dhellmann | I was looking on https://www.openstack.org/community/events/ | 12:45 |
| dhellmann | the calendar includes the spring summit, so I thought if the dates were set for fall that would be there, too, but maybe it's too far out | 12:45 |
| dhellmann | anyway, thanks, I should have looked harder :-) | 12:45 |
| dhellmann | that's all I had for this week | 12:45 |
| ttx | dhellmann: so in summary, next steps are merging requirements patch (but that's arguably non-oslo-specific | 12:46 |
| ttx | and get that policy approved | 12:46 |
| ttx | otherwise you're mostly done release-wise ? | 12:47 |
| dhellmann | yes, I believe that's it | 12:47 |
| ttx | dhellmann: we could push the kilo-3 tag on oslo-incubator now | 12:47 |
| dhellmann | we'll obviously do patch releases if we need to, but the branches are created so we can do that | 12:47 |
| ttx | since we did a 2015.1.0b2 | 12:47 |
| dhellmann | sure, we can push the tag. I think we said we would wait to do the stable branch on the incubator until the other projects had theirs, but the tag is easy | 12:48 |
| dhellmann | do you want to do that, or shall I? | 12:48 |
| ttx | I'll do it now | 12:48 |
| dhellmann | ok | 12:48 |
| ttx | done | 12:49 |
| dhellmann | cool, thanks | 12:49 |
| ttx | ok, thx and have a good day! | 12:50 |
| dhellmann | you, too! | 12:50 |
| SergeyLukjanov | ttx, /me ready when you are | 13:05 |
| ttx | SergeyLukjanov: hi! | 13:05 |
| ttx | #topic Sahara | 13:05 |
| SergeyLukjanov | ttx, hello! | 13:05 |
| SergeyLukjanov | #link https://launchpad.net/sahara/+milestone/kilo-3 | 13:05 |
| SergeyLukjanov | so, we have mostly everything planned done | 13:06 |
| ttx | 8 still up | 13:06 |
| SergeyLukjanov | except few things that are now candidates for FFE | 13:06 |
| SergeyLukjanov | stuff that is under review now is expected to be merged today/tomorrow | 13:06 |
| ttx | SergeyLukjanov: ok | 13:07 |
| ttx | What are the FFE candidates ? edp-job-types-endpoint ? | 13:07 |
| SergeyLukjanov | ttx, yup, this one for sure, there is a core stuff merged already, but plugin-related things not yet merged now, so, we'll need some more time for it | 13:07 |
| ttx | #info edp-job-types-endpoint likely FFE | 13:08 |
| SergeyLukjanov | the same for "Provide default templates for each plugin" https://blueprints.launchpad.net/sahara/+spec/default-templates | 13:08 |
| ttx | #info default-templates likely FFE | 13:08 |
| SergeyLukjanov | and probably for edp-datasource-placeholders as well | 13:08 |
| ttx | #info edp-datasource-placeholders likely FFE | 13:09 |
| ttx | the others shall merge before the k3 date | 13:09 |
| SergeyLukjanov | yup | 13:09 |
| ttx | OK, any k3-blocking bug ? Or can I just defer them to rc1 isf they miss target , | 13:09 |
| ttx | ? | 13:09 |
| SergeyLukjanov | I expect sahara to be ready for tag cut on Thu EU morning | 13:09 |
| SergeyLukjanov | no k3-blocking bugs | 13:09 |
| SergeyLukjanov | I've cleaned up the bugs list, so, there is only few of them and I think they will be merged till the k3 | 13:10 |
| ttx | OK. I had a question for you on dashboard, extra and image-elements | 13:10 |
| SergeyLukjanov | and anyway they aren't importnat | 13:10 |
| SergeyLukjanov | yeah | 13:10 |
| ttx | how many of those are actually still in use ? | 13:10 |
| SergeyLukjanov | dashboard is only for stable/icehouse | 13:11 |
| SergeyLukjanov | starting from Juno it's moved to horizon repo | 13:11 |
| SergeyLukjanov | extra and s-i-e are in use | 13:11 |
| ttx | what is the release model for extra and image-elements ? | 13:11 |
| ttx | once at the end of the 6-month cycle ? | 13:11 |
| SergeyLukjanov | the same as for sahara - tagging each 6 month ~ the same day with sahara | 13:11 |
| ttx | ok, that works | 13:12 |
| SergeyLukjanov | it's needed for coupling images builded for sahara and tools used inside of them | 13:12 |
| ttx | I'll apply the corresponding tag as needed :) | 13:12 |
| SergeyLukjanov | okay, thx :) | 13:12 |
| ttx | you dont use intermediary tags on those, right ? | 13:12 |
| * SergeyLukjanov lurking for gov changes :) | 13:12 | |
| SergeyLukjanov | ttx, we're using the kilo-X tags as well | 13:12 |
| ttx | ok | 13:13 |
| ttx | That's all the questions I had, thx | 13:13 |
| SergeyLukjanov | ttx, in fact all tags done for sahara are done for both extra and image-elements repos as well | 13:13 |
| ttx | ack. have a good day! | 13:13 |
| SergeyLukjanov | oh, I have a thing to share | 13:13 |
| ttx | listening | 13:13 |
| SergeyLukjanov | we have an issue with src juno job for sahara client | 13:13 |
| ttx | maybe #info it | 13:14 |
| SergeyLukjanov | we're now investigating it and we'd like to make it non-voting | 13:14 |
| SergeyLukjanov | for some time to avoid blocking client dev for kilo | 13:14 |
| SergeyLukjanov | heat-engine fails to load because saharaclient installed from source and heat checks versions | 13:14 |
| SergeyLukjanov | and that's extremely strange why only sahara job is failing | 13:15 |
| SergeyLukjanov | we're not trying to understand it | 13:15 |
| SergeyLukjanov | https://review.openstack.org/#/c/165038/ | 13:15 |
| ttx | ok | 13:16 |
| SergeyLukjanov | #info gate-tempest-dsvm-neutron-src-python-saharaclient-juno is now failing due to the very strange issue - heat-engine fails to load because saharaclient installed from source and heat checks versions and finds incorrect version (not <=0.7.6 defined in requirements.txt) | 13:16 |
| SergeyLukjanov | nothing else from my side | 13:16 |
| SergeyLukjanov | thx | 13:16 |
| ttx | cheers | 13:16 |
| SergeyLukjanov | ttx, have a good day! | 13:17 |
| ttx | dhellmann: https://review.openstack.org/#/c/162656/ failed gate on some horizon startup failure | 13:36 |
| ttx | Interesting: http://logstash.openstack.org/#eyJzZWFyY2giOiJcIm9wdC9zdGFjay9uZXcvZGV2c3RhY2svZXhlcmNpc2VzL2hvcml6b24uc2g6Mzk6ZGllXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MjY1OTk1MDQ0ODd9 | 13:38 |
| *** johnthetubaguy is now known as zz_johnthetubagu | 13:43 | |
| *** zz_johnthetubagu is now known as johnthetubaguy | 13:51 | |
| *** thingee has joined #openstack-relmgr-office | 14:18 | |
| ttx | thingee: if you want to go at your usual USA DST time, we can do it now | 14:25 |
| ttx | since I'm around anyway | 14:26 |
| thingee | ha I was just thinking of that | 14:26 |
| ttx | your call | 14:26 |
| thingee | sure sounds good to me | 14:27 |
| ttx | #topic Cinder | 14:27 |
| ttx | #link https://launchpad.net/cinder/+milestone/kilo-3 | 14:27 |
| ttx | So you seem to be all-set featurewise | 14:27 |
| ttx | but you might want to include a few more bugfixes before tagging µ? | 14:27 |
| thingee | yea, we still got some we have to take of. | 14:28 |
| thingee | and me as well ;) | 14:28 |
| ttx | Are any of those targeted bugs k3-critical ? Or can I just move them if they happen not to make it at tag time ? | 14:28 |
| thingee | I just went through the ones targeted and think they have a fair shot. They're all in review. | 14:29 |
| thingee | I removed the ones that have no reviews at this point. | 14:29 |
| ttx | OK, let's try to use the list as targets then | 14:29 |
| ttx | and tag when list is empty, and revise that on Thursday if necessary | 14:29 |
| thingee | sounds good | 14:30 |
| ttx | see PM for a few security issues pings | 14:32 |
| ttx | That's all I had | 14:32 |
| ttx | it's the calmest Cinder FF since a long time :) | 14:33 |
| thingee | :) | 14:33 |
| thingee | see the ML. I'm not a popular person | 14:34 |
| ttx | I'll let you go back to debunking security issues and review bugfix patches. | 14:34 |
| thingee | though I'm not sad to say no to patches coming in on March 10th for new features. | 14:34 |
| ttx | ok, have a great day then | 14:35 |
| thingee | have a great rest of your day! | 14:35 |
| ttx | nikhil_k: interested in speaking now ? I might have a call interrupting our usual time | 14:35 |
| ttx | mestery: same | 14:35 |
| nikhil_k | ttx: sure, trying to do double meeting | 14:36 |
| nikhil_k | another is audio | 14:36 |
| ttx | I'll go slowly | 14:36 |
| ttx | #topic Glance | 14:36 |
| nikhil_k | thanks | 14:36 |
| ttx | #link https://launchpad.net/glance/+milestone/kilo-3 | 14:36 |
| ttx | 3 BPs left on the docket | 14:36 |
| ttx | you sent an email on those, let me check | 14:37 |
| ttx | ok, so those are all candidates for a FFE if they don't make it | 14:37 |
| ttx | How far are they from completion ? | 14:38 |
| ttx | artifact-repository seems to be half-dozen patches away, but mostly proposed | 14:38 |
| nikhil_k | ttx: yes, I'm tentative on all three at this point. Catalog Index Service is still pending some last minute discussion/blockers. Artifacts is stuck on lot of reviews and the policy strenghthening is waiting on one confirmation due to a possible conflict/overlap with another feature. | 14:38 |
| ttx | ok, would be good to have at least one of those in by the deadline to limit the number of exceptions | 14:39 |
| ttx | #info last 3 BPs are likely to require exceptions | 14:39 |
| nikhil_k | ttx: how long can we go with FFE? | 14:39 |
| ttx | nikhil_k: on the targeted bugs side, I assume nothing is k3-critical and everything can be deferred to rc1 if not fixed by Thursday | 14:40 |
| nikhil_k | 1 week / 2 weeks? | 14:40 |
| ttx | nikhil_k: ideally max 10 days | 14:40 |
| nikhil_k | gotcha | 14:40 |
| ttx | (i.e. end of month) | 14:40 |
| nikhil_k | sure thing | 14:40 |
| mestery | ttx: here when ready | 14:40 |
| nikhil_k | ttx: about the bugs | 14:40 |
| ttx | #info Bugs can be deferred if needed | 14:40 |
| nikhil_k | ttx: this one https://review.openstack.org/#/c/119824/11 might be tricy https://launchpad.net/bugs/1365436 | 14:40 |
| openstack | Launchpad bug 1365436 in Glance "Database schema differs from migrations" [High,In progress] - Assigned to Oleksii Chuprykov (ochuprykov) | 14:41 |
| nikhil_k | I will try to review soon | 14:41 |
| nikhil_k | (that's it from me) | 14:41 |
| ttx | nikhil_k: ok, keeping an eye on it | 14:41 |
| ttx | #info Bug 1365436 should be solved before k3 ideally | 14:42 |
| openstack | bug 1365436 in Glance "Database schema differs from migrations" [High,In progress] https://launchpad.net/bugs/1365436 - Assigned to Oleksii Chuprykov (ochuprykov) | 14:42 |
| nikhil_k | thanks! | 14:42 |
| ttx | nikhil_k: that is all I had. We'll revisit progress on Thursday | 14:42 |
| ttx | cheers | 14:43 |
| nikhil_k | sure | 14:43 |
| ttx | mestery: o/ | 14:43 |
| ttx | #topic Neutron | 14:43 |
| mestery | ttx: o/ | 14:43 |
| ttx | #link https://launchpad.net/neutron/+milestone/kilo-3 | 14:43 |
| ttx | hmm, lots of open stuff there | 14:43 |
| mestery | Yup, so many are very close | 14:44 |
| mestery | But the reality is I need to start moving some of them out | 14:44 |
| mestery | We had a gate issue which killed our Fri-Mon the past weekend which was awful :( | 14:44 |
| ttx | you need to sort them so that those that are 99% there get priority reviews | 14:44 |
| mestery | Yes. | 14:44 |
| ttx | because otherwise they will all be at 98% on Thursday and just generate more pain | 14:45 |
| ttx | #info 34 open BPs | 14:45 |
| mestery | Indeed, I'm on that post this meeting and will get it down to the actual 5-8 that will make it | 14:45 |
| ttx | #info need to sort between FFE candidates, nearly-there and wont-make-it | 14:45 |
| ttx | How about we discuss again tomorrow and see how much you managed to clean up ? | 14:46 |
| mestery | Works for me. | 14:46 |
| mestery | The javelin/grenade issue just killed us, apologies for being behind a bit | 14:46 |
| mestery | I spent yesterday sheparding that and trying to recheck some stuff. *sigh* | 14:47 |
| ttx | On the bugs side, anything that should be k3-blocking ? | 14:47 |
| * mestery finds the one | 14:47 | |
| ttx | Or just move them all to RC1 as-needed ? | 14:47 |
| mestery | Well, actually, no none are K3 blocking | 14:47 |
| mestery | We have a few that may be RC blockers, but not K3 | 14:47 |
| ttx | they can be RC1-blocking alright | 14:47 |
| ttx | ok, so I'll just defer the open ones when we tag | 14:47 |
| mestery | Thanks ttx! | 14:48 |
| mestery | ++ to that | 14:48 |
| ttx | That is all I had | 14:48 |
| ttx | Talk to you tomorrow then | 14:48 |
| mestery | Me too, back to cleanup now | 14:48 |
| mestery | yes sir | 14:48 |
| mestery | later! | 14:48 |
| ttx | cheers | 14:48 |
| *** david-lyle_afk is now known as david-lyle | 14:57 | |
| *** SlickNik has joined #openstack-relmgr-office | 15:08 | |
| ttx | david-lyle: I'll be 5min late | 15:40 |
| david-lyle | ttx: no worries | 15:40 |
| ttx | #topic Horizon | 15:44 |
| ttx | david-lyle: hi! | 15:44 |
| david-lyle | ttx: hi | 15:44 |
| ttx | #link https://launchpad.net/horizon/+milestone/kilo-3 | 15:44 |
| ttx | 22 still on the docket, time for some pre-FF cleanup | 15:45 |
| david-lyle | yes indeed | 15:45 |
| *** thingee has quit IRC | 15:45 | |
| david-lyle | will cull today, the process continues | 15:45 |
| david-lyle | had to resharpen cleaver | 15:45 |
| ttx | yeah, would be good to split between FFE candidates, nearly-there and wont-make-it | 15:46 |
| ttx | so that you can actually focus on the 2nd category rather than dilute review effort | 15:46 |
| david-lyle | I have some status updates to roll in too | 15:46 |
| ttx | How about you process that and we discuss status of the remaining items tomorrow ? | 15:47 |
| david-lyle | I believe the launch instance bp finished merging last night | 15:47 |
| david-lyle | sure | 15:47 |
| ttx | On the bugs side I can't find anything k3-critical | 15:47 |
| ttx | so i'll just defer whatever didn't make it at tag time | 15:47 |
| david-lyle | yeah, nothing critical in the current list | 15:48 |
| david-lyle | I'm sure something will spring up | 15:48 |
| ttx | I had a question about tuskar-ui release model, if any | 15:48 |
| ttx | since it's a repo listed under horizon | 15:48 |
| david-lyle | IIRC I just tag it around release time | 15:49 |
| ttx | ok, so one tag every 6 months around cycle end ? | 15:49 |
| david-lyle | that's been the cadence | 15:50 |
| ttx | ok thx | 15:50 |
| ttx | david-lyle: and in that discussion here yesterday we said we'd probably need stable branches for django_openstack_ath, right | 15:51 |
| david-lyle | yes, trying to sort out what that means global-requirements wise | 15:51 |
| ttx | ok | 15:51 |
| ttx | so I'll be talking to you again tomorrow, in the mean time please refine and cut the k3 list | 15:52 |
| david-lyle | I could create a stable branch for 1.1.7 and use that for icehouse and juno, but the keystoneclient dependency isn't exact with the global-requirements for those branches | 15:52 |
| ttx | I created l1 milestones if you want to defer stuff | 15:52 |
| david-lyle | does that have to precisely match? | 15:53 |
| david-lyle | it requires keystoneclient slightly newer than the minimum | 15:53 |
| ttx | david-lyle: I think it does, but might want to cross-check with dhellmann | 15:53 |
| david-lyle | that's going to be a difficult shift then | 15:53 |
| david-lyle | will continue to look into it | 15:54 |
| david-lyle | might be nice to pin in requirements for current stable and cut a stable branch for kilo moving forward | 15:54 |
| ttx | ack, off-sync discussion | 15:54 |
| david-lyle | sure | 15:54 |
| ttx | sure, for kilo we can certainly converge | 15:54 |
| ttx | david-lyle: will talk to you more tomorrow | 15:55 |
| david-lyle | ttx: sounds good, thanks! | 15:55 |
| ttx | morganfainberg: around, | 16:51 |
| ttx | ? | 16:51 |
| morganfainberg | ttx: o/ | 16:51 |
| ttx | #topic Keystone | 16:51 |
| ttx | #link https://launchpad.net/keystone/+milestone/kilo-3 | 16:51 |
| ttx | 3 Bps on the list | 16:52 |
| ttx | https://blueprints.launchpad.net/keystone/+spec/klw-tokens | 16:52 |
| ttx | Thought that was mostly in | 16:52 |
| morganfainberg | Klw-tokens is almost done. We need a couple items reviewed should gate today. | 16:53 |
| ttx | ok | 16:53 |
| ttx | https://blueprints.launchpad.net/keystone/+spec/mapping-enhancements | 16:53 |
| ttx | looks done to me ? | 16:53 |
| ttx | or maybe pending https://review.openstack.org/#/c/163172/ | 16:53 |
| morganfainberg | Not sure. Might be 1 patch | 16:53 |
| morganfainberg | It's also very close. | 16:53 |
| ttx | https://blueprints.launchpad.net/keystone/+spec/model-timestamps | 16:54 |
| ttx | also seemùs one patch away | 16:54 |
| morganfainberg | The last one is a cleanup bp and should have no impact to api. It can move to post k3 | 16:54 |
| morganfainberg | and it will move to post k3 or l1 | 16:54 |
| ttx | #info 2 BPs very close should make it today/tomorrow, last one (model-timestamps) can be deferred | 16:54 |
| morganfainberg | Yep. | 16:55 |
| ttx | OK, sounds pretty close | 16:55 |
| ttx | On the bug side, I assume nothing is k3-critical and all non-merged can be deferred to rc1 | 16:55 |
| morganfainberg | There will be 2 FFEs requested. One has all the code ready just needs review, can't land it all before freeze though. The second is landing a couple final patches for a feature. | 16:56 |
| ttx | I suggest we reconvene on Thursday to tag, or ping me if earlier | 16:56 |
| morganfainberg | Bugs are fairly clear, nothing critical on my radar yet. | 16:56 |
| ttx | I had a few questions for you | 16:56 |
| morganfainberg | Sure. | 16:56 |
| ttx | first would you be available at the cross-project meeting today to discuss progress (or absence thereof) on new client in openstack-sdk | 16:57 |
| ttx | we discussed that back in December and promised a status update in Feb/Mar | 16:57 |
| ttx | can be quick :) | 16:57 |
| morganfainberg | Sure. And the answer is lack of progress afaik. I'll 2x check with jamielennox though. | 16:57 |
| ttx | second, I need to clarify a few release models for your secondary repositories | 16:58 |
| ttx | keystonemiddleware, pycadf and python-keystoneclient-* | 16:58 |
| ttx | keystonemiddleware seems released as-needed + one at the end of the cycle, is that a fair assumption ? | 16:58 |
| morganfainberg | Pycadf is like Oslo packages | 16:59 |
| ttx | ok so same as above | 16:59 |
| morganfainberg | Middleware is like client and typically released as needed. | 16:59 |
| morganfainberg | And yes, one at end of cycle. | 16:59 |
| ttx | and same for the client-* | 16:59 |
| morganfainberg | Yep. | 16:59 |
| ttx | OK makes all sense | 17:00 |
| ttx | That is all I had | 17:00 |
| ttx | anythgin on your side ? | 17:00 |
| morganfainberg | Nope. | 17:00 |
| ttx | alright then, talk to you Thursday if not earlier | 17:00 |
| ttx | notmyname: around? | 17:00 |
| notmyname | good morning | 17:00 |
| ttx | #topic Swift | 17:00 |
| ttx | notmyname: hi! | 17:00 |
| notmyname | hello | 17:00 |
| ttx | Same question as for Morgan | 17:00 |
| ttx | would you be available at the cross-project meeting today to discuss progress (or absence thereof) on new client in openstack-sdk | 17:01 |
| ttx | we discussed that back in December and promised a status update in Feb/Mar | 17:01 |
| ttx | can be quick | 17:01 |
| notmyname | if it's the first agenda item. | 17:01 |
| ttx | ok, that's the plan | 17:01 |
| notmyname | I was double booked with something else for the bottom of the hour | 17:01 |
| ttx | notmyname: second question would be on swift-bench -- I assume it's using the release:independent model, is that a good assumption ? | 17:02 |
| notmyname | same as python-swiftclient | 17:02 |
| ttx | fwiw swift seems to be release:managed, release:at-end-of-6mo-cycle *and* release:independent | 17:02 |
| ttx | notmyname: ok | 17:03 |
| notmyname | the managed one is surprising. is that because of the end of cycle one? | 17:03 |
| notmyname | I'd expected end-of-6mo and independent | 17:03 |
| ttx | notmyname: well, currently I still do the swift releases | 17:03 |
| notmyname | ah, I see | 17:03 |
| notmyname | that makes sense then | 17:04 |
| ttx | I agree that "managed" is tied to milestones, so I might not apply that | 17:04 |
| ttx | and do courtesy handling | 17:04 |
| ttx | and/or give you the tools and have you run with them | 17:04 |
| ttx | we'll refine as we go | 17:04 |
| notmyname | ok. that's something to consider (after kilo) | 17:04 |
| ttx | my added value in the swift release process is pretty slim | 17:04 |
| ttx | if I can get my tools properly documented, that would be an option | 17:05 |
| ttx | anywat, post-kilo | 17:05 |
| notmyname | hmm... rotating that among swift-core would be interesting | 17:05 |
| notmyname | anyway, post-kilo | 17:05 |
| ttx | how is development coming up ? | 17:05 |
| ttx | since last week ? | 17:05 |
| notmyname | for now, we're furiously working on EC stuff | 17:05 |
| notmyname | tons to do | 17:06 |
| notmyname | but here's the plan: | 17:06 |
| notmyname | when it's ready for master (end of next week (-ish), we'll freeze master and work on the merge to master | 17:06 |
| notmyname | like with storage policies, we'll tag the current feature branch (for history) and build a new patchset for the merge. ie cleaned up work | 17:07 |
| notmyname | and, like with storage policies, I'd like to work with -infra to land it as one merge commit instead of a ff merge | 17:07 |
| notmyname | and that gets us to the april 10 (-ish) target for a RC | 17:07 |
| ttx | sounds good | 17:07 |
| ttx | we'll keep track of that | 17:08 |
| notmyname | there's a few other non-ec things I'm tracking | 17:08 |
| notmyname | but the focus is ec | 17:08 |
| ttx | OK... anything else ? | 17:08 |
| notmyname | I proposed a bunch of tests to defcore | 17:08 |
| notmyname | the in-tree functional tests | 17:09 |
| notmyname | to the objectstore capability | 17:09 |
| notmyname | in addition to the existing 15 tempest tests listed, I added references to 279 swift functional tests | 17:09 |
| ttx | heh, ok | 17:09 |
| notmyname | #link https://review.openstack.org/#/c/164865/ | 17:10 |
| ttx | any other news ? | 17:10 |
| notmyname | so I think that's an important pattern for the TC->code->BoD interaction | 17:10 |
| notmyname | no, I think that's it. tons of work on EC. scary. committed to a beta. scope will be cut before the feature | 17:11 |
| ttx | alright, I'll let you run then | 17:11 |
| ttx | devananda: you around ? | 17:11 |
| ttx | notmyname: have a good week | 17:11 |
| notmyname | thanks. have a good day | 17:11 |
| devananda | ttx: hi! | 17:11 |
| ttx | here he is | 17:11 |
| ttx | #topic Ironic | 17:11 |
| ttx | #link https://launchpad.net/ironic/+milestone/kilo-3 | 17:11 |
| ttx | reading your email | 17:12 |
| devananda | I can paste the cliff notes here for record keeping | 17:13 |
| ttx | sure | 17:13 |
| devananda | we now have 7 BP open still | 17:13 |
| devananda | https://blueprints.launchpad.net/ironic/+spec/implement-cleaning-states hit an issue with devstack configuration that's blocking landing the code in ironic | 17:14 |
| devananda | once we can get that in (or work around it temporarily) that should be ready to merge | 17:14 |
| ttx | we can easily grant FFE to cover for the landing issue if that needs a few days | 17:14 |
| devananda | 3 more BPs are driver-specific and I'd really like to get them in, if possible | 17:15 |
| devananda | we've already bumped several other driver-specific pieces to Liberty | 17:15 |
| ttx | devananda: are they likely to hit the Thursday deadline ? | 17:15 |
| ttx | or will require FFE | 17:15 |
| devananda | right now, I'm about 50/50 on whether all of this will land by thursday | 17:15 |
| devananda | but - if it's not in by friday, I may just cut things that are driver-specific | 17:16 |
| ttx | the driver-specific ones are ilo-cleaning-support ilo-properties-capabilities-discovery and... ? | 17:16 |
| devananda | uefi-secure-boot | 17:16 |
| devananda | actually, sorry, uefi secure boot touches all the drivers | 17:17 |
| ttx | what about the last two (local-boot-support-with-partition-images & ipa-as-default-ramdisk) ? How close are they ? | 17:17 |
| devananda | it's the other one that might delay the release | 17:17 |
| devananda | automate-uefi-bios-iso-creation is the other driver-specific one, but it's also very small at this point and will probably land today | 17:17 |
| devananda | those two, I think, are done, though they are tagged on a UEFI-related review, and I'm waiting for feedback from the developers as to why | 17:18 |
| ttx | ok, let's discuss progress tomorrow (your morning) and see where we are at that point | 17:19 |
| devananda | sounds good | 17:19 |
| ttx | Had a question about ironic-pythonagent | 17:19 |
| devananda | sure | 17:19 |
| ttx | I suspect it's released as-needed | 17:19 |
| ttx | any reason we'd do a stable branch for it ? | 17:20 |
| devananda | indeed | 17:20 |
| devananda | possibly | 17:20 |
| ttx | i.e. have a release coinciding with the 6-month cycle ? | 17:20 |
| devananda | one of the story arcs of this cycle has been adding micro version support | 17:20 |
| devananda | there are two open reviews related to that on the server side, and a -lot- of work still in the client to fully utilize it | 17:20 |
| devananda | as we're now versioning the server API, it might make sense to tag clients at the same time | 17:21 |
| ttx | hmm, ok | 17:21 |
| devananda | OTOH, no future client release should ever be unable to talk to an old server | 17:21 |
| devananda | (within the supported window, which is TBD) | 17:21 |
| devananda | so making a statement like "to use the juno server, you need th ejuno client" -- we expressly do not want to do that | 17:21 |
| ttx | trying to see if release:at-6mo-cycle-end would apply to it | 17:22 |
| ttx | or if we'd need something finer for clients/libraries/agents | 17:22 |
| devananda | I will no doubt tag a client somewhere around the time we tag kilo rc, and probably again around kilo-final, and after that i'll tag it again ... | 17:22 |
| ttx | right, sounds like "having a stable branch" should be separated from "releasing at the end of the cycle" | 17:23 |
| devananda | I don't see a need to release the client and server in lock-step. and I don't want to, explicilty or implicitly, require folks to install an older client to talk to an older server | 17:23 |
| devananda | the more i think through it, the less i think a stable branch of python-ironicclient makes sense | 17:24 |
| ttx | yeah, so including clients on the tag might communicate the wrong intent | 17:24 |
| devananda | right | 17:24 |
| ttx | anyway, side discussion | 17:24 |
| ttx | thx for the input though | 17:24 |
| devananda | sure! | 17:24 |
| ttx | devananda: questions on your side ? | 17:24 |
| devananda | ttx: nope. I'm going to keep at the status page, trying to get everything green | 17:25 |
| devananda | tty tmw. same time? | 17:25 |
| ttx | alright, talk to you tomorrow | 17:25 |
| ttx | yes | 17:25 |
| ttx | SlickNik: around? | 17:25 |
| *** johnthetubaguy is now known as zz_johnthetubagu | 17:26 | |
| SlickNik | ttx: o/ | 17:27 |
| ttx | #topic Trove | 17:27 |
| ttx | #link https://launchpad.net/trove/+milestone/kilo-3 | 17:27 |
| ttx | Looks like 6 BPs still on the fence | 17:27 |
| ttx | https://blueprints.launchpad.net/trove/+spec/mgmt-show-deleted | 17:27 |
| ttx | This one looks relatively close | 17:27 |
| SlickNik | Yes, that should make it in by today, I'm guessing. | 17:28 |
| SlickNik | Close to the finish line. | 17:28 |
| ttx | https://blueprints.launchpad.net/trove/+spec/replication-v2 -- not very far either afaict | 17:28 |
| ttx | https://blueprints.launchpad.net/trove/+spec/vertica-db-support -- one patch pending too, but admittedly a large one ? | 17:29 |
| ttx | same for https://blueprints.launchpad.net/trove/+spec/couchdb-plugin-trove | 17:29 |
| ttx | https://blueprints.launchpad.net/trove/+spec/implement-vertica-cluster -- depends on the other, so likely to be late | 17:30 |
| ttx | https://blueprints.launchpad.net/trove/+spec/guest-rpc-ping-pong -- close to merge | 17:30 |
| SlickNik | https://blueprints.launchpad.net/trove/+spec/implement-vertica-cluster I'm concerned about. | 17:30 |
| ttx | yes, it's also a feature needing testing, so deferring might be the rigth call | 17:31 |
| ttx | rather than pushing it late in | 17:31 |
| ttx | How about we revisit tomorrow, once most of those will be in ? | 17:32 |
| SlickNik | ttx: agreed. I'll talk with the author (sushil) to see what's his take on that. | 17:32 |
| ttx | Would be great to push most in in the mean time | 17:32 |
| SlickNik | ttx: sounds good. I think at least 4-5 of those will have merged by then. | 17:32 |
| ttx | ack | 17:32 |
| ttx | On the bugs side, anything k3-critical ? | 17:32 |
| SlickNik | I'm working on getting folks to reviewthe patches by | 17:32 |
| ttx | Or can I just defer to RC1 anything that doesn't make it ? | 17:32 |
| SlickNik | ttx: We've fixed all the ones that are critical already. | 17:33 |
| SlickNik | So I'd defer anything in kilo-3 that doesn't make it (bugwise) to RC1 | 17:34 |
| ttx | alright then, I'll let you babysit patches and talk to you tomorrow | 17:34 |
| SlickNik | sounds good. will ping you if something comes up. | 17:34 |
| ttx | wfm | 17:35 |
| ttx | #endmeeting | 17:35 |
| openstack | Meeting ended Tue Mar 17 17:35:08 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:35 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-17-09.00.html | 17:35 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-17-09.00.txt | 17:35 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-03-17-09.00.log.html | 17:35 |
| SlickNik | Thanks ttx! | 17:35 |
| notmyname | ttx: still around? | 19:17 |
| ttx | notmyname: yes | 19:43 |
| notmyname | see #openstack-dev | 19:43 |
| *** asalkeld has joined #openstack-relmgr-office | 20:48 | |
| *** mestery has quit IRC | 20:55 | |
| *** mestery has joined #openstack-relmgr-office | 20:59 | |
| *** asalkeld has left #openstack-relmgr-office | 21:01 | |
| *** david-lyle is now known as david-lyle_afk | 23:50 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!