| *** yasui has quit IRC | 01:23 | |
| *** yasui has joined #openstack-kuryr | 01:26 | |
| *** diogogmt has quit IRC | 01:48 | |
| *** yasui has quit IRC | 01:56 | |
| *** baohua has joined #openstack-kuryr | 01:57 | |
| *** yasui has joined #openstack-kuryr | 01:57 | |
| *** fawadkhaliq has joined #openstack-kuryr | 01:58 | |
| *** fawadkhaliq has quit IRC | 01:59 | |
| *** yasui has quit IRC | 02:04 | |
| *** yasui has joined #openstack-kuryr | 02:05 | |
| *** banix has joined #openstack-kuryr | 02:14 | |
| *** diogogmt has joined #openstack-kuryr | 02:58 | |
| *** yuanying has quit IRC | 03:21 | |
| *** yuanying has joined #openstack-kuryr | 03:23 | |
| openstackgerrit | Reedip proposed openstack/kuryr: Remove all bytcode before running tox https://review.openstack.org/271910 | 03:27 |
|---|---|---|
| *** yuanying has quit IRC | 03:28 | |
| *** yuanying has joined #openstack-kuryr | 03:33 | |
| *** vikasc has joined #openstack-kuryr | 03:34 | |
| *** yuanying has quit IRC | 03:40 | |
| *** yuanying has joined #openstack-kuryr | 03:40 | |
| *** yuanying has quit IRC | 03:56 | |
| *** yuanying has joined #openstack-kuryr | 03:57 | |
| openstackgerrit | Reedip proposed openstack/kuryr: Support py34 in Kuryr https://review.openstack.org/271914 | 03:57 |
| *** yuanying_ has joined #openstack-kuryr | 03:58 | |
| *** yuanying has quit IRC | 04:01 | |
| *** banix has quit IRC | 04:03 | |
| *** salv-orl_ has quit IRC | 04:09 | |
| *** fawadkhaliq has joined #openstack-kuryr | 04:46 | |
| *** salv-orlando has joined #openstack-kuryr | 05:05 | |
| *** salv-orlando has quit IRC | 05:13 | |
| *** vikasc has quit IRC | 05:16 | |
| *** fawadkhaliq has quit IRC | 05:31 | |
| *** fawadkhaliq has joined #openstack-kuryr | 05:47 | |
| *** fawadkhaliq has joined #openstack-kuryr | 05:50 | |
| *** vikasc has joined #openstack-kuryr | 06:00 | |
| *** salv-orlando has joined #openstack-kuryr | 06:05 | |
| *** salv-orlando has quit IRC | 06:10 | |
| *** vikasc has quit IRC | 06:21 | |
| *** vikasc has joined #openstack-kuryr | 06:32 | |
| *** salv-orlando has joined #openstack-kuryr | 06:57 | |
| *** salv-orlando has quit IRC | 06:57 | |
| *** salv-orlando has joined #openstack-kuryr | 06:58 | |
| *** vikasc has quit IRC | 07:40 | |
| *** vikasc has joined #openstack-kuryr | 07:50 | |
| *** salv-orlando has quit IRC | 08:11 | |
| *** gsagie has joined #openstack-kuryr | 08:16 | |
| openstackgerrit | Reedip proposed openstack/kuryr: Support py34 in Kuryr https://review.openstack.org/271914 | 08:31 |
| *** vikasc has quit IRC | 08:33 | |
| *** vikasc has joined #openstack-kuryr | 08:48 | |
| openstackgerrit | Reedip proposed openstack/kuryr: Support py34 in Kuryr https://review.openstack.org/271914 | 08:49 |
| *** salv-orlando has joined #openstack-kuryr | 09:04 | |
| *** devvesa has joined #openstack-kuryr | 09:04 | |
| openstackgerrit | Merged openstack/kuryr: Add Kuryr network creation/deletion tests https://review.openstack.org/259751 | 09:21 |
| *** baohua has quit IRC | 09:30 | |
| *** vikasc has quit IRC | 09:36 | |
| *** devvesa has quit IRC | 09:42 | |
| *** vikasc has joined #openstack-kuryr | 09:47 | |
| *** devvesa has joined #openstack-kuryr | 09:57 | |
| *** salv-orl_ has joined #openstack-kuryr | 10:06 | |
| *** salv-orlando has quit IRC | 10:08 | |
| *** vikasc has quit IRC | 10:17 | |
| *** salv-orl_ has quit IRC | 10:35 | |
| *** devvesa has quit IRC | 10:39 | |
| *** devvesa has joined #openstack-kuryr | 11:34 | |
| devvesa | Hi gsagie | 11:35 |
| *** fawadkhaliq has quit IRC | 11:42 | |
| *** fawadkhaliq has joined #openstack-kuryr | 11:42 | |
| *** baohua has joined #openstack-kuryr | 12:19 | |
| *** salv-orlando has joined #openstack-kuryr | 12:35 | |
| *** salv-orlando has quit IRC | 12:40 | |
| *** apuimedo_ has joined #openstack-kuryr | 12:56 | |
| openstackgerrit | Gal Sagie proposed openstack/kuryr: Add container connect/disconnect tests to fullstack gate job https://review.openstack.org/265105 | 13:39 |
| *** baohua_ has joined #openstack-kuryr | 13:47 | |
| *** baohua has quit IRC | 13:48 | |
| *** fawadkhaliq has quit IRC | 13:55 | |
| *** fawadk has joined #openstack-kuryr | 13:55 | |
| *** diogogmt has quit IRC | 14:01 | |
| *** diogogmt has joined #openstack-kuryr | 14:03 | |
| *** fawadk has quit IRC | 14:12 | |
| *** salv-orlando has joined #openstack-kuryr | 14:13 | |
| *** fawadkhaliq has joined #openstack-kuryr | 14:15 | |
| *** fawadkhaliq has quit IRC | 14:16 | |
| *** diogogmt has quit IRC | 14:21 | |
| *** baohua_ has quit IRC | 14:29 | |
| *** fawadkhaliq has joined #openstack-kuryr | 15:40 | |
| *** fawadkhaliq has quit IRC | 15:40 | |
| *** fawadkhaliq has joined #openstack-kuryr | 15:40 | |
| *** salv-orl_ has joined #openstack-kuryr | 16:06 | |
| *** salv-orlando has quit IRC | 16:09 | |
| *** banix has joined #openstack-kuryr | 16:10 | |
| *** diogogmt has joined #openstack-kuryr | 16:56 | |
| *** devvesa has quit IRC | 17:08 | |
| *** salv-orl_ has quit IRC | 17:16 | |
| mestery | Has anyone run Kuryr on an existing Neutron install hosting VMs and verified connectivity between containers and VMs? | 17:20 |
| *** fawadkhaliq has quit IRC | 17:51 | |
| *** salv-orlando has joined #openstack-kuryr | 17:53 | |
| *** salv-orlando has quit IRC | 20:27 | |
| *** salv-orlando has joined #openstack-kuryr | 21:16 | |
| *** salv-orl_ has joined #openstack-kuryr | 22:06 | |
| apuimedo_ | darn | 22:08 |
| apuimedo_ | k8s-sig-meeting not on hangouts... Me downloading stupid plugin | 22:08 |
| *** salv-orlando has quit IRC | 22:09 | |
| apuimedo_ | mestery: having a router between a VM network and a kuryr network should work | 22:09 |
| apuimedo_ | there's no reason it would not | 22:09 |
| *** vikasc has joined #openstack-kuryr | 22:13 | |
| apuimedo_ | mestery: in fact, I should be demoing on Sunday at FOSDEM | 22:24 |
| apuimedo_ | so I'll know soon enough :P | 22:24 |
| apuimedo_ | fkautz: what a sudden end to the meeting :P | 22:33 |
| fkautz | yea, that was unexpected :p | 22:33 |
| apuimedo_ | fkautz: I missed the first 13 minutes due to problems with the plugin | 22:34 |
| *** banix has quit IRC | 22:34 | |
| fkautz | we've been slowly trying out every conference solution | 22:34 |
| apuimedo_ | fkautz: how did they say that they want to make policy available in kube-proxy scenarios for CNI plugins? | 22:34 |
| apuimedo_ | I prefer bluejeans | 22:34 |
| fkautz | same here | 22:34 |
| apuimedo_ | in my company we use google hangouts and it makes me miss bluejeans when multiple timezones are involved | 22:35 |
| fkautz | hangouts can't cope with the number of participants | 22:35 |
| fkautz | anyways, i missed that specific answer | 22:35 |
| apuimedo_ | but it seemed to me like they pointed out to the contrail way for getting that info | 22:36 |
| fkautz | i believe the mention was kube-proxy itself was an implementation but not something locked in | 22:36 |
| apuimedo_ | since there is no real plan for having that info available | 22:36 |
| apuimedo_ | and the contrail way is no kube-proxy and have an etcd watcher iirc | 22:36 |
| fkautz | best case would be to work out what info we're missing and ask directly on the email list | 22:36 |
| fkautz | yea, i think that's the most likely solution | 22:37 |
| fkautz | a kube-proxy is installed on each system but they don't appear to communicate with each other | 22:37 |
| fkautz | they listen on a given port on every node and forward packets round robin from what i gathered in that conversation | 22:38 |
| apuimedo_ | from what I saw, they just set iptables doing natting | 22:38 |
| apuimedo_ | but maybe that's just one of the configurations | 22:38 |
| fkautz | if that's the implementation, it wouldn't surprise me | 22:39 |
| fkautz | i'll find the source for it | 22:39 |
| apuimedo_ | I just tried with the sample application | 22:39 |
| apuimedo_ | and saw just a bunch of iptables nat redirects being placed | 22:40 |
| fkautz | yea, it's iptables | 22:40 |
| fkautz | https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-proxy/app/server.go | 22:40 |
| apuimedo_ | as I see it, there's two ways | 22:40 |
| apuimedo_ | replace/impersonate kube-proxy | 22:40 |
| apuimedo_ | since it seems to get enough information for the ref implementation | 22:41 |
| apuimedo_ | or | 22:41 |
| apuimedo_ | have a model watcher | 22:41 |
| apuimedo_ | that does it's own thing | 22:41 |
| fkautz | yea, trying to work out where it gets its state from | 22:41 |
| fkautz | not seeing it, there are calls to a pkg/proxy/config which has calls to pkg/api | 22:47 |
| fkautz | i assume that's backed by etcd and probably emits events over a channel | 22:47 |
| apuimedo_ | events over a channel was my guess | 22:49 |
| apuimedo_ | but I haven't had the time to look at the code yet | 22:49 |
| *** yuanying_ has quit IRC | 23:02 | |
| fkautz | i need to set this system up to use go :x anyways, there is a watch interface provided by the api | 23:04 |
| fkautz | looks like k8s is making some kind of rest call that is providing that info | 23:04 |
| *** yuanying has joined #openstack-kuryr | 23:12 | |
| mestery | apuimedo_: Is the end goal to eventually support containers and VMs (and bare metal even) on the same logical neutron network? | 23:22 |
| apuimedo_ | mestery: yes | 23:56 |
| mestery | apuimedo_: Coolio! That's my goal as well :) | 23:56 |
| apuimedo_ | or in separate neutron routed networks | 23:56 |
| apuimedo_ | good! | 23:56 |
| mestery | apuimedo_: Bah .... I'd rather they be in the same neutron network if possible | 23:56 |
| apuimedo_ | mestery: that needs some labels due to libnetwork | 23:56 |
| apuimedo_ | to specify pre-existing networks | 23:56 |
| mestery | apuimedo_: Right ... | 23:57 |
| apuimedo_ | (unless you create first with kuryr | 23:57 |
| mestery | But we can get there I think, right? | 23:57 |
| apuimedo_ | and then just use the ugly name with nova) | 23:57 |
| apuimedo_ | sure, we can | 23:57 |
| mestery | Excellent! | 23:57 |
| apuimedo_ | it should be doable quite fast | 23:57 |
| apuimedo_ | couple of days | 23:57 |
| mestery | Thanks apuimedo_ :) | 23:58 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!