Tuesday, 2019-07-02

*** yamamoto has joined #openstack-meeting00:01
*** mattw4 has quit IRC00:10
*** lseki has quit IRC00:17
*** gyee has quit IRC00:37
*** jamesmcarthur has joined #openstack-meeting00:40
*** ijw has quit IRC00:43
*** jamesmcarthur has quit IRC00:51
*** jamesmcarthur has joined #openstack-meeting00:53
*** yamamoto has quit IRC01:04
*** lbragstad has quit IRC01:08
*** jamesmcarthur has quit IRC01:10
*** jamesmcarthur has joined #openstack-meeting01:10
*** jamesmcarthur has quit IRC01:15
*** hongbin has joined #openstack-meeting01:16
*** redrobot has quit IRC01:17
*** jamesmcarthur has joined #openstack-meeting01:37
*** jamesmcarthur has quit IRC01:41
*** ircuser-1 has joined #openstack-meeting01:43
*** ekcs has quit IRC02:03
*** vishalmanchanda has joined #openstack-meeting02:06
*** jamesmcarthur has joined #openstack-meeting02:37
*** yamamoto has joined #openstack-meeting02:41
*** yamamoto has quit IRC02:57
*** yamamoto has joined #openstack-meeting03:07
*** diablo_rojo has quit IRC03:26
*** diablo_rojo has joined #openstack-meeting03:27
*** diablo_rojo has quit IRC03:32
*** psachin has joined #openstack-meeting03:37
*** whoami-rajat has joined #openstack-meeting03:42
*** jamesmcarthur has quit IRC03:49
*** jamesmcarthur has joined #openstack-meeting03:50
*** igordc has quit IRC03:51
*** yamamoto has quit IRC03:54
*** tpatil has joined #openstack-meeting03:55
*** jamesmcarthur has quit IRC03:57
samP#startmeeting masakari04:01
openstackMeeting started Tue Jul  2 04:01:11 2019 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samPHi all for masakari04:01
samPtpatil: Hi04:01
*** nitinuikey has joined #openstack-meeting04:02
samP#topic Critical bugs and Patches04:02
*** openstack changes topic to "Critical bugs and Patches (Meeting topic: masakari)"04:02
samPAny critical bugs or patches need to discuss here04:02
*** yamamoto has joined #openstack-meeting04:02
samPtpatil: thanks04:03
samP#topic Train work items04:03
*** openstack changes topic to "Train work items (Meeting topic: masakari)"04:03
tpatilDevstack support for hostmonitor04:04
tpatilWe have made some progress here, able to configure the stonith device successfully04:04
tpatilI don't know whether OpenStack CI gate job supports IPMI or not04:05
samPtpatil: AFAIK, they do not support04:06
tpatilbut it's possible to run it in third party CI job which has support for IPMI04:06
*** shilpasd has joined #openstack-meeting04:06
tpatilwe are planning to check if IPMI is supported or not in the devstack script. if not, then we will log warning and hostmonitor will not be installed04:06
samPtpatil: understood. I think it's OK04:07
tpatilThat's the only progress from my side about Train work items04:08
samPtpatil: Thanks04:08
samPno update from my side.04:08
samP#topic AOB04:08
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:08
samPAs we discussed last week, I would like to propose conduct this meeting bi-weekly from today.04:09
samPIf no objections, next meeting will be on 7/1604:10
samPOK then, I will be edit the meeting details.04:10
samPif no other items to discuss, we can finish today's meeting here.04:11
tpatilAre you planning to update wiki04:11
tpatil#link https://wiki.openstack.org/wiki/Meetings/Masakari04:11
samPtpatil: yes I will04:11
tpatilok, Thank you04:11
tpatilNo there topics to be discussed from my side04:11
samPOK then thanks for your time.04:12
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:12
openstackMeeting ended Tue Jul  2 04:12:24 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-07-02-04.01.html04:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-07-02-04.01.txt04:12
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-07-02-04.01.log.html04:12
*** yamamoto has quit IRC04:20
*** hongbin has quit IRC04:21
*** _alastor_ has quit IRC04:25
*** ricolin has joined #openstack-meeting04:25
*** jamesmcarthur has joined #openstack-meeting04:29
*** vishalmanchanda has quit IRC04:33
*** zaneb has quit IRC04:34
*** zaneb has joined #openstack-meeting04:35
*** jamesmcarthur has quit IRC04:36
*** vishalmanchanda has joined #openstack-meeting04:42
*** tpatil has quit IRC04:49
*** zbitter has joined #openstack-meeting04:57
*** yamamoto has joined #openstack-meeting04:57
*** zaneb has quit IRC04:59
*** nitinuikey has quit IRC05:00
*** dansmith has quit IRC05:04
*** jamesmcarthur has joined #openstack-meeting05:05
*** yamamoto has quit IRC05:07
*** jamesmcarthur has quit IRC05:10
*** Luzi has joined #openstack-meeting05:12
*** boxiang has joined #openstack-meeting05:16
*** imsurit has joined #openstack-meeting05:17
*** dansmith has joined #openstack-meeting05:22
*** yaawang has quit IRC05:24
*** imsurit_ofc has joined #openstack-meeting05:29
*** imsurit has quit IRC05:30
*** imsurit_ofc is now known as imsurit05:30
*** shilpasd has quit IRC05:31
*** ykatabam has quit IRC05:39
*** jamesmcarthur has joined #openstack-meeting05:42
*** zbitter has quit IRC05:44
*** jamesmcarthur has quit IRC05:47
*** yaawang has joined #openstack-meeting06:04
*** yamamoto has joined #openstack-meeting06:09
*** artom has joined #openstack-meeting06:16
*** artom is now known as artom|gmtplus306:19
*** belmoreira has joined #openstack-meeting06:24
*** slaweq has joined #openstack-meeting06:30
*** yamamoto has quit IRC06:33
*** yaawang has quit IRC06:34
*** imsurit has quit IRC06:35
*** yaawang has joined #openstack-meeting06:35
*** yamamoto has joined #openstack-meeting06:37
*** yamamoto has quit IRC06:37
*** yamamoto has joined #openstack-meeting06:41
*** joxyuki has joined #openstack-meeting06:58
*** tssurya has joined #openstack-meeting07:13
*** tesseract has joined #openstack-meeting07:15
*** imsurit has joined #openstack-meeting07:26
*** dkushwaha has joined #openstack-meeting07:26
*** yamamoto has quit IRC07:33
*** ricolin_ has joined #openstack-meeting07:35
*** belmoreira has quit IRC07:37
*** ricolin has quit IRC07:37
*** yamamoto has joined #openstack-meeting07:38
*** ttsiouts has joined #openstack-meeting07:40
*** ociuhandu has joined #openstack-meeting07:42
*** jamesmcarthur has joined #openstack-meeting07:44
*** tpatil has joined #openstack-meeting07:44
*** jamesmcarthur has quit IRC07:48
*** e0ne has joined #openstack-meeting07:49
*** ricolin__ has joined #openstack-meeting07:49
*** jamesmcarthur has joined #openstack-meeting07:51
*** ricolin_ has quit IRC07:51
*** ttsiouts has quit IRC07:52
*** ttsiouts has joined #openstack-meeting07:53
*** jamesmcarthur has quit IRC07:55
*** yamamoto has quit IRC07:55
*** bhagyashris_ has joined #openstack-meeting07:55
*** belmoreira has joined #openstack-meeting07:56
*** ttsiouts has quit IRC07:57
*** yamamoto has joined #openstack-meeting07:57
*** takahashi-tsc has joined #openstack-meeting07:58
*** nitinuikey has joined #openstack-meeting07:59
*** nitinuikey has left #openstack-meeting08:01
*** pcaruana has joined #openstack-meeting08:01
*** ralonsoh has joined #openstack-meeting08:02
*** nitinuikey has joined #openstack-meeting08:02
dkushwaha#startmeeting tacker08:04
openstackMeeting started Tue Jul  2 08:04:23 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:04
*** openstack changes topic to " (Meeting topic: tacker)"08:04
openstackThe meeting name has been set to 'tacker'08:04
dkushwaha#topic Roll Call08:04
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:04
dkushwahawho is here for Tacker weekly meeting?08:04
dkushwahahello all08:06
dkushwahaseems no other members08:07
dkushwahaok, lets start..08:08
dkushwaha#topic summit CFP08:08
*** openstack changes topic to "summit CFP (Meeting topic: tacker)"08:08
dkushwaha#link https://etherpad.openstack.org/p/Tacker-CFP-shanghai-summit08:08
*** imsurit has quit IRC08:08
dkushwahaMe and Phuoc will submit Tacker hands-on lab session.08:09
dkushwahaFeel free to join that08:09
*** yamamoto has quit IRC08:09
dkushwahadoes any one have plan to submit other sessions also ?08:10
*** trident has quit IRC08:10
takahashi-tsc1 information, Jo-san submit the session about telecom aspect.08:11
takahashi-tscI will be also a speaker.08:12
dkushwahatakahashi-tsc, nice to hear that.08:12
dkushwahatakahashi-tsc, will it be related to Tacker ?08:12
dkushwahaother than my hands-on lab session, I will have 2 other sessions(i.e. Tacker project update, and project onboarding session)08:13
takahashi-tscYes, we will talk that operator requires generic VNFM and Tacker will become it.08:13
*** trident has joined #openstack-meeting08:13
dkushwahatakahashi-tsc, great08:14
takahashi-tscdkushwaha Now 3 speakers are decided, but if you are OK, i'd like to join the session as Tacker leader.08:15
*** imsurit has joined #openstack-meeting08:15
*** yamamoto has joined #openstack-meeting08:16
takahashi-tscWe are writing abstract now, I will share the information later.08:16
dkushwahatakahashi-tsc, As i haven't reached my max session limit, so yes, its ok for me.08:16
dkushwahamoving next..08:18
dkushwaha#topic VNF packages support08:18
*** openstack changes topic to "VNF packages support (Meeting topic: tacker)"08:18
tpatildkushwaha: I have replied to your questions on the spec08:19
*** ttsiouts has joined #openstack-meeting08:19
tpatiland soon we will upload updated specs08:19
dkushwahatpatil, aah, I just saw your comments08:19
dkushwahatpatil, ok Thanks. just one more points.As we are glance_store, could you please update the same in spec also08:22
tpatilYes, will do08:22
dkushwaha*.As we are planning to use glance_store08:22
dkushwahatpatil, thanks08:22
*** jamesmcarthur has joined #openstack-meeting08:22
dkushwahamoving next..08:23
dkushwaha#topic OpenDiscussion08:24
*** openstack changes topic to "OpenDiscussion (Meeting topic: tacker)"08:24
dkushwahaDo we have something to discuss for now?08:26
dkushwahaanything from your side?08:27
dkushwahatakahashi-tsc, tpatil nitinuikey ^^08:27
*** jamesmcarthur has quit IRC08:28
takahashi-tscJust FYI... now we are tesintg the scale-in/out features. we may push bug patch.08:29
tpatildkushwaha: No topics from my side08:30
nitinuikeyno topics from my side too08:31
takahashi-tscno topics from my side.08:31
dkushwahatakahashi-tsc, Thanks for testing08:32
dkushwahaOk, Thanks Folks for joining this meeting.08:32
dkushwahaclosing it now.08:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:33
openstackMeeting ended Tue Jul  2 08:33:03 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-07-02-08.04.html08:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-07-02-08.04.txt08:33
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-07-02-08.04.log.html08:33
*** ykatabam has joined #openstack-meeting08:33
*** nitinuikey has left #openstack-meeting08:34
*** imsurit has quit IRC08:40
*** imsurit has joined #openstack-meeting08:40
*** boxiang has quit IRC08:42
*** boxiang has joined #openstack-meeting08:42
*** boxiang has quit IRC08:43
*** boxiang has joined #openstack-meeting08:44
*** takahashi-tsc has left #openstack-meeting08:44
*** boxiang_ has joined #openstack-meeting08:46
*** boxiang has quit IRC08:46
*** imsurit_ofc has joined #openstack-meeting08:48
*** imsurit has quit IRC08:49
*** imsurit_ofc is now known as imsurit08:49
*** belmoreira has quit IRC08:52
*** imsurit has quit IRC08:54
*** imsurit has joined #openstack-meeting09:00
*** jamesmcarthur has joined #openstack-meeting09:00
*** yamamoto has quit IRC09:01
*** dkushwaha has quit IRC09:02
*** ricolin_ has joined #openstack-meeting09:04
*** tetsuro has joined #openstack-meeting09:04
*** ricolin__ has quit IRC09:07
*** bhagyashris_ has left #openstack-meeting09:09
*** Lucas_Gray has joined #openstack-meeting09:11
*** yamamoto has joined #openstack-meeting09:13
*** priteau has joined #openstack-meeting09:17
*** a-pugachev has joined #openstack-meeting09:18
*** belmoreira has joined #openstack-meeting09:20
*** yamamoto has quit IRC09:22
*** tpatil has quit IRC09:32
*** ricolin_ is now known as ricolin09:33
*** whoami-rajat has quit IRC09:42
*** ricolin_ has joined #openstack-meeting09:47
*** yamamoto has joined #openstack-meeting09:47
*** ykatabam has quit IRC09:48
*** ricolin has quit IRC09:49
*** yamamoto has quit IRC09:52
*** dkushwaha has joined #openstack-meeting09:55
*** yamamoto has joined #openstack-meeting09:55
*** dkushwaha has left #openstack-meeting09:55
*** yamahata has quit IRC09:55
*** yamahata has joined #openstack-meeting09:56
*** priteau has quit IRC09:57
*** yamamoto has quit IRC09:59
*** a-pugachev has quit IRC10:01
*** a-pugachev has joined #openstack-meeting10:02
*** jamesmcarthur has quit IRC10:04
*** yamamoto has joined #openstack-meeting10:04
*** tetsuro has quit IRC10:04
*** yamamoto has quit IRC10:04
*** priteau has joined #openstack-meeting10:06
*** psachin has quit IRC10:08
*** tetsuro has joined #openstack-meeting10:10
*** boxiang_ has quit IRC10:10
*** yamahata has quit IRC10:10
*** ykatabam has joined #openstack-meeting10:13
*** a-pugachev has quit IRC10:16
*** yamamoto has joined #openstack-meeting10:30
*** yamamoto has quit IRC10:37
*** brinzhang has quit IRC10:37
*** baojg has joined #openstack-meeting10:38
*** raildo has joined #openstack-meeting10:53
*** yamahata has joined #openstack-meeting11:06
*** yamamoto has joined #openstack-meeting11:30
*** ykatabam has quit IRC11:39
*** psachin has joined #openstack-meeting11:40
*** priteau has quit IRC11:41
*** imsurit has quit IRC11:42
*** baojg has quit IRC11:45
*** yamahata has quit IRC11:56
*** jamesmcarthur has joined #openstack-meeting12:01
*** jamesmcarthur has quit IRC12:05
*** electrofelix has joined #openstack-meeting12:22
*** dmacpher_ has quit IRC12:30
*** yamamoto has quit IRC12:31
*** dmacpher has joined #openstack-meeting12:33
*** jamesmcarthur has joined #openstack-meeting12:34
*** jamesmcarthur has quit IRC12:39
*** jamesmcarthur has joined #openstack-meeting12:42
*** eharney has quit IRC12:43
*** dmacpher has quit IRC12:45
*** jaypipes has joined #openstack-meeting12:46
*** enriquetaso has joined #openstack-meeting12:46
*** tetsuro has quit IRC12:47
*** ricolin_ is now known as ricolin12:56
*** priteau has joined #openstack-meeting12:57
*** dmacpher has joined #openstack-meeting12:58
*** jamesmcarthur has quit IRC13:05
*** priteau has quit IRC13:13
*** priteau has joined #openstack-meeting13:14
*** lseki has joined #openstack-meeting13:14
*** mriedem has joined #openstack-meeting13:14
*** lbragstad has joined #openstack-meeting13:24
*** eharney has joined #openstack-meeting13:26
*** yamamoto has joined #openstack-meeting13:28
*** jamesmcarthur has joined #openstack-meeting13:32
*** zaneb has joined #openstack-meeting13:35
*** zaneb has quit IRC13:43
*** liuyulong has joined #openstack-meeting13:45
*** zaneb has joined #openstack-meeting13:46
*** yamamoto has quit IRC13:47
*** joxyuki has quit IRC13:48
*** heikkine has quit IRC13:48
*** Luzi has quit IRC13:50
*** donghao has joined #openstack-meeting13:53
*** donghao has quit IRC13:53
*** tidwellr has joined #openstack-meeting13:54
*** mlavalle has joined #openstack-meeting13:55
*** boden has joined #openstack-meeting13:59
*** lajoskatona has joined #openstack-meeting13:59
slaweq#startmeeting networking14:00
openstackMeeting started Tue Jul  2 14:00:10 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. 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
slaweqwelcome everyone14:00
slaweq#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
*** shintaro has joined #openstack-meeting14:01
slaweqNext milestone, T-2 is week of July 22 - 26 - that is only 3 weeks from now14:02
slaweqDeadline for CFP for Shanghai summit is today: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006262.html14:02
slaweqso it's last minute to propose talk if You want to have one there :)14:03
slaweqAny other announcements from the team?14:03
mlavallenot from me14:04
slaweq#topic Blueprints14:04
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:04
slaweqTrain-2 BPs are on https://launchpad.net/neutron/+milestone/train-214:04
slaweqany updates?14:05
mlavalleI don't have any today14:05
mlavalleother than say that the spec for Improve Extra Route API was approved last week14:05
mlavalleso it's implementation ony now14:05
mlavallefor Allow multiple segments per host for routed networks14:06
tidwellrI have code for address scope affinity changes https://review.opendev.org/#/c/667511/14:06
slaweqyes, I also updated couple of BPs and added to them links to specs, RFEs and/or patches in review14:06
mlavalletidwellr: is it good to go14:07
tidwellrreally I'm waiting on neutron-lib 1.28.0 before sprinting ahead14:07
mlavallezuul seems happy with it14:07
mlavalleso still wip14:07
tidwellrthere are some todo's related to use of constants14:07
tidwellrbut other than that it's ready for reviews14:08
liuyulongIs there any BP coming out from this: https://review.opendev.org/#/c/658414/ ?14:09
slaweqthx tidwellr for work on this and update today :)14:09
mlavalleliuyulong: eventually, several14:09
slaweqI think that haleyb proposed (or will propose) new meeting to sync between neutron and networking-ovn so it can be discussed there14:10
slaweqare You ok with this?14:10
haleybmlavalle: i am in the process of adding a meeting which can start next Tuesday at this time, once a month to start14:11
mlavallehaleyb: thanks, that's what we agreed on last week14:11
haleybhttps://review.opendev.org/#/c/668013/ - i just need to remove my -W14:11
mlavalle+1ed it14:12
*** _alastor_ has joined #openstack-meeting14:12
haleybtidwellr: if you want to be a chair in ^^^ let me know :)14:13
tidwellrlet's co-chair14:13
haleybtidwellr: ack, i'll update it, i had added lucas as well14:14
haleybin case there is a bus...14:14
tidwellrsounds good14:15
slaweqok, lets move forward then14:16
slaweqI assume that there is no updates about other blueprints, right?14:16
mlavallenot from me14:17
slaweq#topic Community goals14:17
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:17
slaweqfirs on our list is14:17
slaweqRun under Python 3 by default14:17
slaweqwe still have some stadium projects to switch to py314:17
slaweqetherpad with todo list https://etherpad.openstack.org/p/neutron_stadium_python3_status14:18
slaweqrecently my patch to switch neutron-fwaas tempest job to py3 was merged14:18
slaweqso only functional tests job in fwaas repo left14:19
slaweqbut there are some other projects to take care still :)14:19
slaweqnjohnston any other updates on this?14:19
njohnstonNo, I think we have volunteers for each of the remaining projects14:20
bcafarelslaweq: no objection to moving around sections in that etherpad? (moving completed projects down)14:20
njohnstonI'll check on bgpvpn, that may be done now14:20
bcafareljust to easily find remaining work14:20
slaweqbcafarel: yes, that is good idea14:20
slaweqbcafarel: I will do it tomorrow14:20
slaweqthx for this idea :)14:21
slaweqnjohnston: thx for taking care of bgpvpn14:21
slaweqnext goal on the list is14:22
slaweqSupport IPv6-Only Deployments (slaweq)14:22
slaweqI didn't talk with gmann yet14:22
slaweqbut I was looking into storyboard related to this and it looks that there is no any work related to this yet14:22
slaweqI will keep an eye on it to know if we will have something to do here14:22
slaweqand the last goal on the list is:14:23
slaweqEnabling PDF generation support for project documentation (amotoki)14:23
slaweqamotoki: any updates?14:24
amotokiI tried the initial build of PDF doc last week.14:24
amotokiAs of now, we have a trouble when rendering inline neutron.conf sample file but if we drop it it succeeded.14:25
*** heikkine has joined #openstack-meeting14:25
amotokilinks to raw sample files are also broken14:25
amotokiso we need to discuss the general direction as the whole community. it is not specific to neutron.14:25
amotokii will keep my eyes on the discussoin.14:25
amotokithat's all from me.14:25
*** davidsha has joined #openstack-meeting14:26
slaweqthx amotoki for the update and for taking care of this14:26
slaweqanything else You want to talk regarding to community goals?14:26
slaweqok, lets move on14:28
slaweq#topic Bugs14:28
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:28
rubasovthe deputy report: http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007455.html14:28
slaweqthx rubaso14:28
slaweqYou were faster :)14:28
rubasovall gate failure bugs were fixed, including this one that did not make the report: http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007455.html14:28
rubasovmay I call the attention of sqlalchemy experts to this bug: https://bugs.launchpad.net/neutron/+bug/183448414:29
openstackLaunchpad bug 1834484 in neutron "[QoS] qos_plugin._extend_port_resource_request is killing port retrieval performance" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:29
ralonsohI still need to polish this: http://logs.openstack.org/98/667998/3/check/neutron-tempest-plugin-scenario-linuxbridge/7315f86/controller/logs/screen-q-agt.txt.gz?level=ERROR#_Jul_02_09_44_20_64304914:30
ralonsohI don't know why the server is not retrieving correctl the value14:30
ralonsohthat's all from my side (https://review.opendev.org/#/q/topic:bug/1834484+(status:open+OR+status:merged))14:31
njohnstonis this under a context writer with the new engine facade?14:31
* njohnston reconsiders, will debug with ralonsoh offline14:31
ralonsohnjohnston, should be, I'm still reviwing this problem14:31
rubasovralonsoh: thank you for the quick patch14:31
slaweqI noticed that only linuxbridge job is failing due to this issue14:31
*** Lucas_Gray has quit IRC14:32
slaweqbut I'm not sure if same error is visible also in other jobs, but it not cause test failures or there is no similar errors in other jobs14:32
slaweqralonsoh: did You check logs of other jobs?14:32
lajoskatonaslaweq: as I see only the linuxbridge job is running scenario tests, or am I missing somthing?14:32
ralonsohI did and I don't see this error14:32
lajoskatonaslaweq: I checked and for other tempest jobs I can't see the sql error14:33
slaweqthere is also dvr multinode job which is non voting14:33
ralonsohLB agent is the only one using the common agent loop and this call14:33
*** Lucas_Gray has joined #openstack-meeting14:33
*** redrobot has joined #openstack-meeting14:33
slaweqanything else You want to talk about rubasov?14:34
rubasovall other bugs have assignees from last week14:34
slaweqI think other bugs from last week are in pretty good state now, right?14:34
rubasovslaweq: yep14:35
slaweqok, thx14:35
mlavalleI have a question for rubasov14:35
slaweqmlavalle: sure, go on14:35
rubasovmlavalle: shoot14:35
mlavallewe don't need to discuss the rfe https://bugs.launchpad.net/neutron/+bug/1833674, right?14:35
openstackLaunchpad bug 1833674 in neutron "[RFE] Improve profiling of port binding and vif plugging" [Wishlist,In progress] - Assigned to Bence Romsics (bence-romsics)14:35
rubasovmlavalle: I don't think so14:36
rubasovmlavalle: it means to cover what we agreed on the ptg14:36
rubasovmlavalle: I created it for tracking reasons14:36
mlavallecool. I'll mark it approved then14:36
*** enriquetaso has quit IRC14:37
slaweqok, are You ok mlavalle now?14:38
mlavalleyes, thanks :-)14:38
slaweqthis week our bug deputy is bcafarel14:38
slaweqand next week will be me (so I don't need to ping anyone :P)14:39
bcafarelbug deputy on deck o/14:39
*** yamamoto has joined #openstack-meeting14:39
*** yamamoto has quit IRC14:39
slaweqthx bcafarel14:39
slaweqso we are in good hands this week :)14:39
slaweqany other bugs You want to talk about today?14:40
mlavallenot me14:40
rubasovnot me14:40
slaweqmoving on then14:40
slaweqnext topic14:40
slaweq#topic neutron-lib14:40
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:40
slaweqboden: Your turn :)14:40
bodenquickly; we mentioned neutron-lib 1.28.0 earlier... as far as I'm concerned it's ready to be released... see https://review.opendev.org/#/c/666870/14:41
bodenalso I have a question about stable branches and neutron-lib.. probably a question for amotoki14:42
bodenis there a way to back-port a bug fix for a "stable" version of neutron-lib?? for example a bug in the version of neutron-lib that was used with stein or queens14:42
bodenanybody know?14:43
amotokineutron-lib has stable branches so it would be same as usual.14:43
amotokiif we don't have any version number for them, it needs a discussion14:43
bodenamotoki, but stable branches in neutron-lib point to some arbitrary commit... they are not at all "linked" to the tags we release to PyPI14:44
bodene.g. look at stable/stein and 1.25.0 for neutron-lib... they are different and 1.25.0 is wahts used by neutron stable/stein14:44
slaweqboden: is tag 1.25 ahead of behind stable/stein?14:44
bodenbehind.. I think, but would need to verify14:45
bcafarelonly opendev migration patch for now14:45
bcafarel(+ the usual commits for branch creation)14:45
bodenI think stable/stein branch for lib was just created when we did it for all the other net projects... not related to the actual 1.25.0 release on pypi14:45
amotoki1.25.0 is the last release for stein and stable/stein is cut from there,14:45
slaweqso IMO shouldn't be problem if we will release e.g. 1.25.1 from stable/stein branch14:45
amotokiso we can backport any bug fix to stable/stein branch. we can cut 1.25.1 release then14:46
amotokistable/stein branch was created for usual maintenance too, so I believe there is no thing different.14:46
bodenhow about I look into the details of 1.25.0 vs stable/stein after this meeting and I can ping slaweq and amotoki then? no need to digress here I suppose14:47
amotokiboden: sure. makes sense14:47
slaweqboden: good for me14:47
bodenthanks guys!14:47
bodennothing else on neutron-lib from me.. just business as usual14:47
bcafarelupper-constraints in requirements does state neutron-lib===1.25.014:48
amotokithis is only difference between 1.25.0 and stable/stein now http://paste.openstack.org/show/753763/14:48
amotokithe diff is super small.14:48
*** shintaro has quit IRC14:48
bodenbcafarel.. hmm, can we bump the upper-constraints in stable/stein?14:49
amotokiwe can bump u-c in stable branches. bumping the minimum requirements needs to be more carefl.14:50
bcafarellooks like we can from git log I see clients and oslo.cache updates14:50
bcafarelamotoki: ack that one makes sense14:50
slaweqok, lets move on then14:52
slaweq#topic On demand agenda14:52
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:52
slaweqthere is nothing in this section for today14:52
*** _alastor_ has quit IRC14:52
njohnstonI have one question14:52
slaweqbut I just remembered one thing which I wanted to ask14:52
*** zbr has quit IRC14:53
slaweqand as we talked about requirements, it's kind of related14:53
slaweqwe have bug https://bugs.launchpad.net/neutron/+bug/183504414:53
openstackLaunchpad bug 1835044 in neutron "[Queens] Memory leak in pyroute2 0.4.21" [Undecided,New]14:53
slaweqwhich is only in stable/queens release14:53
ralonsohThere is a leak in pyroute14:53
slaweqcan we bump pyroute2 version in stable/queens to 0.5.2?14:53
slaweqdo You know?14:53
ralonsohboth in py2.7 and py3.614:53
ralonsohThat's what I want to know14:53
ralonsohI really don't know14:54
*** zbr has joined #openstack-meeting14:54
amotokiAFAIK we only update the upper-constraints in most cases as long as it works with both versions.14:54
ralonsohif the Neutron CI tests pass, I see no problem14:54
ralonsohthat's the point: I have a patch to test it14:54
mlavalleif needed, we can ask the stable branches team14:54
ralonsohof course, I don't know the repercussion in other out-of-tree projects14:54
ralonsohbut of course, we need to handle this problem14:55
*** _alastor_ has joined #openstack-meeting14:55
slaweqI just wasnt't sure what are policies for doing such big bump of version in stable branch14:55
amotokiisn't it better to start a mailing list discussion including the requirements and stable teams?14:55
ralonsohlet's see first if the neutron patch (CI testing) works14:55
bcafarelit may not be such big jump in pyroute, high level changes between 0.4.21 and 0.5.2 maybe useful14:56
ralonsohok, I'll send a mail for this14:56
slaweqamotoki: good idea14:56
slaweqralonsoh: thx14:56
slaweqok, lets talk about it in review and on ML14:56
slaweqnjohnston: You had question also14:56
njohnstonmlavalle: In Denver you mentioned sending an email to reinvigorate the fwaas community (or show that the project is unmanned), I was wondering if you sent that and I missed it?14:56
slaweqgo on14:56
haleybi think we can bump things to a degree, just have to make release version minor bump, eg 12.0.6 -> 12.1.014:56
haleybdidn't mean to step on question14:57
mlavallenjohnston: no, I will do it soon14:57
njohnstonmlavalle: thanks!14:57
njohnstonthat's all from me14:57
slaweqthx njohnston14:57
slaweqwe have 3 minutes left14:57
slaweqanyone else wants to talk about something?14:57
bcafarelhaleyb: similar to the recent queens release situation then14:58
haleybbcafarel: i think, but i didn't know about that until it happened14:58
bcafarelsame here :)14:58
haleybi just don't think we can go past u/c14:58
bcafarelI think it will probably be "check all projects that depend on pyroute and run ci on them"14:59
slaweqok, we are almost out of time now14:59
slaweqthx for attending and have a great week14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Tue Jul  2 14:59:42 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-07-02-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-07-02-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-07-02-14.00.log.html14:59
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Jul  2 15:00:00 2019 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
*** boden has left #openstack-meeting15:00
ralonsohHello again!15:00
slaweqhi ralonsoh15:00
*** lajoskatona has left #openstack-meeting15:00
* slaweq will be only lurking here15:00
ralonsohthe meeting today is going to be very short15:00
ralonsohdavidsha, are you ready for the Open Discussion?15:00
rubasovI do not have updates for today's meeting and may need to drop off early15:00
ralonsoh(let's wait 30 secs more)15:01
ralonsohrubasov, np15:01
davidsharalonsoh: yup!15:01
ralonsohlet's start15:01
ralonsohlet's start15:01
ralonsoh#topic RFEs15:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:01
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,Fix released] - Assigned to Bence Romsics (bence-romsics)15:01
ralonsohThe only missing piece here is #link https://review.opendev.org/#/c/629253/15:01
ralonsohLajos told me to say this in the meeting15:01
rubasovthat was merged I think15:02
*** mattw4 has joined #openstack-meeting15:02
ralonsoh10 days ago..... so I don't understand15:02
ralonsohok, rubasov, any update?15:02
rubasovso I think we have no more open changes for that rfe15:02
ralonsohI think we can remove this RFE from the agenda15:03
ralonsohwhat do you think?15:03
rubasovyep, the neutron side is all done15:03
ralonsohif you have any new update, you can write it in the etherpad agenda (https://etherpad.openstack.org/p/neutron_qos_meeting_chair)15:03
ralonsohor just you can ping me15:03
rubasovokay, we may come back with related news in nova when that happens15:03
*** yamamoto has joined #openstack-meeting15:04
ralonsohand again, thank you!15:04
*** edmondsw_ has joined #openstack-meeting15:04
rubasovthanks to lajoskatona for these last patches15:04
*** gyee has joined #openstack-meeting15:04
ralonsohok, let's move on15:05
ralonsoh#topic Bugs15:05
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:05
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/182669515:05
openstackLaunchpad bug 1826695 in neutron "[L3][QoS] cache does not removed when router is down or deleted" [Medium,In progress] - Assigned to LIU Yulong (dragon889)15:05
ralonsoh#link https://review.opendev.org/#/c/656105/15:05
ralonsohnot too much activity15:05
ralonsohI'll ping liuyulong in the review15:05
*** cheng1 has joined #openstack-meeting15:06
ralonsohok, let's move to the next one15:06
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/183448415:06
openstackLaunchpad bug 1834484 in neutron "[QoS] qos_plugin._extend_port_resource_request is killing port retrieval performance" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:06
ralonsoh#link https://review.opendev.org/#/q/topic:bug/1834484+(status:open+OR+status:merged)15:06
liuyulongActually no much review activity from the community. We run such code locally for some times long.15:06
ralonsohliuyulong, but the CI is still failing15:07
ralonsohanyway, I'll try to review this patch today15:07
liuyulongLet me rebase it once more.15:08
ralonsohliuyulong, thanks!15:08
ralonsohok, about the second bug, 183448415:08
ralonsohthe problem in https://review.opendev.org/#/c/667998/15:09
ralonsohI found the issue and I'm both writting the problem description in the patch and implementing the solution15:09
ralonsohI'll push it ASAP15:09
rubasovralonsoh: thank you for working on that15:09
ralonsohrubasov, np! We had some testers in my company complaining about15:10
ralonsohabout this15:10
ralonsohbut it was easy to solve15:10
ralonsoh(and now we have more information in the port DB object and OVO)15:10
ralonsoh--> the network qos policy, always good to have it!15:10
*** Lucas_Gray has quit IRC15:10
ralonsohok, no more bugs in the list (good!!)15:11
ralonsohAm I missing something?15:11
ralonsoh#topic Open Discussion15:11
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:11
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/1476527 - Adoption of Neutron Classifier API into QoS15:12
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:12
davidshaI've been a bit locked waiting for feedback, but I might pre-empt one approach by making a patch thats moves Neutron classifier's resources into neutron/neutron-lib15:12
davidshaand rebase the main QoS patch on top of it15:13
ralonsohI support this idea!15:13
davidshaThanks, I'll try to get that up asap!15:13
ralonsohplease, submit this patch and let the community comment about this15:13
davidshawill do!15:13
ralonsohIMO, although that means increasing the complexity of QoS (just a bit, and only for DSCP)15:14
ralonsohthis feature is difficult to be integrated outside Neutron, as a side project15:14
ralonsohthe DB changes (related to DSCP policies) should be integrated in Neutron15:14
davidshaHopefully though the complexity would make it easier if we ever wanted to extend classification to other qos rules in the future, do it right once and all that15:15
ralonsohsure, that's right!15:15
ralonsohof course:15:15
ralonsohyou should provide a code ready NOT to use the classification15:15
ralonsohthat means15:15
ralonsohthe code should with and without classification15:15
davidshaof course15:15
ralonsohDO NOT BRAKE ANYTHING!!!15:16
davidshaOnly a little ;P15:16
ralonsohsorry!! my bad english15:16
ralonsohok, so waiting for your n-lib patch, integrating the classification groups in the QoS15:17
ralonsohand the DB modifications in Neutron15:17
*** baojg has joined #openstack-meeting15:17
ralonsoham I missing anything here?15:17
davidshajust to be sure, the prference is for Neutron classifier to go into Neutron-lib?15:17
ralonsohwell, the API yes15:18
ralonsohthe neutron classifier is going to be used outside Neutron?15:18
ralonsohthe classifier should be a Neutron service, depending on QoS15:19
davidshakk, njohnston mentioned a while back that putting all of it into neutron-lib made sense to him, just wanted to see if that was what you meant15:19
ralonsohyes, but what are you going to put in n-lib?15:19
davidshaI suppose just the API definitions, you need the db models and migrations in neutron.15:20
ralonsohyes, the DB model will be only in Neutro15:20
ralonsohand the service definition15:20
ralonsohsomething else??15:21
davidshanope, thats all for me15:22
*** liuyulong has quit IRC15:22
ralonsohok, thank you all folks, see you in IRC and in two weeks here15:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:22
openstackMeeting ended Tue Jul  2 15:22:59 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-07-02-15.00.html15:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-07-02-15.00.txt15:23
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-07-02-15.00.log.html15:23
*** davidsha has quit IRC15:23
*** enriquetaso has joined #openstack-meeting15:23
*** e0ne has quit IRC15:27
*** yamamoto has quit IRC15:30
*** ttsiouts has quit IRC15:31
*** rubasov has quit IRC15:34
*** tssurya has quit IRC15:40
*** artom|gmtplus3 has quit IRC15:56
*** yamamoto has joined #openstack-meeting15:56
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Jul  2 16:00:25 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
slaweqhello again :)16:00
bcafarelhey again16:01
slaweqfirst of all16:01
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:01
slaweq#topic Actions from previous meetings16:01
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:01
slaweqlast week we didn't have meeting with full agenda as there was only me and ralonsoh there and I didn't even had time to prepare everthing16:02
slaweqso lets check actions from 2 weeks ago now16:02
slaweqfirst action:16:02
slaweqmlavalle to debug neutron-tempest-plugin-dvr-multinode-scenario failures (bug 1830763) reproducing most common failure: test_connectivity_through_2_routers16:02
openstackbug 1830763 in neutron "Debug neutron-tempest-plugin-dvr-multinode-scenario failures" [High,Confirmed] https://launchpad.net/bugs/1830763 - Assigned to Miguel Lavalle (minsel)16:02
mlavalleI have a few things to say about this16:02
*** jamesmcarthur has quit IRC16:03
mlavalle1) your neutron-tempest-plugin patch improved the situation. In fact, now I cannot reproduce the failure locally16:03
slaweqand it also happens less in gate IMHO :)16:04
mlavalle2) We are still seeing failures in in our jobs16:04
mlavalleLook for example at https://review.opendev.org/#/c/66818216:05
*** rubasov has joined #openstack-meeting16:05
mlavallethis is a failure from today16:05
bcafarel1) is https://review.opendev.org/#/c/667547/ right?16:06
*** mattw4 has quit IRC16:06
mlavallebcafarel: yes16:06
*** yamamoto has quit IRC16:06
slaweqI have similar conclusions basically16:06
slaweqand I was also looking into many other failed tests in this job16:07
mlavalle3) I dug in in http://paste.openstack.org/show/6688216:07
mlavalle3) I dug in in http://paste.openstack.org/show/66818216:07
slaweqis it good link mlavalle ?16:07
mlavalleHere's some notes from the tempest and L3 agents log16:08
slaweqI see there some "Wifi cracker ...." info :)16:08
*** enriquetaso has quit IRC16:08
mlavalleFirst note that one of the routers created is c2e104a2-fb21-4f1b-b540-e4620ecc0c5016:08
mlavallelines 1 - 516:09
mlavalleThe note that (lines 8 - 34) we can ssh into the first VM16:09
*** wwriverrat has quit IRC16:09
mlavallebut from there we cannot ping the second instance16:09
slaweqmlavalle: do You have console log from second vm?16:10
slaweqI almost sure that it couldn't get instance-id from metadata service16:10
slaweqso there should be something like http://paste.openstack.org/show/753779/ in this console log16:10
mlavallethen, in lines 37 - 79, from the L3 agent, note that we have a traceback as a consequence of not being able to retrieve info for the router mentioned above16:10
mlavallewait a second16:11
mlavallelet's look here: http://logs.openstack.org/82/668182/3/check/neutron-tempest-plugin-dvr-multinode-scenario/495737b/testr_results.html.gz16:12
*** gyee has quit IRC16:12
slaweqahh, yes16:13
slaweqso in this one it is like I supposed16:13
mlavalleI can see that both instances got instance_id16:13
mlavalledon't they?16:13
haleybfailed 20/20: up 92.68. request failed16:14
haleybfailed to read iid from metadata. tried 2016:14
slaweqin second failed test one instance didn't get it16:14
slaweqsorry for noise mlavalle16:14
haleybi pasted that from neutron_tempest_plugin.scenario.test_connectivity.NetworkConnectivityTest failure16:15
mlavallehaleyb: the other test, right?16:16
haleybmlavalle: it's the second server?16:16
*** jamesmcarthur has joined #openstack-meeting16:17
mlavallehaleyb: there are two tests that failed. I am looking at the second one test_connectivity_through_2_routers16:17
haleybyes, the 2_routers test both got id's16:18
mlavalleso the point I am trying to make is that I can tracebacks in the l3 agent log related to getting info for the routers involved in the test16:18
mlavalletest_connectivity_through_2_routers that is16:18
mlavalleand that might mean that when the VM attempts the ping one of the routers is not ready16:19
mlavalleI'll dig deeper in this16:20
mlavallebut haleyb's point is still valid16:20
slaweqthx mlavalle16:20
mlavalleit seems we still see instances failing to get instance-id from metadata service16:20
mlavalleI'll pursue both16:21
slaweqthat is something what I also wanted to mention16:21
slaweqit looks that we quite often got issues with getting metadata16:21
haleybso this is reminding me of a patch liu (?) had wrt dvr routers and provisioning?  just a thought, i'll find it16:21
slaweqhaleyb: exactly :)16:21
slaweqand today I also send patch https://review.opendev.org/#/c/668643/ just to check how it will work when we don't need to use metadata service16:22
slaweqbut I don't think we should merge it16:22
haleybhttps://review.opendev.org/#/c/633871/ ?16:22
mlavalleI was actually thinking of that last night16:22
slaweqhaleyb: yes16:23
haleybslaweq: the job failed there too :(16:23
slaweqthat patch can probably help a lot with this issue16:23
slaweqhaleyb: but this job failed even before tests started16:23
haleybahh, you're right, can wait for a recheck16:24
mlavalleI'll investigate its impact with the findings described above ^^^^16:24
slaweqI also found one interesting case with this test16:24
slaweqplease see log: http://logs.openstack.org/11/668411/2/check/neutron-tempest-plugin-dvr-multinode-scenario/0d123cc/compute1/logs/screen-q-meta.txt.gz#_Jul_02_03_18_47_24958116:24
slaweqeach request to metadata service took more than 10 seconds16:25
*** gyee has joined #openstack-meeting16:25
slaweqthus e.g. public keys wasn't configured on instance and ssh was not possible16:25
slaweqmlavalle: thx for working on this16:26
haleybslaweq: test ran on slow infra somewhere ?16:26
slaweqhaleyb: maybe16:26
slaweqhaleyb: but we have more issues like that, when request to metadata/public-keys fails due to timeout16:27
slaweqand then ssh to the instance is not possible16:27
mlavallebut I am pretty sure that environment has impact on this test16:28
slaweq#action mlavalle to continue debugging neutron-tempest-plugin-dvr-multinode-scenario issues16:28
slaweqmlavalle: I agree16:28
mlavallesince we merged your patch, I have not been able to reproduce locally16:28
mlavalleI'm running it every half hour, with success....16:28
slaweqin many of those cases it's IMO matter of high load on node when tests are run16:28
mlavallein getting a failure :-)16:29
mlavallewithout success getting a failure I meant16:29
slaweqok, lets move on16:30
slaweqwe have many other thinks to talk about :)16:30
slaweqnext action was:16:30
slaweqslaweq to send patch to switch neutron-fwaas to python 316:30
slaweqI did https://review.opendev.org/#/c/666165/16:30
slaweqand it's merged already16:30
slaweqthis week I will try to do the same for functional tests job16:30
slaweq#action slaweq to send patch to switch functional tests job in fwaas repo to py316:31
njohnstonthanks slaweq!16:31
slaweqnjohnston: yw16:31
slaweqok, next one16:31
slaweqnjohnston update dashboard when ovn job becomes voting16:31
njohnstonI have that change ready locally but I haven't pushed it yet, I'll push it in a sec16:32
slaweqnjohnston: thx16:32
slaweqnext one was:16:32
slaweqslaweq to open bug related to missing namespace issue in functional tests16:32
slaweqDone https://bugs.launchpad.net/neutron/+bug/183338516:32
openstackLaunchpad bug 1833385 in neutron "Functional tests are failing due to missing namespace" [Medium,Confirmed]16:32
slaweqbut it's still unassigned16:33
slaweqand I saw at least 2 other examples of similar failures today16:33
slaweqso I will change Importance to High for this bug, what do You think?16:33
ralonsohI think this is related to https://bugs.launchpad.net/neutron/+bug/183371716:33
openstackLaunchpad bug 1833717 in neutron "Functional tests: error during namespace creation" [High,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)16:33
ralonsohsame problem as before with namespace creation/deletion/listing16:34
slaweqralonsoh: ok, can You then add "related-bug" or "closes-bug" tag to commit message in this patch?16:34
slaweqand assign it to Yourself, ok?16:35
ralonsohIMO, during functional tests, we are overloading sometimes the thread pool of privsep16:35
ralonsohslaweq, ok16:35
ralonsohand related to this: https://review.opendev.org/#/c/668682/16:35
slaweqthx ralonsoh16:35
slaweqyes, I was thinking about this patch :)16:36
slaweqto add in it info that it's related to the https://bugs.launchpad.net/neutron/+bug/1833385 also16:36
openstackLaunchpad bug 1833385 in neutron "Functional tests are failing due to missing namespace" [Medium,Confirmed]16:36
slaweqok, next one16:37
slaweqralonsoh to open bug related to failed test_server functional tests16:37
ralonsohlet me check...16:37
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/183327916:37
openstackLaunchpad bug 1833279 in neutron "TestNeutronServer: start function not called (or not logged in the temp file)" [Medium,Confirmed] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)16:37
ralonsohjust added more info: https://review.opendev.org/#/c/666261/16:38
slaweqok, and now You will try to spot it again and investigate logs, right?16:38
slaweq#action ralonsoh to continue debugging TestNeutronServer: start function (bug/1833279) with new logs16:39
slaweqthx ralonsoh16:39
slaweqand the last one from last week was16:39
slaweqslaweq to report bug regarding failing neutron.tests.fullstack.test_l3_agent.TestLegacyL3Agent.test_north_south_traffic tests16:39
slaweqDone: https://bugs.launchpad.net/neutron/+bug/183338616:39
openstackLaunchpad bug 1833386 in neutron "Fullstack test neutron.tests.fullstack.test_l3_agent.TestLegacyL3Agent.test_north_south_traffic is failing" [High,Fix released] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)16:39
slaweqand this seems to be fixed by ralonsoh :)16:39
slaweqthx a lot16:40
ralonsohthe problem wasn't the connectivity16:40
ralonsohbut the probe16:40
ralonsohand, of course, in high loaded servers, we can have this problem16:40
ralonsohso it's better to remove this probe in fullstack tests, doesn't add anything valuable16:40
slaweqyes, and it's merged already16:41
slaweqok, lets move on then16:42
slaweq#topic Stadium projects16:42
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:42
slaweqwe already talked about py3 for stadium projects16:42
slaweqso I think there is no need to talk about it again16:43
slaweqany updates about tempest-plugins migration?16:43
mlavallenot from me16:43
slaweqnjohnston: any update about fwaas?16:43
* njohnston is going to work on the fwaas one today if it kills him16:44
slaweqok, so lets move on16:44
slaweq#topic Grafana16:44
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:44
slaweqyesterday we had problem with neutron-tempest-plugin-designate-scenario but it's now fixed with https://review.opendev.org/#/c/668447/16:45
slaweqfrom other things, I see that functional/fullstack jobs and unit tests also are going to high numberf today16:46
*** yamamoto has joined #openstack-meeting16:46
slaweqbut I saw today at least couple of patches where unit tests failures were related to change so maybe it will not be big problem16:47
njohnstoneven the pep8 job shows the same curve16:47
slaweqlets observe it maybe and if You will notice some repeated failure, please open bug for it16:47
slaweqor maybe You already saw some :)16:47
*** priteau has quit IRC16:48
slaweqok, anything else You want to talk regarding grafana?16:49
slaweqok, lets move on then16:50
slaweq#topic Tempest/Scenario16:51
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:51
slaweqI have couple of things to mention regarding scenario jobs so lets start with this one today16:51
slaweqfirst of all, we promoted networking-ovn job to be voted recently16:51
slaweqand it's now failing about 25-30% of times16:51
mlavalleI noticed16:51
slaweqI found one repeat error16:51
slaweqso I reported it https://bugs.launchpad.net/networking-ovn/+bug/183502916:52
openstackLaunchpad bug 1835029 in networking-ovn "test_reassign_port_between_servers failing in networking-ovn-tempest-dsvm-ovs-release CI job" [Undecided,New]16:52
slaweqand I asked today dalvarez and jlibosva to take a look into it16:52
slaweqI also found other issue (but this one isn't related stricly to networking-ovn)16:52
openstackLaunchpad bug 1835058 in tempest "During instance creation tenant network should be given always " [Undecided,New]16:53
slaweqI reported it as tempest bug for now16:53
slaweqbasically some tests are failing due to "multiple networks found" exception from nova during spawning vm16:53
slaweqfrom other issues16:54
slaweqI noticed that from time to time port forwarding scenario test is failing16:54
slaweqand we don't have console log from vm in this test16:54
slaweqso I send small patch https://review.opendev.org/668645  to add logging of console log there16:54
slaweqplease review if You will have time16:54
slaweqand finally, during the weekend I spent some time on debugging issue with neutron-tempest-with-uwsgi16:55
slaweqI found what is wrong there and I proposed patch to tempest https://review.opendev.org/#/c/668311/16:55
*** yamamoto has quit IRC16:56
slaweqwith this patch I run couple of times this job in https://review.opendev.org/#/c/668312/1 and it was passing16:56
slaweqthat all from me about scenario jobs16:56
slaweqanything else You want to add?16:57
mlavalleThanks for the pacthes16:57
slaweqok, lets move on then as we are almost out of time16:57
slaweq#topic fullstack/functional16:57
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:57
slaweqI have one more info to mention about fullstack tests16:58
slaweqwe recently merged https://review.opendev.org/#/c/664629/ and again we have failures of test neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_ha_router_restart_agents_no_packet_lost16:58
slaweqso I think we should again mark it as unstable until we will finally found out what is going on with this test16:58
slaweqwhat do You think?16:58
ralonsohok to mark the test16:59
slaweq#action slaweq to mark test_ha_router_restart_agents_no_packet_lost as unstable again16:59
slaweqok, we are running out of time16:59
slaweqthx for attending16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Jul  2 17:00:00 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-02-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-02-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-07-02-16.00.log.html17:00
*** mlavalle has left #openstack-meeting17:00
*** tesseract has quit IRC17:01
*** jamesmcarthur has quit IRC17:02
*** jamesmcarthur has joined #openstack-meeting17:02
*** ricolin_ has joined #openstack-meeting17:05
*** ricolin has quit IRC17:07
*** belmoreira has quit IRC17:09
*** ricolin_ has quit IRC17:14
*** ociuhandu_ has joined #openstack-meeting17:14
*** ociuhandu_ has quit IRC17:15
*** mattw4 has joined #openstack-meeting17:15
*** ociuhandu has quit IRC17:18
*** electrofelix has quit IRC17:26
*** ekcs has joined #openstack-meeting17:26
*** ociuhandu has joined #openstack-meeting17:33
*** ociuhandu has quit IRC17:38
*** ralonsoh has quit IRC17:42
*** bbowen has quit IRC17:42
*** gyee has quit IRC17:52
*** jamesmcarthur has quit IRC17:56
*** ijw has joined #openstack-meeting17:58
*** armax has joined #openstack-meeting18:04
*** gyee has joined #openstack-meeting18:06
*** igordc has joined #openstack-meeting18:13
*** dtrainor_ has quit IRC18:14
*** dtrainor has joined #openstack-meeting18:34
*** hongbin has joined #openstack-meeting18:44
*** armax has quit IRC18:44
clarkbanyone else here for the infra meeting?18:59
clarkbwe will get started in a minute or two18:59
clarkb#startmeeting infra19:01
openstackMeeting started Tue Jul  2 19:01:14 2019 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
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-July/006409.html Meeting Agenda19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
* fungi is sorta here19:01
*** zaneb has quit IRC19:01
clarkbThis week coincides with a major US holiday (I think with a Canadian holiday too) so we can probably expect it to be a slow weird one19:02
clarkbMostly just a heads up that those of us in the USA are likely to disappear thursday and maybe friday19:02
fungii'm also basically gone all week19:02
fungi(just happen to be taking a break near a computer at the moment)19:03
clarkbfungi: was that break timed strategically?19:03
clarkb#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
fungientirely accidental19:03
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-06-25-19.01.txt minutes from last meeting19:03
clarkbmordred: you took actions a little while back to setup an opendevadmin account on github and to clean up the github openstack-infra org19:03
clarkbmordred: have you managed to make progress on that yet? if not I'll tack it back onto the list and I'll bet you are able to get more work done now that you have settled into the nomad life19:04
mordredclarkb: I have not19:04
mordredclarkb: but yes - I should be much more able to actually make progress on it19:04
clarkb#action mordred Set up opendevadmin github account19:05
clarkb#action morded clean up openstack-infra github org19:05
clarkbmordred: if only wifi worked underwater right?19:05
mordredclarkb: one day!19:05
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkb#topic Update Config Management19:06
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:06
clarkbianw: I think you are largely driving the efforts here at this point. Want to update us on the mirror-update ansiblification?19:06
fungii've noticed the kafs-based mirror in iad hasn't crashed in over 5 days now19:08
ianwyeah, so that really came from wanting to export the logs19:08
ianw(mirror-update) ... rather than hacking puppet to do it, seemed better to start an opendev.org mirror-update; initially with the rsync updates because it's easy19:09
ianwthat's in progress, i have the host up and reviews done, just need to babysit it19:09
ianwas mentioned, we have two kafs based mirrors running now, rax.iad & gra1.ovh.  details in https://etherpad.openstack.org/p/opendev-mirror-afs19:10
clarkbya there is some coordinating between the two hosts that needs doing right?19:10
clarkbbasically disable all the crons on the old host, then enable on the new host?19:10
ianwclarkb: yep, that's it, and make sure it's actually working :)19:10
ianwkafs doesn't have any blocking issues afaik.  however we seem to have narrowed down some of the problems with retry logic when we do "vos release"19:12
clarkbianw: the cachefs crashes are still expected to happen though?19:12
fungisurprising we can go nearly a week without one but then sometimes see it thrice in a day19:12
ianwthat's ... undetermined.  dhowells is aware of it (links to mail list posts in that etherpad, although there hasn't been on list discussion)19:13
clarkbgotcha so unsure of root cause or when/why it may happen then19:14
mordredianw: I was enjoying the scrollback between you and auristor from my last evening19:14
clarkbseems like we can skip the agenda entry to talk about the mirrors if we cover at least one more item. That is new mirror should be built with bionic + openafs 1.8.3 (via our ppa) and the ansible is all in place to do that by default?19:15
ianwi think dhowells has a pretty good idea of what's going on, it is in bits of code he wants to rewrite.  i need to sync on what the medium term plans are, because i know significant work won't happen for a few weeks at least19:15
*** donnyd has joined #openstack-meeting19:15
ianwclarkb: i think so; the dfw.rax mirror has been going OK AFAIK?  we got a report last night about the ord.rax mirror and "hash sum mismatch", which we just turned on the other day ... i need to investigate that19:16
clarkbianw: that reminds me of the problems we had on default bionic openafs19:17
clarkb(perhaps we didn't get the ppa version there?)19:17
ianwmordred: yes, auristor has been (and continues to be) super helpful with our AFS infrastructure :)  it's like a direct line to the afs gods :)19:17
mordredianw: +10019:17
clarkbAlright before we move on anyone else have puppet conversion irons in the fire?19:18
clarkb(I'm not aware of any so speak up if I've missed them)19:19
corvusthere is....19:19
corvuswe should remember that further work on the gerrit-gitea-zuul complex is pending a move of the project creation ansible into python (to speed that up)19:19
corvusi think that was on mordred's plate... mordred is that still something you want to do, or would you like me to see if i can scrounge up some time for it?19:20
corvus(i think this week is spoken for for me, but maybe next)19:20
clarkbhttps://review.opendev.org/#/c/651390/ is related to that if we want to poke at a slightly less complex version of that CD thing first19:21
mordredcorvus: I ... yeah - I think this next week is spoken for for me too19:21
*** jamesmcarthur has joined #openstack-meeting19:21
mordredI'm still game to do it - but if someone else wants to hit it, I won't be offended19:21
clarkbMaybe thats a resync next week after the holiday thing then?19:21
corvussounds good, we'll see where we are then19:22
clarkbI'm happy to help as well but ya holiday makes this week a hard one19:22
mordredthere's a holiday? I haven't heard mention of that where I am ...19:22
corvusand yeah, that NS change can go in parallel19:22
clarkbmordred: there is probably an expat community that will have a BBQ type thing19:22
clarkbmordred: we had that growing up19:22
corvusoh mordred should be all caught up by next week then, since he moved *out* of a holiday zone :)19:22
corvusmordred: (you're supposed to nomad into places right before major holidays ;)19:23
mordredmaybe I can celebrate king's day late or something instead19:23
mordredcorvus: point taken19:23
clarkb#topic OpenDev19:24
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:24
clarkbLast week I replaced gitea06 finally19:24
corvusclarkb: huzzah, thanks!19:24
clarkbThe new server has a larger uncorrupted rott disk19:24
corvusheh, it had the disk rot19:24
clarkbI also wrote down the process for replacing the gitea nodes in our docs19:24
clarkbso if we have to do that again hopefully it is nice and easy19:25
clarkb(we should consider replacing all of them actually to get bigger ext4 journals and larger disk over all)19:25
clarkbI don't think ^ is urgent but something to keep in mind as we have time19:25
fungiand inoculate the rest of them against diskrot19:25
clarkbSemi related to that its been pointed out that our larger repos like nova perform poorly in gitea19:26
clarkbI responded to the openstack-discuss thread with pointers on how people might help us debug that, but haven't seen a response19:26
corvusyeah, that's a little disappointing19:26
*** panda has quit IRC19:27
clarkbAny other opendev related business?19:27
mordredI imagine our gitea friends would be interested in making improvements if we can collect the debug info from people19:27
*** jamesmcarthur has quit IRC19:28
clarkbmordred: ya I mentioned that upstream is really helpful and would likely want to fix it too19:28
corvuswe heard a lot of feedback that the complex puppet system we had made it hard for people to contribute casually; it's interesting that a shiny new simple dockerfile is not sufficient enticement.19:28
mordredcorvus: dockerfiles are too complicated - if we could just hand out root accounts to developers, then I'm sure people would help19:29
corvusmordred: i guess our standards are too high :)19:29
*** panda has joined #openstack-meeting19:30
clarkbif anyone is listening in I'm happy to assist someone that would like to debug that in the nearer future, I just have no bw to do it myself currently19:30
clarkbOk sounds like that may be it for opendev. Moving on19:32
clarkb#topic Storyboard19:32
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:32
clarkbfungi: diablo_rojo_phon ^ any updates?19:32
clarkbMy IRC client decided that to reload plugins that meant reloading all channel connections and I've apparently not set up #storyboard again19:32
fungithere was another bug triage on friday19:32
funginothing too exciting19:33
fungimost of the active stories in the storyboard project group are now tagged appropriately19:33
fungithat's the only update i'm aware of19:33
clarkb#topic General Topics19:33
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:33
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:33
clarkbfungi: ^ any new progress on the wiki before stepping out for vacation?19:34
clarkband are there changes we should be looking at?19:34
fungii'll know more after https://review.opendev.org/666162 merges19:36
fungii had to recheck it for a beaker problem, apparently19:36
clarkbya that looks consistent19:37
clarkbmay need debugging19:37
clarkbThe last item on the Agenda (we covered mirrors previously) is a cloud resource status update19:37
fungiright, not sure why the same patchset was passing a week ago19:37
clarkbdonnyd has set up users for us in the fortnebula cloud whcih I'm working through sanity checking of right now19:38
clarkb(tempest is running as we speak)19:38
fungiand apparently tempest needs a boatload of ram nowadays?19:38
clarkbyup tempest/devstack is digging into swap about 389MB deep on our 8GB ram nodes19:38
donnydshould we try a larger flavor... maybe like 10 or 12 G of memory19:39
fungiis that due to increased pressure from devstack?19:39
*** enriquetaso has joined #openstack-meeting19:39
donnydIt might just eat all the rams and swap anyways19:39
clarkbdonnyd: we've long pushed for the 8GB number because it is a reasonable number for people to have on their own machines19:39
ianwhrm, we should have the peak memory dumps going on?  does it give a clue what's growing?19:39
clarkbdonnyd: imo the issue here is openstack is using way too much memory19:39
clarkband that should be fixed rather than increasing memory per node (also increasing memory per node would decrease our total number of test instances)19:40
donnydtrue, but if it makes it through the tests faster its a wash19:40
clarkbianw: I haven't dug into it much beyond discovering I had to enable swap to get tempest to pass on these nodes19:40
donnydnot disagreeing, just willing to test it out19:41
clarkbdonnyd: it seems to have run within similar time bounds of other clouds as is so I think we may be fine then push back on openstack to try and improve memory usage19:42
clarkbdonnyd: it runs devstack faster than other clouds and tempest slightly slower so resulting job runtime should be about the same19:42
clarkbmaybe even a little quicker19:42
ianwright; the one to look for is like -> http://logs.openstack.org/68/668668/2/check/tempest-full-py3/65eee4c/controller/logs/screen-peakmem_tracker.txt.gz19:42
ianwthe idea is that whenver free ram is seen to drop, it logs a new dump of what's taking it up19:43
clarkbin any case Once tempest is done I'll post up numbers and if others agree we are in the same region of time I'll build the mirror when donnyd is done twaeking things then we can have nodepool start using the cloud19:43
clarkbI also wanted to do a quick check on the other two clouds where things have been moving. Inap was turned off because they were upgrading the cloud right? Any word on whether or not we'll be able to turn that back on at some point?19:44
fungii haven't heard anything new from mgagne on that19:45
clarkbLooks like pabelanger and ajaeger may have worked with mgagne to disable that19:45
donnydI am pretty much done19:45
clarkbok I can reach out to mgagne and ask if there is any news19:45
clarkbthe last cloud was limestone which has network trouble currently19:45
donnydjust minor sysctl's at this point to get the last few cycles out19:45
mgagneclarkb, fungi: Sorry, no news for now. A coworker is working on that one. I've been busy working on something else. I can ask him asap.19:46
clarkbmgagne: ok not a rush, but didn't want ti falling through the cracks19:46
clarkbmgagne: thank you19:46
clarkbfungi: you were working with logan on limestone right? is the way to monitor that on our end the cacti gaps with our mirror there?19:47
clarkbI guess we can continue to monitor that and if it stops having gaps put the cloud back into service19:47
*** jamesmcarthur has joined #openstack-meeting19:47
clarkbAlright that was all I had19:48
clarkb#topic Open Discussion19:48
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:48
clarkbAnything else?19:48
clarkbI'm happy to end the meeting early if not19:48
*** zaneb has joined #openstack-meeting19:49
fungiyeah that's what i did previously19:49
fungii think logan- hasn't had a chance to look at it again after it went back to having connectivity issues19:50
*** jamesmcarthur has quit IRC19:50
clarkbsounds liek that may be it. Thank you everyone19:51
clarkbFor those of you celebrating holidays have fun!19:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:51
openstackMeeting ended Tue Jul  2 19:51:52 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-02-19.01.html19:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-02-19.01.txt19:51
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-07-02-19.01.log.html19:51
*** raildo has quit IRC19:52
fungithanks clarkb!19:52
*** bnemec has quit IRC19:54
*** raildo has joined #openstack-meeting20:01
*** mmethot has quit IRC20:04
*** mmethot has joined #openstack-meeting20:05
*** bnemec has joined #openstack-meeting20:07
*** eharney has quit IRC20:15
*** ijw has quit IRC20:32
*** vishalmanchanda has quit IRC20:33
*** Lucas_Gray has joined #openstack-meeting20:34
*** Lucas_Gray has quit IRC20:37
*** tssurya has joined #openstack-meeting20:37
*** ijw has joined #openstack-meeting20:37
*** njohnston has quit IRC20:40
*** njohnston has joined #openstack-meeting20:40
*** iyamahat has quit IRC20:41
*** psachin has quit IRC20:42
*** enriquetaso has quit IRC20:42
*** heikkine has quit IRC20:45
*** Lucas_Gray has joined #openstack-meeting20:52
*** ttsiouts has joined #openstack-meeting20:55
*** mmethot has quit IRC20:58
*** enriquetaso has joined #openstack-meeting20:58
*** pcaruana has quit IRC20:58
*** mmethot has joined #openstack-meeting20:58
*** eharney has joined #openstack-meeting20:59
*** senrique_ has joined #openstack-meeting21:01
*** Lucas_Gray has quit IRC21:03
*** enriquetaso has quit IRC21:03
*** Lucas_Gray has joined #openstack-meeting21:04
*** iyamahat has joined #openstack-meeting21:11
*** raildo has quit IRC21:11
*** iyamahat_ has joined #openstack-meeting21:13
*** ijw has quit IRC21:13
*** ijw has joined #openstack-meeting21:14
*** mattw4 has quit IRC21:15
*** iyamahat has quit IRC21:16
*** mattw4 has joined #openstack-meeting21:17
*** ijw has quit IRC21:19
*** eharney has quit IRC21:22
*** jamesmcarthur has joined #openstack-meeting21:22
*** bnemec has quit IRC21:25
*** jamesmcarthur has quit IRC21:27
*** bnemec has joined #openstack-meeting21:27
*** yamahata has joined #openstack-meeting21:30
*** ttsiouts has quit IRC21:37
*** tssurya has quit IRC21:50
*** iyamahat_ has quit IRC21:51
*** senrique_ has quit IRC21:55
*** iyamahat has joined #openstack-meeting21:55
*** carloss has quit IRC22:01
*** ttsiouts has joined #openstack-meeting22:16
*** ttsiouts has quit IRC22:21
*** ykatabam has joined #openstack-meeting22:38
*** panda has quit IRC22:52
*** panda has joined #openstack-meeting22:59
*** hongbin has quit IRC23:06
*** slaweq has quit IRC23:07
*** yamahata has quit IRC23:15
*** yamahata has joined #openstack-meeting23:18
*** mriedem has quit IRC23:20
*** mattw4 has quit IRC23:23
*** lseki has quit IRC23:33
*** ekcs has quit IRC23:44
*** _pewp_ has quit IRC23:45
*** _pewp_ has joined #openstack-meeting23:45

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