| *** yamamoto_ has joined #openstack-fwaas | 02:09 | |
| *** yamamot__ has joined #openstack-fwaas | 04:20 | |
| *** mfranc213 has quit IRC | 04:20 | |
| *** mfranc213 has joined #openstack-fwaas | 04:21 | |
| *** yamamoto_ has quit IRC | 04:21 | |
| *** lnicolas has quit IRC | 04:59 | |
| *** yamamot__ has quit IRC | 05:07 | |
| *** yamamoto_ has joined #openstack-fwaas | 05:07 | |
| openstackgerrit | Reedip proposed openstack/neutron-fwaas master: Improve test cases for distributed routers https://review.openstack.org/501567 | 05:10 |
|---|---|---|
| reedip | xgerman_ ping | 05:17 |
| openstackgerrit | Reedip proposed openstack/neutron-fwaas master: Improve test cases for distributed routers https://review.openstack.org/501567 | 05:25 |
| reedip | yamamoto_ : u there? | 05:33 |
| yamamoto_ | ? | 05:33 |
| reedip | Hi | 05:33 |
| reedip | yamamoto_ : Currently fwaas is not linked directly with neutron , IIUC | 05:34 |
| reedip | yamamoto_ : is there a way to verify that if there is a change in neutron, we can map it onto fwaas as well ? I mean if there is a change in neutron's code, but the same change has not occurred in fwaas, then notification ( like a test failure ) should be generated | 05:35 |
| *** yushiro has joined #openstack-fwaas | 05:35 | |
| openstackgerrit | Reedip proposed openstack/neutron-fwaas master: Update DVR condition in FWaaS https://review.openstack.org/501570 | 05:39 |
| amotoki | reedip: what would you really like to do? do you want to test if fwaas works fine using some neutron side change ? | 05:40 |
| reedip | amotoki : yes | 05:40 |
| amotoki | reedip: simply Depends-On | 05:40 |
| amotoki | reedip: you can send a test patch to neutron-fwaas with a proper Depends-On | 05:41 |
| reedip | amotoki : umm , thats true, but not what I wanted to know. | 05:41 |
| amotoki | reedip: so perhaps i don't understand what you want correctly | 05:41 |
| reedip | amotoki : just a minute | 05:42 |
| reedip | amotoki : like 3162846a7b42d860533df6dc32d9c553669df45b changed | 05:42 |
| reedip | in neutron, but fwaas which uses similar code didnt know about it. I think the best way to handle such things is with functional testing or fullstack testing | 05:43 |
| reedip | amotoki : but still need your opinion | 05:43 |
| reedip | amotoki : bug 1715395 was raised yesterday because Commit ID: # 3162846a7b42d860533df6dc32d9c553669df45b which changed in neutron was not reflected in fwaas | 05:44 |
| openstack | bug 1715395 in neutron "FWaaS: Firewall creation fails in case of distributed routers (Pike)" [High,In progress] https://launchpad.net/bugs/1715395 - Assigned to Reedip (reedip-banerjee) | 05:44 |
| amotoki | reedip: it depends on cases. does fwaas impl depend on the internal details of l3-agent or non-well-defined methods | 05:46 |
| amotoki | ? | 05:46 |
| reedip | amotoki : loosly dependent but yes dependent | 05:46 |
| amotoki | if so, this kind of things cannot be avoided theoretically, and we need to explore what is more modular appraoch | 05:47 |
| reedip | amotoki : ok, I think improving the secnarios might be the best way forward, atleast having Fullstack tests | 05:47 |
| amotoki | this needs a feedback from out-of-tree users like fwaas | 05:47 |
| reedip | ok | 05:47 |
| amotoki | we are in the early stage of a dev cycle, and it is nice to have this kind of thing now :) | 05:48 |
| reedip | amotoki : I think a similar approach was used by boden for migration of neutron stuff to neutron-lib and he raised emails to all consumers. I think such a model works atleast to a good degree | 05:49 |
| amotoki | reedip: yes, in neutron-lib case, we confidently know we break the current interface and recommend to use new interfaces | 05:50 |
| amotoki | reedip: but this case is a bit different. we were not aware of breaking something AND did not think it is a public interface change | 05:50 |
| amotoki | reedip: we thought it was just an usual neutron-internal change | 05:51 |
| reedip | amotoki : yes, I agree with that. The issue is that neutron change didnot consider that someone else would be using the attributes of the object directly | 05:51 |
| amotoki | reedip: it is what we have now, but it is not a good thing to access internals | 05:52 |
| reedip | amotoki: so this bug is valid, but to prevent future issues, atleast to a certain degree, some method can be found. Obviously neutron cannot announce all its changes to out-of-tree consumers | 05:52 |
| amotoki | reedip: so the stadium health scorecard has this entry N3 http://specs.openstack.org/openstack/neutron-specs/specs/stadium/ocata/neutron-fwaas.html#n3 | 05:54 |
| reedip | checkin | 05:57 |
| reedip | amotoki : ok ... | 06:09 |
| yamamoto_ | reedip: you can review every neutron patches and put -1 for breaking ones. :-) | 06:18 |
| reedip | yamamoto_ : thats a great idea :D | 06:18 |
| *** eezhova has joined #openstack-fwaas | 06:49 | |
| *** yushiro has quit IRC | 06:56 | |
| *** eezhova has quit IRC | 07:45 | |
| *** eezhova has joined #openstack-fwaas | 08:09 | |
| *** yamamoto_ has quit IRC | 09:28 | |
| reedip | amotoki : there? | 09:42 |
| *** yamamoto has joined #openstack-fwaas | 09:46 | |
| *** yamamoto has quit IRC | 10:14 | |
| *** yamamoto has joined #openstack-fwaas | 10:19 | |
| openstackgerrit | Reedip proposed openstack/neutron-fwaas master: Update fwaas configuration for user-defined L3 Agents https://review.openstack.org/501663 | 10:19 |
| amotoki | reedip: what? | 10:42 |
| reedip | amotoki : never mind, resolved the isue, thanks :) | 10:43 |
| *** reedip is now known as reed_afk | 10:53 | |
| *** reed_afk is now known as reedip_afk | 10:53 | |
| openstackgerrit | Inessa Vasilevskaya proposed openstack/neutron-fwaas master: Generate default firewall group via project https://review.openstack.org/425769 | 11:55 |
| *** eezhova_ has joined #openstack-fwaas | 12:12 | |
| *** eezhova has quit IRC | 12:15 | |
| openstackgerrit | Édouard Thuleau proposed openstack/neutron-fwaas master: Implements a plugable backend driver https://review.openstack.org/480265 | 13:35 |
| *** eezhova_ has quit IRC | 13:44 | |
| *** eezhova has joined #openstack-fwaas | 14:25 | |
| xgerman_ | reedip what’s up>? | 14:30 |
| *** eezhova has quit IRC | 15:05 | |
| *** lnicolas has joined #openstack-fwaas | 15:09 | |
| *** reedip has joined #openstack-fwaas | 15:33 | |
| reedip | 0/ | 15:38 |
| openstackgerrit | Reedip proposed openstack/neutron-fwaas master: Update DVR condition in FWaaS https://review.openstack.org/501570 | 15:40 |
| openstackgerrit | Édouard Thuleau proposed openstack/neutron-fwaas master: Implements a plugable backend driver https://review.openstack.org/480265 | 15:41 |
| reedip | hi doude : fixed the conflicts? | 15:45 |
| *** reedip is now known as outofmemory | 15:59 | |
| doude | yes reedip_afk | 16:06 |
| doude | but I was not able to run tempest on my devstack. I don't understand why but the scenario fails here https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/tests/tempest_plugin/tests/scenario/test_fwaas_v2.py#L217 | 16:07 |
| *** mwynne has joined #openstack-fwaas | 16:08 | |
| doude | effectively, the VM cannot be reach through its floating IP | 16:08 |
| doude | I check and the VM receive correctly ICMP request and send a ack (I see that on the VM tap), but the icmp ack is lost somewhere in the OVS mess (qbr, qvo...) | 16:09 |
| doude | I set up a classic devstack install | 16:10 |
| doude | I'll see if CI fails | 16:10 |
| *** eezhova has joined #openstack-fwaas | 16:19 | |
| outofmemory | doude : no issues, I will also pull it up tomorrow :) ( reedip here ) | 16:36 |
| doude | it seems the gate dsvm-tempest succeed with the last patch set | 16:37 |
| doude | I mean gate-neutron-fwaas-v2-dsvm-tempest gate, the v1 not yet finished | 16:38 |
| doude | and v2 multinode also succeed | 16:38 |
| outofmemory | good :) | 16:52 |
| *** eezhova has quit IRC | 16:55 | |
| *** outofmemory has quit IRC | 17:08 | |
| *** SumitNaiksatam has joined #openstack-fwaas | 17:19 | |
| doude | all green | 17:36 |
| *** eezhova has joined #openstack-fwaas | 18:54 | |
| *** eezhova has quit IRC | 18:55 | |
| *** SumitNaiksatam has quit IRC | 19:10 | |
| *** eezhova has joined #openstack-fwaas | 19:24 | |
| *** eezhova has quit IRC | 19:56 | |
| *** eezhova has joined #openstack-fwaas | 20:03 | |
| *** eezhova has quit IRC | 21:19 | |
| *** yushiro has joined #openstack-fwaas | 23:39 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!