14:01:03 #startmeeting fwaas 14:01:04 Meeting started Tue Aug 29 14:01:03 2017 UTC and is due to finish in 60 minutes. The chair is yushiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:07 The meeting name has been set to 'fwaas' 14:01:07 o/ 14:01:21 #chair SridarK yushiro xgerman_ 14:01:22 Current chairs: SridarK xgerman_ yushiro 14:01:24 Hi All 14:01:40 SridarK, Hi. Today is ur turn :) 14:01:48 yushiro: yes thx 14:01:54 hi all O/ 14:01:57 shall we get started 14:02:00 Hello All 14:02:13 #topic Pike 14:02:32 Pike is released 14:02:37 yes 14:02:44 we should change the toic to Queens ;-) 14:03:00 i just wanted to say that we came very close to wrapping up L2 and Horizon 14:03:02 aha 14:03:17 SridarK =+ 14:03:27 and we have good momentum but unfortunately we just missed the boat 14:03:31 :-) 14:03:39 or rather :-( 14:03:52 #topic Queens 14:04:24 target for Queens - is to wrap up L2 support and Horizon among other things 14:04:45 other things --> we will prioritize that list in PTG 14:05:14 Guys sorry, I am driving so will be checking the messages for now (Reedip) 14:05:34 SridarK, yes 14:05:44 Also let us know the possibility of a virtual PTG for those who won't join in(??) 14:05:56 we have captured some thoughts in the etherpad 14:06:12 HoloIRCUser5: (reedip) most definitely lets plan for that 14:06:45 if nothing else we can move to features 14:06:56 that we know about 14:07:09 #topic L2 Support 14:07:31 yushiro: pls go ahead starting with agent changes 14:07:44 SridarK, sure. 14:08:06 #link https://review.openstack.org/#/c/323971/ 14:08:50 Now, I'm fixing UT. On the other hand, I need to decide a constraint to become 'ACTIVE' for firewall group. 14:10:41 yushiro: yes this is a bit more tricky 14:10:48 Currently, in L2, fw_group becomes 'ACTIVE' when it has 'ports' and firewall_policy(ingress or egress) and rules. 14:10:53 Please refer https://review.openstack.org/#/c/323971/49/neutron_fwaas/services/firewall/agents/l2/fwaas_v2.py@165 14:11:25 However, in L3, it becomes 'ACTIVE' when firewall group has 'ports'. 14:12:11 I think 'ACTIVE' means some rules are applied and firewall_group is working. 14:12:41 yep 14:12:41 yushiro: would a simplistic model - like if there is atleast 1 VM port associated it is ACTIVE 14:12:44 Active should mean that the firewall is working, so I guess this can just be something mentioned in the release notes 14:12:59 And it would be an expected behavior 14:13:07 but if there is no VM port - it is INACTIVE 14:13:14 this is consistent with L3 14:13:23 but not make that much sense with L2 14:13:25 yes — that makes sense 14:13:36 SridarK, +1 Yeah, it should be aligned with same constraint b/w L2 and L3. 14:13:43 we could start with this 14:13:48 especially when we think about 3rd party which might have to apply stuff which takes time 14:14:02 xgerman_, SridarK HoloIRCUser5 OK, I'll change the constraint to become 'ACTIVE'. 14:14:02 yes 14:14:19 but i think this will need some revisit 14:14:48 SridarK, +1 yeah, but I agree with your opinion. 14:15:28 That's all for me. chandanc, anythink else for https://review.openstack.org/#/c/447251 ? 14:15:44 nothing as of now 14:16:02 With multiple ports - we may need to revise some thoughts on that - this has been on mind for sometime - will put down some notes and we can discuss during PTG as well 14:16:23 chandanc, I got some comment from neutron guy about ovs firewall driver in neutron has been fixed some bugs. 14:16:43 oh, what bugs are fixed 14:16:47 chandanc, We need to consider how to maintain. 14:17:17 chandanc, Sorry I didn't hear in detail. Let me check more with neutron guy. 14:17:25 ok sure 14:18:19 HoloIRCUser5, BTW, did you execute my latest l2 patch? Was it succeeded in deploying devstack? 14:18:51 No, not yet, will check it tomorrow morning once 14:18:56 OK. 14:19:06 SridarK, That's all. Please going on :) 14:19:55 chandanc: from the driver perspective - are there any things that u need to wrap up ? 14:20:40 chandanc: I think u had some UTs to add 14:20:47 SridarK: i have not done any more tests, but curretly all the points raised in the review are already in 14:21:26 I can check the OVS driver on neutron 14:21:51 chandanc: ok good - we do kick off some integration tests once we things in place 14:21:59 sure SridarK 14:22:33 reedip1: now the roads are safer :-) 14:22:52 No, I am waiting for my missus at the dance centre :p 14:22:56 unless you have a self driving car? 14:23:00 chandanc, I'll help about it and let's decide for maintenance 14:23:17 sure yushiro 14:23:37 reedip1: ah welcome to the next stage in life - which involves a lots of waiting ... ;-) 14:24:04 sorry for the diversion :-) 14:24:15 np :) 14:24:25 reedip1: good u have the devstack things in line too ? 14:24:31 That's why I am here on the IRC 14:24:37 :-) 14:24:40 :-) 14:25:07 I am still fixed upon the full stack for now . Can't seem to get around it 14:25:23 reedip1: ok 14:27:06 I had some notes somewhere on a basic testplan - i will put that into an etherpad - we can refine that as a team and ensure that we test and document 14:27:30 #action SridarK to kick off an intial test plan for L2 support 14:27:47 Ok sure... Let s also include the migration for v1 to v2 14:28:04 It can serve as the items for queens 14:28:15 and during the PTG we can clarify where neutron is with ovs transition - if there are some things we need to address 14:28:28 reedip1: yes great point - lets get that in as well 14:28:53 ok if nothing more lets move to next topic 14:29:04 #topic Horizon 14:29:13 +1 but I thinke we should get V2 working before we worry about migration… 14:29:26 xgerman_: +1 14:29:28 xgerman yep 14:29:38 SarathMekala: pls go ahead 14:29:56 i think we are really close with some great help from amotoki 14:30:00 I would like to thank all for pitching in during the last round 14:30:06 +100 14:30:19 ++ 14:30:21 yes indeed 14:30:38 No problem :) 14:30:42 :) 14:30:48 I am not sure what are the remaiing blocking issues 14:30:52 we are really close except for some minor things that need to be addressed 14:31:00 (except UT failures) 14:31:21 there are some review comments from 17-25 patches that need to be looked into and addressed 14:31:34 and fix UT 14:31:56 amotoki, I think we cannot create firewall policy with rules ( specified rule is not reflected ) 14:31:57 how about the issues reported in the etherpad? 14:31:59 yushiro, seems to have added a comment on rules not getting fetched 14:32:17 SarathMekala, yes, I added a comment to https://etherpad.openstack.org/p/fwaas-v2-dashboard 14:32:28 IIRC most or all comments from 17-25 patches have been addressed 14:32:39 amotoki, yes.. I will clean it up and make it more trackable 14:32:58 Please refer #fwp-6 14:33:45 yushiro, sure 14:33:50 i had some minor issues on PS25 - i will check if there were fixed 14:34:14 I have them on the etherpad - but all major issues were fixed 14:34:31 SarathMekala, any critical issue ? 14:34:46 except creating firewall policy with rule 14:34:50 as of now I dont think so 14:34:56 I think we can test and report the dashboard patch. One question is how we can move things forward. 14:35:20 yes 14:35:28 SarathMekala: you continue to say 'ignore UT failures'. do you have any blocking thing to address UT failures 14:35:31 SarathMekala: pls look at the etherpad on top for PS25 - to be sure 14:36:10 amotoki, I will fix the UT now.. 14:36:18 I think it is time to make UT passed for all patch sets. 14:36:25 *every patch set 14:36:58 yushiro, do you have any progress on the UT or should I take over? 14:37:07 +1 we can then do more manual tests also 14:37:43 right.. I will concentrate of fixing the UTs by Friday 14:37:55 amotoki, +1. SarathMekala I'm fixing UT too. OK, I'll send you my patch file (draft) 14:38:00 I will be travelling this weekend and will be back on Tuesday 14:38:23 yushiro, sure.. 14:38:29 SarathMekala, OK, so could you send me your patch file? 14:38:49 you mean on Friday? 14:39:05 SarathMekala, Yes. I think you should enjoy your weekend travel :) 14:39:17 :) 14:39:38 sure yushiro, I will try to fix them as much as possible.. you can pickup from there 14:40:16 sounds good - i think we will be in good shape by Fri 14:40:33 SarathMekala, OK. If I can fix UT as soon as possible, I'll update PS and tell you. 14:40:40 sure yushiro 14:40:42 we can follow up with more manual tests and we have a chance to merge next week 14:41:15 SridarK, yes.. I will clean up the etherpad so that we can have a better visibility on the status 14:41:23 many thx SarathMekala and to amotoki and yushiro for jumping in 14:41:33 NP :) 14:41:40 you're welcome 14:41:41 I have one more question 14:41:47 So, I'll update test case for manual in https://etherpad.openstack.org/p/fwaas-v2-dashboard 14:42:03 amotoki, how do we test installing dashboard via devstack 14:42:24 currently I am installing it the "pip install -e ." way 14:43:03 SarathMekala: do you mention the instructions described at the bottom of https://etherpad.openstack.org/p/fwaas-v2-dashboard by 'pip install -e .' way ? 14:43:19 yes 14:43:34 I am checking out fwaas-dashboard and installing it onto my devstack 14:43:52 for devstack plugin instruction, i update the devstack doc in your review 14:44:00 see devstack/README.rst 14:44:12 didn't you check it? 14:44:21 ok.. I did not try it 14:45:05 has anyone tested this method? 14:45:16 It mostly does the same thing as 'pip install -e .' way does. 14:45:39 SarathMekala, not yet but will install after finished this meeting. 14:46:01 ok 14:46:22 To summarize: 14:46:28 #action clean up etherpad 14:46:36 #action fix UT 14:46:46 #action fix rules issue 14:47:02 #action address etherpad issues 14:47:04 :) 14:47:18 sounds a good list :) 14:47:20 then call for testing again :) 14:47:29 :) 14:47:32 :) 14:48:16 SridarK, thats it from my side 14:48:16 we are now in queens, so we can merge it once we agree it covers the basic scenarios 14:48:24 and fix other issues in follow-up patches 14:48:34 amotoki, +1 14:48:37 amotoki, +++++++1 14:48:45 Sounds good - i think lets target to be done by next week 14:48:52 let's merge ASAP :) 14:49:24 SridarK, right 14:49:31 Ok i think we have a plan in place - lets move on 14:49:40 #topic Open Discussion 14:50:02 doude: i saw u join - things u would like to bring up ? 14:50:15 Hi all 14:50:34 O 14:50:35 I had not time to make progress during last weeks on my patch 14:50:48 but I plan to work on it next week 14:50:59 The pluggable back end righ5 14:51:08 doude: no worries - i think we can have more traction for Queens 14:51:10 yes 14:51:15 doude, OK. 14:51:22 Too much conflicts 14:51:22 I'll start on a big rebase work :) 14:51:27 yes 14:51:28 doude: will u be at the PTG ? 14:51:36 no 14:51:39 ok 14:51:42 I tried to fix it but too much changes :p 14:51:48 probably at the summit not yet decided 14:51:54 ok 14:52:48 reedip1: I'll try to do that 14:52:50 thx 14:52:57 Ok 14:53:13 I've got a question, probably you already discussed it 14:53:14 I can also pick it up if u want help 14:53:29 what's the deprecation plan for the v1 API? 14:53:33 reedip1: on the virtual PTG - shall we plan to meet virtually sometime mid next week to set priorities before the PTG 14:53:39 ok reedip1 14:54:01 doude: i think we are on way and possibly by R 14:54:34 what do others feel abt meeting virtually before 14:54:40 ok so for the moment keep it as is 14:55:03 yes 14:55:14 I am not sure how good any audio feed during the actual PTG will be to be effective 14:55:23 and the timing may be odd too 14:55:50 ( 5 minutes left ) 14:55:59 yes — maybe we should just do some pre-PTG and then push that at the real one 14:56:33 xgerman_: yes exactly at least we have feedback from the entire team on what things they view as important 14:57:37 +! 14:58:24 also Sydney is a pretty slim agenda… 14:58:48 xgerman_: yes 14:59:00 xgerman_, yes, short term. 14:59:20 I have some budget to cover the flight and meals… so I am on the fence right now… 14:59:38 ok maybe i will ask in an email if folks want to conect before PTG next week. Or we can discuss in next weeks mtg also. 15:00:05 e-mail might be best… PTG is in two weeks 15:00:05 ok i think time to wrap up 15:00:10 thanks all for joining 15:00:17 #endmeeting fwaas