Tuesday, 2017-01-17

*** hongbin has quit IRC00:32
*** limao has joined #openstack-kuryr00:32
*** limao has quit IRC00:32
*** yedongcan has joined #openstack-kuryr00:45
*** tonanhngo has quit IRC01:20
*** salv-orlando has joined #openstack-kuryr01:25
*** tonanhngo has joined #openstack-kuryr01:27
*** tonanhngo has quit IRC01:32
*** salv-orlando has quit IRC01:46
*** tonanhngo has joined #openstack-kuryr02:01
*** tonanhngo has quit IRC02:02
*** tonanhngo has joined #openstack-kuryr02:09
*** tonanhngo has quit IRC02:11
*** salv-orlando has joined #openstack-kuryr02:13
*** salv-orlando has quit IRC02:32
*** tonanhngo has joined #openstack-kuryr02:50
*** tonanhngo has quit IRC02:51
*** hongbin has joined #openstack-kuryr02:53
*** salv-orlando has joined #openstack-kuryr03:00
*** yuanying has quit IRC03:01
*** yuanying has joined #openstack-kuryr03:01
*** yuanying has quit IRC03:01
*** yuanying has joined #openstack-kuryr03:02
*** salv-orlando has quit IRC03:05
*** yuanying has quit IRC03:06
*** janki has joined #openstack-kuryr03:40
*** yuanying has joined #openstack-kuryr04:02
*** v1k0d3n has joined #openstack-kuryr04:07
*** v1k0d3n has quit IRC04:11
*** hongbin has quit IRC04:16
*** hongbin has joined #openstack-kuryr04:17
*** tonanhngo has joined #openstack-kuryr04:19
*** tonanhngo has quit IRC04:22
*** vikas_ has quit IRC04:28
*** tonanhngo has joined #openstack-kuryr04:29
*** tonanhngo has quit IRC04:31
*** vikas_ has joined #openstack-kuryr04:33
*** yuanying has quit IRC04:55
*** salv-orlando has joined #openstack-kuryr05:01
*** yuanying has joined #openstack-kuryr05:03
*** salv-orlando has quit IRC05:06
*** v1k0d3n has joined #openstack-kuryr05:14
*** hongbin has quit IRC05:17
*** v1k0d3n has quit IRC05:25
*** tonanhngo has joined #openstack-kuryr05:30
*** yuanying has quit IRC05:46
*** yuanying has joined #openstack-kuryr05:47
*** yuanying has quit IRC05:51
openstackgerritMerged openstack/kuryr-kubernetes: Updated from global requirements  https://review.openstack.org/41993305:56
*** salv-orlando has joined #openstack-kuryr06:02
*** pc_m has quit IRC06:03
*** salv-orlando has quit IRC06:07
*** saneax-_-|AFK is now known as saneax06:35
janonymousirenab, ivc_: ping06:57
irenabjanonymous, hi06:59
janonymousirenab: i had a small question in kuryr-kubernetes07:00
irenabsure07:00
janonymousirenab: Would that make sense to use paste-deploy for handler pipeline.07:00
*** pc_m has joined #openstack-kuryr07:02
janonymous*it07:04
irenabjanonymous, need to check it, can you point to the cons to use it?07:08
janonymoushttps://pypi.python.org/pypi/PasteDeploy07:08
janonymousswift uses it in its proxy configuration file07:09
janonymousfor loading of middlewares in swift case07:09
janonymoushttps://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L9407:09
irenabjanonymous, interesting07:11
janonymousirenab: let me know if more info is required07:12
irenabjanonymous, give me few mins to catch up on this07:13
janonymousirenab: yeah, pls take your time.07:13
*** yuanying has joined #openstack-kuryr07:23
*** salv-orlando has joined #openstack-kuryr07:40
*** tonanhngo_ has joined #openstack-kuryr07:49
*** tonanhngo_ has quit IRC07:49
*** tonanhngo has quit IRC07:51
*** tonanhngo has joined #openstack-kuryr07:56
*** tonanhngo has quit IRC07:57
*** tonanhngo has joined #openstack-kuryr08:01
*** saneax is now known as saneax-_-|AFK08:09
*** salv-orlando has quit IRC08:09
*** saneax-_-|AFK is now known as saneax08:16
*** yamamoto has quit IRC08:21
*** tonanhngo has quit IRC08:23
yedongcanirenab, ivc_ : ping08:34
openstackgerritvikas choudhary proposed openstack/kuryr-kubernetes: Add support for nested pods with Vlan trunk port  https://review.openstack.org/41057808:43
irenabyedongcan, hi08:45
vikas_irenab, apuimedo|away ivc_ PTAL ^08:45
yedongcanirenab: hi, does kuryr-k8s support LBaaSv2 now?08:46
irenabyedongcan, yes08:46
irenabcheck this patch https://review.openstack.org/#/c/376045/08:46
irenabbut its not merged yet08:47
irenabvikas_, asap08:47
vikas_thanks irenab08:47
yedongcanirenab: thanks, got it.08:48
irenabyedongcan, the plan is to move to use Octavia at some point08:49
yedongcanirenab: does we both supports HAProxy and Octavia?08:50
irenabyedongcan, currently only HAProxy as default implementation, but theoretically any LBaaS Provider that implements LBaaSv2 API08:51
*** limao has joined #openstack-kuryr08:52
yedongcanirenab: sure :)08:52
*** devvesa has joined #openstack-kuryr08:58
*** yamamoto has joined #openstack-kuryr09:00
*** yamamoto has quit IRC09:07
*** yedongcan1 has joined #openstack-kuryr09:17
*** yedongcan has quit IRC09:20
*** apuimedo|away is now known as apuimedo09:24
*** saneax is now known as saneax-_-|AFK09:24
*** limao has quit IRC09:25
*** saneax-_-|AFK is now known as saneax09:34
*** garyloug has joined #openstack-kuryr09:44
*** yamamoto has joined #openstack-kuryr09:45
*** yamamoto has quit IRC09:49
*** yedongcan1 has left #openstack-kuryr10:02
*** salv-orlando has joined #openstack-kuryr10:10
*** salv-orlando has quit IRC10:14
*** tonanhngo has joined #openstack-kuryr10:24
*** yamamoto has joined #openstack-kuryr10:28
*** yamamoto has quit IRC10:29
*** tonanhngo has quit IRC10:29
*** yamamoto has joined #openstack-kuryr10:38
*** yamamoto has quit IRC10:56
*** neiljerram has joined #openstack-kuryr11:01
*** neiljerram has quit IRC11:15
*** yamamoto has joined #openstack-kuryr11:30
apuimedoivc_: irenab: vikas_: https://etherpad.openstack.org/p/kuryr_virtual_gathering_2017h111:33
apuimedoplease contribute to the document, I'll send it to the mailing list tomorrow11:33
*** yamamoto has quit IRC11:34
*** saneax is now known as saneax-_-|AFK11:42
*** saneax-_-|AFK is now known as saneax11:43
*** tonanhngo has joined #openstack-kuryr11:49
*** tonanhngo has quit IRC11:50
*** tonanhngo has joined #openstack-kuryr12:09
*** tonanhngo has quit IRC12:11
*** neiljerram has joined #openstack-kuryr12:17
irenabapuimedo, ack12:33
*** huats has quit IRC12:42
*** huats has joined #openstack-kuryr12:42
apuimedoirenab: and thanks for the reminders!12:48
apuimedoivc_: https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling#add_subports_before_boot.2C_all_at_once13:09
apuimedosearch for "add subports after boot, in batches"13:10
apuimedothis is consistent with the resource management plans13:10
apuimedobatching calls helps a ton13:10
apuimedos/calls/allocation/13:10
*** garyloug has quit IRC13:10
*** saneax is now known as saneax-_-|AFK13:17
*** garyloug has joined #openstack-kuryr13:31
*** neiljerram has quit IRC13:41
*** tonanhngo has joined #openstack-kuryr13:59
*** tonanhngo has quit IRC13:59
*** janki has quit IRC14:00
*** limao has joined #openstack-kuryr14:00
openstackgerritvikas choudhary proposed openstack/kuryr-kubernetes: Add support for nested pods with Vlan trunk port  https://review.openstack.org/41057814:03
vikas_ivc_, irenab apuimedo ltomasbo ^ , i will be update test case for noop plugin shortly, except that PTAL14:04
*** limao has quit IRC14:05
*** limao has joined #openstack-kuryr14:08
*** salv-orlando has joined #openstack-kuryr14:10
*** yamamoto has joined #openstack-kuryr14:31
apuimedoivc_: ltomasbo and I have both confirmed that you can't set trunk subports specifying only the segmentation type14:34
apuimedothe segmentation id is needed as well14:35
apuimedoivc_: ltomasbo said he'd look into how difficult it would be to build a Neutron patch that makes segmentation id allocation behave consistently with IPAM allocation14:35
*** yamamoto has quit IRC14:35
apuimedothe code freeze for Neutron is coming in ~10 days though14:36
irenabapuimedo, what do you mean by 'segmentation id allocation behave consistently with IPAM allocation'?14:42
apuimedoirenab: in Neutron, when you create a port, if you don't specify an IP, it will allocate one for you14:43
apuimedoit does not behave the same way with segmentation ids14:44
apuimedoI think that's an API inconsistency14:44
apuimedoas it's the same problem nature14:44
irenabapuimedo, maybe for now it expects external seg_id management. If it returns proper error in case seg_id is not provided, it is not bug14:47
irenabapuimedo, sounds like a feature to propose14:47
apuimedoirenab: I'm not saying it is a bug14:47
apuimedoit is giving a proper error message14:48
apuimedoI'm saying it is an inconsistency.14:48
apuimedoand that we should try to get it fixed14:49
irenabapuimedo, sounds like a feature neutron should not reject, but do not think its on the same weight as IPAM14:49
apuimedohow is it different?14:50
*** salv-orlando has quit IRC14:50
irenabI checked the spec, and it says that is possible to get reject if backend does not support allocation14:51
irenabcheck here https://specs.openstack.org/openstack/neutron-specs/specs/newton/vlan-aware-vms.html#proposed-change14:52
irenabapuimedo, looks like on the kuryr side we do need both options, depends on the backend14:53
apuimedoirenab: which reinforces my point that we should be able to make a patch that makes the default backend accept14:53
apuimedothese things14:53
apuimedoand we can have an exception handling in kuryr for those that do not support it14:53
irenabit will be nice to delegate vlan management to neutron, so keep kuryr stateless with regards to the seg. ids14:54
irenabbut for now it seems more realistic to provide seg. id management as part of kuryr14:54
irenabapuimedo, lets see if you have super power :-)14:55
apuimedoirenab: I wish14:55
apuimedoxD14:55
*** saneax-_-|AFK is now known as saneax14:59
apuimedoirenab: ivc_: vikas_: Isn't it better to have it stateless anyway. That we do a trunk show for the VM trunk. This gets us all the subports with their segmentation ids and then we request a new one? Saving the map seems a bit of a premature optimization15:00
apuimedoas it could be that soon Neutron allocates by itself and makes the optimization unnecessary15:00
*** tonanhngo has joined #openstack-kuryr15:01
apuimedoor that we see that with resource management we handle this by batching subport allocation in big chunks and we don't need the map either15:01
*** tonanhngo has quit IRC15:01
apuimedoltomasbo: read the above as well15:03
apuimedothoughts?15:03
irenabapuimedo, to request a new one, kuryr will need to check what is available15:04
ltomasboapuimedo, ok, reading15:04
irenabthe map is not meant to be persistent, right?15:05
apuimedoirenab: "15:05
apuimedoirenab: "That we do a trunk show for the VM trunk. This gets us all the subports with their segmentation ids"15:05
irenabapuimedo, but to allocate new one, we need to see wht is available15:06
irenabI am probably missing something...15:06
ltomasboirenab, yes, as neutron does not handle vlan_ids request/release for trunk ports so far15:06
apuimedoirenab: you could do both the trunk show, make a map of that and decide on an id, all inside _get_vlan_id15:07
apuimedoand rather than a map, use a frozenset15:07
ltomasboapuimedo, you mean in the neutron side or kuryr side?15:07
apuimedothis way you are encapsulating the detail of doing the vlan id allocation handling15:07
apuimedoltomasbo: on kuryr side15:07
apuimedohttps://review.openstack.org/#/c/410578/13/kuryr_kubernetes/controller/drivers/nested_vlan_vif.py15:07
apuimedohere in _get_vlan_id15:08
ltomasbowhy a frozenset?15:08
ltomasboshould not that quickly change as it is for containers?15:08
apuimedobecause we do not need to modify it15:08
apuimedoif we make it stateless15:08
apuimedoeach _get_vlan_id will request Neutron the trunk status15:09
ltomasboumm, I think I miss something, perhaps didn't start reading at the top!15:09
ltomasboahh, ok, you mean so that kuryr handles the vlan_ids but by asking neutron15:10
apuimedoltomasbo: yes15:10
ltomasbogot it15:10
apuimedowe also work with Neutron on adding allocation15:10
ltomasbothat will be slower than current approach15:10
apuimedoand if we see performance being a problem that is not solved with that (or that is not accepted) nor by resource management15:10
apuimedothen we consider caching15:11
ltomasboI agree maybe we are missing some use case for some entity/user creating subpors in the kuryr VM15:12
ltomasbobut the impact of calling neutron more times could be big for containers, if there is no such a case15:12
apuimedoltomasbo: I'm all in favor of performance optimizations if that is the case15:13
ltomasbohow I see it is that, the vlan_id collision is only in a per-vm case15:13
apuimedoright15:13
ltomasboand I though, if we dedicate a VM to create nested container with kuryr15:14
*** janki has joined #openstack-kuryr15:14
ltomasbothere will be no other users allocating subports to that VM15:14
ltomasbos/though/thought15:14
*** pcaruana has quit IRC15:15
ltomasboand, even if there were, lets say, 2 independent kuryr services inside that VM15:16
ltomasbowe could still configure them to use different vlan_id range in https://github.com/openstack/kuryr/blob/master/kuryr/lib/constants.py15:16
*** neiljerram has joined #openstack-kuryr15:16
*** tonanhngo has joined #openstack-kuryr15:19
apuimedotbh, if we suppose that, it is better to allocate all the subports ahead of time in a single batch operation15:19
*** tonanhngo has quit IRC15:19
*** saneax is now known as saneax-_-|AFK15:20
ltomasboyep, that would be an optimization from kuryr point of view, pre-creating the ports and the subport_attachments15:21
apuimedoso my point is, we can leave optimization for a follow-up patch15:22
*** hongbin has joined #openstack-kuryr15:24
apuimedoirenab: ltomasbo: Or do you prefer to have this mapping light optimization now?15:26
ltomasboIMO that could be handled later15:26
ltomasboperhaps even by adding the vlan_id management at neutron instead of kuryr15:27
ltomasboand therefore not having to worry about that anymore at kuryr side15:27
apuimedoltomasbo: that's why I said to drop the semi-persistent port mapping and see later which optimization we take15:28
ltomasboapuimedo, that is one approach, but for simplecity, efficiency, and coherency with the current patch at kuryr-libnetwork, I would leave the vlan_id management as it is right now in vikas_ patch15:29
ltomasbootherwise we should update both to always ask neutron about the 'in-use' vlan_ids for an specific trunk port, and still double check that it was really available when later calling the trunk_subport_add15:30
ltomasbono strong opinion anyway, both are ok (one faster, the other more robust)15:31
apuimedook. I'm almost convinced to let this stand15:32
apuimedoltomasbo: let me know when you check how difficult it is to add the allocation support on Neutron side15:32
ltomasbo:D15:33
ltomasbogoing to check15:33
apuimedoirenab: ivc_: vikas_: please read the conversation above and share your thoughts15:33
*** tonanhngo has joined #openstack-kuryr15:39
*** tonanhngo has quit IRC15:42
*** david-lyle has joined #openstack-kuryr15:42
*** huikang has joined #openstack-kuryr15:48
ltomasboapuimedo, right now, only one seg_driver is implemented (vlan)15:50
*** tonanhngo has joined #openstack-kuryr15:50
ltomasboapuimedo, but if there were more, and the segmentation_driver is not specified, how will you choose among the available ones? a default config variable?15:51
ltomasboseems, forcing it right now to be vlan is easy, but getting that accepted (as there may be other segmentation_driver later on) could be harder15:52
*** david-lyle has quit IRC15:55
*** mattmceuen has joined #openstack-kuryr15:57
*** limao has quit IRC16:05
*** david-lyle has joined #openstack-kuryr16:07
irenabapuimedo: I think that starting with kuryr handling the allocation (make it already optional, but by default enable) is a way to start. In parallel, proceed with neutron handling the segmentation allocation support and having sub ports precreated is a possible perfromance optimization for later16:23
*** saneax-_-|AFK is now known as saneax16:35
*** mattmceuen has quit IRC16:38
*** salv-orlando has joined #openstack-kuryr16:51
*** huikang has quit IRC16:54
*** salv-orlando has quit IRC16:54
*** huikang has joined #openstack-kuryr16:55
*** salv-orlando has joined #openstack-kuryr16:55
*** janki has quit IRC16:55
*** huikang has quit IRC16:55
*** huikang has joined #openstack-kuryr16:55
*** devvesa has quit IRC17:00
*** saneax is now known as saneax-_-|AFK17:12
apuimedoltomasbo: I want only the segmentation-type to be mandatory17:31
ltomasboI just tried some modifications to the neutron code to not need neither segmenteation_type, nor segmentation_id17:32
ltomasbojust a few lines17:32
ltomasboit gets the default seg_type plus an available set_id and do the trunk_subport_add with the proper values17:33
ltomasbohowever, the container got no connectivity, so I'm checking what I'm missing17:33
apuimedovery odd!17:37
*** tonanhngo has quit IRC17:46
apuimedoltomasbo: did you touch any agent code?17:50
ltomasbojust the plugin.py at services/trunk17:50
apuimedook17:51
*** huikang has quit IRC17:52
*** huikang has joined #openstack-kuryr17:52
apuimedoivc_: irenab: ltomasbo: vikas_: I was now thinking that since we have two components in Kuryr-kubernetes, maybe it would make sense that all the kuryr-kubernetes controller code (fromerly known as raven) would live in kuryr_kubernetes/controller/ just like the cni code resides in kuryr_kubernetes/cni17:54
apuimedoto make finding things easier17:54
ivc_apuimedo once we get to daemon-based cni, i expect that we'll have the same 'core' service shared between the controller and cni daemon17:55
apuimedothird dir for that?17:56
ivc_maybe just service.py and 'plugins' dir17:56
*** huikang has quit IRC17:56
ivc_i can't tell you now before we get the code in some shape17:57
apuimedoivc_: I'm now looking at the split18:01
apuimedosorry, not at the split, at the run files18:02
apuimedo:P18:02
* apuimedo 's mind goes back and forth18:02
ivc_apuimedo 'service' or 'actor system' or something like that - the 'middleware' - should be common in some way18:02
apuimedoright18:02
ivc_but otherwise we have most of the controller code in 'controller' package now. os-vif-util is the only exception iirc18:03
ivc_and it prolly makes sense to move os-vif-util to 'controller' package to keep things in one place18:05
apuimedoright18:10
*** garyloug has quit IRC18:15
*** huikang has joined #openstack-kuryr18:23
*** huikang has quit IRC18:42
*** huikang has joined #openstack-kuryr18:42
*** huikang has quit IRC18:47
*** david-lyle has quit IRC18:47
*** tonanhngo has joined #openstack-kuryr18:52
*** tonanhngo has quit IRC18:52
*** tonanhngo has joined #openstack-kuryr18:53
*** neiljerram has quit IRC19:41
*** neiljerram has joined #openstack-kuryr19:43
*** david-lyle has joined #openstack-kuryr19:50
*** neiljerram has quit IRC19:51
*** salv-orlando has quit IRC20:11
*** huikang has joined #openstack-kuryr20:19
*** huikang_ has joined #openstack-kuryr20:22
*** huikang has quit IRC20:23
*** janonymous has quit IRC20:34
*** severion has joined #openstack-kuryr20:51
openstackgerritMerged openstack/kuryr: Updated from global requirements  https://review.openstack.org/41879221:17
*** portdirect is now known as portdirect_away21:30
*** severion has quit IRC21:39
*** huikang_ has quit IRC21:51
*** huikang has joined #openstack-kuryr21:52
*** huikang has quit IRC21:56
*** huikang has joined #openstack-kuryr21:59
*** portdirect_away is now known as portdirect22:07
*** huikang has quit IRC22:09
*** huikang has joined #openstack-kuryr22:10
*** yamamoto has joined #openstack-kuryr22:11
*** huikang has quit IRC22:13
*** huikang has joined #openstack-kuryr22:14
*** huikang has quit IRC22:14
*** salv-orlando has joined #openstack-kuryr22:28
*** david-lyle has quit IRC22:51
*** janonymous has joined #openstack-kuryr23:00
*** salv-orlando has quit IRC23:21
*** mattmceuen has joined #openstack-kuryr23:33
*** mattmceuen has quit IRC23:40

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