| *** zenoway has joined #openstack-dragonflow | 00:23 | |
| *** zenoway has quit IRC | 00:27 | |
| *** zenoway has joined #openstack-dragonflow | 00:44 | |
| *** gongysh has quit IRC | 00:47 | |
| *** zenoway has quit IRC | 00:49 | |
| *** zenoway has joined #openstack-dragonflow | 01:11 | |
| *** gongysh has joined #openstack-dragonflow | 01:19 | |
| *** zenoway has quit IRC | 01:55 | |
| *** hshan has joined #openstack-dragonflow | 02:27 | |
| *** zenoway has joined #openstack-dragonflow | 02:32 | |
| *** zenoway has quit IRC | 02:37 | |
| *** zenoway has joined #openstack-dragonflow | 02:44 | |
| *** zenoway has quit IRC | 02:48 | |
| *** dingboopt has joined #openstack-dragonflow | 02:49 | |
| openstackgerrit | hujie proposed openstack/dragonflow: add ovsdb monitor fullstack test case https://review.openstack.org/296905 | 03:23 |
|---|---|---|
| openstackgerrit | hujie proposed openstack/dragonflow: add ovsdb monitor fullstack test case https://review.openstack.org/296905 | 03:23 |
| nick-ma | todin: ok. i'm glad it is working for you. | 03:41 |
| *** hujie has joined #openstack-dragonflow | 03:42 | |
| *** oanson has joined #openstack-dragonflow | 04:10 | |
| *** gongysh has quit IRC | 04:38 | |
| *** irenab has quit IRC | 04:45 | |
| *** irenab has joined #openstack-dragonflow | 05:29 | |
| *** gongysh has joined #openstack-dragonflow | 05:40 | |
| gampel | yuanwei: ping hi | 05:49 |
| *** gampel has quit IRC | 06:00 | |
| *** gsagie has quit IRC | 06:01 | |
| *** oanson has quit IRC | 06:01 | |
| *** gsagie has joined #openstack-dragonflow | 06:14 | |
| *** oanson has joined #openstack-dragonflow | 06:15 | |
| *** gampel has joined #openstack-dragonflow | 06:15 | |
| gampel | Frank_Duan: ping | 06:19 |
| *** CrayZee has quit IRC | 06:21 | |
| *** CrayZee has joined #openstack-dragonflow | 06:24 | |
| hshan | oanson: ping | 06:28 |
| oanson | pong | 06:28 |
| oanson | hshan: pong | 06:29 |
| hshan | hi, omer, I want to discuss the comments you gave for me about the "parser.OFPFlowMod(" | 06:29 |
| hshan | do you remember? | 06:29 |
| Frank_Duan | Hi | 06:29 |
| oanson | Yes | 06:30 |
| oanson | You made changes to DFLowApp.mod_flow, to set the aging cookie | 06:30 |
| oanson | If I understand correctly, this cookie has to be set on all flows | 06:31 |
| hshan | I've scanned for all the related code: all of them should be replaced by ryu_base_app.py DFLowApp.mod_flow | 06:31 |
| hshan | yes, it's should be set on all flows | 06:31 |
| oanson | Yes | 06:31 |
| oanson | You are correct. All flow modifications should be done with DFlowApp.mod_flow | 06:31 |
| hshan | but arp_responder.py is a exception, which is not subclass of DFlowApp | 06:32 |
| hshan | so arp_responder.py has to do it itself | 06:32 |
| oanson | I see the problem. It still needs to set the cookie | 06:32 |
| hshan | I think it should be solved in another patch, what's your opinion? | 06:33 |
| oanson | That would break reliability functionality. | 06:34 |
| hshan | yes, it is the basis of reliability | 06:34 |
| oanson | It means arp-responder related flows may be removed when they shouldn't be, since the cookie is always 0 | 06:34 |
| hshan | yes, you're right | 06:34 |
| hshan | but if I put the modification in reliability patch, that will make the reliability patch too big, | 06:35 |
| oanson | But you can call set_aging_cookie_bits in ArpResponder. | 06:35 |
| oanson | The same way you do in mod_flow | 06:35 |
| hshan | I agree | 06:35 |
| oanson | This way, it only adds 3-4 lines. That's not too bad. | 06:35 |
| hshan | but I have to modify all other apps except ArpResponder to use mod_flow, do you understand me? | 06:36 |
| oanson | Yes. | 06:36 |
| hshan | the modification file list will be very long | 06:37 |
| oanson | But I am afraid that without it, the controller may become unstable. | 06:37 |
| oanson | You can first add a patch for all apps to use mod_flow, and on top of that the reliability patch | 06:37 |
| oanson | You are correct, It is probably better that way | 06:37 |
| hshan | yes, that's just what I plan | 06:37 |
| oanson | That's a good idea. | 06:38 |
| hshan | okay, I'll do it this way:) | 06:38 |
| hshan | another topic | 06:38 |
| oanson | Great. Thanks! | 06:38 |
| oanson | Sure | 06:38 |
| hshan | when will you hand the "switch_features_handler" to ovsdb_monitor? | 06:39 |
| hshan | that's the basics of reliability too. | 06:39 |
| openstackgerrit | Li Ma proposed openstack/dragonflow: Fix port update event loss https://review.openstack.org/303284 | 06:42 |
| oanson | You need switch_features_handler to start the OVSDB monitor. Am I right? | 06:43 |
| hshan | no, it's not needed now | 06:44 |
| oanson | In any case, this event should already be provided. | 06:44 |
| *** yuli_s has joined #openstack-dragonflow | 06:44 | |
| yuli_s | hello | 06:44 |
| oanson | apps can implement switch_features_handler, and then they get that event | 06:45 |
| yuli_s | dingboopt, I was checking the sg patch yesterday. | 06:45 |
| hshan | oanson: it's not true | 06:45 |
| yuli_s | i had 2 bugs | 06:45 |
| hshan | let me explain it for you | 06:45 |
| yuli_s | https://bugs.launchpad.net/dragonflow/+bug/1568498 | 06:46 |
| openstack | Launchpad bug 1568498 in DragonFlow "sg test bug 1" [High,New] | 06:46 |
| yuli_s | https://bugs.launchpad.net/dragonflow/+bug/1568506 | 06:46 |
| openstack | Launchpad bug 1568506 in DragonFlow "sg test bug 2" [Undecided,New] | 06:46 |
| dingboopt | Ok | 06:46 |
| dingboopt | I will take a look at them. thanks | 06:46 |
| hshan | the current implementation of ovsdb_monitor got a little different from former implementation by hujie | 06:46 |
| yuli_s | i am running stack now | 06:47 |
| yuli_s | and will try to reproduce these errors | 06:47 |
| oanson | hshan: I see | 06:47 |
| hshan | hujie's version do all the jobs in a new green thread, the openflow got a thread, dragonflow(processing the event queue) got a thread | 06:48 |
| hshan | so we have to synchronize between the 3 threads | 06:48 |
| hshan | we must to make sure openflow is ready first, so the datapath is ready for apps to flush flow | 06:49 |
| hshan | then the ovsdb_monitor could do it's job | 06:49 |
| hshan | but in current implementation: ovsdb_monitor runs in the same thread with dragonflow, am I right? | 06:50 |
| oanson | hshan, ovsdb monitor has its own thread. In OvsdbSwitchApi calling self.ovsdb.start() starts a new thread | 06:51 |
| hshan | i don't mean that | 06:52 |
| oanson | So OVSDB gets its event from the self.ovsdb thread. It then sends the event to the queue, processed by the controller thread | 06:52 |
| hshan | yes | 06:53 |
| oanson | I don't understand the problem | 06:53 |
| hshan | I mean ovsdb monitor send the 'sync_started', 'vm port online event' 'sync_finished' to event queue is in the same thread with dragonflow, right? | 06:53 |
| oanson | Yes | 06:54 |
| oanson | And the the DF controller processes all these events when it gets control back | 06:54 |
| hshan | okay, so when openflow.start() is blocked by wait_until_ready, 'sync_started', 'vm port online event' 'sync_finished' are blocked too | 06:55 |
| hshan | so we don't need ryu_base_app's switch_features_handler to start ovsdb_monitor now | 06:55 |
| hshan | it's needed in hujie's implementation | 06:56 |
| hshan | do you agree with it? | 06:56 |
| oanson | Yes. | 06:56 |
| hshan | okay, here we just need to move 'switch_features_handler ' from switch_features_handler to ovsdb_monitor | 06:57 |
| hshan | ovsdb_monitor doesn't need to make any modification, because we can handle it in ryu_base_app when we read the 'sync_start' from event queue | 06:58 |
| hshan | we could first send 'sync_start' to apps, then send 'switch_features_handler' to apps | 06:59 |
| hshan | oanson: are you there? | 07:00 |
| oanson | hshan, yes. 1 sec | 07:01 |
| hshan | ok | 07:01 |
| oanson | I don't think the OVSDB monitor supports the features handler. | 07:02 |
| oanson | It is a response to a features request made by ryu | 07:02 |
| oanson | I don't understand why it has to be moved? | 07:02 |
| *** saggi has joined #openstack-dragonflow | 07:02 | |
| hshan | it's for reliability feature consideration | 07:03 |
| hshan | too | 07:03 |
| hshan | so let me ask you a question, what do apps use 'switch_features_handler ' for? | 07:04 |
| hshan | it's for apps to send framework flows, right? | 07:04 |
| oanson | I think that for startup. But that was before sync_started/sync_finished were created | 07:04 |
| hshan | that' why we need to move it | 07:05 |
| oanson | We may need to move from switch_handler to sync_finished, but no this version | 07:05 |
| hshan | all flows should be flushed after sync_started | 07:05 |
| oanson | In fact I'd go as far as saying that we can do without the switch_handler event entirely. Only use sync_started. | 07:06 |
| hshan | you mean we can remove " switch_handler event " totally ? | 07:07 |
| oanson | yes. | 07:07 |
| oanson | But I think it's too risky for this version. | 07:07 |
| hshan | so, when will apps send framework flows? | 07:07 |
| oanson | We are in feature freeze, with code freeze next week | 07:07 |
| oanson | Right now, in switch_handler. But like you said, it may be better in sync_started/sync_finished. | 07:08 |
| oanson | I think gampel and gsagie should give their opinion too on this, since it might be a big change. | 07:08 |
| hshan | yes, it's just a time point | 07:08 |
| hshan | sorry, the code is freeze now, and that will last to the end of next week, right? | 07:09 |
| oanson | Hopefully, only till next Monday. | 07:10 |
| hshan | okay, i got that | 07:10 |
| hshan | the reason I talk about that is: it's the basic of reliability feature | 07:11 |
| hshan | we've tested that locally, everything work fine, maybe you could test it too after moving 'switch_features_handler ' | 07:13 |
| oanson | Sure. I can test it. | 07:14 |
| oanson | Can you upload the new code for review? Then I can take it from there. | 07:14 |
| hshan | okay, i'll add that part of code back | 07:15 |
| hshan | I think we'll be more confidence about the moving when you tested it:) | 07:15 |
| oanson | :) | 07:16 |
| hshan | another topic: i fixed a bug in 'dragonflow/tests/common/utils.py', and you gave a comments 'I should modify the test code that use table_id', you remember that | 07:17 |
| oanson | Yes. I remember | 07:18 |
| oanson | This is a bug. The table now looks like '9,' instead of '9' | 07:18 |
| hshan | yes | 07:19 |
| hshan | i'll evaluate it, if the modification is not very big, I'll do it in the patch, or I'll add a new patch including 'bug fix and fullstack testcases for reliability feature' | 07:19 |
| oanson | I have to go for a sec. I'll be back soon | 07:19 |
| hshan | see you | 07:19 |
| hshan | gsagie: ping | 07:26 |
| oanson | hshan: I'm back. Sorry | 07:27 |
| oanson | hshan: That's a good idea. It would be better if the table was a number, and not a number + a comma :) | 07:28 |
| hshan | pretty good | 07:28 |
| hshan | I'll add a new patch for bug-fix and fullstack of reliability features | 07:29 |
| oanson | Great. Thanks! | 07:31 |
| hshan | oanson: thank you very much, that's all I want to make sure with you | 07:31 |
| hshan | I'll add the code back as soon as possible | 07:31 |
| oanson | hshan: No problem | 07:31 |
| openstackgerrit | hujie proposed openstack/dragonflow: Fix unnecessary IDL run invoke bug https://review.openstack.org/303934 | 07:35 |
| openstackgerrit | hujie proposed openstack/dragonflow: Fix unnecessary IDL run invoke bug https://review.openstack.org/303934 | 07:38 |
| openstackgerrit | hujie proposed openstack/dragonflow: Fix unnecessary IDL run invoke bug https://review.openstack.org/303934 | 07:43 |
| yuli_s | dingboopt, i think i understand the bug better now | 07:52 |
| yuli_s | in df-df | 07:52 |
| yuli_s | Key = ea1ac88f-7c25-477c-83a7-0cd53ff992d5 , Value = {"parent_name": null, "macs": ["fa:16:3e:ca:8e:d1"], "name": "ea1ac88f-7c25-477c-83a7-0cd53ff992d5", "chassis": "ubuntu", "lswitch": "315ed568-4533-4f85-af13-a73a588af3de", "enabled": true, "topic": "c1487fc89cbe4e169329b25c9eb9ecfb", "ips": ["10.0.0.3", "fd42:8ae4:15ec:0:f816:3eff:feca:8ed1"], "device_owner": "compute:nova", "port_security": ["fa:16:3e:ca:8e:d1"], "sg | 07:52 |
| yuli_s | ids": ["41d2f9d1-4111-487f-a8da-73ea385386ac"], "tunnel_key": 6, "external_ids": {"neutron:port_name": ""}, "tag": null, "security_groups": ["40d413ff-126e-4ca7-aeec-d81cba15a953"]} | 07:52 |
| yuli_s | this is a port of the vm | 07:53 |
| yuli_s | it has 2 security group fields ! | 07:53 |
| yuli_s | one is sgids and another one is security_groups | 07:54 |
| yuli_s | both have different values ! | 07:55 |
| yuli_s | "sgids": ["41d2f9d1-4111-487f-a8da-73ea385386ac"] | 07:55 |
| yuli_s | "security_groups": ["40d413ff-126e-4ca7-aeec-d81cba15a953"] | 07:55 |
| yuli_s | one point to default security group | 07:55 |
| yuli_s | another point to the security group I created | 07:55 |
| openstackgerrit | ding bo proposed openstack/dragonflow: This patch implements security group app https://review.openstack.org/280538 | 08:16 |
| *** raofei has joined #openstack-dragonflow | 08:22 | |
| *** yamamoto has joined #openstack-dragonflow | 08:24 | |
| oanson | yuli_s, ping | 08:27 |
| yuli_s | oanson, yes | 08:31 |
| openstackgerrit | heshan proposed openstack/dragonflow: code for local controller reliability https://review.openstack.org/292060 | 08:36 |
| *** zenoway has joined #openstack-dragonflow | 08:44 | |
| *** Shlomo_N has joined #openstack-dragonflow | 08:48 | |
| openstackgerrit | hujie proposed openstack/dragonflow: add ovsdb monitor fullstack test case https://review.openstack.org/296905 | 08:59 |
| oanson | Hi | 09:02 |
| oanson | We're starting the meeting in #openstack-meeting-4 | 09:02 |
| oanson | Please join. | 09:02 |
| nick-ma | ok | 09:03 |
| *** liuhaixia has joined #openstack-dragonflow | 09:09 | |
| *** Mic22 has joined #openstack-dragonflow | 09:11 | |
| *** yuanwei has joined #openstack-dragonflow | 09:13 | |
| liuhaixia | hi,gal, good morning. I have question about when to create bridge 'br-int'. With pure neutorn, ovs-agent response for create bridge 'br-int'. | 09:32 |
| gsagie | hi | 09:33 |
| liuhaixia | With dragonflow, /dragonflow/devstack/plugin.sh create 'br-int'. | 09:33 |
| gsagie | liuhaixia: its currently created by our devstack script i believe | 09:33 |
| gsagie | but if needed you can move it to the df code | 09:33 |
| liuhaixia | I see it. | 09:33 |
| liuhaixia | oh, this is what I want to know. | 09:34 |
| liuhaixia | Do you have plan to move it to code? | 09:34 |
| liuhaixia | Because in HWS Cloud, we need df code to do this. | 09:35 |
| liuhaixia | I think if we do not use devstack to install openstack, we also need to create 'br-int' manually or by scripts. | 09:38 |
| liuhaixia | Sorry, you mean I can move it to code:) | 09:39 |
| liuhaixia | I know, thanks. | 09:39 |
| *** feipeng has joined #openstack-dragonflow | 09:46 | |
| *** Frank_Duan has quit IRC | 10:06 | |
| openstackgerrit | Li Ma proposed openstack/dragonflow: Fix port update event loss https://review.openstack.org/303284 | 10:38 |
| openstackgerrit | heshan proposed openstack/dragonflow: add check_controller() and set_controller_fail_mode() to vswitch_api https://review.openstack.org/292060 | 10:40 |
| openstackgerrit | Li Ma proposed openstack/dragonflow: Fix port update event loss https://review.openstack.org/303284 | 10:43 |
| openstackgerrit | heshan proposed openstack/dragonflow: code for local controller reliability https://review.openstack.org/292060 | 10:43 |
| openstackgerrit | heshan proposed openstack/dragonflow: add check_controller() and set_controller_fail_mode() to vswitch_api https://review.openstack.org/304026 | 10:51 |
| *** zenoway has quit IRC | 11:16 | |
| *** zenoway has joined #openstack-dragonflow | 11:19 | |
| *** mastermind has joined #openstack-dragonflow | 11:21 | |
| openstackgerrit | heshan proposed openstack/dragonflow: change dragonflow apps to use mod_flow instead of ryu's OFPFlowMod https://review.openstack.org/304050 | 11:23 |
| *** zenoway has quit IRC | 11:23 | |
| *** Shlomo_N has quit IRC | 11:25 | |
| *** mastermind has quit IRC | 11:26 | |
| openstackgerrit | heshan proposed openstack/dragonflow: change dragonflow apps to use mod_flow instead of ryu's OFPFlowMod https://review.openstack.org/304050 | 11:26 |
| *** yamamoto has quit IRC | 11:46 | |
| *** zenoway has joined #openstack-dragonflow | 11:52 | |
| openstackgerrit | heshan proposed openstack/dragonflow: code for local controller reliability https://review.openstack.org/292060 | 11:56 |
| *** zenoway has quit IRC | 12:01 | |
| gsagie | All our friends in China, any of you is coming to OpenStack Austin summit by any chance? | 12:08 |
| *** gongysh has quit IRC | 12:09 | |
| *** zenoway has joined #openstack-dragonflow | 12:19 | |
| *** yamamoto has joined #openstack-dragonflow | 12:22 | |
| hshan | oanson: ping | 12:22 |
| oanson | pong | 12:22 |
| oanson | hshan, pong | 12:23 |
| hshan | I encounter a problem when I make set_controller and set_fail_mode through idl, I guess it's caused by the filter | 12:23 |
| hshan | I add the related rows to ovsdb_monitor_table_filter_default, but it doesn't work | 12:24 |
| hshan | I think you must know how to do it | 12:25 |
| hshan | I interested in 'controller' and 'fail_mode' row under 'Bridge' table | 12:25 |
| oanson | 1 sec. I will look at the code | 12:29 |
| hshan | oanson: do you hear me? | 12:29 |
| hshan | okay | 12:29 |
| openstackgerrit | Eran Gampel proposed openstack/dragonflow: Mitaka Version Features Update https://review.openstack.org/303825 | 12:30 |
| oanson | Did you add 'Controller' with 'target' field to ovsdb_monitor_table_filter_default? In addition, did you add the fields 'controller' and 'fail_mode' in 'Bridge' table to ovsdb_monitor_table_filter_default? | 12:31 |
| hshan | 'Did you add 'Controller' with 'target' field to ovsdb_monitor_table_filter_default?' how? | 12:33 |
| hshan | I did the second job | 12:33 |
| oanson | add to ovsdb_monitor_table_filter_default the key: 'Controller': ['target'] | 12:34 |
| oanson | You need to have the 'Controller' table added, otherwise it won't be in the idl. | 12:34 |
| hshan | let me try it | 12:35 |
| hshan | job done! thank you very much! | 12:37 |
| oanson | No problem :) | 12:38 |
| liuhaixia | Help. Does anybody have the problem when run 'tox -e fullstack'? | 12:40 |
| liuhaixia | Three of my colleagues have meet the problem since this week. | 12:41 |
| liuhaixia | The error 'No local packages or download links found for pbr>=1.8' | 12:41 |
| oanson | Can you please run 'pip show pbr'? | 12:43 |
| liuhaixia | It works fine. | 12:43 |
| liuhaixia | Name: pbr | 12:44 |
| liuhaixia | Version: 1.8.1 | 12:44 |
| liuhaixia | Version: 1.8.1 | 12:44 |
| oanson | Could you try again, after running '. .tox/fullstack/bin/activate'? | 12:44 |
| oanson | (run 'deactivate' when finished to leave the virtualenv') | 12:44 |
| liuhaixia | (fullstack) stack@PEK1000047303:~/dragonflow$ pip show pbr | 12:45 |
| *** gongysh has joined #openstack-dragonflow | 12:46 | |
| openstackgerrit | heshan proposed openstack/dragonflow: add check_controller() and set_controller_fail_mode() to vswitch_api https://review.openstack.org/304026 | 12:46 |
| liuhaixia | It seems not work fine. | 12:47 |
| oanson | What's the output? | 12:47 |
| liuhaixia | An HTTPS request has been made | 12:48 |
| liuhaixia | .tox/fullstack/lib/python2.7/pip/_vendor/requests/packages/urllib3/util/ssl_.py:315 | 12:48 |
| liuhaixia | SNIMissingWarning: An HTTPS request has been made, but the SNI | 12:48 |
| liuhaixia | (Subject Name Indication) extension to TLS is not available on this platform. | 12:48 |
| liuhaixia | It looks like SSL issue. | 12:49 |
| oanson | Yes | 12:50 |
| oanson | Do you get a pip version error? | 12:50 |
| oanson | Something like: | 12:50 |
| oanson | You are using pip version 8.0.2, however version 8.1.1 is available. | 12:50 |
| oanson | You should consider upgrading via the 'pip install --upgrade pip' command. | 12:50 |
| liuhaixia | No | 12:50 |
| liuhaixia | It does not have version error. | 12:51 |
| *** zenoway has quit IRC | 12:51 | |
| oanson | I am not familiar with this issue. I will have to search it. | 12:51 |
| liuhaixia | Thank you, I will try also. | 12:52 |
| hshan | gsagie, oanson: the splitting of reliability is ready, details please see email | 12:59 |
| hshan | if you got any problems please email me, see you | 13:00 |
| *** zenoway has joined #openstack-dragonflow | 13:05 | |
| gsagie | hshan: can you please send me which patch to try and test | 13:06 |
| gsagie | which is highest in the hierarchy? | 13:06 |
| gsagie | hshan: ? | 13:08 |
| openstackgerrit | Eran Gampel proposed openstack/dragonflow: Mitaka Version Features Update https://review.openstack.org/303825 | 13:12 |
| *** zenoway has quit IRC | 13:18 | |
| openstackgerrit | Omer Anson proposed openstack/dragonflow: Lookup router_port's network_id with lswitch's topic https://review.openstack.org/298121 | 13:26 |
| *** oanson has quit IRC | 13:31 | |
| *** zenoway has joined #openstack-dragonflow | 13:33 | |
| *** irenab has quit IRC | 13:41 | |
| *** zenoway has quit IRC | 13:41 | |
| *** zenoway has joined #openstack-dragonflow | 13:55 | |
| *** zenoway has quit IRC | 14:04 | |
| *** yamamoto has quit IRC | 14:06 | |
| *** zenoway has joined #openstack-dragonflow | 14:09 | |
| openstackgerrit | Yuli proposed openstack/dragonflow: Fix empty ofport value Closes-bug: #1568506 https://review.openstack.org/304152 | 14:09 |
| openstack | bug 1568506 in DragonFlow "sg test bug 2" [High,New] https://launchpad.net/bugs/1568506 - Assigned to Omer Anson (omer-anson) | 14:09 |
| *** yamamoto has joined #openstack-dragonflow | 14:10 | |
| *** zenoway has quit IRC | 14:13 | |
| openstackgerrit | Yuli proposed openstack/dragonflow: Fix empty ofport value https://review.openstack.org/304152 | 14:16 |
| *** yuli_s has quit IRC | 14:20 | |
| *** zenoway has joined #openstack-dragonflow | 14:27 | |
| openstackgerrit | yuan wei proposed openstack/dragonflow: Impliment security group fullstack and ut cases https://review.openstack.org/299105 | 14:28 |
| *** zenoway has quit IRC | 14:32 | |
| *** zenoway has joined #openstack-dragonflow | 14:41 | |
| *** zenoway has quit IRC | 14:45 | |
| *** yamamoto has quit IRC | 14:51 | |
| *** openstackgerrit has quit IRC | 15:18 | |
| *** openstackgerrit has joined #openstack-dragonflow | 15:18 | |
| *** yamamoto has joined #openstack-dragonflow | 15:21 | |
| *** yamamoto has quit IRC | 15:27 | |
| *** zenoway has joined #openstack-dragonflow | 15:31 | |
| *** zenoway has quit IRC | 15:35 | |
| *** yamamoto has joined #openstack-dragonflow | 15:42 | |
| *** yamamoto has quit IRC | 15:52 | |
| *** gongysh has quit IRC | 16:18 | |
| openstackgerrit | Merged openstack/dragonflow: Send Chassis update on SEND_ALL topic https://review.openstack.org/302601 | 16:29 |
| *** yamamoto has joined #openstack-dragonflow | 16:52 | |
| *** yamamoto has quit IRC | 17:00 | |
| *** oanson has joined #openstack-dragonflow | 17:42 | |
| *** openstackgerrit has quit IRC | 20:05 | |
| *** zenoway has joined #openstack-dragonflow | 20:25 | |
| *** openstackgerrit has joined #openstack-dragonflow | 20:28 | |
| *** zenoway has quit IRC | 20:28 | |
| *** zenoway has joined #openstack-dragonflow | 20:29 | |
| *** openstackgerrit has quit IRC | 20:41 | |
| *** openstackgerrit has joined #openstack-dragonflow | 20:55 | |
| *** oanson has quit IRC | 21:32 | |
| *** zenoway has quit IRC | 21:39 | |
| *** zenoway has joined #openstack-dragonflow | 21:41 | |
| *** zenoway has joined #openstack-dragonflow | 21:43 | |
| *** zenoway has quit IRC | 21:43 | |
| *** zenoway has joined #openstack-dragonflow | 21:45 | |
| *** zenoway has quit IRC | 21:45 | |
| *** zenoway has joined #openstack-dragonflow | 21:46 | |
| *** zenoway has joined #openstack-dragonflow | 22:03 | |
| *** zenoway has quit IRC | 22:06 | |
| *** zenoway has joined #openstack-dragonflow | 22:08 | |
| *** zenoway has quit IRC | 22:08 | |
| *** zenoway has joined #openstack-dragonflow | 22:10 | |
| *** zenoway has quit IRC | 22:11 | |
| *** zenoway has joined #openstack-dragonflow | 22:12 | |
| *** zenoway has quit IRC | 22:13 | |
| *** zenoway has joined #openstack-dragonflow | 22:15 | |
| *** zenoway has quit IRC | 22:15 | |
| *** zenoway has joined #openstack-dragonflow | 22:16 | |
| *** zenoway has quit IRC | 22:16 | |
| *** zenoway has joined #openstack-dragonflow | 22:18 | |
| *** zenoway has quit IRC | 22:18 | |
| *** zenoway has joined #openstack-dragonflow | 22:21 | |
| *** zenoway has quit IRC | 22:27 | |
| *** zenoway has joined #openstack-dragonflow | 22:29 | |
| *** zenoway has quit IRC | 22:29 | |
| *** zenoway has joined #openstack-dragonflow | 22:32 | |
| *** zenoway has quit IRC | 23:15 | |
| *** saggi has quit IRC | 23:26 | |
| *** gampel has quit IRC | 23:26 | |
| *** gsagie has quit IRC | 23:27 | |
| *** gsagie has joined #openstack-dragonflow | 23:40 | |
| *** saggi has joined #openstack-dragonflow | 23:40 | |
| *** gampel has joined #openstack-dragonflow | 23:41 | |
| *** zenoway has joined #openstack-dragonflow | 23:45 | |
| *** zenoway has quit IRC | 23:49 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!