Thursday, 2017-09-07

*** Swami has quit IRC00:29
*** sdague has quit IRC00:36
*** slaweq has joined #openstack-meeting-300:39
*** wanghao_ has quit IRC00:43
*** slaweq has quit IRC00:44
*** harlowja has quit IRC00:48
*** wanghao has joined #openstack-meeting-300:49
*** annabelleB has joined #openstack-meeting-300:54
*** dixiaoli has joined #openstack-meeting-300:57
*** baoli has joined #openstack-meeting-301:03
*** zhurong has joined #openstack-meeting-301:15
*** bobh has joined #openstack-meeting-301:18
*** bobh has quit IRC01:33
*** shuyingya has joined #openstack-meeting-301:36
*** krtaylor has joined #openstack-meeting-301:39
*** slaweq has joined #openstack-meeting-301:40
*** bobmel has joined #openstack-meeting-301:42
*** slaweq has quit IRC01:45
*** bobmel has quit IRC01:47
*** shuyingy_ has joined #openstack-meeting-301:55
*** shuyingya has quit IRC01:56
*** bobh has joined #openstack-meeting-301:56
*** trungnv has joined #openstack-meeting-301:58
*** trungnv has quit IRC02:04
*** yamamoto_ has joined #openstack-meeting-302:09
*** markvoelker has quit IRC02:11
*** gary-smith_ has quit IRC02:11
*** yamahata has quit IRC02:15
*** iyamahat has quit IRC02:15
*** bobh has quit IRC02:15
*** trungnv has joined #openstack-meeting-302:19
*** shu-mutou-AWAY is now known as shu-mutou02:37
*** trungnv has quit IRC02:38
*** slaweq has joined #openstack-meeting-302:41
*** slaweq has quit IRC02:46
*** baoli has quit IRC02:50
*** annabelleB has quit IRC02:50
*** baoli has joined #openstack-meeting-302:50
*** baoli has quit IRC03:01
*** rossella_s has quit IRC03:08
*** rossella_s has joined #openstack-meeting-303:09
*** iurygregory has quit IRC03:10
*** iurygregory has joined #openstack-meeting-303:10
*** markvoelker has joined #openstack-meeting-303:11
*** TuanLA has joined #openstack-meeting-303:17
*** coolsvap has joined #openstack-meeting-303:19
*** trungnv has joined #openstack-meeting-303:32
*** slaweq has joined #openstack-meeting-303:42
*** markvoelker has quit IRC03:46
*** slaweq has quit IRC03:47
*** cshastri has joined #openstack-meeting-303:54
*** rossella_s has quit IRC04:04
*** rossella_s has joined #openstack-meeting-304:05
*** anilvenkata has joined #openstack-meeting-304:05
*** harlowja has joined #openstack-meeting-304:06
*** trungnv has quit IRC04:07
*** bobmel has joined #openstack-meeting-304:09
*** bobmel has quit IRC04:14
*** ianychoi_ has joined #openstack-meeting-304:18
*** calbers has quit IRC04:19
*** yamamot__ has joined #openstack-meeting-304:20
*** spotz has quit IRC04:20
*** mfranc213 has quit IRC04:20
*** edleafe has quit IRC04:20
*** ianychoi has quit IRC04:21
*** cinerama has quit IRC04:21
*** cinerama has joined #openstack-meeting-304:21
*** calbers has joined #openstack-meeting-304:21
*** mfranc213 has joined #openstack-meeting-304:21
*** yamamoto_ has quit IRC04:21
*** julim has quit IRC04:21
*** edleafe has joined #openstack-meeting-304:21
*** kei-ichi has quit IRC04:21
*** kevinbenton has quit IRC04:21
*** spotz has joined #openstack-meeting-304:22
*** julim_ has joined #openstack-meeting-304:22
*** kevinbenton has joined #openstack-meeting-304:23
*** kei-ichi has joined #openstack-meeting-304:23
*** iurygregory has quit IRC04:30
*** gouthamr has quit IRC04:31
*** iurygregory has joined #openstack-meeting-304:36
*** zhurong has quit IRC04:38
*** dims has quit IRC04:40
*** shuyingy_ has quit IRC04:41
*** rakhmerov has quit IRC04:43
*** markvoelker has joined #openstack-meeting-304:43
*** flwang has quit IRC04:44
*** rakhmerov has joined #openstack-meeting-304:44
*** shuyingya has joined #openstack-meeting-304:46
*** rmcall has quit IRC04:48
*** psachin has joined #openstack-meeting-304:51
*** rmcall has joined #openstack-meeting-304:51
*** reed_ has joined #openstack-meeting-304:52
*** reed_ has quit IRC04:54
*** flwang has joined #openstack-meeting-304:55
*** pgadiya has joined #openstack-meeting-305:01
*** yamamot__ has quit IRC05:07
*** yamamoto_ has joined #openstack-meeting-305:07
*** zhurong has joined #openstack-meeting-305:08
*** harlowja has quit IRC05:11
*** pcaruana has joined #openstack-meeting-305:15
*** markvoelker has quit IRC05:16
*** iyamahat has joined #openstack-meeting-305:18
*** iyamahat_ has joined #openstack-meeting-305:19
*** iyamahat has quit IRC05:21
*** marios has joined #openstack-meeting-305:23
*** anilvenkata has quit IRC05:39
*** slaweq has joined #openstack-meeting-305:44
*** diablo_rojo has joined #openstack-meeting-305:48
*** slaweq has quit IRC05:49
*** marios has quit IRC05:53
*** marios has joined #openstack-meeting-305:55
*** marios has quit IRC06:00
*** iyamahat_ has quit IRC06:02
*** marios has joined #openstack-meeting-306:02
*** rossella_s has quit IRC06:04
*** rossella_s has joined #openstack-meeting-306:06
*** diablo_rojo has quit IRC06:11
*** egallen_ has joined #openstack-meeting-306:12
*** rossella_s has quit IRC06:12
*** markvoelker has joined #openstack-meeting-306:13
*** egallen has quit IRC06:14
*** egallen_ is now known as egallen06:14
*** rossella_s has joined #openstack-meeting-306:14
*** TuanLA has quit IRC06:19
*** TuanLA has joined #openstack-meeting-306:19
*** egallen has quit IRC06:20
*** ccamacho has joined #openstack-meeting-306:24
*** iyamahat has joined #openstack-meeting-306:26
*** egallen has joined #openstack-meeting-306:27
*** zshi_ has joined #openstack-meeting-306:27
*** egallen has quit IRC06:28
*** marios has quit IRC06:37
*** zshi_ has quit IRC06:41
*** slaweq has joined #openstack-meeting-306:45
*** zshi_ has joined #openstack-meeting-306:46
*** markvoelker has quit IRC06:47
*** slaweq has quit IRC06:50
*** slaweq has joined #openstack-meeting-307:11
*** ianychoi_ is now known as ianychoi07:12
*** slaweq has quit IRC07:16
*** flwang has quit IRC07:20
*** rossella_s has quit IRC07:28
*** rossella_s has joined #openstack-meeting-307:32
*** flwang has joined #openstack-meeting-307:40
*** iyamahat has quit IRC07:41
*** markvoelker has joined #openstack-meeting-307:44
*** bobmel has joined #openstack-meeting-307:46
*** ralonsoh has joined #openstack-meeting-307:49
*** marios has joined #openstack-meeting-307:49
*** trungnv has joined #openstack-meeting-308:02
*** rossella_s has quit IRC08:02
*** rossella_s has joined #openstack-meeting-308:05
*** rossella_s has quit IRC08:10
*** slaweq has joined #openstack-meeting-308:12
*** rossella_s has joined #openstack-meeting-308:13
*** slaweq has quit IRC08:17
*** markvoelker has quit IRC08:17
*** rmart04 has joined #openstack-meeting-308:31
*** rmcall has quit IRC08:33
*** rmcall has joined #openstack-meeting-308:33
*** rmcall has quit IRC08:34
*** shu-mutou is now known as shu-mutou-AWAY08:42
*** rossella_s has quit IRC08:44
*** rossella_s has joined #openstack-meeting-308:47
*** egallen has joined #openstack-meeting-308:59
*** rossella_s has quit IRC09:08
*** rossella_s has joined #openstack-meeting-309:10
*** slaweq has joined #openstack-meeting-309:13
*** markvoelker has joined #openstack-meeting-309:14
*** stendulker has joined #openstack-meeting-309:16
*** slaweq has quit IRC09:18
*** egallen has quit IRC09:18
*** egallen has joined #openstack-meeting-309:19
*** yamahata has joined #openstack-meeting-309:22
*** egallen has quit IRC09:23
*** sambetts|afk is now known as sambetts09:24
*** marios has quit IRC09:27
*** marios has joined #openstack-meeting-309:28
*** yamamoto_ has quit IRC09:28
*** cshastri has quit IRC09:37
*** psachin has quit IRC09:43
*** yamamoto has joined #openstack-meeting-309:46
*** markvoelker has quit IRC09:48
*** anilvenkata has joined #openstack-meeting-309:49
*** chyka has joined #openstack-meeting-309:51
*** rossella_s has quit IRC09:56
*** chyka has quit IRC09:56
*** cshastri has joined #openstack-meeting-309:57
*** rossella_s has joined #openstack-meeting-309:59
*** TuanLA has quit IRC10:07
*** slaweq has joined #openstack-meeting-310:14
*** yamamoto has quit IRC10:14
*** yamamoto has joined #openstack-meeting-310:19
*** slaweq has quit IRC10:19
*** zhurong has quit IRC10:23
*** egallen has joined #openstack-meeting-310:30
*** markvoelker has joined #openstack-meeting-310:45
*** rossella_s has quit IRC10:52
*** rossella_s has joined #openstack-meeting-310:52
*** reedip is now known as reed_afk10:53
*** reed_afk is now known as reedip_afk10:53
*** egallen has quit IRC11:05
*** ccamacho has quit IRC11:06
*** sdague has joined #openstack-meeting-311:06
*** cshastri has quit IRC11:07
*** zshi_ has quit IRC11:07
*** slaweq has joined #openstack-meeting-311:15
*** psachin has joined #openstack-meeting-311:16
*** markvoelker has quit IRC11:17
*** jjung has joined #openstack-meeting-311:20
*** zhurong has joined #openstack-meeting-311:20
*** slaweq has quit IRC11:20
*** cshastri has joined #openstack-meeting-311:22
*** stendulker_ has joined #openstack-meeting-311:26
*** MarkBaker has joined #openstack-meeting-311:28
*** stendulker has quit IRC11:29
*** stendulker_ has quit IRC11:31
*** pbourke has quit IRC11:34
*** pbourke has joined #openstack-meeting-311:36
*** srobert has joined #openstack-meeting-311:41
*** srobert has quit IRC11:42
*** srobert has joined #openstack-meeting-311:42
*** dixiaoli has quit IRC11:45
*** lpetrut has joined #openstack-meeting-311:46
*** lpetrut has quit IRC11:46
*** julim_ has quit IRC11:46
*** raildo has joined #openstack-meeting-311:55
*** pgadiya has quit IRC12:06
*** dims has joined #openstack-meeting-312:07
*** markvoelker has joined #openstack-meeting-312:15
*** egallen has joined #openstack-meeting-312:15
*** slaweq has joined #openstack-meeting-312:16
*** slaweq has quit IRC12:21
*** markvoelker has quit IRC12:24
*** markvoelker has joined #openstack-meeting-312:24
*** zhurong has quit IRC12:25
*** zshi_ has joined #openstack-meeting-312:30
*** ccamacho has joined #openstack-meeting-312:39
*** shuyingya has quit IRC12:43
*** egallen_ has joined #openstack-meeting-312:49
*** egallen has quit IRC12:52
*** egallen_ is now known as egallen12:52
*** lyan has joined #openstack-meeting-312:57
*** cshastri has quit IRC12:57
*** baoli has joined #openstack-meeting-313:02
*** raildo has quit IRC13:02
*** baojg has joined #openstack-meeting-313:02
*** raildo has joined #openstack-meeting-313:03
*** MarkBaker has quit IRC13:06
*** donghao has joined #openstack-meeting-313:08
*** iyamahat has joined #openstack-meeting-313:08
*** shuyingya has joined #openstack-meeting-313:12
*** shuyingya has quit IRC13:17
*** slaweq has joined #openstack-meeting-313:17
*** MarkBaker has joined #openstack-meeting-313:19
*** rossella_s has quit IRC13:19
*** jjung has quit IRC13:20
*** raildo has quit IRC13:20
*** julim has joined #openstack-meeting-313:20
*** jjung has joined #openstack-meeting-313:21
*** slaweq has quit IRC13:22
*** rossella_s has joined #openstack-meeting-313:23
*** jjung has quit IRC13:25
*** gouthamr has joined #openstack-meeting-313:30
*** janzian has joined #openstack-meeting-313:30
*** raildo has joined #openstack-meeting-313:31
*** slaweq has joined #openstack-meeting-313:33
*** slaweq has quit IRC13:33
*** raildo has quit IRC13:35
*** raildo has joined #openstack-meeting-313:36
*** f13o has joined #openstack-meeting-313:42
*** f13o has quit IRC13:42
*** shuyingya has joined #openstack-meeting-313:53
*** bobh has joined #openstack-meeting-313:53
*** coolsvap has quit IRC13:57
*** annabelleB has joined #openstack-meeting-313:59
tellesnobrega#startmeeting sahara14:00
openstackMeeting started Thu Sep  7 14:00:30 2017 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. 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: sahara)"14:00
openstackThe meeting name has been set to 'sahara'14:00
tellesnobregaI'm not sure we will have quorum for today's meeting, so I'm giving a couple minutes, if people don't show up I'm ending early14:01
*** tosky has joined #openstack-meeting-314:01
shuyingyao/14:01
toskyo/14:01
tellesnobregagood, we have people :)14:02
*** davidsha has joined #openstack-meeting-314:02
*** egallen_ has joined #openstack-meeting-314:02
tellesnobrega#topic News/Updates14:02
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:02
tellesnobregaI'm currently just finishing up prep for PTG, not much upstream work going on14:03
tellesnobregathis is one of the community goals for Queens14:04
shuyingyamost of time working on down stream task. and still investigate bug 171301214:04
openstackbug 1713012 in Sahara "renamed cluster fail to scale" [Undecided,New] https://launchpad.net/bugs/1713012 - Assigned to Shu Yingya (felixshu)14:04
tellesnobrega#link https://review.openstack.org/#/c/501415/14:04
*** egallen has quit IRC14:04
*** egallen_ is now known as egallen14:04
toskyshuyingya: I was going to ask why you moved it to Invalid, but I see that you reopened it14:05
toskynot many updates, I'm in "general testing mode" (aka: deploy with tripleo and test)14:05
tellesnobregashuyingya, I don't know if jeremy had a chance to test that yet14:05
tellesnobregaI will ping him later about it14:06
shuyingyayes, it works on scale up, but it will fail when scale down :(14:06
shuyingyatellesnobrega, you can take a look at what I commented under the bug14:06
tellesnobregaI will14:06
tellesnobrega#action tellesnobrega to take a second round of testing on bug #171301214:07
openstackbug 1713012 in Sahara "renamed cluster fail to scale" [Undecided,New] https://launchpad.net/bugs/1713012 - Assigned to Shu Yingya (felixshu)14:07
tellesnobregalets move on14:09
tellesnobrega#topic queens PTG14:09
*** openstack changes topic to "queens PTG (Meeting topic: sahara)"14:09
tellesnobregawe are all set for PTG, schedule is set and we should be all there starting on wednesday14:10
tellesnobreganot much else on that topic14:10
tellesnobregashuyingya, did you have a chance to look the topics?14:10
tellesnobregaif you want anything to be discussed that we missed please add there and we will do our best to accommodate it14:11
shuyingyawhich topic?14:11
tellesnobregafor ptg14:11
*** ccamacho has quit IRC14:11
shuyingyayou mean etherpad?14:11
tellesnobrega#link https://etherpad.openstack.org/p/sahara-queens-ptg14:11
tellesnobregayes14:11
shuyingyayep, I will14:11
tellesnobregathanks14:11
*** ttrifonov has quit IRC14:12
shuyingyayou are welcome14:12
shuyingyaand tellesnobrega, you have test sahara over baremetal, right?14:12
tellesnobregain a manner yes. I tried it using fake baremetal nodes (vms)14:13
*** ttrifonov has joined #openstack-meeting-314:13
tellesnobregabut yes14:13
shuyingyahave you taken some notes about it?14:13
shuyingyaor you follow nikita's notes?14:14
tellesnobregawhat kind of notes? how to do it?14:14
shuyingyajust the step to deploy cluster on baremetal14:14
tellesnobregaI didn't follow nikita's notes, but it was a fairly flow14:14
shuyingyaI want to try it and test the performance. But not sure the limitation.14:15
shuyingyaOK, maybe I will consult you if I got any problem :)14:15
tellesnobregaI can check nikita's notes (can you paste the link) and if needed I will update with my deployment process14:15
tellesnobregasure14:15
*** VW has joined #openstack-meeting-314:15
shuyingyathanks14:16
toskyand/or our documentation14:16
tellesnobregatosky, yeah14:16
shuyingya+114:16
tellesnobrega#topic Open Discussion14:17
*** openstack changes topic to "Open Discussion (Meeting topic: sahara)"14:17
tellesnobregai guess this should've been done earlier but lets see if we have any more discussion topics14:18
shuyingyaI have no other questions, and I will review the PTG  etherpad later or tomorrow.14:18
tellesnobregathanks shuyingya14:18
shuyingyatellesnobrega, If you test the scale down renamed cluster, please let me know14:18
tellesnobregashuyingya, I will do for sure14:18
*** baoli has quit IRC14:19
shuyingyauser_domain_name=Default14:19
shuyingyaproject_domain_name=Default14:19
*** marst has joined #openstack-meeting-314:19
shuyingyaAnd If it possible, can you investigate the RDO issue about the default value of user_domain_name14:19
*** baoli has joined #openstack-meeting-314:19
shuyingyaI am not familiar with this, and I have deployed RDO with packstack two times. The bug can reproduce 100%14:20
tellesnobregashuyingya, can't promise much at this point (traveling in 2 days)14:20
tellesnobregabut I will take a note to do it once I'm back14:21
shuyingyathanks, I will try to solve it this weekend :) but can't promise too14:21
tellesnobregagood14:22
*** srobert has quit IRC14:24
tellesnobregaanything else for today?14:24
toskynot from me14:24
shuyingyanot from me too14:25
shuyingyaand just now, I commented the step to reproduce the bug14:25
*** bobh has quit IRC14:25
tellesnobregashuyingya, thanks14:26
tellesnobregaI guess we can close early today and have 34 minutes back14:26
*** donghao has quit IRC14:26
tellesnobregathanks tosky and shuyingya for being here and next week we won't be having irc meeting14:26
shuyingyaso happy vacation tellesnobrega14:26
tosky"vacation" :D14:26
tellesnobrega"vacation" is the right way to phrase it14:27
tellesnobregathanks all14:27
shuyingyabye14:27
toskyo/14:27
tellesnobrega#endmeeting14:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:27
openstackMeeting ended Thu Sep  7 14:27:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-09-07-14.00.html14:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-09-07-14.00.txt14:27
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-09-07-14.00.log.html14:27
*** galstrom_zzz is now known as galstrom14:27
*** tosky has left #openstack-meeting-314:28
*** slaweq has joined #openstack-meeting-314:34
*** skelso has joined #openstack-meeting-314:35
*** lucasxu has joined #openstack-meeting-314:36
*** slaweq has quit IRC14:39
*** lucasxu has quit IRC14:41
*** hongbin has joined #openstack-meeting-314:42
*** anilvenkata is now known as anilvenkata|AFK14:45
*** cleong has joined #openstack-meeting-314:46
*** zshi_ has quit IRC14:49
*** Swami has joined #openstack-meeting-314:50
*** skelso has quit IRC14:53
*** rossella_s has quit IRC14:56
*** skelso has joined #openstack-meeting-314:57
*** rossella_s has joined #openstack-meeting-314:58
*** flwang has quit IRC14:59
*** mlavalle has joined #openstack-meeting-315:00
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu Sep  7 15:00:46 2017 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
Swamihi15:00
davidshaHi15:01
haleybhi15:01
mlavalle#chair Swami haleyb davidsha15:01
openstackCurrent chairs: Swami davidsha haleyb mlavalle15:01
mlavalleNice to see you team :-)15:01
mlavalle#topic Annoucements15:01
*** openstack changes topic to "Annoucements (Meeting topic: neutron_l3)"15:01
*** flwang has joined #openstack-meeting-315:01
mlavalleNext week PTG in Denver. Looking forward to see y'all there15:02
mlavalle:)15:02
mlavalleAlso, I wanted to draw the team's attention to the Queens release schedule:15:03
Swamimlavalle: do we have an agenda for the PTG neutron team.15:03
davidshaSwami: Etherpad was updated15:03
mlavalle#link https://releases.openstack.org/queens/schedule.html15:03
Swamidavidsha: thanks.15:03
davidshaSwami: https://etherpad.openstack.org/p/neutron-queens-ptg15:04
mlavalleNext milestone will be Queens 1 October 20 - 2615:04
mlavalleSwami: Yes, I worked with kevinbenton yesterday afternoong in an agenda15:04
Swamimlavalle: good to know15:04
davidshamlavalle: you mean 16th-20th?15:05
mlavalleessentially we swept all the topics that folks put in the etherpad and distributed them in sessions across Wednesday through Friday15:05
mlavalleWednesday and Friday are Neutron days15:06
mlavalleand Friday will let small interest groups to gather around stadium projects15:06
mlavallemakes sense?15:07
Swamimlavalle: thanks for the information.15:07
davidshaWill there be some way to dial in?15:07
davidshaI'd seen it discussed just not sure what the conclusion is.15:07
mlavalleI also heard yesterday that the Cinder team is trying to enable a hangout that creates you tube video15:08
mlavalleso I'll reach out to them to see if we can do the same thing for Neutron15:08
davidshaThanks!15:08
mlavallethat way folks can attend virtualy on their own time15:09
Swamimlavalle: yes that would work for people who are not able to attend in person.15:10
mlavalleFinally, I wanted to remind folks that the Sydney Summit is fast approaching, November 6 - 815:10
mlavalleYou are probably going to need a visa if you plan to attend15:11
Swamimlavalle: I got my approval yesterday and will start my visa process.15:11
mlavalleFor US passport holders (and many other nationalitites) it's just a matter of applying on line and paying about $15 US. Yu get the visa in 5 minutes15:11
mlavalleeverything on line15:12
Swamimlavalle: yeah that should be faster.15:13
mlavalleLast two announcements: we will have a Neutron social event in Denver Thursday night. Hopefully all of you will be there15:13
mlavalleand the very last one: carl_baldwin said to me a few weeks ago that he wants to join as many as possible of us for dinner on Monday or Tuesday15:13
mlavalleI am pinging him today to firm up the day15:14
mlavalleI'll keep you posted15:14
mlavalleAny other announcements?15:15
Swamimlavalle: nothing from me.15:15
*** rmart04 has quit IRC15:15
mlavalleok moving on15:16
mlavalle#topic Bugs15:16
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:16
*** iyamahat has quit IRC15:16
mlavalleas usual, Swami plase fire away15:16
Swamimlavalle: thanks15:16
SwamiFor DVR we have a critical bug and work is in progress.15:16
SwamiWe have two patches so far pushed in for review for this bug.15:16
*** MarkBaker has quit IRC15:17
Swami#link https://bugs.launchpad.net/neutron/+bug/171392715:17
openstackLaunchpad bug 1713927 in neutron "gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial fails constantly" [Critical,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:17
SwamiThe agent side patch is to prevent agent processing a fip that does not have a host key.15:17
Swami#link https://review.openstack.org/#/c/499725/15:18
SwamiThis patch has already been reviewed and had a workflow, but the gate is failing jenkins. I have applied a recheck on it.15:18
*** annabelleB has quit IRC15:18
SwamiThe server side patch is here #link https://review.openstack.org/#/c/499859/15:19
haleybSwami: i also updated https://review.openstack.org/#/c/500143/ - should work the same as yours, was using it for debugging here15:19
SwamiI did some testing with this patch, but I found that the multinode grenade job is still failing. I need to look at the logs, to see if this is due to the current change or something else.15:19
mlavalleso these last two patchsets do the same thing?15:20
haleybmlavalle: well, they should in theory15:20
Swamihaleyb: thanks.15:20
mlavallebut we are merging only one of them, right?15:20
haleybthe goal when the agent and server patch are merged is the multinode job should be passing15:21
Swamihaleyb: mlavalle: I will take a look at the logs again today and see why it fails in tempest 'Networkscenario' tests.15:21
haleybmlavalle: yes, since it was a hot topic we were both looking at failure cases15:21
*** shuyingya has quit IRC15:21
Swamihaleyb: We are not sure there are some other traces also seen in the multinode job.15:21
haleybSwami: we will need to look, there shouldn't be any traces from our changes15:22
Swamihaleyb: Not from our traces. But it is not related to our change.15:23
Swamihaleyb: I see an error on 'Segment' and some 'StaleDataError' produced by DB updates.15:23
haleybi was seeing other failures yesterday unrelated to neutron, was hoping a recent devstack-gate fix would have helped15:23
haleybSwami: we should check if there's an existing bug for that15:23
Swamihaleyb: Sure will do.15:24
Swamihaleyb: mlavalle: Also a general question, I have issues with running the tempest service with devstack. It fails with 'flake' issue. Have anyone seen this.15:24
*** gmann has quit IRC15:24
mlavalleNo, I haven't15:24
*** gmann has joined #openstack-meeting-315:24
haleybi haven't seen that either15:25
SwamiI am having it for a while, ok I will check it out later.15:25
SwamiLet us move on to the next bugs.15:25
mlavalleI have a question15:25
*** annabelleB has joined #openstack-meeting-315:25
Swamimlavalle: yes15:26
*** bobh has joined #openstack-meeting-315:26
mlavalledo we need to wait for the approved patchsetto merge before we push either of the other two?15:26
mlavalleI just don't want to do something stupid trying to help :-)15:26
haleybmlavalle: i did tell ihar i would be careful :)15:27
haleybkevin pushed the agent patch, which failed the gate anyways15:27
Swamimlavalle: what are the approved patches.15:27
mlavallehttps://review.openstack.org/#/c/49972515:28
Swamihaleyb: Theoretically this is an agent side patch and can merge without any issues, but as haleyb pointed out it is currently failing merge in gate. Not sure what is going on.15:29
haleybmlavalle: i was going to wait until today to let you look at that, it's a temp fix until we can get the server code working better15:30
Swamiagreed15:31
SwamiLet us move on.15:31
*** bobmel has quit IRC15:31
haleybSwami: we shouldn't technically need that once we fix the server, but I guess i'd rather have the agent check as well15:31
SwamiThe next bug in the list is15:31
*** bobh has quit IRC15:31
Swamihaleyb: yes I dont' want to remove it for now. This code path will be hit, only when the server misbehaves. So let us leave it for now.15:31
haleybright15:32
Swami#link https://bugs.launchpad.net/neutron/+bug/171425115:32
openstackLaunchpad bug 1714251 in neutron "router_centralized_snat not removed when router migrated from DVR to HA" [Undecided,In progress] - Assigned to venkata anil (anil-venkata)15:32
*** bobmel has joined #openstack-meeting-315:32
SwamiThis bug is related to the csnat port not getting cleared after router migration. This is also seen tempest testing occassionally.15:32
Swamianilvenkata has pushed in a patch for review.15:33
Swami#link https://review.openstack.org/#/c/501717/15:33
SwamiThis patch needs review.15:33
mlavallecan we review and merge regardless of the other work you and haleyb are doing?15:33
SwamiRight now jenkins is not happy with this patch.15:34
* mlavalle is suffering a mild case of PTSD15:34
Swamimlavalle: Sure if there is any patch on our codepath we will let you know. The work we are doing is on the full sync path.15:34
mlavalleok15:34
haleybmlavalle: yes, there are a few migration fixes that can merge when good, the server one we need to triple-check15:34
davidshajli15:34
*** slaweq has joined #openstack-meeting-315:35
*** chyka has joined #openstack-meeting-315:35
SwamiThe next bug is #link https://bugs.launchpad.net/neutron/+bug/171479615:35
openstackLaunchpad bug 1714796 in neutron "Router interface not updated during DVR->HA, HA->DVR migratons" [Undecided,In progress] - Assigned to venkata anil (anil-venkata)15:35
SwamiThere is also a patch to address this issue.15:36
Swami#link https://review.openstack.org/50037915:36
SwamiThe bug states that the device_owner is not updated during the migration.15:36
SwamiI saw haleyb had already reviewed this patch.15:37
SwamiI will include it into my review list as well15:37
SwamiThe next bug is also related to migration with the combination of HA and DVR15:38
Swami#link https://bugs.launchpad.net/neutron/+bug/171480215:38
openstackLaunchpad bug 1714802 in neutron "DVR and HA migration tests failing intermittently for gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv job" [Undecided,In progress] - Assigned to Brian Haley (brian-haley)15:38
Swamianilvenkata has done some work on triaging all these bugs.15:38
SwamiHe also have a patch for it for review.15:38
Swami#link https://review.openstack.org/50038415:39
SwamiNeed reviews on these patches.15:39
haleybthe plan is to probably split that one into two reviews from what i remember15:39
Swamihaleyb: ok15:39
haleybhe also noticed the segment issues, let me see if he filed a bug15:40
SwamiThe next on is #link https://bugs.launchpad.net/neutron/+bug/170977415:40
openstackLaunchpad bug 1709774 in neutron "Multiple router_centralized_snat interfaces created during Heat deployment" [High,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)15:40
Swamihaleyb: I did not see one tagged with DVR on the segment issue, but it might be ml2 specific bug.15:40
*** slaweq has quit IRC15:40
Swami#link https://review.openstack.org/#/c/494376/15:41
SwamiThis patch needs review. mlavalle had already reviewed this patch a couple of times. May be we need to take a look at it again.15:41
SwamiThis patch is can merge on its own and will not cause any trouble to our existing critical issue in the gate.15:42
SwamiThat's all I have for today on DVR bugs.15:42
Swamimlavalle: back to you.15:42
haleybthere was another related to fwaas15:42
haleybhttps://bugs.launchpad.net/neutron/+bug/171539515:43
openstackLaunchpad bug 1715395 in neutron "FWaaS: Firewall creation fails in case of distributed routers (Pike)" [High,In progress] - Assigned to Reedip (reedip-banerjee)15:43
mlavalleSwami: I have a question regarding this last patchset15:43
haleybmlavalle: go ahead15:43
mlavalleif the router port fails, we want to delete the snat port, correct?15:44
mlavallenevermind, I think the answer is yes15:45
mlavalleI just got confused15:45
Swamithe snat port should be removed when we remove the router-interface. Or in other words, if something errors out while router port is getting created, then we need to also clean up the csnat ports.15:45
*** egallen has quit IRC15:46
mlavalleyeap15:46
Swamiprovided the gateway is set.15:46
mlavalleand that is why we need the context15:46
Swamihaleyb: thanks for the buglink on the fwaas. This was not tagged to 'l3_dvr_backlog'. I just tagged it.15:46
*** baoli has quit IRC15:46
SwamiI already see a patch in progress.15:46
Swami#link https://review.openstack.org/50157015:47
haleybyes, i didn't know they were using router_info data like that15:47
*** baoli has joined #openstack-meeting-315:47
SwamiI will review it. They are applying the firewall rules on the 'rfp' port, so they need the info on the fipnamespace creation and the link.15:48
*** bobh has joined #openstack-meeting-315:48
haleyblet's go to mlavalle since he must have bugs as well, only :12 left15:48
mlavalleno, I don't have any15:48
Swamimlavalle: back to you.15:48
mlavalledo we need to discuss something else?15:48
davidshahttps://bugs.launchpad.net/neutron/+bug/1705536 was discussed at the drivers meeting last week.15:49
openstackLaunchpad bug 1705536 in neutron "[RFE] L3-agent agent-mode dvr bridge." [Wishlist,Triaged]15:49
mlavallelet me change topics15:49
davidshaSorry!15:49
*** marios has quit IRC15:49
*** egallen has joined #openstack-meeting-315:49
mlavalle#topic L3-agent agent-mode dvr bridge15:49
*** openstack changes topic to "L3-agent agent-mode dvr bridge (Meeting topic: neutron_l3)"15:49
mlavallego ahead15:49
mlavalleit was actually very well received, I might say15:50
davidshaThe logs: http://eavesdrop.openstack.org/meetings/neutron_drivers/2017/neutron_drivers.2017-08-31-22.03.log.html#l-14715:50
davidshaYes, They were discussing it being an experimental job, it was conditional that it was kept isolated from existing DvR features.15:52
*** rossella_s has quit IRC15:52
davidshamlavalle: that about right?15:52
Swamidavidsha: understood15:52
mlavalleYes15:52
mlavalleso I think the question / ask to Swami and haleyb would be to take a look and make sure that is indded the case, that the DVR code is isolated from this patchset15:53
davidshaThey also were wondering how it would work with HA and VRR15:53
Swamimlavalle: sure will take a look at it.15:53
davidshaSwami: Thank you.15:53
Swamidavidsha: Do we have a spec for it.15:53
*** rossella_s has joined #openstack-meeting-315:53
davidshaSwami: No, but I can draft one if necessary.15:54
Swamidavidsha: if you can draft one that would be great and I can take a look at it during the PTG for review.15:54
davidshaSwami: Ack, I'll work on that asap.15:55
mlavalledavidsha: anything else?15:56
davidshamlavalle: nothing off the top of my head, if you have any questions for me I'm on IRC most of the time15:57
mlavalleok15:57
haleybSwami: was this the segment trace you saw?  https://bugs.launchpad.net/bugs/1714068 - if so guess i need to get to fixing it :)15:58
openstackLaunchpad bug 1714068 in neutron "AttributeError in get_device_details when segment=None" [Medium,New]15:58
mlavalleSwami, haleyb there is a bug that I would like to discuss with you. But since we are running out of time, let's do this in the Neutron channel15:58
Swamimlavalle: ok will do15:58
Swamihaleyb: I did not remember seeing the Nonetype: attribute error. But let me recheck15:59
haleybmlavalle: sure, i'll be in a meeting but will try15:59
*** dtantsur has joined #openstack-meeting-315:59
mlavalleok15:59
mlavalle#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Thu Sep  7 15:59:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-09-07-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-09-07-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-09-07-15.00.log.html15:59
davidshaThanks15:59
edleafeHi mlavalle!15:59
* mlavalle smiles and waves at edleafe16:00
Swamibye16:00
edleafe#startmeeting api-sig16:00
openstackMeeting started Thu Sep  7 16:00:48 2017 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
elmikobeat me to it16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api-sig)"16:01
openstackThe meeting name has been set to 'api_sig'16:01
dtantsuro/16:01
edleafe#chair cdent elmiko edleafe16:01
openstackWarning: Nick not in channel: cdent16:01
openstackCurrent chairs: cdent edleafe elmiko16:01
edleafe#link https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda16:01
*** janzian has left #openstack-meeting-316:01
*** Patifa has joined #openstack-meeting-316:01
edleafecdent isn't around; I think he's enjoying his time between vmware visit and PTG16:01
elmikogotcha16:01
*** rmart04 has joined #openstack-meeting-316:02
* dtantsur will have to run after roughly 30 mins16:02
edleafedtantsur: it shouldn't take that long :)16:03
edleafe#topic previous meeting action items16:03
*** openstack changes topic to "previous meeting action items (Meeting topic: api-sig)"16:03
edleafe#link http://eavesdrop.openstack.org/meetings/api_sig/2017/16:03
*** srobert has joined #openstack-meeting-316:03
*** srobert has quit IRC16:03
edleafeOnly action was for elmiko to send another note to PTLs, and that was done16:03
edleafeStill no takers?16:03
elmiko\o/16:03
elmikonah16:03
elmikoi think dtantsur and tellesnobrega are the only people who have expressed any interest16:03
*** srobert has joined #openstack-meeting-316:03
elmikoi also am putting together my test case to use, so we'll have something to discuss on that front16:04
edleafeMaybe we should follow up with the PTLs later asking why: did they not feel that it was needed, or did they not want to appear dumb, or...16:04
elmikogreat idea16:04
dtantsurwhat I hear is: changing API is too hard, so we probably just leave it as it is..16:04
elmikowe could put together a google form and mail it out after the ptg ?16:04
dtantsurit may be different for people who itnroduce moar new API16:04
edleafeWe can use the docs from the test case to explain it better16:05
elmikogood point dtantsur16:05
elmikoedleafe: that's what i was hoping, something to seed our example case16:05
edleafedtantsur: yeah, I didn't want them to think that was the goal16:05
edleafedtantsur: it was more for new/planned APIs and changes16:05
dtantsurthen maybe we should reach out to people who just plan on joing the big tent (or how is it called now?)16:06
dtantsurthey have bigger chances of needing our guidance16:06
elmikoyeah, if we could have something that new projects could evaluate early in their process that would be excellent16:07
edleafeIt's now "the cozy condo"16:07
elmikoLOL16:07
*** persia has quit IRC16:07
dtantsurmeaning: reach out not only to the official PTLs, but to leaders of the candidate projects16:07
dtantsuryep :D16:07
elmikoi think they missed a great opportunity to call it the Big Bike Shed16:07
edleafeDo we have a resource listing such people?16:07
*** raildo has quit IRC16:08
edleafeelmiko: :)16:08
dtantsurmay require some manual work..16:08
edleafetruth in packaging16:08
elmikonot sure if the governance repo has anything like that16:08
elmikobut yeah, we'll probably have to pepper the mailing lists16:08
dtantsurwe can start with proposed governance changes16:08
*** cdent has joined #openstack-meeting-316:08
edleafeyeah, I'm only aware of them when they apply for inclusion16:08
dtantsurthere are like 4 projects proposed IIRC16:08
cdentI’m not really here16:08
edleafecdent could help with that16:08
edleafeif he were here16:08
dtantsurWHO IS TALKING??16:09
cdentwhat can I help with?16:09
elmikois there any way we could get a blog post put up on the official openstack.org site?16:09
elmikoor maybe superuser or something16:09
edleafecdent: sending the PTL invitation to new projects that are not yet in the ${BIG_TENT_REPLACEMENT}16:09
elmikocdent: we're discussing how we can reach out to new projects before they have joined the community, to help get the api messaging out earlier in their process16:10
dtantsurthen there is this Mogan project, which is Nova-for-Bare-Metal16:10
cdentI’d say watch the commit logs for project-config, not governance16:10
dtantsurthey introduce new APIs on top of a nova-ish thing16:10
cdentas governance will only get you stuff that is wanting to be "official"16:10
cdentby then it is usually too late16:11
elmikoyeah16:11
*** raildo has joined #openstack-meeting-316:12
*** egallen has quit IRC16:12
edleafecdent: can you maybe get a list of such groups to elmiko?16:12
cdenti can take that action, but it won’t be today16:12
* mlavalle waves at cdent16:12
elmikoi think we're talking about sending this email after the ptg, is that accurate?16:13
* cdent waves at mlavalle 16:13
*** raildo has quit IRC16:13
* edleafe demands that cdent drop whatever he's doing and serve elmiko instead16:13
elmikohaha16:13
cdentI’ve missed these special moments16:13
dtantsurlol16:13
*** anilvenkata|AFK has quit IRC16:13
edleafeelmiko: if it were a week earlier, I'd go for it, but perhaps it's best to do it after PTG16:14
elmikoagreed16:14
edleafeok, let's move on16:14
edleafe#topic open mic and new biz16:14
edleafeOnly one item:16:14
edleafeTurn PTG etherpad into more of a schedule16:14
edleafe#link https://etherpad.openstack.org/p/api-ptg-queens16:14
*** openstack changes topic to "open mic and new biz (Meeting topic: api-sig)"16:14
elmikowill there be any projects in attendence at the ptg who are prospects?16:15
edleafeWe've kind of started that16:15
edleafeelmiko: prospects for... ?16:15
elmikoprojects that want to join the ${BIG_TENT_REPLACEMENT}16:16
edleafeI wouldn't expect them16:16
elmikook, i didn't think so, but had to ask =)16:16
edleafeOne of the perks of being official is that you get space at PTG16:16
elmikoright16:16
edleafeSome official groups are doing virtual PTGs even16:16
edleafekeeping costs down16:16
elmikointeresting16:16
edleafeand avoiding flying into the US16:16
cdentelmiko: if you look at the etherpad for the SWG/TC room there’s some stuff on the new groups that are currently applying, some of which will be at ptg16:16
elmikocdent: ack, thanks!16:17
edleafeI posted some proposed time boxes for the items on the PTG agenda16:18
edleafeAs elmiko already noted, some are a bit optimistic16:18
edleafeI just wanted to signal that they were the types of topics that could fill any amount of space given to them16:18
elmikoi think your thought process on the shorter ones was well reasoned16:18
dtantsurdo we have a slot for reading mordred's literature aloud?16:19
edleafeSo it was best to give them small targets16:19
elmikodtantsur: lol +116:19
edleafedtantsur: let's do that after lunch when people will already be sleepy16:19
TheJuliadtantsur: wouldn't that be mordred ranting? :)16:19
dtantsurlol16:19
elmikohaha16:19
dtantsurTheJulia: we will be reading, mordred will be ranting..16:19
edleafeWe can take turns reading it in our best mordred voice16:19
dtantsuran ideal API SIG meeting16:19
dtantsuredleafe: you won't enjoy my accent :)16:20
edleafedtantsur: heh16:20
edleafeAny other topics for new biz?16:21
mordredgah. I REALLY need to update two docs for the ptg ...16:21
mordredso many things, so little time16:21
*** annegentle has joined #openstack-meeting-316:22
edleafemordred: yeah, quit goofing off!16:22
edleafe#topic guidelines16:23
edleafe#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:23
*** openstack changes topic to "guidelines (Meeting topic: api-sig)"16:23
edleafe#link https://review.openstack.org/#/q/status:open+project:openstack/api-sig,n,z16:23
edleafeNo guideines listed as api-sig (yet!)16:23
edleafecdent16:23
edleafegeez16:23
edleafecdent's extensions guideline looks pretty good16:23
cdentwut?16:23
edleafeis it freeze-able?16:24
elmiko+116:24
dtantsurI'd say it's very straightforward16:24
dtantsur"please don't do what ironic is doing with its API"16:24
edleafeI haven't reviewed the latest version, so I'll do that after the meeting, and unless I find a stopper, I'll freeze it16:24
edleafeSound good?16:24
cdentyes16:24
dtantsur++16:24
edleafe#action edleafe to review https://review.openstack.org/#/c/491611/ and freeze it if no problems are found16:25
elmikoedleafe: sounds good16:25
edleafeAnything else for guidelines?16:25
edleafemoving on...16:26
edleafe#topic bug review16:26
*** openstack changes topic to "bug review (Meeting topic: api-sig)"16:26
edleafe#link https://bugs.launchpad.net/openstack-api-sig16:26
edleafeNo new bugs16:26
edleafeAny bug comments?16:26
elmikothat link errors out for me16:27
elmikois it just because there are no bugs yet?16:27
edleafehmmm16:28
edleafeI thought when I changed the name, the link would also follow16:28
edleafeWhen I click the api-sig link, it redirects to the api-wg bug page16:28
elmikohrm16:29
edleafeI'll check it out after the meeting16:29
elmikothanks16:29
edleafewhich leads us to...16:29
edleafe#topic weekly newsletter16:29
*** openstack changes topic to "weekly newsletter (Meeting topic: api-sig)"16:29
edleafe#link https://etherpad.openstack.org/p/api-sig-newsletter16:29
edleafeelmiko: will you do the honors? Since cdent isn't here, of course16:30
elmikoedleafe: sure thing16:30
edleafeok, ping us in -sdks when you're ready16:30
edleafeAnything else before we close?16:30
elmikoquestion about the freeze16:30
elmikoshould i hold off on the newsletter till you read that review?16:30
edleafeok, I'll do that first and then ping you16:31
elmikoack, i'll fix up the rest and just wait on that16:31
edleafeyou can write it up as if it will be frozen, but don't send it until it is16:31
elmikoyup16:31
edleafeI hope everyone has safe travels to the PTG! See you in Denver!16:32
edleafe#endmeeting16:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:32
openstackMeeting ended Thu Sep  7 16:32:35 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-09-07-16.00.html16:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-09-07-16.00.txt16:32
openstackLog:            http://eavesdrop.openstack.org/meetings/api_sig/2017/api_sig.2017-09-07-16.00.log.html16:32
dtantsuro/16:32
*** dtantsur has left #openstack-meeting-316:32
cdento/16:32
*** cdent has left #openstack-meeting-316:33
elmikothanks edleafe16:33
*** rmart04 has quit IRC16:33
*** raildo has joined #openstack-meeting-316:33
*** rmart04 has joined #openstack-meeting-316:34
*** pbourke has quit IRC16:34
*** annegentle has quit IRC16:34
*** slaweq has joined #openstack-meeting-316:37
*** annegentle has joined #openstack-meeting-316:40
*** MarkBaker has joined #openstack-meeting-316:40
*** slaweq has quit IRC16:41
*** rmart04_ has joined #openstack-meeting-316:46
*** rmart04 has quit IRC16:46
*** rmart04_ is now known as rmart0416:46
*** marst has quit IRC16:46
*** annabelleB has quit IRC16:48
*** annabelleB has joined #openstack-meeting-316:48
*** junbo has quit IRC16:50
*** junbo has joined #openstack-meeting-316:55
*** Swami has quit IRC16:56
*** rmcall has joined #openstack-meeting-316:57
*** MarkBaker has quit IRC16:57
*** ralonsoh has quit IRC16:58
*** baoli has quit IRC17:00
*** Patifa has quit IRC17:00
*** baoli has joined #openstack-meeting-317:00
*** Patifa has joined #openstack-meeting-317:01
*** outofmemory has joined #openstack-meeting-317:03
*** mlavalle has left #openstack-meeting-317:03
*** iyamahat has joined #openstack-meeting-317:08
*** outofmemory has quit IRC17:08
*** VW has quit IRC17:12
*** iyamahat_ has joined #openstack-meeting-317:13
*** persia has joined #openstack-meeting-317:16
*** iyamahat has quit IRC17:16
*** SumitNaiksatam has joined #openstack-meeting-317:19
*** harlowja has joined #openstack-meeting-317:19
*** baoli has quit IRC17:19
*** baoli has joined #openstack-meeting-317:20
*** psachin has quit IRC17:31
*** raildo has quit IRC17:33
*** gouthamr has quit IRC17:33
*** slaweq has joined #openstack-meeting-317:38
*** baoli has quit IRC17:39
*** baoli has joined #openstack-meeting-317:41
*** bobmel_ has joined #openstack-meeting-317:42
*** slaweq has quit IRC17:43
*** rmcall has quit IRC17:45
*** bobmel has quit IRC17:46
*** rmcall has joined #openstack-meeting-317:46
*** tbachman has joined #openstack-meeting-317:49
*** annabelleB has quit IRC17:49
*** annabelleB has joined #openstack-meeting-317:52
*** rkukura has joined #openstack-meeting-317:53
*** davidsha has quit IRC17:53
*** bobh has quit IRC17:54
*** annak_ has joined #openstack-meeting-317:58
*** annak_ has quit IRC17:58
*** annakk has joined #openstack-meeting-317:59
SumitNaiksatamrkukura: tbachman annakk: hi18:00
annakkhi!18:00
tbachmanSumitNaiksatam: hi!18:00
rkukurahi18:00
*** rmart04 has quit IRC18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Sep  7 18:01:07 2017 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
SumitNaiksatamrkukura: thanks for chairing the meeting last time18:01
*** gouthamr has joined #openstack-meeting-318:01
SumitNaiksatamtbachman: thanks for shepherding the discussion on the DB migrations18:01
SumitNaiksatamannakk: thanks for bringinging up the UI patches18:01
tbachmanSumitNaiksatam: not sure I shepherded as much as watched18:01
tbachmanthe sheep moved themselves ;)18:01
SumitNaiksatamand my apologies for going MIA at the last minute18:02
rkukurabaa18:02
tbachmanSumitNaiksatam: +1k to annakk18:02
SumitNaiksatamtbachman: lol!18:02
tbachmanrkukura: lol18:02
annakk:)18:02
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Sept_7th_201718:02
SumitNaiksatamwe have a bit to cover today18:02
SumitNaiksatamlets get rolling18:02
SumitNaiksatam#topic mitaka, newton DB migration backport strategy18:02
*** openstack changes topic to "mitaka, newton DB migration backport strategy (Meeting topic: networking_policy)"18:02
SumitNaiksatam#link https://review.openstack.org/#/c/499185/18:02
SumitNaiksatam#link https://review.openstack.org/#/c/49924018:03
*** marst has joined #openstack-meeting-318:03
SumitNaiksatami read the transcript of the last meeting, and i meant to respond last thursday itself, somehow didnt happen, and then fast forward to today :-)18:03
tbachmanSumitNaiksatam: no worries. Good to get it firsthand here18:03
SumitNaiksatami agree with the rkukura and the general point that we have a short term problem to fix and then a longer term decision to make18:04
tbachman(and thanks for catching up via transcript)18:04
SumitNaiksatamtbachman: np18:04
SumitNaiksatamwe cannot do any more releases without solving the current mess we are in (regardless of what longer term strategy we use)18:04
SumitNaiksatamso lets first try to resolve that18:04
SumitNaiksatamwould it make more sense to start with the mitaka to newton migration issue first?18:05
rkukuraSumitNaiksatam: Can we assume master or stable branch trunk chasing use cases are not a concern?18:05
SumitNaiksatam(the discussion will most likely apply to newton to ocata as well)18:05
SumitNaiksatamrkukura: yes, we never claimed to support them18:05
SumitNaiksatamrkukura:  i mean we support them18:05
SumitNaiksatambut we did not claim that they would not break18:06
rkukuraok, just wanted to make that explicit18:06
SumitNaiksatamrkukura: very good point, thanks for stating that upfront18:06
*** Swami has joined #openstack-meeting-318:06
SumitNaiksatamso rkukura and tbachman you idenfied that there are a couple of migrations that are skipped between mitaka and newton?18:07
rkukurafor mitaka->newton upgrade, I see two migraitions that will be missed18:07
SumitNaiksatam(these being different from the ones that are missing between newton and ocata)18:07
rkukura5239 tenant_id->project_iod18:08
rkukurac460 NFP devstack18:08
SumitNaiksatamrkukura: okay18:08
tbachmanSumitNaiksatam: here was the list I’d compiled: https://pastebin.com/sstdM9ZZ18:08
SumitNaiksatami also want to make a general comment regarding NFP18:08
SumitNaiksatamtbachman: great thanks18:08
tbachmanSumitNaiksatam: np!18:08
* tbachman doesn’t have #link powers18:09
tbachmanor maybe I do?18:09
SumitNaiksatamoh18:09
tbachman#link https://pastebin.com/sstdM9ZZ <= DB migrations18:09
SumitNaiksatam#chairs rkukura tbachman annakk18:09
SumitNaiksatam#chair rkukura tbachman annakk18:09
openstackCurrent chairs: SumitNaiksatam annakk rkukura tbachman18:09
tbachmanI guess I didn’t have topic powers18:09
tbachmanbut I did have link18:09
rkukuratbachman: I don’t see 5239 on your list18:10
tbachmanhmmmm18:10
* tbachman tries to remember why18:10
SumitNaiksatamso my comment on NFP, to the extent i am aware of, we dont have a user currently deploying NFP on mitaka or newton18:10
*** rmcall has quit IRC18:10
rkukuratbachman: is it because tenant_id wasn’t renamed project_id in the DB until newton?18:10
* tbachman is looking18:11
SumitNaiksatamso while we should try our best to maintain the integrity of that component, we can make changes to that component without fear of disruption18:11
* rkukura has not looked at when neutron renamed it18:11
tbachmanrkukura: which patch introduced that?18:12
rkukuratbachman: to gbp?18:12
tbachmanyeah18:12
SumitNaiksatami think the change has been going in neutron for a while18:12
SumitNaiksatambut i think we were forced to make the change in newton?18:12
SumitNaiksatamannakk did the change in GBP if recall correctly18:13
annakkyes18:13
SumitNaiksatamand we didnt want to backport it then18:13
tbachmanah18:13
tbachmanrkukura: I think my list was based on the most recent migration in stable/mitaka18:14
tbachmanso it likely doesn’t cover that one18:14
tbachman(and good point)18:14
rkukurayes it was annakk’s newton patch, so we don’t want it on mitaka18:14
rkukurabut it needs to run when upgrading from mitaka->newton, and it will not because mitaka’s HEAD is beyond it in newton’s chain18:15
tbachman#link https://github.com/openstack/group-based-policy/commit/f7f1ce349e2ed7579f64430c8cf8f0f5137c8eec#diff-9ae7c407a57ed5bb5e916dbbf4530e8b <= patch with DB migration18:15
tbachmanrkukura: ack18:15
SumitNaiksatamrkukura: ack18:15
SumitNaiksatamso can we introduce conditional migrations at the HEAD that adds those changes only if they are missing?18:16
rkukuraseems like, on stable/newton, we need to make that migration idempotent and move closer to HEAD18:16
rkukuraSumitNaiksatam: I think we are saying the same thing18:16
annakkSumitNaiksatam18:16
SumitNaiksatamrkukura: right18:16
annakkI think its the best way to go18:17
annakkif we care about same-branch  migrations18:17
rkukurasame thing for the NFP patch?18:17
SumitNaiksatamrkukura: i would vote in favor of doing it for the NFP patch as well, just to maintain the overall consistency18:18
rkukuraSumitNaiksatam: right, even if someone isn’t using NFP, the DB schema needs to be consistent with the code18:18
SumitNaiksatamthe migration patch would however have to be introduced in master, and would have to backport its way to newton18:18
SumitNaiksatamrkukura: agree, depending on the schema change18:18
rkukuraSumitNaiksatam: I agree the same issue with the same two patches will be issues on stable/ocata and master18:19
SumitNaiksatami guess thats what you mean by “consistent"18:19
*** annabelleB has quit IRC18:19
SumitNaiksatamrkukura: ack18:19
rkukuraso there are two more migrations that will be missed on upgrade from mitaka or newton to ocata:18:20
SumitNaiksatamhmmm18:20
rkukurada6a QoS18:20
rkukurabff1 NFP18:20
SumitNaiksatamokay, rkukura thanks for digging those out18:20
rkukuraand my notes have one that at that time was HEAD on master but not back-ported to ocata: 4c0c APIC18:22
*** annabelleB has joined #openstack-meeting-318:24
rkukuraso should our strategy be to do one patch that fixes everyhing on master that might be missed when upgrading from mitaka, and then manually back-porting the needed parts of that to stable/ocata and stable/newton?18:24
SumitNaiksatamrkukura: ack on one patch18:24
tbachmanrkukura: seems like a sound approach18:24
annakkagree18:24
*** VW has joined #openstack-meeting-318:24
SumitNaiksatamstable/ocata would be identical to master18:24
rkukuraSumitNaiksatam: I agree it should be, until there is something new on master that doesn’t get back-ported18:25
SumitNaiksatamrkukura: right18:25
SumitNaiksatamthere is a some difference between newton and ocata18:26
SumitNaiksatamnamely, QoS and the NFP changes18:26
rkukuraSumitNaiksatam: right18:26
SumitNaiksatamokay so assuming we follow this plan18:26
SumitNaiksatamwe will be left with different chains on different branches18:26
rkukuraI could do these patches, but probably wouldn’t get to them til mid next week. I’m flying BOS->SFO tomorrow (might be able to do them on the plane) and taking PTO Monday18:27
tbachmanshould we revert the ip_pool changes the?18:27
tbachmans/the/the/18:27
tbachmandang18:27
tbachmans/the/then/18:27
* tbachman checks his “n” key18:27
rkukuratbachman: 27b7 is on master, ocata, and newton, right?18:27
tbachmanrkukura: ack18:27
tbachmanbut placement was the question18:27
*** chyka has quit IRC18:28
tbachmanjust wasn’t sure if it made things simpler18:28
* tbachman is fine with leaving it as-is18:28
tbachmanbut — I’ll revert the other 2 DB migration patches that I have18:28
SumitNaiksatamtbachman: you are thinking that we should put this change also in the “uber” backport patch?18:28
rkukurais there a reason to have that change on newton, or not?18:28
*** chyka has joined #openstack-meeting-318:28
tbachmanthe IPv6 feature is all the way back to stable/mitaka18:28
SumitNaiksatamrkukura: ideally i think it should be all the branches18:29
tbachmanthe question is whether we want the same behavior of ip_pool18:29
tbachmanmy thinking is that it should be the same18:29
SumitNaiksatamtbachman: ack18:29
rkukuratbachman: ack18:29
tbachmanwhich leaves the stable/mitaka patch for that feature18:30
tbachman#link https://review.openstack.org/#/c/499185/ <= backport of ip_pool size increase to stable/mitaka18:30
*** kbyrne has joined #openstack-meeting-318:30
*** chyka_ has joined #openstack-meeting-318:32
rkukuraso if we back-port this to stable/mitaka and 27b7 becomes HEAD on stable/mitaka, we will have more patches that would be missed upgrading from mitaka to newton or ocata18:32
rkukuras/patches/migrations/18:32
SumitNaiksatamrkukura: so thats the longer term issue18:32
rkukuraguess so18:33
*** chyka has quit IRC18:33
SumitNaiksatammy earlier comment - “we will be left with different chains on different branches”18:33
SumitNaiksatamso what do we do for future backports once we have cleaned up the mess18:33
rkukuraSumitNaiksatam: good transition18:33
SumitNaiksatam(ip_pools falling into that future backports category though we already have the patch ready)18:33
annakkwhy do we backport agressively?18:34
SumitNaiksatamannakk: to support users :-)18:34
rkukuraone option is to try to keep the DB schema identical across the active branches18:34
SumitNaiksatamrkukura: right18:34
*** dims has quit IRC18:34
annakkusers are reluctant to go forward in release?18:35
SumitNaiksatamannakk: typically the users, once they deploy a particular release, dont move as quickly18:35
SumitNaiksatamannakk: within the same release, yes18:35
SumitNaiksatambut moving forward to a new release takes more doing18:35
SumitNaiksatami know people still using liberty18:35
SumitNaiksatami mean legit users in production18:36
*** dims has joined #openstack-meeting-318:36
rkukuraannakk: also, GBP was evolving rapidly, so users wanted the latest GBP18:36
SumitNaiksatamrkukura: ack18:36
annakki think there's a general consensus in openstack to avoid backporting features that require schema changes18:36
SumitNaiksatamannakk: completely agree and understand18:37
SumitNaiksatamannakk: but in those cases, the distro vendors are still doing the backporting18:37
*** annabelleB has quit IRC18:37
SumitNaiksatamalbeit selectively and perhaps on a per customer basis18:38
* tbachman notes there are 2 classes of openstack users. 1) pre-production, who want the latest openstack release; 2) production users, who never want to move to a new release ;)18:38
SumitNaiksatamtbachman: lol18:38
annakk:)18:38
SumitNaiksatamtbachman: and on (2) not only do they dont want to move, they still want all the latest features :-)18:38
*** slaweq has joined #openstack-meeting-318:39
rkukuratbachman: Also, 1.5) want newest GBP on older OpenStack18:39
SumitNaiksatamand that latter part makes it really difficult to support18:39
tbachmanlol18:39
SumitNaiksatamrkukura: i categorized that as 2.518:39
SumitNaiksatamanyway, annakk to your question, we decided to take the simple way out -18:39
SumitNaiksatamthat is try to keep all branches consistent18:39
rkukuraso should GBP start playing by the rules at some point?18:40
SumitNaiksatamthat is feature wise, to the extent possible18:40
*** flwang has quit IRC18:40
annakkSumitNaiksatam: sounds like its only possible if new features don't conflict with neutron db all the way back18:41
SumitNaiksatamrkukura: i think if it was left to us, it would be much easier for us to just play by the rules since it reduces this headache of backporting18:41
SumitNaiksatamannakk: yes sure, and mostly we havent hit issues in that regard (luckily)18:41
*** dims has quit IRC18:41
*** flwang has joined #openstack-meeting-318:41
rkukuraif GBP’s official stable branches followed OpenStack backporting rules, it would be possible to maintain different branches (unstable/mitaka, unstable/newton, unstable/ocata, …) that more aggressively back-port, but that is more work18:42
*** sdague has quit IRC18:42
*** yamahata has quit IRC18:42
SumitNaiksatamrkukura: exactly i was just saying that, we dont have a “distro” vendor like entity doing that “unstable” branch work for us18:42
SumitNaiksatamfor other openstack projects its being done by those distro vendors18:43
rkukuraSumitNaiksatam: right18:43
*** slaweq has quit IRC18:43
annakkthanks for the 101, makes sense18:43
rkukurabut even then, new features are typically not back-ported, are they?18:43
rkukuras/are/aren’t/18:43
SumitNaiksatamrkukura: i agree, mostly not features18:44
SumitNaiksatambut i guess its easier for them to put the stake in the ground for those projects18:44
*** dims has joined #openstack-meeting-318:45
*** egallen has joined #openstack-meeting-318:46
SumitNaiksatamof course we can decide to the same thing here, but i am not sure if this is really beyond our control in the sense that if a user asks for a feature be backported, would we actually be able to say no!18:46
* tbachman wonders if we’re any closer to a path forward here18:46
SumitNaiksatamtbachman: thanks for the reality check :-)18:47
tbachmansorry — not trying to be negative18:47
*** egallen has quit IRC18:47
tbachmanseems like we have several options18:47
SumitNaiksatamtbachman: no, didnt mean to suggest that you were implying that18:47
rkukurait would be good to keep some flexibility18:47
SumitNaiksatamone thing is for sure, we need to be much more selective in backporting features/patches that involve DB migrations (assuming we even decide that we will allow those and have a strategy around it)18:48
SumitNaiksatamrkukura: ack18:48
rkukuraI think a good case to think about is 5239 (tenant->project), which should definitely not be back-ported to stable/mitaka, but is definitely needed when upgrading from mitaka to anything newer18:48
SumitNaiksatamthis current mess is a good opener in that sense18:48
SumitNaiksatamrkukura: so that would be the argument against making all migration chains identical?18:49
tbachmanSumitNaiksatam: you had mentioned the idea of backporting with a no-op18:50
SumitNaiksatamtbachman: thanks, i did, but that is not the ultimate solution, because that introduces the issue of skipping that migration all together18:50
SumitNaiksatamwhen migrating from one branch to the next18:50
SumitNaiksatami meant the no-op only for upgrades witthin the same branch18:51
SumitNaiksataminstead of no-op we could do conditional, but i dont think that would solve the problem18:51
SumitNaiksatamcompletely18:51
SumitNaiksatamwe have 9 mins remaining18:51
rkukuraI don’t see how no-op solves anything18:52
* tbachman nods18:52
SumitNaiksatamno-op could potentially solve the problem of temporarily get the chains to be temporarily identical across the branches18:53
annakkbut they can't stay identical forever, can they?18:53
rkukuraI think it might help to keep the migrations that are not backported to older branches in front of (closer to HEAD than) migrations that are back-ported18:53
SumitNaiksatambut we are solving the short term problem in a better way here by introducing the idempotent migrations at the head18:53
SumitNaiksatamannakk: agree18:54
rkukurano-op makes the chains look identical, but they still are not really identical18:54
SumitNaiksatamannakk: but we would have more control over what we merge in the future18:54
SumitNaiksatamrkukura: right, schema is not identical18:54
annakkhow do we handle situation when feature X is not backported, but after that comes feature Y that is backported?18:55
SumitNaiksatamrkukura: regarding your earlier point, it can still get us to same situation we are currently in18:55
annakkno-op for X?18:55
*** bobh has joined #openstack-meeting-318:55
* tbachman understands why the OpenStack policy is not to backport DB migrations :(18:55
SumitNaiksatami dont think we should discuss no-op since it doesnt solve the longer term problem18:55
*** rossella_s has quit IRC18:55
SumitNaiksatamsorry that i brought it up :-(18:56
tbachmanSumitNaiksatam: I did actually — sorry18:56
tbachman(in this meeting, that is)18:56
*** rossella_s has joined #openstack-meeting-318:56
*** iyamahat_ has quit IRC18:56
SumitNaiksatamtbachman: i take the responsibility18:56
SumitNaiksatamokay so in the interest of time18:56
SumitNaiksatamwe will have to go back to emails18:56
SumitNaiksatamlets try to close this by tomorrow18:56
SumitNaiksatamperhaps we can take a break and think again with some more clarity18:57
SumitNaiksatam#topic UI patches18:57
*** openstack changes topic to "UI patches (Meeting topic: networking_policy)"18:57
SumitNaiksatami have tried the ocata UI18:57
SumitNaiksatamannakk: does your patch fix the issues you are seeing?18:57
rkukuraI think a policy on ordering the migrations when back-porting could at least prevent the need to shuffle them and make them idempotent going forward18:57
SumitNaiksatamrkukura: definitely18:57
rkukuralets cover UI18:58
SumitNaiksatamsorry i meant i *have not* tried Ocata UI18:58
annakkSumitNaiksatam: it fixes one issue, and I'm not sure about the rest since I discovered issues linger after horizon restart18:58
SumitNaiksatami have tested newton recently18:58
SumitNaiksatamannakk: okay, i will give it a try18:58
SumitNaiksatamsorry that you ran into this after we released ocata, should have been caught before release18:58
SumitNaiksatamannakk: thanks also for starting to look at the UI patchers18:59
SumitNaiksatamtbachman: thanks to you as well18:59
SumitNaiksatam#topic py27 logs18:59
*** openstack changes topic to "py27 logs (Meeting topic: networking_policy)"18:59
tbachmanSumitNaiksatam: np!18:59
annakkI'll continue testing it above the fix18:59
SumitNaiksatamplease take look here #link https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#Sept_7th_201718:59
SumitNaiksatamannakk: thanks18:59
*** bobh has quit IRC19:00
SumitNaiksatamin the past we had cleaned up19:00
SumitNaiksatambut again we have a huge amount of repetitive logging19:00
SumitNaiksatammakes it very difficult to debug test failures19:00
SumitNaiksatamwe need to clean up/supress19:00
SumitNaiksatamand check if there are any real issues hidden here in the error message19:01
SumitNaiksatam*messages19:01
SumitNaiksatamthanks all for joining today19:01
SumitNaiksatam#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Thu Sep  7 19:01:10 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
rkukurabye19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-09-07-18.01.html19:01
SumitNaiksatambye19:01
annakkbye19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-09-07-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-09-07-18.01.log.html19:01
rkukurathanks SumitNaiksatam19:01
tbachmanSumitNaiksatam: thanks!19:01
*** rkukura has left #openstack-meeting-319:01
*** tbachman has left #openstack-meeting-319:03
*** annabelleB has joined #openstack-meeting-319:04
*** annabelleB has quit IRC19:05
*** annabelleB has joined #openstack-meeting-319:06
*** egallen has joined #openstack-meeting-319:08
*** julim has quit IRC19:10
*** SumitNaiksatam has quit IRC19:10
*** julim has joined #openstack-meeting-319:12
*** iyamahat has joined #openstack-meeting-319:12
*** slaweq has joined #openstack-meeting-319:12
*** egallen has quit IRC19:14
*** annabelleB has quit IRC19:22
*** skelso has quit IRC19:29
*** yamahata has joined #openstack-meeting-319:31
*** pcaruana has quit IRC19:31
*** annabelleB has joined #openstack-meeting-319:45
*** srobert_ has joined #openstack-meeting-319:54
*** bobh has joined #openstack-meeting-319:56
*** srobert has quit IRC19:58
*** srobert_ has quit IRC19:58
*** bobh has quit IRC20:01
*** iyamahat has quit IRC20:03
*** iyamahat has joined #openstack-meeting-320:03
*** diablo_rojo has joined #openstack-meeting-320:16
*** srobert has joined #openstack-meeting-320:18
*** srobert has quit IRC20:19
*** srobert has joined #openstack-meeting-320:19
*** annabelleB_ has joined #openstack-meeting-320:29
*** annabelleB has quit IRC20:29
*** annabelleB_ is now known as annabelleB20:29
*** bobh has joined #openstack-meeting-320:34
*** cleong has quit IRC20:38
*** julim has quit IRC20:42
*** julim_ has joined #openstack-meeting-320:42
*** iyamahat has quit IRC20:47
*** iyamahat_ has joined #openstack-meeting-320:47
*** chyka_ has quit IRC20:53
*** chyka has joined #openstack-meeting-320:53
*** wanghao_ has joined #openstack-meeting-320:54
*** wanghao has quit IRC20:56
*** julim_ has quit IRC20:57
*** annabelleB has quit IRC20:57
*** scottda_ has joined #openstack-meeting-320:59
*** skelso has joined #openstack-meeting-321:03
*** annabelleB has joined #openstack-meeting-321:03
*** devananda has joined #openstack-meeting-321:08
*** devananda has quit IRC21:08
*** devananda has joined #openstack-meeting-321:09
*** devananda has quit IRC21:10
*** devananda has joined #openstack-meeting-321:10
*** devananda has quit IRC21:14
*** sekelso has joined #openstack-meeting-321:14
*** devananda has joined #openstack-meeting-321:14
*** devananda has quit IRC21:15
*** skelso has quit IRC21:18
*** skelso has joined #openstack-meeting-321:19
*** sekelso has quit IRC21:19
*** srobert has quit IRC21:21
*** baoli has quit IRC21:25
*** slaweq has quit IRC21:27
*** annegentle has quit IRC21:27
*** slaweq has joined #openstack-meeting-321:27
*** egallen has joined #openstack-meeting-321:29
*** slaweq has quit IRC21:32
*** bobh has quit IRC21:33
*** annabelleB has quit IRC21:38
*** Patifa has quit IRC21:39
*** slaweq has joined #openstack-meeting-321:41
*** Patifa has joined #openstack-meeting-321:42
*** slaweq has quit IRC21:43
*** slaweq has joined #openstack-meeting-321:44
*** slaweq has quit IRC21:44
*** slaweq has joined #openstack-meeting-321:46
*** Patifa has quit IRC21:47
*** diablo_rojo has quit IRC21:56
*** slaweq has quit IRC21:56
*** chyka has quit IRC21:59
*** Patifa has joined #openstack-meeting-322:04
*** VW has quit IRC22:07
*** diablo_rojo has joined #openstack-meeting-322:07
*** diablo_rojo_ has joined #openstack-meeting-322:21
*** diablo_rojo has quit IRC22:24
*** egallen has quit IRC22:25
*** annegentle has joined #openstack-meeting-322:33
*** Patifa has quit IRC22:38
*** diablo_rojo__ has joined #openstack-meeting-322:39
*** annegentle has quit IRC22:40
*** Patifa has joined #openstack-meeting-322:41
*** diablo_rojo_ has quit IRC22:42
*** diablo_rojo_ has joined #openstack-meeting-322:43
*** Patifa has quit IRC22:43
*** galstrom is now known as galstrom_zzz22:43
*** diablo_rojo__ has quit IRC22:46
*** marst has quit IRC22:49
*** iyamahat_ has quit IRC22:53
*** iyamahat has joined #openstack-meeting-322:53
*** rossella_s has quit IRC22:56
*** rossella_s has joined #openstack-meeting-322:56
*** rossella_s has quit IRC23:01
*** rossella_s has joined #openstack-meeting-323:05
*** gouthamr has quit IRC23:09
*** lyan has quit IRC23:12
*** annabelleB has joined #openstack-meeting-323:14
*** rossella_s has quit IRC23:19
*** rossella_s has joined #openstack-meeting-323:19
*** chyka has joined #openstack-meeting-323:20
*** julim has joined #openstack-meeting-323:21
*** diablo_rojo_ has quit IRC23:21
*** diablo_rojo_ has joined #openstack-meeting-323:22
*** annabelleB has quit IRC23:24
*** hongbin has quit IRC23:24
*** annabelleB has joined #openstack-meeting-323:24
*** chyka has quit IRC23:25
*** annabelleB has quit IRC23:26
*** skelso has quit IRC23:30
*** Patifa has joined #openstack-meeting-323:38
*** Patifa has quit IRC23:42
*** diablo_rojo_ has quit IRC23:43
*** annabelleB has joined #openstack-meeting-323:47
*** srobert has joined #openstack-meeting-323:49
*** srobert has quit IRC23:49
*** srobert has joined #openstack-meeting-323:50
*** slaweq has joined #openstack-meeting-323:58
*** gouthamr has joined #openstack-meeting-323:59

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