14:00:54 #startmeeting fwaas 14:00:55 Meeting started Tue Mar 28 14:00:54 2017 UTC and is due to finish in 60 minutes. The chair is SridarK_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:58 The meeting name has been set to 'fwaas' 14:01:09 #chair xgerman yushiro 14:01:10 Current chairs: SridarK_ xgerman yushiro 14:01:48 Not sure if more folks have joined 14:01:49 o/ 14:01:51 o/ 14:01:54 Hello All 14:01:57 hi 14:02:00 ah there :-) 14:02:12 lets get started 14:02:51 I did not have any significant annnouncements 14:03:16 v2 Horizon Patch is up for first review SridarK_ : 14:03:27 thats an announcement :D 14:03:27 Yes lets pick that up 14:03:35 :-) 14:03:43 #topic FWaaS v2 14:04:09 Lets dive into L2 Support 14:04:14 chandanc_: pls go ahead 14:04:29 I could run some test on the OVS driver 14:05:03 I am able to populate the OVS tables with flow rules by converting the FWG rules 14:05:10 oh nice 14:05:14 +1 14:05:18 +1 14:05:21 +1 14:05:24 +1 14:05:39 create fwg works though the delete fwg will need work on the def FWG part 14:06:00 and what u have is a table allocated for fwaas ? 14:06:16 this means we can get to a OVS driver in standalone mode 14:06:31 the tables are in 40 and 50 series 14:06:38 ok 14:07:11 there was a suggestion from annp about keeping the tables same and trying out different flow priorities 14:07:18 we can handle coexistence as a next step 14:07:23 will look into that approach too 14:07:29 yes SridarK_ 14:07:54 chandanc_: +1 for your considering. 14:07:56 thats next step but have to fix somesmall issues 14:08:14 ok yes that is an interesting thought too - i dont know too much on ovs but a pros vs cons for taking this approach will be good to evaluate 14:08:26 hi 14:08:26 thanks annp , i will suggest we can start collaborating 14:08:44 sure 14:08:52 chandanc_, annp +1 good collaborating :) 14:08:53 chandanc_, sure. :) 14:08:54 a little more update 14:09:01 chandanc_: annp: u should run this by Jakub as well before we go too far down this path 14:09:14 to ensure that we are aligned with neutron direction 14:09:18 i found some changes were needed on the agent and plugin side 14:09:30 chandanc_: ok pls go ahead 14:09:51 i have updated the l2 ext patch for this 14:10:16 unfortunatly the plugin changes also git into the l2 ext patch 14:10:23 Sridark: Ok, I will evaluate it. 14:10:36 i will clean it up by tomorrow 14:10:59 chandanc_: no issues - we can discuss on gerrit as well 14:11:09 chandanc_, wow, thanks. Could you put some comments to l2 ext patch? 14:11:22 SridarK_, if you look at the l2 ext patch you will figure out the changes 14:11:28 chandanc_: ok 14:11:47 yushiro, my changes are mostly to fix the driver loading 14:12:09 please review it and let me know if it needs rework 14:13:16 SridarK_, i will add Jakub in the reviewer list 14:13:24 chandanc_: +1 14:13:53 that all from my side, please have a look at the patch and provide feedback 14:13:57 :) 14:13:59 chandanc_: anything else to add or discuss ? 14:14:03 chandanc_, aha, I see. thank you. 14:14:08 chandanc_: ok 14:14:15 thats mostly it 14:14:55 chandanc_: i think we can skip the FWaaS L2 driver as such due to some dependency on the ovs changes unless u have something to discuss 14:15:28 I think we can skip it 14:15:43 ok 14:16:10 On the L2 agent #link https://review.openstack.org/323971 14:16:27 chandanc_: u already mentioned that u had some updates 14:16:41 yushiro: other things u would like to discuss 14:17:33 SridarK_, yeah, now I try to test l2 ext + default fwg. 14:18:05 #link https://review.openstack.org/#/c/425769/ - default fwg 14:18:25 aha, thanks. This is link ^^^ 14:18:40 yushiro: i think u had a few minor things to take care off other wise the default fwg is mostly ready 14:19:11 ofcourse pending the dependency on L2 driver + ovs related changes 14:19:25 SridarK_, yeah. Last week meeting, we discussed a little about configuration file for default fwg. 14:19:50 yes, L2 driver + ovs is also pending. 14:20:06 yushiro: yes - unfortunately - i have been swamped the last week with other issues at work so did not get a chance to think more 14:20:20 on reedip's proposal 14:20:38 oh yeah ... I forgot :D 14:20:43 SridarK_, me too. I had to work another job ... 14:20:56 such is life :-) 14:21:10 reedip, wow!! hahaha 14:21:31 yushiro : Another JOB ??? !!! 14:21:33 reedip: could u start a discussion with the fwaas team on email 14:21:33 wow ! 14:22:03 SridarK_ sure, can you add it as an action to me ? ( I dont think # action will work for me) 14:22:26 reedip: or i can possibly do it too i might have an email chain with the entire team 14:22:31 reedip, I'd like to decide 2 things. 1: configurable default fwg with neutron.conf or not. 2: Can we modify default firewall group rule or not 14:22:34 u can then add the discussion 14:23:27 reedip, another job is from my manager... TBH, I'd like to work community more!!! :) 14:23:56 SridarK_ either way works for me. 14:24:17 yushiro: i think reedip was wondering if u found a way to get 2 paychecks ;-) 14:24:32 lol 14:24:39 yushiro : lets discuss it on the email, because I SridarK_ was swammped and I was JUST caught offgaurd ( I forgot my thoughts :P ) 14:24:58 reedip: i will send out an email 14:25:05 I put my thoughts on the review ;-) 14:25:08 and u can add more discussion 14:25:13 :-) 14:25:20 yushiro : dont worry , I am also in the same spot ... doing 2 jobs at the same time... thats why I dont have ny updates for today's meeting for Fullstack / neutron-lib ( jfyi ) 14:25:50 SridarK_, all , actually I have been assigned with Deployment at a customer .... 14:25:54 SridarK_, ahaha! OK, I understood. sorry for confusing ;-) 14:25:56 so m here 14:25:59 i think most of us are in that situation 14:26:12 making openstack WORK ! 14:26:13 :D 14:26:19 reedip: :-) 14:26:27 ok lets move on 14:26:53 reedip, SridarK_ Sure. I agree with your suggestion( discussing on ML) 14:27:33 yushiro: did u have a chance to look at the public vs shared #link https://review.openstack.org/#/c/424534/ 14:28:17 from Akihiro's suggestion - seems like we are more shared than public 14:28:27 As per amotoki we should have it as public :) 14:29:12 SridarK_, Sorry. I couldn't check it but we should convert from 'public' to 'shared'. 14:29:35 yushiro : wait 14:29:42 yushiro: no worries - we can pick it up next week or when u get some bandwidth 14:29:53 i think we have some clarity on that 14:30:19 lets move on 14:30:28 #topic Horizon 14:30:28 SridarK_, sure. 14:30:41 http://eavesdrop.openstack.org/meetings/fwaas/2017/fwaas.2017-03-21-14.00.log.html#l-151 14:30:45 honestly I could not remember where I mentioned it, though I remember I said so. 14:30:55 SridarK_, I have checked in my first patch today 14:30:56 amotoki : Link above :D 14:31:08 SarathMekala: pls go ahead - thx for getting this started 14:31:10 Horizon UI https://review.openstack.org/#/c/450567/ 14:31:32 as of now Rule add and get functionality are working 14:31:37 working on update and delete 14:31:41 SarathMekala: great 14:31:53 +1 14:31:58 SarathMekala: i think we need to address Rob's comments 14:32:03 I got a review comment by Rob Creswell saying we should follow LBAAS plugin model for Horizon 14:32:05 SarathMekala, good start. 14:32:19 +1 14:32:23 SridarK_, yeah.. I was looking into it 14:32:31 https://github.com/openstack/neutron-lbaas-dashboard 14:32:37 https://blueprints.launchpad.net/horizon/+spec/horizon-lbaas-v2-ui 14:32:51 there is a cookie cutter to create a horizon UI plugin project 14:32:57 Cookie cutter https://github.com/openstack/ui-cookiecutter 14:32:58 yep, I figured they liked the plugin and extra repo stuff ;-0 14:33:02 I suggest adding amotoki in the reviewer as well 14:33:10 for Horizon 14:33:16 Also amotoki mentioned to us in the PTG as well in terms of repo strategy - we may need to think in terms of a separate repo 14:33:42 SridarK_, yes.. in the plugin approach we will have a separate repo 14:34:00 yeah, LBaaS has separate repos for horizon, openstack client, and potentially tempest 14:34:05 and we will have to introduce devstack installation procedures e.t.c 14:34:14 xgerman : LBaaS is Everywhere :) 14:34:25 xgerman, yes 14:34:28 and it’s being renamed to octavia ;-) 14:34:31 SarathMekala: but it is good to start getting the code in place - u can cut over to another repo following existing precedents 14:34:51 xgerman : yeah I know it too well :D 14:35:05 SarathMekala: but great and thx for getting this started 14:35:15 SridarK_, should i continue in the current mode and cut out to the plugin mode later? 14:35:29 SarathMekala: i think it is best to make the switch now 14:35:39 SarathMekala : IMHO , could you change to plugin early on ? 14:35:50 than to change a whole lot of stuff later on? 14:36:10 SridarK_, reedip .. I can switch over to plugin mode.. but will have some learning curve for it 14:36:38 SarathMekala: no issues - look for some examples as in the lbaas case 14:36:56 SarathMekala : We can demo the current patch in Boston while the plugin is in progress 14:36:59 SridarK_, sure.. I am looking at lbaas implementation 14:37:03 how does it sound? 14:37:05 got some fair idea 14:37:30 reedip, sure.. I am targetting to get the UI up by boston summit 14:37:35 That's a great idea. 14:37:36 gr8 :) 14:37:36 xgerman: could u maybe link up SarathMekala to an lbaas contact 14:37:52 rm_work would be the best :) 14:38:03 all the people who worked on our dashbaord quit/moved on to other non-OpenStack projects 14:38:10 :-( 14:38:15 IBM… 14:38:31 SarathMekala: i will ping RobC as well to get some info 14:38:58 SridarK_, thanks.. any contact person for general queries will be great as well 14:39:11 I think Rob is a good guy 14:39:18 for that 14:39:35 And keep amotoki on the reviews - he has given the best feedback on all things UI 14:39:44 xgerman, thanks 14:39:46 +1 14:40:03 is the topic still horizon? 14:40:06 SridarK_, reedip .. I will add amotoki as well for the UI review 14:40:10 amotoki: yes 14:40:17 i would like to ask you one question 14:40:33 do you prefer neutron-fwaas-dashboard vs neutron-dashboard (for various stadium projects) 14:40:35 ? 14:41:02 I think we had this topic before but after that no dashboard is coming actually from neutron stadium 14:41:05 mmh, what does Neutron prefer? 14:41:37 amotoki: good point - we will need to be embed fwaas on neutron ports - so u think being a part of neutron dashboard makes more sense ? 14:41:38 neutron-dashboard means dashboard for all neutron stadium projects (except neutron) like fwaas, taas, sfc .... 14:42:14 amotoki, IMHO, neutron-dashboard is much more community concept 14:42:16 SridarK_: what does 'embed' mean? 14:42:23 amotoki: that seems to make more sense 14:42:40 amotoki: just saying that fwaas rules are installed on neutron ports 14:42:45 I am thinking to start a ML thread. you can respond it 14:42:57 This is my irc nick btw, if you need to discuss Horizon 14:43:05 amotoki, Today i tried to push a Horizon patch for VPNaaS. Also got the same comment from Rob to provide a plugin... 14:43:07 Just travelling, will be home in 15 mins 14:43:18 robcresswell, thanks.. I will get in touch with you 14:43:22 robcresswell: thx will ping u as well 14:43:32 Sorry, got disconnected 14:43:33 wow. Nice to meet you robcresswell and thanks for your review for SarathMekala's patch. 14:43:46 +1 14:44:05 amotoki: it seems with the neutron-dashboard - possibly with SFC and some integration with these projects will be a good idea 14:44:52 Sure, ping me any time. I'm always on IRC. Timezone is UTC, but I'm always online so I'll respond ASAP. 14:44:56 neutron-dashboard will be better to keep all projects in sync , I think 14:45:00 As long as I am not asleep. 14:45:11 :) 14:45:14 irc-to-brain interface 14:45:23 :-) 14:46:10 ok good i think we have a plan 14:46:12 :) thanks.. I will go through the lbaas plugin model and get back to you 14:46:12 lets move on 14:46:33 #topic Stadium Compliance 14:46:44 I think separate is better as we are currently control stadium repos by dedicade team. But it needs more discussion 14:46:50 reedip: shal we skip as u said u were swamped 14:47:09 SridarK_ : Please skip for now. I will send an update on the ML 14:47:15 hoangcx: noted lets discuss more 14:47:30 SridarK_ however, the neutron-lib patches need reviews 14:47:36 reedip: cool we will nag u next week 14:47:45 reedip: ok got it 14:47:50 wait I havent finished nagging you guys 14:48:08 reedip: :-) 14:48:20 shall we move on ? 14:48:37 Ok, just one patch probably for neutron-lib : https://review.openstack.org/445728 14:48:43 rest, please move on :) 14:49:48 ok 14:50:11 #topic Performance improvement (Netlink) 14:50:29 tuhv: annp: pls go ahead 14:50:44 hi, I'll continue works of tuhv 14:51:04 Cedric has left some comments since last weekends, I'm updating based on his reviews 14:51:32 cuongnv, good 14:51:34 cuongnv: ok great 14:51:44 your reviews are welcome, of course 14:52:25 cuongnv, tuhv, annp , hoangcx sorry for slow reviewing ;-( 14:52:46 yushiro, np 14:52:54 #link https://review.openstack.org/#/c/433598/ 14:53:09 #link https://review.openstack.org/#/c/437311/ 14:53:23 #link https://review.openstack.org/#/c/438445/ 14:53:38 I have been distracted as well… 14:53:42 cuongnv: these are the reviews correct ? 14:53:56 We All Need A Break ! 14:54:11 SridarK_, yep 14:54:23 reedip: it is more a context switch rather than a break :-) 14:54:26 SridarK_, https://review.openstack.org/#/q/topic:bug/1664294+status:open this works as well 14:54:45 cuongnv: got it 14:55:22 ok lets move on 14:55:36 #topic Open Discussion 14:55:57 reedip asked about our deprecation plan 14:56:04 aah.. yeah ! 14:56:09 xgerman: yes 14:56:12 today morning in the fwaas channel 14:56:31 How abt we align that with the summit 14:56:32 thanx xgerman , I seem to forget things toay 14:56:45 happy to help ;-) 14:56:48 hopefully we will be in good shape with L2 14:56:49 oh , so we would go ... SURPRISE, V1 is being deprecated ! ?? 14:57:02 it’s been deprecated for two years 14:57:08 hehehehe 14:57:25 then SURPRISE .. v1 is deprecated for 2 years but now we are moving On ! ? 14:57:28 with that we can announce the actual, yes really, this time for sure deprecation 14:57:42 yep 14:57:56 though I think Pike 1 is a better option 14:57:59 over next 2 weeks lets put together a plan for the summit presentation 14:58:05 so we also made sure that in theory you could run V1 and V2 side-by-side 14:58:21 so people could keep V1 and ease into V2 14:58:21 but still maintaining / fixing bug for v1,,, right? 14:58:47 well, we need to set an end-of-life date 14:58:55 No new features for V1. 14:59:07 only bug fixes yushiro 14:59:09 possibly Q release ? 14:59:14 usually after deprecation you hAve two cycles… but with use being deprecated for two years we should set a date 14:59:16 till End Of Life as mentioned by xgerman 14:59:18 2 minutes left ... 14:59:27 SridarK_ Lets have a vote on ML 14:59:36 1: Pike-1 with deprecation in R-1 14:59:47 ok lets add this as a topic for next mtg 14:59:47 2: Boston Summit with Deprecation in VanCouver Summit 15:00:03 k 15:00:04 ok we are close to time 15:00:04 sorry EOL in R1 /Vancouver 15:00:16 reedip: lets add this to our discussion in mail 15:00:22 #endmeeting