Monday, 2018-03-19

*** hongbin has joined #openstack-meeting-400:12
*** yamamoto has joined #openstack-meeting-400:13
*** iyamahat has quit IRC00:16
*** yamamoto has quit IRC00:18
*** bobh has joined #openstack-meeting-400:44
*** zhubingbing has joined #openstack-meeting-400:47
*** zhubingbing has quit IRC00:52
*** yamamoto has joined #openstack-meeting-401:13
*** zhurong has joined #openstack-meeting-401:16
*** yamamoto has quit IRC01:19
*** yamamoto has joined #openstack-meeting-401:41
*** VW has joined #openstack-meeting-401:59
*** iyamahat has joined #openstack-meeting-402:24
*** zhurong has quit IRC02:36
*** zhurong has joined #openstack-meeting-402:37
*** zhubingbing has joined #openstack-meeting-402:49
*** psachin has joined #openstack-meeting-402:50
*** salv-orl_ has joined #openstack-meeting-402:51
*** salv-orlando has quit IRC02:53
*** zhubingbing has quit IRC02:53
*** VW_ has joined #openstack-meeting-403:01
*** VW has quit IRC03:03
*** caoyuan has joined #openstack-meeting-403:08
*** caoyuan_ has joined #openstack-meeting-403:15
*** caoyuan has quit IRC03:18
*** Kevin_Zheng has quit IRC03:40
*** hongbin has quit IRC03:44
*** janki has joined #openstack-meeting-403:50
*** janki is now known as janki|office_ina03:51
*** caoyuan_ has quit IRC03:54
*** wxy has quit IRC03:56
*** caoyuan has joined #openstack-meeting-404:00
*** caoyuan has quit IRC04:04
*** caoyuan has joined #openstack-meeting-404:07
*** bobh has quit IRC04:11
*** caoyuan has quit IRC04:12
*** anilvenkata has joined #openstack-meeting-404:17
*** caoyuan has joined #openstack-meeting-404:17
*** caoyuan has quit IRC04:18
*** bobh has joined #openstack-meeting-404:20
*** bobh has quit IRC04:25
*** bobh has joined #openstack-meeting-404:34
*** anilvenkata has quit IRC04:38
*** bobh has quit IRC04:39
*** bobh has joined #openstack-meeting-404:43
*** bobh has quit IRC04:48
*** zhubingbing has joined #openstack-meeting-404:49
*** bobh has joined #openstack-meeting-404:51
*** zhubingbing has quit IRC04:54
*** anilvenkata has joined #openstack-meeting-404:57
*** bobh has quit IRC04:57
*** bobh has joined #openstack-meeting-405:00
*** lpetrut has joined #openstack-meeting-405:01
*** zhurong has quit IRC05:04
*** bobh has quit IRC05:04
*** bobh has joined #openstack-meeting-405:10
*** bobh has quit IRC05:10
*** bobh has joined #openstack-meeting-405:21
*** bobh has quit IRC05:25
*** iyamahat has quit IRC05:49
*** lpetrut has quit IRC05:50
*** bobh has joined #openstack-meeting-405:53
*** trinaths has joined #openstack-meeting-405:54
*** aniketh has joined #openstack-meeting-405:57
*** bobh has quit IRC05:58
*** bobh has joined #openstack-meeting-406:00
*** bobh has quit IRC06:05
*** bobh has joined #openstack-meeting-406:12
*** yboaron has joined #openstack-meeting-406:15
*** bobh has quit IRC06:17
*** bobh has joined #openstack-meeting-406:20
*** kiennt26 has joined #openstack-meeting-406:22
*** bobh has quit IRC06:25
*** bobh has joined #openstack-meeting-406:31
*** radeks has joined #openstack-meeting-406:37
*** bobh has quit IRC06:37
*** alexchadin has joined #openstack-meeting-406:39
*** gcheresh has joined #openstack-meeting-406:41
*** bobh has joined #openstack-meeting-406:41
*** bobh has quit IRC06:46
*** gcheresh has quit IRC06:47
*** gcheresh has joined #openstack-meeting-406:48
*** anilvenkata has quit IRC06:49
*** d0ugal has joined #openstack-meeting-407:00
*** d0ugal has quit IRC07:00
*** d0ugal has joined #openstack-meeting-407:00
*** zhurong has joined #openstack-meeting-407:00
*** bobh has joined #openstack-meeting-407:03
*** anilvenkata has joined #openstack-meeting-407:05
*** bobh has quit IRC07:08
*** bobh has joined #openstack-meeting-407:11
*** bobh has quit IRC07:16
*** anilvenkata has quit IRC07:18
*** bobh has joined #openstack-meeting-407:23
*** bobh has quit IRC07:27
*** pcaruana has joined #openstack-meeting-407:39
*** bobh has joined #openstack-meeting-407:42
*** bobh has quit IRC07:47
*** zhubingbing has joined #openstack-meeting-407:51
*** trinaths has quit IRC07:53
*** zhurong has quit IRC07:54
*** bobh has joined #openstack-meeting-407:55
*** zhubingbing has quit IRC07:55
*** lpetrut has joined #openstack-meeting-407:57
*** bobh has quit IRC07:59
*** lpetrut_ has joined #openstack-meeting-408:00
*** lpetrut has quit IRC08:00
lihi#startmeeting Dragonflow08:01
openstackMeeting started Mon Mar 19 08:01:37 2018 UTC and is due to finish in 60 minutes.  The chair is lihi. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: Dragonflow)"08:01
openstackThe meeting name has been set to 'dragonflow'08:01
snapiriHi08:01
irenabhi08:01
lihiI'll be borrowing oanson chair today08:02
snapirijump on :)08:02
lihi#topic Roadmap08:02
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"08:02
lihiSkydive08:03
lihisnapiri, any updates?08:03
snapirithis is in progress. Working on the requirements08:03
snapiriIt is a bit more complicated than I expected ;)08:03
snapiribut progressing.08:03
snapirinext item will be to start it as a separate daemon08:03
snapiriSpec was already integrated08:04
snapiri(merged)08:04
irenabsnapiri, the spec looks good08:04
lihiYes. Out gate issues got the merge to delayed a bit08:04
irenabmy suggestion is to drop functionaly one by one (iterations), not all at once08:05
snapiriirenab: will do08:05
snapiribut it will have to be one on top of the other08:05
irenabmaybe, but maybe there can be separate features, once you have the basic support08:06
snapiriI will try to keep the changes as small as possible08:07
lihiSmall patches are always a good thing08:08
lihiIGMP:08:08
lihiI don't have updates for this. But after reading the spec, the spec will need to be updated08:09
lihiI will do that soon08:09
lihiApplication decoupling:08:10
irenablihi, do you have a link for the spec?08:10
irenabigmp?08:10
lihi1 moment08:10
lihi#link https://github.com/openstack/dragonflow/blob/master/doc/source/specs/igmp_application_and_multicast_support.rst08:11
lihiI think it was originally wrote by oanson08:12
snapiriyes. https://review.openstack.org/#/c/278400/08:13
irenabthanks08:13
lihiApplication decoupling:08:14
lihiI didn't see much progress last week. I guess dimak was mostly busy with other projects08:14
lihiBGPVPN and RPM:08:15
lihiAs what oanson wrote in the meeting last week, there are no updates08:16
lihiOSA:08:17
lihiI have good news and bad news08:17
snapiri:)08:17
irenabstart with the good08:17
lihiThe good news: I finally succeed in deploy an env with dragonflow using osa08:18
lihiThe bad news: it is not working well08:18
lihiLooks like the pubsub is not behaving nicely08:18
irenabetcd based?08:19
lihiredis08:19
lihiI still don't know if that is because it is a multi node env, or because of deploying it poorly08:19
irenabSome deployment settings?08:19
lihiSo I'm checking both directions08:19
lihiBut other than that, if you don't want to use pubsub it is working :)08:20
snapiriexcellent progress08:21
irenabso probably it is fine for small environments, but still not good for production grade08:21
lihiYes. Though I plan on getting the pubsub working08:22
irenablihi, any details how to try it?08:22
lihiCurrently allmy changes are done on my clones in github:08:24
irenabmaybe worth to push for the basic one , that works without pubsub?08:24
lihihttps://github.com/lihiwish/openstack-ansible-os_neutron/tree/dragonflow08:25
*** janki|office_ina has quit IRC08:25
lihiBecause the pubsub is not working, some of the fullstack tests fail08:25
lihiSo the gate still appear red08:25
irenabMaybe these tests can be disabled till the issue is sorted out?08:26
*** numans_ has joined #openstack-meeting-408:26
lihiGood idea. I will do that08:26
*** yboaron has quit IRC08:27
lihiAnything else for roadmap?08:27
lihi#topic Bugs08:28
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"08:28
*** numans has quit IRC08:29
lihiBug 174073908:29
openstackbug 1740739 in DragonFlow "Security group mismatch for floating IP" [High,New] https://launchpad.net/bugs/1740739 - Assigned to Omer Anson (omer-anson)08:29
lihiosnson havn't updated me on this bug, so I guess he is still working on solving all the different scenarios.08:29
lihiAnything else for bugs?08:29
snapiriOur gate was broken last week probably due to infra changes08:29
snapiriI got some fix in, if there are any other gates broken, let me know :)08:30
lihiThanks:)08:31
lihi#topic Open Discussion08:31
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"08:31
lihiDo you have anything you want to discuss?08:31
snapirinothing here08:31
irenabnothing on my side08:31
lihiOk08:32
lihiThank you for coming!08:32
snapiriCheers08:32
lihi#endmeeting08:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:32
openstackMeeting ended Mon Mar 19 08:32:20 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2018/dragonflow.2018-03-19-08.01.html08:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2018/dragonflow.2018-03-19-08.01.txt08:32
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2018/dragonflow.2018-03-19-08.01.log.html08:32
*** numans has joined #openstack-meeting-408:38
*** slaweq has quit IRC08:38
*** numans_ has quit IRC08:42
*** numans has quit IRC08:42
*** numans has joined #openstack-meeting-408:48
*** iyamahat has joined #openstack-meeting-408:50
*** bobh has joined #openstack-meeting-408:51
*** bobh has quit IRC08:56
*** iyamahat has quit IRC08:57
*** yamahata has quit IRC08:58
*** diman has joined #openstack-meeting-408:59
*** slaweq has joined #openstack-meeting-409:00
*** salv-orl_ has quit IRC09:09
*** salv-orlando has joined #openstack-meeting-409:09
*** bobh has joined #openstack-meeting-409:14
*** salv-orlando has quit IRC09:14
*** anilvenkata has joined #openstack-meeting-409:18
*** psachin has quit IRC09:19
*** bobh has quit IRC09:19
*** gcheresh has quit IRC09:21
*** caoyuan has joined #openstack-meeting-409:21
*** gcheresh has joined #openstack-meeting-409:21
*** bobh has joined #openstack-meeting-409:21
*** diman has quit IRC09:21
*** psachin has joined #openstack-meeting-409:24
*** bobh has quit IRC09:26
*** gibi_ is now known as gibi09:30
*** bobh has joined #openstack-meeting-409:30
*** bobh has quit IRC09:35
*** trinaths has joined #openstack-meeting-409:42
*** yboaron has joined #openstack-meeting-409:47
*** inc0 has quit IRC09:50
*** bobh has joined #openstack-meeting-409:57
*** bobh has quit IRC10:01
*** inc0 has joined #openstack-meeting-410:03
*** bobh has joined #openstack-meeting-410:05
*** trinaths has quit IRC10:05
*** sambetts_ is now known as sambetts10:08
*** bobh has quit IRC10:10
*** kiennt26 has quit IRC10:10
*** bobh has joined #openstack-meeting-410:12
*** yamamoto has quit IRC10:16
*** aniketh has quit IRC10:16
*** bobh has quit IRC10:16
*** caoyuan has quit IRC10:17
*** salmankhan has joined #openstack-meeting-410:19
*** bobh has joined #openstack-meeting-410:22
*** salmankhan has quit IRC10:23
*** salmankhan has joined #openstack-meeting-410:23
*** bobh has quit IRC10:28
*** bobh has joined #openstack-meeting-410:45
*** gcheresh has quit IRC10:47
*** gcheresh has joined #openstack-meeting-410:48
*** bobh has quit IRC10:51
*** bobh has joined #openstack-meeting-410:51
*** zhubingbing has joined #openstack-meeting-410:54
*** bobh has quit IRC10:56
*** chason has quit IRC10:57
*** chason has joined #openstack-meeting-410:58
*** zhubingbing has quit IRC10:58
*** seajay has joined #openstack-meeting-410:59
*** bobh has joined #openstack-meeting-411:01
*** yamamoto has joined #openstack-meeting-411:02
*** salv-orlando has joined #openstack-meeting-411:05
*** bobh has quit IRC11:06
*** bobh has joined #openstack-meeting-411:13
*** bobh has quit IRC11:18
*** bobh has joined #openstack-meeting-411:20
*** alexchadin has quit IRC11:21
*** alexchadin has joined #openstack-meeting-411:21
*** alexchadin has quit IRC11:21
*** alexchadin has joined #openstack-meeting-411:22
*** pbourke_ has quit IRC11:22
*** alexchadin has quit IRC11:22
*** pbourke_ has joined #openstack-meeting-411:22
*** alexchadin has joined #openstack-meeting-411:23
*** gcheresh_ has joined #openstack-meeting-411:23
*** alexchadin has quit IRC11:23
*** alexchadin has joined #openstack-meeting-411:24
*** alexchadin has quit IRC11:24
*** alexchadin has joined #openstack-meeting-411:24
*** alexchadin has quit IRC11:24
*** bobh has quit IRC11:25
*** gcheresh_ has quit IRC11:27
*** bobh has joined #openstack-meeting-411:30
*** chason has quit IRC11:35
*** alexchadin has joined #openstack-meeting-411:35
*** chason has joined #openstack-meeting-411:35
*** bobh has quit IRC11:36
*** bobh has joined #openstack-meeting-411:40
*** bobh has quit IRC11:45
*** aniketh has joined #openstack-meeting-411:45
*** alexchadin has quit IRC11:49
*** logan- has quit IRC11:52
*** logan- has joined #openstack-meeting-411:52
*** salmankhan has quit IRC11:52
*** bobh has joined #openstack-meeting-411:53
*** psachin has quit IRC12:00
*** VW_ has quit IRC12:01
*** salmankhan has joined #openstack-meeting-412:07
*** psachin has joined #openstack-meeting-412:11
*** julim has quit IRC12:14
*** julim has joined #openstack-meeting-412:15
*** chason has quit IRC12:19
*** chason has joined #openstack-meeting-412:19
*** julim has quit IRC12:20
*** bobh has quit IRC12:23
*** dmellado has quit IRC12:24
*** chason has quit IRC12:25
*** chason has joined #openstack-meeting-412:25
*** dmellado has joined #openstack-meeting-412:27
*** yboaron_ has joined #openstack-meeting-412:30
*** tobberydberg_ has joined #openstack-meeting-412:30
*** yboaron has quit IRC12:33
*** tobberydberg_ has quit IRC12:35
*** mjturek has joined #openstack-meeting-412:45
*** VW has joined #openstack-meeting-412:53
*** yamamoto has quit IRC13:08
*** julim has joined #openstack-meeting-413:12
*** lyan has joined #openstack-meeting-413:18
*** lyan is now known as Guest6846113:18
*** psachin has quit IRC13:24
*** mjturek has quit IRC13:35
*** yamamoto has joined #openstack-meeting-413:45
*** psachin has joined #openstack-meeting-413:47
*** yboaron_ has quit IRC13:48
*** yamamoto_ has joined #openstack-meeting-413:48
*** yamamoto has quit IRC13:52
*** kaliya has joined #openstack-meeting-413:54
*** julim_ has joined #openstack-meeting-413:55
*** zhubingbing has joined #openstack-meeting-413:56
*** julim has quit IRC13:57
*** yboaron_ has joined #openstack-meeting-414:00
*** hongbin has joined #openstack-meeting-414:00
dmellado#startmeeting kuryr14:01
openstackMeeting started Mon Mar 19 14:01:19 2018 UTC and is due to finish in 60 minutes.  The chair is dmellado. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
*** zhubingbing has quit IRC14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: kuryr)"14:01
openstackThe meeting name has been set to 'kuryr'14:01
dmelladoHi fellow kuryrs, who's here today for the meeting?14:01
*** zhubingbing has joined #openstack-meeting-414:01
duleko/14:02
yboaron_o/14:02
ltomasboo/14:02
*** beekneemech is now known as bnemec14:02
*** TxGirlGeek has joined #openstack-meeting-414:02
irenabhi14:02
dmellado#chair dulek yboaron_ ltomasbo irenab14:03
openstackCurrent chairs: dmellado dulek irenab ltomasbo yboaron_14:03
kaliyao/14:03
dmelladoHi kaliya14:03
dmelladoso, let's start14:03
dmellado#topic kuryr-kubernetes14:03
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:03
dmelladoI wanted to share with you that after a few days of CI crisis we should be fine for the time being14:04
*** celebdor has joined #openstack-meeting-414:04
dmelladoI'll be trying to decouple a few dependencies14:04
*** maysamacedos has joined #openstack-meeting-414:04
dmelladoso if you've any patch that failed recently, and specially with post_failure, please do recheck it14:05
dmelladoit might not be your fault14:05
dmelladoI'll be also adding some multinode gates during the upcoming days, now with proper services split14:05
dmellado2 and 4 nodes, probably14:05
dmelladoso, besides that, who has something that would love to share? :P14:05
*** psachin has quit IRC14:06
irenabdmellado, is there any news regarding sr-iov/dpdk patches?14:07
*** gcheresh_ has joined #openstack-meeting-414:07
*** gcheresh has quit IRC14:07
dmelladoirenab, not really, maybe kaliya can update us on that14:08
dmelladoI asked the intel foiks to update the blueprint with their contributions/info14:08
kaliyanot much. I know danil is working on rebasing the sr-iov part. For the nested part, I saw somewhere some binary file including some Intel patch14:08
dmelladohttps://blueprints.launchpad.net/kuryr-kubernetes/+spec/nested-dpdk-support14:09
dmelladokaliya: yeah, they sent us a diff file but I asked them to put a proper review so we could take a look and review14:09
dmelladotbh I was hoping that Gary was on the call today to ask him about that14:09
dmelladoirenab: Will send him an email ad cc you14:09
irenabdmellado, thanks14:10
dmelladokaliya: thanks on the sriov side, btw14:10
kaliyayes, that diff has some syntax issues, thank you dmellado14:10
yboaron_Question: Do we plan to merge the multi vif/dpdk/sr-iov patches in current approach, or to wait/sync with what vikasc presented14:10
dmelladoalso tbh I would bet on that diff needing a rebase as well14:10
*** gcheresh has joined #openstack-meeting-414:11
dmelladoyboaron_: they have been there for a while, so I'd get there on their current state once they're good to go14:11
kaliyawhat's vikasc "presentation" ?14:11
dmelladoand add vikasc approach on a follow-up patch14:11
irenabdmellado, +114:11
dmelladokaliya: he did send an email to the ML but should be recorded14:11
*** mjturek has joined #openstack-meeting-414:11
*** gcheresh_ has quit IRC14:11
kaliyaI missed that14:11
*** zhubingbing has quit IRC14:11
dmelladokaliya: I'll ask him for the record link and send an email, no worries14:12
kaliyathanks!14:12
*** bobh has joined #openstack-meeting-414:13
dmelladoyw!14:13
irenabkaliya, the slides https://docs.google.com/presentation/d/1_Yu88NA--afhal5uBipQymGqbNKagi-p2kr9acyH8CM/edit#slide=id.g3525172c70_0_014:13
kaliyaahh this one, yes thanks irenab14:13
dmelladoall right, any another topic or patches that would require attention?14:15
dmelladoltomasbo: yboaron_ dulek ?14:15
dulekdmellado: Not much from my side regarding kuryr-kubernetes.14:15
ltomasbonot much either, perhaps just take a look at the patch:14:16
ltomasbohttps://review.openstack.org/#/c/54867314:16
*** gcheresh has quit IRC14:16
yboaron_dmellado, neither from my side14:16
ltomasboit will be interesting to agree on going for network ids or subnet ids for the pools14:16
ltomasbowith their respective pros and cons14:17
dmelladoltomasbo: will do, tbh though this was already merged14:17
dmelladowill take a look14:17
ltomasbothanks14:17
*** psachin has joined #openstack-meeting-414:17
dmellado#topic kuryr-libnetwork14:17
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:17
irenabltomasbo, what is the argument?14:17
ltomasboirenab, the current patch assumes there is only one subnet per network14:18
irenabltomasbo, so to make it generic case, need to take subnet_id and not network_id into account?14:18
ltomasboirenab, if we use subnet ids instead, we will support multiple subnets per network, but it will have some performance impact, as we need to call neutron to get subnets ids from network ids14:18
ltomasbowhich is the information at the vif object14:19
ltomasbowell, I'm not sure we need multiple subnets per network14:19
ltomasboand celebdor said that their support in neutron is so-so too14:19
dmelladoltomasbo: maybe dual stack, but I'll have to think about it14:20
ltomasbothat is the only case, and it seems it is not that realistic/useful either14:20
irenabwe need to see the use case14:20
ltomasbofor a generic use case, network_id is enough14:20
irenabas long as there is no specific use case, may go with net_id14:20
ltomasbothere may be some corner cases were subnet id may be needed I guess14:21
dmelladoyeah, I don't really think that it might be worth the performance hit14:21
ltomasbo*where14:21
dmelladoltomasbo: you're more than welcome to add tests regarding the corner cases14:21
irenaband the framwork should be flexible enough to add multi subnets in the future is needed14:21
celebdorltomasbo: can you remind me why there is a perf impact on using subnet id?14:21
*** mjturek has quit IRC14:21
ltomasboyes, it is switching one key by the other andthe way to obtain it14:21
ltomasbocelebdor, vif obj has already the network id14:22
celebdorwhere do we obtain the netid from?14:22
celebdorthat's what I thought14:22
celebdorbut I thought that vif also has subnets14:22
ltomasbobut if we want to use the subnet_id we need to retrieve it from the network id + subnet range14:22
celebdorin fact I thought we even get the IP address from subnets14:22
celebdor(of the vif object)14:23
ltomasbocelebdor, we do get the subnet cidr14:23
ltomasbobut not the uuid14:23
*** psachin has quit IRC14:23
yboaron_ltomasbo, I Assume that caching will help with performance, how many network to we intend to support ?14:23
yboaron_networks14:23
ltomasboI thought about that too14:24
ltomasbobut it may have some problems14:24
irenabthe performance impact can be itigatred if kuryr will fetch subnets on start-up14:24
celebdorltomasbo: ah... Another instance of crappy (for our purposes) os-vif information structure14:24
ltomasbowe need to base it on the network ui and the subnet range14:24
ltomasboand then you can actually remove the subnet and create another one, with same range (and different uuid)14:24
ltomasboso, caching could be tricky, and assuming the subnets are already there could not cover all the use cases, for instance creating new subnets for each namespace14:25
dmelladoyeah, if we cache and create new subnets then we're screwed again14:26
yboaron_ltomasbo, yes, that's a good point14:26
ltomasboanother option could be to use network_id + subnet cidr14:26
ltomasbothat should be unique14:26
ltomasbobut perhaps a bit ugly...14:26
irenabdo we capture per namespace subnet discussion somewhere?14:26
irenabnot pool specific parts only?14:27
ltomasbonot yet, I'm working on a PoC, and will write a devref soon14:27
celebdordulek: I sort of feel that with KuryrPort CRDs we would not have that much of a problem14:28
irenabmaybe worth to discuss the the full picture14:28
dmelladoirenab: +114:28
yboaron_+114:28
dulekcelebdor: Well, K8s API is much more reliable than Neutorn.14:28
dulekcelebdor: But we still get synchronization issues, right?14:28
ltomasboirenab, yes, but adding the network id to the pools is related but not only targeting the subnet per namespace14:28
dmelladoltomasbo: let's add in any case some docs to your patch14:29
dmelladoI'll fetch you tomorrow at the office14:29
ltomasboas if you have pools enabled, and change the subnet_id at kuryr.conf and restart the controller, it will lead you to error14:29
ltomasbonot to error, to the pods in a different subnet14:29
celebdordulek: like?14:29
irenabltomasbo, agree, but some scenarious you consider seems to be driven by multi-subnet network14:29
*** yamamoto_ has quit IRC14:30
ltomasboirenab, could be, but the initial though was on making kuryr namespace aware, more than the multi-subnet driver14:30
celebdorWith KuryrPort you'd just get the subnet_id from the driver, create the KuryrPort objects in the K8s API14:30
*** mjturek has joined #openstack-meeting-414:30
celebdorthat are assigned to specific Host14:31
dulekcelebdor: Like when creating and changing subnets? Don't know yet TBH.14:31
dulekcelebdor: Mhm.14:31
irenabcelebdor, how driver will fetch the subnet_id?14:31
celebdorirenab: that's driver specific14:31
celebdorone can be configuration14:32
ltomasbocelebdor, for the subnet per namespace object we could also add subnet id to the CRDs, and use them for the pools14:32
irenabcall neutron?14:32
celebdorltomasbo: yes, I thought about KuryrSubnet14:32
ltomasbobut that will solve only that case14:32
celebdorand have the namespace annotated to point to it14:32
*** salv-orlando has quit IRC14:32
ltomasbocelebdor, I already have a kuryrNet in my Pod :)14:32
ltomasboPoC14:32
celebdorirenab: "call neutron" That usually only makes things worse :P14:32
*** salv-orlando has joined #openstack-meeting-414:33
celebdorltomasbo: that's good14:33
celebdorso... I feel like this needs a videochat discussion :P14:34
ltomasboxD14:34
yboaron_Yeppppppp14:34
ltomasboI agree, but why if we start with 1 subnet per network, and if we find out a use case for more than a subnet per network, then move to subnet_ids14:35
ltomasboit will be much simple and if there is no such use case, it will not pay off14:35
irenab+114:35
ltomasbo(and perhaps the best solution is to include the subnet id at the os-vif object actually)14:36
celebdorltomasbo: okay, okay14:36
ltomasbothat will bring consistency across drivers/pools14:36
celebdorltomasbo: you have my +214:36
celebdorbut if we get to the end of the cycle in this state I'll get grumpy14:37
dmelladocelebdor: like always14:37
celebdorI really want to move state to CRDs14:37
dmelladoxD14:37
yboaron_ltomasbo, you have my +1 for ... video chat :-)14:37
celebdordmellado: but a bit more14:37
ltomasboxD14:37
dmelladoin any case yah, let's do a bluejeans call on the topic14:37
celebdorltomasbo: since you prolly have more meetings, send the invite :P14:38
ltomasbocelebdor, what do you want to move to CRDs? for all the pools? or the cni pool ones?14:38
celebdorltomasbo: I want the Pools to be de facto backed by KuryrPort objects in the API14:38
ltomasboor you mean to move pools to CRD regardless of the driver14:39
celebdorso that reloading is not a Neutron search operation, but a GET on K8s14:39
*** mjturek has quit IRC14:39
celebdorlike what kuryr CNI side pools PoC by dulek is doing14:39
ltomasbowell, reloading is cheap enough now14:39
celebdorltomasbo: I don't mean it just because of this14:40
celebdorI'm just trying to consolidate state on the K8s side14:40
celebdorhaving much in both sides makes me uneasy14:40
ltomasbook, anyway, I'll send an invite for a call14:40
dulekAre w talking kuryr-libnetwork now?14:41
ltomasbogo!14:41
dulekThere's this fix I've wrote for Neutron extensions getting deprecated: https://review.openstack.org/#/c/55375614:41
duleks/deprecated/removed14:41
dulekNeutron patch is depending on this one, so it'll be great to get it reviewed.14:42
*** mjturek has joined #openstack-meeting-414:42
celebdordulek: alrighty14:42
dulekI've already tested it here: https://review.openstack.org/#/c/553763, looks like things are working.14:42
dmelladodulek: saw it, will review14:42
dulekThanks!14:43
*** VW has quit IRC14:43
irenabdulek, will +2 once zuul is happy14:43
dmelladoyep14:43
*** VW has joined #openstack-meeting-414:43
dmellado# open discussion14:44
dmellado#topic open discussion14:44
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:44
celebdordulek: looks good to me14:44
celebdorirenab: dmellado: are you both going to the summit?14:44
celebdorCause I got some requests to confirm my attendance due to the accepted talks14:45
celebdorand as you know I won't be able to make it this time14:45
irenabcelebdor, I am not sure yet, will update14:45
dmelladocelebdor: I am, I'll need still ack fron irena, yep14:45
*** yamamoto has joined #openstack-meeting-414:46
yboaron_the Israeli summit ? :=)14:46
dmelladoyboaron_: the Vancouver one14:46
dmellado:P14:46
celebdoryboaron_: that one I'm counting with you and irenab for14:46
yboaron_dmellado, kidding14:46
*** salv-orlando has quit IRC14:46
celebdorI'd love to go though14:46
celebdorand the weather is nicer than in Vancouver14:47
*** salv-orlando has joined #openstack-meeting-414:47
dmelladocelebdor: in any case throw the session to me and I'll see how can I manage14:47
irenabcelebdor, not sure about the weather14:47
yboaron_I'm sure about the weather!14:47
dmelladoit can't be worse than Dublin14:47
irenabits about +33 here today14:47
ltomasbodmellado, are you also taking the other one (SF one?)14:48
dmellado+33? how much humidity?14:48
celebdordmellado: I already did14:48
dmelladoltomasbo: yeah, those are lightning talks so I could handle14:48
dmelladobut I'll see if I can get cospeakers14:48
ltomasbook14:48
celebdordmellado: the humidity depends on how much you sweat14:48
celebdorxD14:48
irenabltomasbo, are you planning to attend the summit?14:48
dmelladoltomasbo: you're always welcome to come along, though14:49
dmelladoirenab: we split the SF project and the Summit and ltomasbo will travel closer xD14:49
ltomasboirenab, I don't think so, going all the way to Vancouver for just 10 minutes talk...14:49
dmelladoltomasbo: you can also come along for some another session xD14:49
ltomasbodmellado, closer but more boring...14:49
irenabI think it has potential to become 40 mins14:49
dmelladoso far I've got 2 lightning talks14:49
dmellado+ one full talk14:49
dmellado+ project updates14:50
dmellado+ project oboarding14:50
dmelladoman, so much for me xD14:50
ltomasboxD14:50
*** yamahata has joined #openstack-meeting-414:50
irenabdmellado, sounds like you will miss the Dublin summit ...14:50
dmelladoand the worst thing is that my girlfriend expects me to go to the wedding from her friend the next day after I'm back xD14:50
kaliyayou can bring a nice present:)14:51
*** zhubingbing has joined #openstack-meeting-414:51
dmelladoirenab: you go and grab someone from toga if you can't make it in the end xD14:51
irenab:-)14:51
*** salv-orlando has quit IRC14:51
*** yamamoto has quit IRC14:51
dmelladoanyways, it's being a looong meeting day and I still didn't get to have lunch14:52
dmelladoso thanks for attending14:52
dmelladoand bon apetit! xD14:52
kaliyabye14:52
dmelladoxD14:52
celebdorthank you all!14:52
irenabbye14:52
yboaron_bbye14:52
dmellado#endmeeting kuryr14:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:52
openstackMeeting ended Mon Mar 19 14:52:27 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-03-19-14.01.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-03-19-14.01.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-03-19-14.01.log.html14:52
*** maysamacedos has quit IRC14:54
*** chyka has joined #openstack-meeting-414:55
*** yamamoto has joined #openstack-meeting-415:04
*** VW has quit IRC15:06
*** iyamahat has joined #openstack-meeting-415:11
*** VW has joined #openstack-meeting-415:28
*** chyka has quit IRC15:30
*** chyka has joined #openstack-meeting-415:30
*** VW_ has joined #openstack-meeting-415:35
*** VW_ has quit IRC15:35
*** VW_ has joined #openstack-meeting-415:36
*** VW has quit IRC15:38
*** VW__ has joined #openstack-meeting-415:38
*** VW_ has quit IRC15:38
*** VW has joined #openstack-meeting-415:45
*** VW__ has quit IRC15:45
*** mjturek has quit IRC15:51
*** mjturek has joined #openstack-meeting-415:53
*** markvoelker_ has joined #openstack-meeting-415:56
*** markvoelker has quit IRC15:56
*** markvoelker has joined #openstack-meeting-415:59
*** markvoelker_ has quit IRC16:01
*** salv-orlando has joined #openstack-meeting-416:05
*** pcaruana has quit IRC16:07
*** salv-orlando has quit IRC16:09
*** mjturek has quit IRC16:10
*** lpetrut_ has quit IRC16:10
*** mjturek has joined #openstack-meeting-416:11
*** zhubingbing has quit IRC16:11
*** gcheresh has joined #openstack-meeting-416:15
*** mjturek has quit IRC16:15
*** salv-orlando has joined #openstack-meeting-416:18
*** gcheresh has quit IRC16:18
*** gcheresh has joined #openstack-meeting-416:19
*** TxGirlGeek has quit IRC16:20
*** VW has quit IRC16:22
*** VW has joined #openstack-meeting-416:22
*** yamamoto has quit IRC16:23
*** VW has quit IRC16:23
*** kaliya has left #openstack-meeting-416:23
*** VW has joined #openstack-meeting-416:24
*** gcheresh has quit IRC16:25
*** VW has quit IRC16:28
*** yboaron_ has quit IRC16:35
*** VW has joined #openstack-meeting-416:38
*** VW_ has joined #openstack-meeting-416:39
*** VW_ has quit IRC16:39
*** VW_ has joined #openstack-meeting-416:39
*** gcheresh has joined #openstack-meeting-416:40
*** VW has quit IRC16:43
*** TxGirlGeek has joined #openstack-meeting-416:44
*** VW_ has quit IRC16:47
*** VW has joined #openstack-meeting-416:48
*** VW has quit IRC16:48
*** VW has joined #openstack-meeting-416:49
*** ejat has joined #openstack-meeting-417:00
beisner#startmeeting charms17:00
openstackMeeting started Mon Mar 19 17:00:41 2018 UTC and is due to finish in 60 minutes.  The chair is beisner. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: charms)"17:00
beisnero/ hi all17:00
openstackThe meeting name has been set to 'charms'17:00
thedaco/17:00
beisner#topic Review ACTION points from previous meeting17:01
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:01
coreycbo/17:01
*** TxGirlGeek has quit IRC17:02
beisneri don't see any action points from the previous meeting, hanging for a sec in case anyone has something to raise in this section..17:02
*** mjturek has joined #openstack-meeting-417:02
beisner#topic State of Development for next Charm Release17:02
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:02
thedacWe were in Budapest on 2018-03-05 and the previous only had completed action items17:02
beisnerack'17:03
beisner#link https://docs.openstack.org/charm-guide/latest/release-schedule.html17:03
*** TxGirlGeek has joined #openstack-meeting-417:03
beisnernext freeze and release dates are in the charm-guide, subject to move if any crit type bugs are discovered.17:03
beisneranything to add?17:03
*** iyamahat has quit IRC17:04
beisner#topic High Priority Bugs17:04
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:04
beisner#link https://bugs.launchpad.net/openstack-charms/+bugs17:04
beisnerall crit bugs are in progress or fix committed17:04
*** yamahata has quit IRC17:05
beisnerwe have a load of 'high' bugs17:05
beisner(== everything is important!)17:05
thedac:)17:05
beisner:)17:05
beisnerUse stable-backport tag for bugs  http://tinyurl.com/charm-stable-backports17:06
beisnerlooks like no actionable items there, good.17:07
thedacThanks, I was searching for that tag recently17:07
beisnerThere is one crit bug which gnuoy has underway:  https://bugs.launchpad.net/charm-neutron-api/+bug/175352617:08
openstackLaunchpad bug 1753526 in OpenStack neutron-api charm "Neutron-api attempts to use keystone v2 api in Queens for designate calls" [Critical,Confirmed] - Assigned to Liam Young (gnuoy)17:08
beisnerok, i'm not finding a patch up for that.  given that he is out today, we can touch base tomorrow.17:09
beisnerbefore moving on, anyone have any bug-related discussion?17:10
beisner#topic Openstack Events17:10
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:10
beisnerso, we had a number of people attend #openstuck in dublin17:10
thedacha17:10
beisnerany news to share here?17:10
tinwoodapart from lots of snow ...17:11
thedac#link https://www.openstack.org/summit/vancouver-201817:11
tinwoodthere was a discussion about releases.17:11
beisnervancouver summit is right around the corner, we'll have several people there.17:11
beisnerany traction on the annual release?  or was that squashed?17:11
tinwoodthat was largely squashed.17:11
tinwoodIt's sticking at 6 months as of the PTG17:11
beisnerok17:11
beisnerhow about the upstream lts ideas?17:12
*** zhubingbing has joined #openstack-meeting-417:12
*** lpetrut has joined #openstack-meeting-417:12
tinwoodlots of discussion; but people didn't seem to keen on it.17:12
*** TxGirlGeek has quit IRC17:12
beisnerit will take a small army of people willing to carry branches longer than anyone is used to, for sure.17:12
beisnerso, nothing definitive, then?17:12
tinwoodi.e. it was up to the packagers if they want to do LTS releases.17:13
tinwoodyup17:13
beisnerso:  distros, distribute as you wish.17:13
*** TxGirlGeek has joined #openstack-meeting-417:13
beisnerok cool thanks17:13
tinwoodyes, basically.17:13
beisner#topic Open Discussion17:13
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:13
* beisner passes the mic17:13
tinwoodnothing from me.17:14
coreycbnothing here17:14
beisner#topic Next Chair17:14
*** openstack changes topic to "Next Chair (Meeting topic: charms)"17:14
beisnerthedac i believe you're up next17:14
thedacI win17:14
beisner\o/17:14
beisnerthanks, everyone!17:15
thedacThanks, beisner17:15
tinwoodthanks beisner17:15
tinwood:)17:15
beisner#endmeeting17:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:15
openstackMeeting ended Mon Mar 19 17:15:25 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:15
beisnercheers o/17:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-03-19-17.00.html17:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-03-19-17.00.txt17:15
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-03-19-17.00.log.html17:15
*** iyamahat has joined #openstack-meeting-417:17
*** zhubingbing has quit IRC17:19
*** d0ugal has quit IRC17:21
*** TxGirlGeek has quit IRC17:22
*** TxGirlGeek has joined #openstack-meeting-417:25
*** salmankhan has quit IRC17:27
*** TxGirlGeek has quit IRC17:28
*** salmankhan has joined #openstack-meeting-417:29
*** TxGirlGeek has joined #openstack-meeting-417:29
*** TxGirlGeek has quit IRC17:38
*** mjturek has quit IRC17:39
*** TxGirlGeek has joined #openstack-meeting-417:39
*** TxGirlGeek has quit IRC17:39
*** mjturek has joined #openstack-meeting-417:40
*** TxGirlGeek has joined #openstack-meeting-417:41
*** VW_ has joined #openstack-meeting-417:43
*** VW_ has quit IRC17:44
*** VW_ has joined #openstack-meeting-417:44
*** VW has quit IRC17:46
*** radeks has quit IRC17:50
*** TxGirlGeek has quit IRC17:54
*** TxGirlGeek has joined #openstack-meeting-417:55
*** lpetrut has quit IRC17:59
*** VW_ is now known as VW18:03
*** lpetrut has joined #openstack-meeting-418:06
*** iyamahat has quit IRC18:06
*** mjturek has quit IRC18:07
*** sambetts is now known as sambetts|afk18:12
*** TxGirlGeek has quit IRC18:13
*** diman has joined #openstack-meeting-418:15
*** TxGirlGeek has joined #openstack-meeting-418:16
*** diman has quit IRC18:19
*** iyamahat has joined #openstack-meeting-418:23
*** iyamahat has quit IRC18:24
*** iyamahat has joined #openstack-meeting-418:24
*** dave-mccowan has joined #openstack-meeting-418:28
*** iyamahat_ has joined #openstack-meeting-418:45
*** iyamahat has quit IRC18:45
*** anilvenkata has quit IRC18:45
*** radeks has joined #openstack-meeting-418:46
*** yamahata has joined #openstack-meeting-418:46
*** VW has quit IRC18:58
*** VW has joined #openstack-meeting-418:58
*** krtaylor has joined #openstack-meeting-418:59
*** VW has quit IRC19:00
*** VW has joined #openstack-meeting-419:00
*** VW has quit IRC19:01
*** VW has joined #openstack-meeting-419:02
*** zhubingbing has joined #openstack-meeting-419:16
*** zhubingbing has quit IRC19:20
*** radeks has quit IRC19:40
*** VW has quit IRC19:40
*** radeks has joined #openstack-meeting-419:41
*** yboaron_ has joined #openstack-meeting-419:57
*** VW has joined #openstack-meeting-420:00
*** iyamahat_ has quit IRC20:02
*** iyamahat has joined #openstack-meeting-420:03
*** radeks_ has joined #openstack-meeting-420:05
*** radeks has quit IRC20:08
*** salmankhan has quit IRC20:11
*** radeks_ has quit IRC20:13
*** julim_ has quit IRC20:16
*** julim has joined #openstack-meeting-420:16
*** Sukhdev_ has joined #openstack-meeting-420:25
*** yboaron_ has quit IRC20:30
*** iyamahat has quit IRC20:33
*** iyamahat has joined #openstack-meeting-420:33
*** VW has quit IRC20:34
*** lpetrut has quit IRC20:34
*** lpetrut has joined #openstack-meeting-420:34
*** VW has joined #openstack-meeting-420:35
*** VW has quit IRC20:35
*** VW has joined #openstack-meeting-420:35
*** TxGirlGeek has quit IRC20:35
*** julim has quit IRC20:36
*** TxGirlGeek has joined #openstack-meeting-420:39
*** TxGirlGeek has quit IRC20:43
*** TxGirlGeek has joined #openstack-meeting-420:54
*** TxGirlGeek has quit IRC20:56
*** zerick has quit IRC20:56
*** zerick has joined #openstack-meeting-420:56
*** TxGirlGeek has joined #openstack-meeting-421:07
*** TxGirlGeek has quit IRC21:09
*** TxGirlGeek has joined #openstack-meeting-421:12
*** gcheresh has quit IRC21:13
*** vyarma has joined #openstack-meeting-421:16
*** vyarma has quit IRC21:16
*** aniketh has quit IRC21:16
*** TxGirlGeek has quit IRC21:19
*** TxGirlGeek has joined #openstack-meeting-421:25
*** celebdor has quit IRC21:29
*** TxGirlGeek has quit IRC21:30
*** lpetrut has quit IRC21:34
*** celebdor has joined #openstack-meeting-421:44
*** celebdor has quit IRC21:50
*** Guest68461 has quit IRC21:54
*** TxGirlGeek has joined #openstack-meeting-421:59
*** TxGirlGeek has quit IRC22:04
*** celebdor has joined #openstack-meeting-422:06
*** TxGirlGeek has joined #openstack-meeting-422:08
*** zhubingbing has joined #openstack-meeting-422:11
*** zhubingbing has quit IRC22:15
*** VW has quit IRC22:15
*** VW has joined #openstack-meeting-422:16
*** VW_ has joined #openstack-meeting-422:18
*** bobh has quit IRC22:19
*** VW has quit IRC22:21
*** VW_ has quit IRC22:23
*** hongbin has quit IRC22:49
*** celebdor has quit IRC22:49
*** julim has joined #openstack-meeting-422:53
*** david-lyle has joined #openstack-meeting-423:01
*** seajay has quit IRC23:14
*** yamamoto has joined #openstack-meeting-423:27
*** chyka has quit IRC23:30
*** chyka has joined #openstack-meeting-423:31
*** Sukhdev_ has quit IRC23:44

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