09:00:28 #startmeeting ptl_sync 09:00:29 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:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:33 The meeting name has been set to 'ptl_sync' 09:00:36 #topic Heat 09:00:43 ttx sorry, i missed last weeks 09:00:48 #link https://launchpad.net/heat/+milestone/kilo-3 09:00:56 asalkeld: not a problem, I skipped most of them anyway 09:01:08 So... crunch time 09:01:16 6 BPs up 09:01:19 so most are very close to getting merged 09:01:29 Let's go through them one by one 09:01:30 so i am not very stressed about them 09:01:34 ok 09:01:36 https://blueprints.launchpad.net/heat/+spec/convergence-resource-table 09:01:51 Only needing https://review.openstack.org/#/c/156693/ ? 09:01:58 that's a one patch spec 09:02:00 yip 09:02:05 should get in soon 09:02:08 https://blueprints.launchpad.net/heat/+spec/decouple-nested 09:02:14 that's mine 09:02:25 *should* get it in time 09:02:39 3 patches up, all working well 09:02:54 some disent amounst the minions;) 09:03:06 https://blueprints.launchpad.net/heat/+spec/convergence-lightweight-stack 09:03:18 that might well miss 09:03:32 but it't only one patch 09:03:43 so willing to wait until the death 09:03:49 I see two patches 09:04:11 If that one misses, do you intend to request FFE for it ? 09:04:26 ttx: it can just wait 09:04:27 If not, maybe prioritize to Medium 09:04:31 ok 09:04:40 I assume the first two would get exceptions 09:04:46 if they missed 09:04:58 https://blueprints.launchpad.net/heat/+spec/convergence-push-data 09:05:20 that should be ok 09:05:26 again one patch 09:05:44 OK, it's linked to the other 09:05:56 https://blueprints.launchpad.net/heat/+spec/mistral-resources-for-heat 09:06:06 Looks like 2 patches 09:06:24 so this is a bp for code that goes into contrib/ 09:06:36 so IMO it can go in any time 09:06:46 (does not effect strings or deps) 09:06:51 yeah, at least could get an exception as "self-contained" 09:07:00 and gets installed seperately 09:07:00 https://blueprints.launchpad.net/heat/+spec/stack-breakpoint 09:07:23 there are 2 or 3 guys trying hard to get that in 09:07:29 it should make it 09:07:44 needed for tripelo 09:07:52 ok we'll see how it goes 09:08:10 yeah, we can wait 09:08:20 On the bugs side... anything k3-critical that we would not just defer to rc1 ? 09:08:24 they are all on the edge of getting merged 09:08:47 i think just defer everything that's not merged 09:09:04 #info k3 bugs can be deferred to rc1 if incomplete 09:09:26 #info 6 BPs left, all still standing a reasonable chance of making it 09:09:37 * asalkeld is hopeful 09:10:11 OK, that's all I guess. We'll make a new status point on Thursday (your evening, my morning) 09:10:26 hopefully for the final tag / early FFE decisions 09:10:29 ok - same time? 09:10:46 (just want to make a reminder) 09:10:46 sounds good. Ping me if I don't talk 09:10:59 ok, chat then 09:11:21 see you! 09:11:40 zz_johnthetubagu: around? 09:17:06 johnthetubaguy: o/ 09:17:25 ttx: hi 09:17:28 #topic Nova 09:17:35 #link https://launchpad.net/nova/+milestone/kilo-3 09:17:52 That's still 12 BPs in progress 09:18:05 Let's see how far they are 09:18:11 https://blueprints.launchpad.net/nova/+spec/v2-on-v3-api 09:18:29 I see 4 patches on https://review.openstack.org/#/q/topic:bp/v2-on-v3-api,n,z 09:18:53 But the last says it partially implements so it looks like there is more to it 09:19:49 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:20:19 Those might be add-ons patches 09:20:20 ah, yes, I think a lot of this is now unit test clean up 09:20:52 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:53 well, general cleanups anyways 09:21:02 https://blueprints.launchpad.net/nova/+spec/api-microversions 09:21:05 agreed, but folks do like the tracking 09:21:07 seems to be in the same situation 09:21:12 yes 09:21:37 #info v2-on-v3-api and api-microversions are "mostly finished" 09:21:46 https://blueprints.launchpad.net/nova/+spec/cells-v2-mapping 09:22:00 This one will be partial IIUC 09:22:24 in which case it is "mostly finished" too, I suspect 09:22:51 yes, there are a few patches, I think they wanted, but as you say, its kinda partial anyways 09:23:00 https://blueprints.launchpad.net/nova/+spec/kilo-objects 09:23:15 this one is basically tracking cleanups 09:23:21 Feels like another "what's in kilo is kilo" 09:23:27 right 09:23:47 its a tracking placeholder to help with reviews more than anything 09:23:51 #info cells-v2-mapping and kilo-objects are partial work anyway, so what's in kilo is kilo 09:24:02 https://blueprints.launchpad.net/nova/+spec/online-schema-changes 09:24:12 one last patch there I think 09:24:26 pending on https://review.openstack.org/#/c/154521/ 09:24:43 #info online-schema-changes pending on https://review.openstack.org/#/c/154521/ -- looking good 09:24:55 it says "partially implements" though 09:25:57 https://blueprints.launchpad.net/nova/+spec/make-resource-tracker-use-objects 09:26:11 yeah, thats true, I will check, but I thought that was it 09:26:27 Lots of patches up 09:26:46 This one sounds more at risk 09:27:00 although it's marked partial too 09:27:17 oh yes, I think you are right, that one was close to getting kicked out already 09:27:37 #info make-resource-tracker-use-objects might be so partial it could be considered deferred 09:27:46 https://blueprints.launchpad.net/nova/+spec/detach-service-from-computenode 09:28:07 I will check out that one closer after the meeting 09:28:23 Not sure what's waiting on 09:28:37 it might be done now, as much as it will be in kilo, let me check 09:29:05 you can check after meeting, no worry 09:29:16 yep is done, although its technically, a bit partial 09:29:22 #info detach-service-from-computenode might be considered finished 09:29:38 OK, medium stuff now 09:29:43 https://blueprints.launchpad.net/nova/+spec/keypair-x509-certificates 09:30:21 Remaining patches are novaclient and a bug fix 09:30:37 yes, they need work really 09:30:43 so we could move them to RC1 if necessary 09:30:56 and consider this finished 09:31:12 yes, I think thats probably easiest, I might open bugs for those patches 09:31:14 #info keypair-x509-certificates could just be considered finished and remaining bugs pushed to RC1 if need be 09:31:26 https://blueprints.launchpad.net/nova/+spec/v3-api-policy 09:31:39 This one is marked partial, so probably another of those "what's in kilo is kilo" 09:32:08 possibly, there are a few patches they really want in kilo, its on the etherpad I think 09:32:08 Loads of patches there 09:32:22 yeah, its a streatch to get those all in 09:32:33 #info v3-api-policy needs work, will be partial 09:32:46 https://blueprints.launchpad.net/nova/+spec/ec2-api 09:33:04 Isn't that finished? 09:33:53 I think it is 09:33:56 #info ec2-api is probably finished 09:34:02 https://blueprints.launchpad.net/nova/+spec/servicegroup-api-is-up-host-topic 09:34:34 A bit unclear what it's waiting on 09:34:42 also marked partial 09:35:22 I think its this one: https://review.openstack.org/#/c/149924/ 09:36:00 #info servicegroup-api-is-up-host-topic pending on https://review.openstack.org/#/c/149924/ 09:36:08 its a clean up though, so I might just remove the blueprint tag, lets see 09:36:29 https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring 09:36:37 That one looks forever partial 09:37:05 and candidate for deferral 09:37:15 #info hyper-v-test-refactoring may or may not make it 09:37:29 yeah, I vote we defer the BP, I mean its unit tests, so they can merge later if needed I guess 09:37:45 yeah, I'm more afraid of the distration than of the impact 09:37:50 distraction 09:38:34 #info 10 blueprints left, mostly partial & "what's in kilo will be kilo" work anyway 09:38:56 Quick look on the bugs side, see if any of those "critical" are actually k3-critical 09:39:09 like regressions 09:39:14 or showstoppers 09:40:12 https://bugs.launchpad.net/nova/+bug/1383465 is unlikely to be solved in the next two days 09:40:13 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:26 nothing that stops kilo-3 from a quick look, right, thats the only big one 09:40:35 it got discussed in the nova meeting again 09:40:43 trying to move that forward before kilo ships 09:40:57 it was targeted to kilo-1 I think 09:41:16 and passed forward 09:41:34 https://bugs.launchpad.net/nova/+bug/1296414 is another of those long-standing issues 09:41:35 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:42:06 ok, so I'll push to RC1 anything not merged by tag time 09:42:14 #info Bugs to be deferred if not merged 09:42:34 sounds good 09:42:44 I will ask around to see if there are any exceptions to that 09:42:48 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:59 that sounds like a plan 09:43:04 same time ? 09:43:13 yes, I will pop that in my calendar now 09:43:23 sounds good, have a good day! 09:43:37 you too! 12:24:46 ttx: ready when you are 12:25:16 dhellmann: you might be one hour early, but we can probably do it nevertheless 12:25:37 ttx: oh, right, forgot you're not on dst yet 12:25:57 no pb, if you're available now, let's do this 12:26:03 sure thing 12:26:05 #topic Oslo 12:26:24 A quick look at milestone pages 12:26:30 #link https://launchpad.net/oslo/+milestone/kilo-3 12:26:58 there is a bug targeted: https://bugs.launchpad.net/cinder/+bug/1417018 12:26:59 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:27:07 is that something we want to fix and sync in kilo ? 12:27:10 yeah, that one is actually done in oslo.db -- I'll be making a release later today 12:27:30 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:35 I'll update the targets 12:27:40 ok cool 12:28:17 https://launchpad.net/oslo/+milestone/next-kilo shows a bunch of PBR bugfixes 12:28:23 is there a PBR release planned ? 12:28:43 or would those actually appear in next-liberty ? 12:28:46 ttx: not to include those items. I'll retarget them too 12:28:54 ok 12:29:09 Looking at https://review.openstack.org/#/c/162656/ 12:29:12 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:37 do you think we should collect more +2s ? Or should I just W+1 it ? 12:30:09 not sure why the subsequent reviewers didn't w+1 12:30:32 yeah, sdague expressed some reservations and that may have made people hold off on the w+1 12:30:45 I would like to get that in asap so we can also land the subsequent requirements updates to the projects 12:31:02 the requirements freeze is this week, right? 12:31:03 yeah, timing is tight 12:31:04 jogo is +1 on that now, I'll approve 12:31:17 sdague: thanks, I was going to check in with you on that in a bit anyway 12:31:22 that's going to trigger a ton of patch / test churn, btw 12:31:23 requirements freeze is same as feature freeze yes 12:31:37 sdague: yeah, that's why I did it all in one patch :-) 12:31:42 :) 12:31:51 sdague: should we generally try do those one week earlier ? 12:31:59 ttx: probably 12:32:28 I expect we'll consume all the test nodes on the proposal bot changes for that one 12:32:31 note that those could technically land post-requirements freeze, since requirements freeze is mostly to guard against additions 12:32:32 I think we would have been ready a week earlier this cycle except for the deprecation warning issue 12:32:52 ttx: ok, as long as it lands before the branches are made I think we're ok 12:32:56 so I'm fine with those landing post-FF pre-RC1 12:33:07 I'm OK with that if we want to preserve test nodes 12:33:09 if we think approving this now is a bad idea 12:33:20 I can update the policy document to reflect that change, too 12:33:24 (requirements sync is part of the RC1 process) 12:33:31 zuul still has capacity this morning 12:33:47 so anyway, it's approved 12:33:54 ok, thanks, sdague 12:34:36 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:48 First, looking at Oslo libs 12:35:25 I suspect some of them don't really apply 12:35:30 for example openstack-dev/pbr 12:35:33 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:50 I need to get the pbr team inline with the rest of oslo 12:35:55 what about openstack-dev/cookiecutter ? 12:36:04 (and openstack-dev/oslo-cookiecutter) 12:36:33 oh, we don't release that, that's just a template for making new projects 12:36:41 you use it straight from the git url 12:36:46 right, so those would not have release:* tags 12:36:52 right 12:37:22 so what should I do about taskflow/pbr ? Consider them in ? 12:37:36 yes, let's consider them in and I'll talk to the maintainers 12:37:47 Second question is about python-*client, to piggyback on your discussion with David Lyle recently 12:38:05 I'm a bit confused if we should consider them in (as in having stable branches) 12:38:24 I think they might be release:independent, really 12:38:37 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:39:06 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:22 that lets us test new clients from the outside of the cloud while using stable clients inside the cloud 12:39:47 hmm, ok. So they should be at-6mo-end 12:39:57 even if technically they don't have stable branches until needed 12:40:09 yes, unless someone else comes up with an alternative to my stable-library spec 12:40:31 Applying tags results in uncovering interesting corner cases to say the least 12:40:44 true 12:41:01 at the very least helps clarify things, even for us 12:41:18 ok, I think that's all I had in store for you 12:41:27 ok, I had a couple for you 12:41:58 do we have any lib left to release for kilo ? You mentioned pbr ? 12:42:03 that policy on stable branches for libs should be prioritized: https://review.openstack.org/155072 12:42:22 yeah, I added it to todays meeting agenda 12:42:23 I have a backported fix for oslo.db that I will release today, but I don't anticipate any other releases 12:42:27 ok, good 12:42:35 (cross-project meeting) 12:42:37 and do we know the dates for the fall summit yet? 12:42:47 in silence is consent mode 12:43:00 I think we do, let me check 12:43:17 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:27 https://www.openstack.org/summit/tokyo-2015/ 12:43:40 October 26 - 30, 2015 12:43:41 ah, ok thanks 12:43:54 That may not be linked to yet, but the page is public 12:44:01 and the URL is not that hard to guess 12:44:10 yeah, I should have tried that :-) 12:44:20 actually it's linked 12:44:25 https://www.openstack.org/summit/ 12:44:47 so consider it public :) 12:45:08 I was looking on https://www.openstack.org/community/events/ 12:45:31 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:38 anyway, thanks, I should have looked harder :-) 12:45:59 that's all I had for this week 12:46:48 dhellmann: so in summary, next steps are merging requirements patch (but that's arguably non-oslo-specific 12:46:55 and get that policy approved 12:47:05 otherwise you're mostly done release-wise ? 12:47:20 yes, I believe that's it 12:47:34 dhellmann: we could push the kilo-3 tag on oslo-incubator now 12:47:37 we'll obviously do patch releases if we need to, but the branches are created so we can do that 12:47:44 since we did a 2015.1.0b2 12:48:19 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:33 do you want to do that, or shall I? 12:48:39 I'll do it now 12:48:41 ok 12:49:41 done 12:49:47 cool, thanks 12:50:07 ok, thx and have a good day! 12:50:12 you, too! 13:05:22 ttx, /me ready when you are 13:05:47 SergeyLukjanov: hi! 13:05:53 #topic Sahara 13:05:56 ttx, hello! 13:05:58 #link https://launchpad.net/sahara/+milestone/kilo-3 13:06:14 so, we have mostly everything planned done 13:06:20 8 still up 13:06:27 except few things that are now candidates for FFE 13:06:44 stuff that is under review now is expected to be merged today/tomorrow 13:07:02 SergeyLukjanov: ok 13:07:16 What are the FFE candidates ? edp-job-types-endpoint ? 13:07:51 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:08:19 #info edp-job-types-endpoint likely FFE 13:08:20 the same for "Provide default templates for each plugin" https://blueprints.launchpad.net/sahara/+spec/default-templates 13:08:53 #info default-templates likely FFE 13:08:53 and probably for edp-datasource-placeholders as well 13:09:07 #info edp-datasource-placeholders likely FFE 13:09:16 the others shall merge before the k3 date 13:09:22 yup 13:09:40 OK, any k3-blocking bug ? Or can I just defer them to rc1 isf they miss target , 13:09:42 ? 13:09:43 I expect sahara to be ready for tag cut on Thu EU morning 13:09:59 no k3-blocking bugs 13:10:33 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:42 OK. I had a question for you on dashboard, extra and image-elements 13:10:50 and anyway they aren't importnat 13:10:53 yeah 13:10:53 how many of those are actually still in use ? 13:11:05 dashboard is only for stable/icehouse 13:11:13 starting from Juno it's moved to horizon repo 13:11:26 extra and s-i-e are in use 13:11:29 what is the release model for extra and image-elements ? 13:11:39 once at the end of the 6-month cycle ? 13:11:54 the same as for sahara - tagging each 6 month ~ the same day with sahara 13:12:05 ok, that works 13:12:11 it's needed for coupling images builded for sahara and tools used inside of them 13:12:19 I'll apply the corresponding tag as needed :) 13:12:25 okay, thx :) 13:12:38 you dont use intermediary tags on those, right ? 13:12:41 * SergeyLukjanov lurking for gov changes :) 13:12:58 ttx, we're using the kilo-X tags as well 13:13:05 ok 13:13:19 That's all the questions I had, thx 13:13:23 ttx, in fact all tags done for sahara are done for both extra and image-elements repos as well 13:13:34 ack. have a good day! 13:13:35 oh, I have a thing to share 13:13:44 listening 13:13:50 we have an issue with src juno job for sahara client 13:14:01 maybe #info it 13:14:20 we're now investigating it and we'd like to make it non-voting 13:14:27 for some time to avoid blocking client dev for kilo 13:14:50 heat-engine fails to load because saharaclient installed from source and heat checks versions 13:15:05 and that's extremely strange why only sahara job is failing 13:15:16 we're not trying to understand it 13:15:34 https://review.openstack.org/#/c/165038/ 13:16:24 ok 13:16:27 #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:38 nothing else from my side 13:16:39 thx 13:16:44 cheers 13:17:08 ttx, have a good day! 13:36:27 dhellmann: https://review.openstack.org/#/c/162656/ failed gate on some horizon startup failure 13:38:36 Interesting: http://logstash.openstack.org/#eyJzZWFyY2giOiJcIm9wdC9zdGFjay9uZXcvZGV2c3RhY2svZXhlcmNpc2VzL2hvcml6b24uc2g6Mzk6ZGllXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjE3MjgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MjY1OTk1MDQ0ODd9 14:25:53 thingee: if you want to go at your usual USA DST time, we can do it now 14:26:11 since I'm around anyway 14:26:40 ha I was just thinking of that 14:26:47 your call 14:27:01 sure sounds good to me 14:27:06 #topic Cinder 14:27:12 #link https://launchpad.net/cinder/+milestone/kilo-3 14:27:25 So you seem to be all-set featurewise 14:27:47 but you might want to include a few more bugfixes before tagging �? 14:28:27 yea, we still got some we have to take of. 14:28:32 and me as well ;) 14:28:40 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:29:17 I just went through the ones targeted and think they have a fair shot. They're all in review. 14:29:32 I removed the ones that have no reviews at this point. 14:29:37 OK, let's try to use the list as targets then 14:29:52 and tag when list is empty, and revise that on Thursday if necessary 14:30:03 sounds good 14:32:46 see PM for a few security issues pings 14:32:52 That's all I had 14:33:06 it's the calmest Cinder FF since a long time :) 14:33:46 :) 14:34:07 see the ML. I'm not a popular person 14:34:08 I'll let you go back to debunking security issues and review bugfix patches. 14:34:23 though I'm not sad to say no to patches coming in on March 10th for new features. 14:35:13 ok, have a great day then 14:35:41 have a great rest of your day! 14:35:44 nikhil_k: interested in speaking now ? I might have a call interrupting our usual time 14:35:53 mestery: same 14:36:05 ttx: sure, trying to do double meeting 14:36:13 another is audio 14:36:20 I'll go slowly 14:36:23 #topic Glance 14:36:27 thanks 14:36:37 #link https://launchpad.net/glance/+milestone/kilo-3 14:36:44 3 BPs left on the docket 14:37:06 you sent an email on those, let me check 14:37:50 ok, so those are all candidates for a FFE if they don't make it 14:38:01 How far are they from completion ? 14:38:43 artifact-repository seems to be half-dozen patches away, but mostly proposed 14:38:48 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:39:20 ok, would be good to have at least one of those in by the deadline to limit the number of exceptions 14:39:28 #info last 3 BPs are likely to require exceptions 14:39:54 ttx: how long can we go with FFE? 14:40:02 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:09 1 week / 2 weeks? 14:40:10 nikhil_k: ideally max 10 days 14:40:15 gotcha 14:40:22 (i.e. end of month) 14:40:29 sure thing 14:40:42 ttx: here when ready 14:40:43 ttx: about the bugs 14:40:44 #info Bugs can be deferred if needed 14:40:59 ttx: this one https://review.openstack.org/#/c/119824/11 might be tricy https://launchpad.net/bugs/1365436 14:41:00 Launchpad bug 1365436 in Glance "Database schema differs from migrations" [High,In progress] - Assigned to Oleksii Chuprykov (ochuprykov) 14:41:13 I will try to review soon 14:41:20 (that's it from me) 14:41:48 nikhil_k: ok, keeping an eye on it 14:42:26