| *** SumitNaiksatam has quit IRC | 00:12 | |
| *** Tim_Eberhard has joined #openstack-fwaas | 00:30 | |
| *** Tim_Eberhard has quit IRC | 00:31 | |
| *** hoangcx has joined #openstack-fwaas | 00:56 | |
| *** trungnv has joined #openstack-fwaas | 01:09 | |
| *** SumitNaiksatam has joined #openstack-fwaas | 02:25 | |
| *** vks1 has joined #openstack-fwaas | 03:24 | |
| *** mickeys has quit IRC | 03:59 | |
| *** yushiro has joined #openstack-fwaas | 04:28 | |
| *** mickeys has joined #openstack-fwaas | 04:39 | |
| reedip | xgerman : yeah, saw it.. tempest failed for fwaas router insertion | 04:43 |
|---|---|---|
| reedip | @yushiro: do you have any idea if we are going to propagate fwaasrouterinsertion extension for fwaas_v2 | 04:43 |
| reedip | as per the current understanding, the way fwaas_v2 is written, we do not wish to use the extension | 04:43 |
| yushiro | reedip, hi. You mean, enable to specify router_id in creating firewall-group? | 04:44 |
| reedip | yep | 04:45 |
| yushiro | hmm..., Currently,,, I don't have. However, can we use current extension with a few customization? | 04:47 |
| yushiro | reedip, xgerman Sorry, I couldn't read previous log. Was there some issue? | 04:49 |
| reedip | none as such yushiro | 05:01 |
| reedip | currently I am trying to debug http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce/console.html | 05:02 |
| reedip | The issue is that fwaasrouterinsertion tempest test are failing even though the extension is included | 05:02 |
| reedip | because router_ids is not a part of the API | 05:02 |
| *** Tim_Eberhard has joined #openstack-fwaas | 05:21 | |
| yushiro | aha. OK. I'll dit it. | 05:24 |
| yushiro | s/dit/dig/ | 05:24 |
| *** Tim_Eberhard has quit IRC | 05:25 | |
| *** mickeys has quit IRC | 05:40 | |
| yushiro | reedip, fwaasrouterinsertion is definitely loaded... http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce/logs/devstacklog.txt.gz#_2017-05-22_09_50_04_296 | 06:13 |
| reedip | yushiro : yeah, but I am not sure why its not loading | 06:13 |
| yushiro | yes.. | 06:13 |
| reedip | as in why the tempest tests for routerinsertion are failing | 06:13 |
| yushiro | yes. And, it also fails 'without router insertion' case. | 06:14 |
| reedip | yushiro : does it ????? | 06:14 |
| yushiro | for example | 06:15 |
| yushiro | neutron_fwaas.tests.tempest_plugin.tests.scenario.test_fwaas.TestFWaaS.test_firewall_block_icmp[id-b985d010-994a-4055-bd5c-9e961464ccde](without router insersion) | 06:16 |
| yushiro | http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce/console.html#_2017-05-22_10_23_51_592713 | 06:16 |
| yushiro | result: http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce/console.html#_2017-05-22_10_23_51_633673 | 06:16 |
| reedip | yushiro: but the reason is a bit different | 06:19 |
| reedip | I mean it states that the IP is reachable | 06:19 |
| yushiro | yes, but I'm doubting it affects other scenario tests now. Anyway, I'll focus on routerinsertion first. | 06:20 |
| reedip | thanks yushiro , it would be great help.. :D | 06:25 |
| yushiro | reedip, NP. It's my job ;) | 06:25 |
| yushiro | http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce/logs/screen-q-svc.txt.gz#_May_22_09_47_32_547499 | 06:27 |
| yushiro | fwaasrouterinsertion is definitely perfectly strongly accordingly loaded... | 06:27 |
| reedip | Yes, I checked that | 06:27 |
| yushiro | Do you know where is DB migration log? | 06:28 |
| reedip | DB Migration would be in svc logs only, shouldnt it? | 06:29 |
| reedip | yamamoto : any suggestions ? | 06:30 |
| yushiro | OK, thanks | 06:30 |
| yamamoto | ? | 06:30 |
| reedip | yamamoto : Do you know where is DB migration log? In case of http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce | 06:30 |
| reedip | yamamoto , yushiro : I think its here http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce/logs/devstacklog.txt.gz#_2017-05-22_09_46_05_906 | 06:31 |
| yamamoto | yes | 06:31 |
| reedip | thanks yamamoto | 06:32 |
| yushiro | reedip, yamamoto Thanks. I found following log messages : 4202e3047e47 -> 540142f314f4, FWaaS router insertion | 06:32 |
| reedip | yushiro: yep | 06:33 |
| reedip | yushiro : then there must be some reason why the API is not registering the router_ids as the API extension for fwaas v1 | 06:35 |
| yushiro | Yes, API definition. So, neutron-lib patch for an API definition has been merged in these days, right? | 06:37 |
| reedip | yushiro : yes, it has been merged | 06:40 |
| *** mickeys has joined #openstack-fwaas | 06:41 | |
| reedip | yushiro : something strange here | 06:42 |
| reedip | yushiro: https://review.openstack.org/#/c/389388/28/neutron_lib/api/definitions/firewallrouterinsertion.py | 06:42 |
| reedip | check the alias | 06:42 |
| reedip | thats correct? | 06:42 |
| yushiro | Yes, I found same point. https://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/firewallrouterinsertion.py#L17 | 06:42 |
| yushiro | oh.... | 06:43 |
| yushiro | https://review.openstack.org/#/c/428000/ | 06:44 |
| reedip | yushiro : wait , I remembered: https://review.openstack.org/#/c/434771/ | 06:44 |
| reedip | see boden's comments here | 06:44 |
| *** mickeys has quit IRC | 06:45 | |
| yushiro | I still don't see why this is needed; it's the same thing as RESOURCE_ATTRIBUTE_MAP that's already defined. In the consumption patches, just use RESOURCE_ATTRIBUTE_MAP instead of EXTENDED_ATTRIBUTES_2_0. | 06:45 |
| yushiro | this one? | 06:46 |
| reedip | yushiro : got it, probably | 06:47 |
| reedip | yes... | 06:47 |
| reedip | yushiro : see https://review.openstack.org/#/c/456511/12/neutron_fwaas/extensions/firewallrouterinsertion.py | 06:47 |
| reedip | its returning sub_resource_attribute_map | 06:47 |
| reedip | and not resource_attribute_map | 06:47 |
| reedip | and as per https://review.openstack.org/#/c/434771/7/neutron_lib/api/definitions/firewallrouterinsertion.py , we need to return resource attribute map | 06:48 |
| reedip | the sub resource is empty | 06:48 |
| yushiro | aha! | 06:49 |
| reedip | thanks yushiro, pushed the change, now waiting for the result | 06:50 |
| yushiro | So, we should modify return value of get_extended_resources or .. | 06:50 |
| reedip | but I think we still need to check why the tests "without_router_insertion" are failing | 06:50 |
| yushiro | Yes. Indeed. | 06:50 |
| yushiro | I'm doubting fwaas driver. | 06:50 |
| reedip | which section? | 06:51 |
| reedip | because this is not happening in normal scenarios | 06:52 |
| reedip | therefore would be something else | 06:52 |
| reedip | I mean this doesnt happen in other patches, happens only in this patch | 06:52 |
| yushiro | OK. I just watched WARNING message from q-l3 about driver iptables. | 06:52 |
| yushiro | OK, I'm focus on the patch. | 06:53 |
| reedip | log location ? | 06:53 |
| yushiro | http://logs.openstack.org/11/456511/11/check/gate-neutron-fwaas-v1-dsvm-tempest/8d600ce/logs/screen-q-l3.txt.gz#_May_22_09_47_36_400780 | 06:53 |
| yushiro | This one. But as you said, there is no relation. | 06:54 |
| *** trungnv has quit IRC | 07:00 | |
| *** mickeys has joined #openstack-fwaas | 07:03 | |
| *** trungnv has joined #openstack-fwaas | 07:07 | |
| yushiro | reedip, Could you update your patch and upload? | 07:39 |
| reedip | Updating the patch | 07:39 |
| yushiro | reedip, great. It's better to find issues after updated your patch :) | 07:39 |
| *** mickeys has quit IRC | 08:04 | |
| yushiro | I'll leave my office and online at home. | 08:23 |
| yushiro | patially, bye | 08:23 |
| *** yushiro has quit IRC | 08:23 | |
| *** vcn[m] has quit IRC | 08:46 | |
| *** amotoki has quit IRC | 08:49 | |
| *** amotoki has joined #openstack-fwaas | 08:51 | |
| *** vcn[m] has joined #openstack-fwaas | 08:51 | |
| reedip | Ok | 09:00 |
| *** mickeys has joined #openstack-fwaas | 09:05 | |
| *** mickeys_ has joined #openstack-fwaas | 09:09 | |
| *** mickeys has quit IRC | 09:09 | |
| *** mickeys_ has quit IRC | 09:11 | |
| *** mickeys has joined #openstack-fwaas | 10:12 | |
| *** mickeys has quit IRC | 10:18 | |
| *** hoangcx has quit IRC | 10:54 | |
| *** mickeys has joined #openstack-fwaas | 11:14 | |
| *** yamamoto has quit IRC | 11:17 | |
| *** mickeys has quit IRC | 11:19 | |
| xgerman | Guys, I am on PTO the next two weeks - but will try to move things along ;-) Not sure if I can make the meeting today though -- | 11:19 |
| *** yamamoto has joined #openstack-fwaas | 11:58 | |
| *** yamamoto_ has joined #openstack-fwaas | 12:00 | |
| *** yamamoto has quit IRC | 12:04 | |
| *** vcn[m] has quit IRC | 12:09 | |
| *** mickeys has joined #openstack-fwaas | 12:15 | |
| *** vcn[m] has joined #openstack-fwaas | 12:16 | |
| *** mickeys has quit IRC | 12:19 | |
| *** vks1 has quit IRC | 12:31 | |
| *** mickeys has joined #openstack-fwaas | 13:15 | |
| *** mickeys has quit IRC | 13:20 | |
| *** reedip__ has joined #openstack-fwaas | 13:31 | |
| *** SarathMekala has joined #openstack-fwaas | 13:43 | |
| *** hoangcx has joined #openstack-fwaas | 13:52 | |
| *** hoangcx has quit IRC | 13:54 | |
| *** hoangcx has joined #openstack-fwaas | 13:54 | |
| *** chandanc has joined #openstack-fwaas | 13:55 | |
| reedip__ | xgerman : updated the patch | 13:55 |
| *** vks1 has joined #openstack-fwaas | 13:59 | |
| *** Tim_Eberhard has joined #openstack-fwaas | 14:16 | |
| *** mickeys has joined #openstack-fwaas | 14:16 | |
| *** Tim_Eberhard has quit IRC | 14:17 | |
| *** mickeys has quit IRC | 14:21 | |
| *** yushiro has joined #openstack-fwaas | 15:00 | |
| SarathMekala | hi amotoki | 15:01 |
| yushiro | I'm home. | 15:01 |
| amotoki | SarathMekala: hi | 15:01 |
| *** SridarK_ has joined #openstack-fwaas | 15:01 | |
| SarathMekala | I will give you a heads up on my progress and we can plan the next steps | 15:01 |
| yushiro | vks1, chandanc Hi, let's continue to discuss L2 part. | 15:01 |
| SridarK_ | SarathMekala: sounds good | 15:02 |
| amotoki | SarathMekala: yeah. as my horizon hat, we plan to split FWaaS v1 dashboard in horizon to a newly created repo | 15:02 |
| SarathMekala | yes amotoki | 15:02 |
| yushiro | sounds good | 15:02 |
| SridarK_ | yushiro: i will need to step away shortly but will look at logs and maybe we need to think this thru more | 15:03 |
| SarathMekala | to start with... rob cresswell has advised me to start a new project for fwaas dashboard | 15:03 |
| amotoki | SarathMekala: yes | 15:03 |
| yushiro | SridarK_, Sure. Thanks for your help! | 15:03 |
| SarathMekala | so I have used the cookie cutter plugin and created the folder structure needed | 15:03 |
| amotoki | my plan at now is to create a new repo, move FWaaS v1 panel to a new repo and then add FWaaS v2 support based on your work | 15:03 |
| SridarK_ | the approach of handling this in the plugin could make things similar to L3 | 15:03 |
| amotoki | SarathMekala: so perhaps the works we two have done would conflict :( | 15:04 |
| amotoki | and we need to resolve conflicts | 15:04 |
| yushiro | SridarK_, you mean 'plugin layer' is 'fwaas_plugin_v2.py' ? | 15:04 |
| *** hoangcx has quit IRC | 15:05 | |
| SridarK_ | yushiro: yes that is what vks1 seemed to suggest | 15:05 |
| SarathMekala | yeah amotoki ... there seems to be some overlap | 15:05 |
| SridarK_ | or at least how i understood | 15:05 |
| vks1 | yushiro: yes, I suggested to validate the host bounding in plugin side | 15:05 |
| amotoki | SarathMekala: which one do you want, FWaaS v1 or v2 first? | 15:05 |
| SridarK_ | yushiro: but i would think this would an issue for qos as well with a similar workflow | 15:05 |
| *** chandanc has quit IRC | 15:05 | |
| vks1 | SridarK_: yes you understood correctly :) | 15:05 |
| yushiro | SridarK_, vks1 OK, thanks. However, in plugin layer, we can only trigger fwg CRUD. | 15:06 |
| amotoki | SarathMekala: perhaps Angular stuff requires more dependencies than django one (v1 stuff) | 15:06 |
| SarathMekala | amotoki, can these two projects co-exist | 15:06 |
| *** mickeys has joined #openstack-fwaas | 15:06 | |
| SarathMekala | it may be possible.. and we may need only one repo | 15:06 |
| amotoki | SarathMekala: what do you mean? if you are talking about FWaaS support, it is not a good idea to have two repos for FWaaS | 15:07 |
| yushiro | SridarK_, Yes, QoS works at L2 and service plugin layer I think. | 15:07 |
| vks1 | yushiro: plugin is the only place where you can be sure of this binding | 15:07 |
| amotoki | SarathMekala: do you have any public repo now? | 15:07 |
| SarathMekala | amotoki, i meant one UI plugin project for v1 and v2 dashboards | 15:07 |
| SarathMekala | no | 15:07 |
| SarathMekala | I have v2 code that needs to be pushed to the repo | 15:08 |
| SarathMekala | and thus be reviewed :0 | 15:08 |
| yushiro | vks1, hmm, When creating/updating fwg, we can check binding status to get port DB in plugin layer. | 15:08 |
| amotoki | SarathMekala: perhaps most things do not conflict and you can put a new panel to FWaaS v1 panel | 15:08 |
| yushiro | vks1, I agree with you. | 15:08 |
| amotoki | SarathMekala: what conflicts is just about the common stuff. The directory structure may need to be changed. | 15:09 |
| vks1 | yushiro: if its OK with you , it seems simpler and less buggy | 15:09 |
| yushiro | vks1, However, how should we know in case of VM port creation? | 15:09 |
| SarathMekala | amotoki, yes.. openstack_dashboards/firewalls will be for V1 | 15:09 |
| amotoki | SarathMekala: can you check how you can add your contents to my initial repo based on v1 panel? | 15:10 |
| yushiro | vks1, I think l2-agent extension can only handle port behavior. | 15:10 |
| SarathMekala | and openstack-dashboards/firewalls_v2 will be for V2 | 15:10 |
| amotoki | SarathMekala: I think you can easily check the dir structure of https://github.com/amotoki/neutron-fwaas-dashboard | 15:10 |
| SridarK_ | yushiro: i think we can get a plugin notification as well but need to check but still there could be a timing and we need to validate | 15:10 |
| SarathMekala | ok | 15:10 |
| amotoki | SarathMekala: at now FWaaS v1 panel is placed at https://github.com/amotoki/neutron-fwaas-dashboard/tree/master/neutron_fwaas_dashboard/dashboards/project | 15:11 |
| SridarK_ | but overall if we react to a port create, validate and then push the rules from the plugin that could be cleaner | 15:11 |
| amotoki | but I can move it to dashboards/project/fwaas | 15:11 |
| SridarK_ | we will need db cleanup on the delete workflow as well | 15:11 |
| SridarK_ | but needs some digging | 15:11 |
| vks1 | SridarK_: there is one thing , will it be scalable ? | 15:12 |
| SridarK_ | vks1: i am not really sure | 15:12 |
| vks1 | SridarK_: I aggree we need some digging | 15:12 |
| SridarK_ | vks1: i think in parallel we need to investigate qos - | 15:12 |
| SarathMekala | amotoki, why is the project called as "project"... shouldn't it be firewalls | 15:12 |
| SridarK_ | with the agent ext - there is possibly a mechanism for a specific notification that we can listen on | 15:13 |
| SridarK_ | so we can serialize after the L2 processing | 15:13 |
| SarathMekala | amotoki, if we go with your structure.. V1 and V2 projects will be under these hierarchies | 15:13 |
| SridarK_ | lets look at that too | 15:13 |
| SarathMekala | neutron-fwaas-dashboard/neutron_fwaas_dashboard/dashboards/project/ | 15:13 |
| SarathMekala | ---> V1 | 15:13 |
| SarathMekala | neutron-fwaas-dashboard/neutron_fwaas_dashboard/dashboards/firewalls_v2 ---> V2 | 15:13 |
| amotoki | SarathMekala: it is not a requirement. I assumed we have just 'project' and 'admin' panels when I split out the panel | 15:14 |
| yushiro | SridarK_, vks1 OK, I understood currently. Thanks for your explanation. | 15:14 |
| SridarK_ | vks1: on a orthogonal point - u asked abt heat if i recall correctly - Hemanth in ur org did some extensive work with heat | 15:14 |
| amotoki | SarathMekala: if we have multiple panels, it is reasonable to have multiple dirs under dashboards/project | 15:14 |
| SridarK_ | vks1: may be a good point to start | 15:14 |
| amotoki | SarathMekala: and perhaps it is what we want now. | 15:14 |
| SarathMekala | amotoki, yes | 15:15 |
| SarathMekala | one for V1 and other for V2 | 15:15 |
| vks1 | SridarK_: Yeah hemanth have lead some work there. | 15:15 |
| amotoki | SarathMekala: so neutron_fwaas_dashboard/dashboards/project/{firewalls(_v1),firewalls_v2} sound good to you? | 15:15 |
| SarathMekala | amotoki, yes.. that sounds good | 15:16 |
| yushiro | SridarK_, vks1 so, Should I stop updating current L2-agent patch? | 15:16 |
| amotoki | SarathMekala: thanks | 15:16 |
| vks1 | SridarK_: We have used V1 for our customer :) | 15:16 |
| SridarK_ | yushiro: vks1: I think chandanc logged off - maybe lets start an email discussion with some points raised | 15:17 |
| SarathMekala | amotoki, can you IM me your email.. it will be easy to get in touch with you | 15:17 |
| SridarK_ | and we can do some investigation | 15:17 |
| amotoki | SarathMekala: regarding repo naming, I can easily change it, so it does not matter me. | 15:17 |
| vks1 | yushiro: please don't stop | 15:17 |
| yushiro | SridarK_, vks1 Sure. | 15:17 |
| amotoki | SarathMekala: my email is amotoki@gmail.com | 15:17 |
| SridarK_ | vks1: ok | 15:17 |
| SarathMekala | amotoki, thanks | 15:17 |
| yushiro | OK, all guys start digging in parallel :) | 15:17 |
| SarathMekala | amotoki, will you also create the repo under openstack? | 15:17 |
| amotoki | SarathMekala: sure. I will send a mail to -dev to check our plan. | 15:18 |
| SarathMekala | amotoki, cool.. thanks a lot for your help | 15:18 |
| amotoki | SarathMekala: I would like to clarify the repo will be under the neutron stadium and what launchpad project will be used for bug tracking | 15:19 |
| amotoki | SarathMekala: this is the main goal of my mail tomorrow | 15:19 |
| SarathMekala | sure.. | 15:19 |
| yushiro | SridarK_, vks1 thanks for your help today :) | 15:19 |
| amotoki | SarathMekala: thanks for your work :) | 15:19 |
| SarathMekala | I have created a launchpad project https://launchpad.net/neutron-fwaas-v2-dashboard.. see if it helps.. or you can create your own | 15:20 |
| yushiro | reedip, Hi! | 15:20 |
| SarathMekala | amotoki, thanks.. need to log off now.. will check your mail and get back to you | 15:20 |
| SridarK_ | yushiro: no worries let us continue on email - it is very late for u as well | 15:20 |
| amotoki | SarathMekala: personally I would like to avoid 'v2' :p | 15:20 |
| yushiro | SridarK_, Thank you. But I'm not so sleepy today. Maybe amotoki is too :) | 15:21 |
| amotoki | SarathMekala: perhaps we will have a new repo next week | 15:21 |
| amotoki | yushiro: no. am chatting in bed now | 15:22 |
| amotoki | yushiro: :) | 15:22 |
| yushiro | amotoki, aha :) | 15:22 |
| SridarK_ | :-) | 15:22 |
| *** sarathmekala_ has joined #openstack-fwaas | 15:22 | |
| amotoki | good night all | 15:23 |
| yushiro | night | 15:23 |
| *** SarathMekala has quit IRC | 15:25 | |
| *** yamamoto_ has quit IRC | 15:26 | |
| *** yamamoto has joined #openstack-fwaas | 15:27 | |
| *** Tim_Eberhard has joined #openstack-fwaas | 15:31 | |
| *** yamamoto has quit IRC | 15:32 | |
| SridarK_ | good night | 15:34 |
| *** sarathmekala_ has quit IRC | 15:39 | |
| *** yushiro has quit IRC | 15:40 | |
| *** vks1 has quit IRC | 15:57 | |
| *** reedip__ has quit IRC | 16:19 | |
| *** yamamoto has joined #openstack-fwaas | 16:30 | |
| *** yamamoto has quit IRC | 16:39 | |
| *** SumitNaiksatam has quit IRC | 17:17 | |
| *** SridarK_ has quit IRC | 17:28 | |
| *** SumitNaiksatam has joined #openstack-fwaas | 17:52 | |
| *** SridarK_ has joined #openstack-fwaas | 19:00 | |
| *** mickeys has quit IRC | 19:58 | |
| *** mickeys has joined #openstack-fwaas | 20:59 | |
| *** mickeys has quit IRC | 21:03 | |
| *** mickeys has joined #openstack-fwaas | 21:05 | |
| -openstackstatus- NOTICE: The logserver has filled up, so jobs are currently aborting with POST_FAILURE results; remediation is underway. | 21:20 | |
| *** ChanServ changes topic to "The logserver has filled up, so jobs are currently aborting with POST_FAILURE results; remediation is underway." | 21:20 | |
| *** Tim_Eberhard has quit IRC | 21:58 | |
| *** SridarK_ has quit IRC | 22:10 | |
| *** mickeys has quit IRC | 22:25 | |
| *** Tim_Eberhard has joined #openstack-fwaas | 22:28 | |
| *** mickeys has joined #openstack-fwaas | 22:43 | |
| *** Tim_Eberhard has joined #openstack-fwaas | 22:45 | |
| *** Tim_Eberhard has quit IRC | 22:58 | |
| *** SumitNaiksatam has quit IRC | 23:59 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!