| *** limao has joined #openstack-kuryr | 00:30 | |
| *** limao_ has joined #openstack-kuryr | 00:34 | |
| *** limao has quit IRC | 00:37 | |
| *** limao_ has quit IRC | 01:12 | |
| *** limao has joined #openstack-kuryr | 01:14 | |
| *** shashank_hegde has quit IRC | 01:15 | |
| *** salv-orlando has joined #openstack-kuryr | 01:18 | |
| *** hongbin has joined #openstack-kuryr | 01:23 | |
| *** salv-orlando has quit IRC | 01:25 | |
| *** hongbin has quit IRC | 01:29 | |
| *** banix has joined #openstack-kuryr | 01:35 | |
| *** hongbin has joined #openstack-kuryr | 02:20 | |
| *** salv-orlando has joined #openstack-kuryr | 02:49 | |
| *** salv-orlando has quit IRC | 02:54 | |
| *** yamamoto_ has joined #openstack-kuryr | 03:02 | |
| *** hongbin has quit IRC | 03:09 | |
| *** shashank_hegde has joined #openstack-kuryr | 03:41 | |
| *** shashank_hegde has quit IRC | 03:49 | |
| *** yamamoto_ has quit IRC | 03:54 | |
| *** salv-orlando has joined #openstack-kuryr | 04:00 | |
| *** huikang has joined #openstack-kuryr | 04:03 | |
| *** salv-orlando has quit IRC | 04:14 | |
| *** shashank_hegde has joined #openstack-kuryr | 04:20 | |
| *** limao has quit IRC | 04:28 | |
| *** janonymous has joined #openstack-kuryr | 04:30 | |
| *** vikasc has joined #openstack-kuryr | 04:31 | |
| vikasc | gsagie, ping | 04:33 |
|---|---|---|
| *** diga has joined #openstack-kuryr | 04:33 | |
| vikasc | banix, hi | 04:34 |
| banix | VikasC: hi | 04:34 |
| vikasc | banix, I updated test cases and fixed fullstack as per your suggestion :) | 04:35 |
| vikasc | banix, https://review.openstack.org/#/c/331050/ | 04:35 |
| banix | VikasC: yes noticed it; had a quick look, it looks good. will review more carefully tomorrow (thursday) | 04:35 |
| vikasc | banix, sure | 04:35 |
| banix | VikasC: thanks for working on it | 04:36 |
| *** huikang has quit IRC | 04:36 | |
| vikasc | banix, my pleasure | 04:36 |
| vikasc | banix, now i have started working on nested vm | 04:36 |
| banix | VikasC: containers in VMs? | 04:36 |
| *** huikang has joined #openstack-kuryr | 04:36 | |
| vikasc | banix, yes | 04:36 |
| banix | cool | 04:36 |
| vikasc | banix, I feel our current 'Kuryr' code should be rename as "kuryr-driver" | 04:37 |
| vikasc | or something similar | 04:37 |
| vikasc | banix, and parallel to it one more common kuryr-api should be written | 04:38 |
| vikasc | banix, kuryr-api will be responsible for talking to other openstack services | 04:39 |
| banix | well, Kuryr seems to be expanding to cover a few things beyond the libnetwork driver which means what you suggest makes sense | 04:39 |
| vikasc | banix, kuryr-drivers will talk to kuryr api | 04:39 |
| vikasc | banix, kuryr apis will be generic | 04:39 |
| vikasc | banix, kuryr-driver part will have seperate support directories like driver-libnetwork, driver-k8s etc | 04:40 |
| banix | well we are having a separate repo for k8s | 04:41 |
| *** huikang has quit IRC | 04:41 | |
| vikasc | banix, makes sense... libnetwork-driver part got to kuryr libnetwork and similarly k8s driver to kuryr-k8s | 04:41 |
| vikasc | banix, common library , kuryr-api will remain in our current Kuryr | 04:42 |
| vikasc | banix, makes sense? | 04:42 |
| banix | yes thats where we are going; may need to be revised as we go forward | 04:42 |
| vikasc | thanks banix , wanted to just confirm | 04:43 |
| vikasc | :) | 04:43 |
| banix | great; ttyl | 04:44 |
| vikasc | banix, bye | 04:44 |
| *** yamamoto_ has joined #openstack-kuryr | 04:45 | |
| *** salv-orlando has joined #openstack-kuryr | 04:50 | |
| *** banix has quit IRC | 04:52 | |
| *** limao has joined #openstack-kuryr | 04:55 | |
| *** reedip has quit IRC | 04:58 | |
| *** salv-orl_ has joined #openstack-kuryr | 04:59 | |
| *** salv-orlando has quit IRC | 05:02 | |
| *** tfukushima has joined #openstack-kuryr | 05:16 | |
| vikasc | tfukushima, ping | 05:29 |
| vikasc | irenab, ping | 05:31 |
| irenab | vikasc: hi | 05:31 |
| vikasc | irenab, Hi, should not this "doc/specs/mitaka" directory be renamed to "specs/newton" now? | 05:31 |
| vikasc | irenab, wanted to discuss before raising a bug | 05:31 |
| irenab | let me check what is there inside | 05:32 |
| vikasc | irenab, or the ones completed can be there and a new directory , newton can be created for active specs? | 05:32 |
| irenab | I think you are right, but lets check how they do it in neutron. I beleive there is some sort of approved sub folder | 05:32 |
| *** shashank_hegde has quit IRC | 05:34 | |
| irenab | Iactually, its in nova. there is approved and implemented sub folders | 05:35 |
| irenab | But I think renaming to newton will be good enough | 05:35 |
| vikasc | yeah, in neutron there is no release-wise folder | 05:35 |
| vikasc | yes, because all are being implemented in newton | 05:35 |
| irenab | its nice in nova: https://github.com/openstack/nova-specs/tree/master/specs/newton | 05:35 |
| *** diga has quit IRC | 05:36 | |
| irenab | but we do not have too many specs right now, so I guess moving these specs to newton is fine | 05:36 |
| vikasc | irenab, makes sense. | 05:36 |
| vikasc | irenab, I will also open a bug you brought up in last meeting regarding neutron restart | 05:37 |
| vikasc | irenab, just to keep track | 05:37 |
| irenab | vikasc: thanks, it wa still on my todo list -) | 05:37 |
| vikasc | irenab, shall i do it? | 05:38 |
| *** shashank_hegde has joined #openstack-kuryr | 05:38 | |
| irenab | vikasc: I think we should consider cases where neutron is restarted or maybe even upgraded or reconfigured to keep it in sync with kuryr | 05:38 |
| vikasc | irenab, valid point | 05:38 |
| irenab | vikasc: I do not mind, either way. I can do it now before being distructed by other tasks :-) | 05:39 |
| vikasc | irenab, please go ahead :) | 05:39 |
| vikasc | vikasc, i will take care of renaming task | 05:40 |
| vikasc | irenab, nested-vm spec is too abstract | 05:40 |
| irenab | vikasc: I agree | 05:41 |
| vikasc | irenab, documentation on seperation of project into common kuryr library and other COE specific drivers is also not there | 05:41 |
| irenab | I think adding devref for more detailed implementation details will be very helpful | 05:41 |
| vikasc | irenab, should we enhance nested-vm spec or several small small devrefrences will be better | 05:42 |
| irenab | vikasc: do you think documentation is required? I thought we can have launchpad bp for this | 05:42 |
| irenab | for code split | 05:42 |
| irenab | vikasc: I do not have preference, I think maybe both … | 05:43 |
| irenab | clarify the spec + adding devref for more design/implementation details | 05:43 |
| vikasc | irenab, ok... will add to todo-list | 05:44 |
| irenab | :-) | 05:44 |
| vikasc | irenab, thanks :) | 05:44 |
| vikasc | irenab, Can you please review this one, https://review.openstack.org/#/c/328656/ its a very minor doc change | 05:45 |
| vikasc | irenab, its been there since long | 05:45 |
| irenab | vikasc: sure, after the bug report …. | 05:46 |
| vikasc | irenab, Also if you get timewould appreciate review comments on "short-term fix for overlapping", https://review.openstack.org/#/c/331050/ | 05:46 |
| irenab | adding to my todo list :-) | 05:47 |
| irenab | vikasc: https://bugs.launchpad.net/kuryr/+bug/1595399 | 05:48 |
| openstack | Launchpad bug 1595399 in kuryr "kuryr does not support neutron server reconnect" [Undecided,New] | 05:48 |
| vikasc | irenab, thanks | 05:50 |
| vikasc | irenab, I could not find any bp for refactoring. Can you please share link? | 05:51 |
| irenab | I think it was discussed that there is no such. Can you please create one, or coordinate with gsagie ? | 05:51 |
| vikasc | irenab, Closest one is this by fawad mentioning kuryr agent and kuryr server, https://blueprints.launchpad.net/kuryr/+spec/kuryr-agent | 05:51 |
| vikasc | irenab, you already mailed, so i expect he would reply | 05:52 |
| irenab | vikasc: I think the code split is unrelated, it is needed for k8s/libnetwork as well | 05:52 |
| vikasc | irenab, as per my current understanding, Kuryr server will be this common library which will reside with current Kuryr project | 05:53 |
| vikasc | irenab, agents will be specific to each coe like libnetwork/k8s and will be maintained in seperate repos like kuryr-libnetwork and kuryr-k8s | 05:54 |
| vikasc | irenab, am i saying wrong something | 05:54 |
| vikasc | irenab, so it seems to me that fawad bp covers Kuryr(common library/server) and kuryr-libnetwork(agent) part | 05:56 |
| vikasc | irenab, though enough details are missing | 05:56 |
| irenab | vikasc: I beleive that code split is not only about server/agent reorg. We need also common kuryr part to be shared between libnetwork/k8s integration. Please try to rreach gsagie to coordinate the work. If you create launchpad bp, you can put your ideas in the whileboard section there | 05:58 |
| vikasc | irenab, ok so i am going to create a bp for code refactoring | 05:58 |
| vikasc | irenab, im my understanding , "Kuryr common part" is being refered to as Kuryr server only. This server is different from remote driver server listening for libnetwork api calls | 06:00 |
| vikasc | irenab, I will add details on bp | 06:01 |
| vikasc | irenab, we can discuss there. Thanks for the time :) | 06:01 |
| irenab | vikasc: welcome, have a great day | 06:02 |
| *** oshidoshi has joined #openstack-kuryr | 06:05 | |
| gsagie | hi vikasc | 06:06 |
| vikasc | hi gsagie | 06:07 |
| gsagie | I havent started working on the split part, so if you would like to do it feel free | 06:07 |
| gsagie | and let me know how i can help | 06:07 |
| vikasc | gsagie, ok.. so i was just drafting a bp for refactoring but before that i would like to confirm very briefly my understanding | 06:07 |
| gsagie | i will start reading the channel buffer :) | 06:07 |
| vikasc | gsagie, that will be great | 06:08 |
| vikasc | gsagie, whatever i was just discussing with irenab , please share your view on that | 06:08 |
| vikasc | gsagie, I am waiting | 06:08 |
| gsagie | ok | 06:11 |
| gsagie | so yes. we have 2 repos already for libnetwork specific integration and k8s | 06:11 |
| gsagie | the common lib should have the "controller" part with the binding for example and the part that speak with Neutron probably | 06:11 |
| vikasc | gsagie, yes and this will be like common kuryr server running on cluster controller node, serving requests from kuryrs agents running inside vms | 06:12 |
| vikasc | gsagie, is this correct? | 06:13 |
| gsagie | vikasc: not sure what you mean server/agent | 06:13 |
| gsagie | if you mean the nested containers/kubernetes integration | 06:13 |
| gsagie | thats something else i think | 06:13 |
| gsagie | for example the code in libnetwork repo should still call the Neutron API, same implementation we have today for Neutron | 06:14 |
| gsagie | but code wise, the libnetwork driver and IPAM should be inside libnetwork driver, the controller binding part should be in Kuryr as a library that the libnetwork code use | 06:14 |
| gsagie | to communicate with Neutron | 06:14 |
| gsagie | i think something along these lines, but thats what i had in mind, happy to hear if anyone had anything else in mind | 06:14 |
| vikasc | i have a little different than this in my mind | 06:15 |
| vikasc | gsagie, would appreciate if you have time and patience to understand my view point :) | 06:16 |
| gsagie | of course | 06:16 |
| vikasc | gsagie, I was thinking like this | 06:16 |
| vikasc | gsagie, kuryr-libnetwork or kuryr-k8s will have code talking to conatiner run-time and will talk on the other side to kuryr controller only | 06:18 |
| vikasc | kuryr repo will have code for kuryr controller | 06:18 |
| vikasc | Kuryr controller will be like kuryr-api, talking to other services on behalf of kuryr-k8s or kuryr-libnetwork | 06:19 |
| vikasc | kuryr controller will talk to neutron to get plumbing done on nova nodes and will allocate and pass per-container tag to kuryr-libnetwork/kuryr-k8s running on vm. | 06:21 |
| vikasc | gsagie, am i making a bit sense :) ? | 06:21 |
| vikasc | gsagie, kuryr-libnet/kuryr-k8s running inside vm will configure let say local ovs for tagging container traffic | 06:22 |
| gsagie | sec reading :) | 06:24 |
| vikasc | gsagie, to tag container traffic kuryr-libnet/k8s will configure ovs running inside vm using tags received from kuryr-controller running on cluster controller node | 06:24 |
| gsagie | vikasc: you are making sense, however if we take the examples we have right now, the libnetwork implementation you will need to write a new mechanism to sync between the "agents" and the controller | 06:25 |
| gsagie | or the one that is calling Neutron | 06:25 |
| gsagie | and you will have to define an API to do so | 06:25 |
| gsagie | or a message patterns | 06:25 |
| vikasc | gsagie, true.. APIs would be my preference and "agent" will actually be a client | 06:26 |
| vikasc | gsagie, kuryr-libnet/k8s will be client to kuryr controller to get things done | 06:27 |
| vikasc | gsagie, so whatever kuryr controller will think that client needs such as IP of vif will be passed to client and if something is to configured such as untagging part on compute, that controller can get done by talking to neutron | 06:28 |
| vikasc | gsagie, so these "clients" kuryr-k8s or kuryr-libnetwork will work as drivers for native docker but client for kuryr controller and not talking to any other openstack service | 06:29 |
| gsagie | vikasc: i will have to think about it, it sounds like a good direction overall, the thing i am not sure about is the communication channel between the "client" and controller, for example in Kubernetes plan the CNI driver is just doing binding and talking | 06:29 |
| gsagie | with Kubernetes master maybe over the kubernetes API | 06:29 |
| vikasc | gsagie, cant it be rest calls | 06:29 |
| gsagie | and the "controller" is basically a watcher on the API of the Kube master | 06:30 |
| gsagie | so there is not required to be any communication between the agent/client and Kuryr controller/watcher | 06:30 |
| vikasc | gsagie, but our approach should be working for other coes also such as swarm | 06:31 |
| gsagie | i think that by doing what you propose we are locked to a certain way of implementing things | 06:31 |
| gsagie | vikasc: yes, i agree that doing something like that make sense for Swarm | 06:31 |
| gsagie | i think it make sense for the nested VMs case | 06:31 |
| vikasc | gsagie, yes | 06:31 |
| gsagie | but again make sense for libnetwork/Swarm | 06:32 |
| gsagie | less for Kubernetes | 06:32 |
| vikasc | gsagie, i thought of all this while splitting tasks for nested vm, | 06:32 |
| gsagie | vikasc: yeah i can see where you coming from :) i do want us to reuse as much as possible so its good thinking | 06:32 |
| vikasc | gsagie, :D | 06:32 |
| gsagie | i would raise this in the mailing list | 06:32 |
| gsagie | or maybe in the next IRC meeting | 06:33 |
| vikasc | gsagie, thanks.. i think you can better present my thinking | 06:33 |
| vikasc | :) | 06:33 |
| gsagie | np, i will send the email today | 06:33 |
| vikasc | gsagie, shall i open a bp for refactoring also | 06:33 |
| gsagie | vikasc: yep | 06:33 |
| vikasc | with current thoughts. ok | 06:34 |
| vikasc | gsagie, thanks Gal | 06:34 |
| gsagie | thank you vikasc :) | 06:34 |
| *** irenab has quit IRC | 06:58 | |
| vikasc | gsagie, we can have config options in controller. If controllerd configured for k8s it will use api watcher patch otherwise handling rest cases. | 07:00 |
| *** irenab has joined #openstack-kuryr | 07:00 | |
| vikasc | gsagie, s/patch/path | 07:01 |
| *** irenab has quit IRC | 07:01 | |
| openstackgerrit | Merged openstack/kuryr: Fix .rst format in kuryr_k8s_integration.rst https://review.openstack.org/328656 | 07:03 |
| *** irenab has joined #openstack-kuryr | 07:08 | |
| *** irenab has quit IRC | 07:09 | |
| *** irenab has joined #openstack-kuryr | 07:09 | |
| vikasc | gsagie, controller may futher have k8s-controller(api-watcher), libnetwork-controller and so on | 07:14 |
| vikasc | gsagie, to me k8s-integration is one specific case of nested vm. | 07:15 |
| *** irenab has quit IRC | 07:17 | |
| *** salv-orl_ has quit IRC | 07:18 | |
| *** irenab has joined #openstack-kuryr | 07:38 | |
| *** limao_ has joined #openstack-kuryr | 07:41 | |
| *** limao has quit IRC | 07:44 | |
| apuimedo | I just got headache reading so many early morning messages :P | 07:59 |
| apuimedo | gsagie: vikasc: I think taking this discussion to the mailing list would be the best | 08:00 |
| *** salv-orlando has joined #openstack-kuryr | 08:05 | |
| *** diga has joined #openstack-kuryr | 08:15 | |
| vikasc | apuimedo, :) , gsagie would initiating a thread on ml | 08:26 |
| *** shashank_hegde has quit IRC | 08:29 | |
| *** irenab_ has joined #openstack-kuryr | 08:29 | |
| *** irenab has quit IRC | 08:30 | |
| *** irenab_ is now known as irenab | 08:30 | |
| *** irenab has quit IRC | 08:40 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr: Updated from global requirements https://review.openstack.org/332304 | 08:41 |
| openstackgerrit | vikas choudhary proposed openstack/kuryr: Rename spec directory to newton https://review.openstack.org/333185 | 08:47 |
| *** salv-orlando has quit IRC | 08:49 | |
| *** salv-orlando has joined #openstack-kuryr | 08:50 | |
| *** salv-orlando has quit IRC | 08:55 | |
| *** vikasc has quit IRC | 08:59 | |
| *** vikasc has joined #openstack-kuryr | 09:12 | |
| apuimedo | cool | 09:13 |
| *** neiljerram has joined #openstack-kuryr | 09:14 | |
| *** irenab has joined #openstack-kuryr | 09:20 | |
| openstackgerrit | Merged openstack/kuryr: Rename spec directory to newton https://review.openstack.org/333185 | 09:36 |
| *** salv-orlando has joined #openstack-kuryr | 09:42 | |
| *** limao_ has quit IRC | 10:06 | |
| openstackgerrit | vikas choudhary proposed openstack/kuryr: Short-Term fix for overlapping cidrs using docker options https://review.openstack.org/331050 | 10:36 |
| *** salv-orl_ has joined #openstack-kuryr | 10:58 | |
| *** salv-orlando has quit IRC | 11:01 | |
| *** salv-orl_ has quit IRC | 11:53 | |
| *** banix has joined #openstack-kuryr | 11:56 | |
| *** vikasc has quit IRC | 11:59 | |
| openstackgerrit | Peter V. Saveliev proposed openstack/kuryr: contrib/vagrant: fix env vars type conversion https://review.openstack.org/333295 | 11:59 |
| *** diga has quit IRC | 12:06 | |
| *** yamamoto_ has quit IRC | 12:41 | |
| *** banix has quit IRC | 12:44 | |
| *** salv-orlando has joined #openstack-kuryr | 12:47 | |
| *** janonymous has quit IRC | 12:51 | |
| *** lezbar__ has joined #openstack-kuryr | 13:08 | |
| *** lezbar has quit IRC | 13:12 | |
| *** salv-orlando has quit IRC | 13:40 | |
| *** salv-orlando has joined #openstack-kuryr | 13:41 | |
| *** huikang has joined #openstack-kuryr | 13:50 | |
| *** huikang has quit IRC | 13:51 | |
| *** huikang has joined #openstack-kuryr | 13:51 | |
| *** huikang has quit IRC | 13:54 | |
| *** huikang has joined #openstack-kuryr | 13:55 | |
| *** diga has joined #openstack-kuryr | 13:57 | |
| *** huikang has quit IRC | 14:09 | |
| *** diga has quit IRC | 14:12 | |
| *** huikang has joined #openstack-kuryr | 14:12 | |
| *** kfox1111 is now known as kfox1111_away | 14:17 | |
| *** salv-orlando has quit IRC | 14:35 | |
| *** salv-orlando has joined #openstack-kuryr | 14:36 | |
| *** yamamoto has joined #openstack-kuryr | 14:59 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr: Updated from global requirements https://review.openstack.org/332304 | 15:32 |
| *** salv-orlando has quit IRC | 15:33 | |
| *** huikang has quit IRC | 15:48 | |
| *** oshidoshi has quit IRC | 15:49 | |
| *** diga has joined #openstack-kuryr | 15:58 | |
| *** diogogmt has joined #openstack-kuryr | 16:03 | |
| *** tfukushima has quit IRC | 16:05 | |
| *** huikang has joined #openstack-kuryr | 16:29 | |
| *** huikang has quit IRC | 16:34 | |
| *** shashank_hegde has joined #openstack-kuryr | 17:11 | |
| *** huikang has joined #openstack-kuryr | 17:19 | |
| *** shashank_hegde has quit IRC | 17:26 | |
| *** huikang has quit IRC | 17:35 | |
| *** salv-orlando has joined #openstack-kuryr | 17:42 | |
| *** salv-orl_ has joined #openstack-kuryr | 17:49 | |
| *** salv-orlando has quit IRC | 17:49 | |
| *** shashank_hegde has joined #openstack-kuryr | 17:51 | |
| openstackgerrit | Mohammad Banikazemi proposed openstack/kuryr: Waiting for Neutron port to become ACTIVE https://review.openstack.org/319484 | 18:22 |
| *** yamamoto has quit IRC | 18:22 | |
| *** yamamoto has joined #openstack-kuryr | 18:22 | |
| *** salv-orl_ has quit IRC | 18:28 | |
| *** yamamoto has quit IRC | 18:30 | |
| *** salv-orlando has joined #openstack-kuryr | 18:36 | |
| *** huikang has joined #openstack-kuryr | 18:36 | |
| *** huikang has quit IRC | 18:41 | |
| *** huikang has joined #openstack-kuryr | 18:48 | |
| *** huikang has quit IRC | 18:49 | |
| *** hongbin has joined #openstack-kuryr | 18:51 | |
| *** huikang has joined #openstack-kuryr | 19:05 | |
| *** salv-orlando has quit IRC | 19:30 | |
| *** yamamoto has joined #openstack-kuryr | 19:30 | |
| *** yamamoto has quit IRC | 19:40 | |
| *** salv-orlando has joined #openstack-kuryr | 19:52 | |
| *** banix has joined #openstack-kuryr | 20:13 | |
| *** huikang has quit IRC | 20:16 | |
| openstackgerrit | Mohammad Banikazemi proposed openstack/kuryr: Waiting for Neutron port to become ACTIVE https://review.openstack.org/319484 | 20:17 |
| *** huikang has joined #openstack-kuryr | 20:24 | |
| *** huats has quit IRC | 20:27 | |
| *** huats has joined #openstack-kuryr | 20:27 | |
| *** huikang has quit IRC | 20:28 | |
| *** fkautz has quit IRC | 20:30 | |
| *** fkautz has joined #openstack-kuryr | 20:42 | |
| *** diga has quit IRC | 20:55 | |
| *** huikang has joined #openstack-kuryr | 21:18 | |
| *** irenab has quit IRC | 21:19 | |
| *** huikang has quit IRC | 21:24 | |
| *** huikang has joined #openstack-kuryr | 21:40 | |
| *** irenab has joined #openstack-kuryr | 21:41 | |
| *** ivc_ has joined #openstack-kuryr | 22:03 | |
| *** huikang has quit IRC | 22:05 | |
| *** ivc_ has quit IRC | 22:06 | |
| *** limao has joined #openstack-kuryr | 22:28 | |
| *** diogogmt has quit IRC | 22:33 | |
| *** diogogmt has joined #openstack-kuryr | 22:44 | |
| *** dingboopt has joined #openstack-kuryr | 22:46 | |
| *** salv-orl_ has joined #openstack-kuryr | 22:59 | |
| *** salv-orlando has quit IRC | 23:02 | |
| *** limao_ has joined #openstack-kuryr | 23:13 | |
| *** hongbin has quit IRC | 23:21 | |
| *** limao_ has quit IRC | 23:23 | |
| *** banix has quit IRC | 23:32 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!