14:01:02 #startmeeting fwaas 14:01:04 Meeting started Tue Apr 4 14:01:02 2017 UTC and is due to finish in 60 minutes. The chair is xgerman. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:08 The meeting name has been set to 'fwaas' 14:01:15 #chair SridarK yushiro xgerman njohnston 14:01:16 Warning: Nick not in channel: yushiro 14:01:17 Current chairs: SridarK njohnston xgerman yushiro 14:01:30 #topic Announcements 14:01:50 So I saw that TC elections are coming up; so vote, vote,vopte 14:02:22 sorry got bounced 14:02:38 I have a conflict with another meeting so will lurk around 14:02:42 #chair SridarK_ 14:02:43 Current chairs: SridarK SridarK_ njohnston xgerman yushiro 14:03:11 o\/o 14:03:19 also P-1 is coming up: #link https://releases.openstack.org/pike/schedule.html 14:03:35 Hi. Sorry for late ;( 14:03:42 #chair yushiro 14:03:42 Current chairs: SridarK SridarK_ njohnston xgerman yushiro 14:03:58 no worries, was just going through announcements ;-) 14:04:02 anyhting else? 14:04:04 xgerman : whome to vote ??? 14:04:09 no idea 14:04:13 OK, thanks xgerman 14:04:34 Boston forum ideas? 14:04:55 mmh, nova says they are not very informative 14:05:21 who are not informative ? 14:05:24 nova? 14:05:35 the forums where you meet with end users/operators 14:06:19 #link https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg103433.html 14:07:05 #link http://forumtopics.openstack.org 14:07:41 I guess any exposure is good so hoangcx if you want to propose something I will show up (if my travel gets approved) 14:08:02 oh ok ... 14:08:38 xgerman I am waiting for travel approval too :-( 14:08:38 moving on… 14:09:15 #topic Pike 14:09:34 #link https://etherpad.openstack.org/p/fwaas-pike 14:10:26 I have seen movement on shared/public - reedip/yushiro? 14:10:31 yep 14:10:50 xgerman : vks1 already proposed a patch in neutron-fwaas and I proposed in neutron-lib 14:10:59 awesome! 14:11:04 yup. but sorry I am so swamped and not pushed yet into python-neutronclient 14:11:24 yushiro : I can help if you want 14:11:24 well, it’s supposed to be osc anyway ;-) 14:11:26 +1 i think this was a bit of taking a wrong turn early on 14:11:32 vks1, reedip Thank you so much for your great work :) 14:11:35 at least we have clarity 14:11:43 now 14:11:50 +1 14:11:51 For review : https://review.openstack.org/#/q/status:open+branch:master+topic:bug/1676922 14:12:58 xgerman : its OSC layer in NeutronClient :D 14:13:27 LBaaS has started some plugin… 14:14:11 also you need to name things differently, e.g. firewall rule create 14:14:27 so not sure how much work that will end up being 14:14:28 xgerman : I know about the octavia client :) 14:14:34 I am working on that with Ankur :) 14:14:57 cool, I am just afraid the osc work is more then we anticipate right now 14:15:11 xgerman : let me look into the OSC side, but it will take some time, so if someone else wants to take it up meanwhile, loop me in :) 14:17:20 ok, let’s keep an eye on that; yushiro let us know if there is anything we can help you with… 14:17:30 xgerman, Sure. 14:17:32 +1 14:17:39 next… L2 support 14:18:07 xgerman, driver or agent ? 14:18:13 both ;-) 14:18:16 :) 14:18:24 :P 14:18:38 on the driver side i need to make the co-existance work now 14:19:02 i have started some experiment but will take a little more time 14:19:37 the fwg delete api in driver is dependent on the default FWG implementation 14:19:49 on no progress on the delete part 14:19:59 no worries… I don’t think we need to release soemthing for 14:20:02 P-1 14:20:09 SridarK_? 14:20:23 chandanc : any reason for its dependency in the Default FWG implementation ? Just asking 14:20:24 yes, but any one helping with the agent side will be great 14:20:25 xgerman: yes agree - we have a few things we need to clear up here 14:20:47 reedip, yes, on delet ports need to be assigned to default FWG 14:20:57 reedip: yes ^^ 14:21:06 chandanc, yes 14:21:20 interesting use case 14:21:22 chandanc: i think we can work thru this while we settle down on this 14:21:29 if we do not have default FWG, then ? 14:21:47 SridarK_, please let me know your feedback on the plugin change 14:21:51 SridarK_, sure 14:22:16 chandanc: will do lets sync on this - sorry i am really swamped at work too 14:22:23 the plugin changes are part of the l2 ext agent patch 14:22:29 but lets close this either tomorrow or day after 14:22:32 SridarK_, no worries 14:22:34 chandanc, SridarK_ :I mean is it necessary to send it back to default FWG ? 14:22:38 reedip, If a user deletes default fwg, new default fwg will be generated automatically 14:22:58 SridarK_, sure 14:22:59 unless we switch it off (as discussed last week) 14:23:17 reedip: yes the default fwg will be the default if we remove something else configured 14:23:22 xgerman, i have some comments on reedip's mail 14:23:22 xgerman : exactly 14:23:27 xgerman: yes pending that 14:23:36 but i thing i got a bounce from your mail id 14:23:46 but we need a model when it is not turned off too 14:23:51 s/have/had/ 14:23:51 chandanc : I saw your email, but my intention was not to get rid of default FWG but keep it optional for the user 14:24:12 IIUC :) 14:24:40 reedip, i agree with your intentions :) only the implementation i have some concerns 14:24:58 yeah, and I can see us switching off = applying a default which allows or denies all 14:25:51 lets continue that in the Email itself .. SridarK_ , xgerman , yushiro , @all : your comments are pending :) 14:25:58 ok 14:26:08 reedip: yes i am guilty - sorry just not had a chance 14:26:16 but +1 lets discuss on email 14:26:17 sure reedip , i think xgerman mail id was wrong 14:26:17 aha, I'll reply it. sorry for slow 14:26:35 chandanc german.eichberger @ rackspace . com 14:27:00 xgerman : silly me :D 14:27:01 xgerman, will forward the thread 14:27:07 thanks 14:27:09 xgerman, you may need to update your email id on the etherpad 14:27:33 yep 14:27:42 a few of my previous mails bounced off 14:27:47 xgerman, thanks 14:28:21 sorry, forgot that update 14:28:30 xgerman : did u get it? 14:28:52 yep 14:29:30 ok, so where were we ? 14:29:44 well, next would be Horizon & Tempest 14:29:54 any updates? 14:29:59 lets close the default fwg on email 14:30:04 +1 14:30:07 +1 14:30:12 and on L2 chandanc lets see what else is pending 14:30:21 I am sorry, I was down sick for the last 6 days and could not make much progress 14:30:28 Did some catch up today: 14:30:29 SridarK_, sure 14:30:32 hope you feel better! 14:30:38 +1 14:30:48 thanks...am a bit better now 14:30:55 1. Created a project https://launchpad.net/neutron-fwaas-v2-dashboard on launchpad 14:31:04 2. Will also create a docs.openstack.org site for it 14:31:04 ohh 14:31:14 3. Generated the cookiecutter code for fwaas and compared it aginst lbaas 14:31:19 so we have a new project now ... 14:31:27 nice! 14:31:36 yeah.. its an individual project 14:31:49 need to support devstack as well 14:32:02 okk.... and it would be a part of neutron-dashboard in the future ???? 14:32:09 no 14:32:31 this is the new path set for all the neutron plugins 14:32:38 hmm .. ok... not sure whether its required for the stadium criteria, so we may need to clear that doubt up 14:32:40 such as fwaas, lbaas, vpnaas e.t.c 14:32:46 okk.... 14:33:16 I found some differneces against lbaas and two generaion options were not clear 14:33:31 I have a feeling that I can hack around and get the stuff working but not sure if its the right way to go 14:33:34 SarathMekala: one thought is that we can balance out the repo structure etc along with functionality - so worst case we do have something to demo (even if the code has not merged) 14:33:46 by Summit time 14:34:00 yeah SridarK_ , I can get that done 14:34:02 but lets do get the repo model right 14:34:05 SarathMekala you cna probably ask the horizon people what tey prefer 14:34:16 yes xgerman 14:34:18 Had a brief chat with Rob Cresswell.. will send across a detailed mail to him tonight and get things clarified 14:34:30 awesome — he’s the right guy 14:34:37 and Plan B is that u will be able to hack something that shows users what to expect 14:34:38 +1 14:35:14 as plan B we can go with the old structure and show case the usage.. it will be fast 14:35:29 Plan A is to hack the new model and get it working 14:35:49 regarding tempest, I didnt get the time, though I am looking into the fullstack now. I respun the neutron-lib patch of njohnston , and found some issues, have pushed the latest iteration 14:36:30 yeah, from what I have heard tempest is also a moving target since they actively move stuff into te,pest-lib 14:36:39 reedip: yes this seemed to run into some issues 14:36:49 I am targetting completing that patch so that API related changes then remain in neutron-lib itself 14:37:34 SridarK_ : right now,the duplicate extensions are an issue 14:38:10 but also , this patch is needed : https://review.openstack.org/453110 14:39:12 k, looks sane 14:41:24 moving on: 14:41:25 #topic performance improvement for v2 14:41:54 I'm still working on that 14:42:32 nice. 14:42:35 for now I've pushed some updates based on reviews of Cedric, but got a problem with ctypes 14:42:57 had a short discussion with Cedric too, but we couldn't figure out what happened 14:43:09 thats the same issue wrt to the gate's libraries, right ? 14:43:44 reedip, not really 14:43:53 cuongnv and Cedric Thank you so much. I'm sorry I couldn't review so much in these month.. 14:43:59 oh ok, thats a separate issue ?? :D 14:44:18 yushiro, yeah np 14:44:38 reedip, i think so, haven't took a deeper look yet 14:44:49 ok ... no issues 14:45:09 so, if anyone familiar with ctypes it'd be great for a help :) 14:45:55 my next action would be compare it with previous uploaded ps and discuss with Cedric to see what'd be the problem 14:46:40 that's all for performance improvement atm 14:46:42 cuongnv: I have same problem with ctypes, too.:) 14:47:13 yeah annp_ 14:48:02 if no one has any comments or questions, we can move on.. 14:48:06 blallau had some patches to speed up the RPC calls and DB queries 14:48:15 but I haven’t seen updates in a while… 14:49:16 xgerman, was there any problem with ctypes on that too? 14:49:21 let me spin up this one https://review.openstack.org/#/c/436978/ 14:49:32 remove the merge conflict and lets see where it takes us 14:49:52 cuongnv don’t think so… 14:50:00 xgerman, ok 14:50:23 thought you're continue with my problem :) 14:51:07 xgerman: i think blallau finished his work which should get us some good performance - but lets take a look to see something is pending 14:52:11 well, some of it we can’t merge without improvements — so wondering if we need to adopt the patches or if he will finish 14:52:33 e.g. #link https://review.openstack.org/#/c/428034/ 14:53:50 respun this https://review.openstack.org/436978 xgerman 14:53:54 xgerman: ok 14:53:56 thanks 14:54:31 ok, 6 minutes left… 14:54:49 #topic bugs 14:54:56 we did some cleanup… 14:55:01 kk 14:55:37 I'd like to have your guys reviews on this https://review.openstack.org/436978 14:55:50 xgerman, thanks for your review and +2 on that 14:56:21 cuongnv : whats the issue with 436978 ? 14:56:42 reedip, it's a fix for a port range bug 14:56:53 cuongnv wrong link? 14:56:59 yep 14:57:04 oh my 14:57:06 yeah, it is hoangcx :D 14:57:07 sorry guys 14:57:09 this one https://review.openstack.org/#/c/443385/ 14:57:10 thats what I thought :P 14:57:28 something wrong with my ctrl+c :D 14:58:05 yeah, we need to do more reviews… 14:58:22 okay, as it's been there for weeks, could you guys help to take a look? 14:58:24 2 min warning :-) 14:58:37 Yeah. Review velocity so slow, i guess 14:58:58 reedip, I've just added https://review.openstack.org/#/q/topic:bug/1676922 14:59:11 Pls review it. 14:59:15 Especially from fwaas cores 14:59:31 hoangcx: will look - just been too swamped 14:59:31 hoangcx we know :-( 14:59:45 hoangcx, indeeeeeeeeed ;( 14:59:53 :-) 15:00:20 over and out 15:00:20 ok, time 15:00:25 #endmeeting