Monday, 2018-01-08

*** slaweq has joined #openstack-meeting-400:11
*** slaweq has quit IRC00:15
*** d0ugal has quit IRC00:15
*** hippiepete has quit IRC00:22
*** d0ugal has joined #openstack-meeting-400:27
*** tuanla____ has joined #openstack-meeting-400:40
*** yujunz has joined #openstack-meeting-400:47
*** dave-mccowan has joined #openstack-meeting-401:06
*** seajay has joined #openstack-meeting-401:34
*** kiennt26 has joined #openstack-meeting-401:36
*** yujunz has quit IRC01:40
*** seajay has quit IRC01:40
*** seajay has joined #openstack-meeting-401:41
*** seajay has quit IRC01:48
*** yujunz has joined #openstack-meeting-401:55
*** hongbin has joined #openstack-meeting-402:03
*** VW has joined #openstack-meeting-402:46
*** zhurong has joined #openstack-meeting-402:46
*** VW has quit IRC02:46
*** VW has joined #openstack-meeting-402:47
*** hongbin has quit IRC03:09
*** dave-mccowan has quit IRC03:09
*** hongbin has joined #openstack-meeting-403:09
*** hongbin has quit IRC03:10
*** hongbin has joined #openstack-meeting-403:10
*** hongbin has quit IRC03:10
*** hongbin has joined #openstack-meeting-403:11
*** hongbin has quit IRC03:12
*** hongbin has joined #openstack-meeting-403:13
*** hongbin has quit IRC03:14
*** hongbin has joined #openstack-meeting-403:15
*** yamahata has joined #openstack-meeting-403:16
*** VW has quit IRC03:24
*** VW has joined #openstack-meeting-403:25
*** yamamoto has joined #openstack-meeting-403:58
*** janonymous has joined #openstack-meeting-404:01
*** yujunz has quit IRC04:02
*** yamamoto has quit IRC04:03
*** hongbin has quit IRC04:19
*** yujunz has joined #openstack-meeting-404:31
*** yujunz has quit IRC04:35
*** zhurong has quit IRC04:52
*** anilvenkata has joined #openstack-meeting-404:57
*** yamamoto has joined #openstack-meeting-405:04
*** yamamoto has quit IRC05:12
*** janki has joined #openstack-meeting-405:28
*** psachin has joined #openstack-meeting-405:33
*** shaohe_feng has quit IRC05:38
*** shaohe_feng has joined #openstack-meeting-405:42
*** yboaron has joined #openstack-meeting-405:47
*** zhurong has joined #openstack-meeting-405:52
*** arcolife has joined #openstack-meeting-405:57
*** junboli has joined #openstack-meeting-405:58
*** yujunz has joined #openstack-meeting-406:00
*** janki has quit IRC06:17
*** janki has joined #openstack-meeting-406:18
*** yamahata has quit IRC06:32
*** yujunz has quit IRC06:37
*** gcheresh_ has joined #openstack-meeting-406:38
*** yujunz has joined #openstack-meeting-406:38
*** coolsvap has joined #openstack-meeting-406:51
*** liuyulong has joined #openstack-meeting-406:54
*** reedip has quit IRC06:55
*** pcaruana has joined #openstack-meeting-407:04
*** reedip has joined #openstack-meeting-407:07
*** Kevin_Zheng has quit IRC07:13
*** Dmitrii-Sh has quit IRC07:13
*** chigang_ has quit IRC07:13
*** ChrisPriceAB has quit IRC07:13
*** mgkwill has quit IRC07:13
*** margaret has quit IRC07:13
*** diablo_rojo_phon has quit IRC07:13
*** mgkwill has joined #openstack-meeting-407:13
*** margaret has joined #openstack-meeting-407:13
*** chigang_ has joined #openstack-meeting-407:13
*** ChrisPriceAB has joined #openstack-meeting-407:14
*** diablo_rojo_phon has joined #openstack-meeting-407:14
*** Kevin_Zheng has joined #openstack-meeting-407:16
*** makowals has joined #openstack-meeting-407:36
*** karthiks has joined #openstack-meeting-407:36
*** arcolife has quit IRC07:42
*** VW has quit IRC07:51
*** lihi has joined #openstack-meeting-408:00
oanson#startmeeting Dragonflow08:00
openstackMeeting started Mon Jan  8 08:00:11 2018 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: Dragonflow)"08:00
openstackThe meeting name has been set to 'dragonflow'08:00
snapiriHi08:00
dimakGood morning08:00
lihiHi08:00
oansonirenab, are you in?08:01
oansonleyal-, are you in?08:01
irenabhi08:01
leyal-Hi08:01
oanson#info snapiri dimak lihi irenab leyal- in meeting08:01
oanson#topic Roadmap08:01
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"08:01
oansonLet's stick to the things there's progress:08:02
oansonDNS08:02
oansonthe spec is up and there's some discussion there08:02
oansonIs there something we need to raise here?08:02
*** yboaron has quit IRC08:02
oanson#link DNS spec https://review.openstack.org/#/c/527956/08:03
lihiI don't think there are major issues. irenab and snapiri asked I'll add the DB definition with more details08:04
*** yujunz has left #openstack-meeting-408:04
oansonDo you think it is doable by end of February?08:04
oansonlihi, ^^^ ?08:04
lihiYes08:05
oansonAll right. Then let's try to close the spec as soon as possible (say, this week)?08:05
lihiSure08:06
oansonCool!08:06
oansonUpgrades - there is some discussion on the spec08:06
oanson#link Upgrade spec https://review.openstack.org/#/c/500647/08:06
oansonThere are two options on the spec08:07
dimakZuul's unhappy ;)08:07
oansonI sent a recheck. I don't think it's me... :D08:07
irenabOf the spec?08:07
oansonyes08:07
oansonSo there are two options: two migration scripts, or a migration + online upgrade08:08
oansonOr two migration script, and then online upgrade.08:08
oansonI don't have a problem saying that upgrades that can't be done with migration scripts are not supported.08:08
irenaboanson, such as?08:09
oansonSince I *really* don't want online upgrades08:09
*** yujunz has joined #openstack-meeting-408:09
dimakVoted on spec08:09
oansonirenab, such as anything requiring IPAM08:09
irenaboanson, what is the case with IPAM?08:10
oansonBasically, everything we have today (including DHCP) can be done that way08:10
oansonirenab, none yet that I know of08:10
lihiWhy will it require IPAM?08:11
oansonIt won't08:11
oansonI think there's a mixup08:11
*** yujunz has left #openstack-meeting-408:11
oansoncurrently, all upgrades we need can be done with two migration scripts. We don't need e.g. IPAM or other such services.08:11
oansonIf ever we will need IPAM during upgrade, it won't be supported by our upgrade method.08:11
leyal-irenab. let assume that we will have a topology change that will require a new port , we will need to assign an ip to this port08:11
irenaboanson, so with 2 migration, dev will provide neutron and df scripts each to be invoked during neutron/df db migration process. Correct?08:12
snapirioanson: none of the terms you use here (upgrade / migration) is from Neutron DB, right?08:12
oansonirenab, yes08:13
*** anilvenkata has quit IRC08:13
*** anilvenkata has joined #openstack-meeting-408:13
oansonsnapiri, 'alembic migration' is the Neutron upgrade process08:13
oansons/Neutron/Neutron DB/08:13
irenableyal-, I think that use case you raised is more than just DB upgrade08:13
irenabI think maybe case like this should be handled as exceptions08:14
lihileyal-, if the neutron server is down (option 1), can we even have topology changes?08:15
irenabprobably involving dedicated upgrade procedure08:15
irenaboanson, what about changing subnet to become core df model entity?08:16
oansonirenab, what about it?08:16
oansonThe upgrade code is here: https://review.openstack.org/#/c/52771708:17
leyal-lihi , yes , i talked about topology changes that caused by the upgrade , like virtual ports for apps ..08:17
oansonleyal-, I think this is the part that will need specialised changes anyway.08:17
irenaboanson, so it Noop for neutron and the script in the change for df?08:17
oansonI think lihi also meant that you can't do that in a Neutron-only upgrade (i.e. Neutron doesn't support that feature)08:18
oansonirenab, yes08:18
oansonThe only upgrade script we have that needs Neutron DB changes is DHCP08:18
*** pabelanger has quit IRC08:19
oanson#link DHCP upgrade https://review.openstack.org/#/c/52771608:19
*** trozet has quit IRC08:19
oansonI added the relevant comment08:19
irenaboanson, leyal- so looks like DHCP/Topology change can be resolved by 2 scripts08:20
*** pabelanger has joined #openstack-meeting-408:20
oansonirenab, yes08:20
oansonleyal-, are you convinced?08:20
leyal-I think that the  currently dhcp app is to only app that use neutron for creating new object..08:20
*** trozet has joined #openstack-meeting-408:20
oansonleyal-, yes. But even that is solvable with offline scripts08:21
leyal-oanson, i will go with majority decision :)08:22
oansonAll right. So do we have consensus on option 1: Two offline scripts?08:22
oansonSpeak now or forever hold your pieces08:22
irenab+108:22
lihi+108:22
dimakaye08:23
snapiriyes08:23
oansonHooray!08:23
oansonI'll update the spec today and start cracking08:23
oansonAnything else for roadmap?08:23
leyal-yep08:24
oansonleyal-, shoot!08:24
leyal-still working on the comment's on the kuryr df drivers . hope that i will came with primitive IPAM patch -  today or tommarow ..08:25
oanson#link Kuryr-Dragonflow patch https://review.openstack.org/#/c/529971/08:25
oansonCool08:25
oansonAnything else for roadmap?08:26
oanson#topic Bugs08:27
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"08:27
oansonSo08:27
oansonThe end of the cycle is coming fast08:27
irenaboanson, date?08:27
oansonAnd I think now would be a good time to start tackling bugs08:27
oansonEnd of February, if I recall.08:27
oanson28th of February08:28
oansonSo that gives us almost two months to tackle bugs, and we have quite a few08:28
snapiriThere is the biggie with the SG...08:28
oansonYes. We'll get to that in a minute08:29
oansonBasically, so we don't step on each other's toes, if you start looking at a bug, assign it to yourself.08:29
oansonDon't feel bad about unassigning it later if you feel it's boring08:29
*** kevzha01 has joined #openstack-meeting-408:30
*** kevzha01 is now known as kevinz08:30
oansonWe have 14 High bugs. I think we can manage it. Except the ZMQ active-port bug, which I want to demote.08:30
oanson(Unless there are objections?)08:30
irenablink?08:30
oansonI speak of https://bugs.launchpad.net/dragonflow/+bug/171693308:30
openstackLaunchpad bug 1716933 in DragonFlow "ZMQ and Active Port Detection app try to bind to the same port" [High,New]08:30
snapirioanson: is this the one failing the devstack?08:31
oansonBasically it is the entire issue we're having with the 'multiproc' direction. I think the correct solution is to move to broker-only pub/sub.08:31
oansonsnapiri, No. We disabled these tests08:31
snapirioanson: I meant is this the one I encountered when I tried to deploy devstack on my VM...08:32
oansonYes08:32
oansonYes it is.08:32
snapiriAny solution to that would be appreciated as it is super annoying08:33
oansonThere was a lot of research done here and many ideas already thrown around. But I think it is a. not so important due to the etcd pub/sub mechanism, and b. a lot of work, so I think it can wait for R cycle08:33
oansonsnapiri, yes: Use the etcd pub/sub and not ZMQ08:33
oansonOr use redis08:33
oansonNow for the really interesting bug:08:34
irenaboanson, about this baug08:34
oanson#link Security groups + FIP bug https://bugs.launchpad.net/dragonflow/+bug/174073908:34
openstackLaunchpad bug 1740739 in DragonFlow "Security group mismatch for floating IP" [High,New]08:34
oansonirenab, yes?08:34
irenabCan you please update in the bug about the etc/redis alternatives and and reason why reducing the priority or making this non issue08:35
oansonSure. Will do08:35
oansonirenab, Done08:36
oansonRe bug 174073908:36
openstackbug 1740739 in DragonFlow "Security group mismatch for floating IP" [High,New] https://launchpad.net/bugs/174073908:36
oansonBasically, the issue is that today security groups takes the private IP of the VMs when building the OpenFlow rules.08:37
oansonEven for Security Group based rules (i.e. saying 'allow for ports in Security Group B')08:37
oansonThis breaks when using FIP, since the packet arrives with the floating IP (external) and not the VM's IP08:38
oansonThere's a proposed solution on the bug08:38
oansonAnd I'm reading the code to understand how Neutron does it.08:38
oansonI should be able to update the bug with that as well by EOW08:38
oansonAnything else for this bug?08:39
oansonAnything else for bugs, in general?08:39
oanson#topic Open Discussion08:40
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"08:40
oansonThe floor is for the taking08:40
oansonLAst chance?08:41
oansonLast*08:41
oansonCool.08:41
oansonThanks everyone for coming.08:42
snapiricheers08:42
oanson#endmeeting08:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:42
openstackMeeting ended Mon Jan  8 08:42:29 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2018/dragonflow.2018-01-08-08.00.html08:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2018/dragonflow.2018-01-08-08.00.txt08:42
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2018/dragonflow.2018-01-08-08.00.log.html08:42
*** gibi_away is now known as gibi08:44
*** yboaron has joined #openstack-meeting-408:57
*** yujunz has joined #openstack-meeting-409:03
*** sbezverk has quit IRC09:11
*** Dmitrii-Sh has joined #openstack-meeting-409:11
*** arcolife has joined #openstack-meeting-409:13
*** finucannot is now known as stephenfin09:16
*** TuanVu has joined #openstack-meeting-409:26
*** yujunz has quit IRC09:30
*** junboli has quit IRC09:33
*** salmankhan has joined #openstack-meeting-410:01
*** zhurong has quit IRC10:02
*** kiennt26 has quit IRC10:07
*** tinwood_ is now known as tinwood10:10
*** pbourke has quit IRC10:12
*** pbourke has joined #openstack-meeting-410:12
*** TuanVu has quit IRC10:26
*** sambetts|afk is now known as sambetts10:50
*** jamespage has quit IRC10:51
*** wolsen has quit IRC10:51
*** wolsen has joined #openstack-meeting-410:52
*** jamespage has joined #openstack-meeting-410:52
*** numans has quit IRC11:06
*** numans has joined #openstack-meeting-411:08
*** zhurong has joined #openstack-meeting-411:35
*** tuanla____ has quit IRC11:46
*** anilvenkata has quit IRC11:50
*** seajay has joined #openstack-meeting-411:53
*** seajay has quit IRC11:56
*** seajay has joined #openstack-meeting-411:56
*** sdague has joined #openstack-meeting-412:00
*** dave-mccowan has joined #openstack-meeting-412:09
*** liuyulong has quit IRC12:24
*** janki has quit IRC12:24
*** julim_ has quit IRC12:37
*** julim has joined #openstack-meeting-412:38
*** julim has quit IRC12:42
*** dave-mccowan has quit IRC12:47
*** dave-mccowan has joined #openstack-meeting-412:49
*** zhurong has quit IRC13:01
*** hieulq has quit IRC13:04
*** hieulq has joined #openstack-meeting-413:05
*** iurygregory has quit IRC13:20
*** janonymous has quit IRC13:22
*** anilvenkata has joined #openstack-meeting-413:24
*** pcaruana has quit IRC13:25
*** pcaruana has joined #openstack-meeting-413:25
*** cleong has joined #openstack-meeting-413:28
*** yamamoto has joined #openstack-meeting-413:28
*** coolsvap has quit IRC13:36
*** woodard has quit IRC13:36
*** woodard has joined #openstack-meeting-413:36
*** juriarte1 has joined #openstack-meeting-413:52
*** kiennt26 has joined #openstack-meeting-413:53
*** salmankhan1 has joined #openstack-meeting-413:55
*** yamamoto has quit IRC13:56
*** yamamoto has joined #openstack-meeting-413:57
*** salmankhan has quit IRC13:59
*** salmankhan1 is now known as salmankhan13:59
irenabstartmeeting #kuryr14:00
irenab#startmeeting kuryr14:01
openstackMeeting started Mon Jan  8 14:01:25 2018 UTC and is due to finish in 60 minutes.  The chair is irenab. Information about MeetBot at http://wiki.debian.org/MeetBot.14: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
*** bhagyashris has joined #openstack-meeting-414:01
irenabhi, who is here for kuryr weekly?14:01
*** yamamoto has quit IRC14:01
yboaron+114:02
*** bhagyashris has left #openstack-meeting-414:02
ltomasbohi!14:02
duleko/14:02
*** woodard has quit IRC14:02
irenab#chair ltomasbo14:03
openstackCurrent chairs: irenab ltomasbo14:03
irenabltomasbo, added you since I will have to leave in about 20 mins14:03
irenablets start with kuryr-kubernetes?14:03
*** apuimedo has joined #openstack-meeting-414:03
apuimedoyes14:03
irenab#chair apuimedo14:03
openstackCurrent chairs: apuimedo irenab ltomasbo14:03
ltomasbook14:03
irenab#topic kuryr-kubernetes14:04
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:04
apuimedo#info an important fix for kubelet retries has been merged 21060314:04
apuimedodamn, wrong number14:04
apuimedo#link https://review.openstack.org/51840414:04
apuimedo#info The new readiness check server has been marked for merging too14:05
irenabapuimedo, question on that one14:05
dulekI'm not sure if 518404 it's so important, but it helps a bit with failures. :)14:05
*** maysamacedos has joined #openstack-meeting-414:06
irenabRegarding readiness check, I suggest to make the probe loadable via stevedore to keep the kuryr infra as generic as it used to be14:06
apuimedodulek: it helps prevent an very frustrating issue14:06
irenabCan be done as a follow up, just wanted to check if agreed14:06
apuimedomakes it important for ux14:07
irenabdulek, link?14:07
apuimedoirenab: you meant the stevedorization?14:07
irenabapuimedo, yes :-)14:07
dulekirenab: I've meant https://review.openstack.org/518404 - the retries fix.14:07
apuimedomaysamacedos is here too now14:07
irenabdulek, important fix14:07
apuimedoirenab: well, I do think that kuryr-kubernetes should be able to have methods that are used for readiness and health checks14:08
apuimedoso that when they are instantiated they get registered with the readiness/health check servers14:08
irenabI kind like the way we had kuryr as generic integration framework, so it could be used to have non neutron drivers14:09
apuimedoirenab: dulek: granted it only affected baremetal14:09
irenabapuimedo, no argument on your point14:09
apuimedoso that makes it slightly less damning14:09
irenabI just think that it should not be explicetly hard coded in the kuryr server code, but loadable based on deployment option14:09
apuimedoirenab: currently maysamacedos and I were about to discuss about the approach for the liveness checks14:09
apuimedoI suggested having the liveness check server hold references to the handler threads for checks14:10
apuimedobut it would probably be better that the references are used to ask the handler instances themselves14:10
irenabapuimedo, not sure I follow14:11
apuimedosince it could happen that the thread is alive14:11
apuimedobut the handler is in a bad state14:11
apuimedoirenab: we want to add liveness checks that monitor the health of the vif/service/etc handlers as well14:11
dulekapuimedo: You mean the watcher threads?14:12
apuimedodulek: yes, the different threads on which the handlers run14:12
irenabapuimedo, important to have that too. My point is that we need to have this not explicit, but based on the drivers used in the deployment to keep the current pluggability14:12
dulekapuimedo: I'm not sure if it's worth it, I think Watcher threads has protection from unexpected exceptions.14:13
apuimedowhat I'm saying is that probably we should have protocols for instances to register to the readiness/liveness check servers14:13
apuimedothat can be implemented by any instance14:13
*** lyan has joined #openstack-meeting-414:13
dulekapuimedo: Ah, that might be better.14:13
*** julim has joined #openstack-meeting-414:13
apuimedoirenab: yes, but maybe we don't need stevedore for that14:13
apuimedostevedore handles loading of the instances14:13
apuimedothat part we already have14:13
apuimedoI'm just saying that as part of the loading14:13
irenabapuimedo, not for the readiness probe14:13
apuimedothat currently exists14:13
apuimedothey could register with readiness/liveness depending on which of those two protocols they implement14:14
apuimedodulek: irenab: maysamacedos: how does that sound?14:14
irenabline 53 is bothering me https://review.openstack.org/#/c/529335/17/kuryr_kubernetes/controller/service.py14:14
apuimedoirenab: why?14:15
apuimedoI think we always want a readiness check server14:15
apuimedowhat should be different14:15
irenabexplicit call to the brobe that checks for neutron and keystone. What if kuryr is used for non neutron drivers?14:15
apuimedois that only checks for components that have been plugged should be performed in it14:15
apuimedoirenab: that's what I'm saying14:16
apuimedo:-)14:16
apuimedoyou want the readiness checker running14:16
irenabWe started to play with adding DF native drivers to kuryr14:16
apuimedothe currently not ideal thing14:16
irenabso we will check for DF readiness and not neutron14:16
apuimedois that now it is a module that just performs always the same checks14:16
apuimedowhat I want is that the neutron vif handler14:16
maysamacedosapuimedo: not sure I get it what you meant with "protocols for instances to register to the readiness/liveness"14:16
apuimedoregisters its checking method14:16
apuimedowhich checks neutron14:17
apuimedothe neutron service handler14:17
irenabapuimedo, sounds reasonable if I got it correctly14:17
apuimedowill check lbaasv2 or octavia14:17
dulekI'm +1 on that.14:17
apuimedobut we do want a single health checker server in the controller14:17
irenabapuimedo, agreed, but this will invoke routines of enabled Handlers/drivers14:18
apuimedonot necessarily14:18
apuimedothey may be external to the instances in some cases14:18
irenabso how this will be extendable?14:18
apuimedothe instance sets what it needs14:19
irenabapuimedo, instance of what?14:19
dulekHandler?14:19
apuimedohandlers and drivers14:19
dulekMore like driver. :)14:19
apuimedoI think both could need specific checks14:19
apuimedohandlers need checks for liveness mostly14:19
apuimedoin our neutron case14:20
apuimedothey may need more for DF if they want to check redis for example, I don't know14:20
irenabWe can have sort of dedicated hierarchy for the probes14:20
apuimedoirenab: what I want to avoid for sure is to have repeated probes14:21
irenabprobe routines14:21
apuimedoso if two drivers need the same Neutron support (not different exts), I only want one check14:21
irenabto be performed by single health server14:21
apuimedoexactly14:21
apuimedobut that is a bit of fine tuning14:22
irenabroutines can be added and for deployment just 'checked' to be invoked14:22
apuimedoand if in the beginning there is multiple neutron extension checks, clocking that at 22ms per check is not too terrible14:22
irenabso checking same one several times will end up calling this routine once14:23
apuimedoirenab: that will be the ideal14:23
apuimedobut we don't need to get there in a single patch14:23
irenabas long as we agree on the longer term generic approach, I am fine with merging the current patch14:24
apuimedomaysamacedos: what do you think of this approach?14:24
apuimedotaking the checks to their respective handler/drivers?14:24
irenabapuimedo, may I interrupt with short update on net policies on behalf of leyal- ? I have to leave in a few mins?14:25
apuimedoirenab: irenab14:26
apuimedosure!14:26
maysamacedosapuimedo: Isn't that kind what I suggested in the email?14:26
irenabThe spec is up for review https://review.openstack.org/#/c/519239/14:26
irenabThere are 2 patches WIP mainly for missing unit tests14:26
irenabhttps://review.openstack.org/#/c/530655/14:27
apuimedomaysamacedos: in the email about the references to the task?14:27
irenabhttps://review.openstack.org/#/c/526916/14:27
maysamacedosapuimedo: eys14:27
maysamacedosyes14:27
*** makowals has quit IRC14:27
apuimedomaysamacedos: what we're saying is to move the check code out of the server14:27
irenabPlease review and comment, the most important is the spec patch to agree on direction of the implementation14:27
apuimedoso each module/class can contribute its own readiness and liveness code14:28
apuimedoand the readiness/health check servers just load id14:28
maysamacedoshmm I see14:28
irenabapuimedo, all, please review the Net policies spec14:28
apuimedo(not the k8s readiness check)14:28
apuimedoirenab: will do14:28
irenabthanks! /me sorry, have to leave14:28
apuimedoirenab: have you tried straight to DF policy translation?14:28
*** makowals has joined #openstack-meeting-414:29
irenabapuimedo, no, not yet14:29
irenabfirst with translation to neutron SGs14:29
apuimedoirenab: and for port operations, how much faster is it, bypassing neutron14:29
apuimedo?14:30
apuimedoltomasbo: are you here?14:30
ltomasboI am14:30
irenabapuimedo, have to measure, the patch is here but it is very WIP: https://review.openstack.org/#/c/529971/14:30
apuimedohow's the node depending vif driver?14:30
apuimedoirenab: cool!14:31
apuimedottyl then!14:31
ltomasboapuimedo, you mean this: https://review.openstack.org/#/c/528345?14:31
dulekapuimedo: You mean stuff I'm working on?14:31
*** VW has joined #openstack-meeting-414:31
ltomasbothe multi-pool multi-vif thing?14:32
maysamacedosapuimedo: what you meant with the checks servers load the id?14:33
dulekapuimedo's just sitting there wondering what we'll figure out from his cryptic message. :D14:36
apuimedoltomasbo: right14:36
apuimedothat14:37
apuimedomaysamacedos: id?14:37
ltomasboso, I tested it and it was working (before Christmas)14:37
apuimedodulek: apuimedo was taking the baby outside of the room :P14:37
ltomasbobut I would like to check it at a real mix environment14:37
apuimedosorry14:37
apuimedo:-)14:37
apuimedoltomasbo: ok14:37
ltomasboas I just checked from one or the other environment, with the multi driver14:37
apuimedomaysamacedos: not sure about "the id" part14:38
apuimedoa typo maybe14:38
ltomasbodetecting the pool driver to use from the node vif label14:38
maysamacedosapuimedo: thats what you said "the readiness/health check servers just load id "14:38
apuimedoltomasbo: with multi node devstack it should be doable14:38
ltomasboI'm deploying the devstack with kubelet in one port to test14:38
maysamacedosprobably a typo14:38
apuimedomaysamacedos: typo then14:38
apuimedomean "just load it"14:38
ltomasboapuimedo, yes, but our current local.conf are kind of broken14:38
*** makowals has quit IRC14:39
apuimedoltomasbo: that's interesting14:39
ltomasboI got a problem with the etcd running on a nested configuration14:39
apuimedohow?14:39
apuimedomaysamacedos: so I meant that when we load the drivers/handlers, they can contain methods for the health check servers14:39
ltomasbobecasue devstack now forces etcd to be installed on the server_host, instead of on the local one14:39
apuimedoand for the readiness one too14:39
ltomasboand I needed local to be nested14:39
*** makowals has joined #openstack-meeting-414:39
apuimedowhy?14:40
ltomasboand I just created the port on the pods network and deploying on baremetal on the remove server14:40
ltomasboapuimedo: https://github.com/openstack-dev/devstack/commit/146332e349416ac0b3c9653b0ae68d55dbb3f9de14:40
*** apuimedo has quit IRC14:40
*** apuimedo has joined #openstack-meeting-414:42
ltomasboapuimedo: https://github.com/openstack-dev/devstack/commit/146332e349416ac0b3c9653b0ae68d55dbb3f9de14:42
*** yamamoto has joined #openstack-meeting-414:42
ltomasboand it also fails on the remove baremetal devstack node, I'm going to check what the problem is there14:42
apuimedoltomasbo: crap14:43
ltomasboumm 2018-01-08 14:41:43.053 | ++ /opt/stack/kuryr-kubernetes/devstack/plugin.sh:extract_hyperkube:497 :   docker cp :/hyperkube /tmp/hyperkube14:43
ltomasbo2018-01-08 14:41:43.069 | must specify at least one container source14:43
apuimedook, that's a bug14:43
apuimedo:-)14:43
apuimedowe should have our local.conf put :: then14:43
apuimedoor just '0'14:43
maysamacedosapuimedo: got it14:44
apuimedomaysamacedos: ;-)14:44
ltomasboapuimedo, but still the neutron services are on the Service_host14:44
ltomasboso, we also need that14:44
*** psachin has quit IRC14:45
apuimedoltomasbo: I'm not sure I follow14:46
apuimedodevstack with everything (including etcd) and another with just the kubelet running on a nova VM14:46
ltomasboapuimedo, are you suggesting our local.conf just set server_host to :::14:46
apuimedoone uses veth, the other pod in VM14:47
ltomasboahh, ok, now I got what you meant14:47
*** yamamoto has quit IRC14:47
apuimedoltomasbo: on the devstack with everything the server host would be 0.0.0.0:237914:47
ltomasbothe other way around I was doing...14:47
apuimedofor etcd14:47
maysamacedosapuimedo: but what this methods would check then? since they are in each module they could not verify the thread state neither if an exception occured.. or they could?14:47
apuimedomaysamacedos: would not be called on the instance14:48
apuimedowhat you wrote on the email14:48
apuimedobut outside of the liveness monitor14:48
apuimedoprobably on the watcher instance14:49
apuimedoltomasbo: anything else?14:49
apuimedoor did I miss something?14:49
ltomasboapuimedo, that's it from my side14:49
apuimedogood!14:50
dulekOkay, so maybe a quick update from me?14:50
apuimedodulek: please!14:50
dulekSimple one: https://review.openstack.org/#/c/531128/14:50
dulekI've tried K8s 1.9 on the gate, everything looks fine.14:50
dulekI don't know what policy we have on updating it. And I don't have a strong opinion on that.14:50
apuimedothe policy is, if it ain't failing, upgrade14:51
dulekBut in any case once we decide to move forward we should be fine with that.14:51
apuimedoso that we know that the queens release works well with 1.914:52
dulekI wonder if we want to gate on older versions as well?14:52
dulekDo we have support matrix or sth like that?14:52
dulekI guess it's something we need to discuss with irenab as well.14:54
apuimedodulek: indeed14:54
apuimedolet's discuss it tomorrow morning when irenab and dmellado will also be able to weigh in14:54
dulekSecond thing is I've updated https://review.openstack.org/#/c/527243 with apuimedo's remarks.14:54
dulekNow pooled VIFs are attached to a dummy namespace when discovered and on CNI ADD they're only replugged (at least I think they are).14:55
apuimedodulek: for baremetal or for all?14:55
dulekapuimedo: Good question, only bare metal for now, I've left nested in TODO for now.14:55
apuimedogood!14:56
dulekI'm trying to time BM case now to see if there's a benefit from that in a single-node case.14:56
apuimedo:-)14:56
*** yamahata has joined #openstack-meeting-414:56
apuimedodulek: with port pooling I would seriously hope there's a big improvement14:56
dulekFirst results show a tiny performance improvement, but I'm trying now with higher number of ports.14:56
apuimedosince there's only a veth change of NS14:56
apuimedoinstead of activation + netlink creation + move14:57
apuimedodulek: first create 50 ports14:57
apuimedowait until the dummy namespace is full14:57
apuimedothen create the pods14:57
dulekapuimedo: That's how I'm trying to test it.14:57
apuimedothat's the scenario14:57
apuimedook14:57
dulekapuimedo: Please take a look at binding code then. I may do too much stuff on the reattachment side.14:57
apuimedodulek: will do!14:57
dulekapuimedo: An advice there would help. :)14:58
apuimedoanything else anybody?14:58
dulekOkay, that's it!14:58
yboaronI Can update from my side14:58
apuimedoyboaron: please do!14:58
yboaronPlease ,Review https://review.openstack.org/#/c/529966/14:58
apuimedooh fuck14:58
yboaronThe devref to support Ingress controller , the OCP-route support will be based on this common part14:58
yboaron(L7 routers)14:58
yboaronapuimedo, fuck the ingres-controller ???14:58
apuimedoI wanted to spend some time discussing your proposal for separate router/ingress controller component14:58
apuimedobut irenab and dmellado left already14:59
*** arcolife has quit IRC14:59
apuimedolet's discuss that tomorrow morning, please14:59
yboaronI almost finished splitting the patch into 3 pieces , but there's an open issue if we need to have a seperate controller for that purpose,14:59
yboaronsomething similiar to NGINX/GCE ingress controller,14:59
yboaronor just extend kuryr-controller to support ingress and OCP-Route14:59
apuimedoyboaron: I'll review the patch ;-)14:59
yboaronapuimedo, so maybe we can do  it tomorrow on kuryr channel14:59
apuimedodulek: take a look at it too14:59
apuimedoyboaron: we'll have to14:59
apuimedo:-)14:59
apuimedothere's not enough people now to discuss15:00
apuimedoand the time just ran out15:00
apuimedoTHanks all for joining15:00
apuimedo!15:00
apuimedo#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Mon Jan  8 15:00:20 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-01-08-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-01-08-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-01-08-14.01.log.html15:00
*** hongbin has joined #openstack-meeting-415:01
*** Guest8485 is now known as dansmith15:02
*** dansmith is now known as Guest6250115:02
*** sdague has quit IRC15:04
*** Guest62501 is now known as dansmith15:05
*** maysamacedos has quit IRC15:07
*** maysamacedos has joined #openstack-meeting-415:08
*** sbezverk has joined #openstack-meeting-415:09
*** juriarte1 has left #openstack-meeting-415:10
*** VW has quit IRC15:10
*** SerenaFeng has joined #openstack-meeting-415:10
*** VW has joined #openstack-meeting-415:10
*** makowals has quit IRC15:22
*** makowals has joined #openstack-meeting-415:23
*** woodard has joined #openstack-meeting-415:26
*** yamamoto has joined #openstack-meeting-415:27
*** yamamoto has quit IRC15:32
*** makowals has quit IRC15:40
*** bobh has joined #openstack-meeting-415:42
*** maysamacedos has quit IRC15:43
*** woodard has quit IRC15:43
*** woodard has joined #openstack-meeting-415:44
*** ram5391 has joined #openstack-meeting-415:52
*** yamamoto has joined #openstack-meeting-415:53
*** yamamoto has quit IRC15:53
*** kiennt26 has quit IRC15:54
*** gcheresh_ has quit IRC15:55
*** TxGirlGeek has joined #openstack-meeting-415:59
*** SerenaFeng has quit IRC16:03
*** chyka has joined #openstack-meeting-416:05
*** yboaron_ has joined #openstack-meeting-416:05
*** yboaron has quit IRC16:08
*** anilvenkata has quit IRC16:19
*** anilvenkata has joined #openstack-meeting-416:21
*** yboaron_ has quit IRC16:25
*** krtaylor has quit IRC16:27
*** krtaylor_ has joined #openstack-meeting-416:27
*** yfauser has joined #openstack-meeting-416:30
*** yfauser has quit IRC16:31
*** d0ugal has quit IRC16:35
*** maysamacedos has joined #openstack-meeting-416:44
*** maysamacedos has quit IRC16:45
*** arcolife has joined #openstack-meeting-416:47
*** david-lyle has quit IRC16:47
*** david-lyle has joined #openstack-meeting-416:48
*** pcaruana has quit IRC16:48
*** yamahata has quit IRC16:48
*** ram5391 has quit IRC16:52
*** david-lyle has quit IRC16:52
*** yamamoto has joined #openstack-meeting-416:53
*** ram5391 has joined #openstack-meeting-416:56
*** d0ugal has joined #openstack-meeting-416:59
coreycb#startmeeting charms17:00
openstackMeeting started Mon Jan  8 17:00:13 2018 UTC and is due to finish in 60 minutes.  The chair is coreycb. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
coreycbo/ hi all17:00
*** openstack changes topic to " (Meeting topic: charms)"17:00
openstackThe meeting name has been set to 'charms'17:00
thedaco/17:00
tinwoodo/ corey17:00
coreycb#topic Review ACTION points from previous meeting17:00
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:00
*** slaweq has joined #openstack-meeting-417:00
coreycbwe have 2 action items in the minutes from our last meeting17:01
coreycb1) all - fix critical and high priority bugs17:01
*** iyamahat has joined #openstack-meeting-417:01
coreycb2) jamespage - update the release policy again - ongoing.17:01
coreycbi'll keep those there unless there are any objects or updates17:02
thedacCriticals are all fix committed. There are 56 open high bugs17:02
thedac+1 to keeping17:02
coreycb\o/17:02
*** yamamoto has quit IRC17:02
coreycb#action - fix critical and high priority bugs - 56 open high - currently all critical are fix committed!17:03
coreycb#action all fix critical and high priority bugs - 56 open high - currently all critical are fix committed!17:03
*** arcolife has quit IRC17:03
coreycb#action jamespage update the release policy again - ongoing17:03
coreycb#topic State of Development for next Charm Release17:04
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:04
coreycbwhat's new with dev?17:04
thedacIn the middle of the 18.02 cycle.17:05
tinwoodStill doing py3 charm conversions17:05
thedacCurently gnouy is writing the spec for cells v217:05
thedacDesignate - neutron integration is committed. Still needs a blog post from me to explain how to use it.17:05
thedaccoreycb: that can be an action item ^^17:06
tinwood\o/17:06
coreycb#action thedac designate neutron integration blog post on how to use17:06
coreycbthanks. and i know james had some queens updates to the charms for milestone 2 that i think have landed.17:06
*** maysamacedos has joined #openstack-meeting-417:07
coreycb#topic High Priority Bugs17:07
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:07
coreycb#link  https://bugs.launchpad.net/openstack-charms/+bugs17:07
coreycbcritical: 0, high: 56, new: 1617:08
coreycbwell, still a lot of highs to dig into. would be nice to get those numbers down.17:09
tinwoodindeed.17:09
thedac+117:09
coreycb#link http://tinyurl.com/charm-stable-backports17:09
*** maysamacedos has left #openstack-meeting-417:10
coreycb#link https://tinyurl.com/osc-critical-bugs17:10
coreycb#link https://tinyurl.com/osc-high-priority17:10
*** TxGirlGeek has quit IRC17:11
coreycbquick links there for bugs ^^17:11
coreycb#topic Openstack Events17:11
*** slaweq has quit IRC17:11
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:11
thedacPTG in February https://www.openstack.org/ptg/17:11
coreycbthedac: great, thanks17:11
*** woodard has quit IRC17:11
*** d0ugal has quit IRC17:11
*** woodard has joined #openstack-meeting-417:12
coreycband end of May for openstack summit in vancouver17:12
tinwoodVancouver's nice.17:12
coreycbsure is, and so is Spring!17:13
tinwood:)17:13
coreycb#topic Open Discussion17:13
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:13
coreycbanything to bring up here?17:13
thedacI am good17:13
coreycbthedac: is osci off for the spectre/meltdown issues?17:14
thedacYes it is. Once we have kernel and qemu updates we will restore functionality17:14
coreycbthedac: ok great17:14
coreycbalright if there's nothing else then let's get back at it17:15
tinwoodnot from me17:16
coreycb#topic Next Chair17:16
*** openstack changes topic to "Next Chair (Meeting topic: charms)"17:16
coreycbjamespage17:16
coreycbbye all, thanks for attending17:16
coreycb#endmeeting17:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:16
openstackMeeting ended Mon Jan  8 17:16:49 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-01-08-17.00.html17:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-01-08-17.00.txt17:16
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-01-08-17.00.log.html17:16
thedacThanks, coreycb17:16
*** TxGirlGeek has joined #openstack-meeting-417:17
tinwoodthanks coreycb17:17
*** woodard has quit IRC17:18
*** woodard has joined #openstack-meeting-417:19
*** yamahata has joined #openstack-meeting-417:20
*** ram5391 has quit IRC17:27
*** david-lyle has joined #openstack-meeting-417:34
*** yamamoto has joined #openstack-meeting-417:43
*** yamamoto has quit IRC17:43
*** david-lyle has quit IRC17:47
*** ram5391 has joined #openstack-meeting-417:51
*** ram5391 has quit IRC17:53
*** gnuoy has joined #openstack-meeting-418:00
*** slaweq has joined #openstack-meeting-418:05
*** salmankhan has quit IRC18:16
*** slaweq has quit IRC18:17
*** slaweq has joined #openstack-meeting-418:21
*** emagana has joined #openstack-meeting-418:21
*** slaweq has quit IRC18:31
*** slaweq has joined #openstack-meeting-418:34
*** beekneemech is now known as bnemec18:34
*** corey_ has joined #openstack-meeting-418:39
*** cleong has quit IRC18:40
*** yamamoto has joined #openstack-meeting-418:44
*** yamamoto has quit IRC18:52
*** TxGirlGeek has quit IRC18:55
*** TxGirlGeek has joined #openstack-meeting-418:59
*** slaweq has quit IRC19:01
*** yamamoto has joined #openstack-meeting-419:01
*** slaweq has joined #openstack-meeting-419:02
*** TxGirlGeek has quit IRC19:04
*** slaweq has quit IRC19:06
*** slaweq has joined #openstack-meeting-419:09
*** harlowja has joined #openstack-meeting-419:19
*** slaweq has quit IRC19:19
*** TxGirlGeek has joined #openstack-meeting-419:21
*** slaweq has joined #openstack-meeting-419:28
*** salmankhan has joined #openstack-meeting-419:37
*** salmankhan has quit IRC19:41
*** david-lyle has joined #openstack-meeting-419:43
*** yamamoto has quit IRC19:53
*** sdague has joined #openstack-meeting-420:00
*** VW_ has joined #openstack-meeting-420:01
*** VW__ has joined #openstack-meeting-420:03
*** VW_ has quit IRC20:03
*** yamamoto has joined #openstack-meeting-420:04
*** VW has quit IRC20:05
*** snapiri1 has joined #openstack-meeting-420:07
*** snapiri1 has quit IRC20:08
*** yamamoto has quit IRC20:09
*** openstack has quit IRC20:38
*** openstack has joined #openstack-meeting-420:39
*** ChanServ sets mode: +o openstack20:39
*** TxGirlGeek has quit IRC20:45
*** TxGirlGeek has joined #openstack-meeting-420:56
*** woodard_ has joined #openstack-meeting-420:57
*** woodard has quit IRC20:57
*** VW__ has quit IRC21:01
*** VW has joined #openstack-meeting-421:02
*** VW has quit IRC21:06
*** VW_ has joined #openstack-meeting-421:06
*** MeganR has joined #openstack-meeting-421:11
*** corey_ has quit IRC21:25
*** woodard_ has quit IRC21:25
*** woodard has joined #openstack-meeting-421:26
*** julim has quit IRC21:27
*** david-lyle has quit IRC21:28
*** yamamoto has joined #openstack-meeting-421:39
*** yamamoto has quit IRC21:47
*** MeganR has quit IRC21:49
*** slaweq has quit IRC21:50
*** TxGirlGeek has quit IRC21:50
*** TxGirlGeek has joined #openstack-meeting-421:59
*** TxGirlGeek has quit IRC21:59
*** TxGirlGeek has joined #openstack-meeting-422:14
*** woodard has quit IRC22:24
*** emagana has quit IRC22:30
*** emagana has joined #openstack-meeting-422:31
*** emagana has quit IRC22:32
*** dave-mccowan has quit IRC22:37
*** emagana has joined #openstack-meeting-422:38
*** emagana has quit IRC22:39
*** lyan has quit IRC22:40
*** TxGirlGeek has quit IRC22:41
*** hongbin has quit IRC22:45
*** TxGirlGeek has joined #openstack-meeting-422:46
*** emagana has joined #openstack-meeting-422:47
*** emagana has quit IRC22:51
*** TxGirlGeek has quit IRC22:53
*** VW has joined #openstack-meeting-422:54
*** david-lyle has joined #openstack-meeting-422:55
*** slaweq has joined #openstack-meeting-422:58
*** VW_ has quit IRC22:58
*** VW has quit IRC22:59
*** slaweq has quit IRC23:00
*** chyka_ has joined #openstack-meeting-423:06
*** bobh has quit IRC23:09
*** chyka has quit IRC23:09
*** david-lyle has quit IRC23:12
*** david-lyle has joined #openstack-meeting-423:13
*** chyka_ has quit IRC23:13
*** chyka has joined #openstack-meeting-423:14
*** TxGirlGeek has joined #openstack-meeting-423:14
*** sambetts is now known as sambetts|afk23:22
*** chyka_ has joined #openstack-meeting-423:32
*** chyka has quit IRC23:35
*** chyka_ has quit IRC23:48
*** chyka has joined #openstack-meeting-423:49
*** chyka_ has joined #openstack-meeting-423:55
*** chyka has quit IRC23:55

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