Tuesday, 2018-11-20

*** tetsuro has joined #openstack-meeting00:11
*** jamesmcarthur has quit IRC00:16
*** Liang__ has joined #openstack-meeting00:24
*** longkb has joined #openstack-meeting00:48
*** longkb has quit IRC00:49
*** jamesmcarthur has joined #openstack-meeting01:13
*** jamesmcarthur has quit IRC01:29
*** Liang__ is now known as LiangFang01:32
*** Swami has quit IRC01:34
*** jamesmcarthur has joined #openstack-meeting01:41
*** rbudden has joined #openstack-meeting01:42
*** jamesmcarthur has quit IRC01:53
*** rbudden has quit IRC02:03
*** yamahata has quit IRC02:08
*** jamesmcarthur has joined #openstack-meeting02:12
*** jamesmcarthur has quit IRC02:20
*** yamahata has joined #openstack-meeting02:47
*** jamesmcarthur has joined #openstack-meeting02:58
*** hongbin has joined #openstack-meeting02:58
*** bswartz has joined #openstack-meeting02:59
*** dtrainor_ has quit IRC03:09
*** dtrainor has joined #openstack-meeting03:10
*** jamesmcarthur has quit IRC03:12
*** dtrainor has quit IRC03:13
*** rbudden has joined #openstack-meeting03:27
*** dklyle has quit IRC03:45
*** david-lyle has joined #openstack-meeting03:45
*** armax has joined #openstack-meeting03:46
*** tpatil has joined #openstack-meeting03:54
*** sagara has joined #openstack-meeting03:57
samPHi all for masakari04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Nov 20 04:00:11 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPtpatil: Hi04:00
samPLet's start04:00
samP#topic Critical bugs/patches04:00
*** openstack changes topic to "Critical bugs/patches (Meeting topic: masakari)"04:00
tpatil#link : https://review.openstack.org/#/c/61575204:00
tpatilthis patch is to fix openstack client issue04:01
tpatilif python-masakariclient is installed then osc doesn't work for any command04:01
samPsagara: hi04:01
tpatilPlease review this patch04:01
samPtpatil: got it. LGTM04:01
samPtpatil: thanks for the fix04:01
tpatilwe will need to back port it to stable Rocky branch as well04:02
samPtpatil: OK, let vote now.04:02
samPsagara: Can you review this patch? ^^04:02
sagarasamP: OK, I'll review it later04:03
samPsagara: thanks04:03
tpatilAlso, please review https://review.openstack.org/#/c/61606804:04
*** tetsuro has quit IRC04:04
samPtpatil: OK, this is the cache issue04:04
tpatilyes, same db session is used to create and get resources04:05
samPtpatil: I need time to understand this. I will do review this.04:05
tpatilOk, Thanks04:05
samPtpatil: Do we need to backport this? to Rocky?04:06
tpatilBasically, there are other ways to fix this issue as well04:06
tpatil1. In version objects04:06
tpatil2. API Controller layer04:06
tpatilsamP: No need to back port this issue04:06
tpatilI mean it's not critical/blocker issue04:07
samPtpatil: got it. But the problem was there in rocky and earlier?04:08
tpatilyes, this issue exists since beginning04:09
tpatilduring writing openstacksdk functional tests, we encountered this issue04:09
samPtpatil: OK. Sorry I dont have enough knowledge of this. I will read your patch and review it.04:11
samPThen, let's discuss whether to backport or not.04:12
samPany other critical issus?04:12
samPif not let's jump to next topic.04:14
samPPlease bring up any critical issues anytime04:15
samP#topic Stein Work Items04:15
*** openstack changes topic to "Stein Work Items (Meeting topic: masakari)"04:15
samPSince we all are in summit last week, might not have any progress04:15
tpatilNo big progress at my end04:16
samPtpatil: got it.04:16
samPOK then, pretty quick but let's finish the meeting, if nothing to share04:17
tpatilOk, let's end today's meeting early04:18
samPThank you for your time!04:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:18
openstackMeeting ended Tue Nov 20 04:18:38 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-11-20-04.00.html04:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-11-20-04.00.txt04:18
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-11-20-04.00.log.html04:18
*** rbudden has quit IRC04:20
*** sagara has quit IRC04:21
*** yamamoto has quit IRC04:24
*** yamamoto has joined #openstack-meeting04:28
*** tashiromt has joined #openstack-meeting04:28
*** sridharg has joined #openstack-meeting04:28
*** janki has joined #openstack-meeting04:30
*** tashiromt has quit IRC04:31
*** tpatil has quit IRC04:34
*** yamamoto has quit IRC04:45
*** armax has quit IRC05:00
*** hongbin has quit IRC05:07
*** tetsuro has joined #openstack-meeting05:11
*** jamesmcarthur has joined #openstack-meeting05:12
*** jamesmcarthur has quit IRC05:17
*** dtrainor has joined #openstack-meeting05:26
*** links has joined #openstack-meeting05:57
*** radeks_ has joined #openstack-meeting05:59
*** radeks_ has quit IRC06:00
*** radeks_ has joined #openstack-meeting06:02
*** yamamoto has joined #openstack-meeting06:07
*** yamamoto has quit IRC06:16
*** Luzi has joined #openstack-meeting06:42
*** mahatic has joined #openstack-meeting06:52
*** apetrich has quit IRC07:00
*** mahatic has quit IRC07:12
*** jamesmcarthur has joined #openstack-meeting07:14
*** apetrich has joined #openstack-meeting07:17
*** jamesmcarthur has quit IRC07:19
*** pcaruana has joined #openstack-meeting07:20
*** kopecmartin|off is now known as kopecmartin07:25
*** pcaruana has quit IRC07:34
*** psachin has joined #openstack-meeting07:37
*** pcaruana has joined #openstack-meeting07:40
*** tssurya has joined #openstack-meeting07:46
*** bhagyashris__ has joined #openstack-meeting07:52
*** bhagyashris__ has left #openstack-meeting07:53
*** bhagyashris__ has joined #openstack-meeting07:53
*** tpatil has joined #openstack-meeting07:54
*** longkb has joined #openstack-meeting08:00
*** yamamoto has joined #openstack-meeting08:01
*** tpatil has quit IRC08:10
*** bhagyashris__ has left #openstack-meeting08:13
*** hadai has joined #openstack-meeting08:18
*** YanXing_an has joined #openstack-meeting08:22
*** ralonsoh has joined #openstack-meeting08:24
*** hadai has quit IRC08:35
*** bobh has joined #openstack-meeting08:52
*** longkb has quit IRC08:53
*** priteau has joined #openstack-meeting08:54
*** lbragstad has joined #openstack-meeting08:54
*** bobh has quit IRC09:05
jiaopengju #startmeeting karbor09:09
jiaopengjuhi, all, it’s karbor meeting time, anyone has some topics to discuss?09:10
jiaopengjuit seems the meeting robot is not working, I will try to end the meeting soon. If you has someting that want me know, please join the karbor irc channel09:16
*** YanXing_an has quit IRC09:19
*** jamesmcarthur has joined #openstack-meeting09:24
*** e0ne has joined #openstack-meeting09:24
*** links has quit IRC09:26
*** YanXing_an has joined #openstack-meeting09:28
*** jamesmcarthur has quit IRC09:28
*** a-pugachev has joined #openstack-meeting09:34
*** a-pugachev has quit IRC09:34
*** a-pugachev has joined #openstack-meeting09:39
*** mahatic has joined #openstack-meeting09:41
*** slaweq__ has quit IRC09:48
*** shrasool has joined #openstack-meeting10:02
*** YanXing_an has quit IRC10:23
*** LiangFang has quit IRC10:29
*** slaweq__ has joined #openstack-meeting10:40
*** shrasool has quit IRC11:07
*** shrasool has joined #openstack-meeting11:08
*** njohnston has joined #openstack-meeting11:56
*** raildo has joined #openstack-meeting12:04
*** Luzi has quit IRC12:07
*** slaweq__ has quit IRC12:07
*** janki has quit IRC12:10
*** Luzi has joined #openstack-meeting12:22
*** shrasool has quit IRC12:25
*** slaweq__ has joined #openstack-meeting12:27
*** priteau has quit IRC12:28
*** matrohon has joined #openstack-meeting12:31
fricklerjiaopengju: just a remark for next time, avoid having a space in front of the "#startmeeting" command, because that causes the bot to ignore it12:34
*** psachin has quit IRC12:41
*** slaweq__ is now known as slaweq12:42
*** yamamoto has quit IRC12:57
*** yamamoto has joined #openstack-meeting12:58
*** njohnston has quit IRC12:58
*** kailun has joined #openstack-meeting13:07
*** matrohon has quit IRC13:07
*** mhen has joined #openstack-meeting13:08
*** priteau has joined #openstack-meeting13:11
*** mriedem has joined #openstack-meeting13:41
*** lpetrut has joined #openstack-meeting13:44
*** mlavalle has joined #openstack-meeting13:44
*** boden has joined #openstack-meeting13:58
*** whoami-rajat has quit IRC14:00
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Nov 20 14:00:27 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
amotokiI still seem to be in jet lag. This meeting time is fine today :)14:01
*** rubasov has joined #openstack-meeting14:01
mlavalleamotoki: LOL14:01
mlavalleok, let's get going14:02
*** artom has quit IRC14:02
mlavalleAs usual the meeting's agenda is here: https://wiki.openstack.org/wiki/Network/Meetings14:02
mlavalle#Topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:03
mlavalleOur next milestone is Stein-2, January 7 - 1114:03
mlavalleThe other topic I wanted to share with the team is that last week the TC approved and merged  vision for OpenStack Clouds:14:05
*** hle2 has joined #openstack-meeting14:05
mlavalle#link https://governance.openstack.org/tc/reference/technical-vision.html14:05
mlavalleThis is meant to be a vision developed by OpenStack developers for OpenStack developers14:06
*** davidsha has joined #openstack-meeting14:06
*** njohnston has joined #openstack-meeting14:06
mlavalleit is expected to help guide, at a high level, how we develop OpenStack services14:06
mlavalleI encourgage the team to read and internalize it14:06
mlavalleand of course, if you have more ideas to add to it, please feel free to propose a follow up patch14:07
mlavalleany other announcements?14:07
mlavalleok, let's move on...14:08
mlavalle#topic Blueprints14:08
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:08
mlavalleThese are the blueprints that we are targeting for Stein-2: https://launchpad.net/neutron/+milestone/stein-214:09
mlavalleDoes anyone have an update / request on the blueprint you are working on?14:10
mlavalleok, I have a couple of updates / questions....14:11
mlavalleFirst, The StarlingX project has currently is based on the Pike release14:12
mlavalleThe goal by the end of Stein is to converge with master in all the projects14:12
mlavalleIn order to do that, there is a number of specs / patches that need to be merged, mostly in Neutron and Nova (minor things in Glance)14:13
*** mmethot has quit IRC14:13
mlavalleIn Neutron we are in very good shape beacause we have been working with them since the PTG in Denver14:13
mlavalleI am going to create a blueprint to track the patches / specs that we need to merge in Stein14:14
amotokigeneral question: where are they tracked?14:14
amotokiah... your last comment answered me14:14
mlavalleand I am also going to send to the ML the PDF with the "gap analysis" that describes them14:15
mlavalleamotoki: and also the PDF sheds light on them. Let's focues on the Neutron section14:15
amotokimlavalle: thanks14:15
mlavalleThe other point I question I want to ask is in regards to https://blueprints.launchpad.net/neutron/+spec/port-mirroring-sriov-vf14:16
mlavalledoes anyone know who is core in the Tap-as-a-service project?14:16
amotokiI think takashi is a core of taas14:17
mlavalleIt is not under Neutron governance, so we need help there14:17
mlavalleamotoki: perfect, I'll follow up with him14:17
*** mmethot has joined #openstack-meeting14:17
rubasovhere's the core list: https://review.openstack.org/#/admin/groups/957,members14:17
*** shrasool has joined #openstack-meeting14:17
amotokimlavalle: some other taas cores are from fujitsu. I can ask yushiro to check the status14:17
mlavalleamotoki: that would be very helpful. Thanks14:18
mlavallethanks rubasov14:18
*** Liang__ has joined #openstack-meeting14:19
yamamotokaz and I are somehow responsive if you ping. other cores are inactive.14:19
*** Liang__ is now known as LiangFang14:19
mlavalleyamamoto: thanks. there is a patch in tap as a service waiting for review for the port mirroring functionality14:20
mlavalleif you have time, please take a look14:20
mlavalleI know you have been giving feedback on the spec14:20
yamamotoi'm aware of the patch. a large patch will take longer :-)14:20
njohnstonProgress continues on bulk port update - battling an enginefacade error when testing with one of the changes but I think there are a couple of changes that are pretty close.14:21
mlavallethanks for the update njohnston :-)14:22
mlavalleanything else on blueprints?14:22
mlavalleok, next topic is14:23
mlavalle#topic Community goals14:23
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:23
mlavalleamotoki: any updates on policy in code?14:24
amotokire: policy-incode, I am preparing a email to dev list (now -discuss ML) to drop user_name:neutron from neutron policy.json to simplify the further effort.14:24
amotokias far as I checked no project uses advsvc explicitly, so I concluded it woudl be fine to send a mail to ML along with a devstack patch14:24
*** awaugama has joined #openstack-meeting14:25
mlavalleany other help you might need form the team?14:25
*** kiennt26 has joined #openstack-meeting14:26
mlavalleI take that as a no :-)14:26
amotokiperhaps I would like to ask testing and detail reviews.14:26
mlavallenjohnston: any updates on Python 3?14:26
amotokiAt least I should pass the test.14:26
njohnstonSo we're discussing Python 3 in the CI meeting, later today, but I put together an etherpad that summs up the current state of things (although I have not delved as far as I need to for the experimental jobs).  So I expect that will help drive the work that needs to be done.14:27
njohnston#link https://etherpad.openstack.org/p/neutron_ci_python314:27
mlavallenjohnston: do you need volunteers?14:28
njohnstonI would never say no to a volunteer.  :-)14:29
mlavalleso team, if you are interested in helping with the py3 community goals, please look at the etherpad and join the CI meeting at 1600UTC today in this same channel14:30
yamamotoi have a question about py314:30
*** rbudden has joined #openstack-meeting14:30
yamamotowhat importance should be for py3 related bugs these days?14:30
*** dustins has joined #openstack-meeting14:30
yamamotolike this https://bugs.launchpad.net/neutron/+bug/180417314:30
openstackLaunchpad bug 1804173 in neutron "Metadata proxy server SSL handshake problem if Python >= 3" [Undecided,New]14:30
*** liuyulong has joined #openstack-meeting14:30
mlavalleyamamoto: I think the same importance as any other bug14:31
mlavalleit really depends on the impact in the project14:31
*** finix has joined #openstack-meeting14:31
yamamotook. makes sense14:32
yamamotobtw i have no idea about the above bug so anyone familiar with the topic please help triage it :-)14:32
mlavalleLOL. Thanks14:32
* mlavalle notices yamamoto is already performing his bugs deputy duties :-)14:32
mlavalleslaweq: any updates on pre-upgrade checks?14:33
slaweqactually yes14:33
slaweqI wanted to raise for review patch https://review.openstack.org/#/c/615196/14:34
slaweqit's patch which will allow to use checks by entrypoints so e.g. stadium projects will be able to load their checks to neutron cli tool14:34
slaweqonce this will be done, we will be done with base framework I think14:34
slaweqand we will be ready to implement some real checks if that will be necessary14:35
mlavalleand the goal for Stein, right?14:35
slaweqactually goal is fine now as we have base cli tool merged already14:35
mlavalleahead of the curve.... Nice!14:35
mlavalleThanks for the update?14:36
slaweqyw? ;)14:36
mlavalleok, let's move on14:37
mlavalle#topic Bugs14:37
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:37
mlavalleLast week lujinluo was our bugs deputy14:38
mlavalleShe doesn't seem to be on-line14:38
mlavalleand I didn't find any message to the ML from her. Did anyone see it?14:38
mlavalleany bugs that should be discussed here today?14:39
bodencan I bring one up quick14:39
mlavalleof course14:39
openstackLaunchpad bug 1787420 in neutron "Floating ip association to router interface should be restricted" [Low,In progress] - Assigned to Michal Kelner Mishali (mkelnermishal)14:40
bodenfor which there's already a patch https://review.openstack.org/#/c/599572/14:40
bodenlooks like we are still waiting on a response from the drivers team on the patch?14:40
mlavalleboden: mhhh. I'll take a look today14:41
bodenmlavalle thanks14:41
liuyulongWe met the but https://launchpad.net/bugs/1803919 locally last week. And I added a patch set here: https://review.openstack.org/#/c/618720/14:41
openstackLaunchpad bug 1803919 in neutron "[L2] dataplane down during ovs-agent restart" [Undecided,In progress] - Assigned to LIU Yulong (dragon889)14:41
mlavalleliuyulong: thanks, will take a look at it14:43
mlavalleThis week, our deputy is yamamoto, who, as you have noticed, is already hard at work. Thanks!14:43
mlavallelet's move on14:43
mlavalle#topic neutron-lib14:44
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:44
mlavalleboden: you are up14:44
* mlavalle has an update for boden14:44
bodengo ahead mlavalle14:44
mlavalleI had conversations with some people regarding networking-sfc. I targeted people I though have interest in the project, since their own projects depened on it14:45
mlavalleThis people are: the Tacker PTL. He indicated he is available to help to merge patches14:45
bodenmlavalle; ok we can see how it goes... I think SFC is behind already so I'll have to take some time to submit some patches to get them up to date14:46
mlavallein the OPNFV community, they also use networking-sfc. In fact, they have a sfc project that depends on it. Manuel Buil(mbuil) is the PTL and he has also accepted to help merging patches14:46
mlavalleI talked to him in Berlin14:47
mlavalleand finally, I also taked to tmorin, who also accepted to help. his project depends on it14:47
bodenthanks for taking the time to reach out to these folks14:47
mlavallethat's my update14:47
*** weshay_pto is now known as weshay14:47
bodenok I just have a brief update for neutron-lib14:48
amotokimlavalle: which project does mbull work on as PTL in OPNFV?14:48
mlavalleamotoki: the sfc project. I don't remeber the excat name14:48
amotokithanks, my colleague work on OPNFV actively and I will let him know this.14:48
mlavalleand it is mbuil14:48
mlavalleamotoki: ^^^^14:49
amotokii made typo... :(14:49
mlavalleHe is based out of Spain, so closer to you in time zones14:49
mlavalleboden: go ahead14:49
bodenI know we just released 1.20.0, but I'd like to plan another release in the near future; maybe next week after the holiday.. there's a few patches I need for some of the decouple-db work14:49
mlavallethat is fine with me14:50
bodenstill waiting for https://review.openstack.org/#/c/615941/  but after that lands I'd be ready to do a release14:50
bodenother than that, just business as usual.. moving pretty slow this release, but I won't whine too much about it :)14:50
bodenand that's it for me14:50
mlavallein fact I have some changes to the extension definition for qos rules alias, based on my experience with https://review.openstack.org/#/c/613820/14:51
yamamotoboden: thank you for your patience with subprojects14:51
mlavalleso the new release is timely for me14:51
mlavalleboden: yes, you do great job on that14:51
bodenthanks guys.. nothing else from me14:52
mlavalleI don't see hongbin on line, so we will skip os-ken14:52
mlavalle#topic On demand agenda14:52
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:52
mlavalleAnything else we should discuss today?14:52
*** munimeha1 has joined #openstack-meeting14:53
mlavalleok, I give back 5 minutes to your busy days14:54
mlavalleHave a great week14:54
*** boden has left #openstack-meeting14:54
mlavalleand happy Thanksgiving for those in the USA14:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:54
openstackMeeting ended Tue Nov 20 14:54:24 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-11-20-14.00.html14:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-11-20-14.00.txt14:54
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-11-20-14.00.log.html14:54
amotokihappy holidays!14:54
*** kiennt26 has left #openstack-meeting14:58
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Nov 20 15:00:18 2018 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. 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_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
* mlavalle welcomes back ralonsoh as the chair of this meeting \o/15:01
ralonsohthanks! I'll do my best today15:01
*** efried is now known as efried_pto15:02
ralonsohplease, if I miss something, say it15:02
ralonsohlet's start15:02
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:02
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:02
slaweqhi, sorry for being late :)15:02
ralonsohI have started again pushing an old patch to have egress QoS in physical and ext bridges, but not tunnel15:03
*** shintaro has joined #openstack-meeting15:03
ralonsohtunnel bridges egress QoS must be addressed in other patch15:03
ralonsoh#link https://review.openstack.org/#/c/406841/15:03
mlavallethanks for picking this up15:03
ralonsohthis is just an initial draft15:04
ralonsohlet's see if I can finish it now15:04
mlavalleand pretty sure you will :-)15:04
ralonsohok, next one15:04
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/172757815:05
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:05
ralonsoh#link https://review.openstack.org/#/c/558986/15:05
mlavallethat one is being taken care of by my colleague Zhabo15:05
ralonsohis still WIP15:05
mlavalleyes, he is focused right now on three features in Octavia15:05
ralonsohand seems not to be progress since Oct15:05
mlavallebut he is commited to come back to this one in this cycle15:06
ralonsohok, so we can wait for this one15:06
ralonsohI'll skip it15:06
ralonsohnext one15:06
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/175704415:06
openstackLaunchpad bug 1757044 in neutron "[RFE] neutron L3 router gateway IP QoS" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:06
ralonsohPatches in progress:15:06
ralonsoh#link https://review.openstack.org/#/c/424468/ - server side patch,15:06
ralonsoh#link https://review.openstack.org/#/c/568526/ - agent side patch,15:06
mlavalleI'll review them this week15:07
mlavalleThey are in my pile15:07
ralonsohagent side has one +215:07
ralonsohsame as server side15:07
mlavalleI feel the pressure15:07
ralonsohI'll review them this week to (two more to my pile)15:08
mlavalleralonsoh: thanks. I was about to ask15:08
ralonsohany comment on those ones?15:08
mlavallenot from me15:09
ralonsohok, next one15:09
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/177762715:09
openstackLaunchpad bug 1777627 in neutron "RFE: QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel)15:09
ralonsoh#link https://review.openstack.org/#/c/613820/15:09
mlavalleit's good to go from my point of viw15:10
ralonsohok, another one to the review backlog fro everyone15:10
mlavalleplease note that based on the experience with this patch, I'll update the api-ref and the extension definition ijn neutron-lib15:10
ralonsohwhy are not you pushing the change to neutron-lib now?15:11
mlavalleI'll do it this week15:11
mlavallejust lack of time in Berlin15:12
ralonsohsure, busy week15:12
ralonsohnext one15:12
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:12
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Lajos Katona (lajos-katona)15:12
rubasovslow progress with open patches during the summit15:13
ralonsoh#link https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)15:13
mlavallerubasov did a great demo last week15:13
*** shintaro has quit IRC15:13
mlavalledespite having to wrestle to submission the projection equipment15:13
rubasovwe'll have a youtube video of the presentation done together with mlavalle and gibi soon15:13
ralonsohonce you have it, please share it!15:14
*** edmondsw has joined #openstack-meeting15:14
*** Luzi has quit IRC15:14
mlavalleit was 6pm on the last day of the summit and rubasov had the audience spellbound with a CLI demo15:14
rubasovwith lajoskatona we plan to have a bit more focus in the coming weeks and produce a new set of changes15:14
rubasovralonsoh: will do15:14
rubasovmlavalle: thanks for the flattery15:15
ralonsohabout the patches, only in neutron there are still 7 ongoing patches: https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open)15:15
rubasovlajoskatona's open patches are all close to being merged15:16
ralonsohso I encourage everyone to take a look at them15:16
rubasovso the number will be lower soon15:16
ralonsohis a big feature, I now15:16
ralonsohany tech problem you want to talk about?15:17
rubasovand we made an update to our todo etherpad: https://etherpad.openstack.org/p/QoS_minimum_bandwidth_allocation_in_Placement_API15:17
rubasovit's quite complex15:17
rubasovso I only recommend it for the brave15:17
mlavalleI think the brave includes everybody in this meeting15:17
*** hle2 has quit IRC15:18
mlavalleralonsoh runs bulls every year in Panplona15:18
mlavalleand El Comandante in Poland is fearless15:18
ralonsohsure...... hehehee15:18
rubasovwow :-)15:18
rubasovand that's about all from me15:19
ralonsohthere are a couple more RFEs15:19
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178779215:19
openstackLaunchpad bug 1787792 in neutron "[RFE] Does not support ipv6 N-S qos" [Wishlist,New]15:19
mlavallethanks rubasov lajoskatona.... great work15:20
ralonsohis there any update or new comment on these one?15:20
mlavalleI'll start working on this one when I finish the rules alias15:20
ralonsohwe'll update the status next week15:21
mlavallein fact, if you can provide you thoughts in the RFE, I will appreciate it a lot ralonsoh15:21
ralonsohwhere is the link?15:21
ralonsohI don't see it in the bug15:21
mlavalleralonsoh: I meant the RFE itself. If you have any thoughts or advice, it will be appreciated15:22
mlavalleor guidance15:22
ralonsohoh, you said the bug itself15:22
ralonsohadded to my pile15:22
ralonsohok, last one15:23
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178779315:23
openstackLaunchpad bug 1787793 in neutron "[RFE] Does not support shared N-S qos per-tenant" [Wishlist,New]15:23
ralonsohthis one is tricky15:23
ralonsohis LIU here?15:24
mlavalleand I am also willing to work on it15:24
ralonsohliuyulong, you have two patches15:24
ralonsoh#link https://review.openstack.org/#/c/568526/15:25
ralonsoh#link https://review.openstack.org/#/c/568526/15:25
ralonsohfrom the other RFE15:25
ralonsohyou stated that those patches could resolve this problem15:26
* mlavalle listens15:26
liuyulongHmm, this bug is for share bandwidth for entire tenant15:26
liuyulongThe patches I submitted there, it is for traditional router gateway IPs QoS.15:27
ralonsohyou said that handling QoS in the router gateway15:27
ralonsohthe limits will be shared by the tenant15:28
ralonsohliuyulong, ?15:29
liuyulongThis bug is something like this. Users buy a bandwidth once from the provider.15:29
liuyulongThen share this bandwidth crossing the tenant's floating IPs, gateway IPs, VPN IPs, and so on.15:30
mlavalleand ports15:30
ralonsohbut what happens if none of the tenants are using FIPs?15:31
ralonsohand you are not limiting physically the BW in the host15:31
ralonsohfor example, if you are not using DVR15:31
liuyulongYes, this is the point, they want share a bandwidth for floating IPs.15:32
mlavallecan we debate / disucss in the RFE?15:32
ralonsohsure, that's better15:32
mlavalleif we can come up with a nice design15:32
liuyulongAnd dvr or different routers' floating IP make things a little complicated.15:32
mlavalleI'll be glad to work on the implementation15:33
ralonsohlet's discuss in the RFE15:33
ralonsohok, no more RFEs15:33
ralonsohlet's go to bugs15:33
ralonsoh#topic Bugs15:33
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:33
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178400615:33
openstackLaunchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)15:33
mlavalleralonsoh: but I think you are on to something. If we can put something in from of all the tenant resources, we limit the bandwidth in that something15:34
*** zaneb has quit IRC15:34
ralonsohwe need to be cautious on having a bottle neck, adding something like a unique pipe for all the traffic15:35
*** zaneb has joined #openstack-meeting15:35
ralonsohmlavalle, #link https://bugs.launchpad.net/neutron/+bug/178400615:35
openstackLaunchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)15:35
ralonsohany update?15:35
mlavalleno, didn't have time to work on it15:36
mlavalleif anyone has bandwidth, feel free to take it. otherwiese, I'll get to it later15:36
ralonsohI don't have now15:36
mlavalleI'm glad to be on the hook15:37
mlavallejust don't want to hoard bugs15:37
ralonsohwe have too much backlog sometimes...15:38
ralonsohok, we have the last one15:38
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178518915:38
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Undecided,In progress] - Assigned to Brian Haley (brian-haley)15:38
ralonsohstill no answer to liuyulong questions15:39
ralonsoh#link https://review.openstack.org/#/c/596637/15:39
ralonsohIMO, the solution is ok15:39
ralonsohbut questions marked by liuyulong are fair15:39
ralonsohand we should have this information to validate this solution15:40
mlavalleI'll ping Brian15:40
*** lpetrut has quit IRC15:40
ralonsohI think we should reproduce this environment to test liuyulong questions15:41
ralonsohanyway, I'll try to reach Brian too15:41
*** finix has quit IRC15:42
ralonsohdoes anyone have any other bug not listed?15:42
*** finix has joined #openstack-meeting15:42
ralonsohok, other opens15:43
ralonsoh#topic Open Discussion15:43
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:43
mlavallenone from me15:44
*** yamamoto has quit IRC15:44
ralonsohok, we can finish the meeting today15:44
ralonsoh(do you remember the command to close the meeting?)15:45
ralonsoh(I'm still learning)15:45
ralonsohthank you all!15:45
njohnstongood job ralonsoh :-)15:45
rubasovthank you guys15:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:45
openstackMeeting ended Tue Nov 20 15:45:57 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-11-20-15.00.html15:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-11-20-15.00.txt15:46
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-11-20-15.00.log.html15:46
ralonsohsee you all15:46
*** liuyulong has quit IRC15:47
*** zaneb has quit IRC15:51
*** armax has joined #openstack-meeting15:53
*** tssurya has quit IRC15:55
*** shrasool has quit IRC15:57
slaweq#startmeeting neutron_ci16:01
openstackMeeting started Tue Nov 20 16:01:48 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:01
openstackThe meeting name has been set to 'neutron_ci'16:01
slaweqlets start last of today's meetings then :)16:02
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqmlavalle/slaweq to continue debugging issue with not reachable FIP in scenario jobs16:02
mlavalleI continued doing that16:02
mlavallesince I came back from berlin16:03
mlavalleand before leaving as well16:03
slaweqI didn't have time to look at this one, but I found some issue related to https://bugs.launchpad.net/neutron/+bug/171730216:03
openstackLaunchpad bug 1717302 in neutron "Tempest floatingip scenario tests failing on DVR Multinode setup with HA" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)16:03
slaweqand it maybe can help with this one too16:03
mlavalleI've been comparing a "good run" with "bad run"16:03
slaweqI sent some patch already: https://review.openstack.org/#/c/618750/16:03
slaweqthis my patch can help with dvr jobs only16:04
slaweqI saw issues like that in quite many test runs, e.g. in http://logs.openstack.org/24/618024/5/check/neutron-tempest-dvr-ha-multinode-full/d27f183/logs/16:05
mlavalleis this going to address also https://bugs.launchpad.net/neutron/+bug/1795870?16:05
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:05
*** finix has quit IRC16:05
slaweqif You had in l3-agent logs something like: http://logs.openstack.org/24/618024/5/check/neutron-tempest-dvr-ha-multinode-full/d27f183/logs/subnode-2/screen-q-l3.txt.gz?level=ERROR then it should help16:06
slaweqif not, then it's different issue probably16:07
*** hongbin has joined #openstack-meeting16:07
mlavalleI was thinking of a different aproach16:07
mlavallewe recently merged https://review.openstack.org/#/c/609924/16:08
mlavallethis fixes a situation where the fip is associated to a port before the port is found16:09
mlavalleas a consequence, the fip is create in the snat node, right?16:09
mlavallenow, when the port is bound, the patch fixes the migration of the fip / port to the corresponding node16:10
mlavallea compute presumably16:10
mlavallenow, let's look at the code of test_trunk_subport_lifecycle:16:10
mlavalleit creates the port and associates it to a fip16:11
mlavalleso in a dvr env, that fip is going to the snat node16:11
mlavalleand then the server is created in L7616:12
mlavalleso the migration starts16:12
*** zaneb has joined #openstack-meeting16:12
mlavalleit is possible that the bug https://bugs.launchpad.net/neutron/+bug/179587016:12
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)16:12
mlavalleis a consequence of the fip not being ready in the compute, because it is migrating16:13
mlavalleit is a race that is not fixed by https://review.openstack.org/#/c/609924/16:13
*** shrasool has joined #openstack-meeting16:13
slaweqit can be something like that16:14
slaweqmaybe this FIP is configured in both snat and fip- namespaces then?16:14
mlavallenoiw the trunk test bug happens 95% of the time with DVR16:14
slaweqas in our gates all nodes are dvr_snat nodes16:15
*** weshay is now known as weshay_pto16:15
mlavalleso I intend to change the test script16:15
mlavalleto create and associate the fip after the server16:15
mlavalleand see what happens16:15
mlavallemakes sense?16:16
slaweqyes, totally :)16:16
mlavalleso I propose the following:16:16
mlavalle1) let's merge your patch first and see the effect on the trunk bug16:16
mlavalle2) Then let's change the trunk test script and see the effect16:17
mlavallethis way we learn what fix is having an efect or not16:17
slaweqok, I will address comments on my patch today (or tomorrow morning)16:17
mlavalleand the other think that I propose is let's track the trunk test failure independently of the bug you are fixing16:18
mlavallebecause in the case of the trunk stuff, it might be something else16:18
slaweqone more question, if it's like You are described it, is it still happens so often, or maybe it's now fixed by https://review.openstack.org/#/c/609924/11 ?16:18
mlavalleI mean the problem might be in the trunks code for example16:18
*** artom has joined #openstack-meeting16:19
*** artom has quit IRC16:19
mlavalleit's still happening after merging that patch16:19
mlavalleI saw it yesterday16:19
slaweqsure, I just raised this patch here as I saw issues like that in many tests different tests (trunk also) - only common thing was not reachable FIP16:19
*** artom has joined #openstack-meeting16:19
slaweqok, so lets do it as You described and we will see how it will be16:20
mlavalleI am just trying to be disciplined and merge fixes orderly, to learn what fixes what16:20
mlavallemakes sense?16:20
slaweq#action mlavalle to continue tracking not reachable FIP in trunk tests16:20
slaweqsure, makes sense for me :)16:20
*** e0ne has quit IRC16:21
slaweqI think we can go on to the next one then, right?16:21
mlavallethanks for listening :-)16:21
slaweqok, so the next one is:16:21
slaweqnjohnston rename existing neutron-functional job to neutron-functional-python27 and switch neutron-functional to be py316:21
slaweqnjohnston: any updates?16:22
njohnstonbcafarel already had that underway before we had talked about it: https://review.openstack.org/#/c/577383/16:22
njohnstonIt is still showing the same issue with subunit.parser that I have been stumped by: http://logs.openstack.org/83/577383/12/check/neutron-functional/e02bd4f/job-output.txt.gz#_2018-11-13_14_10_04_21253616:23
slaweqbcafarel: are You around? Do You need help with this one?16:23
njohnstonbut if I or anyone else has a eureka moment and figures out what in the functional test harness is not py3 ready, then the change is ready to go16:23
njohnstonbcafarel and I have talked about it, when last we chatted he also had not had luck finding the py3 string handling incompatibility that is causing the error16:24
bcafarelyeah basically what njohnston said16:24
*** yamamoto has joined #openstack-meeting16:24
slaweqok, I will try to take a look this week on it if I will have few minutes16:24
bcafarelI will try to catch this issue again, but will not mind at all if someone solves it in the meantime :)16:24
slaweqok, let's move forward then16:25
slaweqnjohnston make py3 etherpad16:25
slaweqI guess it's https://etherpad.openstack.org/p/neutron_ci_python3, right?16:25
njohnstonAs mentioned in the neutron team meeting, that is up16:25
njohnston#link https://etherpad.openstack.org/p/neutron_ci_python316:25
slaweqthx njohnston :)16:25
slaweqI will go through it and will start doing some patches with conversion to py3 as I have some experience with it already16:26
njohnstonI need to flesh out the experimental jobs a bit16:27
njohnstonbut I figure it will be a while before we get tot hose anyway16:27
njohnston* to those16:27
slaweqI think that we should revisit which experimental jobs we still need :)16:28
*** shrasool has quit IRC16:28
njohnstonyes, many of the legacy ones may be able to be removed, like legacy-tempest-dsvm-neutron-dvr-multinode-full16:29
slaweqyes, I will take a look at them too16:29
slaweq#action slaweq to check which experimental jobs can be removed16:29
njohnstonsince that is covered already by neutron-tempest-dvr-ha-multinode-full in check and gate queues16:29
slaweq#action slaweq to start migrating neutron CI jobs to zuul v3 syntax16:29
*** yamamoto has quit IRC16:29
njohnstonMuch appreciated slaweq, my attempts at zuul v3 conversions have taught me humility16:30
slaweqI spent some time on converting neutron-tempest-plugin jobs to it so I understand You :)16:31
slaweqok, lets move to the next one then16:31
slaweqnjohnston check if grenade is ready for py316:31
njohnston    Looks like Grenade has py3 supported and has a zuul job defined for py3 by mriedem https://github.com/openstack-dev/grenade/commit/7bae489f38f8f0c82c8eb284d1841ef68d8e9a4316:31
slaweqso we should just switch to use this one instead of what we are using now, right?16:32
mriedemstill need https://review.openstack.org/#/c/617662/16:33
mriedembut maybe unrelated to what you care about16:33
*** jamesmcarthur has joined #openstack-meeting16:34
njohnstonNo, I think that is excellent16:35
njohnstonI think we probably make use of that template16:35
njohnstonSo we can either base our jobs off of that zuul template or just use it outright16:35
slaweqI'm now comparing our definition of neutron-grenade job with grenade-py3 job16:36
slaweqI see only one difference, in grenade-py3 there is no openstack/neutron in required projects16:37
slaweqwill we have to add it if we will use this job, or it's not necessary?16:37
mriedemi believe that comes from legacy-dsvm-base16:37
mriedembut i'm never really sure how that all works16:37
*** ayoung has joined #openstack-meeting16:38
*** ayoung has left #openstack-meeting16:38
slaweqahh, so we don't need to define it in our template16:38
mriedemi do'nt think it's needed,16:38
mriedemgrenade-py3 is stein only,16:38
mriedemand devstack has defaulted to neutron since i think newton16:38
slaweqthx mriedem16:38
slaweqso IMO we could switch to use this template in neutron's .zuul.yaml file16:39
slaweqnjohnston: will You do it then?16:39
mriedemcorrect, neutron is the default since ocata, but doesn't matter for this anyway https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L20116:40
slaweq#action njohnston to switch neutron to use integrated-gate-py35 with grenade-py3 job instead of our neutron-grenade job16:40
slaweqthx mriedem, that sounds very good for us :)16:40
slaweqok, so lets move on to the next one then16:41
slaweqslaweq to check Fullstack tests fails because process is not killed properly (bug 1798472)16:41
openstackbug 1798472 in neutron "Fullstack tests fails because process is not killed properly" [High,In progress] https://launchpad.net/bugs/1798472 - Assigned to Slawek Kaplonski (slaweq)16:41
slaweqI was checking that one16:41
slaweqand what I found is, that in some cases openvswitch-agent or sometimes neutron-server are not responding for SIGTERM at all16:42
slaweqand then tests are failing in cleanup phase as process is not stopped properly and timeout is raised16:42
njohnstonoh interesting16:42
mlavalledidn't we approve a patch for that yesterday?16:42
slaweqI did patch https://review.openstack.org/#/c/618024/ which should at least workaround it in tests16:42
slaweqmlavalle: yes :)16:42
slaweqI just wanted to do introduction for everyone ;)16:42
slaweqfor now it failed with some not related errors so I rechecked it16:43
slaweqit should help with such issues in fullstack tests16:43
slaweqok, next one16:43
slaweqmlavalle to check bug 179847516:44
openstackbug 1798475 in neutron "Fullstack test test_ha_router_restart_agents_no_packet_lost failing" [High,Confirmed] https://launchpad.net/bugs/179847516:44
mlavalleno time to check this one16:44
slaweqdo You plan to check that this week maybe?16:44
*** zaneb has quit IRC16:44
mlavalleno, I don't thinbk I'll time this week16:45
mlavalleThursday and Friday are holidays16:45
slaweqok, I will assign it to me but I will check it only if I will have some time for it16:45
slaweq#action slaweq to check bug 179847516:45
openstackbug 1798475 in neutron "Fullstack test test_ha_router_restart_agents_no_packet_lost failing" [High,Confirmed] https://launchpad.net/bugs/179847516:45
slaweqand the last one was:16:46
mlavalleGreat, thanks!16:46
slaweqslaweq to check why db_migration functional tests don't have logs16:46
slaweqyw mlavalle :)16:46
slaweqfor this last one I didn't have time16:46
slaweqso I will assign it to me for next week too16:46
slaweq#action slaweq to check why db_migration functional tests don't have logs16:46
slaweqok, that were all actions from previous week16:46
slaweqdo You want to add anything?16:47
mlavallenot from me16:47
slaweqok, lets move on then16:47
slaweq#topic Python 316:47
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:47
slaweqI think we discussed most things already :)16:48
njohnstonindeed :-)16:48
slaweqI just wanted to mention that fullstack tests are now running on py3 only:16:48
slaweq#topic Python 316:48
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:48
openstackRemoving item from minutes: #topic Python 316:48
slaweqso we don't have neutron-fullstack-python36 anymore16:49
*** zaneb has joined #openstack-meeting16:49
slaweqthx bcafarel and njohnston for that one16:49
njohnstonDid someone already submit a change to remove that from the grafana dashboard, or shall I do it?16:49
slaweqno, I think there is no such patch yet16:50
slaweqwould be good if You will do it :)16:50
slaweqthx for remember about that16:50
slaweq#action njohnston to remove neutron-fullstack-python36 from grafana dashboard16:50
njohnstonWill do, and I'll prep a second one one to match up with the change in functional tests with a proper depends-on16:50
slaweqthx njohnston16:50
slaweqok, so speaking about grafana16:51
slaweq#topic Grafana16:51
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:51
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:51
slaweqthere were quite big failure rates during the weekend on charts but there was not many jobs running then so I don't think we should focus on those16:53
slaweqexcept that, I think that most things are similar like it was two weeks ago16:53
slaweqone thing which I want to rais is failing neutron-tempest-postgres-full periodic job16:54
slaweqwe should check that one16:54
slaweqlooks like some nova issue, e.g.: http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/neutron-tempest-postgres-full/a52bcf9/job-output.txt.gz#_2018-11-18_06_59_45_18326416:56
slaweqand nova logs: http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/neutron-tempest-postgres-full/a52bcf9/logs/screen-n-api.txt.gz?level=ERROR16:56
slaweqmriedem: does it ring a bell for You ^^ ?16:56
mriedembut should be fixed16:57
mriedemoh nvm this is something else16:58
slaweqlast such issue is from today, http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/neutron-tempest-postgres-full/1de7427/logs/screen-n-api.txt.gz?level=ERROR16:58
mriedemok so the pg jobs are broken16:59
mriedemhas anyone reported a bug?16:59
slaweqnot me, I just noticed that in periodic job16:59
slaweqI will report a bug aftet this meeting16:59
slaweq(which is just over) :)17:00
slaweqok, thx for attending17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Nov 20 17:00:16 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-11-20-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-11-20-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-11-20-16.01.log.html17:00
slaweqand thx mriedem for Your help17:00
*** a-pugachev_ has joined #openstack-meeting17:00
*** a-pugachev has quit IRC17:04
*** a-pugachev_ is now known as a-pugachev17:04
*** fanzhang has quit IRC17:06
*** shrasool has joined #openstack-meeting17:07
*** a-pugachev has quit IRC17:17
*** jamesmcarthur has quit IRC17:18
*** shrasool has quit IRC17:20
*** davidsha has quit IRC17:22
*** lpetrut has joined #openstack-meeting17:24
*** yamahata has quit IRC17:26
*** sridharg has quit IRC17:28
*** kopecmartin is now known as kopecmartin|off17:28
*** e0ne has joined #openstack-meeting17:31
*** lbragstad has quit IRC17:38
*** iyamahat has joined #openstack-meeting17:38
*** rossella_s has quit IRC17:40
*** lbragstad has joined #openstack-meeting17:41
*** e0ne has quit IRC17:44
*** shrasool has joined #openstack-meeting17:52
*** e0ne has joined #openstack-meeting17:57
*** yamahata has joined #openstack-meeting17:59
*** zbitter has joined #openstack-meeting18:04
*** zaneb has quit IRC18:06
*** zbitter is now known as zaneb18:18
*** mlavalle has left #openstack-meeting18:24
*** efried_pto is now known as efried18:28
*** armax has quit IRC18:29
*** pcaruana has quit IRC18:47
*** anteaya has joined #openstack-meeting18:51
*** yamahata__ has quit IRC18:52
*** AJaeger has joined #openstack-meeting18:54
clarkbInfra meeting will be starting in just a minute or two18:59
clarkbAnyone here for the meeting?19:00
* fungi wonders how many others are still hungover19:00
*** ralonsoh has quit IRC19:00
clarkbI didnt' feel too bad yesterday but then I was awake at 2am this morning and well today hasn't gone as well19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Nov 20 19:01:18 2018 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
gary_perkinso/ is here for the meeting :)19:01
*** rfolco has joined #openstack-meeting19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
clarkb#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
fungii missed adding a reminder about the largeish ml merge i enacted yesterday19:03
clarkbThis week is a big holiday week in the USA. This means in addition to jet lag lag you'll likely find that many of us in this country will be ignoring our computers later this week19:03
clarkbfungi: that seems like it is worth a reminder here though19:03
funginote: i'm not ignoring my computer, i'm just ignoring people i don't like (kidding!)19:03
clarkbfungi did the openstack-dev/etc into openstack-discuss switch as discussed for a few months since the PTG19:03
clarkbif you haven't joined the -discuss list now is an excellent time to do so19:04
*** apetrich has quit IRC19:04
fungiwe're almost at 350 subscribers now19:04
clarkbI'm personally intending to try and be around today and tomorrow with various errands interspersed in today (to convince my body that it shouldn't fall asleep at 5pm). But then I'm afk Thursday to Monday19:04
fungii'll be offline some of my usual thursday to meet friends for chow19:05
fungiotherwise i should mostly be around19:05
* AJaeger is not celebrating Thanksgiving but travelling all of next week...19:05
anteayahappy thanks chow19:05
fungias much as i ever am the week after a summit anyway19:05
clarkb#topic Actions from last meeting19:06
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:06
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-11-06-19.01.txt minutes from last meeting19:06
clarkbNo explicit actions called out and considering we have a lot ot talk about post summit I'm inclined to push forward19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkb#topic Update Config Management19:07
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:07
clarkbI believe the changes that ianw wanted to get in to make dockering possible have happened19:07
clarkbother than that I'm not sure we've made much progress on this effort since we last met since summit and associated demands were happening19:07
*** corvus has joined #openstack-meeting19:08
ianwhttps://review.openstack.org/#/c/605585/ is ready for review, that installs docker on control plane19:08
corvussorry i'm late19:08
clarkbmordred: ianw Mathias Gutehall mentioned on the infra mailing list that there was interest in helping with the dockering. I've suggested that you two may be the best points of contact for that19:08
clarkbI'm happy to help there as I can but most likely as a reviewer19:08
ianwyes, we've had a brief chat.  i think the next thing to do is to get a hello-world type thing working ontop of 60558519:08
clarkb#link https://review.openstack.org/#/c/605585/ install docker on the control plane (ready for review)19:08
ianwthen get an ipv6 hello-world working too ... this will i think be harder, but required for anything we deploy19:09
corvusianw: awesome!19:09
clarkbah I know this change. I'll rereview it before I take off for errands19:09
ianwclarkb: it's a unix system, i know this!19:10
clarkbvelociraptors don't stand a chance19:10
*** armax has joined #openstack-meeting19:10
corvuswhy don't the iptables tests work?19:11
clarkbcorvus: I had to update the iptables tests to accomodate the stuff docker adds19:11
corvuslike -- i get that dockers doing other weird stuff, but shouldn't the rules we check for still be there?19:11
clarkbcorvus: yup they are still there, but the order changes (docker prepends iirc)19:11
clarkboh latest patchset removed the test19:12
corvusgotcha... maybe we could reduce the scope of the iptables test then, so we're still at least checking that, say, snmp is open19:12
clarkbianw: I had updated it so that the existing test would work with docker I thought. But doing somethign like ^ is probably good enough too19:12
fungigranted if the block rule came first and we weren't checking at least some ordering, that could be problematic19:12
clarkbI don't think docker adds any block rules19:13
clarkbin any case we should be able to test the iptables + docker and iptables + !docker case19:13
corvusfungi: yeah, we could assert that snmp is open and our block rule is after that19:13
clarkbAre there other config mgmt update changes or items we'd like to talk about before moving on?19:14
ianwok, make review comments and i'll look at it :)19:14
corvusclarkb: yep, and i think testing is worthwhile to prevent a regression; seems easy to do here19:14
*** yamamoto has joined #openstack-meeting19:14
corvusianw: done :)19:15
clarkb#topic Storyboard19:15
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:15
fungiwe yakked about some storyboard stuff at the forum last week19:16
clarkbThere was a good storyboard migration blockers session in Berlin. Seemed like it mostly boiled down to improving performance and error handling as well as some specific needs by various projects19:16
*** apetrich has joined #openstack-meeting19:16
clarkbthe other item that came up was easy mode file a bug tooling19:16
clarkbas is the current story creation process is quite involved and makes more sense on the backend for a developer planning work19:16
fungi#link https://etherpad.openstack.org/p/BER-Contrib-Portal-Feedback19:16
clarkbI don't think there were any real surprises though which is good19:17
corvuswhy is that called 'contrib portal'?19:17
fungii think it must have gotten repurposed from a contributor portal session19:18
fungii wondered that myself19:18
corvusok.  it's not relevant, that's the main thing to know i guess.  :)19:18
corvus(i thought i mispercieved what was happening)19:18
*** jamesmcarthur has joined #openstack-meeting19:19
fungithere's also a BER-Contrib-Portal pad which i think was for that19:19
fungiguessing it was a cut-n-paste error and we were all too jetlagged on tuesday to notice19:19
clarkbfungi: diablo_rojo_phon anything else worth calling out from that session?19:20
clarkbLooks like we had pretty decent note taking :)19:20
funginot that i'm aware of19:20
clarkbMoving on then19:20
clarkb#topic General Topics19:20
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:20
clarkbI'll start with a quick summit recap. One of the sessions was on dealing with timezones and language barriers and a suggestion that came out of that was leaning on meeting agendas more explicitly and only having meetings if we have an agenda19:21
diablo_rojo_phonI definitely messed up the Etherpads and rather than lose the edit history just kept the confusing name.19:21
diablo_rojo_phonJust got into SeaTac :)19:22
clarkbthe goal here is to allow people in less convenient timezones for the meeting to sleep/have dinner/etc if the meeting doesn't need to happen or doesn't have an agenda that affects them19:22
fungithanks for the deets diablo_rojo_phon!19:22
clarkbAlso gives people a chance to prepare their thoughts on topics19:22
anteayaclarkb: was the timezones and language barriers aimed at infra? or was it openstack wide?19:22
clarkbI've proposed to the infra mailing list that we require agenda updates 24 hours before the start of the infra meeting and if there is no update at that time then cancel the meeting19:22
clarkbanteaya: was openstack wide19:22
*** e0ne has quit IRC19:22
*** jamesmcarthur has quit IRC19:23
clarkbdo we think this proposal is worthwhile? so far the reception on the mailing list has been positive19:23
fricklerI think it's a good proposal19:23
anteayaI'd like to add that we have at least one meeting every four weeks19:23
clarkbI'm happy to do my best to send notes to the mailing list signalling if (or not) we will have a meeting around 1900UTC monday19:23
gary_perkinsI'm in the UK, so +119:23
anteayaso if we have an agenda lull we at least have a cadence for some sort of meeting19:23
clarkbanteaya: can probably do that informally with a catch up agenda item if we otherwise wouldn't meet19:24
fungii'm just not a fan of holding meetings we don't need, so also in favor ;)19:24
clarkbanteaya: I expect we'll end up having meetings closer to every other week19:24
corvusclarkb: ++ plan; ++ anteaya's idea19:24
clarkbwe can also tweak it as we go19:24
anteayasure, I'd just like something in the proposal, so that in years to come it is written down19:25
anteayaand thanks19:25
corvusi think in practice, it'll be at least every other week.  we often have something to talk about here :)19:25
fungiusually someone at least adds something to the agenda, yes19:25
fungii wouldn't be surprised if we still hold it most weeks19:26
anteayaoh I agree, I don't think we will only meet once per month19:26
anteayaI just like a backstop19:26
clarkbok how about this for an ammended proposal " THe infra team requires an updated meeting agenda 24 hours prior to the meeting time otherwise the meeting will be cancelled. If we don't have a meeting for 4 weeks we should have a catch up agenda item added by the chair"19:26
fungibut we'll need to be more diligent about adding things to the agenda sooner19:26
anteayaclarkb: +119:26
fungithat wfm. also not necessary to spell out in the agenda but if you have an agenda item to add in the final 24 hours it probably goes on the backlog for the next week's agenda19:26
anteayayes, this is where I miss pleia219:26
anteayashe was very attentive to meeting things19:27
fungii miss pleia2 for many, many reasons. she's still lurking in here though!19:27
clarkbWe can start with that process next week then. I'll do my best monday morning to check in on agenda and send email as necessary from the beach house19:27
ianwi'm not about this cancelling but I'll respond on list, seems a better place to discuss it19:27
anteayayes, not the only thing I miss her for19:27
* corvus waves at pleia2 19:27
clarkbianw: ya I'll follow up there to19:27
clarkbthe other summit session that impacts us is the opendev feedback session.19:28
corvusianw: was that last missing a word?19:28
anteayaclarkb: beach house has a lovely ring to it19:28
clarkbIf I had to sum that one up the tl;dr would be communicate communicate communicate19:28
fungigood thing that session was also a means of communicating!19:28
clarkbThere didn't seem to be any major sky is falling concerns but there was the ask that we keep bodies like the TC informed of planning. I think we've managed to communicate well so far, we just have to keep at it19:29
anteayaI will say again I hope the team will continue to be available in the openstack-infra channel19:29
fungii don't think we intend to cease having an irc channel19:30
clarkbanteaya: yup I don't expect we'll move soon and if/when we do move we can set things up with freenode to redirect people to the correct location19:30
anteayaI hope it has infra in the name of the channel if the openstack is dropped19:30
anteayaand thank you19:30
clarkbour attentiveness and willingness to help was called out. People don't want that to go away and I don't expect it to19:31
clarkbthe TC is particularly interested in any plans for reorganizing git repos in gerrit19:31
*** jamesmcarthur has joined #openstack-meeting19:31
anteayawhen you say called out do you mean some find it lacking currently?19:31
clarkbanteaya: no they found it helpful today and don't want that to change19:31
anteayaah, maintainance of status quo19:32
clarkb(I don't think we intend for that to change)19:32
* fungi doesn't intend to try to change it19:32
*** a-pugachev has joined #openstack-meeting19:32
anteayayeah, I didn't think so19:32
anteayacalled out has many meanings for me, I guess19:32
fungiexcept finding ways to get even better at it, if possible19:32
anteayaI'm not a fan of cloning19:32
clarkbI'm trying to think if there were any other sessions that have a direct impact on the infra team19:33
clarkbany other summit recap related items others want to bring up? or questions from those that weren't able to attend?19:34
fungithe summit feedback session sort of impacts us, insofar as one of our infra-root sysadmins should see if we can figure out how to roll back an edit to the pad for it19:34
anteayaI hope you got to a beirgarten?19:34
fungisomeone autotranslated the first half the pad into japanese after the session ended19:34
clarkbfungi: if the pad isn't broken corrupt I think we can rell back to an older version with the api19:34
fungiyep, i was just digging up the api docs19:35
clarkbssbarnea|bkp2: corvus: re gertty is that still something we need/want to discuss in this meeting? or did that get sorted out?19:35
clarkbalright the next agenda item is having an infra topic for the new -discuss list19:36
clarkb#link https://etherpad.openstack.org/p/common-openstack-ml-topics openstack-discuss topics listing19:36
clarkbcorvus: ^ I think you added this19:36
corvusyep.  i don't have a position to advocate, mostly wanted to see if folks thought we should19:37
corvusor how we should use the new list to communicate to folks about infra changes19:37
anteayaI think we should19:37
fungiseems like a fine addition. [infra] works for that case19:37
fricklerisn't "infra" a team name already like "qa"?19:37
clarkbyes, I think it will be helpful since the alternative is likely to be filtered into the bitbucket19:37
clarkband then people will miss our updates19:37
corvus[infra] for "hey should we tweak a thing?" and [infra][all] for "gerrit is being upgraded" ?19:38
fungifrickler: future status as an openstack team is probably up in the air19:38
clarkbfrickler: it is technically "infrastructure" I think19:38
clarkbcorvus: ++19:38
fungicorvus: i like19:38
corvusof course "all" is now more than just "all developers" it's "all people interested in openstack"19:38
fungiadding [all] in the case of announcements basically19:38
corvushrm.  maybe we should refrain from [all] except in the most highly impactful cases, and use [infra][dev] for "gerrit is being upgraded"?19:39
fungithere are plenty of people in the community who don't engage in software development but probably still care about bits of the community infrastructure19:39
*** a-pugachev has quit IRC19:39
anteayaI'm a fan of using [all] judiciously19:39
corvusfungi: indeed; i certainly think it's widely applicable, but i don't have a read on how much.19:40
funginot sure any of us do yet19:40
fungiwe're all still figuring this out19:40
clarkbcorvus: I still feel like gerrit upgrades are an [all]? simply due to the large impact it is19:40
clarkb*impact it has19:40
clarkband maybe we scale that back if we get asked to?19:40
fungiopenstack-discuss [all] is still not on the same level as posting to openstack-announce at least19:40
anteayaI'd go the other way19:40
corvusi can buy the argument for [all]19:41
anteayause [infra][dev] to start and go to all if the feedback requests19:41
clarkbas fungi points out we are all learning and probably best thing is to try something and change if that doesn't work19:42
anteayaand put gerrti upgrade in the subject line19:42
corvuswe can also add [all] to, say, an initial announcement of a major change (such as a gerrit upgrade) and drop down to [dev] for followup scheduling messages, etc19:42
frickler+1 to anteaya, folks will just unsubscribe instead of complaining about too many mails19:42
clarkbcorvus: that might be a good compromise19:42
fungiyeah, all fine ideas in my opinion, we just need to be flexible (especially here at the beginning) until we work out a viable pattern19:42
anteayajust suggestions19:42
corvuswe can ask for feedback after our first message:  "did you enjoy receiving this message?"  "do you wish you had received this message?"  ;)19:43
fungii don't really have enough of a feel yet for which will work better, so use [infra] and apply your best judgement in adding other tags?19:43
anteayaha ha ha19:43
clarkbfungi: ++19:43
corvussounds good.  i'm glad we thought a bit about it.19:44
clarkbwe've also only got about ~16 minutes left and a couple important topics left so I think we should move on. I think we are all aware of how careful we should be using [all] and we can learn to see what works as we go19:44
clarkbNext on the list is an opendev update19:44
clarkbI believe we are waiting on dns registrar to be happy with dnssec?19:44
corvusyeah, jamesmcarthur has been very helpful in making requests to the registrar19:45
corvusapparently they are confused about our request to add dnskey records.  we're trying to convince them that the data we sent are correct, or at least find out more info about why they think it isn't.19:45
fungiand i have to assume we haven't heard any more because he hasn't heard any more yet19:46
clarkbcan (should) we set up the domain without dnssec to start?19:46
corvusthe glue records are said to be in place now, however, i think making requests to them in this manner is a bit like talking to a jinn -- i don't think we actually asked them to change the ns records to *use* the glue records.19:46
corvusso i reckon we need to explicitly ask for that too :)19:46
corvusclarkb: technically, yes, but i have to say i'm really not interested in it.19:47
corvusi *really* want sshkey records19:47
* fungi too19:47
fungii use them with my domains, very handy19:48
clarkbin that case I guess we wait for registrar to say more words about the problem?19:48
clarkbfungi and I may be able to followup with them and jimmy if necesary too (I think email is their primary form of communication)19:48
clarkbI'll check with jimmy if he thinks we can do anything else to help as well19:49
clarkbhe has some experience with this group19:49
fungivery confused e-mail, if my previous experiences with them are representative19:49
corvusit'd be one thing if requests like this took a day or two, but the fact that it's taking *weeks* is, honestly, pretty unworkable.19:50
jamesmcarthurclarkb: I'm waiting to hear back from them after rebutting their last assertion that the DNSSEC key is wrong.19:50
jamesmcarthurAnd corvus: I agree 100%.19:50
clarkbjamesmcarthur: roger19:50
fungithanks jamesmcarthur!19:50
jamesmcarthurIt's top of our list to move off to a different registrar.19:50
corvusjamesmcarthur: yeah, i think we're on the same page on that :)19:50
jamesmcarthurJust one of those "we need some time" things19:50
jamesmcarthurThese guys are absolutely useless.19:50
clarkbonce dns is in place I expect we can start pushing snowballs downhill quickly19:51
jamesmcarthurlsell: and I have already been communicating about a plan to move to another registrar19:51
clarkbAnything else before that snowball is rolling? I'd like to get to ianw's topic before we run out of time19:51
*** tobiash has joined #openstack-meeting19:51
*** isq has joined #openstack-meeting19:51
fungiwe have a few snowballs already perched atop the avalanche19:51
clarkbAlright ianw would like to talk about cleaning up our pypi afs volume19:52
clarkbfor those that maybe don't know we serve pypi via caching proxy now beacuse pypi itself has become quite large and is growing more quickly every day19:52
clarkbthis has been mostly working19:52
ianwyes, our afs volume is basically full, the f29 updates are pushing it.  removing the old pypi volume obviously frees up most of it19:53
clarkband I'm not sure we'd be able to realistically go back to mirroring even if we wanted to. But if we did creating a new voluming and building up without packages that are huge and we don't want is possible19:53
clarkbI'm in favor of removing the pypi volume given that doing ^ is feasible if we need to go back to the old setup19:53
fungialso switching to a new enough version of bandersnatch to successfully clean up that mirror needs python from ubuntu bionic or later19:53
ianwyeah, the idea we could re-use the data is probably fantasy19:54
ianwwhat i would like to happen is people +2 on the removal of the docs etc with19:54
ianw#link https://review.openstack.org/#/c/618326/19:54
fungiwe certainly may want to switch back to bandersnatch at some point, but by the time we can do that we're better off just starting a fresh mirror from scratch anyway19:54
ianwand i'll take that as an indication to clean up19:54
ianwthe f29 mirror is pushing it (but i'll ping in #infra about removing f27, which will relieve some of the pressure)19:55
ianwthat's all on that19:56
AJaegerthanks, ianw19:56
corvusa note on the commit message -- we can work around the 2tb limit by sharding.  but i think the other issues are compelling and we should stick with proxy.19:56
clarkbcorvus: ya the fact that the growth is only getting worse as time goes on makes it a treadmill that will continue to be hard to be on19:57
fungiyeah, we're not using it anyway, so the complexity of sharding that isn't worth the effort to maintain19:57
ianwcorvus: true, but we'd have to sort of invent the sharding, an effort i'm not sure any of us want to go to19:57
clarkbWe have just a couple minutes left19:58
clarkb#topic Open Discussion19:58
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:58
clarkbAny last minute items before our hour is up?19:58
corvusit's not difficult; just do a volume for each directory under packages/19:58
corvus(so ~256 volumes for the 00 -- ff directories) plus some more19:58
corvusi mostly mention this as a general pattern it's useful to keep in mind19:59
corvusafs can handle hundreds of thousands of volumes easily19:59
*** jamesmcarthur has quit IRC19:59
anteayathanks for the meeting clarkb19:59
ssbarnea|bkp2considering the size  (and number of changes) of pypi i suspect we are better off with a proxy than a mirror, but that's only my "gut feeling".19:59
corvus(this is the way home directories are set up at the big universities)19:59
clarkbthe biggest issue is the pypi package size cost is concentrated in a few packages so we'd still need to ignore them in bandersnatch19:59
anteayahappy too much food and shopping those who do19:59
corvusclarkb: yes, and keep adding packages to the list as we see them20:00
clarkbssbarnea|bkp2: yup mine too. Basically current system works and is low maintenance20:00
clarkbI think if we decide to go back to afs for pypi we'd be rebuiilding things anyway20:00
clarkbso its fine to move fowrard on ianw's plan for now20:00
clarkband with that we are at time20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
fungithanks clarkb!20:00
openstackMeeting ended Tue Nov 20 20:00:42 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-11-20-19.01.html20:00
clarkbthank you everyone20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-11-20-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-11-20-19.01.log.html20:00
gary_perkinsthanks clarkb :)20:00
*** AJaeger has left #openstack-meeting20:01
*** yamamoto has quit IRC20:15
*** a-pugachev has joined #openstack-meeting20:18
*** jamesmcarthur has joined #openstack-meeting20:35
*** david-lyle is now known as dklyle20:46
*** raildo has quit IRC20:48
*** yamamoto has joined #openstack-meeting20:48
*** priteau has quit IRC20:52
*** yamamoto has quit IRC20:58
*** jamesmcarthur has quit IRC20:58
*** shrasool has quit IRC21:00
*** apetrich has quit IRC21:02
*** rcernin has joined #openstack-meeting21:38
*** lpetrut has quit IRC21:41
*** apetrich has joined #openstack-meeting21:51
*** jamesmcarthur has joined #openstack-meeting21:51
*** awaugama has quit IRC22:04
*** imacdonn has quit IRC22:42
*** imacdonn has joined #openstack-meeting22:42
*** efried is now known as efried_back_mond22:43
*** efried_back_mond is now known as efried_back_mon22:43
*** apetrich has quit IRC22:47
*** munimeha1 has quit IRC22:49
*** mugsie has quit IRC23:06
*** armax has quit IRC23:08
*** dustins has quit IRC23:19
*** hongbin has quit IRC23:30
*** yamamoto has joined #openstack-meeting23:30
*** rbudden has quit IRC23:33

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