Monday, 2017-04-17

*** jayahn has joined #openstack-kuryr00:28
*** jayahn has quit IRC00:56
*** jayahn has joined #openstack-kuryr00:58
*** tonanhngo has joined #openstack-kuryr01:00
*** tonanhngo has quit IRC01:01
*** yedongcan has joined #openstack-kuryr01:14
*** limao has joined #openstack-kuryr01:18
openstackgerritHongbin Lu proposed openstack/kuryr-kubernetes master: [WIP] Spec for fuxi-kubernetes  https://review.openstack.org/45255401:26
*** jayahn has quit IRC01:41
*** tonanhngo has joined #openstack-kuryr01:42
*** tonanhngo has quit IRC01:42
*** jayahn has joined #openstack-kuryr01:44
*** yamamoto has joined #openstack-kuryr01:45
*** jayahn has quit IRC02:06
*** yamamoto has quit IRC02:23
*** yamamoto has joined #openstack-kuryr02:30
*** tonanhngo has joined #openstack-kuryr02:44
*** shu-mutou-AWAY has joined #openstack-kuryr02:44
*** tonanhngo has quit IRC02:44
*** shu-mutou-AWAY is now known as shu-mutou02:44
*** hongbin has joined #openstack-kuryr02:52
*** yamamoto has quit IRC02:56
*** aojea has joined #openstack-kuryr03:01
*** aojea has quit IRC03:05
*** jayahn has joined #openstack-kuryr03:15
*** Guest32684 has joined #openstack-kuryr03:34
*** yamamoto has joined #openstack-kuryr03:45
*** tonanhngo has joined #openstack-kuryr03:45
*** tonanhngo has quit IRC03:46
*** Guest32684 has quit IRC04:09
*** hongbin has quit IRC04:20
*** shu-mutou has left #openstack-kuryr04:37
*** limao has quit IRC04:50
*** limao has joined #openstack-kuryr05:18
*** kzaitsev_ws has joined #openstack-kuryr06:08
*** janki has joined #openstack-kuryr06:17
*** jayahn has quit IRC06:26
kzaitsev_wsivc-: ping. May I ask you a few questions on future design of kuryr-k8s?07:21
kzaitsev_wsI mean you seem to have mentioned previous discussions in your comments =) and I have a couple of questions about them07:22
*** vikasc has quit IRC08:35
*** vikasc has joined #openstack-kuryr08:37
*** jchhatbar has joined #openstack-kuryr08:38
*** janki has quit IRC08:41
*** yedongcan has quit IRC08:47
*** egonzalez has joined #openstack-kuryr08:47
*** aojea has joined #openstack-kuryr08:48
*** yedongcan has joined #openstack-kuryr08:50
*** aojea has quit IRC08:55
*** jchhatbar_ has joined #openstack-kuryr08:59
*** jchhatbar has quit IRC09:02
*** aojea has joined #openstack-kuryr09:07
*** kzaitsev_ws has quit IRC09:11
*** kzaitsev_ws has joined #openstack-kuryr09:11
*** limao has quit IRC09:25
*** limao has joined #openstack-kuryr09:26
*** limao has quit IRC09:30
*** aojea has quit IRC09:39
*** aojea has joined #openstack-kuryr09:40
*** aojea has quit IRC09:44
*** jchhatbar has joined #openstack-kuryr10:31
ivc-kzaitsev_ws pong10:31
*** aojea has joined #openstack-kuryr10:31
*** jchhatbar_ has quit IRC10:33
*** jchhatbar_ has joined #openstack-kuryr10:34
*** jchhatbar has quit IRC10:36
*** janki has joined #openstack-kuryr10:42
*** jchhatbar_ has quit IRC10:42
*** jchhatbar has joined #openstack-kuryr10:46
*** janki has quit IRC10:48
kzaitsev_wsivc-: oh, sry =) I wanted to ask — what are the plans for KuryrK8sService handler registration?11:11
ivc-kzaitsev_ws soz on a meeting now. will be back in about 30 minutes or so11:12
kzaitsev_wssure np =)11:12
kzaitsev_wsI'll put my thoughts/questions here meanwhile11:13
*** yedongcan has left #openstack-kuryr11:14
kzaitsev_wsI think I saw you mention, that you already discussed making pipeline handlers configurable somewhere.11:14
*** dougbtv_ is now known as dougbtv11:16
*** aojea has quit IRC11:18
*** aojea has joined #openstack-kuryr11:18
kzaitsev_wsI want to allow Pods to request multiple additional ports from neutron.11:20
kzaitsev_wsSo I was thinking about writing a separate handler to kuryr-k8s and then a separate cni (and use kuryr-cni and my onw via multus-cni)11:21
*** aojea has quit IRC11:23
kzaitsev_wsThe CNI in turn would pass interfaces from host to Pods namespace. much like sriov-cni does =)11:24
*** reedip is now known as reedip_afk11:26
kzaitsev_wsI'm afraid this kind of change would be hard to upstream though.11:26
kzaitsev_wsI can imagine adding requests for multiple IPs (and possibly requesting specific IP at Pod creation time) added to kuryr-k8s11:27
kzaitsev_wsbut interface passthrough feels out of scope of kuryr-cni11:28
kzaitsev_wsso I wanted to ask for opinions11:29
kzaitsev_wsif we make handlers configurable/dynamic (through stevedore for example) it would enable makeing rather custom configurations. And I would probably be able to share mine somewhere under /contrib11:30
kzaitsev_wsivc-: would love to hear your thoughts on ^^^ =)11:31
dmelladokzaitsev_ws: that looks like an interesting idea that con be drafted on a spec ;)11:31
*** jchhatbar has quit IRC11:32
*** jchhatbar has joined #openstack-kuryr11:33
kzaitsev_wsdmellado: yeah =) but I'd like to get some preliminary opinions on design )11:39
ivc-kzaitsev_ws multi-port support for pods has been discussed many times. there are some proposed changes to k8s itself that will add 'network' entity to api11:39
dmelladoIIRC we discussed also the idea of having multiple CNIs11:39
* dmellado just came back from PTO, so still unsure11:39
dmelladoxD11:39
kzaitsev_wsyep, I've see those, but they're in design stages, right?11:40
kzaitsev_wsso for now I'm thinking of using https://github.com/Intel-Corp/multus-cni11:40
kzaitsev_wsthe only downside is that k8s would know nothing about those additional ips on a pod11:41
ivc-kzaitsev_ws also i'd be against using different handlers/cnis to do the same thing (i.e. single vs multi-port). i'd much prefer if the current model is extended to use a list (or dict) of VIFs in place of current single-VIF annotation11:41
kzaitsev_wsAny reason why it's a bad idea to allow multiple handlers?11:43
ivc-why have multiple handlers for the same thing?11:43
kzaitsev_wsin my scenario they would be configuring different interfaces differently11:45
ivc-so how do you expect to compose it with other parts? e.g. the vif pool?11:45
ivc-also are we talking about controller-side handler or a cni-side handler?11:47
kzaitsev_wsactually both. I want to request additional IP from neutron, assign it to a VF of a Network Card and pass this interface to Pods namespace11:49
kzaitsev_wsam I talking nonsence? =)11:50
kzaitsev_wsSo I was looking for a way to make it in a non-disruptive manner, so that I would be able to contribute some parts of my solution back to kuryr-k8s11:55
*** egonzalez has quit IRC11:58
kzaitsev_wsI just think, that adding this kind of passthrough capabilities to kuryr-cni would be out of scope of its functionality.12:06
kzaitsev_wsAlso I'm intending to use OPI in k8s to bookkeep the amount of free VFs on a node, so it complicates things a little tad further =)12:12
kzaitsev_ws*OIR (don't know why I keep using OPI)12:13
*** aojea has joined #openstack-kuryr12:54
kzaitsev_wsivc-: also. I think I'll add a dpendant commit with doc-strings added to functions or https://review.openstack.org/#/c/376045 would never get merged )))13:00
*** jayahn has joined #openstack-kuryr13:49
*** limao has joined #openstack-kuryr13:51
*** yedongcan has joined #openstack-kuryr13:56
dmelladokzaitsev_ws: huh, pls do that and hopefully it'll unlock that13:57
dmelladoyou've got my +1, in case it helps ;)13:57
*** hongbin has joined #openstack-kuryr14:03
*** yedongcan has left #openstack-kuryr14:35
*** aojea has quit IRC14:44
*** aojea has joined #openstack-kuryr14:45
*** aojea has quit IRC14:49
*** jayahn has quit IRC14:50
openstackgerritMerged openstack/kuryr-kubernetes master: K8s Services support: LoadBalancerHandler  https://review.openstack.org/37604514:52
openstackgerritMerged openstack/kuryr-kubernetes master: Implement Guru meditation reports  https://review.openstack.org/44794214:52
*** jchhatbar has quit IRC15:01
hongbinkzaitsev_ws: there?15:26
hongbinkzaitsev_ws: left some comments on https://review.openstack.org/#/c/456586/15:26
kzaitsev_wssure would address those a bit later today15:35
kzaitsev_wsthanks for pointin that out15:36
*** limao has quit IRC15:41
*** limao has joined #openstack-kuryr15:42
*** kzaitsev_ws has quit IRC15:44
*** limao has quit IRC15:46
*** aojea has joined #openstack-kuryr16:18
*** aojea has quit IRC16:37
*** aojea has joined #openstack-kuryr16:38
*** aojea has quit IRC16:42
openstackgerritMerged openstack/kuryr-libnetwork master: Remove subunit-trace fork  https://review.openstack.org/45429516:47
openstackgerritMerged openstack/kuryr master: Replace http with https  https://review.openstack.org/45443016:47
openstackgerritMerged openstack/kuryr master: Remove log translations  https://review.openstack.org/44783516:56
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements  https://review.openstack.org/45593117:14
*** tonanhngo has joined #openstack-kuryr17:22
*** tonanhngo has quit IRC17:26
*** tonanhngo has joined #openstack-kuryr17:27
*** vikasc has quit IRC17:30
*** vikasc has joined #openstack-kuryr17:45
*** alraddarla_ has joined #openstack-kuryr18:07
*** alraddarla_ has quit IRC18:12
*** vikasc has quit IRC18:37
*** vikasc has joined #openstack-kuryr18:40
*** aojea has joined #openstack-kuryr19:10
openstackgerritHongbin Lu proposed openstack/kuryr-libnetwork master: [WIP] Avoid running more than one etcd process  https://review.openstack.org/45736121:23
openstackgerritHongbin Lu proposed openstack/fuxi master: [WIP] Avoid running more than one etcd process  https://review.openstack.org/45736321:25
*** aojea has quit IRC21:37
*** alraddarla_ has joined #openstack-kuryr21:45
openstackgerritHongbin Lu proposed openstack/fuxi master: [WIP] Avoid running more than one etcd process  https://review.openstack.org/45736321:49
openstackgerritHongbin Lu proposed openstack/kuryr-libnetwork master: [WIP] Avoid running more than one etcd process  https://review.openstack.org/45736121:50
*** alraddarla_ has quit IRC21:51
*** pmannidi has joined #openstack-kuryr23:19

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