| *** caowei has joined #openstack-kuryr | 01:25 | |
| *** kiennt26 has joined #openstack-kuryr | 01:46 | |
| *** dougbtv__ has quit IRC | 01:57 | |
| *** hongbin has joined #openstack-kuryr | 02:06 | |
| *** janonymous has joined #openstack-kuryr | 02:24 | |
| *** salv-orlando has joined #openstack-kuryr | 02:48 | |
| *** salv-orl_ has quit IRC | 02:51 | |
| *** yamamoto has joined #openstack-kuryr | 04:01 | |
| *** caowei has quit IRC | 04:56 | |
| *** caowei has joined #openstack-kuryr | 05:29 | |
| *** hongbin has quit IRC | 05:30 | |
| *** janki has joined #openstack-kuryr | 05:33 | |
| irenab | dulek, good morning | 06:49 |
|---|---|---|
| openstackgerrit | Eyal Leshem proposed openstack/kuryr-kubernetes master: Network policy support spec https://review.openstack.org/519239 | 06:50 |
| openstackgerrit | Eyal Leshem proposed openstack/kuryr-kubernetes master: Network policy support spec https://review.openstack.org/519239 | 06:56 |
| *** yboaron has joined #openstack-kuryr | 07:25 | |
| *** pmannidi has quit IRC | 07:39 | |
| *** pcaruana has joined #openstack-kuryr | 08:10 | |
| *** salv-orlando has quit IRC | 08:11 | |
| *** salv-orlando has joined #openstack-kuryr | 08:11 | |
| *** salv-orlando has quit IRC | 08:15 | |
| *** yboaron_ has joined #openstack-kuryr | 08:16 | |
| *** yboaron has quit IRC | 08:18 | |
| dulek | irenab: Hi, what's up? | 08:23 |
| *** yboaron_ has quit IRC | 08:25 | |
| *** yboaron_ has joined #openstack-kuryr | 08:25 | |
| openstackgerrit | Michał Dulko proposed openstack/kuryr-kubernetes master: Prevent pyroute2.IPDB threads leaking https://review.openstack.org/517406 | 08:27 |
| openstackgerrit | Michał Dulko proposed openstack/kuryr-kubernetes master: CNI split - introducing CNI daemon https://review.openstack.org/515186 | 08:27 |
| openstackgerrit | Michał Dulko proposed openstack/kuryr-kubernetes master: Support kuryr-daemon when running containerized https://review.openstack.org/518024 | 08:27 |
| *** salv-orlando has joined #openstack-kuryr | 08:36 | |
| openstackgerrit | Eyal Leshem proposed openstack/kuryr-kubernetes master: Network policy support spec https://review.openstack.org/519239 | 09:27 |
| *** garyloug has joined #openstack-kuryr | 09:30 | |
| *** caowei has quit IRC | 09:50 | |
| *** caowei has joined #openstack-kuryr | 09:52 | |
| *** yamamoto has quit IRC | 10:02 | |
| *** s1061123 has joined #openstack-kuryr | 10:03 | |
| *** s1061123_ has quit IRC | 10:04 | |
| irenab | dulek, wanted to check waht tool you used to create sequence diagram for the Pod create flow | 10:06 |
| dulek | irenab: It's Inkscape, I've just modified already existing diagram. | 10:06 |
| *** kiennt26 has quit IRC | 10:08 | |
| *** caowei has quit IRC | 10:13 | |
| ltomasbo | ping dulek, I've just seen your comments on https://review.openstack.org/#/c/518502/ | 10:18 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/fuxi master: Updated from global requirements https://review.openstack.org/519094 | 10:18 |
| ltomasbo | I want to discuss a couple of things with you (as I'm not sure how to better fix it) | 10:18 |
| dulek | ltomasbo: Let me just read those again. :) | 10:18 |
| ltomasbo | they are simple | 10:18 |
| ltomasbo | about the LOG message when the ports are loaded | 10:19 |
| ltomasbo | but that made me realize about one thing | 10:19 |
| dulek | ltomasbo: Yup, okay. So you prefer no try-except? | 10:19 |
| ltomasbo | regardless of setting the LOG.info inside or outside of the with | 10:19 |
| ltomasbo | no, my question is about another related issue | 10:19 |
| ltomasbo | if the with fail | 10:20 |
| ltomasbo | the kubernetes-controller pod will never be ready | 10:20 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements https://review.openstack.org/516936 | 10:20 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements https://review.openstack.org/516937 | 10:20 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements https://review.openstack.org/509781 | 10:20 |
| ltomasbo | so, on the one hand, I'm not sure if the LOG should be in or out of the with | 10:20 |
| ltomasbo | and yep, I agree I need to include a try-except, but perhaps with a LOG.Error if it is not possible to write the file | 10:21 |
| ltomasbo | what do you think? | 10:21 |
| dulek | ltomasbo: I agree with the ERROR level, being an admin I'd prefer to have it logged clearly why my pod isn't ready. | 10:21 |
| dulek | ltomasbo: But I'd also prefer a log instead of pod being restarted constantly. | 10:22 |
| ltomasbo | yep, so, I'll print the ERROR in the try-except, and the LOG.info before the with | 10:22 |
| ltomasbo | dulek, thanks for the feedback, just wanted to double check with you | 10:23 |
| dulek | ltomasbo: Works for me. No problem. :) | 10:23 |
| ltomasbo | great! | 10:23 |
| openstackgerrit | Luis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Add readiness probe to kuryr-controller pod https://review.openstack.org/518502 | 10:51 |
| *** yamamoto has joined #openstack-kuryr | 10:52 | |
| ltomasbo | hi again dulek | 10:56 |
| ltomasbo | once that is polished and merged ^^, could you update the dockerhub containers? | 10:56 |
| dulek | ltomasbo: Sure, apologies I haven't did that earlier, but I've had hope that CNI daemon will be merged earlier. | 10:57 |
| dulek | ltomasbo: BTW I've found the problem with ADD-DEL-ADD-DEL sequence. Had you taken a look on newest version of the patch? | 10:58 |
| ltomasbo | ohh | 10:58 |
| ltomasbo | no, I didn't | 10:58 |
| ltomasbo | I'll do now! what was the problem (I was on PTO last Thu-Fri) | 10:59 |
| dulek | ltomasbo: Main problem was that we're using names to identify pods. | 10:59 |
| dulek | ltomasbo: And we cannot really use anything different as that's the only common value in both API and CNI requests. | 10:59 |
| ltomasbo | umm | 11:00 |
| dulek | ltomasbo: Now kubelet (more specifically CRI) uses CNI_CONTAINERID value. | 11:00 |
| dulek | ltomasbo: It's internal, but this is the ultimate *container* id. | 11:00 |
| ltomasbo | so the add from one pod, was mathcing with the del of other? | 11:00 |
| dulek | ltomasbo: Exactly. Last DEL was actually for older CNI_CONTAINERID. | 11:01 |
| ltomasbo | man, you are dealing with the hardest/trickiest bugs... | 11:01 |
| ltomasbo | dulek, can we use the neutron port id to differentiate them? | 11:02 |
| dulek | ltomasbo: I've fixed it by ignoring DEL requests that doesn't match CNI_CONTAINERID saved when doing last ADD request. | 11:02 |
| ltomasbo | ahh, you already fixed it! | 11:02 |
| dulek | ltomasbo: Hm… Wouldn't it be the same? | 11:02 |
| ltomasbo | going to take a look at the patch then | 11:03 |
| ltomasbo | well, neutron port ids should be unique | 11:03 |
| dulek | I mean - the problem is we're networking Pods, not containers. VIF annotation is tied to Pod, same is true for ports then. | 11:03 |
| dulek | CNI assumes each container (with unique CNI_CONTAINERID) will have a separate networking. | 11:04 |
| ltomasbo | umm, I'm missing something | 11:04 |
| ltomasbo | we are doing 1pod-1port | 11:04 |
| dulek | Yes. | 11:04 |
| ltomasbo | what was the problem then? I assume we still want to do 1 pod 1 port (or many for the multi nic later on) | 11:05 |
| ltomasbo | and hte problem happened with single container pods, right? | 11:05 |
| dulek | ltomasbo: Yes. | 11:05 |
| dulek | ltomasbo: Uhm. Okay, so main problem is that CRI/CNI is working on container level, not pod level. | 11:06 |
| dulek | ltomasbo: Maybe an example: | 11:06 |
| dulek | ltomasbo: 1. kubelet tries to spawn a container "foo" for pod "bar". CNI fails for that request. | 11:07 |
| dulek | ltomasbo: 2. Therefore kubelet will send a CNI DEL request for container "foo" in pod "bar". | 11:07 |
| ltomasbo | example will help a lot! thanks! (and taking a look at your modifications to the patch...) | 11:07 |
| ltomasbo | ok | 11:07 |
| dulek | ltomasbo: 3. Meanwhile a new container "foo2" is starting. | 11:07 |
| dulek | ltomasbo: 4. If DEL request from point 2 gets retried - we don't want to unplug container foo2, but only foo. | 11:08 |
| ltomasbo | ok, got it | 11:09 |
| ltomasbo | so it was deleting the wrong container inside the right pod... | 11:09 |
| ltomasbo | (I need more coffee after the long weekend...) | 11:09 |
| dulek | ltomasbo: For kubelet it's perfectly normal as it works on containers, not pods. | 11:10 |
| dulek | ltomasbo: In Kuryr we're networking whole pods, so it's kind of Kuryr architecture flaw. | 11:10 |
| ltomasbo | well, AFAIK, kubernetes is suppose to network pods, not containers either | 11:11 |
| ltomasbo | so, we are aligned with that | 11:11 |
| dulek | ltomasbo: Kubernetes as a whole - yes, AFAIR there's an assumption that all containers in a pod use single IP. | 11:12 |
| ltomasbo | yep, as well as they 'schedulable' items are pods, not containers | 11:12 |
| dulek | ltomasbo: But that isn't true for CNI/CRI interfaces, that are more universal and are designed to deal with containers, not pods. | 11:12 |
| *** atoth has quit IRC | 11:13 | |
| ltomasbo | I thought the containers in a multi-container pod where meant to share the IP (and communicate among them as normal processes) | 11:13 |
| ltomasbo | *were | 11:14 |
| dulek | ltomasbo: Yes, yes, they are. Just on the low level kubelet invokes CNI commands assuming they work on containers, not whole pods. | 11:15 |
| dulek | ltomasbo: So it has an assumption that DEL request for podA, containerA will not unplug podA, containerB. | 11:15 |
| dulek | ltomasbo: And in Kuryr case it would as we're using names to identify which VIF to unplug. | 11:16 |
| ltomasbo | dulek, and for a 2 container pod, the cni is meant to link the network to both containers? or just to one of them? | 11:16 |
| ltomasbo | IMHO kuryr is providing neutron ports to pods, not to containers, but I understand the problems with the retries | 11:17 |
| dulek | ltomasbo: TBH I haven't checked that. | 11:17 |
| dulek | Okay, so retries were tricky. :) | 11:17 |
| dulek | Now it works much better, you can try to verify. | 11:17 |
| dulek | But I've easily networked 50 pods on my env. | 11:18 |
| ltomasbo | sure, I'll give it a try asap! thanks for the clear explanation! | 11:18 |
| dulek | Some timed out on waiting for VIF annotation, but now with restarts working correctly - it's fine. :) | 11:18 |
| dulek | s/restarts/retries | 11:18 |
| ltomasbo | great! | 11:19 |
| *** yamamoto has quit IRC | 11:51 | |
| *** atoth has joined #openstack-kuryr | 11:59 | |
| *** yamamoto has joined #openstack-kuryr | 12:08 | |
| openstackgerrit | Luis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Add readiness probe to kuryr-controller pod https://review.openstack.org/518502 | 12:09 |
| irenab | dulek, ltomasbo I was trying to catch up on your discussion regarding CNI/CRI kubelet calls. I am still not sure I understand what is the issue kuryr has | 12:20 |
| irenab | dulek, is there any difference in what kuryr does for the forst Pod Container plug versus second one? | 12:21 |
| ltomasbo | irenab, let me try to explain it (to also double check if I got it right) | 12:22 |
| dulek | irenab: No, there isn't a difference. VIF annotation stays the same, maybe only netns id changes. | 12:22 |
| ltomasbo | when there are multiple pods being created, some actions may fail due to timeouts | 12:22 |
| ltomasbo | and the problem is that when the add operation for a container in a pod fails there will be a retry for a new container inside the pod | 12:23 |
| ltomasbo | but the add action for the second container may come before the del action for the failed container | 12:23 |
| irenab | in this case the container id will be different, right? | 12:23 |
| ltomasbo | yep, that is what dulek has fixed, so that if the id is different, the del action is skipped | 12:24 |
| irenab | since it failed to wire it before? | 12:24 |
| irenab | kuryr failed to wire the first container, therefor it is not present? | 12:25 |
| dulek | irenab: Yup, failures where seen most often when ~50 pods were created at once, as kuryr-controller wasn't catching up with annotation pods in time. | 12:25 |
| dulek | (probably Neutron being slow was also an issue) | 12:25 |
| irenab | dulek, agree with ltomasbo , you revealed very interesting issues | 12:26 |
| dulek | irenab: I really hope that's the last one… | 12:26 |
| irenab | dulek, I won't count o it :-) | 12:26 |
| ltomasbo | I wonder if there are other race conditions where we trigger the events in the wrong order | 12:27 |
| dulek | BTW I've described the issue in a bug: https://bugs.launchpad.net/kuryr-kubernetes/+bug/1731485 | 12:27 |
| openstack | Launchpad bug 1731485 in kuryr-kubernetes "Kuryr ignores CNI_CONTAINERID when serving requests" [High,In progress] - Assigned to Michal Dulko (michal-dulko-f) | 12:27 |
| dulek | irenab: Ah, you've already saw it. | 12:27 |
| irenab | yes, but somehow it was a bit confusing why kuryr disconnects the pod | 12:28 |
| dulek | https://bugs.launchpad.net/kuryr-kubernetes/+bug/1731486 - this one is also interesting. Guys from k8s sig-network pointed it out to me. | 12:28 |
| openstack | Launchpad bug 1731486 in kuryr-kubernetes "Kuryr ignores namespaces" [Undecided,New] | 12:28 |
| dulek | irenab: Here's the k8s guys explanation of logic behind those retries: "Yeah. In general you can't rely on the caller remembering what happened last time - due to process crashes it may not have received the result. | 12:29 |
| dulek | So you always have to be prepared for the caller to send you something you didn't expect. | 12:29 |
| dulek | And kubelet takes advantage of this: it deliberately doesn't remember certain things and speculatively calls DEL because it knows you have to deal with it." | 12:29 |
| irenab | we need to have namespace name to be either tagged on port or added to the port name | 12:30 |
| dulek | irenab: Yup! And added to watcher URL-s to make sure we're watching on correct namespace. | 12:30 |
| dulek | Anyway that's separate issue. | 12:30 |
| ltomasbo | how will namespaces fit openstack resources? could it be just different projects? | 12:31 |
| irenab | dulek, and you previously hoped you dealed with last issue... Seems you just started | 12:31 |
| ltomasbo | that way you will not need to add tags/names (and skip neutron calls...) | 12:31 |
| dulek | irenab: I have something with higher priority today, but I can definitely grab that bug when I'll have some more time. | 12:32 |
| irenab | ltomasbo, this is the topic we discussed previously and din't reach consensus. Same project can be mapped to number of namespaces | 12:32 |
| dulek | ltomasbo: I'm not sure if I follow. The only issue we have is that Kuryr assumes names are unique. And they aren't, (namespace, name) pairs are. | 12:33 |
| dulek | ltomasbo: I don't think we need to provide isolation of namespaces - please note that kubernetes doesn't separate networking of different namespaces either. | 12:33 |
| ltomasbo | irenab, but we can have tenants being in different projects, and the projects being mapped to namespaces (1-1) | 12:33 |
| irenab | we will have to deal with it once start Network Policies implementation, since policies are aplicable per namespace | 12:34 |
| ltomasbo | umm | 12:34 |
| dulek | irenab: +1! | 12:34 |
| ltomasbo | perhaps now that we have more info about the network policies | 12:34 |
| ltomasbo | it will be nice to have a call and discuss about the namespaces again | 12:34 |
| irenab | there is a spec for Network Policies that leyal published today | 12:35 |
| irenab | https://review.openstack.org/#/c/519239/ | 12:35 |
| ltomasbo | I'm a bit scare about the amount of calls to neutron... | 12:35 |
| irenab | ltomasbo, agree with you, we will need to check what can be batched | 12:36 |
| ltomasbo | yep | 12:36 |
| irenab | ltomasbo, +1 on renew the discussion on multiple namespaces. I think we probably need some tests that involve multi ns applications | 12:38 |
| dulek | oc | 12:39 |
| dulek | Aww, wrong window. :) | 12:39 |
| ltomasbo | +1 on the tests too | 12:40 |
| ltomasbo | xD | 12:40 |
| *** yboaron_ has quit IRC | 13:23 | |
| *** yboaron has joined #openstack-kuryr | 13:24 | |
| *** yamamoto has quit IRC | 13:24 | |
| *** yboaron has quit IRC | 13:31 | |
| *** yboaron has joined #openstack-kuryr | 13:31 | |
| dulek | Meeting time? | 14:01 |
| irenab | lets start | 14:07 |
| irenab | kuryr meeting is at openstack-meeting-4, sorry for the delay | 14:08 |
| irenab | ltomasbo: dulek leyal joining the meeting? | 14:09 |
| ltomasbo | ups, yep | 14:09 |
| *** garyloug has quit IRC | 14:18 | |
| *** yamamoto has joined #openstack-kuryr | 14:25 | |
| *** yamamoto has quit IRC | 14:34 | |
| *** janki has quit IRC | 14:41 | |
| *** hongbin has joined #openstack-kuryr | 15:05 | |
| *** salv-orlando has quit IRC | 15:15 | |
| *** salv-orlando has joined #openstack-kuryr | 15:15 | |
| *** salv-orlando has quit IRC | 15:20 | |
| *** yboaron has quit IRC | 15:39 | |
| ltomasbo | dulek, I can confirm you were right! | 15:40 |
| ltomasbo | even with the pod in status 'NotReady', I can create/scale pods | 15:40 |
| dulek | ltomasbo: Well, it's not that I'm happy of making your task harder. :P | 15:41 |
| ltomasbo | xD | 15:41 |
| *** yboaron has joined #openstack-kuryr | 15:41 | |
| *** gouthamr_ has joined #openstack-kuryr | 15:41 | |
| ltomasbo | dulek, nice catch! let's see how I can fix it... | 15:41 |
| dulek | ltomasbo: I'd leave the probe exactly as it is - that's still useful piece of information for the admin if we document it. | 15:42 |
| ltomasbo | it was too easy to be true... | 15:42 |
| *** gouthamr_ is now known as gouthamr | 15:42 | |
| dulek | ltomasbo: And meanwhile kuryr-controller should not do Watcher.start until all the ports are recovered. | 15:42 |
| ltomasbo | dulek, yep, I agree that it a good to have, but I'll try to figure out (in a different patch) how to achieve the other behavior too | 15:42 |
| dulek | Cool! :) | 15:43 |
| yboaron | ltomasbo, I have a question regarding : https://review.openstack.org/#/c/518502/ is relevant | 15:58 |
| ltomasbo | yboaron, tell me | 15:58 |
| yboaron | Does readinessProbe is added to yaml only for devstack ? | 15:59 |
| yboaron | From what I saw , it's added only at devstack/lib/kuryr_kuberenets , but maybe I'm missing something .. | 16:00 |
| ltomasbo | yboaron, that is a deployment configuration, it is added to devstack if you deploy with it, and I'll try to add it to openstack-ansible if you deploy it with that: https://github.com/openshift/openshift-ansible/pull/6062 | 16:00 |
| ltomasbo | but you are right, perhaps I need to update some documentation for manual installation about this | 16:01 |
| ltomasbo | or are you missing it in a different place? | 16:01 |
| yboaron | ltomasbo, Yes as you said , thought a bout kuryr-k8s user , that would like to utilize ports pool | 16:02 |
| yboaron | in non devstack environment | 16:02 |
| ltomasbo | yboaron, we only have tools for devstack installation at the kuryr-kubernetes repo, so that is why I only included that way there | 16:03 |
| ltomasbo | but you are right, I should add some note/info somewhere about this... | 16:04 |
| yboaron | OK , got it - devstack is all our world ! :-) thanks | 16:04 |
| ltomasbo | xD | 16:05 |
| ltomasbo | yboaron: https://github.com/openstack/kuryr-kubernetes/blob/master/doc/source/installation/containerized.rst | 16:05 |
| ltomasbo | yboaron, will that be a good place to include that information? | 16:05 |
| yboaron | ltomasbo, looks like that right place | 16:07 |
| yboaron | the | 16:07 |
| ltomasbo | great! thanks! I'll add it there then | 16:07 |
| yboaron | ltomasbo, thanks | 16:08 |
| *** salv-orlando has joined #openstack-kuryr | 16:16 | |
| *** salv-orlando has quit IRC | 16:21 | |
| *** yboaron has quit IRC | 16:24 | |
| dulek | yboaron, ltomasbo: We have a script generating yamls for general k8s use: https://docs.openstack.org/kuryr-kubernetes/latest/installation/containerized.html#generating-kuryr-resource-definitions-for-kubernetes | 16:37 |
| dulek | Those use the same functions as DevStack, so adding probe to DevStack will add it to scripts as well. | 16:37 |
| *** pcaruana has quit IRC | 16:49 | |
| *** salv-orlando has joined #openstack-kuryr | 17:09 | |
| *** dougbtv__ has joined #openstack-kuryr | 17:14 | |
| *** janonymous has quit IRC | 17:20 | |
| *** dougbtv__ has quit IRC | 18:12 | |
| *** aojea has joined #openstack-kuryr | 18:21 | |
| openstackgerrit | Michał Dulko proposed openstack/kuryr-kubernetes master: Prevent pyroute2.IPDB threads leaking https://review.openstack.org/517406 | 18:34 |
| openstackgerrit | Michał Dulko proposed openstack/kuryr-kubernetes master: CNI split - introducing CNI daemon https://review.openstack.org/515186 | 18:34 |
| openstackgerrit | Michał Dulko proposed openstack/kuryr-kubernetes master: Support kuryr-daemon when running containerized https://review.openstack.org/518024 | 18:34 |
| *** aojea has quit IRC | 19:14 | |
| *** atoth has quit IRC | 20:09 | |
| *** salv-orlando has quit IRC | 20:28 | |
| *** salv-orlando has joined #openstack-kuryr | 20:28 | |
| *** salv-orlando has quit IRC | 20:33 | |
| *** aojea has joined #openstack-kuryr | 20:33 | |
| *** salv-orlando has joined #openstack-kuryr | 21:00 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/fuxi master: Updated from global requirements https://review.openstack.org/519094 | 21:06 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/fuxi master: Updated from global requirements https://review.openstack.org/519094 | 21:08 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/fuxi master: Updated from global requirements https://review.openstack.org/519094 | 21:08 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/fuxi master: Updated from global requirements https://review.openstack.org/519094 | 21:09 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/fuxi master: Updated from global requirements https://review.openstack.org/519094 | 21:09 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements https://review.openstack.org/516936 | 21:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements https://review.openstack.org/516937 | 21:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements https://review.openstack.org/509781 | 21:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements https://review.openstack.org/516936 | 21:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements https://review.openstack.org/516937 | 21:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements https://review.openstack.org/509781 | 21:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements https://review.openstack.org/516937 | 21:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements https://review.openstack.org/509781 | 21:11 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements https://review.openstack.org/516936 | 21:12 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements https://review.openstack.org/516937 | 21:12 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements https://review.openstack.org/509781 | 21:12 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements https://review.openstack.org/516936 | 21:17 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements https://review.openstack.org/516937 | 21:17 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements https://review.openstack.org/509781 | 21:17 |
| *** fkautz_ has joined #openstack-kuryr | 21:46 | |
| *** fkautz has quit IRC | 21:51 | |
| *** nhlfr has quit IRC | 21:51 | |
| *** fkautz_ is now known as fkautz | 21:51 | |
| *** Guest57502 has quit IRC | 22:00 | |
| *** aojea has quit IRC | 22:01 | |
| *** aojea has joined #openstack-kuryr | 22:02 | |
| *** aojea has quit IRC | 22:06 | |
| *** Guest54320 has joined #openstack-kuryr | 22:10 | |
| *** dougbtv__ has joined #openstack-kuryr | 22:10 | |
| *** nhlfr has joined #openstack-kuryr | 22:15 | |
| *** dougbtv__ has quit IRC | 22:29 | |
| *** pmannidi has joined #openstack-kuryr | 22:46 | |
| *** gouthamr has quit IRC | 23:09 | |
| openstackgerrit | Hongbin Lu proposed openstack/kuryr-libnetwork master: Introduce sriov port driver https://review.openstack.org/500436 | 23:21 |
| *** salv-orlando has quit IRC | 23:37 | |
| *** salv-orlando has joined #openstack-kuryr | 23:38 | |
| openstackgerrit | Hongbin Lu proposed openstack/kuryr-libnetwork master: Add debug statement for response data https://review.openstack.org/519507 | 23:40 |
| *** salv-orlando has quit IRC | 23:42 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!