Monday, 2016-10-03

*** tonanhngo has joined #openstack-kuryr00:23
*** tonanhngo has quit IRC00:25
*** yamamoto_ has joined #openstack-kuryr00:27
*** yamamoto_ has quit IRC00:35
*** huikang has joined #openstack-kuryr00:36
*** akanksha_ has quit IRC00:37
*** huikang has quit IRC00:53
*** huikang has joined #openstack-kuryr00:54
*** huikang has quit IRC00:58
*** tonanhngo has joined #openstack-kuryr01:23
*** tonanhngo has quit IRC01:25
*** tonanhngo has joined #openstack-kuryr01:37
*** salv-orlando has joined #openstack-kuryr02:04
*** salv-orlando has quit IRC02:08
*** huikang has joined #openstack-kuryr02:26
*** sdake has quit IRC02:29
*** huikang has quit IRC02:31
*** yuanying has quit IRC02:52
*** yuanying has joined #openstack-kuryr02:53
*** lezbar has quit IRC03:03
*** lezbar has joined #openstack-kuryr03:03
*** salv-orlando has joined #openstack-kuryr03:04
*** salv-orlando has quit IRC03:09
*** sdake has joined #openstack-kuryr03:21
*** yamamoto_ has joined #openstack-kuryr03:31
*** sdake_ has joined #openstack-kuryr03:38
*** sdake has quit IRC03:40
*** yuanying has quit IRC03:44
*** huikang has joined #openstack-kuryr03:49
*** yuanying has joined #openstack-kuryr03:51
*** huikang has quit IRC03:57
*** huikang has joined #openstack-kuryr03:58
*** huikang has quit IRC04:02
*** salv-orlando has joined #openstack-kuryr04:05
*** salv-orlando has quit IRC04:10
*** vikasc has quit IRC04:14
*** vikasc has joined #openstack-kuryr04:28
*** yamamoto_ has quit IRC04:38
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: K8s and Neutron clients support  https://review.openstack.org/37604204:42
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: [WIP] Watcher and event processing base  https://review.openstack.org/37604304:48
*** yuanying has quit IRC04:59
*** yuanying_ has joined #openstack-kuryr04:59
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: K8s and Neutron clients support  https://review.openstack.org/37604205:01
*** salv-orlando has joined #openstack-kuryr05:04
vikascapuimedo, ping05:15
*** vikasc has quit IRC05:20
*** yamamoto_ has joined #openstack-kuryr05:28
openstackgerritJaivish Kothari(janonymous) proposed openstack/kuryr-libnetwork: Update file mode 777->664  https://review.openstack.org/38092505:31
*** janki has joined #openstack-kuryr05:36
*** vikasc has joined #openstack-kuryr05:37
*** salv-orlando has quit IRC06:00
*** sdake has joined #openstack-kuryr06:22
*** sdake_ has quit IRC06:23
*** tonanhngo has quit IRC06:27
*** yuanying_ has quit IRC06:33
*** salv-orlando has joined #openstack-kuryr06:50
*** tonanhngo has joined #openstack-kuryr07:02
*** tonanhngo has quit IRC07:04
apuimedoapuimedo: pong07:12
*** sdake has quit IRC07:15
*** sdake has joined #openstack-kuryr07:26
*** tonanhngo has joined #openstack-kuryr07:38
*** tonanhngo has quit IRC07:39
*** salv-orl_ has joined #openstack-kuryr07:44
*** salv-orlando has quit IRC07:48
*** lezbar has quit IRC07:55
*** garyloug has joined #openstack-kuryr07:55
*** lezbar has joined #openstack-kuryr07:56
*** sdake has quit IRC07:58
*** lmdaly has joined #openstack-kuryr07:59
*** lezbar has quit IRC08:33
*** lezbar has joined #openstack-kuryr08:34
*** yuanying has joined #openstack-kuryr08:59
apuimedovikasc: please, merge https://review.openstack.org/#/c/379556/09:03
vikascapuimedo, done!09:05
apuimedothanks09:06
vikascyw09:06
apuimedovikasc: https://review.openstack.org/#/c/375389/ is also ready09:07
apuimedoand also https://review.openstack.org/#/c/376173/09:08
vikascapuimedo, sure09:08
openstackgerritMerged openstack/kuryr-libnetwork: Fix tox -e cover in kuryr-libnetwork  https://review.openstack.org/37955609:12
*** ivc_ has joined #openstack-kuryr09:25
openstackgerritMerged openstack/kuryr: Remove redundant 'limitations' section  https://review.openstack.org/38068109:27
apuimedolmdaly: sorry I forgot to put the reference to the PoC09:31
apuimedoI'll address it now09:31
apuimedothanks for pointing it out09:31
lmdalyNo problem at all, thanks! :)09:31
*** sdake has joined #openstack-kuryr09:44
*** garyloug has quit IRC09:54
apuimedolmdaly: here it is10:07
apuimedohttps://blueprints.launchpad.net/kuryr/+spec/driver-binding-ipvlan10:07
apuimedoI put the info here10:07
apuimedoand in gerrit I'll reference the blueprint10:07
lmdalyapuimedo, looks good! thanks again10:16
apuimedothanks to you10:16
apuimedofor bringing it up10:16
*** yamamoto_ has quit IRC10:24
*** tonanhngo has joined #openstack-kuryr10:27
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr: binding: Add driver based subsystem  https://review.openstack.org/37586410:29
*** tonanhngo has quit IRC10:29
apuimedovikasc: ivc_ lmdaly: ^^10:29
vikascapuimedo, ack10:29
ivc_apuimedo what about veth_dst_prefix https://review.openstack.org/#/c/375864/8/kuryr/lib/config.py@67 ?10:32
apuimedoivc_: sorry. I had forgotten to publish my comments10:33
apuimedojust pushed it now10:33
apuimedoit's something I prefer to do on a separate patch10:33
apuimedowhich I'll send now10:33
apuimedofunnily enough, I don't think that config variable was being used10:34
ivc_btw apuimedo, vikasc I've lifted [WIP] from https://review.openstack.org/#/c/376042/; now focused on bringing os-vif objects/models to https://review.openstack.org/#/c/376044/10:34
apuimedoonly in kuryr-libnetwork I see it used10:35
apuimedogreat!10:35
apuimedoivc_: going to it10:35
vikascivc_, thanks!10:36
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr: Replace link_remove with link delete  https://review.openstack.org/37459110:37
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr: binding: use cached interface info  https://review.openstack.org/33550010:37
ivc_also thnx for your reviews on k8s events devref10:38
*** diga_ has joined #openstack-kuryr10:41
vikascivc_, eagerly waiting for an update patch on k8s events devref. :)10:41
ivc_vikasc I'm deliberately not updating it until I've settled with the implementation approach :)10:43
ivc_the blocker for me is https://review.openstack.org/#/c/376043/10:44
ivc_as i'm not quite happy with the implementation yet10:44
vikascivc_, i was thinking that details on devref will help better understand and review implentation patches. No worries. Please update once you feel comfortable :)10:45
ivc_and also I'll probably get rid of context/providers concept in favour of a more simple approach like in https://review.openstack.org/#/c/376044/10:45
ivc_there are literally just 2 things that i don't quite like that. one is that watcher/events patch (but thats mostly a cleanup issue)10:46
ivc_and the other one is i need some container for a shared state like global_context in https://review.openstack.org/#/c/376046/1/kuryr_kubernetes/controller/service.py@3910:47
ivc_to hold the namespace/node specific networking configuration (e.g. neutron subnet/network/tenant ids)10:47
*** openstackgerrit has quit IRC10:48
ivc_ofc we could just http 'get' namespace/node annotations on each pod event, but thats something i'd like to avoid10:48
*** openstackgerrit has joined #openstack-kuryr10:48
ivc_that was the main reason for the context/providers approach i described in devref, but when it gets to code it really just makes things more complex than it should be and hard to read/navigate the codebase10:50
apuimedoindeed10:52
apuimedomaybe we can find another way of avoiding the extra get10:52
ivc_its quite simple. that 'global_context' in https://review.openstack.org/#/c/376046/1/kuryr_kubernetes/controller/service.py@39 does solve the problem10:54
ivc_i just want it to have some better name than 'context' and some clean api rather then just a dict10:55
apuimedowell, I think it's okay if we just put retrieval methods as needed10:56
apuimedofor 0.1.010:56
ivc_i was for a moment thinking of using config.CONF as a storage for that10:56
apuimedoand in 1.0.0 we take the experience to make a better API10:56
apuimedoivc_: that's a bit brutal :P10:57
ivc_but that info is indeed part of the config10:57
apuimedoI consider it more state than info10:58
apuimedos/info/config/10:58
ivc_but its static10:58
apuimedoexample?10:59
ivc_and as you said once it could even be driven by the config (e.g. when we are leaving namespaces without network annotations and sticking with default subnet from config)10:59
ivc_the namespace annotation i'm talking about is the pod subnet id / service subnet id / tenant id11:00
apuimedooh, I thought you meant namespace live annotation state11:00
ivc_its live but its static11:00
ivc_i mean we can start k8s without annotations on namespace11:01
ivc_but then use our (yet to be implemented) cli to update namespace with neutron subnets11:01
ivc_but that annotation would be write-once as there's no sane way to reconfigure pods/services if we want to change subnet on namespace11:02
apuimedommm11:02
apuimedoso the options are11:03
ivc_tho that annotation is live as it would be configurable in runtime with our cli and will be picked by watchers' namespace event processor11:03
apuimedoa) We have a config option that says, for each namespace we see, we get a subnet from a pool11:03
ivc_b) we will specify subnet with cli11:04
apuimedoc) we rely completely on the users creating the namespaces with annotations of existing subnets11:04
ivc_no (c). that is covered by (b)11:04
ivc_and (a) would just add annotations for (b), so the annotation handling is the same for both options11:07
ivc_just that (a) is automation for (b)11:07
*** tonanhngo has joined #openstack-kuryr11:08
*** tonanhngo has quit IRC11:09
ivc_i think i'll just make some simple dict-wrapping api e.g. class NetworkSettings(): def get_pod_subnet(namespace, node) / get_service_subnet(namespace)11:10
ivc_and make it a singleton11:10
ivc_yeah! i like it now11:11
ivc_thnx guys :)11:11
ivc_(sry for spam)11:12
apuimedomm11:12
*** sdake_ has joined #openstack-kuryr11:12
apuimedoif you want to make it a singleton, why to use a class and not directly a module, which is guaranteed to be a singleton?11:12
ivc_its an object11:13
*** salv-orl_ has quit IRC11:14
ivc_and it complicates testing11:14
*** sdake has quit IRC11:14
ivc_if you do like you said with modules11:14
apuimedook, go ahead with the dict wrapper11:17
*** salv-orlando has joined #openstack-kuryr11:18
apuimedoand it is not spam, it is wanted and healthy discussion11:20
apuimedolmdaly: please, review the new binding patch when you get a chance11:21
apuimedovikasc: waiting for your +2 two :P11:21
*** yamamoto has joined #openstack-kuryr11:26
*** lmdaly has quit IRC11:30
vikascapuimedo, i am on it11:41
apuimedocool, thanks11:42
*** tonanhngo has joined #openstack-kuryr11:43
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: K8s and Neutron clients support  https://review.openstack.org/37604211:44
*** tonanhngo has quit IRC11:45
* apuimedo reviewing ^^11:49
*** lezbar has quit IRC11:49
*** lezbar has joined #openstack-kuryr11:50
*** sdake_ is now known as sdake11:52
ivc_apuimedo, agreed on using kuryr_lib get_neutron_client11:55
apuimedoivc_: what are the cycles for in the watch test?11:56
ivc_but then we should probably update kuryr_lib to use OpenStackConfig11:56
ivc_apuimedo, cycles are how many times it will go through while True loop11:57
apuimedoivc_: ?11:57
apuimedoit uses keystoneauth111:57
apuimedojust like the other projects11:57
apuimedoos-client-config it uses only for testing11:57
apuimedohttps://github.com/openstack/kuryr-libnetwork/blob/master/kuryr_libnetwork/controllers.py#L47-L6511:58
ivc_but https://review.openstack.org/#/c/376042/4/kuryr_kubernetes/clients.py uses both keystoneauth1 and os-client-config11:58
ivc_i actually just 'borrowed' the implementation from neutronclient itself11:58
ivc_https://github.com/openstack/python-neutronclient/blob/master/neutronclient/shell.py#L88911:59
*** lmdaly has joined #openstack-kuryr12:00
ivc_i think its the way we should do it in kuryr.lib12:00
openstackgerritMerged openstack/kuryr-libnetwork: Using kuryr-lib constants  https://review.openstack.org/37538912:09
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: K8s and Neutron clients support  https://review.openstack.org/37604212:10
ivc_apuimedo ^^ updated to use kuryr.lib get_neutron_client12:11
*** tonanhngo has joined #openstack-kuryr12:13
*** tonanhngo has quit IRC12:14
ivc_apuimedo, regarding cycles, K8sClient.watch is a generator and is infinite (it will take care of retrying http calls on failures, tho the http connection failures are not handled atm). so the cycles is the means to limit that generator. think of cycles as if the k8s 'watch' get request was ended by k8s api server and restarted12:15
*** yamamoto has quit IRC12:21
apuimedounderstood12:44
apuimedothanks12:44
apuimedoivc_: why the __version__ removal?12:59
apuimedohttps://review.openstack.org/#/c/376042/5/kuryr_kubernetes/__init__.py12:59
*** yamamoto has joined #openstack-kuryr13:04
*** tonanhngo has joined #openstack-kuryr13:04
*** tonanhngo has quit IRC13:05
*** limao has joined #openstack-kuryr13:12
ivc_apuimedo, didn't notice __version__ there :) the intent was to remove config_map and py35-related watchers import13:22
apuimedo:-)13:22
ivc_why do we need __version__ there btw?13:23
apuimedoivc_: it's just nice when you import some package to check the __version__13:25
*** limao has quit IRC13:26
*** limao has joined #openstack-kuryr13:27
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: K8s and Neutron clients support  https://review.openstack.org/37604213:27
ivc_^^ reverted the removal of __version__13:28
apuimedothanks ivc_13:28
apuimedoivc_: approved13:28
apuimedovikasc: review it, when you have a moment13:28
ivc_thnx apuimedo13:29
vikascsure apuimedo13:29
apuimedothanks to you ivc_13:29
apuimedoivc_: which should we check next13:34
apuimedo?13:34
*** limao_ has joined #openstack-kuryr13:35
*** janki has quit IRC13:36
ivc_apuimedo https://review.openstack.org/#/c/376043/ maybe13:36
apuimedok13:36
*** limao__ has joined #openstack-kuryr13:36
ivc_i still want to cleanup it a bit and have not fixed pep8 and no ut yet13:36
ivc_but some sort of 'conceptual' review would not hurt :)13:37
*** limao has quit IRC13:37
*** limao_ has quit IRC13:39
*** huikang has joined #openstack-kuryr13:41
*** huikang has quit IRC13:41
*** huikang has joined #openstack-kuryr13:41
*** diga_ has quit IRC13:43
*** salv-orl_ has joined #openstack-kuryr13:44
*** ivc_ has quit IRC13:47
*** salv-orlando has quit IRC13:47
*** hongbin has joined #openstack-kuryr13:47
*** limao has joined #openstack-kuryr13:47
*** limao_ has joined #openstack-kuryr13:48
*** limao_ has quit IRC13:49
*** ivc_ has joined #openstack-kuryr13:49
*** limao_ has joined #openstack-kuryr13:49
*** limao__ has quit IRC13:50
ivc_apuimedo, vikasc, also regarding  https://review.openstack.org/#/c/376043/ i've got a naming issue :)13:50
ivc_i dont like the 'Processor' name for those classes, maybe you got a better suggestion13:50
ivc_e.g. Listener or Observer or just Callback13:51
apuimedolet me check13:51
*** limao has quit IRC13:52
apuimedoivc_: well, it is processor or handler13:53
apuimedoI think I prefer handler13:54
apuimedosince it is more identifiable13:54
*** tonanhngo has joined #openstack-kuryr13:57
*** yedongcan has joined #openstack-kuryr13:58
vikasc+1 for handler13:58
*** limao has joined #openstack-kuryr14:01
*** huikang has quit IRC14:01
apuimedoivc_: meeting in openstack-meeting-4\14:01
ivc_ok its handler then14:01
ivc_yup14:01
*** huikang has joined #openstack-kuryr14:01
*** limao_ has quit IRC14:03
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr: Updated from global requirements  https://review.openstack.org/35768314:10
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr-libnetwork: Updated from global requirements  https://review.openstack.org/35197614:10
*** huikang has quit IRC14:18
*** huikang has joined #openstack-kuryr14:18
*** huikang has quit IRC14:23
*** garyloug has joined #openstack-kuryr14:24
*** diogogmt has joined #openstack-kuryr14:50
*** limao_ has joined #openstack-kuryr14:52
*** limao has quit IRC14:55
*** limao has joined #openstack-kuryr15:00
apuimedoivc_: hongbin: tonanhngo: one option I considered with the no-auth approach15:01
apuimedowas to have ssl client side authentication to an nginx neutron proxy15:02
*** yedongcan_ has joined #openstack-kuryr15:02
apuimedoand have there some modification of the headers that put our service token auth15:02
*** yedongcan_ has quit IRC15:03
*** limao_ has quit IRC15:03
hongbinsorry, didn't get your question15:04
*** limao_ has joined #openstack-kuryr15:04
*** yamamoto has quit IRC15:04
*** yedongcan has quit IRC15:05
*** limao has quit IRC15:06
apuimedonot really a question15:06
hongbinapuimedo: the authentication happened between kuryr agent in VM and the neutron api?15:06
apuimedoI was more thinking while writing15:06
apuimedothe we could have kuryr in the instances have an ssl key and cert15:07
apuimedoand then an nging proxy to neutron outside of the instance that checked the client auth and dropped not whitelisted requests15:08
apuimedobut it sounds hacky15:08
hongbinthe kuryr agent has to be installed in nova instance?15:09
apuimedoeach nova instance that runs docker engine will need a kuryr agent15:09
apuimedolibnetwork driver or kubelet cni driver15:09
hongbinhowever, the libnetwork driver just needs to do the port binding, not necessary doing teh authentication15:10
hongbinright?15:10
hongbin(i am possibly wrong since i am not in the domain)15:10
apuimedohongbin: kuryr-libnetwork needs to do both15:12
apuimedokuryr cni driver only the binding15:12
apuimedohowever15:12
apuimedoit would be possible to have kuryr-libnetwork broken out15:13
apuimedoin a way to have only one server doing the the auth and neutron actions15:13
hongbinthe broken out seems to be more ideal15:13
apuimedoand then calling other servers in each machine to do the binding15:13
hongbinyes15:14
apuimedohongbin: well, we could test the assumption of this being possible by writing a binding driver that does the operations via ssh to the hosts where the binding should happen :P15:14
apuimedohacky as hell, but to proof the concept...15:15
*** limao_ has quit IRC15:15
hongbinapuimedo: you could have two agents15:15
hongbinapuimedo: one that is providing rest service for port binding15:15
*** limao has joined #openstack-kuryr15:15
hongbinapuimedo: another is doing the rest15:15
apuimedosure, that would be the proper way15:15
apuimedoI was talking about a one day effort to try it out :P15:16
hongbinok15:16
tonanhngothat would be good, to see if any issue pops up.15:16
apuimedocause with the two agents, you should also set up some authentication between the main agent and the binding ones15:16
apuimedoexactly15:16
tonanhngosecurity is hard :)15:17
hongbinapuimedo: yes, there are several ways to deal with authentication between agents15:17
hongbinapuimedo: if one agent on swarm agents, another agent on swarm master, we could use security group and disable authentication15:18
hongbinapuimedo: if one agent on swarm agents, another agent on kuryr control plane, we could have a keystone role to limit the access of the agent15:18
apuimedohongbin: I didn't mean keystone auth, I meant just so that the requests to the binding agent would only come from the kuryr-libnetwork agent running on the controller15:19
hongbinapuimedo: in magnum, we can place two agents in the same security group, that restrict the access to the agent port within that security group15:20
hongbinhowever, that is magnum specific15:21
apuimedohongbin: I was more worried about local access to the binding server15:22
apuimedobut it may not be a problem after all15:22
apuimedolike, containers run with host networking could mess with the driver, but this is already the case15:22
apuimedoso yeah, we should probably try this agent separation15:22
apuimedo(we would need a blueprint and somebody to take up this task)15:23
*** yamamoto has joined #openstack-kuryr15:23
hongbini might take the bp, but needs some times to pick up the kuryr codebase15:24
apuimedohongbin: let me know when the bp is up and I'll review15:24
apuimedoand if you have time for coding it I can give you some tips15:24
hongbinapuimedo: sure. thx15:24
apuimedothanks to you!15:25
hongbinmy pleasure15:25
*** limao_ has joined #openstack-kuryr15:27
openstackgerritMerged openstack/kuryr: binding: Add driver based subsystem  https://review.openstack.org/37586415:28
*** limao has quit IRC15:30
*** huikang has joined #openstack-kuryr15:32
ivc_apuimedo, hongbin, i think for kuryr-k8s access to neutron from cni is not an issue as cni will only use k8s watch api to get the data15:34
apuimedoivc_: agreed15:35
apuimedo:-)15:35
ivc_and all neutron interactions are done by the controller (did we actually drop the 'raven' name?)15:35
ivc_i think i understand the reason why you wanted the rpc server for libnetwork :)15:37
*** lezbar has quit IRC15:44
*** lezbar has joined #openstack-kuryr15:45
openstackgerritLiping Mao proposed openstack/kuryr-libnetwork: [DO NOT MERGE] Test UT  https://review.openstack.org/37929515:49
*** huikang has quit IRC15:58
*** huikang has joined #openstack-kuryr15:59
*** tonanhngo has quit IRC15:59
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: K8s and Neutron clients support  https://review.openstack.org/37604216:01
ivc_hongbin, apuimedo, ^^ updated the commit message to reflect that the K8sClient it introduces is a temporary solution16:02
*** huikang_ has joined #openstack-kuryr16:03
*** huikang has quit IRC16:03
hongbinivc_: thx16:04
openstackgerritIlya Chukhnakov proposed openstack/kuryr-kubernetes: K8s and Neutron clients support  https://review.openstack.org/37604216:07
ivc_^^ l2spell issue:/16:07
ivc_they should really add a spellcheck to gerrit 'edit' form :)16:08
*** huikang_ has quit IRC16:26
*** huikang has joined #openstack-kuryr16:26
*** sdake has quit IRC16:30
*** huikang has quit IRC16:31
*** sdake has joined #openstack-kuryr16:34
*** tonanhngo has joined #openstack-kuryr16:48
*** tonanhngo has quit IRC16:50
*** tonanhngo has joined #openstack-kuryr16:50
*** lmdaly has quit IRC16:50
*** yamamoto has quit IRC16:59
*** salv-orl_ has quit IRC17:12
*** salv-orlando has joined #openstack-kuryr17:20
*** huikang has joined #openstack-kuryr17:37
*** sdake has quit IRC17:39
*** lezbar has quit IRC17:42
*** lezbar has joined #openstack-kuryr17:43
*** sdake has joined #openstack-kuryr17:44
*** salv-orlando has quit IRC17:53
*** huikang has quit IRC17:54
*** lezbar has quit IRC18:00
*** sdake has quit IRC18:01
*** lezbar has joined #openstack-kuryr18:01
*** ivc_ has quit IRC18:07
openstackgerritMerged openstack/kuryr: Replace link_remove with link delete  https://review.openstack.org/37459118:10
openstackgerritMerged openstack/kuryr: binding: use cached interface info  https://review.openstack.org/33550018:10
*** banix has joined #openstack-kuryr18:11
*** garyloug has quit IRC18:11
*** ivc_ has joined #openstack-kuryr18:11
*** yamamoto has joined #openstack-kuryr18:30
*** banix has quit IRC18:38
*** ivc_ has quit IRC18:39
*** banix has joined #openstack-kuryr18:52
*** yamamoto has quit IRC19:00
*** garyloug has joined #openstack-kuryr19:19
*** salv-orlando has joined #openstack-kuryr19:30
*** salv-orl_ has joined #openstack-kuryr19:44
*** salv-orlando has quit IRC19:47
banixapuimedo: are you around by any chance?19:52
*** tonanhngo has quit IRC19:57
*** sdake has joined #openstack-kuryr20:05
*** garyloug has quit IRC20:08
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr: Updated from global requirements  https://review.openstack.org/35768320:11
*** tonanhngo has joined #openstack-kuryr20:18
*** tonanhngo has quit IRC20:23
*** tonanhngo has joined #openstack-kuryr20:27
*** garyloug has joined #openstack-kuryr20:28
*** banix has quit IRC20:30
*** lezbar has quit IRC21:10
*** lezbar has joined #openstack-kuryr21:11
*** banix has joined #openstack-kuryr21:14
*** openstackgerrit has quit IRC21:19
*** openstackgerrit has joined #openstack-kuryr21:19
*** garyloug has quit IRC21:19
*** diogogmt has quit IRC21:32
*** tonanhngo has quit IRC21:36
*** tonanhngo has joined #openstack-kuryr21:43
*** tonanhngo has quit IRC21:48
*** sdake has quit IRC22:16
*** salv-orlando has joined #openstack-kuryr22:28
*** salv-orl_ has quit IRC22:28
*** sdake has joined #openstack-kuryr22:34
*** lezbar has quit IRC22:48
*** lezbar has joined #openstack-kuryr22:49
*** salv-orlando has quit IRC22:55
*** hongbin has quit IRC22:59
*** tonanhngo has joined #openstack-kuryr23:15
*** tonanhngo has quit IRC23:18
*** pmannidi has joined #openstack-kuryr23:21
*** tonanhngo has joined #openstack-kuryr23:27
*** lezbar has quit IRC23:28
*** tonanhngo has quit IRC23:28
*** lezbar has joined #openstack-kuryr23:29
*** tonanhngo has joined #openstack-kuryr23:35
*** tonanhngo has quit IRC23:40
*** tonanhngo has joined #openstack-kuryr23:47
*** tonanhngo has quit IRC23:47

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!