15:01:28 #startmeeting horizon 15:01:29 Meeting started Wed Jul 29 15:01:28 2020 UTC and is due to finish in 60 minutes. The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:33 The meeting name has been set to 'horizon' 15:01:33 hi 15:01:35 hi 15:01:44 hi 15:03:20 let's wait two minutes more if somebody joins us 15:05:33 #topic Notices 15:06:05 this week is victoria-2 milesone https://releases.openstack.org/victoria/schedule.html 15:06:21 we discussed it during the previous meeting 15:06:44 I didn't find deprecated features to be removed in victoria 15:06:59 of course, I could miss something 15:08:12 but it looks like there is nothing special for horizon to make victoria-2 release 15:08:33 we have to drop this https://opendev.org/openstack/horizon/src/branch/master/openstack_dashboard/usage/quotas.py#L365 in victoria cycle. 15:09:17 I would like to ask amotoki for this as a neutron expert 15:09:21 amotoki: any plans of doing this? 15:10:17 e0ne: yeah, it is a long-standing topic. 15:11:05 most neutron deployments are ready for it, but there is only one exception, contrail based deployments..... 15:11:35 amotoki: that's was my point 15:11:37 contrail based deployments has completely different neutron implementations and it is always a headache for us. 15:11:44 I was looking for this https://review.opendev.org/#/c/707774/ patch 15:12:28 anyway, we can discuss it later 15:13:02 the contrail plugin only implements the neutron API long ago and it does not follow all changes... so it is a fork of neutron 15:13:14 I have no idea on how to support it. 15:13:18 :( 15:14:25 as my hat of neutron liaison, I cannot support it and spend time on reviewing it without more volunteers from contrail based consumers 15:15:23 that's the reason I moved it to the deprecation status in the last cycle. 15:15:26 I'm working with contrail-base deployments but I'm not expert in it at all 15:16:11 btw just for curiosity what is "contrail-base deployments" ? 15:16:33 we have always handled such issues only based on bug reports but at least we have some contributions from operators (not from vendors) on this 15:16:35 I mean contrail-based 15:17:37 amotoki: the patch above is from my colleague from contrail team 15:19:22 I am okay to keep the support, but the difficulty is that such report does not mention it and detail discussions in bug reports reveal it. it is a waste of time to me. I hope someone is aware of it. 15:19:49 I just wanna a person who takes care of it 15:19:55 amotoki: sure, we need to have bug reports for such patches 15:20:47 e0ne: the similar situation happens for ceph, so I am not so against only for contrail/tungstenfabric 15:21:07 amotoki: what do you mean? 15:21:33 amotoki: I'm not familiar with any ceph-related issues in horizon 15:21:44 e0ne: ceph's swift support is sometimes a variant and it is sometimes a headache 15:22:17 amotoki: yes, I understand you. we've got such bugs reported time to time 15:22:28 ceph implements a dialect of the Swift API for example the capability support. we had a bug report 15:22:59 amotoki: usually, we can't fix such bugs from horizon's side 15:23:27 but we need to ask people to add details into the launchpad about their environments 15:23:50 yeah 15:26:13 back to the topic on neutron quota_details, one aggresive idea is to drop the support once. They have choices: to implement quotas_detail (which was implemeted four or more releases ago) or to blame horizon 15:27:27 haha🙂) 15:28:08 :) 15:28:51 in any case, we won't remove it right now so we've got nothing critical to release victoria-2 15:28:59 back to serious, what is the possible next step? 15:29:38 I'm interesting in contrail/tf support in horizon because our customers uses it 15:30:01 sounds fair 15:30:31 but I can't review related patches because we've got a dedicated team to work with contrail, so I don't have a lot of experience in this area 15:31:53 it shows the fact that many developers have been changed in neutron and horizon so it is not easy to only understand the background now 15:31:54 I mean, I can't review patches from contrail perspective 15:32:52 what I can do is to add more NOTE comments on this to the related pieces of codes. 15:33:17 like "NOTE: It is for contrail requirements" :) 15:34:14 it could be useful 15:34:58 okay, our consensus so far is: 15:35:29 (1) to keep neutron quota supports WITHOUT quota_details (at least for contrail/tf) 15:36:09 (2) amotoki will add more context on this to the related codes 15:36:24 okay? 15:36:31 sounds good 15:36:50 thanks 15:37:48 let's move on 15:38:03 CFP for the next Virtual Open Infra summit is open until Aug 4th 15:38:13 #link https://www.openstack.org/summit/2020/ 15:38:53 if you're going to submit your talk proposal for the next summit, you've got few more days 15:39:24 it will be a free full-virtual event 15:40:25 Horizon virtual mid-cycle 15:40:33 only vishalmanchanda voted yet 15:40:34 #link https://doodle.com/poll/3neps94amcreaw8q? 15:40:49 I'm going to send one more email for it 15:41:04 probably, we need to re-shcedule it 15:41:15 I thought the candidate dates are updated. 15:41:27 so it won't be not a mid-cycle but late-cycle meetup 15:41:29 so I didn't vote it 15:41:52 amotoki: my fail 15:42:15 I have to register to doodle.com to change a description 15:42:23 e0ne: how long do you think it is? 15:42:58 amotoki: sorry, what actually do you mean? 15:43:13 e0ne: how many hours/days do you expect? 15:43:40 I was expecting for one day/one hour for sure 15:44:07 I don't expect a lot of participators there 15:44:11 ( 15:45:14 I am planning to join it during my vacation week after a bit thinking (as changing my off week needs duplicated procedure and perhaps extra off would be easier) 15:46:26 perhaps wed/thur would be fine 15:48:42 I've updated the poll 15:48:44 #link https://doodle.com/poll/dkmsai49v4zzpca2 15:48:52 vishalmanchanda: please, vote again 15:48:59 sure. 15:49:07 I'll send a mail notification after the meeting 15:49:13 vishalmanchanda: thank you 15:50:09 #topic Open Discussion 15:50:16 we've got 10 minutes left 15:50:25 I have a couple of small things 15:50:32 amotoki: sure 15:50:40 the first one is https://review.opendev.org/#/c/743600/ 15:50:57 it is against the deprecation of OPENSTACK_NOVA_EXTENSIONS_BLACKLIST 15:51:20 I think we need to ask nova team 15:51:31 I posted my opinion to introduce new corresponding settings. I hope your thoughts on this 15:51:40 we should follow their decision on it 15:52:07 e0ne: I had a discussion with mridemm a year ago and it sounds reaosnable to drop the nova extension support. 15:52:35 the problem looks like how we can migrate the era without nova extension 15:52:40 amotoki: did nova deprecated extensions? 15:52:45 s/migrate/migrate horizon/ 15:53:04 e0ne: nova dropped the extension support several releases ago 15:53:23 it means we should do it too 15:53:37 but it happened in the microversion 15:53:52 nova API v2.1 (mirror of v2.0) still supports it 15:53:53 * e0ne hates microversions 15:54:07 it is the reason we can still use the nova extension API. 15:54:43 but novaclient already dropped it and horizon has the nova extension list as hardcode in our code. 15:54:58 so it is now an issue in horizon 15:55:17 looks like we have to go forward and use new microversion API 15:55:33 I have a full history on this and can discuss it with mnaser in the review (or in IRC) 15:56:36 it would be good to understand what actually works slow 15:56:55 yeah 15:57:05 the other thing is about the policy support. e0ne, have you discuss something with oslo.policy team? 15:57:24 amotoki: no, I didn't 15:57:27 if not, I will discuss it in the policy pop-up team 15:57:40 I am writing my draft on the policy support and can cover it. 15:57:49 great! 15:58:12 I just would like to confrim the situation. np 15:58:45 that's all from me 15:59:27 Can I have a review on this patch https://review.opendev.org/#/c/708069/ 16:00:55 vishalmanchanda: thanks for working on this. I failed to find time these weeks due to events and others... will review it but not immediately, sorry 16:01:20 amotoki: ohk, will wait. 16:01:29 bye. 16:02:01 we're out of time 16:02:12 thanks all 16:02:21 we can continue our conversation in #openstack-horizon channel 16:02:24 it was a good time to sync 16:02:33 thanks for the participation 16:02:39 amotoki: +1 16:02:45 #endmeeting