| *** hongbin has quit IRC | 00:12 | |
| *** mattmceuen has joined #openstack-kuryr | 00:44 | |
| *** yedongcan1 has joined #openstack-kuryr | 01:10 | |
| *** limao has joined #openstack-kuryr | 01:17 | |
| *** salv-orlando has joined #openstack-kuryr | 01:22 | |
| *** tonanhngo has quit IRC | 01:25 | |
| *** salv-orlando has quit IRC | 01:27 | |
| *** pmannidi has quit IRC | 01:27 | |
| *** pmannidi has joined #openstack-kuryr | 01:29 | |
| *** tonanhngo has joined #openstack-kuryr | 01:33 | |
| *** mattmceuen has quit IRC | 01:34 | |
| *** tonanhngo has quit IRC | 01:37 | |
| vikas_ | ivc_, ping | 02:47 |
|---|---|---|
| *** hongbin has joined #openstack-kuryr | 02:54 | |
| *** salv-orlando has joined #openstack-kuryr | 03:23 | |
| *** salv-orlando has quit IRC | 03:28 | |
| *** janki has joined #openstack-kuryr | 03:53 | |
| openstackgerrit | vikas choudhary proposed openstack/kuryr-kubernetes: Add support for nested pods with Vlan trunk port https://review.openstack.org/410578 | 05:01 |
| *** hongbin has quit IRC | 05:48 | |
| openstackgerrit | Merged openstack/kuryr-libnetwork: Updated from global requirements https://review.openstack.org/419932 | 06:15 |
| *** ivc_ has quit IRC | 06:28 | |
| *** tonanhngo has joined #openstack-kuryr | 06:52 | |
| *** saneax-_-|AFK is now known as saneax | 07:00 | |
| *** salv-orlando has joined #openstack-kuryr | 07:12 | |
| *** salv-orlando has quit IRC | 07:17 | |
| *** salv-orlando has joined #openstack-kuryr | 07:45 | |
| *** pmannidi has quit IRC | 07:53 | |
| *** salv-orlando has quit IRC | 07:53 | |
| apuimedo | limao: congratulations on you becoming a core ;-) | 07:58 |
| limao | apuimedo: Thanks team! | 07:58 |
| apuimedo | irenab: Do you agree with sending the virtual gathering etherpad to the mailing list already? | 07:59 |
| irenab | apuimedo: give me a min to recheck, but generally yes | 07:59 |
| apuimedo | ok | 07:59 |
| *** yamamoto has quit IRC | 08:17 | |
| openstackgerrit | vikas choudhary proposed openstack/kuryr-kubernetes: Add support for nested pods with Vlan trunk port https://review.openstack.org/410578 | 08:19 |
| vikas_ | apuimedo, irenab ltomasbo PTAL ^ | 08:20 |
| ltomasbo | vikas_, ok, I'll do asap | 08:20 |
| vikas_ | ltomasbo, thanks | 08:20 |
| irenab | apuimedo: I think the agendais good. Wonder if there is nothing for libnetwork or the lib | 08:26 |
| *** salv-orlando has joined #openstack-kuryr | 08:37 | |
| openstackgerrit | Zhang Ni proposed openstack/fuxi: Enable Fuxi to use Manila share https://review.openstack.org/375452 | 08:37 |
| irenab | vikas_: ping | 08:42 |
| vikas_ | irenab, hi | 08:42 |
| irenab | vikas_: I am checking the latest patchset and wonder about the vlan allocation logic | 08:43 |
| vikas_ | irenab, ok.. which part is bothering you | 08:43 |
| irenab | I know it was discussed yesterday, but still not sure why its required to rebuild the allocated vlans map every time subport is created | 08:44 |
| vikas_ | irenab, this will be needed in a/a HA | 08:44 |
| irenab | vikas_: can you elaborate? | 08:44 |
| vikas_ | irenab, let say there are two kuryr-controllers and both gets pod request at same time | 08:44 |
| irenab | vikas_: hereyou have the reties to help | 08:45 |
| irenab | retries | 08:45 |
| vikas_ | irenab, and both has seg_driver of their own, let say they got allocated same vlan_ids | 08:45 |
| vikas_ | irenab, yes | 08:45 |
| vikas_ | irenab, now one of the pods will succeed and other will fail | 08:46 |
| vikas_ | irenab, in that case retry will happen and allocated vlan_id will be retrieved from neutron | 08:46 |
| vikas_ | irenab, and this time seg_driver will not allocate this vlan_id | 08:46 |
| vikas_ | irenab, does this make sense | 08:47 |
| irenab | vikas_ its very not intuitive | 08:47 |
| vikas_ | irenab, which part should i try explaining again | 08:47 |
| irenab | vikas_: I got your explanation, but I mean from the code it does not seem intuitive | 08:48 |
| irenab | I guess woth ports preallocated in advance, we may get into similar issues once consider A:A | 08:49 |
| vikas_ | irenab, got your point | 08:51 |
| ltomasbo | vikas_, irenab: whould it make sense to also change seg_driver so that the vlan_ids return are not in order but somehow random within the available set? | 08:51 |
| ltomasbo | that way we may avoid a few collisions | 08:52 |
| ltomasbo | such as in the example vikas_ described about A:A | 08:52 |
| vikas_ | ltomasbo, IMO, yes that should also be done | 08:52 |
| irenab | vikas_: for now we probably need to have comment on this (better devref), but I think we should have it obvious in the code | 08:52 |
| irenab | ltomasbo: vikas_ :yes random seems as improval | 08:53 |
| vikas_ | irenab, should i add comments in the code for explanations? | 08:53 |
| irenab | vikas_: maybe docstring for the add_subport, and better namings for the inner methods following ltomasbo comment | 08:54 |
| apuimedo | irenab: waiting for somebody to propose libnetwork related stuff :P | 08:54 |
| vikas_ | irenab, cool, going to update | 08:54 |
| ltomasbo | I'm by the way working on a patch to make neutron allocate the vlan_ids if they are not provided by, in our case, kuryr | 08:54 |
| apuimedo | \o/ | 08:55 |
| *** tonanhngo has quit IRC | 08:55 | |
| vikas_ | ltomasbo, cool | 08:55 |
| ltomasbo | which will remove (hopefully) all the mess from kuryr level | 08:55 |
| irenab | apuimedo: or maybe its just in a good shape, perfect as there is nothing to add :-) | 08:55 |
| ltomasbo | but I'm getting some weird behavior, not sure if related to trunk ports or kuryr yet | 08:56 |
| apuimedo | irenab: there's nothing to add, but there's stuff to remove | 08:56 |
| apuimedo | ltomasbo: please describe it | 08:56 |
| irenab | apuimedo: :-) | 08:56 |
| ltomasbo | as even though the vlan driver and id are properly chosen at neutron level (if not passed from kuryr) | 08:56 |
| ltomasbo | sometimes the nested container get connectivity, other times not | 08:56 |
| irenab | ltomasbo: if we want to support Ocata, it will have to manage seg. ids | 08:57 |
| ltomasbo | irenab, kuryr or neutron? | 08:57 |
| *** garyloug has joined #openstack-kuryr | 08:57 | |
| irenab | ltomasbo: kuryr | 08:57 |
| vikas_ | if kuryr wants to support neutron ocata release | 08:58 |
| irenab | assuming neutron seg. ids management enters in Pike | 08:58 |
| apuimedo | irenab: ocata is not frozen yet | 08:58 |
| apuimedo | there's a slim chance | 08:58 |
| ltomasbo | the patch I'm preparing is to remove the need for vlan_ids to be specify, but you can of course specify them if you want | 08:58 |
| apuimedo | irenab: ltomasbo's patch is compliant with the spec, so it seems like it could be accepted | 08:58 |
| ltomasbo | so, the logic is the next -> if you request a subport_add with seg_type and id, then it uses that one (could fail if already taken) | 08:59 |
| irenab | apuimedo: ltomasbo vikas_ : I think we should have kuryr seg_ids specify as optional toggled by config setting | 08:59 |
| vikas_ | irenab, +1 | 08:59 |
| ltomasbo | and if you don't specify seg_type, it chooses vlan by default, and if you don't speficy seg_id it chooses on available for you | 08:59 |
| irenab | ltomasbo: this makes sense. Its the same way as provider networks work | 09:00 |
| apuimedo | irenab: vikas_: I prefer it as exception handling | 09:00 |
| apuimedo | the exception should allow us to differentiate if none are available or we requested with 'wrong' parameters | 09:00 |
| vikas_ | apuimedo, make sense | 09:01 |
| irenab | apuimedo: it seems less ‘managed’ approach, but I I do not have strong objection | 09:01 |
| ltomasbo | apuimedo, I think irenab meant that we can make kuryr either to handle its own seg_ids or allow neutron manage them for us, but one way or the other could be enabled at kuryr based on config, am I right irenab? | 09:02 |
| irenab | ltomasbo: yes, exactly | 09:02 |
| irenab | with reasonable defaults | 09:03 |
| *** yamamoto has joined #openstack-kuryr | 09:07 | |
| *** salv-orlando has quit IRC | 09:21 | |
| *** limao has quit IRC | 09:25 | |
| *** limao has joined #openstack-kuryr | 09:26 | |
| *** limao has quit IRC | 09:30 | |
| openstackgerrit | vikas choudhary proposed openstack/kuryr-kubernetes: Add support for nested pods with Vlan trunk port https://review.openstack.org/410578 | 09:31 |
| vikas_ | ltomasbo, irenab ^ | 09:34 |
| *** yamamoto has quit IRC | 09:34 | |
| *** yamamoto has joined #openstack-kuryr | 09:36 | |
| ltomasbo | vikas_, ok | 09:37 |
| *** devvesa has joined #openstack-kuryr | 09:38 | |
| *** yamamoto has quit IRC | 09:39 | |
| *** pcaruana has joined #openstack-kuryr | 09:41 | |
| irenab | vikas_: posted few questions | 09:47 |
| *** neiljerram has joined #openstack-kuryr | 10:04 | |
| openstackgerrit | Antoni Segura Puimedon proposed openstack/kuryr-kubernetes: vif: avoid exceptions for non exceptional cases https://review.openstack.org/421777 | 10:06 |
| apuimedo | irenab: vikas_: ltomasbo: small patch to improve handling of common cases ^^ | 10:07 |
| irenab | apuimedo: ack | 10:07 |
| vikas_ | apuimedo, sure | 10:07 |
| openstackgerrit | Antoni Segura Puimedon proposed openstack/kuryr-kubernetes: vif: avoid exceptions for non exceptional cases https://review.openstack.org/421777 | 10:11 |
| apuimedo | vikas_: irenab: I simplified it | 10:11 |
| apuimedo | a bit more | 10:11 |
| *** garyloug has quit IRC | 10:17 | |
| *** garyloug has joined #openstack-kuryr | 10:18 | |
| *** garyloug has quit IRC | 10:19 | |
| openstackgerrit | vikas choudhary proposed openstack/kuryr-kubernetes: Add support for nested pods with Vlan trunk port https://review.openstack.org/410578 | 10:19 |
| *** garyloug has joined #openstack-kuryr | 10:19 | |
| vikas_ | irenab, ltomasbo :) | 10:19 |
| irenab | vikas_: ack | 10:19 |
| vikas_ | apuimedo, ^ | 10:21 |
| apuimedo | I'm wondering if to do the same for _get_vif | 10:22 |
| apuimedo | since it is pretty common not to have a vif annotation | 10:22 |
| *** devvesa has quit IRC | 10:24 | |
| irenab | apuimedo: pointer to the place you wonder about? | 10:26 |
| irenab | vikas_: looks good, some more suggestions posted | 10:26 |
| apuimedo | https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/handlers/vif.py#L116-L120 | 10:26 |
| apuimedo | it's not such a clear cut case like the one before, where the exception raising was gratuitous | 10:27 |
| openstackgerrit | Dongcan Ye proposed openstack/kuryr-libnetwork: Optimize add subnetpool tag https://review.openstack.org/420610 | 10:27 |
| irenab | apuimedo: returning None is expected either if there is no annotations or the expected annotation is not there | 10:28 |
| apuimedo | right | 10:28 |
| apuimedo | it is almost asking for some annotation wrapping | 10:29 |
| apuimedo | :P | 10:29 |
| irenab | apuimedo: looks like you are in the mood to pythonize the code, go for it :-) | 10:29 |
| apuimedo | in fact, there's TODO's from ivc_ about that | 10:29 |
| apuimedo | I'm in the middle of using /run files for keeping vif data for deletion | 10:29 |
| apuimedo | and this caught my eye | 10:29 |
| *** devvesa has joined #openstack-kuryr | 10:30 | |
| *** pcaruana has quit IRC | 10:38 | |
| *** devvesa has quit IRC | 10:39 | |
| *** yamamoto has joined #openstack-kuryr | 10:55 | |
| *** tonanhngo has joined #openstack-kuryr | 10:55 | |
| *** devvesa has joined #openstack-kuryr | 10:56 | |
| *** tonanhngo has quit IRC | 10:57 | |
| *** yamamoto has quit IRC | 11:10 | |
| mchiappero | sorry folks, do you know where the code for trunk ports is in neutron? | 11:14 |
| mchiappero | ltomasbo? | 11:14 |
| ltomasbo | yep | 11:14 |
| ltomasbo | services/trunk | 11:14 |
| mchiappero | it was easy actually... | 11:15 |
| mchiappero | thanks | 11:15 |
| ltomasbo | I think I found the issue for the connectivity, going to try to push the automatic vlan id allocation in a while | 11:15 |
| openstackgerrit | vikas choudhary proposed openstack/kuryr-kubernetes: Add support for nested pods with Vlan trunk port https://review.openstack.org/410578 | 11:28 |
| vikas_ | irenab, ltomasbo ^ | 11:29 |
| ltomasbo | vikas_, you are working hard today :D | 11:31 |
| vikas_ | ltomasbo, :D | 11:32 |
| *** salv-orlando has joined #openstack-kuryr | 11:49 | |
| irenab | vikas_: thanks a lot for addressing all comments | 11:55 |
| *** pcaruana has joined #openstack-kuryr | 11:56 | |
| vikas_ | irenab, thanks a lot for quick responses :) | 11:56 |
| vikas_ | ltomasbo, too | 11:56 |
| ltomasbo | np, nice work! | 11:57 |
| vikas_ | apuimedo, https://review.openstack.org/410578 | 12:07 |
| apuimedo | vikas_: would the retry handler that wraps the handler already take care of the retry in https://review.openstack.org/#/c/410578/12..18/kuryr_kubernetes/controller/drivers/nested_vlan_vif.py | 12:13 |
| *** ivc_ has joined #openstack-kuryr | 12:16 | |
| vikas_ | apuimedo, that retires for different exception | 12:25 |
| vikas_ | s/retries | 12:25 |
| apuimedo | i wonder if it could be adapted | 12:26 |
| apuimedo | wdyt ivc_ ^^ | 12:26 |
| vikas_ | may be we can iterate after this patch for improvement | 12:26 |
| vikas_ | and see if possible to adapt | 12:27 |
| ivc_ | apuimedo vikas_ sorry i'm missing parts of the discussion, my irc bouncer died today :/ | 12:28 |
| vikas_ | ivc_, apuimedo said vikas_: would the retry handler that wraps the handler already take care of the retry in https://review.openstack.org/#/c/410578/12..18/kuryr_kubernetes/controller/drivers/nested_vlan_vif.py | 12:29 |
| ivc_ | yup thats what retry handler is for | 12:30 |
| ivc_ | but in some cases it does not solve the problem | 12:31 |
| ivc_ | i had to do the same thing in https://review.openstack.org/#/c/376045/12/kuryr_kubernetes/controller/drivers/lbaasv2.py@307 | 12:32 |
| irenab | ivc_: the method should raise ResourceNotReady to get pipeline call the event handler again, right? | 12:33 |
| vikas_ | we can write a wrapper on add_subport for retrying on "Conflict" exception. But i will love to defer this to a successive patch | 12:33 |
| ivc_ | irenab yes but the problem is when you have some parts of work already done before the exception it gets messy | 12:34 |
| apuimedo | vikas_: I'm okay with just putting a REVISIT note | 12:34 |
| ivc_ | apuimedo in https://review.openstack.org/#/c/376045/12/kuryr_kubernetes/controller/drivers/lbaasv2.py@326 | 12:35 |
| irenab | ivc_: agree with you, looks like the one who writes the code of the event handler must be aware of the Retry being applied and keep the code that handles this properly. | 12:35 |
| ivc_ | irenab i'm actually thinking about getting rid of the retry _handler_ and replacing it with just a decorator | 12:36 |
| irenab | ivc_: which requires some sort of state store | 12:36 |
| vikas_ | apuimedo, https://review.openstack.org/#/c/410578/18/kuryr_kubernetes/controller/drivers/nested_vlan_vif.py@131 already have a note added | 12:36 |
| apuimedo | ivc_: it's probably a good idea to move it to a decorator and context manager | 12:37 |
| apuimedo | for finer granularity | 12:37 |
| apuimedo | vikas_: very well | 12:37 |
| ivc_ | apuimedo yup | 12:37 |
| apuimedo | irenab: have you tried the patch? | 12:39 |
| ivc_ | apuimedo irenab vikas_ btw while we are at it, wdyt if we need to preserve the 'timeout per event' functionality with the ctxmgr/deco retry? | 12:39 |
| apuimedo | ivc_: I'm not sure I got the question | 12:39 |
| ivc_ | or just keep it simple/generic and be per-call timeout | 12:39 |
| apuimedo | oh | 12:39 |
| *** gsagie has joined #openstack-kuryr | 12:40 | |
| apuimedo | I think I get it now, you mean whether the context manager/decorator event timeout aware | 12:40 |
| apuimedo | or not | 12:40 |
| ivc_ | apuimedo with the current retry handler you have a shared timeout for different operations, so it is predictable how much time is spent per event | 12:40 |
| ivc_ | yup | 12:40 |
| apuimedo | It would be better to keep this guarantee | 12:40 |
| apuimedo | but the code is going to look funny | 12:41 |
| vikas_ | i think individual time-outs per event will give better tuning capability | 12:41 |
| ivc_ | apuimedo we can keep the guarantee. we keep the 'retry' handler and have it store remaining time or the timestamp the event was received | 12:42 |
| *** yedongcan1 has left #openstack-kuryr | 12:42 | |
| irenab | apuimedo: deploying now | 12:43 |
| ivc_ | it wont 'look funny', there's a pretty clean/simple solution for that :) | 12:43 |
| apuimedo | irenab: then I leave the w+1 on you | 12:43 |
| irenab | apuimedo: ok | 12:43 |
| apuimedo | ivc_: won't that couple the retry handler and the decorator/ctxtmgr? | 12:44 |
| irenab | apuimedo: must get fullstack asap | 12:44 |
| * apuimedo knows | 12:44 | |
| apuimedo | the CI mechanism confuses me | 12:44 |
| irenab | apuimedo: another topic to the virtual sprint if we won’t sort it out before | 12:45 |
| apuimedo | I have to ask a couple of questions to yuvalb | 12:45 |
| apuimedo | irenab: indeed | 12:45 |
| ivc_ | apuimedo it will in some way | 12:45 |
| ivc_ | apuimedo ok now i think it would be best if we keep the current 'retry event' but also make a decorator/context manager that will share the same time limit. it covers all the cases | 12:47 |
| * apuimedo 'd like to avoid the coupling | 12:47 | |
| ivc_ | it wont be coupling, they would be different APIs of the same thing | 12:48 |
| apuimedo | ivc_: That's what I was thinking about | 12:48 |
| apuimedo | but! | 12:48 |
| apuimedo | how do you give the ctxt manager a reference to the retry handler that is wrapping the current event? | 12:48 |
| apuimedo | afaik we don't have it available | 12:49 |
| ivc_ | apuimedo thread-local var | 12:49 |
| apuimedo | ivc_: it is there? Or you are thinking about putting it? (green thread local var, I suppose) | 12:49 |
| ivc_ | eventlet has support for it | 12:50 |
| ivc_ | you just use the one from threading module and eventlet has it patched already | 12:50 |
| apuimedo | oh... that's so implicit... this monkeypatching gives me the creeps | 12:52 |
| irenab | vikas_: I think you didn’t update the local.conf options following the review comments ltomasbo posted few spins ago | 12:56 |
| *** devvesa has quit IRC | 12:58 | |
| vikas_ | irenab, i missed that but existing local.conf is also working. Are you facing any issue | 13:14 |
| irenab | vikas_: I had issues with ovecloud, it kept failing for keystone service to start | 13:15 |
| irenab | vikas_: but not a proable, this can be fixed by the devstack support patch | 13:16 |
| irenab | not a problem | 13:16 |
| vikas_ | irenab, thanks | 13:16 |
| ltomasbo | yep. I was not able to deploy the overcloud with the current local.conf | 13:23 |
| *** gsagie has quit IRC | 13:31 | |
| *** salv-orlando has quit IRC | 13:36 | |
| apuimedo | ltomasbo: maybe you can send a follow-up patch to fix :P | 13:37 |
| *** salv-orlando has joined #openstack-kuryr | 14:21 | |
| ltomasbo | I didn't manage so far to get the patch working in my environment, but I will keep trying | 14:26 |
| ltomasbo | that said, I think it should be change for the multi_host as it makes more sense rather than have under/over cloud, which has a slightly different meaning in my opinion, and will fix the problem of keystone being a requirement | 14:27 |
| ltomasbo | for the overcloud | 14:27 |
| ltomasbo | That said, I agree, polishing the local.conf could be done in a follow-up patch | 14:28 |
| apuimedo | ltomasbo: I agree with you | 14:33 |
| openstackgerrit | Zhang Ni proposed openstack/fuxi: Enable Fuxi to use Manila share https://review.openstack.org/375452 | 14:38 |
| *** gsagie has joined #openstack-kuryr | 14:47 | |
| *** devvesa has joined #openstack-kuryr | 14:50 | |
| *** mattmceuen has joined #openstack-kuryr | 14:52 | |
| *** hongbin has joined #openstack-kuryr | 14:53 | |
| *** mattmceuen has quit IRC | 15:06 | |
| *** openstack has joined #openstack-kuryr | 15:17 | |
| *** jerms has quit IRC | 15:18 | |
| *** jermz has joined #openstack-kuryr | 15:18 | |
| *** pcaruana is now known as pablo|500| | 15:18 | |
| *** neiljerram has quit IRC | 15:19 | |
| *** alraddarla has quit IRC | 15:19 | |
| *** alraddarla has joined #openstack-kuryr | 15:19 | |
| *** neiljerram has joined #openstack-kuryr | 15:22 | |
| *** v1k0d3n has joined #openstack-kuryr | 15:25 | |
| *** v1k0d3n has quit IRC | 15:33 | |
| *** v1k0d3n has joined #openstack-kuryr | 15:34 | |
| *** saneax is now known as saneax-_-|AFK | 15:36 | |
| *** limao has joined #openstack-kuryr | 15:36 | |
| *** limao_ has joined #openstack-kuryr | 15:39 | |
| *** limao has quit IRC | 15:40 | |
| *** v1k0d3n has quit IRC | 15:41 | |
| *** david-lyle has joined #openstack-kuryr | 15:47 | |
| *** v1k0d3n has joined #openstack-kuryr | 15:49 | |
| *** janki has quit IRC | 16:03 | |
| *** tonanhngo has joined #openstack-kuryr | 16:12 | |
| *** salv-orl_ has joined #openstack-kuryr | 16:24 | |
| *** salv-orlando has quit IRC | 16:27 | |
| *** limao_ has quit IRC | 16:39 | |
| *** gsagie has quit IRC | 16:46 | |
| *** devvesa has quit IRC | 16:52 | |
| *** v1k0d3n has quit IRC | 16:58 | |
| *** salv-orl_ has quit IRC | 16:58 | |
| *** v1k0d3n has joined #openstack-kuryr | 16:58 | |
| *** v1k0d3n has quit IRC | 17:21 | |
| *** v1k0d3n has joined #openstack-kuryr | 17:35 | |
| *** david-lyle is now known as bailing-wire | 17:37 | |
| *** dougbtv is now known as dougbtv|afk | 17:40 | |
| *** bailing-wire has quit IRC | 17:46 | |
| *** v1k0d3n has quit IRC | 18:48 | |
| *** v1k0d3n has joined #openstack-kuryr | 18:52 | |
| *** huikang has joined #openstack-kuryr | 19:01 | |
| *** salv-orlando has joined #openstack-kuryr | 19:27 | |
| *** huikang has quit IRC | 19:43 | |
| *** huikang has joined #openstack-kuryr | 19:44 | |
| *** huikang has quit IRC | 19:47 | |
| *** huikang has joined #openstack-kuryr | 19:47 | |
| *** bailing-wire has joined #openstack-kuryr | 20:00 | |
| *** bailing-wire is now known as david-lyle | 20:02 | |
| *** salv-orlando has quit IRC | 20:04 | |
| *** huikang has quit IRC | 20:21 | |
| *** huikang has joined #openstack-kuryr | 20:23 | |
| *** huikang has quit IRC | 20:46 | |
| *** v1k0d3n has quit IRC | 20:56 | |
| *** v1k0d3n has joined #openstack-kuryr | 21:23 | |
| *** huikang has joined #openstack-kuryr | 21:47 | |
| *** severion has joined #openstack-kuryr | 21:47 | |
| *** huikang has quit IRC | 21:51 | |
| *** severion has quit IRC | 21:56 | |
| *** severion has joined #openstack-kuryr | 21:56 | |
| *** severion has quit IRC | 21:58 | |
| *** severion has joined #openstack-kuryr | 22:00 | |
| *** severion is now known as v1k0d3m | 22:00 | |
| *** v1k0d3m has quit IRC | 22:01 | |
| *** severion has joined #openstack-kuryr | 22:03 | |
| *** v1k0d3n has quit IRC | 22:24 | |
| *** severion has quit IRC | 22:24 | |
| *** portdirect is now known as shipindirect | 22:25 | |
| *** david-lyle has quit IRC | 22:32 | |
| *** david-lyle has joined #openstack-kuryr | 22:40 | |
| *** pmannidi has joined #openstack-kuryr | 22:54 | |
| *** salv-orlando has joined #openstack-kuryr | 23:05 | |
| *** salv-orlando has quit IRC | 23:09 | |
| *** saneax-_-|AFK is now known as saneax | 23:15 | |
| *** jermz has quit IRC | 23:24 | |
| *** jermz has joined #openstack-kuryr | 23:24 | |
| *** garyloug has quit IRC | 23:27 | |
| *** tonanhngo has quit IRC | 23:41 | |
| *** tonanhngo has joined #openstack-kuryr | 23:42 | |
| *** shipindirect is now known as portdirect | 23:43 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!