Monday, 2018-12-10

*** pbourke_ has quit IRC00:13
*** pbourke_ has joined #openstack-meeting-400:13
*** dave-mccowan has quit IRC00:23
*** Liang__ has joined #openstack-meeting-400:37
*** dave-mccowan has joined #openstack-meeting-400:57
*** Liang__ is now known as LiangFang01:10
*** markvoelker has quit IRC01:21
*** markvoelker has joined #openstack-meeting-401:22
*** markvoelker has quit IRC01:26
*** hongbin has quit IRC01:45
*** yamamoto has quit IRC01:50
*** yamamoto has joined #openstack-meeting-401:53
*** yamamoto has quit IRC01:53
*** yamamoto has joined #openstack-meeting-401:56
*** yamamoto has quit IRC01:56
*** yamamoto has joined #openstack-meeting-401:57
*** yamamoto has quit IRC02:05
*** lei-zh has joined #openstack-meeting-402:07
*** bobh has joined #openstack-meeting-402:18
*** yamamoto has joined #openstack-meeting-402:39
*** yamamoto has quit IRC02:46
*** yamamoto has joined #openstack-meeting-402:50
*** psachin has joined #openstack-meeting-402:59
*** hongbin has joined #openstack-meeting-403:05
*** bobh has quit IRC03:31
*** bobh has joined #openstack-meeting-403:42
*** hongbin has quit IRC04:00
*** bobh has quit IRC04:33
*** bobh has joined #openstack-meeting-404:47
*** dave-mccowan has quit IRC04:53
*** bobh has quit IRC05:00
*** yamamoto has quit IRC05:36
*** yamamoto has joined #openstack-meeting-405:39
*** yamamoto has quit IRC05:44
*** yamamoto has joined #openstack-meeting-406:37
*** yamamoto has quit IRC06:42
*** Luzi has joined #openstack-meeting-406:58
*** yamamoto has joined #openstack-meeting-407:12
*** slaweq has joined #openstack-meeting-407:47
*** gkadam has joined #openstack-meeting-407:52
*** trident has quit IRC08:10
*** evrardjp_ is now known as evrardjp08:11
*** trident has joined #openstack-meeting-408:13
*** yboaron has quit IRC08:36
*** yamamoto has quit IRC08:47
*** ralonsoh has joined #openstack-meeting-408:53
*** radeks has joined #openstack-meeting-408:57
*** yamamoto has joined #openstack-meeting-409:17
*** ktibi has joined #openstack-meeting-409:31
*** gcheresh has joined #openstack-meeting-409:35
*** yboaron has joined #openstack-meeting-409:49
*** yamamoto has quit IRC09:58
*** lei-zh has quit IRC10:00
*** e0ne has joined #openstack-meeting-410:03
*** yboaron_ has joined #openstack-meeting-410:04
*** yboaron has quit IRC10:07
*** LiangFang has quit IRC10:14
*** salmankhan has joined #openstack-meeting-410:15
*** e0ne has quit IRC10:30
*** yamamoto has joined #openstack-meeting-410:31
*** e0ne has joined #openstack-meeting-410:36
*** yamamoto has quit IRC10:39
*** yboaron_ has quit IRC10:41
*** yboaron_ has joined #openstack-meeting-410:41
*** yamamoto has joined #openstack-meeting-410:53
*** pbourke_ has quit IRC11:05
*** pbourke_ has joined #openstack-meeting-411:08
*** ktibi has quit IRC11:40
*** yamamoto has quit IRC11:47
*** yamamoto has joined #openstack-meeting-411:47
*** e0ne has quit IRC11:58
*** e0ne has joined #openstack-meeting-412:00
*** e0ne has quit IRC12:00
*** yamamoto has quit IRC12:04
*** yamamoto has joined #openstack-meeting-412:16
*** yamamoto has quit IRC12:22
*** salmankhan has quit IRC12:24
*** ktibi has joined #openstack-meeting-412:28
*** salmankhan has joined #openstack-meeting-412:31
*** ktibi has quit IRC12:39
*** seajay has joined #openstack-meeting-412:57
*** bobh has joined #openstack-meeting-412:58
*** aperevalov has joined #openstack-meeting-413:03
*** psachin has quit IRC13:05
*** dave-mccowan has joined #openstack-meeting-413:13
dmellado#startmeeting kuryr14:00
openstackMeeting started Mon Dec 10 14:00:06 2018 UTC and is due to finish in 60 minutes.  The chair is dmellado. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: kuryr)"14:00
openstackThe meeting name has been set to 'kuryr'14:00
dmelladoHi folks, who's around today?14:00
duleko/14:00
aperevalovo/14:00
dmellado#chair dulek14:00
ltomasboo/14:00
openstackCurrent chairs: dmellado dulek14:00
dmellado#chair ltomasbo14:00
openstackCurrent chairs: dmellado dulek ltomasbo14:00
dmelladohmmm seems like we're missing a few folks around here14:01
yboaron_o/14:01
dmellado#chair yboaron_14:01
openstackCurrent chairs: dmellado dulek ltomasbo yboaron_14:01
dmelladocelebdor_:14:01
dmelladolazy former ptl14:01
dmelladoxD14:01
dmelladoseems like we're also missing sean14:01
dmelladoI wanted to discuss the os-vif issue around here14:02
dmelladodulek: I've seen your email replying to him14:02
dmelladoas I was away due to bank holidays14:02
dmelladoany additional concerns that you or anyone might have with this?14:03
dulekAh, I haven't checked again if I've got a reply to that email…14:03
dmelladoto put up some context on the ppl around here, it seems that os-vif is basically going to change stuff and break backwards compatibility14:03
dmelladoso we have two options, IMHO14:03
dulekHm, nop.e14:03
dmellado1) Check back with the os-vif folks, which I wanted to do today on the meeting14:04
dmelladoor 2) Just go and use kuryr-lib bindings14:04
dmelladowith my personal opinion going on the latter14:04
dmelladoI will also reply to dulek's email14:04
dmelladowith my preference and so, as I would've loved to get some more quorum and discussion on this here14:05
dmelladoso for the people that are around, any concerns on 2) ?14:05
celebdor_I'm here14:05
celebdor_I was dropping the kid at school14:05
dulekdmellado: Remember that besides binding it also means copying os-vif o.vo's into our code.14:06
dulekOtherwise we're unable to read older annotations.14:06
dmelladodulek: yeah, that's why I said I'd address that on an email, as it'd imply some stuff like that14:06
celebdor_dulek: you're right on the older annotations14:07
dmelladocelebdor_: any additional concerns you might have on this?14:07
dmelladoTBH, after the email I was thinking about filling a blueprint14:07
dmelladobut I don't think that this will be affecting to us only14:08
dmelladoand thus wanted to raise the flag with os-vif folks and the TC14:08
dmelladoas breaking backwards compatibility is something that probably won't be allowed14:08
dulekdmellado: Well, they say that o.vo's serialization was never the public API.14:08
dulekFrom my discussion with Sean they're really willing to do changes in such a way that we can easily support.14:09
dmelladodulek: my concern is that this might happen again in the future14:09
dmelladoand we'd be better off with something that is under our control14:10
dmelladobut I'll follow up on the email. Sean told me that he'd be attending the meeting today but obviously he couldn't xD14:10
dulekdmellado: Yeah, I get the argument. My concern with os-vif policy on that email is "we will support serialization in the future".14:11
dulekFor us it should be - we make necessary changes now, Kuryr folks swallow that and from now on it's stable, public API.14:11
dulekWith that I'd be fine.14:11
dmelladodulek: yeah, I was looking for some reply there, let's see14:11
dmellado+114:11
dmelladootherwise we'll go for our own version14:12
dulekFine with me, sounds like a fair trade-off for both teams.14:12
dulekAnd I know that celebdor_ is for ditching it now. ;)14:13
dmelladoso, what else? I've a few more topics for the day but I don't want to monopolize the meeting14:13
dmelladoanything else anyone? xD14:13
aperevalov maybe me, something regarding SR-IOV again )14:14
dmelladoaperevalov: shoot! ;)14:14
celebdor_dulek: I'm for keeping it during 1514:14
celebdor_and ditching it for 1614:14
dmelladocelebdor_: that's DS xD14:15
celebdor_I meant, S and Train14:15
dulekcelebdor_: You mean Stein and train?14:15
*** e0ne has joined #openstack-meeting-414:15
dmelladoexactly14:15
celebdor_I only remember train14:15
celebdor_CHoo CHoooo14:15
aperevalovwe tald about tempest tests, so now it almost done, but now I'm in vacation ), but I have some point... it's about dummy implementation...14:15
dmelladocelebdor_: https://www.youtube.com/watch?v=4k8ICZoMIJ014:15
aperevalovw/o sriov hw14:15
celebdor_aperevalov: what's the minimum kernel req for that?14:16
aperevalovcelebdor_, do you mean for none hw way of testing?14:16
celebdor_yeah14:16
celebdor_for gates14:16
dmelladoaperevalov: so basically we want to make sure that the dummy one is something that is supported on gates hw14:17
aperevalovunfortunately it's impossible to do it w/o hardware right now, I tald with sean about it, he did the same reseach of kernel/qemu. I filled blueprint for it.14:17
dmelladoaperevalov: do you have any link for it?14:18
aperevalovone moment14:19
dmelladoaperevalov: if that's the case the best case would be for this would be to have third party CI for kuryr with SRIOV hardware. Back there garyloug told that intel would be willing to provide such hw setup14:19
dmelladobut we'd need to double check with him14:19
aperevalovcelebdor_, please take a look at https://blueprints.launchpad.net/kuryr-kubernetes/+spec/test-sriov-ports-without-sriov-hw14:20
aperevalovI assumed to do some mockup which doesn't require hw, but it requires sriov binding driver modification (some special mode). I feel it's not good idea ;)14:21
dmellado#link https://blueprints.launchpad.net/kuryr-kubernetes/+spec/test-sriov-ports-without-sriov-hw14:21
dmelladoaperevalov: I'll check with the infra folks just in case, but seems like FT won't be possible for now, yeah14:22
aperevalovregarding Gary, and his nested, I rebased, but upper-constraints.txt still has os-vif 1.11.1 reference, need to update it to 1.12, I already updated in patch (requirements.txt) to 1.12)14:22
dmellado#action dmellado to check with infra re: sriov hw14:22
dulekaperevalov: We've talked at the Summit that for the first step it's fine if you'll add a "dummy" SR-IOV binding driver.14:22
dulekaperevalov: So I'm fine with this.14:23
dmelladodulek: yeah, until 3rd party CI is set that's the max they would be able to do14:23
dmelladoI recall speaking with AJaeger about hw anyway, so I'll recheck14:23
aperevalovdulek, ok. Separate driver or just a configuration tweak for current one?14:23
dmelladofrom my side both would work, unless the strict dulek has any more concerns xD14:24
aperevalov;)14:24
*** gkadam has quit IRC14:24
dulekaperevalov: Separate, just make it inherit from the current one. :)14:25
aperevalovok14:25
dmelladoall right, anything else on sriov?14:25
*** aspiers has quit IRC14:26
aperevalovI think that all for now except this one https://review.openstack.org/#/c/616504/.14:27
aperevalov And regarding DPDK, I hope Danil will check Gary's patch in run time.14:27
dmelladoawesome, thanks for all the update aperevalov14:28
dmelladodulek: I'm pretty sure you'd have a new topic, besides Alhambra14:28
aperevalovwe changed interface and added container_id, it was necessary for DPDK on BM, but SR-IOV binding driver was merged w/o correct rebase. Also that patch adds unit tests.14:29
dulekdmellado: Uhm…?14:29
dmelladodulek: meeting topic, I meant ;)14:29
dulekaperevalov: I have it opened, will review in next round. :)14:29
dmelladootherwise, I can go14:29
dmelladoltomasbo: around?14:29
dulekdmellado: Well, we were to discuss the idea of dropping support for running non-containerized Kuryr-Kubernetes?14:29
ltomasbodmellado, have to leave now-ish for a meeting...14:30
dmelladoyep, CI stuff was my next topic14:30
dmelladoltomasbo: go to your meeting, we'll sync afterwards14:30
ltomasbodmellado, I'll be reading... and trying to answer14:30
dmelladojust wanted to mention that regarding NP, we'll make a kuryr release supporting it within this week14:30
dmelladoI'll be finishing the devref14:30
dmelladoand putting up a few more tempest tests for its experimental gate14:31
aperevalovwe're using venv for development14:31
dmellado#topic Upstream CI14:32
*** openstack changes topic to "Upstream CI (Meeting topic: kuryr)"14:32
dmelladohere as dulek was saying I was thinking about changing both the documentation and the gates14:32
dmelladoand set containerized and daemonized as both the preferred installation mode14:32
dmelladoand the main gates there14:32
dmelladohttps://review.openstack.org/#/c/623444/14:32
dmelladofrom this patch, dulek had a few concerns where we agreed to keep the lbaas and the centos gate, at least for the cycle14:33
dmelladoso has anyone strong feelings about this? xD14:33
dulekSoooo… Who's using kuryr-kubernetes anywhere? :D14:34
dulekAnd can provide us with feedback on how they run it?14:34
dulekBecause that needs to be main decision factor.14:35
dulekIf we'll be breaking someone's use case, we're the evil breaking-backwards-compatibility guys.14:35
aperevalovdulek, our production is containerized14:35
dulekaperevalov: That's great to hear. :)14:35
dmelladoawesome, totally glad to hear that too14:36
dmelladoin any case also I'll send an email to the ML as I wanted to hear from irena and gary14:36
dmelladoand hongbin as well if possible14:36
dmelladoin the meanwhile I'll update my patch14:37
dmelladoand I'll try to make sure I don't become an evil guy in the process, dulek xD14:38
dmellado#topic open discussion14:38
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:38
dmelladoAll right, so it looks like that's it for today14:40
dmelladothanks for attending, folks!14:40
dmellado#endmeeting14:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:41
openstackMeeting ended Mon Dec 10 14:41:00 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-12-10-14.00.html14:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-12-10-14.00.txt14:41
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2018/kuryr.2018-12-10-14.00.log.html14:41
*** aspiers has joined #openstack-meeting-414:47
*** yboaron_ has quit IRC15:01
*** yboaron_ has joined #openstack-meeting-415:02
*** ktibi has joined #openstack-meeting-415:07
*** salmankhan1 has joined #openstack-meeting-415:11
*** salmankhan has quit IRC15:12
*** salmankhan1 is now known as salmankhan15:12
*** aperevalov has quit IRC15:13
*** Luzi has quit IRC15:18
*** mjturek has joined #openstack-meeting-415:19
*** hongbin has joined #openstack-meeting-415:36
*** ktibi has quit IRC15:55
*** gcheresh has quit IRC15:57
*** yboaron_ has quit IRC16:06
*** yboaron_ has joined #openstack-meeting-416:07
*** macza has joined #openstack-meeting-416:08
*** gcheresh_ has joined #openstack-meeting-416:31
*** psachin has joined #openstack-meeting-416:42
*** gcheresh_ has quit IRC16:43
*** yboaron_ has quit IRC16:46
*** yamamoto has joined #openstack-meeting-416:55
*** thedac has joined #openstack-meeting-416:59
thedaco/16:59
*** yamamoto has quit IRC16:59
*** freyes has joined #openstack-meeting-417:00
thedac#startmeeting charms17:00
openstackMeeting started Mon Dec 10 17:00:55 2018 UTC and is due to finish in 60 minutes.  The chair is thedac. 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
openstackThe meeting name has been set to 'charms'17:00
jamespageo/17:01
fnordahl\o17:01
thedac#topic Review ACTION points from previous meeting17:01
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:01
thedacjamespage to sort out wonky bugs in charms that should be fix released17:01
thedacjamespage: Did you get a chance to look at those? ^^17:01
jamespagelets mark that completed - I think I got them all17:01
thedacTa17:01
thedac#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
thedacfnordahl: Want to tell us about Octavia?17:02
fnordahlThe promised stable release update to Octavia landed on Friday17:02
fnordahlThe octavia and barbican-vault charms should be promulgated now, and we are about to get the octavia-dashboard out the door.17:03
thedac\o/17:03
johnsom+1 cool, thank you folks!17:03
fnordahlA section has been added to the deployment guide, there is also a overlay bundle up as a PR to the openstack-bundles repo17:03
thedacThe OpenStack charmers have received our roadmap items and we have begun our next cycle of development for 19.0417:04
thedacMore to come17:04
thedacAnything else to add?17:04
thedacMoving on17:05
thedac#topic High Priority Bugs17:05
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:05
thedac  Critical bugs: https://tinyurl.com/osc-critical-bugs17:05
thedac  High priority bugs: https://tinyurl.com/osc-high-priority17:05
thedac  https://bugs.launchpad.net/openstack-charms/+bugs17:05
thedacWe have a critical bug which I belive admcleod is working on as we speak17:05
thedac73 High importance bugs17:05
thedac60 New bugs17:05
thedacWe are making a dent. More work to do17:05
thedacAny bugs to highlight here?17:06
tinwoodnot from me17:06
thedacOk17:06
thedac#topic Openstack Events17:06
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:06
thedacSince it is the end of the year I am not aware of much until next Spring.17:07
thedacAnyone else have events to talk about?17:07
jamespagenope17:07
thedacOK17:07
thedac#topic Open Discussion17:07
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:07
thedacAnyone have something to discuss?17:08
thedacGoing once17:09
thedactwice17:09
thedac#topic Next Chair17:09
*** openstack changes topic to "Next Chair (Meeting topic: charms)"17:09
thedacgnouy is the next chair17:09
thedacThanks everyone17:09
thedac#endmeeting17:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:09
openstackMeeting ended Mon Dec 10 17:09:47 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-12-10-17.00.html17:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-12-10-17.00.txt17:09
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2018/charms.2018-12-10-17.00.log.html17:09
fnordahlthanks thedac o/17:11
*** e0ne has quit IRC17:22
*** e0ne has joined #openstack-meeting-417:23
*** e0ne has quit IRC17:23
*** e0ne has joined #openstack-meeting-417:26
*** ralonsoh has quit IRC18:04
*** e0ne has quit IRC18:09
*** e0ne has joined #openstack-meeting-418:11
*** e0ne has quit IRC18:11
*** yamahata has quit IRC18:15
*** psachin has quit IRC18:23
*** diablo_rojo has joined #openstack-meeting-418:29
*** e0ne has joined #openstack-meeting-418:34
*** salmankhan has quit IRC18:36
*** yamahata has joined #openstack-meeting-418:54
*** diablo_rojo has quit IRC18:57
*** e0ne has quit IRC19:06
*** diablo_rojo has joined #openstack-meeting-419:09
*** bobh has quit IRC19:15
*** bobh has joined #openstack-meeting-419:25
*** bobh has quit IRC19:30
*** bobh has joined #openstack-meeting-419:34
*** bobh has quit IRC19:38
*** diablo_rojo has quit IRC20:00
*** salmankhan has joined #openstack-meeting-420:01
*** salmankhan has quit IRC20:06
*** freyes has left #openstack-meeting-420:25
*** e0ne has joined #openstack-meeting-420:28
*** e0ne has quit IRC20:28
*** bobh has joined #openstack-meeting-420:30
*** bobh has quit IRC20:35
*** yamamoto has joined #openstack-meeting-420:57
*** diablo_rojo has joined #openstack-meeting-420:58
*** yamamoto has quit IRC21:01
*** salmankhan has joined #openstack-meeting-421:04
*** yboaron_ has joined #openstack-meeting-421:12
*** yboaron_ has quit IRC21:24
*** iyamahat has joined #openstack-meeting-421:34
*** salmankhan has quit IRC21:36
*** bobh has joined #openstack-meeting-421:36
*** radeks has quit IRC21:36
*** mjturek has quit IRC22:03
*** diablo_rojo has quit IRC22:44
*** diablo_rojo has joined #openstack-meeting-423:03
*** dave-mccowan has quit IRC23:19
*** slaweq has quit IRC23:19
*** diablo_rojo has quit IRC23:30
*** bobh has quit IRC23:39
*** bobh has joined #openstack-meeting-423:43
*** yamamoto has joined #openstack-meeting-423:45
*** bobh has quit IRC23:53

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