Wednesday, 2017-06-28

« Tuesday, 2017-06-27 Index Thursday, 2017-06-29 »
*** atoth has quit IRC00:16
*** tonanhngo has quit IRC00:18
*** tonanhngo has joined #openstack-kuryr00:18
*** tonanhngo has quit IRC00:18
*** salv-orl_ has joined #openstack-kuryr00:37
*** salv-orlando has quit IRC00:40
*** hongbin has joined #openstack-kuryr00:49
*** kiennt has joined #openstack-kuryr00:55
*** hongbin has quit IRC01:00
*** caowei has joined #openstack-kuryr01:07
kienntHi, the patchset https://review.openstack.org/#/c/462106/ still failed, because some testcases. My patchset fixes this problem (https://review.openstack.org/#/c/477427/), but need core reviewers check it.02:00
*** hongbin has joined #openstack-kuryr02:16
*** c00281451__ is now known as zengchen02:33
*** caowei_ has joined #openstack-kuryr03:04
*** caowei has quit IRC03:07
*** caowei_ is now known as caowei03:07
*** caowei_ has joined #openstack-kuryr03:21
*** caowei has quit IRC03:25
*** caowei_ is now known as caowei03:25
*** vikasc has joined #openstack-kuryr03:56
*** hongbin has quit IRC03:58
*** sridhar_ram has joined #openstack-kuryr04:12
*** yamamoto has joined #openstack-kuryr05:34
*** kiennt has quit IRC05:47
*** kiennt has joined #openstack-kuryr05:56
*** salv-orl_ has quit IRC06:10
*** kiennt has quit IRC06:10
*** salv-orlando has joined #openstack-kuryr06:10
*** kiennt has joined #openstack-kuryr06:14
*** salv-orlando has quit IRC06:15
*** salv-orlando has joined #openstack-kuryr06:21
*** salv-orl_ has joined #openstack-kuryr06:37
*** salv-orlando has quit IRC06:40
*** rwallner has quit IRC06:44
*** rwallner has joined #openstack-kuryr06:44
*** yboaron has joined #openstack-kuryr06:50
*** yamamoto has quit IRC06:55
*** yamamoto has joined #openstack-kuryr07:04
*** kzaitsev_mb has quit IRC07:09
*** aojea has joined #openstack-kuryr07:23
*** egonzalez has joined #openstack-kuryr07:42
*** sridhar_ram has quit IRC08:02
*** kzaitsev_mb has joined #openstack-kuryr08:09
*** aojea has quit IRC08:12
*** aojea has joined #openstack-kuryr08:13
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Gate test DNM  https://review.openstack.org/47842808:18
*** kzaitsev_ws has joined #openstack-kuryr08:20
kzaitsev_wsapuimedo: are you back? =)08:21
*** vikasc has quit IRC08:37
*** garyloug has joined #openstack-kuryr08:40
dmelladoheh not yet08:41
dmelladobut I've a dreaded gate-gate waiting for him08:42
*** vikasc has joined #openstack-kuryr08:55
*** aojea has quit IRC09:12
*** aojea has joined #openstack-kuryr09:12
*** yamamoto has quit IRC09:13
kzaitsev_wsdmellado: where is he travelling btw? =)09:14
dmelladooh, he's headed to a meeting near boston that I got lucky enough to avoid xD09:15
kzaitsev_wsoh boston.09:15
kzaitsev_wsI wish to visit it someday %)09:15
kzaitsev_wssinging "I'm shipping up to Boston!"09:16
dmelladoheh xD09:16
dmelladoI recall seeing dropkick murphys live a few years ago xXD09:17
*** yamamoto has joined #openstack-kuryr09:17
*** pcaruana has joined #openstack-kuryr09:28
kzaitsev_wslucky you =)09:29
kzaitsev_wsthere's an irish pub in moscow, styled after irish village house. every 2 hours or so they play Shipping to Boston and everyone starts tapping glasses against the tables.09:31
kzaitsev_wshaven't been there in a while, though (=09:31
*** caowei_ has joined #openstack-kuryr09:38
*** caowei has quit IRC09:42
*** caowei_ is now known as caowei09:42
dmelladoheh, sounds funny xD09:45
*** aojea has quit IRC09:51
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV documentation  https://review.openstack.org/47845809:55
*** aojea has joined #openstack-kuryr09:55
*** rwallner has quit IRC09:56
*** aojea_ has joined #openstack-kuryr09:58
*** aojea has quit IRC10:01
*** yamamoto has quit IRC10:08
*** yamamoto has joined #openstack-kuryr10:13
*** yamamoto has quit IRC10:15
*** kiennt has quit IRC10:21
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846510:24
*** yamamoto has joined #openstack-kuryr10:25
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Allow passing multiple VIFs to CNI  https://review.openstack.org/47101210:26
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV binding driver to CNI  https://review.openstack.org/46245610:26
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV capabilities to VIF handler  https://review.openstack.org/46245510:26
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV documentation  https://review.openstack.org/47845810:26
kzaitsev_wsa tiny bit of a rebase =)10:26
*** caowei_ has joined #openstack-kuryr10:29
kzaitsev_wsdmellado: copy command looks wierd in your ^^^ patch10:31
dmelladohey kzaitsev_ws10:31
dmelladoi.e. echo ~stack10:31
dmelladowould output /opt/stack/new10:31
dmelladoouch, you're right10:32
dmelladoI need coffee xD10:32
*** caowei has quit IRC10:32
*** caowei_ is now known as caowei10:32
kzaitsev_wsyeah it should probably be `cp -r "smth/smth/.kube"`10:33
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846510:33
kzaitsev_wsdmellado: but I think you're still copying .kube/config to /home/tempest, instead of /home/tempest/.kube/10:35
dmelladokzaitsev_ws: and I said I needed coffee10:35
kzaitsev_ws(=10:35
* dmellado facepalms10:35
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846510:37
dmelladokzaitsev_ws: sorry on this xD10:38
dmelladoI've been debugging this for days and it's starting to get to me xD10:38
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846510:41
* dmellado gets for a coffee before he does more stupid mistakes10:41
dmelladoxD10:41
kzaitsev_wshm. I'm afraid I still got bad news for you )10:41
kzaitsev_ws$ x=teferi; echo ~$x "~$x" ~teferi "~teferi"10:41
kzaitsev_ws~teferi ~teferi /home/teferi ~teferi10:41
kzaitsev_wsI'm on bash 4.3 =)10:42
dmelladohmmm it did work when I tested it on the upstream gate clone10:43
dmelladolet's wait for the gate output ;)10:43
kzaitsev_wsyeah. it should be in the logs10:43
*** yamamoto has quit IRC10:48
*** yamamoto has joined #openstack-kuryr10:49
kzaitsev_wsand another round of rebasing. things get wierd when code is based on outdated master10:56
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV binding driver to CNI  https://review.openstack.org/46245610:56
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV capabilities to VIF handler  https://review.openstack.org/46245510:56
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV documentation  https://review.openstack.org/47845810:56
dmelladoheh, totally11:00
dmelladoif it gets to the point when you have depends-on patches11:00
dmelladoit gets trickier11:00
*** caowei has quit IRC11:07
*** rwallner has joined #openstack-kuryr11:08
kzaitsev_wsoh, i can remove that11:10
kzaitsev_wsit's just my colleagues here asked me for a quick doc on how to configure sriov, so I decided to write it upstream-first. but the code was based on a branch without documentation update11:11
*** atoth has joined #openstack-kuryr11:11
kzaitsev_wsso i added a depends-on, that highlighted that there would be a merge-conflict (or rather broken tests) in the current state %)11:12
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add SR-IOV documentation  https://review.openstack.org/47845811:12
vikasckzaitsev_ws, dmellado : did you guys get chance to take a look at this? https://review.openstack.org/#/c/477066/ :)11:19
kzaitsev_wsI read it through once or twice =) I think I even had a question or two. let me recall11:21
vikascsure11:22
kzaitsev_wsvikasc: ah. you mention you want to use OIR to request networks. I'm not sure how that should work. can you elaborate?11:23
vikasckzaitsev_ws, since scheduler understands OIR only, we can have a OIR name to represent each network object11:24
kzaitsev_wsbut OIR is finite and integer (hence the name =)) how much of such resource should be available? and on which nodes?11:25
vikasckzaitsev_mb, just OIR name is not sufficient to hold all the information encoded in string11:25
vikasckzaitsev_ws, right, so admin would patch node status with capacity11:26
vikasckzaitsev_ws, network object is just to hold/store network metadata11:26
kzaitsev_wsI'm not sure I understand what the capacity should be then.11:27
vikasckzaitsev_ws, capacity would be for example allowed VFs for the vif-type that netwok object is targetting11:28
kzaitsev_wswouldn't node-affinity or taints/toleration fit the model better?11:28
vikasckzaitsev_ws, taints and tolerations will also be used to create dedicated scheduling domains.11:28
vikascTaints and tolerations cannot help keep accounting of number of devices remaining on each node11:29
kzaitsev_wsok. let me explain how I understand what you want to do and you will correct me where I'm wrong.11:29
kzaitsev_wsor where I got you wrong )11:29
vikascsure11:30
vikascgo ahead11:30
vikasci think it will be easier to dicuss over the patch :)11:30
dmelladovikasc: I didn't but I will review it ;)11:31
vikascwe can have a first pass here as well :)11:31
vikascdmellado, thanks :)11:31
kzaitsev_ws1st) you create a bunch of TPR/CRD objects in k8s. they hold info of the networks we will use (probably ids of those networks too?). 2) Then you assign k8s nodes with OIR for names of those networks with some arbitrary amount (100/1000 per node?) 3) You create a pod that requests said OIR. k8s schedules it to one of the nodes, that has it. 4) kuryr-k8s reads requests and allocates additional11:35
kzaitsev_wsports on said networks. is that right?11:35
vikascon 1st -->11:37
vikascneutron network id will not be there. Network objects would correspond to a neutron subnet rather neutron network. So CIDR and may be subnet id.11:38
kzaitsev_wsyeah. s/nets/subnets/11:38
vikascon 4) , right, controller will use oir as a refernce to fetch network object and thus all the network details11:39
kzaitsev_wsemm, I don't think CIDRs are globaly unique11:39
vikascso yes, you got me right. taints and tolerations is a best practice tip/suggestion11:39
kzaitsev_wsI think affinity may be used instead https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity11:40
vikascthere network objects are namespaced objects, and each k8s namespace will map to a neutron network11:40
vikascproblem with affinity is that for normal workload pods, anti-affinity will be used11:41
vikascto avoid normal pods get scheduled on special nodes11:41
vikascit can be done with affinity/anti-affinity, IMO taints and tolerations are a better approach11:42
kzaitsev_wsbut you would only need that whole mechanism if you want some nodes to *not* have pods from certain networks11:43
kzaitsev_wsi.e. the whole affinity/taint mechanism11:43
vikascand another problem with affinity is that when you add a new special node to cluster, affinity and anti-affinity for all the existing pods will have to be updated.11:43
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846511:44
vikascanyways thats upto user whether he want to use affinity or taints11:44
vikasckuryr need not to add any handling for either11:44
vikasckzaitsev1pi, nodes to *not* have pods from certain networks,11:45
vikasckzaitsev_ws, generally special nics like sriov or may be dpdk in future or some other are special in sense that these are expensive hw and should be used wisely11:46
vikasckzaitsev_mb, so it would make sense to avoid normal pods getting scheduled to these special nodes11:47
vikasckzaitsev_mb, as i said, its upto user deployment choice.11:47
kzaitsev_wswell, imo sriov maps real nice to OIR, since you can only have so much VF from a PF11:48
vikasckzaitsev_mb, right, so what is your concern11:49
kzaitsev_wsdon't you think that you're trying to solve two tasks at the same time? multi-network pods and pod scheduling (which is not part of what kuryr-k8s does)?11:49
kzaitsev_wsI don't entirelly understand your usecase tbh11:50
vikascwhat is being talked as multi-networks (which is multiple interfaces in container) is essentially same as multi-vif11:50
*** salv-orl_ has quit IRC11:51
*** salv-orlando has joined #openstack-kuryr11:51
vikascif you mention specifically what point you are not understanding, may be i can explain11:51
kzaitsev_wsI imagined, that multi-vif should allow VIFs from different networks(not only subnetworks)11:52
kzaitsev_wsvikasc: your usecase, that you're trying to cover =)11:53
vikascif you follow discussions/proposals on multi-network at signetwork, those are multi-nic only11:53
vikasci am trying to address multi-nic functionality, which is being refered as multi-network at sig-network since some time now11:54
vikascwhile doing so, i observed that multi-vif work that you are doing can be used as a component in this.11:55
kzaitsev_wscan you link pls? I'm reading slack and didgests, but it's hard to follow everything =)11:55
vikascsure11:55
*** salv-orlando has quit IRC11:56
kzaitsev_wsand so far it just seems to me that kuryr multi-vif does not need taints/tolerations/etc11:56
vikasckzaitsev1pi, this is the root proposal, https://docs.google.com/document/d/1TW3P4c8auWwYy-w_5afIPDcGNLK3LZf0m14943eVfVg/edit?ts=58877ea711:56
kzaitsev_wsif you just want a pod with interfaces from 2 different nets/subnets — there should not be a restriction on where this pod runs11:56
kzaitsev_wsam I wrong with that?11:57
vikasckzaitsev1pi, but after lots of discussions, current state is that network objects are not going to be k8s native11:57
kzaitsev_wshow does it affect my usecase? =)11:58
vikaschttps://groups.google.com/forum/#!topic/kubernetes-sig-network/8nDSQ2hF40w11:58
vikasci will respond one-by-one to your above statements :)11:59
kzaitsev_wssure. sorry if I'm frustrating you =)11:59
vikascno, not at all11:59
vikasc:)11:59
vikasctaints are tolerations are not needed by kuryr in any case, it just an advice to user to use wisely expensive resources12:00
vikascnext12:01
kzaitsev_wsphew. makes sense )12:01
vikascthere should not be a restriction on where this pod runs12:01
*** pcaruana has quit IRC12:02
vikascthere should be restrictions because all nodes might not have the requested networks12:02
*** pcaruana has joined #openstack-kuryr12:02
vikascplease read nic/network12:02
vikascand network is not neutron network12:03
vikascdoes my point on restriction makes sense to you?12:04
vikascif not i will reword and elaborate :)12:04
*** janki has joined #openstack-kuryr12:07
kzaitsev_wsvikasc: does network mean a different cni driver here?12:08
vikasckzaitsev1pi, no, network means a nic in container and at kuryr side, handled by multi-vif work that you doing12:08
vikasckzaitsev1pi, its same as what you wrote in your srioc spec, just one difference, network metadata in network objects12:09
vikascs/sriov12:09
vikasckzaitsev_ws, its kind of enhancement to generalize your work12:10
vikasckzaitsev_ws, just an idea to discuss over. spec is added only for discussion. :)12:12
openstackgerritDanil Golov proposed openstack/kuryr-kubernetes master: Allow setting specific ports for SRIOV handler  https://review.openstack.org/47849412:13
vikasckzaitsev_ws, you might be interested, https://docs.google.com/document/d/1mNZZ2lL6PERBbt653y_hnck3O4TkQhrlIzW1cIc8dJI/edit12:14
kzaitsev_wsso to request pod from several networks I would probably add several tolerations to it?12:14
kzaitsev_wsyeah, I'll read through the docs +)12:14
kzaitsev_wsand nodes might (or might not) have taints for those networks?12:15
*** pcaruana has quit IRC12:16
vikasckzaitsev_ws, right, if admin wants to have dedicated nodes12:17
vikasckzaitsev_mb, as i said , kuryr is not bothered about taints/tolerations12:17
vikasckzaitsev_ws, it is cluster admin decision12:17
kzaitsev_wsok, I think now I have a bit better understanding of what's happening12:18
kzaitsev_ws%)12:18
vikasckzaitsev_mb, in worse case it might happen that there are some pods which dont need for example sriov nic but got scheduled on nodes that have sriovs and consumed all12:18
vikasckzaitsev_mb, i envision that your multi-vif work and Luis's multi-subnet work are solutions to same problem, multi-nic12:19
kzaitsev_wsvikasc: that wouldn't happen with my current approach, btw.12:20
vikasckzaitsev_mb, how that wont happen with your current approach12:20
vikasckzaitsev_mb, if a pod does not request sriov nic, how it scheduler make sure that it does not get scheduled on node that has sriov12:21
vikasccapabilities12:21
kzaitsev_wsThat would be a problem only if traffic from regular network and sriov would be using the same network. even then the card would be responsible for handling this. the traffic would probably go through PF, while pods get the VF12:22
kzaitsev_wsvikasc: why would you not want it to be scheduled there?12:22
kzaitsev_wsif it only needs high-speed VF it's ok to schedule other pods there12:22
*** pcaruana has joined #openstack-kuryr12:23
vikasckzaitsev_mb, because that pod might consume memory/cpu resources of the nodes12:23
*** pcaruana has quit IRC12:23
vikasckzaitsev_mb, i mean normal pods may exhaust memory/cpu resources of special nodes12:23
kzaitsev_wsvikasc: that is not about network at all. we're both following sig-resource-management. they have a dedicated CPUs initiative12:23
*** pcaruana has joined #openstack-kuryr12:23
kzaitsev_wsif you need a dedicated CPU — you ask for it in the requests section, same with memory12:24
vikasckzaitsev_mb, i am working or resource classes PoC12:24
vikasckzaitsev_mb, https://asciinema.org/a/ak6rx6j308x9m9j6mjwhf6rym12:25
vikasc:)12:25
vikasckzaitsev_mb, sorry for distraction,12:26
vikasckzaitsev_mb, let me put my point with an example12:26
kzaitsev_wsvikasc: it might happen, that special pods, will drain CPU from a sriov node, yes. but that's solvable with taints/tolerations12:26
vikasckzaitsev_mb, thats what i am saying12:26
vikasckzaitsev_mb, ditto.12:27
vikasc:)12:27
*** yamamoto has quit IRC12:27
vikasckzaitsev_mb, not just special pods, normal pods can also drain cpu/memory from sriov node, if taints/tolerations are not used12:27
vikasckzaitsev_mb, so what should we discuss now12:28
vikasckzaitsev_mb, what is your another concern12:28
*** pcaruana has quit IRC12:29
*** yamamoto has joined #openstack-kuryr12:30
kzaitsev_wsvikasc: ok. so the usecase you're trying to solve: 1) allow pod to request multiple interfaces 2) allow admin to optionally configure which nodes have access to these networks?12:30
*** yamamoto has quit IRC12:30
vikasckzaitsev_mb, yes, plus a dynamic way to configure networks like physnet to subnet mappings, instead in kuryr.conf12:33
*** janki has quit IRC12:33
vikasckzaitsev_mb, using kubectl end-user(non-admi) will also be able to see network metadata/configuration12:34
vikascs/admin12:34
vikasckzaitsev_mb, i need to jump on a meeting. Thanks for the discussion, lets continue over the patch further. :)12:36
kzaitsev_wsok. so in your scenario we hold metadata in TPR(or whatever k8s replaces them with =)) and pods request them in tolerations.12:37
*** pcaruana has joined #openstack-kuryr12:37
kzaitsev_wsok, I think I've grasped the big picture =)12:37
vikasckzaitsev_ws, exactly12:37
vikasc:) thanks a lot12:37
vikascplease do watch  https://asciinema.org/a/ak6rx6j308x9m9j6mjwhf6rym :)12:38
vikasckzaitsev_ws, resource classes are next gen OIR12:39
kzaitsev_wsyeah, I've seen those. I just hope k8s does not remove OIR before these are ready12:41
*** kiennt has joined #openstack-kuryr12:41
vikasckzaitsev_ws, i dont think so.12:42
vikasckzaitsev_mb, i presented this resource class demo at RMWGM12:42
kzaitsev_wswith the current plan the resource classes are planned to land around 1.10 so I hope we'll be able to merge sriov based on oir and we'll have some time to update it to resource cleasses after12:42
vikasckzaitsev_ws, i too think so12:43
*** pcaruana has quit IRC12:43
kzaitsev_wsvikasc: when was that? I maybe attended =)12:43
kzaitsev_wsaren't you supposed to go on a meeting? =)12:43
*** pcaruana has joined #openstack-kuryr12:44
vikasckzaitsev_ws, i am on it12:44
vikasc:)12:44
kzaitsev_wsok, sounds like a boring meeting then12:44
kzaitsev_ws(=12:44
vikasc:) kinda12:44
*** yamamoto has joined #openstack-kuryr12:49
*** yamamoto has quit IRC12:52
*** pcaruana has quit IRC12:53
kzaitsev_wsdmellado: hm. the job has ended, but the logs are empty. Or do we need to launch a special job?12:58
kzaitsev_wshttp://logs.openstack.org/65/478465/5/check/gate-install-dsvm-default-kuryr-kubernetes/60d11a0/logs/devstacklog.txt.gz12:58
kzaitsev_wshttp://logs.openstack.org/65/478465/5/check/gate-install-dsvm-default-kuryr-kubernetes/60d11a0/logs/devstacklog.txt.gz#_2017-06-28_12_13_50_92312:58
kzaitsev_wsoh yeah. 1 means disabled =/13:00
*** gouthamr has joined #openstack-kuryr13:01
dmelladooh, /me stupid13:03
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846513:03
dmelladostack home = /opt/stack/new13:03
*** pcaruana has joined #openstack-kuryr13:05
kzaitsev_wsdmellado: ~/home/$tempest_user -> /home/$tempest_user ?13:06
dmelladokzaitsev_ws: ??13:08
dmelladodeff not my day13:08
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846513:08
dmelladoI'm gonna get some rest, I've been getting hit by the alergy and making mistakes all day13:08
dmelladoo/13:08
kzaitsev_wsdmellado: just one of those days =))13:09
*** yamamoto has joined #openstack-kuryr13:10
*** pcaruana has quit IRC13:13
*** pcaruana has joined #openstack-kuryr13:14
*** kzaitsev_ws has quit IRC13:14
*** kzaitsev_ has joined #openstack-kuryr13:15
kzaitsev_dmellado: its from a song :)13:17
dmelladokzaitsev_: ?13:18
kzaitsev_nevermind, I'm on a phone and might be answering old messages :)13:20
dmelladoheh, no worries! but now I'm curious about the song13:20
*** kzaitsev_ has quit IRC13:23
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846513:36
*** yboaron has quit IRC13:37
*** pcaruana has quit IRC13:40
*** pcaruana has joined #openstack-kuryr13:46
*** gouthamr has quit IRC13:52
*** aojea_ has quit IRC14:01
*** aojea has joined #openstack-kuryr14:05
*** gouthamr has joined #openstack-kuryr14:05
*** hongbin has joined #openstack-kuryr14:21
*** aojea_ has joined #openstack-kuryr14:28
*** aojea has quit IRC14:30
*** gouthamr has quit IRC14:34
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Skip test_list_pods  https://review.openstack.org/47852414:35
*** salv-orlando has joined #openstack-kuryr14:37
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Skip test_list_pods  https://review.openstack.org/47852414:37
openstackgerritDaniel Mellado proposed openstack/kuryr-tempest-plugin master: Skip test_list_pods  https://review.openstack.org/47852414:39
dmelladoheh, it actually works!14:41
dmelladoapuimedo: it liveeees14:41
dmelladoit's alive! xD14:41
*** gouthamr has joined #openstack-kuryr14:43
*** rwallner has quit IRC14:50
*** rwallner has joined #openstack-kuryr14:56
*** edisonxiang has quit IRC15:12
*** edisonxiang has joined #openstack-kuryr15:13
*** inc0 has quit IRC15:33
*** salv-orlando has quit IRC15:44
*** salv-orlando has joined #openstack-kuryr15:45
*** aojea_ has quit IRC15:49
*** salv-orlando has quit IRC15:49
*** garyloug has quit IRC15:53
*** salv-orlando has joined #openstack-kuryr16:00
*** garyloug has joined #openstack-kuryr16:00
*** kiennt has quit IRC16:06
*** egonzalez has quit IRC16:17
*** atoth has quit IRC16:54
*** salv-orlando has quit IRC17:10
*** salv-orlando has joined #openstack-kuryr17:10
*** salv-orlando has quit IRC17:15
*** aojea has joined #openstack-kuryr17:21
*** neiljerram has quit IRC17:22
*** tonanhngo has joined #openstack-kuryr17:23
*** aojea has quit IRC17:25
*** tonanhngo has quit IRC17:28
*** gouthamr has quit IRC17:34
*** tonanhngo has joined #openstack-kuryr17:42
*** tonanhngo has quit IRC17:47
*** tonanhngo has joined #openstack-kuryr17:53
*** garyloug has quit IRC17:55
*** tonanhngo has quit IRC17:58
*** tonanhngo has joined #openstack-kuryr17:59
*** tonanhngo has quit IRC18:03
*** tonanhngo has joined #openstack-kuryr18:05
*** tonanhngo has quit IRC18:10
*** yamamoto has quit IRC18:11
*** rwallner has quit IRC18:17
*** rwallner_ has joined #openstack-kuryr18:20
*** rwallner_ has quit IRC18:25
*** janki has joined #openstack-kuryr18:33
*** aojea has joined #openstack-kuryr18:38
*** kzaitsev_mb has quit IRC19:04
*** rwallner has joined #openstack-kuryr19:09
*** yamamoto has joined #openstack-kuryr19:12
*** tonanhngo has joined #openstack-kuryr19:12
*** rwallner has quit IRC19:14
*** rwallner has joined #openstack-kuryr19:14
*** rwallner has quit IRC19:15
*** rwallner has joined #openstack-kuryr19:15
*** tonanhngo has quit IRC19:16
*** yamamoto has quit IRC19:16
*** tonanhngo has joined #openstack-kuryr19:24
*** tonanhngo has quit IRC19:29
*** tonanhngo has joined #openstack-kuryr19:33
*** salv-orlando has joined #openstack-kuryr19:44
apuimedodmellado: awesome20:09
apuimedoirenab: kzaitsev1pi: could we set up some time on Monday to go over the multi-vif patches on bluejeans?20:10
apuimedoand whoever else wants to join, of course20:10
apuimedovikasc: svinota published pyroute2 0.4.17 (with the fixes I sent for pyinstaller). Could you send the patch to openstack/requirements to bump the req to it?20:14
*** yamamoto has joined #openstack-kuryr20:14
openstackgerritMerged openstack/kuryr-kubernetes master: Copy kubeconfig to tempest dir  https://review.openstack.org/47846520:14
openstackgerritMerged openstack/kuryr-kubernetes master: Adding a default ETCD_PORT to devstack settings for legacy_etcd  https://review.openstack.org/47672920:14
*** yamamoto has quit IRC20:23
*** garyloug has joined #openstack-kuryr20:43
*** garyloug has quit IRC21:00
*** pcaruana has quit IRC21:01
*** jchhatbar has joined #openstack-kuryr21:50
*** janki has quit IRC21:51
*** jchhatbar has quit IRC22:10
*** salv-orl_ has joined #openstack-kuryr22:14
*** tonanhngo has quit IRC22:16
*** salv-orlando has quit IRC22:18
*** tonanhngo has joined #openstack-kuryr22:21
*** tonanhngo has quit IRC22:25
*** aojea has quit IRC22:29
*** gouthamr has joined #openstack-kuryr22:50
*** gouthamr has quit IRC22:54
*** salv-orl_ has quit IRC22:59
*** hongbin has quit IRC23:44
« Tuesday, 2017-06-27 Index Thursday, 2017-06-29 »

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