Wednesday, 2017-02-01

*** yuvalb has quit IRC00:06
*** yuvalb has joined #openstack-kuryr00:08
openstackgerritHongbin Lu proposed openstack/kuryr-libnetwork: Add prefix to the specified name of subnetpool  https://review.openstack.org/42662300:09
openstackgerritHongbin Lu proposed openstack/kuryr-libnetwork: [WIP] Support creating from existing subnetpool  https://review.openstack.org/42659500:09
*** limao_ has quit IRC00:10
*** dims_ has joined #openstack-kuryr00:10
*** dims has quit IRC00:11
*** limao has joined #openstack-kuryr00:11
*** hongbin has quit IRC00:14
*** limao_ has joined #openstack-kuryr00:21
*** limao has quit IRC00:22
*** limao_ has quit IRC00:26
*** limao has joined #openstack-kuryr00:26
*** saneax is now known as saneax-_-|AFK00:30
*** limao has quit IRC01:08
*** limao has joined #openstack-kuryr01:08
*** limao has quit IRC01:44
*** limao_ has joined #openstack-kuryr01:45
*** tonanhngo has quit IRC01:47
*** yedongcan has joined #openstack-kuryr02:11
*** tonanhngo has joined #openstack-kuryr02:13
*** yedongcan has quit IRC02:15
*** yedongcan has joined #openstack-kuryr02:15
*** tonanhngo has quit IRC02:17
*** yuanying has quit IRC02:21
janonymousapuimedo: https://etherpad.openstack.org/p/Dur3bXQTNH , Some pointers02:22
*** limao_ has quit IRC02:36
*** limao has joined #openstack-kuryr02:52
openstackgerritDongcan Ye proposed openstack/kuryr: Fix param in get_neutron_subnetpool_name  https://review.openstack.org/42753303:00
*** limao has quit IRC03:04
*** yedongcan has left #openstack-kuryr03:27
*** janki has joined #openstack-kuryr05:01
*** tonanhngo has joined #openstack-kuryr05:22
janonymousapuimedo: https://review.openstack.org/#/c/410609/05:32
janonymousapuimedo: non-voting jobs pass now05:32
*** saneax-_-|AFK is now known as saneax06:05
*** yedongcan has joined #openstack-kuryr06:15
*** pcaruana has joined #openstack-kuryr07:19
*** yamamoto has quit IRC07:25
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr: Make segmentation driver testable  https://review.openstack.org/42719007:37
*** tonanhngo has quit IRC07:40
*** pmannidi has quit IRC07:43
irenabivc_: I am not sure I got the context of your previous commet. Was the patch to make sure the expected exception log causing trouble?07:49
apuimedothanks janonymous for the patch! Merged08:08
janonymousapuimedo:thanks!08:08
apuimedoirenab: please review https://review.openstack.org/#/c/427190/408:09
irenabok08:09
apuimedojanonymous: thanks for the check on client-python08:10
apuimedodid you check if they support http2 or websockets for streaming events?08:11
openstackgerritMerged openstack/kuryr-libnetwork: Tls support configurations  https://review.openstack.org/41060908:12
janonymousapuimedo:checking in a sex08:16
janonymous*sec08:16
janonymousops, sry08:17
openstackgerritMerged openstack/kuryr-kubernetes: testing: drop zero hashseed  https://review.openstack.org/42749508:18
janonymousapuimedo: https://github.com/kubernetes-incubator/client-python/pull/2/commits/750c9eaba4dd7e692edb4d2d7d842e05452d92a708:18
irenabjanonymous: Do you feel the k8s client is table eanough?08:25
janonymousirenab:According to code seems like they have major things that needs for kuryr, but personally i feel i requires some time to get production ready08:27
janonymous*it08:27
apuimedoxD08:27
* janonymous I donno where to hide08:29
irenabjanonymous: so you would suggest towait before switching to use the k8s clinet?08:29
irenabclient08:29
*** yuanying has joined #openstack-kuryr08:30
janonymousirenab: tricky question, but i am in favor of moving to officially supported client but would wait for some time more08:31
janonymousto check if it wont break our existing enviornment08:32
irenabjanonymous: is there pipi for the client?08:32
irenabpypi08:32
janonymousyes08:32
janonymoushttps://pypi.python.org/pypi/kubernetes/1.0.0b1#downloads08:33
janonymousreleased after i asked on sig-api machinery few time back08:33
irenabjanonymous: cool08:35
janonymousmaybe in vtg, we can write down everything we need from client in our kuryr-kuberentes code and check those one-by-one08:36
irenabapuimedo: janonymous : sounds like a plan08:36
janonymousyeah, i would say not to jump directly on using that, instead we can make changes on k8s-client in external repo first according to our needs, when that is done we can safely replace out our internal implementation08:38
janonymousmore suggestions are welcomed.08:39
openstackgerritMerged openstack/kuryr: Make segmentation driver testable  https://review.openstack.org/42719008:43
*** jchhatbar has joined #openstack-kuryr08:46
*** janki has quit IRC08:48
irenabjanonymous: longer term, using k8s sdk is the proper way to go. I do not think kuryr should have any notexpected usage for the k8s api.08:54
irenabjanonymous: but we should make sure that not only functionality but also performance wirse it fits kuryr needs08:54
apuimedoirenab: agreed08:54
janonymous+108:55
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr: Add randomness to the returned vlan_ids  https://review.openstack.org/42264108:58
apuimedoltomasbo: the testable patch got much better! Thanks!08:58
ltomasbothank you for the comments!08:59
ltomasboI just rebased the other patch to see if know unit tests pass08:59
ltomasboapuimedo, ^^08:59
apuimedoI saw09:00
apuimedoI'm looking at it now09:00
ltomasboyep, now they pass unit tests!09:04
*** garyloug has joined #openstack-kuryr09:08
irenabltomasbo: hi09:12
ltomasboirenab, hi!09:13
irenabltomasbo: checking the randomness patch now.09:13
ltomasbogreat!09:13
irenabnot related tot he change, but general question about the local_vlans09:13
irenabis it sort of the local cache?09:14
ltomasboyes09:14
ltomasbothese vlans are local to each trunk port09:15
ltomasboand independent of the vlans used for the subnets09:15
ltomasboso, each kuryr running inside the trunk VM will have their own local range09:16
irenabit starts with full vlan range. How is it synced with the host?09:16
ltomasbothat is handled by kuryr-libnetwork (or kuryr-kubernetes)09:16
ltomasbowhere they check (by calling neutron) what vlans are already in used by that trunk port09:17
irenaband this is passed into allocate_xxx method09:17
ltomasboand it will be passed in allocated_ids, so that those are removed from the full range in the allocate_segmentation_id call09:17
ltomasboyep09:18
irenabI am not sureI see the value of the local cache09:18
irenabcan you please expain how is it used09:18
ltomasbonot sure I get what is the problem with that (and that was in the patch before anyway)09:19
ltomasbothe idea is that you get a vlan_id from the list of available vlans09:19
ltomasboand we used the available_local_vlans just to keep which vlans are already taken09:20
irenabltomasbo: debug purposes?09:20
ltomasbowe don't want to call neutron all the time to check what vlan_ids are available09:20
ltomasboso we keep track of that to avoid neutron calls09:21
ltomasboat starting kuryr, we sync with neutron (for the specific VM trunk port)09:21
ltomasboand then we handle the vlan_ids09:21
ltomasbois it not for debuging, we need to figure out the vlan_ids as neutron don't give you one by default09:22
ltomasbohttps://review.openstack.org/#/c/42188009:22
ltomasboI'm trying to get that supported, but didn't get too far09:23
irenabok. thereis something bothering me here :-), but it is not related to your change anyway09:24
ltomasboirenab: not sure this answer your question/concern09:24
ltomasbowhat do you have in mind to remove the cache?09:24
ltomasbocalling neutron? or simply using allocated_ids?09:25
irenabltomasbo: we keep neutron as a single source of truth, regardless what is the status in the VM09:25
ltomasbowe still do that09:25
ltomasboand even if we are not completely in sync at some point09:26
ltomasboneutron will reject to use an already allocated vlan09:26
ltomasbofor the specific purpose09:26
irenabI mean for the case is ther is some restart of the kuryr service, we loose the cache09:26
ltomasbothe problem here is neutron should give you a default vlan_id by definition, but it is not09:26
ltomasboyes, but if we restart the kuryr service, then we call neutron at restart time to get the vlans09:27
apuimedoltomasbo: that's the problem :-) "neutron should give you a default vlan_id by definition, but it is not"09:27
apuimedoany advance in getting the neutron patch in?09:27
ltomasbohttps://github.com/openstack/kuryr-libnetwork/blob/master/kuryr_libnetwork/port_driver/drivers/vlan.py#L39:L4209:28
ltomasbono, armax said it will not work with ironic09:28
ltomasboI tried to reach him but didn't get any more info09:28
ltomasboand I did check ironic a bit, and it seems trunk-ports are not supported at all09:28
irenabltomasbo: maybe worth to check with Ironic team09:29
ltomasboso not sure what the problem may be with my patch and ironic09:29
ltomasboI saw there is a spec to include trunks support09:29
ltomasbobut it is not yet there, so I'm not sure how the patch can break it!09:29
apuimedoltomasbo: so you are saying that trunk ports are not supported in Ironic yet it is blocked on those grounds?09:29
apuimedoI must be missing something09:30
ltomasboarmax did not get back to me with more info, but that is what I found by looking at trunk ports at ironic09:30
apuimedoltomasbo: does ironic always use vlans?09:30
irenabapuimedo: As far as I know its eiter flat or VLANs09:31
ltomasbothe think I'm forecasting, is that they plan to support trunk ports by sending the traffic encapsulated as vlan ids09:31
ltomasboon the wire09:31
ltomasboso, there is a need of those vlans_ids to be accepted/configured in the physical network switches (ToR)09:32
apuimedoirenab: oh, I had thought maybe with some switches it could do vxlan09:32
ltomasbobut neutron is not configuring physical switches directly09:32
apuimedobut even if it vlan09:32
apuimedoif you get a "physical trunk" port to the host09:32
apuimedoyou could run containers in vlans09:33
irenabltomasbo: it can with ml2 drivers. It waht it does for Arista switches09:33
apuimedoso neutron trunk ports could be supported in that way09:33
apuimedoor nested tags (though that sucks)09:33
apuimedoltomasbo: I thought ironic did some switch interaction09:33
*** saneax is now known as saneax-_-|AFK09:33
apuimedoI wonder how they do it09:34
ltomasboapuimedo, I think they do, but not sure how static/dynamic that may be09:34
irenabhttps://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/ironic-ml2-integration.html09:34
apuimedoit seems it is implemented (despite the spec path)09:35
apuimedoat least the linked bugs are09:35
irenabapuimedo: so it mentions the case with single interface on multiple networks09:35
irenabas TBD09:36
apuimedoyeah09:36
apuimedoirenab: but in any case, it depends on ml2 being able to configure switches, right?09:38
irenabyes09:38
ltomasboI think the problems was related to not having ovs agent on ironic nodes09:39
ltomasboso, the vlan-aware-vm, instead of having the tagging only up to br-int09:40
ltomasbofor ironic it will go out of the server tagged09:40
ltomasboand therefore it needs to use proper tags09:40
ltomasboand we cannot get the tags by asking neutron about the range and the already used ones09:40
ltomasbounless the range is the same as the one configured for the ironic nodes/switches09:40
ltomasboand for that specific case, the vlan tags needs to be the same as the ones used for the subnets09:41
ltomasbowhile for normal vlans-aware-vms, that tag is independent of the subnets tags09:41
ltomasboas it is only local to the OVS trunk-port created for the VM, which will translate it to the subnet vlan at br-int09:42
apuimedoltomasbo: but there must be some sort of agent, right?09:43
irenabwhat I don’t understadn is why not enableAPI to support both scenarios. It seems to be the caller responsibility to decide if provide vlan or use neutron to pick itfor him. Like with ml2 type drivers for provider network09:43
apuimedoirenab: ltomasbo's patch just made it optional to automatically get an id09:44
apuimedoblocking it seems needless09:44
ltomasboyep, but maybe it should be optional just non-ironic scenario...09:44
apuimedoltomasbo: does that not depend just on ironic usage09:44
apuimedoI don't see what they are being so protective about in this specific case09:45
ltomasboapuimedo, I'm not sure how ironic works, but I'm guessing configurations happens though pxe09:45
ltomasboand they just connect to vlans by eth0.101 or something like that09:45
apuimedoltomasbo: yes, I assume that's the case, but there may be some dynamic aspect09:45
ltomasboyes, but maybe it is in an ironic controller instead of the ironic nodes itselfs09:46
ltomasbothen again, I do not have enough knowledge about ironic to support any of this, just some reading, never tried myself09:46
apuimedoltomasbo: I've been wanting to experiment with ironic for some time09:48
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr: Add randomness to the returned vlan_ids  https://review.openstack.org/42264109:51
ltomasbome too, I just don't have the hardware...09:52
ltomasboit would be nice to have ironic support at kuryr when trunk ports are supported09:53
apuimedoexactly09:53
ltomasbothat way we can just have containers veth connected to the nick09:53
ltomasbos/nick/nic09:53
ltomasboI think that could be an awesome solution for some telco operators...09:54
apuimedoltomasbo: you'd probably use either nic vfs or ipvlan/macvlan09:58
apuimedowouldn't you?09:58
apuimedo(instead of veths)09:59
ltomasbofor ironic?10:00
ltomasboyou want to use the subnet vlan tag10:00
ltomasboso, why using ipvlan/macvlan?10:00
ltomasboit is just plug the container on, let's say eth0.101 for subnet on vlan tag 10110:01
ltomasbosimilarly to what we do today for vlans nested containers at VMs with kuryr10:02
ltomasbobut as if the ironic node was the trunk VM10:02
ltomasbo(unless I'm missing something)10:03
apuimedoright10:08
apuimedoltomasbo: https://github.com/openstack/pyghmi/blob/master/bin/virshbmc10:17
apuimedothere is a fake ipmi server that uses libvirt python module10:17
apuimedomaybe it can be used to try ironic10:17
apuimedo:-)10:17
ltomasboumm10:17
ltomasbothanks!10:17
ltomasboI may try it later!10:18
*** saneax-_-|AFK is now known as saneax10:38
*** yedongcan has left #openstack-kuryr10:45
openstackgerritMerged openstack/kuryr: Add randomness to the returned vlan_ids  https://review.openstack.org/42264111:06
*** v1k0d3n has quit IRC12:02
*** jchhatbar_ has joined #openstack-kuryr12:31
*** jchhatbar has quit IRC12:34
*** dougbtv has joined #openstack-kuryr12:35
*** garyloug has quit IRC12:48
*** garyloug has joined #openstack-kuryr12:50
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes: Kuryr Kubernetes Resource Manager design reference document  https://review.openstack.org/42768113:00
*** limao has joined #openstack-kuryr13:36
*** limao_ has joined #openstack-kuryr13:40
*** limao has quit IRC13:41
*** v1k0d3n has joined #openstack-kuryr13:48
*** limao_ has quit IRC14:08
*** limao has joined #openstack-kuryr14:09
*** limao has quit IRC14:10
*** limao has joined #openstack-kuryr14:10
apuimedoivc_: sometimes I'm tempted to use https://github.com/h2o/picohttpparser for the requests14:40
apuimedobtw, review ltomasbo's https://review.openstack.org/#/c/427681/1/doc/source/devref/resource_manager.rst14:45
apuimedo;-)14:45
apuimedoltomasbo: just posted some comments14:50
*** limao has quit IRC14:50
apuimedoon to the lbaas patch review14:50
*** limao has joined #openstack-kuryr14:50
apuimedoirenab: ltomasbo: what about https://review.openstack.org/#/c/425040/14:52
apuimedo?14:52
ivc_apuimedo does that mean we also want to move to C instead of Py? xD but seriously, C extensions do not work well with eventlet14:54
ltomasboapuimedo, thanks! It was a first draft. I will take a look asap14:54
apuimedoivc_: I know, I just like to have speedup plans for all the parts14:55
apuimedo:P14:55
ivc_apuimedo now i want to cite donald knuth :)14:56
apuimedoivc_: he only spoke of premature optimization, not of premature optimization plans14:57
apuimedo:-)14:57
apuimedoso I'm in the clear14:57
ivc_thats even more premature xD14:57
ltomasboapuimedo: ahh, not that many comments! :D14:57
apuimedoivc_: and less of an optimization14:58
ivc_apuimedo well, we can also talk about 'go' then :)15:00
apuimedoivc_: it is less performant, but it gets you free client15:01
irenabapuimedo: totally forgot about it, will update later today15:09
apuimedothanks15:10
*** saneax is now known as saneax-_-|AFK15:17
*** hongbin has joined #openstack-kuryr15:19
*** limao_ has joined #openstack-kuryr15:34
*** limao has quit IRC15:36
*** jchhatbar_ has quit IRC15:43
openstackgerritMerged openstack/kuryr-libnetwork: Add nested-containers limitations  https://review.openstack.org/42504015:49
openstackgerritMerged openstack/kuryr-libnetwork: README: fix nested container rendering  https://review.openstack.org/42530915:50
*** limao_ has quit IRC16:15
*** tonanhngo has joined #openstack-kuryr16:37
*** tonanhngo has quit IRC16:42
*** tonanhngo has joined #openstack-kuryr17:31
*** tonanhngo has quit IRC17:36
*** v1k0d3n has quit IRC17:56
*** v1k0d3n has joined #openstack-kuryr18:00
*** tonanhngo has joined #openstack-kuryr18:20
*** garyloug has quit IRC18:23
*** tonanhngo has quit IRC18:23
*** tonanhngo has joined #openstack-kuryr18:23
*** pcaruana has quit IRC18:28
*** yuanying has quit IRC19:03
openstackgerritMerged openstack/kuryr-libnetwork: Optimize add subnetpool tag  https://review.openstack.org/42061019:08
alraddarlaDoes libnetwork follow the same versioning of kuryr20:40
alraddarlaAlso, is this a bug: https://github.com/openstack/kuryr/blob/master/releasenotes/source/conf.py#L61-L6320:44
alraddarlaShouldn't version and release be flipped?20:44
openstackgerritHongbin Lu proposed openstack/kuryr-libnetwork: [WIP] Optimize the search of subnet  https://review.openstack.org/42792321:06
openstackgerritHongbin Lu proposed openstack/kuryr-libnetwork: [WIP] Optimize the search of subnet  https://review.openstack.org/42792321:24
hongbinapuimedo: irenab : hey, when you have a chance, would like to get your early feedback on this one: https://review.openstack.org/#/c/427923/21:25
alraddarlaAfter looking into it, seems as though these have been updated here: https://github.com/openstack-dev/pbr/blob/master/pbr/version.py#L468-L46921:52
alraddarlaI can volunteer to update Kuryr as well.21:52
apuimedoalraddarla: did you check how neutron does it?22:38
apuimedohongbin: I'll bring it up with irenab tomorrow22:40
apuimedothanks22:40
hongbinapuimedo: ok22:40
*** pc_m has quit IRC22:49
*** pc_m has joined #openstack-kuryr22:50
*** yuanying has joined #openstack-kuryr23:07
*** v1k0d3n has quit IRC23:07
*** pmannidi has joined #openstack-kuryr23:14
*** v1k0d3n has joined #openstack-kuryr23:22
*** yamamoto has joined #openstack-kuryr23:24
*** v1k0d3n has quit IRC23:41

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