Monday, 2017-11-13

*** sbezverk has joined #openstack-meeting-400:07
*** hieulq has joined #openstack-meeting-401:00
*** Sukhdev has joined #openstack-meeting-401:08
*** hongbin has joined #openstack-meeting-402:06
*** Sukhdev has quit IRC02:16
*** yifei has joined #openstack-meeting-402:19
*** janonymous has joined #openstack-meeting-402:24
*** Sukhdev has joined #openstack-meeting-402:31
*** salv-orlando has joined #openstack-meeting-402:48
*** salv-orl_ has quit IRC02:51
*** links has joined #openstack-meeting-402:53
*** Sukhdev has quit IRC03:07
*** trungnv has joined #openstack-meeting-403:11
*** Adrian___ has joined #openstack-meeting-403:36
*** abhishekk has joined #openstack-meeting-403:39
*** TuanLA has joined #openstack-meeting-403:39
*** bobh has joined #openstack-meeting-403:45
*** bobh has quit IRC03:49
*** psachin has joined #openstack-meeting-403:56
*** yamamoto has joined #openstack-meeting-404:01
*** dhellmann has quit IRC04:06
*** dhellmann has joined #openstack-meeting-404:07
*** Adrian___ has quit IRC04:08
*** anilvenkata has joined #openstack-meeting-404:21
*** zenirc369 has joined #openstack-meeting-404:40
*** coolsvap has joined #openstack-meeting-405:11
*** eN_Guruprasad_Rn has joined #openstack-meeting-405:29
*** hongbin has quit IRC05:30
*** janki has joined #openstack-meeting-405:33
*** bobh has joined #openstack-meeting-405:47
*** bobh has quit IRC05:52
*** trungnv has quit IRC05:55
*** trozet has quit IRC06:13
*** zenirc369 has quit IRC06:44
*** abhishekk has quit IRC06:49
*** trozet has joined #openstack-meeting-406:50
*** slaweq has joined #openstack-meeting-406:54
*** slaweq has quit IRC06:59
*** yifei has left #openstack-meeting-407:15
*** yujunz has joined #openstack-meeting-407:22
*** yujunz has joined #openstack-meeting-407:24
*** TuanLA has quit IRC07:43
*** trungnv has joined #openstack-meeting-407:44
*** belmoreira has joined #openstack-meeting-407:45
*** bobh has joined #openstack-meeting-407:49
*** bobh has quit IRC07:53
*** zenirc369 has joined #openstack-meeting-408:00
*** oanson_ has joined #openstack-meeting-408:00
oanson_#startmeeting Dragonflow08:01
openstackMeeting started Mon Nov 13 08:01:26 2017 UTC and is due to finish in 60 minutes.  The chair is oanson_. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
dimakhey08:01
*** openstack changes topic to " (Meeting topic: Dragonflow)"08:01
openstackThe meeting name has been set to 'dragonflow'08:01
oanson_Hi08:01
snapiriHi08:01
oanson_Who's here for the weekly?08:01
irenabhi08:01
*** lihi has joined #openstack-meeting-408:01
lihiHi08:01
leyalhi08:01
oanson_Give me a minute to find the agenda, and we can start08:02
oanson_All right. Let's start08:03
oanson_#topic Roadmap08:03
*** openstack changes topic to "Roadmap (Meeting topic: Dragonflow)"08:03
oanson_First off, let me say that lihi and I were in the Sydney summit.08:03
oanson_It was lotsa fun08:03
oanson_But it's nice to be home08:03
irenabsorry having meetings conflict, will catch up later08:04
oanson_We had some interesting talks, which may change a bit the strategy. We'll see how it affects this meeting and next (The ship is still rocking)08:04
oanson_LBaaS08:04
oanson_Please throw your comments at the spec (link in a second)08:04
oanson_#link LBaaS spec https://review.openstack.org/#/c/47746308:04
oanson_This way we can start the implementation08:04
oanson_DNS08:05
oanson_We spoke with the Designate PTL. He's very nice.08:05
oanson_Mostly he said that Designate sits on top of the Neutron DNS integration extension. So our DNS application should only concentrate on that.08:05
dimakoanson_, what do you mean?08:06
oanson_The good news is that it's a very simple API, so the application (barring the general difficulties in DNS) shouldn'08:06
oanson_shouldn't be too complex08:06
oanson_dimak, Neutron gives a DNS server (via dnsmasq, IIRC), and then provides the 'next hop DNS' (I forgot the terminology)08:06
dimakWho deploys the actual DNS service?08:07
dimakDesignate?08:07
oanson_Neutron deploys dnsmasq daemons. We're going to deploy our own. My guess is (lihi do you remember?) that designate integrates with a deployed DNS server (e.g. bind9) and populates it according to its API08:07
oanson_I think the DNS server has to be deployed manually (but maybe deployment options like devstack and OSA provide help with that)08:08
lihiYes I think they deploy their own DNS server08:08
oanson_In any case, it's beyond the scope of the Dragonflow application. So that's good news for us.08:09
dimakSo if that DNS server has a port, what's there for Dragonflow?08:09
oanson_We need to provide a DNS server (-like behaviour) that answers DNS requests for Neutron ports08:09
oanson_As per the Neutron DNS integration extension.08:09
oanson_lihi, I don't have access to it now - could you post the links to the docs?08:10
dimakYou plan on answering it from the controller?08:10
lihihttps://docs.openstack.org/mitaka/networking-guide/config-dns-int.html08:10
*** pcaruana has joined #openstack-meeting-408:10
*** salv-orlando has quit IRC08:11
oanson_dimak, two options: 1. yes. 2. Have a DNS server that answers the request in a similar fashion to the metadata service or HA proxy design in LBaaS.08:11
dimakI may be missing something but I don't see the benefit08:11
*** salv-orlando has joined #openstack-meeting-408:11
oanson_dimak, I don't think the integration is supported at the moment08:11
oanson_We don't have those dnsmasq daemons running in current DF deployment08:12
dimakIf that's just a port like lbaasv2 then there's no problem08:12
oanson_No one to answer DNS requests - it's just forwarded to the configured general DNS server08:12
dimakWe can use dhcp-agent08:12
oanson_Both options require development: Option 1. requires writing the packet handler in the controller. Option 2. requires writing the server: Both reading the info and matching (mangled) IP addresses to ports08:13
oanson_The second is needed to know to which project/network the port belongs08:13
dimakunless designate deploys a DNS server like LBaaSv2 deploys a loadbalancer08:13
*** alexchadin has joined #openstack-meeting-408:13
oanson_We may be able to use an existing dhcp-agent with a few modifications, or an existing DNS library08:14
oanson_dimak, I think whatever Designate deploys is centralised, so that's not a problem for us08:14
leyalit's sound similar to dhcp , maybe we can prevent from the dns request to leave the compute-node ..08:15
oanson_leyal, that's the plan for things we know to respond to08:15
dimakThen you have to run bind9 on all nodes08:15
oanson_Within limits of course - we don't want the compute node to work too hard08:15
*** salv-orlando has quit IRC08:15
oanson_That's why I'm looking at something more lightweight than bind9, like dnsmasq or a simple python service08:15
*** arcolife has joined #openstack-meeting-408:16
oanson_Do we all agree this is a feature we want?08:16
oanson_i.e. to support Neutron DNS integration ?08:16
dimakthen you'll need one per "namespace"08:16
oanson_dimak, I think we can avoid that using existing patterns08:16
dimakIt just seems a lot of effort and resources to distribute DNS08:17
dimakA classic DC does not need one on every node08:18
oanson_The Neutron integration allows you to look up VMs in your project using DNS. That's the part we want to distribute08:18
dimakenough to have a few and do HA08:18
oanson_We can use that solution, but then how do you encode who can see whom?08:18
dimakif you're using bind9, it supports that08:18
oanson_Let's split this discussion in two: 1. Do we want to support this extension? 2. How do we go about it?08:19
dimakyou can have a different view based on query origin08:19
dimakSure,08:19
oanson_Let's vote on 1.:08:19
oanson_+108:19
dimak+108:19
lihi+108:19
oanson_leyal, irenab, snapiri ?08:19
*** ralonsoh has joined #openstack-meeting-408:19
leyal+108:20
oanson_All right, with +4 and 2 abstaining due to timeout, we can go forwards with this08:20
oanson_lihi, you still want this feature?08:20
lihiYes, I can take it08:20
oanson_All right. Then please fire up a spec including the three options (or less, if you think some aren't realistic), and we'll continue the rest of the discussion there?08:21
oanson_dimak, good enough for you?08:21
dimaksure08:21
lihi👍08:21
oanson_Great. Then let's move on08:22
oanson_L3 flavour -08:22
oanson_I'm demoting this for now. It doesn't fit with our immediate strategy08:23
oanson_ETCD publisher -08:23
oanson_I believe this was merged?08:23
oanson_lihi, ?08:23
lihioanson_, yes08:24
oanson_Coo.l08:24
lihiBefore the summit08:24
oanson_Cool!08:24
oanson_Upgrades -08:24
oanson_dimak, I believe we said we're giving this one some air in favour of the wiring feature?08:24
dimakThere's an issue I have there08:25
dimakthat we should see how we can resolve08:25
dimakIt's on the spec08:25
oanson_dimak, all right. Then let's take it there08:25
oanson_Wiring: The spec is here:08:25
oanson_#link Wiring spec (Datapath abstraction) https://review.openstack.org/#/c/503538/08:25
oanson_dimak, I think the current direction is a good one.08:26
dimakThanks08:26
oanson_If we want to change the language later, we can always build a compiler to/from the new language08:26
dimakWill try to drive it to completion08:26
oanson_Thanks.08:26
oanson_I think this is the last step to support pure out-of-tree applications08:27
oanson_Unless there's something I forgot?08:27
oanson_Yes there is: stevedore for models. But that's a small item08:27
oanson_Anything else for features roadmap?08:27
oanson_#topic Deployment08:28
*** openstack changes topic to "Deployment (Meeting topic: Dragonflow)"08:28
oanson_RPM packaging: I spoke with RDO guys at the summit. We agreed on what has to be done.08:28
oanson_OSA - lihi ?08:28
lihiDiscussed with evrardjp, we've got action items to get this thing working08:29
oanson_Sounds good!08:30
oanson_incorporating DF into existing clouds08:30
oanson_Does this belong to anyone?08:30
oanson_That's a shame. Since we're all fully booked, it will have to wait. But it would be great to have this done by end-of-cycle08:31
oanson_Anything else for deployment?08:31
oanson_#topic Gates08:32
*** openstack changes topic to "Gates (Meeting topic: Dragonflow)"08:32
oanson_Grenade depends on upgrade, so that will take a whil08:32
oanson_while*08:32
oanson_Tempest gate - snapiri did some good work there08:32
oanson_In this patch: https://review.openstack.org/#/c/517814/08:32
snapiriall exceptions cleared, take a few that will be handled by leyal's patch08:33
oanson_All right. Cool08:33
oanson_I see they conflict, but I understood that the conflicts aren't difficult. So we'll see which one lands first :)08:33
snapiri:)08:33
oanson_By the way, the other patch is: https://review.openstack.org/#/c/50396508:33
oanson_cores, take your pick :)08:34
*** kkxue has joined #openstack-meeting-408:34
dimaksnapiri, any chance you can split that patch into separate changes?08:34
dimakSo we can examine each fix individually08:35
oanson_^^^ +108:35
snapiriI think so, though each change is quite self-contained in one file08:36
*** salv-orlando has joined #openstack-meeting-408:36
oanson_It would still make the review process easier08:36
leyal+108:36
snapirican do08:36
oanson_Kuryr integration gate: Discussed with apuimedo and dmellado during the summit. We're going to have both a single node and multi node tempest gates, which will run the same tests for ODL and DF, and maybe even DF specific tests in the future08:37
oanson_(This is more of a status update. I don't think we have much to do here yet)08:37
oanson_The gates will be different than the existing install gate08:37
oanson_Anything else for gates?08:37
oanson_#topic Troubleshooting08:38
*** natanbro has joined #openstack-meeting-408:38
*** openstack changes topic to "Troubleshooting (Meeting topic: Dragonflow)"08:38
*** natanbro has left #openstack-meeting-408:39
dimakoanson_, I've uploaded our skydive hackathon code08:39
oanson_OSProfiler - I haven't seen any changes on the patch. snapiri - could you maybe put together a quick tutorial? We can then publish it as a docs or blog post08:39
oanson_dimak, thanks!08:39
oanson_dimak, linky?08:40
dimakSure, available here: https://review.openstack.org/#/c/518670/08:40
snapirioanson, let's take it offline08:40
oanson_snapiri, sure. Thanks!08:40
dimakIt's very raw08:40
snapiridimak, you can say this again :)08:40
oanson_All right. I think we'll work together to get it merge-ready08:40
dimakIt's good for playing around but I think we should write a spec and formalize what we want08:41
oanson_We also have some design questions that need to be answered08:41
oanson_dimak, great minds, etc... :)08:41
dimakAs in - where do we run it? An app? Service plugin? What resources? How?08:41
oanson_Makes sense08:41
oanson_It also looks like our 'topology viewer' will be integrated into Skydive as well.08:42
oanson_snapiri, so maybe you can add your 2 cents to the design too?08:42
oanson_snapiri, ?08:43
snapiridid not get to it yet. we can have a discussion and try to formalize something concrete later this week08:43
oanson_Sure. Let's take this offline then08:43
snapirithough I had some thoughts I already shared with you08:43
*** natanbro has joined #openstack-meeting-408:43
oanson_#topic Documentation08:44
*** openstack changes topic to "Documentation (Meeting topic: Dragonflow)"08:44
*** yujunz has quit IRC08:44
oanson_dimak, snapiri, lihi, you mentioned you have an etherpad with the new docs structure?08:44
oanson_Could one of you share it, please?08:44
dimakYes, a moment08:44
lihi# link https://etherpad.openstack.org/p/dragonflow-documentation08:44
lihi#link https://etherpad.openstack.org/p/dragonflow-documentation * :)08:45
oanson_All right. The next step is to start picking it apart and writing these things08:45
oanson_When you have time, just mark a page as taken, and then take it and write it.08:46
oanson_There is no real rush, but it would be great to have everything finished by end-of-cycle08:46
dimakI think for starters we can restructure our ToC08:46
dimakand move relevant things where they belong already08:46
oanson_Sure. We can start with that08:46
oanson_I think the brunt of the work will be the actual writing, rather than the restructuring, but it's a good place to start.08:47
*** yujunz has joined #openstack-meeting-408:47
oanson_Anythign else for docs?08:47
oanson_Anything*08:47
oanson_#topic Bugs08:48
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"08:48
oanson_We still have one critical bug: https://bugs.launchpad.net/dragonflow/+bug/172073408:48
openstackLaunchpad bug 1720734 in DragonFlow "Floating IP association to LBaaS VIP supported by Octavia does not work" [Critical,New]08:48
oanson_I am working on a temporary solution here:08:48
oanson_https://review.openstack.org/#/c/516101/08:49
oanson_And I hope to turn this into a Neutron API (one sec, I'll find the RFE)08:49
oanson_Neutron RFE: https://bugs.launchpad.net/neutron/+bug/173084508:50
openstackLaunchpad bug 1730845 in neutron "[RFE] support a port-behind-port API" [Undecided,New]08:50
oanson_Anything else for bugs?08:50
oanson_Any particular bugs anyone wants to discuss?08:50
oanson_#topic Open Discussion08:50
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"08:50
oanson_Floor is for the taking. Knock yourselves out08:51
oanson_Last chance?08:51
oanson_All right.08:52
oanson_Thanks everyone!08:52
oanson_#endmeeting08:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:52
openstackMeeting ended Mon Nov 13 08:52:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-11-13-08.01.html08:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-11-13-08.01.txt08:52
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2017/dragonflow.2017-11-13-08.01.log.html08:52
dimakBye08:52
leyalBye08:54
*** oanson_ has quit IRC09:03
*** kkxue has quit IRC09:07
*** yujunz has quit IRC09:27
*** natanbro has left #openstack-meeting-409:45
*** alexchadin has quit IRC09:51
*** alexchadin has joined #openstack-meeting-409:53
*** eN_Guruprasad_Rn has quit IRC09:55
*** yamamoto has quit IRC10:02
*** salmankhan has joined #openstack-meeting-410:07
*** pbourke has quit IRC10:21
*** zenirc369 has quit IRC10:23
*** belmoreira has quit IRC10:42
*** bobh has joined #openstack-meeting-410:51
*** yamamoto has joined #openstack-meeting-410:52
*** bobh has quit IRC10:55
*** sdague has joined #openstack-meeting-411:21
*** arcolife has quit IRC11:50
*** yamamoto has quit IRC11:51
*** bobh has joined #openstack-meeting-411:52
*** seajay has joined #openstack-meeting-411:54
*** bobh has quit IRC11:56
*** alexchadin has quit IRC12:03
*** alexchadin has joined #openstack-meeting-412:03
*** pbourke has joined #openstack-meeting-412:05
*** yamamoto has joined #openstack-meeting-412:08
*** belmoreira has joined #openstack-meeting-412:18
*** salmankhan has quit IRC12:27
*** salmankhan has joined #openstack-meeting-412:29
*** markvoelker has joined #openstack-meeting-412:53
*** salmankhan has quit IRC12:57
*** salmankhan has joined #openstack-meeting-412:58
*** julim has quit IRC13:01
*** alexchadin has quit IRC13:07
*** alexchadin has joined #openstack-meeting-413:08
*** alexchadin has quit IRC13:10
*** alexchadin has joined #openstack-meeting-413:11
*** yboaron has joined #openstack-meeting-413:24
*** yamamoto has quit IRC13:24
*** efried has joined #openstack-meeting-413:30
*** yboaron has quit IRC13:31
*** yboaron has joined #openstack-meeting-413:31
*** woodard_ has quit IRC13:35
*** woodard has joined #openstack-meeting-413:36
*** coolsvap has quit IRC13:48
*** efried has left #openstack-meeting-414:02
irenab#startmeeting kuryr14:07
openstackMeeting started Mon Nov 13 14:07:39 2017 UTC and is due to finish in 60 minutes.  The chair is irenab. Information about MeetBot at http://wiki.debian.org/MeetBot.14:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:07
*** openstack changes topic to " (Meeting topic: kuryr)"14:07
openstackThe meeting name has been set to 'kuryr'14:07
irenabhi, who is here for kuryr meeting?14:07
yboaronHi14:08
*** salmankhan has quit IRC14:09
duleko/14:09
irenabyboaron, dulek hi14:09
leyalo/14:09
ltomasboo/14:09
irenab#info yboaron dulek leyal ltomasbo irenab in a meeting14:10
irenablets start14:10
*** lyan has joined #openstack-meeting-414:10
irenabapuimedo asked me to chair the meeting today, he is sick and still recovering from the trip to OS summit14:11
irenabI suggest we skip kuryr and kuryr-libnetwork topics, unless you have something to update14:11
irenab#topic kuryr-kubernetes14:12
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:12
irenabdulek: do you want to update regarding CNI slip adventure?14:12
dulekirenab: Sure!14:12
dulekSooo… ltomasbo found bugs that I was fixing most of the last week.14:13
*** julim has joined #openstack-meeting-414:13
dulekPatches are ready again, bugs were related to incorrect assumption we had in Kuryr, that's why it took me whole week.14:13
ltomasbowell, I would say I hit the bug, but dulek found it14:13
dulekSo this is the main patch: https://review.openstack.org/#/c/515186/, it's dependent on one more bugfix.14:14
irenabdulek: the missing container_id check?14:14
dulekirenab: Yes, but also some pyroute2 internal timeout issues.14:15
dulekI hope apuimedo will be well tomorrow and we'll be able to start merging the patches. :)14:15
irenabdulek: please share the link14:15
irenab#link https://review.openstack.org/#/c/515186/14:15
irenab#action apuimendo irenab to review the https://review.openstack.org/#/c/515186/14:16
dulekirenab: Hm, I don't have a bug created for this pyroute2 issue as I think it only manifests in CNI daemon case - so fix for this one is included.. ;)14:16
irenabdulek: so the same patch, right?14:17
dulekYes.14:17
irenabgreat14:17
irenabgood that you and ltomasbo ran scale scenario14:17
dulekirenab: https://review.openstack.org/#/c/515186/11/kuryr_kubernetes/cni/daemon/service.py@194 - if you're interested in how fix looks like.14:17
dulekYeah, thanks ltomasbo for running the tests!14:18
*** links has quit IRC14:18
ltomasbonp, glad to help!14:18
irenabdulek: so the fix is to increase timeout?14:18
ltomasboand it was not that big scale, just a bunch of pods in a single server (around 20-30)14:18
dulekirenab: More like to make it configurable. My kernel on a VM was just not fast enough to complete all the pyroute2 operations in default 5 seconds.14:19
irenabI wonder if the timeout shouldn’t be dynamically adjustable14:19
dulekirenab: In case a timeout will be hit - kubelet will retry, so with bug 1731485 fixed we'll be fine anyway.14:20
openstackbug 1731485 in kuryr-kubernetes "Kuryr ignores CNI_CONTAINERID when serving requests" [High,In progress] https://launchpad.net/bugs/1731485 - Assigned to Michal Dulko (michal-dulko-f)14:20
irenabdulek: proably need to add some advisory on how to setup the timeout14:20
dulekirenab: To be honest - I don't really know how to do that myself. I was just trying a few values, 30 seconds were enough for ~50 pods being created.14:21
dulekirenab: Plus this timeout doesn't mean we'll be always waiting that much. It's just the maximum wait time.14:21
irenabdulek: I am just not sure we should expose some operator facing configs if we are not sure how to set them …14:22
dulekirenab: I think I can add some documentation describing relationships between timeouts as we have multiple options now.14:22
irenabgood enough, lets keep reasonable default and document the relationship to enable tuning14:23
dulekWill do!14:23
irenabdulek: thanks a lot14:23
irenab#action dulek to document the CNI daemon config timeout14:24
irenabdulek: anything else you would like to raise?14:25
*** yamamoto has joined #openstack-meeting-414:25
dulekNope, that's it, thanks!14:25
irenabltomasbo: anything from your side?14:25
ltomasboI have a patch about adding a readiness probe to the kuryr controller14:25
ltomasbowhen running in containerized mode14:26
ltomasbohttps://review.openstack.org/#/c/518502/14:26
ltomasbodulek, already provided some reviews14:26
irenabltomasbo: this should prevent kuryr controller pod to be considered active till pools are populated?14:26
ltomasboit basically makes the controller not ready until the precreated ports have been loaded14:26
irenab#link https://review.openstack.org/#/c/518502/14:27
ltomasboirenab, yep, until the existing ports are loaded into their respective pools14:27
irenabltomasbo: any issue you want to discuss?14:27
irenab#action everyone please review https://review.openstack.org/#/c/518502/14:27
*** salmankhan has joined #openstack-meeting-414:28
ltomasboI tested it and seems to work find14:28
ltomasbo*fine14:28
dulekltomasbo: One question… Besides pod being not ready - does it affect if it accepts requests?14:28
irenabltomasbo: I wonder if there supposed to be single readiness probe per container or there can be few?14:28
*** makowals has quit IRC14:29
ltomasboirenab, that I don't know, but probably there may be more than one, need to check that14:29
ltomasboirenab, are you thinking on another test to be added?14:29
*** belmoreira has quit IRC14:30
irenabltomasbo: yes, maybe one will beneeded once Network Policies are supported14:30
ltomasbodulek, I assume it should not accept requests, but didn't check actually14:30
irenabdulek: this is probably up to k8s to manage14:30
ltomasboirenab, worse case we can create a script that it to be executed and return a given value, and that could include several checkings14:31
dulekltomasbo: If it's before Watcher is started, then it won't.14:31
irenabltomasbo: +114:31
*** makowals has joined #openstack-meeting-414:31
ltomasbodulek, good question, I will double check that14:32
dulekirenab: k8s can manage that if e.g. the Pod is added to a Service. But kuryr-controller have no API.14:32
*** belmoreira has joined #openstack-meeting-414:32
irenabthere is the one for the tool to populate pools14:32
dulekltomasbo: It would be good to block annotating VIFs until we have all info recovered. But that's most likely already done. :)14:32
irenabdulek: do you suggest internal controller state of being active?14:33
irenabmaybe a good idea14:33
ltomasbodulek, that was the intention with the readiness probe, but I just added the check, so probably not at the right place... :/14:34
dulekirenab: Yes, or more specifically - not to start any Watcher before all ports are recovered.14:34
yboaronltomasbo, is it probe per pod/resource or a global one ?14:34
*** SerenaFeng has joined #openstack-meeting-414:34
dulekltomasbo: Yeah, so if that was the intention, then k8s will not manage that for you on it's own.14:34
*** yamamoto has quit IRC14:34
yboaronresource14:34
irenabdulek: yes, moving to Active will ‘open’ the controller to external world14:34
*** SerenaFeng has quit IRC14:35
irenabyboaron: Pod (which is k8s Controller container)14:35
ltomasboirenab, dulek: I thought that was managed by kubernetes, if it was not ready, it will not receive requests14:35
dulekirenab: Oh? So until it's ready pod will have no network connectivity? Then it will be unable to complete the recovery.14:35
ltomasboyboaron, yep, the kuryr-controller pod14:36
dulekltomasbo: Yes, but what requests? Controller watches on k8s API, doesn't do much more.14:36
ltomasbodulek, controller calls neutron to get/create the ports14:36
irenabI think it can still work, but will allocate the ports via neutron14:37
dulekltomasbo: Sure thing, but how can k8s block that? Let me try to find this in k8s docs.14:37
irenabltomasbo: waht was your intention with the readiness probe?14:38
ltomasbodulek, irenab: "A pod with containers reporting that they are not ready does not receive traffic through Kubernetes Services."14:38
dulekltomasbo: Exactly. And we're not using Services for kuryr-controller, as it doesn't have an API.14:38
irenabltomasbo: so what it supposed to serve?14:39
dulekltomasbo: Where by Service I mean this: https://kubernetes.io/docs/concepts/services-networking/service/ - it's just a load balancer.14:39
ltomasbodulek, aren't we?14:39
ltomasbodon't we have a service (lbaas) for the K8S API?14:39
irenabltomasbo: but k8s controller jst watches the events, it does not serve any API requests14:39
dulekirenab: Right! :)14:40
irenabltomasbo: I wonder if it is realted to any further work of adding HA to the k8s controller14:40
ltomasbodulek, irenab: yep, but if kubernete sets the pod as not ready, it will not perform the API actions regarding the kuryr-controller (the needed annotations)14:40
*** janki has quit IRC14:41
dulekltomasbo: Can you check that? If it's true, then I'm totally wrong and should apologize.14:41
ltomasbono, most probably I'm wrong, I did not check that14:41
ltomasboI just assumed kubernetes was taking care of that14:42
*** d0ugal has quit IRC14:42
ltomasboI will double check14:42
ltomasbothanks for pointing that out!14:42
irenabltomasbo: so you suggest that k8s will ignore the changes applied by k8s controller on k8s API ?14:42
irenabtill it is ready?14:42
ltomasbothat is what I understood from this: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#define-readiness-probes14:43
irenab#action ltomasbo check and update regarding readiness probe for k8s controller14:43
irenabltomasbo: thanks, lets follow up on this after the check14:44
irenableyal: do you want to update regarding Network Policy support?14:44
leyalyes ,14:44
leyali upload a spec -14:44
irenablink?14:45
leyalhttps://review.openstack.org/#/c/519319/ \14:45
irenab#link https://review.openstack.org/#/c/519319/ Network Policy Spec14:45
irenabeveryone  please review the spec14:46
irenableyal: anything you want to raise now?14:46
*** d0ugal has joined #openstack-meeting-414:46
leyallets to the discussion on the patch ..14:47
irenabsure, thank you for the update14:47
leyalit's contains a lot of details..14:47
irenabanything else on kuryr-kubernetes?14:48
*** d0ugal_ has joined #openstack-meeting-414:48
irenab#topic open discussion14:49
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:49
irenabany other issue/topic to discuss?14:49
*** d0ugal_ has quit IRC14:50
irenabI hope next time we will have dmellado and apuimedo to share the inputs from the summit14:50
*** d0ugal_ has joined #openstack-meeting-414:50
irenabWell, I think we can close a meeting few munute earlier14:51
*** d0ugal has quit IRC14:51
irenabthanks everyone for joining14:51
irenab#endmeeting14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:51
openstackMeeting ended Mon Nov 13 14:51:37 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-11-13-14.07.html14:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-11-13-14.07.txt14:51
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2017/kuryr.2017-11-13-14.07.log.html14:51
*** yboaron has left #openstack-meeting-414:51
*** d0ugal_ is now known as d0ugal14:52
*** d0ugal has quit IRC14:53
*** d0ugal has joined #openstack-meeting-414:53
*** d0ugal has quit IRC14:53
*** d0ugal has joined #openstack-meeting-414:53
*** yamahata has joined #openstack-meeting-415:00
*** arcolife has joined #openstack-meeting-415:02
*** hongbin has joined #openstack-meeting-415:05
*** galstrom_zzz is now known as galstrom15:11
*** salv-orlando has quit IRC15:15
*** salv-orlando has joined #openstack-meeting-415:15
*** salv-orlando has quit IRC15:20
*** SerenaFeng has joined #openstack-meeting-415:20
*** galstrom is now known as galstrom_zzz15:41
*** yboaron has joined #openstack-meeting-415:41
*** galstrom_zzz is now known as galstrom15:43
*** david-lyle has joined #openstack-meeting-415:44
*** galstrom is now known as galstrom_zzz15:50
*** dave-mccowan has joined #openstack-meeting-415:52
*** makowals has quit IRC15:53
*** belmoreira has quit IRC15:53
*** bobh has joined #openstack-meeting-415:56
*** belmoreira has joined #openstack-meeting-416:00
*** alexchadin has quit IRC16:06
*** SerenaFeng has quit IRC16:11
*** salv-orlando has joined #openstack-meeting-416:16
*** iyamahat has joined #openstack-meeting-416:20
*** salv-orlando has quit IRC16:21
*** yboaron has quit IRC16:24
*** belmoreira has quit IRC16:25
*** psachin has quit IRC16:46
*** galstrom_zzz is now known as galstrom16:47
*** pcaruana has quit IRC16:49
*** makowals has joined #openstack-meeting-416:52
tinwoodhi all17:00
thedaco/17:00
coreycbo/17:00
tinwoodI'll give it a minute for more people to turn up.17:00
tinwood#startmeeting charms17:01
openstackMeeting started Mon Nov 13 17:01:31 2017 UTC and is due to finish in 60 minutes.  The chair is tinwood. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: charms)"17:01
openstackThe meeting name has been set to 'charms'17:01
tinwoodThe agenda is: https://etherpad.openstack.org/p/openstack-charms-weekly-meeting-2017111317:01
tinwoodHello all17:01
tinwoodkicking off, just a quick review17:01
tinwood#topic Review ACTION points from previous meeting17:02
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:02
tinwoodthe actions were:17:02
tinwoodall - fix critical and high priority bugs (currently at 1/59) - carried over17:02
tinwoodjamespage to review changes to openstack endpoint loadbalancer spec17:02
tinwoodjamespage - update the release policy again - ongoing.17:02
tinwoodThe first one we can probably drop?  (i.e. we're always going to want to do that).17:02
tinwoodIs jamespage with us?17:02
tinwoodokay, we'll carry those two over.17:03
jamespageo/17:03
jamespagesorry was typing something needed to finish17:03
tinwoodHi jamespage17:03
jamespageyes just carry the release clarification one pls17:03
tinwoodokay, will do.17:04
tinwoodright, moving on ...17:04
tinwood#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
tinwoodAnything significant that needs to be noted?17:04
thedacWork on the Python3 migration in progress17:05
thedacSwift storage ACLs landed17:05
tinwoodah, yes, some are easier than others.17:05
tinwoodAnd lots of bugs fixed.17:05
tinwoodAnyone else for this topic?17:06
tinwoodOkay, moving on ...17:06
tinwood#topic High Priority Bugs17:07
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:07
tinwoodUseful urls:17:07
tinwood  https://bugs.launchpad.net/openstack-charms/+bugs17:07
tinwood  Use stable-backport tag for bugs  http://tinyurl.com/charm-stable-backports17:07
tinwood  Critical bugs: https://tinyurl.com/osc-critical-bugs17:07
tinwood  High priority bugs: https://tinyurl.com/osc-high-priority17:07
tinwoodWe have just 2 open critical bugs: https://bugs.launchpad.net/charm-test-infra/+bug/1728843 and https://bugs.launchpad.net/charm-neutron-api/+bug/172398117:08
openstackLaunchpad bug 1728843 in OpenStack Charm Test Infra "OSCI test_charm_single failing due to missing keystone package" [Critical,Confirmed] - Assigned to Ryan Beisner (1chb1n)17:08
openstackLaunchpad bug 1723981 in OpenStack neutron-api charm "Neutron-api fails ocata to pike upgrade" [Critical,Confirmed]17:08
thedacI am looking at the neutron-api bug17:08
thedacI'll take ownership of that17:08
tinwoodThanks very much thedac17:09
*** salv-orlando has joined #openstack-meeting-417:09
tinwoodThere are 51 outstanding high priority bugs currently.17:10
tinwoodWhich is fewer than a couple of weeks ago.17:10
tinwoodWhich is good news.17:10
tinwoodAnything more on bugs?17:10
coreycbnice downward trend17:10
tinwoodOkay, on to the next topic ...17:11
tinwood#topic Openstack Events17:11
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:11
tinwoodSo we just had sydney.17:11
tinwoodAny comments from attendees?17:12
tinwood(I think they mostly have jetlag!)17:13
thedac:)17:13
*** makowals has quit IRC17:13
tinwoodRight next!17:13
tinwood#topic Open Discussion17:13
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:13
tinwoodThe floor is open :)17:13
*** makowals has joined #openstack-meeting-417:13
*** makowals has quit IRC17:14
thedacnothing from me17:14
*** makowals has joined #openstack-meeting-417:14
Dmitrii-Shquestion17:14
tinwoodHi Dmitrii-Sh:)17:15
tinwoodgo on.17:15
Dmitrii-Shwhat's the latest on service discovery?17:15
*** makowals has quit IRC17:15
Dmitrii-Shsorry, got in late17:15
tinwoodno problem17:15
Dmitrii-ShI have an intention to write some code in ceilometer17:15
tinwoodI'm going to have to defer that question to someone else.17:15
Dmitrii-Shwhere it checks relations via charm-helpers17:15
tinwoodWe can take it as an action?17:15
*** makowals has joined #openstack-meeting-417:15
Dmitrii-Shyes17:16
Dmitrii-Shthis is needed for panko basically17:16
tinwoodokay, Dmitrii-Sh, I'll take an action to find out where we are with it.17:16
*** makowals has joined #openstack-meeting-417:16
*** makowals has quit IRC17:16
tinwood#action tinwood find out status of service discovery17:16
Dmitrii-Shif there is no panko, there shouldn't be a configuration that configures a publisher for it in ceilometer17:17
*** makowals has joined #openstack-meeting-417:17
*** makowals has quit IRC17:17
thedacDmitrii-Sh: https://specs.openstack.org/openstack/charm-specs/specs/queens/approved/service-discovery.html17:17
Dmitrii-Shotherwise messages will not be delivered to anyone17:17
thedacthat spec is designed to solve this issue17:18
Dmitrii-Shthedac: yes, just wanted to know if anybody had a peek at that yet before I start doing any changes17:18
thedacjamespage: ? ^^17:18
thedacI am not aware of anyone diving in quite yet17:18
jamespagenot yet17:18
Dmitrii-Shok17:19
tinwoodOkay, thanks Dmitrii-Sh for raising that.17:20
tinwoodIs there anything else (from anybody including Dmitrii-Sh)?17:20
Dmitrii-ShI will get back to my ceilometer patch then and see how I can take that spec into account17:20
*** janonymous has quit IRC17:20
tinwoodokay.17:21
tinwoodwell, next up in the chair is beisner17:21
tinwoodand with that, thanks everybody.17:21
thedacthanks, tinwood17:22
tinwood#endmeeting17:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:22
Dmitrii-Shthx tinwood17:22
openstackMeeting ended Mon Nov 13 17:22:02 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-11-13-17.01.html17:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-11-13-17.01.txt17:22
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-11-13-17.01.log.html17:22
coreycbthanks tinwood17:22
*** ralonsoh has quit IRC17:22
jamespageta17:31
*** salmankhan has quit IRC18:20
*** woodard has quit IRC18:28
*** woodard has joined #openstack-meeting-418:29
*** woodard has quit IRC18:30
*** woodard has joined #openstack-meeting-418:31
*** slaweq has joined #openstack-meeting-418:36
*** Sukhdev has joined #openstack-meeting-418:57
*** slaweq has quit IRC19:03
*** yamahata has quit IRC19:09
*** slaweq has joined #openstack-meeting-419:13
*** makowals has joined #openstack-meeting-419:26
*** makowals has quit IRC20:02
*** iyamahat has quit IRC20:12
*** rockyg has joined #openstack-meeting-420:13
*** iyamahat has joined #openstack-meeting-420:13
*** woodard has quit IRC20:16
*** woodard_ has joined #openstack-meeting-420:16
*** woodard_ has quit IRC20:21
*** woodard has joined #openstack-meeting-420:22
*** salv-orlando has quit IRC20:28
*** salv-orlando has joined #openstack-meeting-420:28
*** iyamahat has quit IRC20:29
*** dklyle has joined #openstack-meeting-420:31
*** david-lyle has quit IRC20:31
*** salv-orlando has quit IRC20:33
*** iyamahat has joined #openstack-meeting-420:44
*** seajay has quit IRC20:53
*** salv-orlando has joined #openstack-meeting-421:00
*** rocky_g has joined #openstack-meeting-421:01
*** rockyg has quit IRC21:01
*** arcolife has quit IRC21:02
*** yamahata has joined #openstack-meeting-421:02
*** woodard has quit IRC21:06
*** woodard has joined #openstack-meeting-421:06
*** woodard has quit IRC21:07
*** woodard has joined #openstack-meeting-421:07
*** d0ugal has quit IRC21:10
*** d0ugal has joined #openstack-meeting-421:11
*** Sukhdev has quit IRC21:12
*** rocky_g has quit IRC21:21
*** mgkwill_ has joined #openstack-meeting-421:46
*** xgerman__ has joined #openstack-meeting-421:46
*** vdrok_ has joined #openstack-meeting-421:46
*** fkautz_ has joined #openstack-meeting-421:46
*** icey_ has joined #openstack-meeting-421:46
*** johnsom_ has joined #openstack-meeting-421:46
*** patrickeast_ has joined #openstack-meeting-421:46
*** julim has quit IRC21:47
*** patrickeast has quit IRC21:51
*** mgkwill has quit IRC21:51
*** xgerman_ has quit IRC21:51
*** ying_zuo has quit IRC21:51
*** icey has quit IRC21:51
*** johnsom has quit IRC21:51
*** fkautz has quit IRC21:51
*** diablo_rojo_phon has quit IRC21:51
*** fungi has quit IRC21:51
*** vdrok has quit IRC21:51
*** gnuoy has quit IRC21:51
*** rwellum has quit IRC21:51
*** xgerman__ is now known as xgerman_21:51
*** patrickeast_ is now known as patrickeast21:51
*** mgkwill_ is now known as mgkwill21:51
*** icey_ is now known as icey21:51
*** fkautz_ is now known as fkautz21:51
*** vdrok_ is now known as vdrok21:51
*** johnsom_ is now known as johnsom21:51
*** diablo_rojo_phon has joined #openstack-meeting-421:52
*** fungi has joined #openstack-meeting-421:53
*** gnuoy has joined #openstack-meeting-421:54
*** kbyrne has quit IRC21:54
*** kbyrne has joined #openstack-meeting-421:56
*** rwellum has joined #openstack-meeting-421:58
*** slaweq has quit IRC22:36
*** lyan has quit IRC22:44
*** iyamahat_ has joined #openstack-meeting-423:06
*** iyamahat has quit IRC23:06
*** bobh has quit IRC23:15
*** galstrom is now known as galstrom_zzz23:23
*** salv-orlando has quit IRC23:37
*** salv-orlando has joined #openstack-meeting-423:38
*** salv-orlando has quit IRC23:42
*** ying_zuo has joined #openstack-meeting-423:44
*** julim has joined #openstack-meeting-423:51
*** julim has quit IRC23:55

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