04:00:02 #startmeeting fwaas 04:00:03 Meeting started Wed Nov 2 04:00:02 2016 UTC and is due to finish in 60 minutes. The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:06 The meeting name has been set to 'fwaas' 04:00:18 #chair SridarK xgerman yushiro 04:00:19 Warning: Nick not in channel: yushiro 04:00:20 Current chairs: SridarK njohnston xgerman yushiro 04:00:21 Hi All 04:00:23 Hello all O/ 04:00:41 shall we get started 04:00:54 by all means 04:01:01 #topic Summit briefing 04:01:07 hi 04:01:10 Hello 04:01:55 Was a good summit and nice to meet all the folks who made it in - we had productive discussions. Really missed the folks who could not be there 04:02:15 I was very pleased to meet everyone who was able to attend the summit! I very much hope to meet everyone who could not attend at the PTG in Atlanta. 04:02:22 +1 04:02:25 +1 04:02:30 really good summit :) 04:02:54 There was a summit session on the neutron stadium situation, but it turns out that was really just to make sure that everyone understood the requirements - no new news. 04:03:15 perhaps we can see where we can get max attendance PTG or Boston and can make some plans accordingly too 04:03:48 njohnston: +1 it was indeed very reasonable on the requirements and we have a good chance of making it 04:04:51 Was there anything else earthshaking from the summit? I can't think of anything. 04:05:36 The talk mfranc213 and I and davidsha gave seemed to be very well recieved. If you want to learn how neutron agent extensions work and how to write one I recommend the video. 04:05:37 we had a good discussion amongst the team - njohnston, mfranc213, vichoward, hoangcx and myself - thanks to yushiro 04:06:04 You're welcome. 04:06:05 +1 thanks again to Yushiro and Fujitsu for generously making your meeting room available for us! 04:06:05 we also had other folks from fujitsu - many thanks to yushiro for hosting us 04:06:56 njohnston: +1 on the L3 agent ext talk - was really fantastic and is indeed a very valuable contribution to neutron for services 04:07:00 njohnston, do you have the video link ? 04:07:16 chandanc_: http://www.openstack.org/videos/video/under-the-trenchcoat-neutron-agent-extensions 04:07:25 thanks :) 04:07:32 you're welcome :) 04:08:16 chandanc_: & SarathMekala: Had a discussion with Kevin Benton and described the patch and intent and he was fine with that 04:08:30 and said he would start looking into it and get back to u 04:08:47 Great news SridarK 04:08:55 great :) 04:09:01 i communicated ur intent that u wanted to make sure general direction is good and wanted opinions 04:09:10 cool, now we can fixup all the UTs and move forward 04:09:14 and ignore Jenkins failure 04:09:29 chandanc_: yes do wait for his inputs 04:09:36 ok sure 04:09:42 but u can keep churning the patch 04:09:50 yes 04:09:58 +1 churn! 04:10:40 We also met with korzen at the developer meetup; he is looking for opportunities to contribute as well. He appears to have a deep knowledge base. 04:11:20 njohnston: +1 really looking fwd to have more involvement from korzen 04:11:39 chandanc_: & SarathMekala: i met some folks from contrail who were interested in FWaaS and i mentioned ur contributions - i will connect u guys 04:12:02 Sure SridarK 04:12:08 sure 04:13:40 Also as i was leaving, got to know that there is interest from the ODL community as well - they want some support for precommit notifications - Isaku will propose some changes and discuss with us 04:14:01 that is interesting 04:14:07 yes, quite 04:14:12 Thats pretty much what i had 04:14:36 overall it was good and productive 04:15:11 Also as i was leaving yushiro introduced me to Takashi Yamamoto who said will help with tempest reviews 04:15:37 he suggested to follow the neutron model as opposed to what he had done for FWaaS which could be a bit dated 04:16:14 I am trying to connect with someone internally who may also have some background on tempest - i will update on what i find out 04:16:47 ok i think now i am done :-) 04:17:12 njohnston: , yushiro: other things to add ? 04:17:26 yes, but not about the summit :-) 04:17:38 well,, it's all for me :) 04:17:48 thanks, SridarK 04:17:53 ok lets move on then 04:18:04 #topic stadium requirements 04:18:10 njohnston: pls go ahead 04:19:04 On the topic of stadium requirements, I have started some developer documentation. Please kindly take a look at this link and suggest what you think needs to be added: http://docs-draft.openstack.org/77/391477/1/check/gate-neutron-fwaas-docs-ubuntu-xenial/205c721//doc/build/html/ 04:19:39 The main thing that I would like to ad at some point is a document explaining how to write a fwaas driver, for in-tree or out-of-tree drivers. 04:19:50 but I don't want to hold things up for that 04:20:34 mfranc213's api-ref change seems to be well received https://review.openstack.org/#/c/391338/ 04:21:30 The neutron-lib contribution front seems to be going well; I hope to slip at least one contribution in, probably this: https://review.openstack.org/#/c/389825/ 04:21:43 njohnston: i can contribute on the writing of fwaas driver (esp out of tree - as i have done that before) 04:22:08 Excellent! But don't let me distract you from tempest! 04:22:14 I too have done work on out of tree driver 04:22:20 njohnston: no only after tempest 04:23:14 SridarK has the two tempest patches in WIP still, but I am optimistic we can close on them soon, especially with the resources you are bringing to bear 04:24:04 the grenade job is merged, and is 100% successful when checking experimentally, so I am going to put out a change to move it to gate queue non-voting 04:24:23 chandanc_ and I are getting together to look at the multinode job and clear the comments on that 04:24:49 yushiro: How goes the OSC patch and it's dependency, the OSC lib utils? 04:25:11 yes, we can have a discussion on the CI patch maybe after this meeting and close on the comments 04:25:47 njohnston: I'll try to import to osc-lib. But currently, Akihiro hasn't updated yet. 04:25:48 njohnston: yes, i have one (API) and SarathMekala: has the scenario 04:26:30 I just rebased yesterday and try to move it into osc-lib today after discussing with Akihiro. 04:26:42 SridarK, njohnston I am working on the scenario tests.. will do a checkin soon 04:26:45 excellent, everyone, excellent 04:27:29 I believe that if the deadline for stadium compliance fell right now, we would pass. We don't have all the elements, but for all the required ones we can show strong and steady progress. 04:27:39 Which is the criteria we need to meet. 04:28:15 Anything else on the stadium? 04:29:05 ok, moving along. 04:29:11 #topic FWaaS v2 04:29:19 I expect this to be a very short topic because of the summit 04:29:26 +1 04:29:30 +1 04:29:33 We already mentioned the work on OSC, as well as the discussions with kevinbenton 04:29:53 But I wanted to check and see if anyone had any progress on anything else. 04:30:21 And we agreed on the L2 model being default fwg for tenant wide 04:30:32 Ah yes, thank you 04:30:36 once that is set, any VM coming up will get that 04:30:46 great 04:31:10 but then this is not for stadium requirements just to be clear 04:31:11 Super +1 04:31:24 so we can focus on it once we are solid on the stadium req 04:31:36 +1 04:32:18 I think that is it. Moving on then... 04:32:22 #topic meeting time 04:32:51 I sent an email to openstack-dev about this but I don't think I got any responses 04:32:53 #link http://lists.openstack.org/pipermail/openstack-dev/2016-October/106410.html 04:33:29 but with everyone shifting off DST (if it applies to you) it seemed to be a good time to revisit the timing of the meeting 04:33:52 njohnston: and i discussed this and i think we defn need to change it 04:33:55 njohnston: Sorry, today I absent for office. I just watched it. now watching.. 04:34:05 will help njohnston and mfranc213 to more sane times 04:34:12 What does everyone think? What sounds good? Please don't consider the options I presented as set in stone; suggest one if you think it would be better. :-) 04:35:03 Option 1 looks good for us 04:35:34 I am okay with both, but i think Option 1 is good because it is also more Europe friendly 04:35:40 Option 1 looks good but it seems to impact SridarK more 04:35:42 what do others feel ? 04:35:42 njohnston: quick reply. Both proposals are comfortable for me :) It's more better to 1st proposal. 04:36:04 SarathMekala: no i am an early riser - so i am ok 04:36:16 Yes, I didn't list Europe but I believe korzen is there... not sure where exactly... 04:36:18 njohnston: now this would be Thu ? 04:36:53 Yes, I was thinking Thursday, if that is amenable to everyone 04:37:10 ok with us 04:37:21 Yes should be good 04:37:27 Thursday is OK for me 04:37:30 Yes works for me 04:37:53 it sounds like we have a consensus for option #1. Does anyone object? 04:38:34 I did not respond on the mailer as it is more important to have consensus here 04:38:46 we can respond now 04:39:24 Hearing no objections, the motion passes. I'll respond to the ML post and generate a change to update the irc-meetings repo - unless anyone else wants to try their hand at it, it's really very easy. 04:39:29 Or can we just move fwd 04:40:16 I think it's best to move forward, if anyone objects on the ML we can check it out 04:40:27 ok sounds good 04:40:55 That's all I have 04:40:59 #topic Open Discussion 04:41:17 Anything else anyone would like to discuss? 04:41:20 hi, I have one question about firewall-rule 04:41:28 I wanted to clarify some things on capacity 04:41:36 but yushiro: pls go ahead 04:41:45 we don't support 'source_firewall_group_id' and 'destination_firewall_group_id' ? 04:42:19 currently, these values aren't included in resource attribute map. 04:42:24 yushiro: yes, i think we can look for use cases that really demand it and that can come after L2 in priority 04:42:31 yushiro: yes i asked to remove them 04:42:43 as we did not have support on the plugin/db layer 04:43:12 SridarK: OK, I understood. CLI patch still include these values, so I'll remove them. 04:43:17 we can certainly attack them but we can come up with some usecases on that 04:43:36 yushiro: yes i think u should remove them, we can add them when we have support on the server 04:43:47 chandanc_: i think u had some use cases 04:43:53 SridarK, Sure. It's all for me. 04:43:58 Thanks 04:44:02 we can discuss that after L2 04:44:09 or after the O-1 04:44:25 ok let me ask my question 04:44:38 I had some questions on this earlier 04:44:42 check out this link https://docs.google.com/document/d/1w8JjOp_iu6Lwr59saDDyMHLbmY_r4g-gvsvE-R1xD_k/edit 04:45:01 SarathMekala: ok yes actually we discussed it 04:45:15 good lets hold that and we can come back to it 04:45:18 sorry SridarK, i will have to go back an recollect the use-case, may be i can send in a mail 04:45:22 Just to note, I added the bit about source and dest fwg ID to the https://etherpad.openstack.org/p/fwaas-meeting etherpad fwaas v2 punchlist in a section titled 'deferred work' so we can track it and not forget about it 04:45:34 ok great 04:45:58 SridarK: ask away 04:46:06 I wanted to get a sense of how much capacity all of us can contribute to the FWaaS activities 04:46:07 Thanks njohnston. 04:46:17 we dont have to answer the question now 04:46:46 pls just think abt this and also discuss with ur management etc as all of us are probab juggling other responsibilities also 04:46:56 I should hopefully have more clarity on that in a month. 04:46:57 so we can get a sense in terms of planning 04:47:26 njohnston: yes totally fine - and this can also change from time to time 04:48:12 I guess also for the P cycle it will be good to know what features we can tackle 04:48:35 indeed 04:48:42 there have been many ambitious proposals but we will need to make sure we have enough contributors 04:48:50 SridarK, I hope so. 04:49:05 just a long term planning thing for some thoughts from all of us and our management 04:49:15 no rush here - just wanted to get it out 04:49:18 and i am done 04:49:33 yes, let's revisit this in a couple of weeks, perhaps we can all aim for some data by the first week in December 04:49:39 totally 04:49:57 just as a checkpoint, no stress for anyone 04:50:01 if nothing else from anyone we can close 04:50:07 yes exactly 04:50:07 Also, if you have any problems with getting patches in for project-config let me know - I am now one of the neutron infra liaisons https://review.openstack.org/#/c/392294/1/doc/source/policies/neutron-teams.rst@76 04:50:39 great :) 04:50:45 njohnston, wow! great!! 04:50:51 oh cool 04:51:20 njohnston: u can give us a tutorial on how all of this magic works some day :-) 04:51:29 +1 ^^ 04:51:32 great +1 04:51:33 I will! :-D 04:51:39 thx 04:51:55 Thanks everyone, and have a great day! 04:52:03 thx all for joining 04:52:09 Thanks all. 04:52:14 lets push for a productive week 04:52:34 njohnston, lets discuss about th CI patch 04:52:55 chandanc_: Yes, lets flip back to #openstack-fwaas 04:52:56 #endmeeting