Thursday, 2018-10-18

*** Swami has quit IRC00:02
*** mjturek has quit IRC00:05
*** TuanVu has joined #openstack-meeting-300:16
*** TuanVu has quit IRC00:23
*** TuanVu has joined #openstack-meeting-300:32
*** TuanVu has quit IRC00:36
*** diablo_rojo has quit IRC00:39
*** njohnston has quit IRC00:48
*** TuanVu has joined #openstack-meeting-300:53
*** TuanVu has quit IRC00:57
*** bobh has quit IRC01:00
*** markvoelker has joined #openstack-meeting-301:05
*** markvoelker has quit IRC01:09
*** TuanVu has joined #openstack-meeting-301:10
*** yamahata has quit IRC01:14
*** TuanVu has quit IRC01:15
*** TuanVu has joined #openstack-meeting-301:25
*** TuanVu has quit IRC01:29
*** TuanVu has joined #openstack-meeting-301:38
*** TuanVu has quit IRC01:43
*** TuanVu has joined #openstack-meeting-301:53
*** TuanVu has quit IRC01:58
*** TuanVu has joined #openstack-meeting-302:01
*** TuanVu has quit IRC02:05
*** TuanVu has joined #openstack-meeting-302:09
*** TuanVu has quit IRC02:14
*** TuanVu has joined #openstack-meeting-302:21
*** TuanVu has quit IRC02:25
*** TuanVu has joined #openstack-meeting-302:27
*** hongbin has joined #openstack-meeting-302:29
*** TuanVu has quit IRC02:32
*** TuanVu has joined #openstack-meeting-302:34
*** psachin has joined #openstack-meeting-302:53
*** bnemec has joined #openstack-meeting-303:05
*** bnemec has quit IRC03:10
*** isq_ has joined #openstack-meeting-303:37
*** yamahata__ has quit IRC03:39
*** hongbin has quit IRC03:57
*** TuanVu has quit IRC04:01
*** TuanVu has joined #openstack-meeting-304:05
*** yamamoto has quit IRC04:34
*** yamamoto has joined #openstack-meeting-304:34
*** TuanVu has quit IRC04:44
*** liuyulong has quit IRC05:24
*** Luzi has joined #openstack-meeting-306:15
*** e0ne has joined #openstack-meeting-306:38
*** lpetrut has joined #openstack-meeting-307:09
*** alexchadin has joined #openstack-meeting-307:14
*** alexchadin has quit IRC07:19
*** persia has quit IRC07:19
*** persia has joined #openstack-meeting-307:21
*** apetrich has quit IRC07:39
*** apetrich has joined #openstack-meeting-308:00
*** e0ne has quit IRC08:02
*** slaweq has joined #openstack-meeting-308:02
*** e0ne has joined #openstack-meeting-308:13
*** tssurya has joined #openstack-meeting-308:16
*** alexchadin has joined #openstack-meeting-308:40
*** alexchadin has quit IRC09:50
*** yamamoto has quit IRC10:11
*** yamamoto has joined #openstack-meeting-310:12
*** yamamoto has quit IRC10:16
*** yamamoto has joined #openstack-meeting-310:16
*** yamamoto has quit IRC11:20
*** yamamoto has joined #openstack-meeting-311:21
*** yamamoto has quit IRC11:25
*** njohnston has joined #openstack-meeting-311:27
*** e0ne has quit IRC11:50
*** yamamoto has joined #openstack-meeting-312:03
*** raildo has joined #openstack-meeting-312:13
*** yamamoto has quit IRC12:20
*** yamamoto has joined #openstack-meeting-312:20
*** apetrich has quit IRC12:21
*** liuyulong has joined #openstack-meeting-312:27
*** dims has quit IRC12:30
*** dims has joined #openstack-meeting-312:33
*** apetrich has joined #openstack-meeting-312:33
*** lpetrut has quit IRC12:33
*** psachin has quit IRC12:50
*** bobh has joined #openstack-meeting-313:01
*** e0ne has joined #openstack-meeting-313:07
*** adriancz has quit IRC13:21
*** mjturek has joined #openstack-meeting-313:22
*** munimeha1 has joined #openstack-meeting-313:29
*** mjturek has quit IRC13:43
*** bnemec has joined #openstack-meeting-313:43
*** tosky has joined #openstack-meeting-313:54
*** annp_ has joined #openstack-meeting-313:55
*** jeremyfreudberg has joined #openstack-meeting-313:58
toskyhi, anyone interested in the Sahara meeting??14:01
tosky(with just one "?")14:01
* tosky sees jeremyfreudberg14:02
toskyoki, let's go14:03
tosky#startmeeting sahara14:03
openstackMeeting started Thu Oct 18 14:03:07 2018 UTC and is due to finish in 60 minutes.  The chair is tosky. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: sahara)"14:03
openstackThe meeting name has been set to 'sahara'14:03
jeremyfreudbergo/14:03
toskyTelles is on vacation, but still, good to check the status14:03
jeremyfreudbergindeed14:03
tosky#topic News/Updates14:04
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:04
toskyI've been working on S3 testing (still, I know, but now there is more working code)14:04
*** hongbin has joined #openstack-meeting-314:05
jeremyfreudbergi have not had any quality time to work on features recently (unlike last cycle, the features are a bit more complicated). very slowly making progress on health repair (which I have a small discussion point about)14:05
toskyapart from that, I've been following the status of the gates and discussed with -infra and -releases about few issues and changes14:05
jeremyfreudbergthanks tosky for holding down the fort, both on the openstack-wide stuff and also on those big patches like s3 testing, doc refactor, etc14:06
toskyin the doc refactor one, at some point I had too many windows open with code floating14:06
toskybut yeah :)14:06
*** slaweq has quit IRC14:06
toskylast time I spoke with Telles, the unit tests for the split repositories were passing and he was going to start the real testing14:07
*** slaweq has joined #openstack-meeting-314:07
toskyI'm writing an email about the planned impact on deployment tools and users14:08
jeremyfreudbergindeed, i've seen interesting stuff on telles's github14:08
jeremyfreudbergand yes, the email is a good idea14:09
toskywhen we are done with the split, apart from the bugs that can come from it, we can go full steam with API v2 and Python 314:09
toskywhich are the other big things14:09
jeremyfreudbergyup14:09
toskyI guess we are done with the news - any specific point to discuss? Until I'm out from the S3 pit, I don't have a lot more to add14:11
*** apetrich has quit IRC14:11
toskyoh, health repair14:12
toskylet's go for it, jeremyfreudberg14:12
jeremyfreudbergyes, health repair14:12
tosky#topic Health repair14:12
*** openstack changes topic to "Health repair (Meeting topic: sahara)"14:12
jeremyfreudbergso, i won't discuss every aspect of health repair, but there's one aspect that i've been grappling with recently14:13
jeremyfreudbergas you know (or not), the idea was to base health repair off of the existing health checks mechanism14:13
toskyI'm re-reading the minutes from the PTG14:14
jeremyfreudbergand in looking at that code, i'm surprised at how much database stuff are involved14:14
jeremyfreudbergand from what i can tell, the point of putting health checks in the DB is to make things stateful-- don't start a check when one is already in progress, etc. plus with the checks being (configurably) periodic the db kinda acts as a log14:15
jeremyfreudberganyway, my question for today is14:15
jeremyfreudbergis all that DB stuff really necessary for health repair?14:16
jeremyfreudbergmy sense is, kinda, but not totally14:16
toskydon't you see the same need for a synchronization point, so that the same operation don't start again?14:17
toskyor anyway, do you think it could be implemented differently?14:17
jeremyfreudbergshort answer- yes to both14:17
jeremyfreudberglong answer-14:17
*** apetrich has joined #openstack-meeting-314:20
jeremyfreudbergbecause health repair is thought to only be executed by user request (NOT periodic), the synchronization point is easier to pin down. AND, I planned to make the repair modes as idempotent and non-disruptive as possible, so theoretically i don't care if the repair call gets sent twice in quick succession14:20
jeremyfreudbergbut then again, some kind of locking mechanism seems intuitively necssary14:20
*** mjturek has joined #openstack-meeting-314:21
jeremyfreudbergnot to mention, if there is no lock, then the user could send way-too-many repair requests launching way-too-many subprocesses14:21
toskyyep, that's the risk14:21
tosky"why it's not working, repair, REPAAAAIR"14:22
toskyyeah14:22
jeremyfreudbergso, a lock of some kind is necessary, i'm just not convinced that tossing around db state is the right way to go about it14:22
jeremyfreudbergnot sure how else to do it, though14:22
toskymaybe minimizing the use of the DB may be enough14:22
jeremyfreudbergi'll see what i can trim out14:23
jeremyfreudbergi haven't done much of a deep dive yet14:24
toskyor we can have an hard-requirement on tooz (which is optional right now, used only for one functionality)14:24
jeremyfreudbergyes, there is tooz14:24
tosky... if we can make it working with python3, the better14:24
jeremyfreudberganother subtopic about health repair:14:24
jeremyfreudbergi wrote this on the story last night14:25
jeremyfreudbergthat there won't be a direct correspondence between all the existing health checks, and the new health repair modes14:25
jeremyfreudbergat least in the basic case14:25
toskyuh, what is the story? I didn't get the notification14:26
toskybut I should be subscribed to all sahara* notifications14:27
jeremyfreudbergthe description update doesn't seem to trigger the email14:27
jeremyfreudberghttps://storyboard.openstack.org/#!/story/200384214:27
toskyoh, ok14:27
jeremyfreudberglet me try to remember what i mean by my point, actually14:29
toskywhat would the main difference be then?14:29
toskyyeah, better14:29
*** mjturek has quit IRC14:31
jeremyfreudbergactually, i disagree now, with what i just said (not sure what i was thinking last night)14:31
jeremyfreudbergall of the health checks can have an inverse which is its repair mode14:31
jeremyfreudbergwith the exception of this check https://github.com/openstack/sahara/blob/master/sahara/service/health/health_check_base.py#L13314:31
*** sambetts|afk is now known as sambetts14:31
jeremyfreudbergoh, i think my point from last night was, health repair can eclipse health check14:36
jeremyfreudbergas in, we can write MORE health repair modes, beyond what limited checks we have14:36
jeremyfreudbergand my other point-- there is a minimal amount of work that needs to be done before the plugin split (the plugin-specific health repair modes need to be able to import the right stuff from core)14:37
toskyand then we will have more checks? If we have more repair modes, it means that we can check that something is really broken14:37
toskyuh, I didn't check if Telles also considered that14:37
jeremyfreudbergyes-- hopefully new repair modes will encourage new checks14:38
*** davidsha_ has joined #openstack-meeting-314:38
*** mjturek_ has joined #openstack-meeting-314:38
jeremyfreudbergregarding the split, i think it should only be one new import to cover14:39
*** TuanVu has joined #openstack-meeting-314:39
jeremyfreudbergthere would be a new module similar to sahara/service/health/health_check_base.py which has exceptions and the base class, for the plugin-specific repair modes to consume14:40
jeremyfreudbergactually, telles did something which i don't understand14:41
jeremyfreudberglooking at what he has on github (which may not be accurate), he simply moved health_check_base.py from sahara/service/health to sahara/plugins14:42
jeremyfreudbergbut he didn't change the imports within that file14:42
toskyuh14:43
jeremyfreudberghe did fix the import on the, for example, sahara-plugin-ambari side though14:44
jeremyfreudberganyway, i have to signoff in a minute14:44
toskyoki, I guess we discussed enough points14:44
jeremyfreudbergyes14:45
jeremyfreudbergi'll be sure to look further into health repair14:45
toskyTelles, when you read this, remember to recheck the rechecks14:45
toskythanks!14:45
toskyso if there is nothing else to discuss, we can close it here14:45
jeremyfreudbergyup, thanks, let's close14:45
toskysee you next week14:45
jeremyfreudbergbye14:46
*** jeremyfreudberg has quit IRC14:46
tosky(or even before, on the usual channel)14:46
tosky#endmeeting14:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:46
openstackMeeting ended Thu Oct 18 14:46:21 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2018/sahara.2018-10-18-14.03.html14:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2018/sahara.2018-10-18-14.03.txt14:46
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2018/sahara.2018-10-18-14.03.log.html14:46
*** Swami has joined #openstack-meeting-314:56
*** manjeets_ has joined #openstack-meeting-314:56
*** annp_ has quit IRC14:57
*** mlavalle has joined #openstack-meeting-315:00
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu Oct 18 15:00:37 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
manjeets_o/15:00
mlavalleo/15:00
haleybhi15:00
davidsha_o/15:00
mlavallehaleyb: go Sox. almost there15:01
*** Luzi has quit IRC15:01
haleybeven the bad calls have been going our way :)15:01
* haleyb is very tired this morning15:01
mlavalleis next game at Fainway?15:01
haleybno, tonight in houston15:01
mlavallegood luck15:02
Swamihi15:02
mlavalle#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
mlavalleJust a reminder that next week we reach Stein-115:02
njohnstono/15:02
mlavalleand the Summit in Berlin is three weeks away, November 13 - 1515:03
mlavalleany other annoucements?15:03
mlavalleok, let's move on15:04
mlavalle#topic Bugs15:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:04
mlavalleSwami: fire away15:04
Swamimlavalle: thanks, will do15:04
Swami#link https://bugs.launchpad.net/neutron/+bug/179499115:05
openstackLaunchpad bug 1794991 in neutron "Inconsistent flows with DVR l2pop VxLAN on br-tun" [Undecided,New]15:05
SwamiI was trying to reproduce this pike, but unfortunately I am not successful in reproducing this bug.15:05
SwamiWe have also internally seen such problems in newton.15:06
*** dklyle has joined #openstack-meeting-315:06
SwamiHas anyone else seen similar problems mentioned in this bug, where there is a race between the vxlan tunnel creation and the l2pop adding the flows for the vxlan.15:06
mlavalleno I haven't15:06
*** xubozhang has joined #openstack-meeting-315:07
mlavalleso, according to the bug report, what is the effect when it happens?15:07
Swamimlavalle: OK I will try couple of more tests to see if I can reproduce this. There is definitely a race.15:07
mlavalleThe reason I ask is that we have other bugs related to DVR15:08
SwamiWhen it happens the new VMs that come in on that compute cannot reach the DHCP server on the network node and also VM to VM communication will be blocked.15:08
Swamimlavalle: So just to refresh, the vxlan tunnels are created when the agent first registers with the neutron-server right?15:08
SwamiIs there a possibility that the vxlan tunnel interfaces might change down the line.15:09
mlavalleyes, that should be it15:09
mlavalleand no, I don't think so15:09
mlavalleThe reason I am asking is that I am debugging a couple of DVR related bugs15:09
Swamimlavalle: sure15:10
mlavalleI will keep this in mind as a possible cause for the bugs I am working on15:10
mlavalleIf we see this problem, it should be in the gate15:10
mlavallewhere we have concurrency15:10
Swamimlavalle: Yes basically you should have all the flows in place for the communication to be error free.15:10
Swamimlavalle: ok thanks15:10
mlavallemany of these races happen only with many concurrrent thinks happening15:11
Swamimlavalle:yes that's why reproducing it is a nightmare, unless we have the hardware resources and a script to trigger it.15:12
Swami#link https://bugs.launchpad.net/neutron/+bug/179352915:12
openstackLaunchpad bug 1793529 in neutron "[dvr][ha][dataplane down] router_gateway port binding host goes wrong after the 'master' host down/up" [Undecided,In progress] - Assigned to LIU Yulong (dragon889)15:12
mlavallenow, if the it hist DHCP, it seems to me that the problem goes beyond DVR, right?15:12
SwamiThere is a patch up for review. #link https://review.openstack.org/#/c/606384/15:12
*** e0ne has quit IRC15:12
Swamimlavalle: no the reason is there should be a flow rule in there with the MAC address of the dhcp server pointing to the right vxlan tunnel. Otherwise the dhcp request is not sent15:13
mlavalleah, that's right15:14
mlavalleok?15:14
mlavalleok15:14
Swamimlavalle: It is directly a problem with DHCP, but somehow when the l2pop populates the flows, it is either not populated properly when the VM on that network pops up or it is getting removed on restarts etc.,15:14
mlavalleack15:15
Swamis/it is directly/it is not directly15:15
Swamimlavalle: thanks15:15
SwamiIf you have not review this, please review this patch. #link https://review.openstack.org/#/c/606384/15:15
SwamiThe next one in the list is15:15
Swami#link https://bugs.launchpad.net/neutron/+bug/179649115:16
openstackLaunchpad bug 1796491 in neutron "DVR Floating IP setup in the SNAT namespace of the network node and also in the qrouter namespace in the compute node" [Medium,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:16
SwamiThere is a patch up for review. #link https://review.openstack.org/60992415:16
Swamihaleyb: liuyulong: thanks for your reviews on the patch.15:17
Swamihaleyb: I will address your comment, I think it is a minor one. So I hope this patch is in a good condition.15:17
haleybthanks15:17
*** e0ne has joined #openstack-meeting-315:18
SwamiThe next one is15:18
Swami#link https://bugs.launchpad.net/neutron/+bug/179682415:18
openstackLaunchpad bug 1796824 in neutron "Port in some type of device_owner should not allow update IP address" [Medium,In progress] - Assigned to LIU Yulong (dragon889)15:18
SwamiThere is a patch up for review #link https://review.openstack.org/#/c/608909/15:19
SwamiIf not review please review it.15:19
SwamiI think this bug #link https://bugs.launchpad.net/neutron/+bug/1785227 is a duplicate of the above one. So I am going to mark it as Duplicate.15:20
openstackLaunchpad bug 1785227 in neutron "Router port: no dataplane update on change" [Medium,Confirmed]15:20
SwamiDoes anyone have any concerns on this.15:20
mlavallego ahead15:20
Swamimlavalle: ok15:20
Swami#link https://bugs.launchpad.net/neutron/+bug/179703715:21
openstackLaunchpad bug 1797037 in neutron "Extra routes configured on routers are not set in the router namespace and snat namespace with DVR-HA routers" [Medium,In progress] - Assigned to Brian Haley (brian-haley)15:21
*** yamamoto has quit IRC15:21
Swami#link https://review.openstack.org/609273 - This patch fails zuul.15:21
*** yamamoto has joined #openstack-meeting-315:22
SwamiIt seems to be happy now, but let us see if it will merge.15:22
Swami#link https://bugs.launchpad.net/neutron/+bug/178627215:22
openstackLaunchpad bug 1786272 in neutron "Connection between two virtual routers does not work with DVR" [Medium,In progress] - Assigned to Slawek Kaplonski (slaweq)15:22
slaweqI just pushed new PS for this one: https://review.openstack.org/#/c/597567/2715:23
Swami#link https://review.openstack.org/#/c/597567/15:23
slaweqliuyulong is doing great review and testing manually different scenarios on this patch15:23
Swamislaweq: yes just noticed.  I will review it. I hope everything is fine with this patch. But liuyulong had some questions still.15:23
slaweqI hope that now it will be fine15:23
Swamislaweq: Ok thanks.15:24
slaweqSwami: if You can, please try it also on Your env - it's really tricky patch IMO and I don't want to break something :)15:24
liuyulongI'm testing this locally too.15:24
Swamislaweq: Yes I will do one more round of testing today.15:24
slaweqYou have much more experience with dvr than me15:24
*** jamesmcarthur has joined #openstack-meeting-315:24
slaweqthx liuyulong and Swami15:24
Swamislaweq:I also wanted to test the shared-network scenario with this patch between two tenants. Let me do it.15:25
slaweqSwami: ok15:25
slaweqthx15:25
haleybthanks everyone, at PS27 this has taken a long time but it's good work :)15:25
Swamihaleyb: Yep it is a complex one.15:26
slaweqyes, it is15:26
SwamiThe next one is15:26
*** yamamoto has quit IRC15:26
Swami#link https://bugs.launchpad.net/neutron/+bug/177445915:26
openstackLaunchpad bug 1774459 in neutron "Update permanent ARP entries for allowed_address_pair IPs in DVR Routers" [High,Confirmed] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:26
Swamimlavalle: haleyb: can you take a look at this patch . #link https://review.openstack.org/60133615:27
mlavalleSwami: yes, I promised last week to take a look and couldn't find the time. sorry15:27
SwamiThis is just a WIP based on our conversation at the PTG, but I am waiting for your inputs on this. I have a question. I also mentioned it in the last meeting.15:27
mlavalleI'll try again this week15:27
Swamimlavalle: thanks15:27
haleybi'll try to look by tomorrow too15:28
Swamimlavalle: haleyb : thank you15:28
Swamimlavalle: that's all I have for today.15:28
Swamimlavalle: Back to you.15:28
mlavalleI want to mention two bugs15:29
mlavalleFirst one is https://bugs.launchpad.net/neutron/+bug/179587015:29
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)15:29
mlavalleit was reported as a trunk failure (it is a trunk test failure)15:29
mlavallehowever, based on the debugging I've done so far, it seems to be a DVR problem15:30
mlavalleI left debugging notes a couple of days ago15:30
mlavalleso for the time being I'm adding it to the DVR backlog15:30
mlavalleand I'l, continue debugging15:30
Swamimlavalle: thanks15:31
mlavallethe problem really occurs when trying to ssh to a test instance using a floating ip15:31
*** xubozhang has quit IRC15:32
mlavallethe second bug is https://bugs.launchpad.net/neutron/+bug/178791915:33
openstackLaunchpad bug 1787919 in neutron "Upgrade router to L3 HA broke IPv6" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)15:33
mlavalleAt this point I have a deployment reproducing the conditions and am testing15:33
mlavalleI'll keep pushing forward with this one as well15:33
mlavallefinally, we have https://bugs.launchpad.net/neutron/+bug/178943415:34
openstackLaunchpad bug 1789434 in neutron "neutron_tempest_plugin.scenario.test_migration.NetworkMigrationFromHA failing 100% times" [High,Confirmed] - Assigned to Manjeet Singh Bhatia (manjeet-s-bhatia)15:34
manjeets_https://review.openstack.org/#/c/611461/15:34
manjeets_I posted a solution ideally notification part should be in l3_hamodedb code15:34
manjeets_Please reviews it if solution is okay I’ll update and add tests15:35
Swamimanjeets_: Yes i did a first pass on it yesterday15:36
manjeets_Thanks swami totally agree to your comments15:36
manjeets_I’ll revise it today15:37
Swamimanjeets_: thanks15:38
*** xubozhang has joined #openstack-meeting-315:38
mlavallemanjeets_: I will also look at it soon15:38
mlavalleany other bugs we should discuss today?15:40
mlavalleok, moving on15:42
mlavalle#topic On demand agenda15:42
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_l3)"15:42
davidsha_mlavalle, Thank you for looking at the agent refactor, We're working through it atm to make sure the tests are right.15:43
mlavalledavidsha_: last evening I left Xubo some guidnace as to how to debug the failures15:43
davidsha_It's mostly mocks pointing to the wrong objects atm.15:43
mlavalleyeah, I know. I just didn't want to fix it for him15:43
mlavalleI wanted to have him work through the process15:44
mlavalleit's part of my job to help new devs15:44
*** tssurya has quit IRC15:44
davidsha_kk, We're having calls as well so I'll try to keep things moving!15:45
mlavalletell him that if he has questions or needs guidance, he can leave a comment in the patch and I'll follow up15:45
*** liuyulong has quit IRC15:46
mlavalleany other topics to discuss?15:46
*** liuyulong has joined #openstack-meeting-315:46
mlavalleok, thanks for attending15:46
davidsha_cool, think he's online if you have any questions15:47
davidsha_thanks!15:47
mlavallehave a great weekend!15:47
*** xubozhang has quit IRC15:47
mlavallehaleyb: go finish those Astros off tonight!15:47
mlavalle#endmeeting15:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:47
openstackMeeting ended Thu Oct 18 15:47:34 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2018/neutron_l3.2018-10-18-15.00.html15:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2018/neutron_l3.2018-10-18-15.00.txt15:47
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2018/neutron_l3.2018-10-18-15.00.log.html15:47
*** manjeets_ has quit IRC15:47
davidsha_talk to ye15:47
haleybmlavalle: will do :)15:47
*** mjturek_ has quit IRC15:49
*** tosky has left #openstack-meeting-315:50
*** macza has joined #openstack-meeting-315:56
*** e0ne has quit IRC16:00
*** davidsha_ has quit IRC16:06
*** yamamoto has joined #openstack-meeting-316:11
*** liuyulong is now known as liuyulong_zzz16:13
*** jamesmcarthur has quit IRC16:15
*** dklyle has quit IRC16:16
*** dklyle has joined #openstack-meeting-316:16
*** Swami has quit IRC16:21
*** manjeets has joined #openstack-meeting-316:28
*** jamesmcarthur has joined #openstack-meeting-316:30
*** macza has quit IRC16:33
*** dklyle has quit IRC16:37
*** yamamoto has quit IRC16:56
*** yamamoto has joined #openstack-meeting-316:56
*** yamahata has joined #openstack-meeting-317:04
*** sambetts is now known as sambetts|afk17:07
*** munimeha1 has quit IRC17:10
*** mjturek has joined #openstack-meeting-317:16
*** dklyle has joined #openstack-meeting-317:30
*** yamamoto has quit IRC17:33
*** dklyle has quit IRC17:42
*** diablo_rojo has joined #openstack-meeting-317:44
*** dklyle has joined #openstack-meeting-317:50
*** dklyle has quit IRC18:02
*** jamesmcarthur has quit IRC18:09
*** apetrich has quit IRC18:10
*** diablo_rojo has quit IRC18:12
*** diablo_rojo has joined #openstack-meeting-318:13
*** yamamoto has joined #openstack-meeting-318:14
*** dklyle has joined #openstack-meeting-318:20
*** apetrich has joined #openstack-meeting-318:24
*** diablo_rojo has quit IRC18:26
*** dklyle has quit IRC18:29
*** mjturek has quit IRC18:35
*** jamesmcarthur has joined #openstack-meeting-318:37
*** jamesmcarthur has quit IRC18:43
*** caboucha has joined #openstack-meeting-318:43
*** diablo_rojo has joined #openstack-meeting-318:44
*** mjturek has joined #openstack-meeting-318:53
*** dklyle has joined #openstack-meeting-319:07
*** jamesmcarthur has joined #openstack-meeting-319:12
*** dklyle has quit IRC19:14
*** jamesmcarthur has quit IRC19:16
*** bobh has quit IRC19:17
*** diablo_rojo has quit IRC19:35
*** mlavalle has left #openstack-meeting-319:37
*** apetrich has quit IRC19:44
*** e0ne has joined #openstack-meeting-319:52
*** e0ne has quit IRC20:05
*** mjturek has quit IRC20:38
*** pcaruana has quit IRC20:44
*** raildo has quit IRC21:09
*** diablo_rojo has joined #openstack-meeting-321:12
*** bnemec is now known as bnemec-bbl21:20
*** dklyle has joined #openstack-meeting-321:36
*** diablo_rojo has quit IRC21:42
*** diablo_rojo has joined #openstack-meeting-321:44
*** dklyle has quit IRC21:45
*** jamesmcarthur has joined #openstack-meeting-321:55
*** jamesmcarthur has quit IRC21:59
*** pbourke has quit IRC22:35
*** pbourke has joined #openstack-meeting-322:36
*** bobh has joined #openstack-meeting-322:37
*** bobh has quit IRC22:41
*** diablo_rojo has quit IRC22:52
*** diablo_rojo has joined #openstack-meeting-323:03
*** hongbin has quit IRC23:08
*** mjturek has joined #openstack-meeting-323:17
*** jamesmcarthur has joined #openstack-meeting-323:36
*** diablo_rojo has quit IRC23:37
*** jamesmcarthur has quit IRC23:39
*** jamesmcarthur has joined #openstack-meeting-323:39
*** mjturek has quit IRC23:42
*** bnemec has joined #openstack-meeting-323:50
*** bnemec-bbl has quit IRC23:52
*** jamesmcarthur has quit IRC23:55
*** jamesmcarthur has joined #openstack-meeting-323:58

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