14:00:44 #startmeeting fwaas 14:00:45 Meeting started Tue Aug 22 14:00:44 2017 UTC and is due to finish in 60 minutes. The chair is yushiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:48 The meeting name has been set to 'fwaas' 14:01:06 #chair SridarK yushiro xgerman_ 14:01:07 Current chairs: SridarK xgerman_ yushiro 14:01:52 yushiro: ur turn to run the mtg ? 14:02:13 sorry i forget 14:02:24 SridarK, ah, me too :) 14:02:41 i think xgerman_ ran it last time 14:02:45 yes 14:02:54 yushiro: so u are the chair 14:03:06 OK, I will :) 14:03:11 pls go ahead :-) 14:03:14 so, let's start 14:04:10 #topic Pike 14:04:46 L2-agent 14:05:20 #link https://review.openstack.org/#/c/323971/ 14:05:30 isn't FFE period over? 14:06:00 amotoki, I think yes. 14:06:18 So, 14:07:11 Just an announce. I fixed l2-agent bug which relates existing l3 behavior. 14:07:23 hi 14:07:54 As you know, this week is dashboard release term. 14:08:27 So, let's move next topic if there is no comment on l2. 14:08:30 sorry I was late , got stuck in the gym , and then traffic 14:08:32 yushiro: nice - i just see the email from u 14:08:57 reedip_, NP 14:09:07 #topic Horizon support 14:09:10 yushiro: if l2-agent stuffs is really a bug, it can be considered for backport, but it should be without any feature 14:10:10 amotoki, OK 14:10:22 SarathMekala, Hi 14:10:36 hi.. let me give some updates on Horizon 14:11:02 thanks yushiro and amotoki for your suggestions 14:11:39 SarathMekala, NP :) 14:11:43 I am following up on the #link https://etherpad.openstack.org/p/fwaas-v2-dashboard created by yushiro 14:11:55 #link https://etherpad.openstack.org/p/fwaas-v2-dashboard FWaaS dashboard reviews and feedbacks 14:12:15 so there seems to be an issue when the ingress/egress policies are not specified 14:12:28 yushiro: will that fix the duplicate problems as u mentioned on the fwaas channel (sorry i went to bed) 14:12:34 and it effects all the crud operations.. i will fix it 14:13:04 SarathMekala: yes i seem to have issues on CR on FWG and Policy 14:13:07 Rules were ok 14:13:26 CR = code review? 14:13:26 SridarK, Yes. Previous code used 'public' instead of 'shared' for getting. 14:13:28 If u spin another PS - i can do more testing 14:13:36 ok.. did you find any issues with creating policies? 14:13:42 amotoki: sorry CR - CReate 14:13:46 they should have gone smoothly as well 14:13:59 too many abbrevs :( 14:14:04 SarathMekala: no i was not able to create a policy 14:14:11 amotoki: Sorrry :-) 14:14:17 hehe 14:14:22 ok.. 14:14:46 I recently changed 'shared' to 'public' :( 14:14:52 SarathMekala: ok perfect 14:15:03 will revert it back 14:15:12 SarathMekala: ok thx 14:15:35 SarathMekala, yes, I commented it in your patch. 14:15:53 SarathMekala: also on FWG, can we update to add in the ingress / egress policy 14:16:11 i could update to add in ports but i seem to miss policy 14:16:35 my workflow: I created a policy on OSC (no ports or policy) 14:16:43 hmm.. the update operation should allow to select the policy using a drop down 14:16:45 i was now able to see that on the dashboard 14:17:01 then i was looking to update to add the policy 14:17:02 i have tested that flow 14:17:17 SarathMekala: ok my bad then - i may have missed something - let me recheck that 14:17:24 SridarK, it may be 'public'/'shared' issue ... 14:17:27 ** too much data to process ** 14:17:35 perhaps everyone has different expected workflows, so we hit several issues. 14:17:35 yushiro: ok 14:17:35 SridarK, np .. I will also recheck 14:17:48 may have got broken during the last patches 14:17:53 amotoki: could be also 14:17:58 I tried to deploy the horizon plugin but failed :( Will recheck 14:18:08 I think it's better to respin new patch set for testing 14:18:11 SarathMekala: ok once u revert to shared 14:18:13 i will check 14:18:17 yushiro: +1 14:18:31 SridarK, sure 14:18:38 i have some questions 14:18:48 how can we move the thing forward fast? 14:18:50 amotoki, yes.. 14:19:02 yushiro: also i am not pulling in the L2 Agent / driver patches in my testing 14:19:19 since they are not part of the release 14:19:31 we (including yushiro, me or others) might be able to propose a fix, but we are afraid the duplicated work 14:19:56 SridarK, OK. for testing with dashboard, it is not necessary. 14:20:02 amotoki, +1 14:20:03 amotoki, its fine.. you can put in your fixes 14:20:11 i heard yushiro has some fixes for the current dashboard, but we don't know SarathMekala's status 14:20:16 and did not push it 14:20:46 if we are not aware of each other, we can easily override another fix :( 14:20:47 SarathMekala: i think both yushiro and amotoki have pointed to that in gerrit as well 14:21:03 SridarK, yes 14:21:13 amotoki, I am in a terrible fix right now... have a customer demo tomorrow and am running on a tight rope.. 14:21:26 am actually planning to push in the patches by eod tomorrow 14:21:47 so, we need to discuss we should defer it to Queens or not 14:22:07 mmh 14:22:24 can we take the call on 24th :) 14:22:29 do we want production bugs ? 14:22:38 SarathMekala: any chance u will be able to address the last set of review comments 14:22:47 then i can do some testing today 14:22:49 nobody will use Pike in prod — people never update right away 14:22:51 SarathMekala: ur call 14:23:03 SridarK, I will address some issues today 14:23:05 SarathMekala: dont mean to put pressure on u 14:23:11 and the remaining tomorrow.. 14:23:21 let me share my thoughts on the release schedule 14:23:22 xgerman_ oh yeah, right :) 14:23:37 its just us developers :P 14:23:43 yes 14:23:46 SarathMekala: ok sounds good - i will pick up that PS 14:24:01 customers are getting to Newton right now 14:24:18 xgerman_: tend to agree 14:24:26 That reminds me we need to pick up the migration of V1 to V2 as well soon 14:24:36 amotoki and yushiro wait for today and you can put in your patches on top of mine tomorrow 14:24:36 atleast in the start of queens 14:24:39 +1 14:24:39 reedip_: yes 14:24:54 I think we need at least three rounds of reviews to land it and we don't have enough to do so 14:25:17 Thursday is the release day, so we should not count it as days we have. 14:25:23 it means Wed is the last day for larger changes 14:25:51 "three rounds' means: the next patch set addresses the current issues raised. 14:26:08 the second patch set will addressed new issues raised based on the next patch set. 14:26:19 the third one is for clean up 14:26:36 and the fourth one MUST be a release deliverable. 14:26:44 this is the current situation. 14:27:01 amotoki: +1 yes it is very tight 14:27:11 can we propose "the third patch set" in Wed? 14:28:25 amotoki, do you see any critical issues 14:28:40 other than the ones mentioned 14:28:40 SarathMekala: it depends on fwaas team 14:29:12 Note that on Thursday we need to land a patch in the releases repo. it means we propose a patch, ack by the neutron-release team, and approved by the release team. 14:29:17 SarathMekala, amotoki think that we can find any bugs after updated new patchset. 14:29:30 SarathMekala: IMHO - i think right now with PS 17 it has critical issues, but i think based on the review comments - it will be much better 14:29:43 we are standing by — so if it’s us it would work 14:29:58 SarathMekala: but more testing can reveal other issues 14:30:05 yes 14:30:31 I see there are two options: to have it in Pike, or to land it early Queens 14:30:33 How abt we give things a try with PS 18 and then decide if it is even realistic 14:30:47 SridarK: +1 14:30:54 SridarK, +1 14:30:56 hmm, yes, agree! 14:31:33 I can follow to update PS18 -> 19 14:31:55 also 19 -> 20 :) 14:32:02 :-) 14:32:04 yushiro, :) 14:32:16 yeah.. lets give it our best shot 14:32:23 +1 14:32:26 +1 14:32:42 I will prepare a release patch based on the current commit and share the review link with you all. Someone from the fwaas team can take care of it then. 14:33:10 I will 14:33:10 I cannot have enough time on Thursday and Friday morning in my TZ 14:33:15 I am sure there will be bugs but if the basic workflows work - it is acceptable for someone to start playing with it 14:34:23 regarding Pike dashboard release, I would like to have https://review.openstack.org/#/c/495487/ 14:34:50 patch set 15 is the one I have done quite a bit of testing 14:35:12 amotoki done — 14:35:15 xgerman_: thanks 14:35:23 you can pickit up and see if things are better (it has 'shared' attribute) .. I made significant changes in patchset 16 14:35:49 if amotoki 's patch is merged, we don't need to execute 'cp' command, right? 14:36:08 yushiro: what do you mean by 'cp'? 14:36:18 yushiro: do you talk about the manual step? 14:36:25 amotoki, oops, sorry. cp is 'copy' command. 14:36:31 yes, manual step 14:36:55 yushiro: they are different things 14:37:20 amotoki, ah, OK. I was just misunderstanding. 14:38:26 yushiro: no problem 14:39:54 OK, so it is just reminder for next patchset(18) from me. 14:40:10 yushiro: ok perfect 14:40:27 i will do more testing with PS 18 today 14:40:32 yushiro, yes 14:40:44 I will push in the patch tonight 14:40:48 yushiro: / SarathMekala: we can discuss during ur day time 14:40:49 SarathMekala, now 'Create firewall group' and 'Add policy'(create firewall policy) button doesn't work (not displayed) 14:41:32 SridarK, sure.. I will be on hexchat.. you can reach me when you want 14:41:39 SarathMekala, I hope to fix both buttons in PS18 14:42:04 yushiro, I will do some thorough testing and push in PS18 14:42:11 ok 14:42:18 After that, we can start testing 'create' part. 14:42:29 all basic functionality should work excepting some corner case scenarios and any missed out validations 14:42:53 yushiro: SarathMekala: will we fix the duplicate issue as well with this ? 14:43:27 I will fix it as well SridarK 14:43:31 perhaps, we can update patch sets more 14:43:33 ok 14:43:42 with small changes 14:43:45 I will try to take out as many issues as possible.. yushiro and amotoki and pick up from there 14:44:26 a couple of small changes sounds better than a big single change :) 14:44:33 SridarK, duplicate issue is here: https://review.openstack.org/#/c/475840/17/neutron_fwaas_dashboard/api/fwaas_v2.py (commented) 14:44:33 +1 14:44:34 +1 14:44:40 +1 14:44:49 SarathMekala: btw, do you see any difficulties in passing unit tests? 14:45:30 we've never seen ut passed so far :( 14:45:38 amotoki, I could not run them locally as my setup had some issues... 14:45:47 yushiro: ok 14:46:02 woops.... really bad news. 14:46:54 SarathMekala: so, do you mean you need more help to make unit tests healthy? 14:47:43 amotoki, I referred to the existing V1 cases to create these.. so except for some import issue which i am seeing 14:47:52 there should not be much issue.. 14:48:22 yushiro, amotoki it will be great if you can try to run them on your local setup and share me the feedback 14:49:00 can anyone help it? 14:49:03 yushiro? 14:49:05 SarathMekala, Of course I can. 14:49:29 SarathMekala: let me also pull in the PS and check UT 14:49:34 i could help it last week but i have no enough time this week 14:49:44 sure SridarK .. if possible try out PS 15 14:49:52 SarathMekala: ok 14:49:55 it should be more solid 14:50:10 But for manual tests i will wait on PS 18 14:50:23 SridarK, sure 14:50:48 So just to be sure that there is no confusion: 14:50:51 let's wait PS18 first and then test and fix various things 14:50:59 SarathMekala, I'll give you UT feedback after PS18. 14:51:12 yushiro, sure 14:51:18 SarathMekala: u will push in PS18 with the Create issue and Duplicate fixed ? 14:51:34 SridarK, yes.. I think I will have to do a night out today :) 14:51:44 SarathMekala: :-( 14:52:09 SarathMekala: sounds not a good idea :/ 14:52:26 it might be good to share the status in the etherpad if some of you are working on some 14:52:41 +1 14:52:46 something like 'hey, I am working on UT based on PS18' 14:52:54 yes +1 14:53:11 last thing we need now is for folks stepping on each othersPS 14:53:43 oops!! so fast today's time 14:53:48 yes 14:53:51 time flies 14:53:51 amotoki, sure.. wait for my PS 18 and you guys can jump in 14:54:10 SarathMekala, sure. Thank you. 14:54:19 Let us quick hit: https://specs.openstack.org/openstack/neutron-specs/specs/stadium/ocata/neutron-fwaas.html#c7 14:54:46 I asked kevinbenton how to update but he didn’t get back — anyone has an idea? 14:54:47 SarathMekala: thanks 14:54:50 +1 14:55:12 also is there a Pike verison? 14:55:52 you can propose an updated pike version to neutorn-spec repo 14:56:11 I created one for Tap-as-a-Service, I can work on it for Pike 14:56:11 unelss kevinbenton is preparing it 14:56:25 I updated the pending items on the fwaas channels yesterday 14:56:50 reedip_: i think fullstack is WIP else we are ok 14:56:59 sounds good 14:57:04 +1 14:57:05 No, some are still pending, but not much 14:57:29 I will check the fwaas channel , I forgot what I wrote there :) 14:57:35 reedip_: ok could u paste that into the fwaas meeting etherpad whenever u have some time 14:57:42 wonder if we archive? 14:57:53 sure. 14:57:58 it'S better. 14:58:03 xgerman_: yes we do 14:58:15 :-) 14:58:30 I will share it still :) 14:58:33 :-) 14:58:38 SridarK, xgerman_ here is a bug which relates fw_group and fw_policy relation https://review.openstack.org/#/c/453786/ I noticed this fix is necessary while testing dashboard. 14:58:39 Hi guys, hopefully you have time to check 14:58:40 shall I take the Stadium patch ? 14:58:40 https://review.openstack.org/#/c/443385 14:58:40 Thanks to the help from Motoki, the Release Note has been added. 14:58:40 If there's not any other update required, I hope that this patch can be merged soon. 14:59:00 TuanVu_, Thanks for your fix. 14:59:06 TuanVu_ everything seems ok in your patch :) 14:59:36 1 minutes left! 14:59:44 Thank you, yushiro and reedip_ :) 15:00:01 TuanVu_: np 15:00:02 ok, I am taking the stadium report patch SridarK :) 15:00:19 OK, it's time. 15:00:22 #endmeeting