04:00:29 #startmeeting fwaas 04:00:30 Meeting started Wed Sep 7 04:00:29 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:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:33 The meeting name has been set to 'fwaas' 04:00:36 Hi all 04:00:41 #chair xgerman SridarK yushiro 04:00:42 Current chairs: SridarK njohnston xgerman yushiro 04:00:44 O/ 04:00:44 Hello all 04:00:47 Hi all 04:00:48 Good day all! 04:00:58 lets get started 04:01:07 #topic FWaaS v2 04:01:27 firstly congrats and thanks to all for the super human effort over the last week to get things in 04:01:45 +100, thanks and congratulations to all. 04:01:58 We got more done than anyone thought we could! 04:01:59 +1 04:01:59 yes it was a great team work :) 04:02:00 yes, thanks !! 04:02:07 IMHO, i think this was a great run for the team to get a lot of things done 04:02:25 and some fantastic teamwork across multiple time zones 04:02:25 +1 04:03:20 yes :) thanks for your kindness. 04:03:21 i think we pretty much have everything in, 04:03:30 based on #link https://review.openstack.org/#/c/360207/ 04:03:51 the post mortem doc - it seems we will not get an FFE to push the CLI in 04:04:26 oh 04:04:33 i think that is fine, we still have some drawing board discussions - as in the email we have going with the FWaaS folks 04:04:58 yushiro: i know u have been pushing real hard on this 04:05:07 It is sad, but at least with the policy.json changes that just merged we will have the ability to give instructions using API interactions instead of CLI interactions, at least 04:05:22 +1 04:05:27 SridarK: Yes with Akihiro. 04:05:27 Nice! 04:05:39 And I am sure that if we keep the good work up there will be a python-neutronclient with the fwaas changes coming out soon 04:05:55 yushiro: i think u can continue to address the review comments and u can merge it in very soon into O-1 04:06:18 yushiro: also over the next few days if something were to change - we will take that 04:06:32 SridarK: Yeah. I hope so. Also I'll try to docs after. 04:07:05 i think we have enough in for folks to use with the REST i/f as njohnston mentions above 04:07:21 yushiro: I have an update to documentation that I have started, if anyone wants to contribute please do: https://review.openstack.org/366331 04:07:31 njohnston: +1 04:07:31 This is based on a conversation I had with Sam-I-Am today: http://eavesdrop.openstack.org/irclogs/%23openstack-doc/%23openstack-doc.2016-09-06.log.html#t2016-09-06T17:04:02 04:08:07 njohnston: great. 04:08:13 njohnston, sure 04:08:24 so lets all chip in on the doc front 04:08:34 both in terms of content and reviews 04:08:54 the other thing for us this week - would be to continue with the testing 04:09:32 +1 04:09:43 as we find issues - lets look at the seriousness of the issue and look for a solution - we should make sure that we follow due process 04:09:54 I haven't seen anyone else using the policy.d framework that we just shifted to use, so it'd be good to make sure it actually works. 04:10:14 and get critical fixes in and let the not so crtitical or cosmetic issues slide on to O 04:10:21 njohnston: +1 04:10:43 yes we do need to ensure that it is good, first order of business for us 04:11:02 njohnston: exactly. we need to make sure. 04:11:54 ok we can all get some devstack deployments spinning 04:12:21 It should be much easier now that all these things have merged - much less cherry-picking! 04:12:45 i think with that and the documentation - we should be wrapping up Newton 04:13:01 +1 04:13:21 other things to discuss for Newton ? 04:14:01 nope! 04:14:04 OK. 04:14:16 ok lets move on 04:14:27 #topic FWaaS v2 Ocata 04:14:42 njohnston: thx for capturing some of the things in flight for Ocata 04:15:15 I put up a separate Etherpad where we can all share out Ocata thoughts: https://etherpad.openstack.org/p/fwaas-ocata 04:15:27 Ocata is a short cycle, so we should try to be focused on our work and keep up the velocity we have maintained in the past few weeks 04:15:40 njohnston, getting permission denied on the links 04:16:08 njohnston: thanks! 04:16:13 SarathMekala: That is odd, it's just the regular openstack etherpad... I don't thinkt here is any authentication for those 04:16:19 lets review that and actually if we can target the remaining things and try to wrap up as much b4 the Summit that will be great 04:16:32 SarathMekala: i am able to get on 04:16:56 njohnston: documentation for CLI usage is necessary. Can I add for it ? 04:17:06 njohnston# Should we be targetting versioned objects as well? 04:17:09 yushiro: Please do! 04:17:12 chandanc: & SarathMekala: as soon as Newton ends can u push for reviews on the neutron changes for iptables 04:17:17 sorry my bad.. its working.. the links have a trailing ')' 04:17:18 padkrish: Yes, I think we should 04:17:20 padkrish: i believe so too 04:17:23 yes will do 04:17:32 ok, will add it to etherpad 04:17:43 done 04:18:25 great! 04:20:43 ok i think we are in agreement here that we will focus on the dependencies and other things we need to wrap up around L2 04:21:18 yes 04:21:24 other things to discuss here ? 04:22:17 if there are no other topics, we can head to open discusion 04:22:29 hi, I happened to find this meeting. 04:22:35 amotoki: hi 04:22:43 welcome! 04:22:43 do you have a plan to implement FWaaS v2 horizon support in Ocata? 04:22:50 amotoki: yes 04:22:58 we will need to find a volunteer 04:23:13 horizon team needs to deprecate fwaas v1 panel at some time officially. 04:23:22 amotoki: but yes that is the plan 04:23:36 amotoki: ah ok - this should be in Ocata ? 04:23:54 it is not a requirement 04:24:07 amotoki: is it possible that this can wait till we deprecate fwaas v1 04:24:11 amotoki: We are still supporting FWaaS v1 at this time 04:24:23 I think it should be doen once FWaaS v2 API becomes stable or mature. 04:24:32 +1 04:24:35 amotoki: ok that makes sense 04:24:43 :) 04:24:48 njohnston: fwaas v1 API is marked as deprecated in liberty release notes. 04:25:14 njohnston: I know we are still supporting it though. 04:25:35 amotoki: it seems there are still some users, so we should let v2 mature 04:25:48 totally agree 04:26:46 but there's no option now, it has to be V1 :) 04:27:32 amotoki: ok we will look into seeing who can volunteer for the Horizon work for fwaasv2, i will also talk to robcresswell 04:28:04 SridarK: i chatted this topic with rob a few days ago. 04:28:12 amotoki: also thx for helping with reviews on the fwaas v2 CLI 04:28:16 SridarK: this leads to my question above. 04:28:23 amotoki: ok 04:28:32 hi SridarK: I can give it a shot 04:28:40 SarathMekala: ok great 04:28:43 I have done some dabbling with Django a while ago 04:28:46 anyway let's share the plan if any udpate! 04:28:52 *update 04:28:59 amotoki: ok will do 04:29:06 SridarK: thanks 04:29:20 amotoki: do u see a lot more work on the CLI 04:30:35 amotoki: thx for ur help and direction, it seems this may not get an FFE, so in that case we would like to get it in soon after Ocata opens 04:30:50 SridarK: I think CLI support is almost good. some clean up are needed. 04:31:18 SridarK: we can release the client once Ocata release window is open. 04:31:29 SridarK: I think it is fine with FWaaS team. 04:31:32 amotoki: ok great, i think we had some discussions on co-existence with fwaas v1 04:31:51 amotoki: ok thx, anyways yushiro is working closely with u 04:32:02 SridarK: exactly 04:32:12 yeahaaaad 04:32:14 *yeah 04:32:24 amotoki: any thing else u would like to discuss 04:33:06 SridarK: none from me 04:33:17 amotoki: thx for stopping by 04:33:26 and we will update the Horizon plan 04:33:34 Thanks amotoki. 04:33:58 #topic Open Discussion 04:34:32 ok folks i think we have the important issues covered, we focus on testing/ critical bug fixing and Docs 04:34:47 Yeah. 04:34:51 I will be out of station for the next 2 days 04:34:59 other things we would like to discuss 04:35:10 chandanc: ok thx - u deserve a break 04:35:13 SridarK: 1 thing 04:35:20 :) 04:35:36 How about OSC plugin for fwaas v1 ? I'd like to disscuss this priority. 04:36:11 I think this priority is not so high and should be focus on debugging/testing. 04:36:25 yushiro: i would agree with u 04:36:44 I think it needs to be discussed with migration plan to v2 and neutron CLI deprecation plan. 04:36:59 but soon after this next week or 2 - if it makes sense lets look into it 04:37:21 even after neutron CLI is deprecated, it does not mean neutron CLI will go away soon. 04:38:30 amotoki: ok so this can wait as we figure out the migration plan 04:38:41 So I was wondering, who on the team is going to Barcelona? I am, with mfranc213. Who else? 04:38:58 njohnston: Maybe I will ! 04:39:25 I will make it 04:39:36 njohnston: I will be there too 04:39:46 not sure about me, waiting for budget 04:39:51 xgerman: said he may not be able to 04:39:59 chandanc: , SarathMekala: ? 04:40:07 Not sure as of now 04:40:15 will update soon 04:40:22 yep.. not clear as of now 04:40:27 I will be glad to see everyone who can be there! Perhaps this time we can get a room to discuss things and work together. 04:40:29 ok hope u guys can make it too 04:40:36 njohnston: +1 04:40:44 njohnston++ 04:41:52 as you may know, pike project team gathering will be held around Feb 20. 04:41:56 http://www.openstack.org/ptg 04:41:56 njohnston: In Austin, We found a good place for discussion. But it would be better if we can get a room :-) 04:42:07 note that ocata cycle will be shorted than usual. 04:42:17 *shorter* 04:43:28 amotoki: OK thanks. I'll remember. 04:43:36 Indeed. We will have to keep our disciplined approach to make sure we meet the expedited timetable for delivery of what we have targeted for that timeperiod. 04:43:42 i am hoping we will be able to pick up the L2 pieces rather quickly 04:44:11 SridarK: Yes. I'll work on it. 04:44:14 njohnston: +1 04:44:33 yushiro: thx, we will need to get the neutron pieces reviewed first 04:44:34 padkrish: thanks for your e-mail around L2 pieces. 04:44:36 me too... 04:44:55 need to finalize on the RPC part, will send a rough patch 04:45:01 yushiro: padkrish: i think the pieces are quite well defined 04:45:11 thanks njohnston for the pointer 04:45:36 SridarK: I think so. padkrish and njohnston can clarify that. 04:45:48 with the CLI in good shape, if we land the L2 pieces - we will have time to do more interop testing with Security Groups 04:46:00 +1 04:47:07 We should also go through the spec and make sure we identify any other areas we need to implement in order to complete it 04:47:34 for example, the spec says that we must allow multiple firewall group associations to a given port, but I think at the moment we only allow one 04:47:36 njohnston: yes i think the pieces are quite relevant in the L2 context 04:48:02 njohnston: +1 04:48:12 njohnston, i agree 04:48:32 njohnston: correct. We should support step by step. 04:49:15 right. The current driver design supports multi-port association though 04:49:16 njohnston: on that specific, we should be more comfortable on any ordering implications -there were some concerns there 04:49:28 the behaviour is that the latest rule wins 04:49:34 but yes we can validate that for sure 04:49:46 SridarK: agreed 04:50:00 also possibly a scrub thru the spec to see if some of the more esoteric features are needed 04:50:50 It is better to summarize on etherpad or anywhere with current SPEC(we should support for Ocata) 04:51:04 I'll consider about it. 04:51:24 hi all.. while going though the spec I had some questions 04:51:33 was waiting for the right time to ask :0 04:51:37 https://docs.google.com/document/d/1w8JjOp_iu6Lwr59saDDyMHLbmY_r4g-gvsvE-R1xD_k/edit?usp=sharing 04:51:44 can you take a look at this doc 04:52:02 looking... 04:52:28 go through it.. we can follow up on mail 04:52:49 SarathMekala: thx, lets add this to the ocata etherpad 04:53:05 sure.. will do that 04:54:32 Well, we're almost out of time 04:54:37 we could build a user story around some of these next level features - to validate complexity vs how useful 04:55:10 yes more offline discussions, after the next couple weeks 04:55:21 now we can stay on testing and doc 04:56:37 over the last few weeks - it has been fantastic to work together as a team - even though we come from differing corporate affiliations 04:56:48 never actually felt that 04:57:02 so thx again for that 04:57:14 I couldn't agree more. I am so proud to be a member of the FWaaS team! Thanks everyone! 04:57:25 i hope we can continue to to work togther over Ocata as well 04:57:28 Thanks to all :) 04:57:41 Me too. Thanks for giving me this opportunity. 04:57:47 +1 Great to be with this team 04:58:02 +1 04:58:19 2 min warning :-) 04:58:51 all right we can connect up over on openstack-fwaas or email 04:58:51 Anything else? 04:58:56 sounds good 04:59:00 nothing from me 04:59:08 None for me 04:59:15 #endmeeting