04:01:54 #startmeeting fwaas 04:01:55 Meeting started Wed Jun 22 04:01:54 2016 UTC and is due to finish in 60 minutes. The chair is njohnston|afk. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:01:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:01:58 The meeting name has been set to 'fwaas' 04:02:06 #chair SridarK xgerman 04:02:12 Hello all 04:02:40 aloha 04:02:45 njohnston: as always thx for updating the agenda 04:02:58 we can make a quick run thru of things 04:03:10 indeed 04:03:17 As noted we are getting close to N-2 04:03:22 my pleasure re: the agenda 04:03:27 hi 04:03:48 i think we are in various phases of things 04:04:12 lets get to v2 quickly and then we can get to the L3 ext work 04:04:18 ok 04:04:18 #topic FWaaS v2 04:04:44 njohnston: i have been working thru the integration with the db 04:05:20 mostly run into some teething issues - i have one issue with the ext getting loaded properly as neutron goes thru the extensions 04:05:51 i am debugging that - i think once i get past that i should be able to test more with the db 04:06:07 i had some down time last week so lost some time on that 04:06:53 njohnston: i had some pieces that i updated with the db - once i get thru a basic test - i can publish them to u 04:06:53 sounds good on the progress 04:07:08 SridarK: thanks 04:07:47 njohnston: mfranc213_: things u would like to bring up in the context of the db patchset or anything on versioned objects 04:08:07 I haven't had any time to work on the db patchset 04:08:20 njohnston: understand totally 04:08:34 I thought padkrish and yushiro were working on versioned objects https://review.openstack.org/#/c/323971/ 04:08:39 paddu is still out this week 04:08:48 over to yushiro 04:09:10 yushiro: things to discuss with the agent ? I saw that u pushed another update 04:09:49 SridarK, njohnston : Yes. I've updated the patchset but it is 'nit'. 04:10:18 SridarK, njohnston Today, I ask someone to help to reach out ajo and Ihar. 04:10:32 yushiro: ok 04:10:44 sure thing - you want them to review the change, or do you have specific questions? 04:11:00 I've been contacting ajo and Ihar on IRC and e-mail. But the timing is not good ;( They don't answer. 04:11:01 * njohnston will speak to them in the morning. 04:11:28 I know they both use ZNC bouncers. It is unfortunate they haven't answered email. 04:11:30 njohnston, Both. Therefore, I'll send e-mail to you about 'question'. 04:12:08 Thanks! My email is openstacknate@gmail.com 04:12:28 yushiro: great - njohnston: thx to help facilitate movement on this 04:12:31 njohnston, Understood. Thanks for your help and sorry for my slow progress. 04:12:42 yushiro: It is my pleasure to assist. 04:13:45 chandanc, SarathMekala: how is your progress going? 04:13:54 yushiro: if i can get some basic db integration going, in a day or two - perhaps we can try to see if we can get some basic plugin - agent communication 04:14:03 I have been discussing the driver changes with mickey 04:14:27 chandanc: thx - i think u can start a WIP patchset 04:14:28 but need some help with starting change request with the neutron project 04:14:38 SridarK, Great. I see. 04:15:14 SridarK: I will ping you for some help with the PS creation 04:15:22 chandanc: surely 04:16:30 not much progress from my side.. I was doing a deep dive into L3 agent code 04:16:38 chandanc: i think once u have some clarity on this - u can start thinking in terms of the driver changes ? 04:17:00 SarathMekala: ok let me know if u have questions on that 04:17:09 yes, once the conntrack is done, totally have to be on the driver 04:17:22 sure.. I will spend a few more days on this and review the corresponding rsts 04:17:58 ok other things to discuss on iptables ? 04:18:16 chandanc: we will figure out a time to connect 04:18:54 sure, do you hangout on the openstack-fwaas during the week ? 04:19:33 chandanc: yes i am on - last couple of days - had some issues to deal with it and i may not have been on 04:19:45 if u dont find me email will work too 04:19:46 ok sure 04:20:09 ok lets move on 04:20:24 #topic L3 Agent extension 04:20:37 njohnston: pls go ahead 04:20:52 So the spec was discussed in the neutron team meeting earlier today 04:20:52 njohnston: thx for pushing this forward 04:21:10 I believe the decision was to up the priority from 'low' to 'high' to match the fwaas v2 spec 04:21:58 I've been keeping up with the comments, although there is a lot about the l3 agent I still need to learn about, like l3 agent variants (i.e. neutron-vpn-agent) 04:22:25 i think u have addressed all the comments - i think the last set was more of a general nature 04:22:43 njohnston: i can help a bit with the vpn agent 04:22:55 As far as implementation, I have the first part of the work up, which is to move selected parts of the l2 agent extension stuff out of the l2 agent so that l3 agent can use it as well. 04:23:24 basically if vpn is configured - due to the old inheritance model - l3 agent runs as the vpn agent 04:23:31 kind of confusing for sure 04:24:09 SridarK: If you could tell me if the comment "probably make them an alias of the base l3 agent but with a different set of default extension drivers?" from yamamoto takashi is correct? 04:24:40 so QoS stuff still works with https://review.openstack.org/#/c/329701/ going, so I think/hope it's pretty good 04:25:10 njohnston: it was not very clear to me on his comment 04:25:17 and now my effort is in writing a stub for an fwaas agent extension that will hook in to the agent extension code, that we can then integrate with the right parts of the existing fwaas codebase. 04:25:27 that is my main effort for this week. 04:26:17 njohnston: the first patchset shd move fwd irrespective of fwaas 04:27:04 The main impediment now seems to be getting reviews 04:27:06 njohnston: i can help with the next part to hook things up with fwaas 04:27:17 SridarK: Excellent, I was hoping you would say that 04:27:54 just give me 1 or 2 days - i want to wrap up this integration effort 04:28:16 SridarK: absolutely 04:28:59 i think for our part - we can keep getting the patches out 04:29:06 agreed 04:29:24 that is it for me on this topic 04:29:25 anything else to discuss on this topic ? 04:29:34 ok u read my mind :-) 04:29:50 #topic devstack plugin patch 04:30:07 #link https://review.openstack.org/214350 04:30:22 there was an issue with the testing of the devstack patch 04:30:27 so this has been causing me some intermittent issues 04:30:30 but sc68cal isolated it to something else 04:30:45 https://review.openstack.org/#/c/332256/3 04:31:16 it looks like the test accessed an element that never existed 04:31:16 ok 04:31:30 I think the consensus is that the devstack patch is fine to proceed 04:31:46 i found out more on the issue i was seeing 04:31:59 do tell 04:32:15 yes 04:32:18 it seemed for some odd reason on my test - the install of neutron-fwaas as a component had some issue 04:32:45 so i did not see the db migration scripts run to create the firewall_router_insertion table 04:33:02 now even if i ran the script manually it did not happen 04:33:58 wierd 04:34:35 but if i did a pip install from neutron-fwaas - i was good 04:35:00 given that chandanc consistently did not see an issue 04:35:20 njohnston: are u also now okay with testing on this ? 04:35:39 may be because I was running a fresh devstack 04:35:52 chandanc: i did the same too 04:36:19 SridarK: I am having issues with local testing, my neutron does not start 04:36:30 but I think xgerman commented that it worked well for him 04:36:30 njohnston: ok 04:36:36 ok 04:36:48 and the only gate issue was the issue sc68cal identified, which only occurs on the postinstall tempest tests 04:37:00 ok 04:37:07 SarathMekala: is ur setup good now ? 04:37:21 I am getting an issue 04:37:37 I replicated Chandans setup but my setup fails with 04:38:11 *while starting neutron 04:38:25 njohnston, I'm trying the latest version of devstack with https://review.openstack.org/#/c/214350 04:38:31 2016-06-16 14:36:21.821 10798 ERROR neutron ImportError: Plugin 'neutron_fwaas.services.firewall.fwaas_plugin.FirewallPlugin' not found. 2016-06-16 14:36:21.821 10798 ERROR neutron q-svc failed to start 04:38:50 SarathMekala: I had the same issue 04:38:55 SarathMekala: hmm that is odd 04:39:07 I talked with sc68cal on it in #openstack-fwaas earlier 04:39:14 yushiro: i think ur setup was good too 04:39:58 I can give another run on a fresh system, if that helps ? 04:40:28 chandanc: sure and i will move some things around too and try again 04:40:44 if we can converge on this - we can move fwd with this 04:40:47 will give it a shot as well 04:41:01 will post my local.conf on pastebin and share 04:41:03 just trying to be conservative on this to do the due diligence 04:41:15 chandanc: lets sync on the same email thread 04:41:20 my discussion with sc68cal was brief but here it is: http://paste.openstack.org/show/521038/ 04:41:20 sure 04:41:35 all I know is that the error does not occur in the gate 04:41:42 the ImportError error 04:41:54 96 04:42:31 njohnston: this could have some bearing on what i see - perhaps a slightly different symptom 04:43:31 njohnston: lets compare notes tomorrow and see if there is something we are missing 04:43:43 definitely, let's connect on #openstack-fwaas 04:43:52 njohnston: sounds good 04:43:54 njohnston: nor mally python setup.py develop puts a path link to the source location in the python path, you can manually run the command "python setup.py develop" can check the output 04:45:23 ok lets continue this tomorrow 04:45:23 ok, so we will reconvene on this tomorrow and compare notes 04:46:08 ok lets get to the open slot 04:46:15 #topic Open Discussion 04:46:28 I added another topic to the agenda earlier today 04:46:46 I think we should talk about our pending ejection from the stadium 04:46:54 njohnston: yes absolutely 04:47:16 when the fwaas v2 spec came up in the neutron team meeting, the comments were very critical 04:47:47 ejection seems close to inevitable http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-06-21-14.00.log.html#l-214 04:48:17 Neutron is going to hold real mid-cycle. Will FWaaS team planing to hold virtual mid-cycle? 04:48:45 I am not sure what we can control on this front, my take is that we should continue with things to get the spec implemented 04:48:47 hoangcx: Yes, we are definitely planning on a virtual mid-cycle. It's getting late in the cycle, we should probably schedule it 04:48:59 Just concerning :-) 04:49:29 it seems the other *aaS will be out for sure 04:49:34 njohnston: Thanks for the info. I got it. 04:50:01 my wonder is if the community would look on us more favorably if we take control of the spinout process rather than getting evicted 04:50:30 njohnston: that is a good point for us to ponder on 04:50:53 njohnston: but will be good if we can get some of our patches merged first 04:51:04 atleast that is one thought 04:51:11 SridarK: Agreed, just thinking about the long game. :-) 04:51:24 njohnston: yes agreed 04:52:22 do others have some immediate thoughts ? 04:53:30 dont mean to put anyone on a spot - we can take some time to deliberate on this 04:53:49 but this will bear some decision making on our parts 04:54:27 Indeed, I want to raise awareness - I was dispirited to see the tone of some of the comments 04:54:37 njohnston: +1 04:55:20 njohnston, +1 04:55:38 lets continue to target a basic end to end implementation by N-2 04:56:25 yep 04:56:38 :) 04:56:44 sure. Whats the date for N-2? 04:56:54 lets get some of these patches merged - show progress by N-2 will be very positive for us 04:56:58 mid July 04:57:07 SarathMekala, http://releases.openstack.org/newton/schedule.html 04:57:15 Thanks Yushiro 04:57:53 lets think thru a favorable time for the virtual mid-cycle 04:58:19 ok i think we all know our priorities 04:58:31 we are almost at time 04:59:15 thanks everyone! yushiro, I will talk to ajo and ihrachys tomorrow first thing and keep you updated 04:59:31 njohnston, Thank you so much! 04:59:50 thanks all 05:00:03 Thanks. Bye. 05:00:08 bye 05:00:17 * SarathMekala thanke every one o/ 05:00:18 Bye 05:00:28 #endmeeting 05:00:41 bye 05:01:01 njohnston: looks like u will need to close 05:01:07 #endmeeting 05:01:19 #endmeeting