Wednesday, 2016-08-31

mfranc213because this all worked without the L3 agent ext framework, right?  (just to verify; apologies for very low-level questions, since i was out.)00:00
mfranc213which is to confirm with you that the smoking gun would have to be the change to the l3 agent ext framework...?00:01
SridarK_mfranc213: yes we tested that with the first agent patch (that merged)00:02
SridarK_no worries00:02
mfranc213thank you sridar00:03
mfranc213thinking/looking...00:03
mfranc213i wonder if it is related to the change at https://review.openstack.org/#/c/355576/22/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent_v2.py@11900:08
SridarK_ok i am in the rpc layer, let me pass on this info to u00:11
SridarK_http://paste.openstack.org/show/564930/00:12
SridarK_so on the rpc00:13
SridarK_In "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 155, in dispatch00:13
SridarK_so it does land up at the L3Agent as expected, but look at the attributes of that endpoint - the method of interest is missing00:14
SridarK_which is probab right in that as without the inheritance - create_firewall_group is not going to be there00:15
SridarK_so we may either need to sprinkle some other magic dust so we are also part of that rpc endpoint00:16
mfranc213thinking about what you said.00:18
mfranc213was there another alternative you were going to present?00:18
SridarK_no i am not sure on this either00:18
mfranc213and we know that the fwaas agent extension has been loaded properly?00:19
SridarK_but looking at the change u pointed to - let me try to undo that00:19
SridarK_that is something i would like to understand more too00:20
SridarK_ok undoing that change back to host=host did not help00:23
mfranc213yeah.  what happened then?00:24
njohnstonI think I have a theory.  What we had before, with the inheritance model, had the FWaaS agent code taking over entirely - it inherited from L3NATAgent and then became the primary identity of the agent.  So it had access to all L3_AGENT RPC messages.00:25
njohnstonBut now with the new code, we are separated, and there are only two ways for messages to get sent to the FWaaS code00:26
mfranc213the inheritance was the other way around, but i think the principal is the same00:26
njohnstonFirst, the L3NATAgent forwards the message (i.e. L# agent extensions API object)00:27
njohnstonSecond, the FWaaS agent extension configures itself as a direct RPC listener00:27
njohnston(which we haven't coded yet)00:27
mfranc213yes00:27
mfranc213good.00:27
mfranc213well, bad, but good.00:27
SridarK_njohnston: yes that makes sense00:28
mfranc213we were thinking of that inheritance model primarily/solely in terms of getting access to router info00:28
njohnstonso the message is getting dropped because we haven't set anything up to route it00:28
mfranc213but that model also enabled the rpd itself.00:28
mfranc213rpc00:28
njohnstonyes00:28
mfranc213so on the qos side...00:28
njohnstonon the QoS side all that mattered were messages on the PORT RPC topic00:28
SridarK_hmm but "to forward the RPC msg" - we will need something else in neutron to do this ?00:29
mfranc213they had both traditional and new-style rpc messaging on qos.00:29
mfranc213s/had/have00:29
mfranc213port deletes are done using the traditional rpc mechanism afaict00:31
njohnstonThe easiest solution at this point, if I am right, would be to go ahead and change the RPC topic for FWG, FWR, etc. objects from L3_AGENT to L3_FWAAS, and set up the FWaaS agent extension to subscribe to that topic directly00:31
SridarK_njohnston: that is my thought too00:31
njohnstonthe problem is not new style versus old style messaging, I believe00:31
mfranc213i'm catching up on this so you two go ahead while i try to wrap my brain around it00:33
njohnstonwe ave two different kinds of messaging - router updates, and firewall object updates.  We handled the first set, but the second set is a totally different kind of messaging.  Damn, I wish I had figured this out before.00:34
SridarK_njohnston: the second set is basically the CRUD00:35
SridarK_plugin - agent00:35
njohnstonright00:37
mfranc213njohnston are you talking, at least in part, about changing lines 74-76, and 84 on https://review.openstack.org/#/c/355576/22/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent_v2.py?00:38
SridarK_i am trying out a quick validation - by adding a new topic00:40
njohnstonit means fleshing out _register_rpc_customers on line 8500:41
mfranc213good.00:42
mfranc213i'm caught up now.  nate, you still have the baton though.00:42
mfranc213i would defn be way slower than you.00:42
njohnstonit'd be something like00:43
SridarK_i am adding this00:43
SridarK_    def start_rpc_listeners(self):         self.endpoints = [FWaaSL3AgentExtension(self)]          self.conn = n_rpc.create_connection()         self.conn.create_consumer(             'firewall_agent', self.endpoints, fanout=False)         return self.conn.consume_in_threads()00:43
njohnston    registry.subscribe(fwaas_callback, resources.FWAAS, events.UPDATE)00:43
SridarK_ouch that is not great00:43
SridarK_njohnston: ok this is a new style00:43
SridarK_i just added this - let me quickly change the topic in teh plugin for a quick test00:44
njohnstonSridarK_: you're right, I am wrong00:44
*** yamamoto_ has joined #openstack-fwaas00:44
njohnstonso will we end up bundling this all together into this change?  I kind of think we have to, but I am not sure00:48
mfranc213i think we have to00:49
SridarK_njohnston: yes i think so too - lets add this change00:56
SridarK_but let me see if it works00:56
njohnstonsounds good.  Do you want to send the necessary changes to me and I add them so you can preserve +2, or do you want to go ahead and add them directly?  I am fine either way.00:57
mfranc213oh boy nate.00:57
njohnstonmfranc213: ?00:57
mfranc213good thinking on that one00:57
njohnstonbrb, I need to go put my daughter to bed00:57
mfranc213i would have forgotten about the +2 piece of it.00:57
SridarK_njohnston: no i will send it across to u01:05
mfranc213did it work SridarK_ ?01:05
SridarK_mfranc213: sigh - ran into some stupid issues01:08
SridarK_mfranc213: do u have a few mins for a quick call ?01:08
mfranc213yes01:09
SridarK_ok let me get to a conf room01:09
mfranc213webex?01:09
SridarK_y01:09
SridarK_give me few mins01:09
mfranc213np01:10
*** yamamoto_ has quit IRC01:31
*** yamamoto_ has joined #openstack-fwaas01:38
*** vishwanathj has quit IRC01:59
*** chandanc_ has joined #openstack-fwaas02:04
*** chandanc_ has quit IRC02:15
*** diogogmt has quit IRC02:19
*** SridarK_ has quit IRC02:31
*** yamamoto_ has quit IRC02:48
*** yamamoto_ has joined #openstack-fwaas03:02
mfranc213i am fading and need to go to sleep.  i tend to wake up very early and i will get back online when i wake up.03:13
*** mickeys has quit IRC03:13
njohnstonsleep well mfranc213!  I am back on now03:14
*** yamamoto_ has quit IRC03:22
*** yamamoto_ has joined #openstack-fwaas03:22
*** yamamoto_ has quit IRC03:22
*** yamamoto_ has joined #openstack-fwaas03:25
*** yamamoto_ has quit IRC03:29
*** diogogmt has joined #openstack-fwaas03:44
*** chandanc_ has joined #openstack-fwaas03:47
chandanc_Hello All03:47
yushirohi03:47
chandanc_hello yushiro03:48
*** SridarK has joined #openstack-fwaas03:53
chandanc_Are we going to use only RPC calls ?03:54
chandanc_Hello SridarK03:54
SridarKchandanc_: Hi03:54
chandanc_Just going through the diffs03:55
SridarKok - i think something minor is missing03:55
chandanc_which one should i take03:55
SridarKhold off03:56
chandanc_ok03:56
SridarKi dont think either work properly03:56
chandanc_ok03:56
SridarKi think we can try to get this to quick resolution03:56
SridarKmay be we can try to wrap up the mtg quickly and debug this03:56
chandanc_ok03:57
*** padkrish has joined #openstack-fwaas04:00
*** SarathMekala has joined #openstack-fwaas04:02
*** njohnsto_ has joined #openstack-fwaas04:16
*** xdcc has joined #openstack-fwaas04:21
*** yamamoto_ has joined #openstack-fwaas04:29
yushirohi04:33
SridarKhi all04:33
chandanc_Hello All04:33
yushirofolks, I'll continue to fix UTs for CLI patch.04:33
chandanc_sure yushiro04:33
chandanc_give me a ping when ready04:33
SridarKyushiro: yes makes sense - we will not disturb u04:33
chandanc_I will test04:33
SridarKnjohnsto_: we will continue the debugging and update thru email04:34
yushiroI'm sorry for slow speed..  If you need some help, please ping me at any time!04:34
SridarKyushiro: no worries - many thx04:34
SridarKchandanc_: are u ok for a call - easier to share screen04:34
chandanc_yes, was about to ask for a call04:35
chandanc_ya04:35
njohnstonSridarK: Sounds good.  Is there anything in particular I can do to help now, or should I focus on being ready in the morning to take the torch from wherever you and chandanc_ have left things to keep it moving?04:35
chandanc_sounds good njohnston04:35
SridarKnjohnston: it seems that i am missing some piece - but we will continue - hopefully if we get this figured out - u can push the changes04:36
SridarKwe can sync over email or early am04:36
njohnstonSridarK: sounds good.  I will leave myself signed in and will read the logs as soon as I wake up.04:38
njohnstonchandanc_ SridarK: Thank you very much, ttyl.04:39
SridarKnjohnston: GN04:39
chandanc_GN njohnston04:39
*** padkrish has quit IRC04:40
*** padkrish has joined #openstack-fwaas04:41
*** padkrish has quit IRC04:41
*** njohnsto_ has quit IRC04:42
*** diogogmt has quit IRC05:17
*** xdcc has quit IRC05:23
*** chandanc_ has quit IRC08:15
*** mickeys has joined #openstack-fwaas08:20
*** mickeys has quit IRC08:25
*** chandanc_ has joined #openstack-fwaas08:45
*** yamamoto_ has quit IRC10:01
mfranc213hello.10:08
mfranc213looking at chandan's ps now.10:08
mfranc213i see what he did.  very nice.10:10
mfranc213i'm starting to look at the jenkins 3.4 failures on the plugin now.10:25
njohnstonthe pep8 failure is easy to fix10:32
njohnstonbut the failure for test neutron_fwaas.tests.unit.services.firewall.test_fwaas_plugin_v2.TestFirewallPluginBasev2.test_update_firewall_group_with_new_ports_no_polcy10:33
njohnstonthat one I don't see how it is happening10:33
mfranc213me neither :(10:33
mfranc213still looking10:33
njohnstonis that the one you're talking about, that has this midway through the traceback?10:33
mfranc213good morning nate10:33
njohnston      File "neutron_fwaas/services/firewall/fwaas_plugin_v2.py", line 230, in create_firewall_group10:33
njohnston        fwg_ports)10:33
njohnstongood morning10:33
mfranc213new ports no policy...10:39
mfranc213(just thinking out loud)10:39
SarathMekalaHi all.. I was looking at Yushiro's patch https://review.openstack.org/#/c/355755/2/etc/policy.json,unified10:40
SarathMekalaI have one question in this regards10:40
njohnstonmfranc213: I wonder if the issue is that there was no argument to FirewallGroupPortInvalid https://review.openstack.org/#/c/355576/23/neutron_fwaas/extensions/firewall_v2.py10:40
mfranc213njohnston: the key error must be in fwg_ports10:40
mfranc213njohnston: looking at what you just said10:41
SarathMekalaIn V2 we have renamed shared --> public, so in the policy.json all the existing references to shared_** should be renamed to public_** right?10:41
mfranc213njohnston: i agree that that's a problem, but i believe it's a separate problem.10:42
mfranc213the error is a key error10:42
mfranc213with no policy there's no port_id in the fwg dict10:43
mfranc213no 'port_id' dict10:43
mfranc213in fwg_ports dict i should say10:43
yushiroSarathMekala: no, if renames from 'shared' to 'public', fwaas v1 doesn't work at policy check.10:43
mfranc213but i'm not sure where that is being checked actually.10:44
SarathMekalaok.. so do we have corresponding public_** methods for all the existing commands?10:44
mfranc213njohnston: i'm going to talk to you privately to not muddle SarathMekala's posts10:45
*** mestery has quit IRC10:46
* njohnston thinks SarathMekala brings up an interesting point, but is not sure of the answer himself10:46
SarathMekalayushiro: I think "create_firewall_policy:shared": "rule:admin_or_owner", should have a corresponding "create_firewall_policy:public": "rule:admin_or_owner",10:47
yushiroSarathMekala: ah, Yes. You're right.10:49
yushiroSarathMekala: I was missing your point.10:50
SarathMekalayushiro : should I leave a comment on the review or do you think its a bit risky at this time10:50
yushiroSarathMekala: hmm, yes it's difficult timing ... let me see..10:51
SarathMekalayushiro, : one more thing that I have noticed.. there is no public definition for firewall_rule even in V110:52
SarathMekalabut I remember that a rule can be tagged as public10:52
yushiroSarathMekala: Yes. v1 is also missing 'shared' policy definition.10:53
SarathMekalayeah.. do you want to add it to V1 and V2 now?10:54
yushiroSarathMekala: No I don't. We shuould focus on V2 policy.  Regarding v1, we should post as an another patch.10:55
SarathMekalaOk.. Can I go ahead and post the patch for V1. I need to get my hands wet here :)10:55
yushiroSarathMekala: OK. Thanks. BTW, your previous question "ok.. so do we have corresponding public_** methods for all the existing commands?"10:56
yushiroSarathMekala: You mean that validation method on fwaas v2?10:57
yushiroSarathMekala: quick question.10:58
SarathMekalayushiro : your previous answer was good as I see that V1 and V2 both use the same policy.json file10:59
SarathMekalayushiro : so V1 will have shared_** aliases and V2 will public_** aliases11:00
SarathMekalayushiro : but there seems to be one target (policy) that mentioned that needs a corresponding target in V211:01
yushiroSarathMekala: OK, I understand.  Thank you.11:01
SarathMekalayushiro : need to catch my cab.. will login later tonight..11:01
*** chandanc_ has quit IRC11:02
*** SarathMekala has quit IRC11:06
*** chandanc_ has joined #openstack-fwaas11:12
*** SarathMekala has joined #openstack-fwaas11:15
mfranc213ihar just gave a million comments on the l3 agent extension api object.  i'm looking these over now.  https://review.openstack.org/#/c/357503/11:36
mfranc213nate and i are still looking into the plugin UT failures.  it's producing a {"NeutronError": {"type": "FirewallGroupPortInvalid", "detail": "", "message": "Firewall Group Port 2aba5c36-38cc-42dc-a68b-996f374794d3 is invalid"}} on the test for new ports no policy11:37
*** vishwanathj has joined #openstack-fwaas11:44
mfranc213ihar's suggestions will require changes to the agent extension.  we'll need to get coordinated on who's doing what.  right now, i'm drafting responses to ihar's comments in gerrit.11:47
mfranc213which means that i'm not looking at the moment at the plugin UT failures...11:56
*** yamamoto has joined #openstack-fwaas11:59
*** yamamoto_ has joined #openstack-fwaas11:59
*** yamamoto has quit IRC12:03
*** chandanc_ has quit IRC12:16
*** chandanc_ has joined #openstack-fwaas12:32
chandanc_Hello all12:36
chandanc_i am currently fixing the UT12:40
chandanc_can someone help me with running the UT as it needs to have the neutron patch in venv12:40
*** chandanc_ has quit IRC12:41
*** chandanc_ has joined #openstack-fwaas12:41
chandanc_Hello mfranc213 , njohnston12:42
njohnstonchandanc_: The easiest thing to do is to do: cd .tox/py27/src/neutron && git review -d 357503 && cd ../../../.. && tox -e py2712:42
chandanc_thanks a lot, let me try that12:43
mfranc213chandanc_ i had to do a git review -s first in that .tox subfolder...12:45
chandanc_yes i realized that12:45
njohnstonmfranc213: Really?  Interesting, it worked without that for me12:45
mfranc213okay, good, that's good to know.12:45
*** mestery has joined #openstack-fwaas12:52
*** yamamoto_ has quit IRC13:20
njohnstonchandanc_: How are you doing with the UT fixes for https://review.openstack.org/#/c/355576/ ?13:41
chandanc_mostly done,13:42
njohnstonExcellent!13:42
chandanc_just doing a final check and i have 6 more :(13:42
chandanc_njohnston, after discussing with SridarK , i introduced a validation for port owner in the plugin, it is causing some test failure. Need help to fix those13:43
chandanc_can you help ?13:43
chandanc_the last 6 UT are failing due to this13:44
njohnstonSure thing - why don't you push your changes to gerrit, and I can pull it to run in mye nvironment?13:46
*** _SarathMekala_ has joined #openstack-fwaas13:47
*** SarathMekala_ has joined #openstack-fwaas13:47
*** SarathMekala_ has quit IRC13:48
*** _SarathMekala_ has quit IRC13:48
chandanc_sure13:50
njohnstonchandanc_: Thanks!13:50
chandanc_let me push it13:50
chandanc_ok i just pushed it13:56
njohnstonThanks, already testing13:56
njohnston:-)13:56
chandanc_thanks :)13:57
njohnstonIn my environment, `tox -e py27` passed all tests13:57
chandanc_ya it passes, as i commented ou the validation13:57
njohnstonOh, what needs to be uncommented?13:57
njohnstonto exercise the issue we need to fix, I mean13:58
chandanc_https://review.openstack.org/#/c/355576/24/neutron_fwaas/services/firewall/fwaas_plugin_v2.py L20813:58
chandanc_basically check to validate for router port13:58
njohnstonOK, uncommented and testing13:59
chandanc_also both njohnston and mfranc213 please review the test related changes13:59
njohnstonWill do13:59
mfranc213i will.  thank you chandanc_!13:59
*** _SarathMekala_ has joined #openstack-fwaas14:03
njohnstonOK, uncommented and testing; I see that the web call returns this error, which makes sense for a validation fail: {"NeutronError": {"type": "FirewallGroupPortInvalid", "message": "Firewall Group Port 13a1a781-276f-4d17-8df3-275526424219 is invalid", "detail": ""}}14:05
chandanc_ya14:05
chandanc_actually the validation tries to access the port['device_owner']14:05
chandanc_this may not be populated in the test data14:06
njohnstonright, so right before that I checked the value of port_db['device_owner'], and it is indeed set to "network:router_interface"14:06
chandanc_yes14:06
njohnstonso the logic is performing as instructed14:06
chandanc_ya14:06
*** yamamoto has joined #openstack-fwaas14:07
njohnstonSo the next question is, why is a router interface in the firewall group?14:07
njohnstonLooking at the test_update_firewall_group_with_new_ports_status_pending test, for example, I see router interfaces getting created - but I see no interfaces that are not routers getting created.14:08
chandanc_this is to make sure that only l3 ports are added to the FWG, as the current implementation is supporting only l314:08
chandanc_but is the device owner set for those ports ?14:09
chandanc_can you give me the code location14:10
chandanc_I can also look in parallel14:10
njohnstonwell, in this case routers == l3, so when we do "self._router_interface_action('add', ..." we're always going to have the port owned by 'network:router_interface'14:10
njohnstonneutron_fwaas/tests/unit/services/firewall/test_fwaas_plugin_v2.py line 38414:10
chandanc_ok14:11
njohnstonso if the l3 agent is managing a port, it is almost certaintly going to be a router interface, right?  otherwise it'd be a port being managed by the L2 side of the code14:12
chandanc_in that case, i am not sure why the tests are failing :(, i could make sure that the error is coming due to this validation14:12
njohnstonIt seems like the validation logic is opposite, like it should say if port_db['device_owner'] != "network:router_interface":  raise fw_ext.FirewallGroupPortInvalid(port_id=port_id)14:12
njohnstonchange of '==' to '!='14:12
chandanc_:) thanks a lot14:13
chandanc_sorry, i missed it14:14
njohnstonchanging that causes all tests to pass14:14
njohnston:-)14:14
chandanc_cool14:14
njohnstonOK, feel free to push that fix, and then once mfranc213 is done with 357503 I can change 355576 to adjust to her changes14:15
SridarKHi All14:15
njohnstonHi SridarK!14:15
chandanc_I need to be away for 1/2 hr , then will pickup the functional/integ testing14:15
chandanc_Hello SridarK14:15
SridarKsorry just catchin up14:15
chandanc_SridarK, i could not proceed with the integ test as there were UT failure on the last PS14:17
chandanc_i will get to it in some time14:17
njohnstonSridarK: So ihrachys had some feedback for 357503, mfranc213 is working it; it will require some adjustment to 355576 because a method name changed etc.  And chandanc_ just pushed the last UT fix for 355576.14:18
*** xdcc has joined #openstack-fwaas14:18
*** mickeys has joined #openstack-fwaas14:18
*** chandanc_ is now known as chandanc_afk_30m14:20
mfranc213chandanc_, njohnston, SridarK 355576 will need a couple changes to coordinate with 357503.14:20
*** mickeys has quit IRC14:20
SridarKok just caught up, sorry was a long night and got up later than usual14:20
SridarKnjohnston: i think u have the issue on the UT failures nailed down14:21
njohnstonSridarK: Thanks!14:21
SridarKand chandanc has fixed the PS14:21
*** SarathMekala_ has joined #openstack-fwaas14:24
*** SridarK has quit IRC14:26
*** _SarathMekala_ has quit IRC14:27
*** SridarK has joined #openstack-fwaas14:27
*** chandanc_afk_30m has quit IRC14:28
*** yamamoto has quit IRC14:29
*** yamamoto has joined #openstack-fwaas14:29
njohnstonI just pushed a new PS for 355576 that changes the method names to match Margaret's changes in 357503.14:34
mfranc213i'm finishing up final ihar changes for 357503...14:34
njohnstonmfranc213: router_in_ns -> router_in_namespace and get_router_from_port_id -> get_router_hosting_port; are there any other changes that 355576 needs to account for?14:35
mfranc213njohnston: thinking about this14:52
*** chandanc_afk_30m has joined #openstack-fwaas14:52
*** chandanc_afk_30m is now known as chandanc_14:53
mfranc213njohnston: it's router_in_ns -> is_router_in_namespace.  other than those 2 method name changes i can't think of anything else15:00
chandanc_Hello mfranc213 , njohnston15:13
mfranc213hello chandanc_15:13
chandanc_i think we may need to add some entry points to the setup.cfg15:13
*** diogogmt has joined #openstack-fwaas15:14
chandanc_should i send you a paste url ?15:14
mfranc213yes please15:14
chandanc_http://paste.openstack.org/show/565212/15:14
chandanc_please have a look15:15
chandanc_you can always adjust the alias names15:15
njohnstonadded setup.cfg entries to https://review.openstack.org/35557615:18
SridarKok perfect on the setup.cfg15:18
mfranc213pushed hopefully last PS for https://review.openstack.org/35750315:19
SridarKmfranc213: :-)15:19
mfranc213fingers crossed15:19
mfranc213i keep making stupid mistakes today15:20
SridarKsigh no worries - i am on that boat too15:20
SridarKmfranc213: thx for getting all those comments addressed quickly15:21
njohnstonWe're all a little brain-fried %-)15:21
SridarK+115:21
SridarKnow with the setup.cfg entries does that do all the magic for us to stack and start up with everything setup ?15:22
njohnstonI *think* so15:22
njohnstonas long as we do the python setup.py develop15:22
chandanc_ya, that should be all we need, but we will need the ini file configs15:22
SridarKok - something chandanc_ and i were also discussing15:22
SridarKl3_agent.ini ?15:23
chandanc_ya15:23
SridarKadding the ext fwaas ?15:23
chandanc_let me share mine15:23
njohnstonI wish there was a way to put something in etc/oslo-config-generator that would mod l3_agent.ini15:23
mfranc213biab15:24
SridarKshould we try to get this in to 355576 or handle it as a bug15:24
SridarKalso do we want the devstack script to set the plugin to v2 ?15:24
njohnstonI think these changes are orthogonal to 35557615:25
SridarKshould we just keep v1 as default and have a doc entry to enable v215:25
SridarKnjohnston: ok agreed15:26
chandanc_http://paste.openstack.org/show/565216/15:26
*** yamamoto has quit IRC15:26
SridarKwe can probab add this as part of the q-fwaas tag - the processing for that15:27
SridarKbut i think there was some issue in us being able to define another tag due to the L3 Agent interaction15:28
njohnstonSridarK: you mean in the devstack plugin?15:29
SridarKnjohnston: yes15:29
SridarKbut if we want to keep v1 as default15:29
SridarKand turn on v2 that may be good too15:29
SridarK*turn on v2 if the user desires15:30
SridarKi have to drive in to work for an important meeting - so will be offline for a bit, but will log back in as soon as i am at work15:30
SridarKchandanc_: will u be able to start a sanity test on ur env ?15:30
njohnstonSridarK: Drive safe!15:30
SridarK:-)15:31
chandanc_sure will start15:31
chandanc_I was planning to pull in the CLI15:31
SridarKok will sync up in abt an hour15:31
chandanc_ok sure15:31
SridarKi think yushiro is probab nearing the final stage on this15:32
chandanc_I hope so15:32
yushiroSridarK: yes..15:32
SridarKok great15:32
SridarKbe back soon15:32
yushiroI finished firewall_group and firewall_policy.  the last is firewall_rule.15:33
*** _SarathMekala_ has joined #openstack-fwaas15:35
mfranc213great yushiro!15:36
*** SridarK has quit IRC15:37
*** SarathMekala_ has quit IRC15:39
chandanc_yushiro, just sent you a mail, some issue with CLI15:43
yushirochandanc_: Thanks! but I'll push it at once and reflect your feedback!15:43
chandanc_ok15:44
chandanc_sure, more like a FYI15:44
yushirochandanc_: If you'd like to through fwaas v2 API more easily, I'll send you a short term solution.15:47
yushiromaybe 3 month ago, I made ruby script to though REST API.15:48
yushiroCan I send to you?15:48
chandanc_I have some shell scripts :)15:48
yushiroOK.15:49
chandanc_using curl15:49
*** SarathMekala has quit IRC15:53
*** _SarathMekala_ has quit IRC15:55
njohnstonbbl, meeting my father for lunch15:57
mfranc213bye nate15:57
chandanc_mfranc213, which is the neutron patch that we need to apply for the last adjustment you did on 35557616:01
mfranc2131 sec chandanc_16:04
mfranc21327 is the last one, and it is the one nate pushed in order to work with PS 18 of https://review.openstack.org/#/c/357503/16:05
chandanc_ok thanks mfranc21316:06
mfranc213please let me know if there's anything else you need.16:06
chandanc_mfranc213, although i could do one end to end fwg create and populate iptables16:10
chandanc_there is an issue16:10
chandanc_2016-08-31 15:51:31.245 TRACE neutron_fwaas.services.firewall.agents.l3reference.firewall_l3_agent_v2 AttributeError: 'FirewallPluginV2' object has no attribute '_get_ports_for_firewall_group'16:10
chandanc_this happens when i restarted the l3 agent16:10
chandanc_mfranc213, here is the full trace on plugin side http://paste.openstack.org/show/565234/16:12
chandanc_afk for dinner16:12
*** chandanc_ is now known as chandanc_afk16:13
mfranc213thank you.  looking now.16:15
*** yamamoto has joined #openstack-fwaas16:17
*** mickeys has joined #openstack-fwaas16:29
mfranc213chandanc_ the db layer has changed: https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/db/firewall/v2/firewall_db_v2.py#L69416:30
*** yamamoto has quit IRC16:30
mfranc213the method name is now _get_ports_in_firewall_group16:31
mfranc213dealing with the fix now16:31
mfranc213not quite sure how the db patch made it in.  SridarK am i right that gate allowed this problem in?  see link above compared with https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/fwaas_plugin_v2.py#L11416:35
mfranc213(don't trust myself)16:36
mfranc213okay, SridarK isn't here at the moment.  looking further as to which direction to change things16:38
*** SridarK has joined #openstack-fwaas16:41
*** yamamoto has joined #openstack-fwaas16:47
*** chandanc_afk has quit IRC16:49
mfranc213chandanc_ https://review.openstack.org/#/c/355576 has the correct method name in the plugin but i'm trying to figure out why your version of the plugin has the wrong method name, since i know you're using 35557616:52
SridarKmfranc213: chandanc_: which method is this ? sorry just got back online16:53
mfranc213_get_ports_for_firewall_group (in chandanc_ 's plugin) verses _get_ports_in_firewall_group in the version of the plugin in 35557616:54
mfranc213the db has "def _get_ports_in_firewall_group"16:55
mfranc213but i don't see where https://review.openstack.org/#/c/355576 changed that part of the plugin16:55
SridarKhmm16:55
mfranc213so i'm trying to figure out how chandanc_ has the wrong version of the plugin, and how he got it!16:56
SridarKi am wondering if this was an issue that slipped thru16:59
mfranc213it did, yes.17:00
mfranc213but some patch fixed it, but it's not https://review.openstack.org/#/c/355576, which *contains* the fixed code but did not fix it itself17:01
SridarKi think it is a typo in _get_ports_for_firewall_group17:01
mfranc213yes, i agree.17:02
mfranc213i think _get_ports_in_firewall_group17:02
mfranc213makes more sense17:02
SridarKagreed17:02
mfranc213but where/how is chandanc_ getting the old code?17:02
SridarKhttps://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/fwaas_plugin_v2.py#L10017:02
SridarKi think we need to fix the typo here17:03
mfranc213no, no, wait SridarK17:03
mfranc213i don't think i'm making myself clear.17:03
mfranc213let me link something to you.  one sec17:03
SridarKoh sorry go ahead17:03
SridarKsorry i am in a mtg so i am a bit distracted17:04
mfranc213https://review.openstack.org/#/c/355576/27/neutron_fwaas/services/firewall/fwaas_plugin_v2.py@16917:04
SridarKand that looks to be the right thing17:05
mfranc213yes, but chandanc_ 's environment has the wrong thing.  how?17:05
SridarKoh i wonder if he might have fixed something17:06
SridarKlets wait for him to get back online17:06
mfranc213could there be another patchset that he has overlaid on the top of 355576, where the other patchset reverts that line of code?17:07
SridarKnot sure, but this is an opportunity to fix it17:07
SridarKas we get the final PS pushed for 3557617:08
mfranc213right17:08
SridarK*35557617:08
mfranc213yep :)17:08
mfranc213but SridarK, 35576 did not fix that--if  you compare latest PS to its base, that line was already fixed.17:09
mfranc213so what fixed that line in the plugin, do you know?17:09
njohnstonback17:11
mfranc213hi nate17:12
SridarKmfranc213: i am wondering if L#169 was not a problem17:12
SridarKit was as is17:12
SridarKi think the method around L#100 had the snafu17:13
mfranc213oh, ok.17:13
mfranc213no, wait, i retract that "oh, ok"17:14
mfranc213:)17:14
mfranc213i agree with you that that line 100 has the problem.17:14
SridarKok good17:14
mfranc213i guess my questions are: 1) where and how did it get fixed? 2) how come chandanc_ 's environment doesn't have the fix, given that he's using 355576 ?17:15
SridarKthat i am also wondering17:18
*** chandanc_afk has joined #openstack-fwaas17:23
SridarKchandanc_afk: hi17:31
SridarKmfranc213: i sent an email out on related to what u found17:32
chandanc_afkHello All17:32
SridarKpls check if that diff makes sense and we will pick that up on the next rev17:32
*** chandanc_afk is now known as chandanc_17:32
mfranc213SridarK reading it now!17:33
*** yamamoto has quit IRC17:34
chandanc_Hello SridarK17:35
chandanc_just catching up17:35
*** SridarK has quit IRC17:37
*** SridarK has joined #openstack-fwaas17:39
SridarKmfranc213: my version of 355576 did not have the change in the method around L#10017:40
SridarKi pulled it late last night17:40
SridarKchandanc_: did u do a sanity with the latest PS17:41
njohnstonhttps://github.com/openstack/neutron-fwaas/blame/master/neutron_fwaas/services/firewall/fwaas_plugin_v2.py#L107 has the 'for' not the 'in' syntax and says the v2 driver plugin had it17:41
SridarKnjohnston: yes that needs to be fixed17:42
njohnstonpushing a new PS for 355576 that has the fix now17:42
mfranc213it already has the fix!!!17:42
mfranc213is already has the fix17:43
mfranc213oh my goodnes!17:43
njohnstonmfranc213: I just did 'git review -d 355576' and it didn't have the fix17:43
SridarKmfranc213: that is what i think too17:43
mfranc213https://review.openstack.org/#/c/355576/27/neutron_fwaas/services/firewall/fwaas_plugin_v2.py@16917:43
mfranc213is it wrong in another place?17:43
chandanc_L11017:44
mfranc213ah17:44
mfranc21311017:44
chandanc_L11417:44
njohnstonand L11417:44
mfranc213ok, i'm sorry17:44
mfranc213i thought i was going crazy17:44
mfranc213and now i know that i am17:44
SridarKmfranc213: relax - u are fine17:44
chandanc_same here :)17:44
njohnstonnew PS piushed for 35557617:44
mfranc213thank you njohnston17:44
SridarKnjohnston: thx17:45
njohnstonmy pleasure17:45
chandanc_I could do, one end-to-end fwg-create17:46
chandanc_all seemed good except the one issue17:46
chandanc_with the new PS we should be good17:46
njohnstonfantastic, chandanc_17:48
SridarKchandanc_: the issue that u hit was the change njohnston just pushed ?17:48
SridarKie, problem with get_firewall_groups_for_project17:49
chandanc_http://paste.openstack.org/show/565234/ yes17:49
chandanc_it has the trace17:49
chandanc_L11417:49
chandanc_njohnston, yes looks like we are mostly there17:51
SridarKchandanc_: ok perfect17:51
mfranc213jeopardy music17:54
mfranc213who wants to go out for a beer with me once all this merges?17:55
chandanc_:) too bad for me17:55
SridarKvirtual beer :-)17:55
chandanc_thats one thing not for the cloud17:56
mfranc213:)17:56
SridarK:-)17:57
xgermanSangria in Barca?18:01
xgermantoo bad I don’t have funding18:01
njohnstonxgerman: :-(18:02
*** diogogmt has quit IRC18:02
SridarKxgerman: sigh :-(18:02
xgermanno worries, maybe next time will be better ;-)18:03
SridarKlets hope for that18:06
mfranc213does this mess us up or help us: Use model_base from neutron-lib  https://review.openstack.org/36384518:09
mfranc213(just proposed by Henry Gessau)18:09
xgermangood thing18:09
xgermanneutron_lib is supposed to be the future18:10
njohnstonyep.  I had a change already to do this, but I abandoned it in favor of Henry's18:20
njohnstonJust keeping us up to date with the developments in neutron_lib as of v0.4.018:21
mfranc213cool18:21
njohnstonI also made a full list of all the imports fwaas has from neutron proper and passed that along to dougwig for them to use as a punchlist18:21
mfranc213how will they use that?18:23
mfranc213(you are always at least 2 steps ahead of me, btw)18:23
njohnstonSo their charter is to take all those places and move them from neutron to neutron_lib so fwaas won't import from neutron anymore.18:23
mfranc213ohhh, of course.18:24
njohnstonI am hoping to help with that next cycle18:24
mfranc213nice.18:24
njohnstonI have to step into a meeting with my new VP now, back in :3018:24
njohnstonIdeally in the meantime we can get a +2+A from carl_baldwin on https://review.openstack.org/#/c/357503/ - I think that will clear our biggest impediment.18:25
mfranc213bfn18:25
carl_baldwinnjohnston: I have it up, was meaning to check out what was suggested since my last review.18:26
mfranc213thank you carl_baldwin18:26
*** chandanc_ has quit IRC18:32
*** yamamoto has joined #openstack-fwaas18:35
*** mickeys has quit IRC18:39
*** xdcc has quit IRC18:40
*** yamamoto has quit IRC18:42
*** diogogmt has joined #openstack-fwaas18:48
yushiroHi, all.18:54
yushiroI just updated CLI patch.  UT is good bat more UTs are necessary.  I'll add more.18:55
yushiromfranc213: Thanks for your comment but I'll reflect the next PS.18:55
yushiroSo, I'll go home and come back to my office.18:55
yushiroSee you 5 hours later!18:55
*** diogogmt has quit IRC18:57
mfranc213thank you yushiro!19:01
SridarKyushiro:thx - i think we can track the need for more UT as a bug19:02
mfranc213+2+1 from carl on l3 agent extension api19:20
SridarKyes saw that - that is so great - njohnston: , mfranc213: really nice job in pushing that thru19:28
mfranc213thank you SridarK!19:32
njohnstonthanks to everyone19:32
mfranc213seconded19:33
SridarK+119:33
SridarKi am on 355576, some quick thoughts - sort of stating the obvious19:33
SridarKnow that we have uncoupled the inheritance relationship, we have broken v119:34
SridarKand the tempest failures19:35
njohnstonUnderstandable - what do we need to do to adapt v1 to the new methodology?19:35
SridarKwhich is expected19:35
mfranc213can the delta in https://review.openstack.org/#/c/355576 simply be applied to v1, or is it not that simple?19:36
SridarKthe changes could be ccery similar19:36
SridarK*very19:36
SridarKshall we do a quick call ?19:36
SridarKi think it is not that complicated to do this19:37
mfranc213SridarK what would be the desired timelines for issuing such patches?19:37
mfranc213yes, i can do a call :)19:37
njohnstonme too19:37
SridarKnjohnston: are u avail as well ?19:37
SridarKok got it let me go to a conf room19:37
njohnstonthanks SridarK19:37
mfranc213sounds good19:38
*** yushiro has quit IRC19:38
*** mickeys has joined #openstack-fwaas19:40
*** mickeys has quit IRC19:45
*** diogogmt has joined #openstack-fwaas20:14
SridarKCLI - pep8 was simple, looking at UT20:19
SridarKmfranc213: can u pls take a look here:20:26
SridarKhttp://logs.openstack.org/82/351582/11/check/gate-python-neutronclient-python27-ubuntu-xenial/881db50/testr_results.html.gz20:26
SridarKit seems the failures are unrelated20:26
mfranc213yes20:26
mfranc213SridarK i see four failures all of the sort AttributeError: 'module' object has no attribute 'add_project_domain_option_to_parser'20:28
SridarKyes exactly20:28
mfranc213are there others that i'm missing?20:28
SridarKno all others pass20:28
SridarKnow these are not tests that are part of this PS20:29
mfranc213should a rebase be done, since the failures are all in osc_utils?20:29
njohnstonSridarK: quick question - do we need to change FWaaSL3PluginApi in https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py#L33 - I think it can stay the same, but want a doublecheck20:30
mfranc213looking20:30
mfranc213i do not see a need to change this other than the tenant-->project vernacular.20:31
SridarKnjohnston: yes u are correct no change needed there20:32
mfranc213i see you asked SridarK!20:32
SridarKmfranc213: i wonder too - i am also looking into the code there20:33
*** mickeys has joined #openstack-fwaas20:41
njohnstonSridarK: It looks like the v1 file does not have a class like 'L3WithFWaaS' at https://review.openstack.org/#/c/355576/28/neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent_v2.py@501 - is this something we need to add for v1?20:41
*** mickeys has quit IRC20:42
*** mickeys_ has joined #openstack-fwaas20:42
SridarKnjohnston: yes we will need that, i think it was present in one of the files we are deleting as part of this change20:44
njohnstonSridarK: Great, thanks!20:45
SridarKnp20:45
njohnstonStatus update: I just pushed a new PS for https://review.openstack.org/355576 and there are 3 UTs still broken, I haven't even tried to run the tempest tests yet21:01
njohnstonIt looks like what needs to happen is for the tests to create an agent extension api and pass it to the extension and then it will work.21:02
njohnstonThe errors for all 3 failures are:21:02
njohnston      File "neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py", line 126, in _get_router_info_list_for_tenant21:02
njohnston        self.agent_api.get_routers_in_project(tenant_id)21:02
njohnston    AttributeError: 'NoneType' object has no attribute 'get_routers_in_project'21:02
njohnstonI think that code can be copied from the v2 tests21:03
njohnstonThe 3 tests failing are all in neutron_fwaas.tests.unit.services.firewall.agents.l3reference.test_firewall_l3_agent.TestFwaasL3AgentRpcCallback21:03
njohnstonSridarK, mfranc213, and *, I am going to head home now, I will be on later21:04
mfranc213njohnston, thank you.  excellent work.  i'll look at fixing the final UTs now as you head home.21:05
SridarKnjohnston: cool21:08
*** mickeys_ has quit IRC21:13
*** mickeys has joined #openstack-fwaas21:14
SridarKi can get some UT's to pass in changing an import to use a different package (openstackclient) on the CLI patch21:30
mfranc213SridarK that is most excellent21:31
SridarKi will step away for a bit - be back online in abt 30 or 40 mins21:31
mfranc213SridarK: bye for now21:31
SridarKi am not so sure on that still - let me clean that up do more verification and share that - we can decide on what next after that21:32
SridarKbye be back soon21:32
mfranc213SridarK: sounds good.21:35
*** SridarK has quit IRC21:37
*** diogogmt has quit IRC21:48
mfranc213ping njohnston22:16
*** SridarK_ has joined #openstack-fwaas22:22
SridarK_njohnston: & mfranc213: on 355576 - we probab want the default to load up v1 so tempest can run as opposed to loading up v222:26
*** njohnsto_ has joined #openstack-fwaas22:57
*** njohnsto_ has quit IRC23:01
*** njohnsto_ has joined #openstack-fwaas23:02
SridarK_njohnsto_: hi so 3 failures on the v1 agent file,23:05
SridarK_just need to step away for 10 mins or so - will get back23:06
njohnsto_Ok so those are still an issue then?23:09
*** njohnsto_ has quit IRC23:20
SridarK_looking23:25
*** njohnsto_ has joined #openstack-fwaas23:29
mfranc213njohnston: i am working on these23:31
mfranc213the fixes revealed some other issues.23:32
njohnsto_Gotcha, thanks!23:32
mfranc213i can push the PS shortly to have you take a look23:32
*** SarathMekala has joined #openstack-fwaas23:32
SridarK_mfranc213: ok23:32
SridarK_mfranc213: neutron_fwaas/services/firewall/agents/l3reference/firewall_l3_agent.py", line 12623:33
mfranc213yes, i've changed that23:33
SridarK_self.agent_api is not getting set for the agent ext to pick up the  ...23:33
SridarK_ah ok cool23:34
mfranc213yes, i've fixed that part of things.  i'm down to one UT failure.23:34
*** njohnsto_ has quit IRC23:34
*** njohnsto_ has joined #openstack-fwaas23:35
SridarK_one other thing is i wonder if we can actually have it run v1 for tempest23:35
mfranc213njohnsto_ do you want to take a look?23:37
mfranc213you'll see what i've done.  it has a print in there to show the namespace.  the agent_api is being consumed, some other issues that were then revealed have been resolved.23:38
mfranc213but the one test failure remains and i think fresh eyes would be super.23:38
njohnsto_Sure, when I get home; on via my iPhone running an errand ATM.23:38
SridarK_mfranc213: which test ?23:38
mfranc213i'm going to take a break and will come back a bit later.23:39
mfranc213SridarK: neutron_fwaas.tests.unit.services.firewall.agents.l3reference.test_firewall_l3_agent.TestFwaasL3AgentRpcCallback.test_get_router_info_list_two_routers_one_without_router_info23:39
*** yushiro has joined #openstack-fwaas23:39
SridarK_mfranc213: ok let me pull ur PS23:39
mfranc213thank you sridar23:39
yushiromorning, all I just come to office.23:39
yushiro^^ I saw IRC log now.  Conguras for L3-agent !23:41
njohnsto_Thanks, yushiro!23:42
*** diogogmt has joined #openstack-fwaas23:46
yushirooh... my CLI patch got '-1' from jenkins Thouth UT has succeeded in local.23:48
yushiroI'll fix it now.23:48
*** _SarathMekala_ has joined #openstack-fwaas23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!