Tuesday, 2018-04-10

*** yamamoto has quit IRC00:03
*** annabelleB has quit IRC00:08
*** gyee has quit IRC00:11
*** sshank has quit IRC00:13
*** erlon has joined #openstack-meeting00:17
*** mjturek has quit IRC00:19
*** annabelleB has joined #openstack-meeting00:20
*** zhurong has joined #openstack-meeting00:20
*** number80 has quit IRC00:21
*** HeOS has joined #openstack-meeting00:21
*** jamesmcarthur has joined #openstack-meeting00:26
*** jamesmcarthur has quit IRC00:31
*** number80 has joined #openstack-meeting00:35
*** wanghao has joined #openstack-meeting00:36
*** HeOS has quit IRC00:39
*** wanghao has quit IRC00:39
*** wanghao has joined #openstack-meeting00:40
*** wanghao has quit IRC00:47
*** jamesmcarthur has joined #openstack-meeting00:47
*** wanghao has joined #openstack-meeting00:47
*** aeng has joined #openstack-meeting00:47
*** anilvenkata has quit IRC00:48
*** artom has joined #openstack-meeting00:48
*** shu-mutow has joined #openstack-meeting00:49
*** wanghao has quit IRC00:49
*** tovin07_ has joined #openstack-meeting00:50
*** wanghao has joined #openstack-meeting00:50
*** jamesmcarthur has quit IRC00:51
*** wanghao has quit IRC00:54
*** wanghao has joined #openstack-meeting00:55
*** mriedem_afk has quit IRC01:00
*** wanghao has quit IRC01:00
*** bobh has quit IRC01:01
*** wanghao has joined #openstack-meeting01:01
*** slaweq has joined #openstack-meeting01:03
*** wanghao has quit IRC01:05
*** wanghao has joined #openstack-meeting01:05
*** gman-tx has joined #openstack-meeting01:06
*** slaweq has quit IRC01:08
*** wanghao has quit IRC01:08
*** kaisers has joined #openstack-meeting01:09
*** wanghao has joined #openstack-meeting01:09
*** Zames has joined #openstack-meeting01:09
*** Zames has quit IRC01:10
*** wanghao has quit IRC01:13
*** wanghao has joined #openstack-meeting01:13
*** kaisers has quit IRC01:15
*** salv-orl_ has joined #openstack-meeting01:15
*** epico has joined #openstack-meeting01:15
*** wanghao has quit IRC01:15
*** wanghao has joined #openstack-meeting01:16
*** salv-orlando has quit IRC01:18
*** jamesmcarthur has joined #openstack-meeting01:20
*** wanghao has quit IRC01:20
*** wanghao has joined #openstack-meeting01:22
*** fzdarsky_ has joined #openstack-meeting01:22
*** epico has quit IRC01:23
*** epico has joined #openstack-meeting01:24
*** wanghao has quit IRC01:24
*** wanghao has joined #openstack-meeting01:25
*** fzdarsky|afk has quit IRC01:25
*** fzdarsky_ has quit IRC01:27
*** janki has joined #openstack-meeting01:27
*** wanghao has quit IRC01:27
*** wanghao has joined #openstack-meeting01:28
*** claudiub has quit IRC01:31
*** fzdarsky_ has joined #openstack-meeting01:32
*** wanghao has quit IRC01:32
*** wanghao has joined #openstack-meeting01:33
*** hongbin has joined #openstack-meeting01:33
*** markstur_ has quit IRC01:34
*** wanghao has quit IRC01:35
*** wanghao has joined #openstack-meeting01:35
*** wanghao has quit IRC01:40
*** jchhatbar has joined #openstack-meeting01:40
*** cloudrancher has quit IRC01:41
*** wanghao has joined #openstack-meeting01:41
*** cloudrancher has joined #openstack-meeting01:41
*** janki has quit IRC01:43
*** wanghao has quit IRC01:46
*** wanghao has joined #openstack-meeting01:46
*** bkopilov has quit IRC01:52
*** wanghao has quit IRC01:52
*** wanghao has joined #openstack-meeting01:53
*** yamahata has quit IRC01:53
*** annabelleB has quit IRC01:57
*** wanghao has quit IRC01:57
*** jamesmcarthur has quit IRC01:58
*** wanghao has joined #openstack-meeting01:58
*** wanghao has quit IRC02:06
*** wanghao has joined #openstack-meeting02:06
*** salv-orlando has joined #openstack-meeting02:10
*** wanghao has quit IRC02:10
*** wanghao has joined #openstack-meeting02:11
*** salv-orl_ has quit IRC02:13
*** lhx_ has joined #openstack-meeting02:17
*** wanghao has quit IRC02:21
*** wanghao has joined #openstack-meeting02:21
*** erlon has quit IRC02:25
*** wanghao has quit IRC02:25
*** wanghao has joined #openstack-meeting02:26
*** kevzha01 has joined #openstack-meeting02:26
*** kevzha01 is now known as kevinz02:26
*** SumitNaiksatam has joined #openstack-meeting02:29
*** ricolin has joined #openstack-meeting02:29
*** wanghao has quit IRC02:29
*** wanghao has joined #openstack-meeting02:30
*** andreas_s has joined #openstack-meeting02:32
*** annabelleB has joined #openstack-meeting02:32
*** wanghao has quit IRC02:33
*** wanghao has joined #openstack-meeting02:33
*** andreas_s has quit IRC02:37
*** wanghao has quit IRC02:38
*** wanghao has joined #openstack-meeting02:39
*** amodi has quit IRC02:40
*** SumitNaiksatam has quit IRC02:41
*** yamamoto has joined #openstack-meeting02:41
*** wanghao has quit IRC02:41
*** wanghao has joined #openstack-meeting02:41
*** yamamoto has quit IRC02:45
*** jamesmcarthur has joined #openstack-meeting02:47
*** wanghao has quit IRC02:47
*** wanghao has joined #openstack-meeting02:48
*** artom has quit IRC02:50
*** tovin07_ has quit IRC02:51
*** wanghao has quit IRC02:51
*** psachin has joined #openstack-meeting02:51
*** rbudden has quit IRC02:52
*** wanghao has joined #openstack-meeting02:52
*** annabelleB has quit IRC02:52
*** gman-tx has quit IRC02:55
*** wanghao has quit IRC02:57
*** wanghao has joined #openstack-meeting02:57
*** fnaval has quit IRC03:00
*** wanghao has quit IRC03:00
*** wanghao has joined #openstack-meeting03:00
*** slaweq has joined #openstack-meeting03:04
*** wanghao has quit IRC03:04
*** wanghao has joined #openstack-meeting03:05
*** slaweq has quit IRC03:09
*** wanghao has quit IRC03:09
*** wanghao has joined #openstack-meeting03:09
*** harlowja has quit IRC03:16
*** wanghao has quit IRC03:16
*** ianychoi has quit IRC03:16
*** wanghao has joined #openstack-meeting03:16
*** bkopilov has joined #openstack-meeting03:19
*** ianychoi has joined #openstack-meeting03:20
*** jamesmcarthur has quit IRC03:22
*** wanghao has quit IRC03:22
*** wanghao has joined #openstack-meeting03:23
*** bobh has joined #openstack-meeting03:29
*** wanghao has quit IRC03:29
*** markstur has joined #openstack-meeting03:30
*** wanghao has joined #openstack-meeting03:30
*** bobh has quit IRC03:35
*** wanghao has quit IRC03:36
*** wanghao has joined #openstack-meeting03:36
*** SumitNaiksatam has joined #openstack-meeting03:36
*** naichuans_ has joined #openstack-meeting03:41
*** zhurong has quit IRC03:41
*** wanghao has quit IRC03:41
*** wanghao has joined #openstack-meeting03:42
*** naichuans_ has quit IRC03:45
*** naichuans_ has joined #openstack-meeting03:45
*** wanghao has quit IRC03:46
*** wanghao has joined #openstack-meeting03:47
*** esberglu has quit IRC03:49
*** wanghao has quit IRC03:51
*** wanghao has joined #openstack-meeting03:52
*** tpatil has joined #openstack-meeting03:54
*** niraj_singh has left #openstack-meeting03:56
*** hongbin has quit IRC03:57
*** niraj_singh has joined #openstack-meeting03:57
*** wanghao has quit IRC03:57
*** harlowja has joined #openstack-meeting03:57
*** wanghao has joined #openstack-meeting03:57
*** Dinesh_Bhor has joined #openstack-meeting03:58
samPHi all for Masakari04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Apr 10 04:00:06 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
*** wanghao has quit IRC04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPHi all04:00
samPsorry for last 2 weeks, wasn't able to do much work.04:00
*** sridharg has joined #openstack-meeting04:00
*** wanghao has joined #openstack-meeting04:00
samP#topic Bugs/Patches04:01
*** openstack changes topic to "Bugs/Patches (Meeting topic: masakari)"04:01
samPAny bugs or patches need to discuss?04:01
*** rkmrHonjo has joined #openstack-meeting04:02
tpatilChange service type patches are on hold as these patches won't be needed after newer version of openstacksdk is released04:02
*** wanghao has quit IRC04:02
samPtpatil: got it04:02
*** wanghao has joined #openstack-meeting04:03
tpatil# link : https://review.openstack.org/#/c/536668/04:03
tpatilNeed to find out when openstacksdk team will release newer version04:03
tpatilbecoz the current master branch is totally broken04:04
samPtpatil: let's ask in ML04:04
*** wanghao has quit IRC04:04
*** wanghao has joined #openstack-meeting04:05
*** pcaruana has joined #openstack-meeting04:06
tpatilLouie has requested to review his specs and patches04:06
tpatil#link https://review.openstack.org/#/c/547118/04:06
tpatil# link https://review.openstack.org/#/c/534958/04:06
*** wanghao has quit IRC04:07
tpatilI have started reviewing his implementation04:07
tpatilDo you have any comments on his specs?04:07
*** wanghao has joined #openstack-meeting04:07
samPtpatil: No comments on specs from my side.04:08
samPtpatil: I partially review the implementation. since it is a large patch, nee more time.04:09
tpatilsamP: Mee too, it's taking lot of time04:10
samPI'll try my best to pass comments as soon as possible.04:10
*** vabada2 has joined #openstack-meeting04:10
*** wanghao has quit IRC04:10
samPBut for the spec, if you have no comments, please mark your +1 for that.04:11
*** wanghao has joined #openstack-meeting04:11
samPI will +1 for workflow04:11
*** liuzz has quit IRC04:11
tpatilDinesh has voted -1 and the author will need to address his comments04:11
*** strigazi has quit IRC04:11
tpatilDinesh_Bhor: Did you propose a patch in masakari-specs to add rocky folder?04:12
samP#link https://review.openstack.org/#/c/469070/04:12
*** wanghao has quit IRC04:12
Dinesh_Bhortpatil: Not yet, I will propose it soon04:12
*** vabada has quit IRC04:13
*** wanghao has joined #openstack-meeting04:13
samPDinesh_Bhor: thanks04:13
tpatilDinesh_Bhor: Thank you04:13
*** strigazi has joined #openstack-meeting04:14
*** ianychoi has quit IRC04:14
samPI will ask Greg to move the spec once we create the directory04:15
*** wanghao has quit IRC04:15
*** wanghao has joined #openstack-meeting04:15
*** ianychoi has joined #openstack-meeting04:16
*** pcaruana has quit IRC04:16
samPI would like to know the current status of masakari command04:17
samPsorry for me not in touch04:17
samPrkmrHonjo: you propose a new patch?04:17
*** wanghao has quit IRC04:17
tpatilThere is a dependency on newer version of openstacksdk04:17
*** wanghao has joined #openstack-meeting04:18
samP#link https://review.openstack.org/#/c/557634/04:18
samP^^ is this the one?04:18
tpatilsamP: Correct04:18
samPhumm, https://review.openstack.org/#/c/555710/ is merged04:20
*** trinaths has joined #openstack-meeting04:20
*** wanghao has quit IRC04:20
*** wanghao has joined #openstack-meeting04:21
samPfor stable/queens, this is still valid,04:21
samP#link https://review.openstack.org/#/c/553319/04:21
samP^^ sorry for the delay. I will review and merge this and then push a new version for python-masakariclient04:22
samPtpatil: thanks04:23
*** wanghao has quit IRC04:23
samPAny other bugs or patches need to discuss?04:23
*** wanghao has joined #openstack-meeting04:24
samPDinesh_Bhor: thanks for uwsgi support04:25
tpatil# link : https://review.openstack.org/#/c/55905104:25
samP#link https://review.openstack.org/#/c/553319/04:25
*** liuzz has joined #openstack-meeting04:25
tpatilIn this patch, policy.json is referenced. But I have added one new item in rocky etherpad to Register and Document Policy in Code04:26
*** wanghao has quit IRC04:26
tpatil# link : https://etherpad.openstack.org/p/masakari-rocky-work-items04:26
*** wanghao has joined #openstack-meeting04:26
tpatilIf we decide to implement policy changes, then no need to add policy.json in data_files in the above patch04:28
tpatilI have added three new items for Rocky, please check lines #49-5404:28
tpatilAll these new items are community wide goal04:29
tpatiland I think it's applicable for Masakari as well04:29
*** wanghao has quit IRC04:29
samPtpatil: thanks. mutable configs, mox3, and doc policy in code04:29
samPtpatil: it is.04:29
*** wanghao has joined #openstack-meeting04:30
samPtpatil: I think above patch is based on current code base of masakari, where policy.json has fixed content04:30
*** radeks has joined #openstack-meeting04:31
samPtpatil: In that point of view, policy.json could be shipped in data_files04:31
tpatilsamP: That's true, but if we decide to implement policy in code, then no need to mention policy.json in data_files04:32
*** wanghao has quit IRC04:32
samPtpatil: agree.04:32
tpatilit's only needed if operator wants to override default policy04:32
*** wanghao has joined #openstack-meeting04:33
samPtpatil: noob question: how operator finds sample policy file to edit?04:34
samPtpatil: agree. after implementing policy in code, we don't need policy.json in /etc/masakari04:35
tpatilThere is a policy generator tool that you can use to generate policy.json04:35
*** wanghao has quit IRC04:36
*** wanghao has joined #openstack-meeting04:37
samP#link https://specs.openstack.org/openstack/oslo-specs/specs/newton/policy-sample-generation.html04:37
samPI guess ^^04:37
samPtpatil: got it. I will look for that later.04:38
samPI will put my comments on that patch04:38
tpatilsamP: OK, nova example : https://github.com/openstack/nova/blob/master/etc/nova/nova-policy-generator.conf04:38
*** wanghao has quit IRC04:39
tpatilthis is the command to generate policy : tox -egenpolicy04:39
samPtpatil: thanks for the info04:39
*** wanghao has joined #openstack-meeting04:39
samPAny other bugs or patches?04:41
niraj_singhmasakaridashboard patches are up for community review waiting for openstacksdk release04:41
samPniraj_singh: thanks04:42
*** wanghao has quit IRC04:42
samPniraj_singh: I think you also waiting for this vv04:43
samP#link https://review.openstack.org/#/c/555710/04:43
*** wanghao has joined #openstack-meeting04:43
samPah, yes, it's in tpatil's comment04:43
samPniraj_singh: thanks, I did a recheck for zuul -1, I will review this04:45
niraj_singhok thank you04:45
*** wanghao has quit IRC04:45
*** wanghao has joined #openstack-meeting04:46
tpatilsamP: recheck won't help as openstacksdk newer version is not yet released04:46
tpatilsamP: Niraj has confirmed his dashboard changes are working as expected after updating his dev environment with latest openstacksdk master branch04:47
samPtpatil: oh yes. thanks04:47
tpatilWe need newer version of openstacksdk badly04:48
samPtpatil: understand, let's ask it on ML04:48
tpatilsamP: Yes04:49
samPI will talk to release team and monty04:49
*** wanghao has quit IRC04:49
tpatilThat will be great, Thank you04:50
*** wanghao has joined #openstack-meeting04:50
samP#topic Discussion points04:50
*** openstack changes topic to "Discussion points (Meeting topic: masakari)"04:50
samPAbout next release,04:50
samP#link https://review.openstack.org/#/c/557968/04:51
samPNow we have 4 projects for Rocky release. We have follow the deadline04:52
samP#link https://releases.openstack.org/rocky/schedule.html04:52
*** wanghao has quit IRC04:53
samPNext milestone is Jun 04 - Jun 08 R-1204:53
samPRocky-2 milestone04:53
*** wanghao has joined #openstack-meeting04:53
samPAnd I got 2 session for masakari in Vancouver summit04:54
*** lpetrut has joined #openstack-meeting04:54
samPProject Update and Project Onboarding04:54
samPPlease let me know if you would like to talk in sessions04:55
*** wanghao has quit IRC04:55
tpatilThis time I might not visit Vancouver summit04:56
samPtpatil: really?04:56
*** wanghao has joined #openstack-meeting04:56
samPThat's too bad ;), anyway how about other members?04:57
tpatilI will update you about it in the next week04:57
samPtpatil: sure..04:57
*** marios has joined #openstack-meeting04:58
*** wanghao has quit IRC04:58
samPplease let me know if you would like to talk, specially in project update session04:58
tpatilsamP: Sure04:58
*** wanghao has joined #openstack-meeting04:58
samPplease consider04:59
samPWe only have 1 mins left04:59
samPThanks you all for your time04:59
samPPlease use IRC #openstack-masakri or ML with [masakari] for further discussions04:59
samPThanks again..04:59
*** Dinesh_Bhor has quit IRC05:00
*** wanghao has quit IRC05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"05:00
openstackMeeting ended Tue Apr 10 05:00:04 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-04-10-04.00.html05:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-04-10-04.00.txt05:00
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-04-10-04.00.log.html05:00
*** rkmrHonjo has quit IRC05:00
*** wanghao has joined #openstack-meeting05:00
*** claudiub has joined #openstack-meeting05:04
*** naichuans_ is now known as naichuans05:05
*** wanghao has quit IRC05:07
*** wanghao has joined #openstack-meeting05:08
*** yamamoto has joined #openstack-meeting05:08
*** Dinesh_Bhor has joined #openstack-meeting05:09
*** ekcs has joined #openstack-meeting05:09
*** yamahata has joined #openstack-meeting05:10
*** wanghao has quit IRC05:10
*** wanghao has joined #openstack-meeting05:11
*** links has joined #openstack-meeting05:11
*** yamamoto has quit IRC05:12
*** armax has quit IRC05:13
*** strigazi_ has joined #openstack-meeting05:13
*** wanghao has quit IRC05:13
*** wanghao has joined #openstack-meeting05:14
*** vabada has joined #openstack-meeting05:14
*** vabada2 has quit IRC05:17
*** strigazi has quit IRC05:17
*** wanghao has quit IRC05:17
*** wanghao has joined #openstack-meeting05:17
*** tpatil has quit IRC05:19
*** wanghao has quit IRC05:20
*** cloudrancher has quit IRC05:21
*** wanghao has joined #openstack-meeting05:21
*** jamesmcarthur has joined #openstack-meeting05:23
*** wanghao has quit IRC05:25
*** wanghao has joined #openstack-meeting05:25
*** jamesmcarthur has quit IRC05:27
*** kaisers has joined #openstack-meeting05:28
*** wanghao has quit IRC05:29
*** wanghao has joined #openstack-meeting05:30
*** Li_Jiale has joined #openstack-meeting05:31
*** kaisers has quit IRC05:32
*** wanghao has quit IRC05:34
*** wanghao has joined #openstack-meeting05:35
*** lpetrut has quit IRC05:37
*** wanghao has quit IRC05:39
*** Li_Jiale has quit IRC05:39
*** wanghao has joined #openstack-meeting05:40
*** longkb_ has joined #openstack-meeting05:42
*** Li_Jiale has joined #openstack-meeting05:43
*** wanghao has quit IRC05:44
*** wanghao has joined #openstack-meeting05:44
*** ianychoi has quit IRC05:47
*** lpetrut has joined #openstack-meeting05:47
*** ianychoi has joined #openstack-meeting05:49
*** wanghao has quit IRC05:49
*** wanghao has joined #openstack-meeting05:49
*** ekcs has quit IRC05:51
*** ekcs has joined #openstack-meeting05:53
*** wanghao has quit IRC05:54
*** wanghao has joined #openstack-meeting05:55
*** belmoreira has joined #openstack-meeting06:00
*** wanghao has quit IRC06:00
*** wanghao has joined #openstack-meeting06:00
*** wanghao has quit IRC06:04
*** wanghao has joined #openstack-meeting06:05
*** kaisers has joined #openstack-meeting06:07
*** markstur has quit IRC06:10
*** wanghao has quit IRC06:11
*** wanghao has joined #openstack-meeting06:11
*** Alex_Staf has joined #openstack-meeting06:12
*** kaisers has quit IRC06:14
*** kaisers has joined #openstack-meeting06:14
*** wanghao has quit IRC06:14
*** wanghao has joined #openstack-meeting06:15
*** rubasov has joined #openstack-meeting06:16
*** wanghao has quit IRC06:18
*** wanghao has joined #openstack-meeting06:19
*** lpetrut has quit IRC06:19
*** wanghao has quit IRC06:25
*** wanghao has joined #openstack-meeting06:25
*** andreas_s has joined #openstack-meeting06:29
*** wanghao has quit IRC06:29
*** e0ne has joined #openstack-meeting06:29
*** wanghao has joined #openstack-meeting06:29
*** Dinesh_Bhor has quit IRC06:30
*** dbecker has quit IRC06:30
*** Dinesh_Bhor has joined #openstack-meeting06:32
*** wanghao has quit IRC06:32
*** wanghao has joined #openstack-meeting06:33
*** anilvenkata has joined #openstack-meeting06:35
*** wanghao has quit IRC06:36
*** wanghao has joined #openstack-meeting06:36
*** yamamoto has joined #openstack-meeting06:37
*** pcaruana has joined #openstack-meeting06:40
*** wanghao has quit IRC06:40
*** harlowja has quit IRC06:40
*** wanghao has joined #openstack-meeting06:40
*** Guest66700 has joined #openstack-meeting06:40
*** rcernin has quit IRC06:41
*** Li_Jiale has quit IRC06:42
*** dbecker has joined #openstack-meeting06:43
*** wanghao has quit IRC06:43
*** wanghao has joined #openstack-meeting06:44
*** kopecmartin has joined #openstack-meeting06:44
*** arnewiebalck has joined #openstack-meeting06:47
*** slaweq has joined #openstack-meeting06:47
*** wanghao has quit IRC06:47
*** salv-orlando has quit IRC06:48
*** wanghao has joined #openstack-meeting06:48
*** ekcs has quit IRC06:48
*** salv-orlando has joined #openstack-meeting06:48
*** wanghao has quit IRC06:50
*** wanghao has joined #openstack-meeting06:51
*** alexchadin has joined #openstack-meeting06:52
*** slaweq has quit IRC06:53
*** salv-orlando has quit IRC06:53
*** lpetrut has joined #openstack-meeting06:53
*** wanghao has quit IRC06:53
*** wanghao has joined #openstack-meeting06:54
*** slaweq has joined #openstack-meeting06:56
*** wanghao has quit IRC06:56
*** wanghao has joined #openstack-meeting06:57
*** wanghao has quit IRC07:02
*** wanghao has joined #openstack-meeting07:02
*** lpetrut has quit IRC07:03
*** wanghao has quit IRC07:05
*** wanghao has joined #openstack-meeting07:06
*** ad_ri3n_ has joined #openstack-meeting07:07
*** kaisers has quit IRC07:08
*** wanghao has quit IRC07:12
*** yamamoto has quit IRC07:12
*** wanghao has joined #openstack-meeting07:12
*** yamamoto has joined #openstack-meeting07:14
*** yamamoto has quit IRC07:14
*** yamamoto has joined #openstack-meeting07:15
*** wanghao has quit IRC07:15
*** wanghao has joined #openstack-meeting07:15
*** tesseract has joined #openstack-meeting07:19
*** wanghao has quit IRC07:19
*** yamamoto has quit IRC07:19
*** wanghao has joined #openstack-meeting07:20
*** radeks has quit IRC07:21
*** radeks has joined #openstack-meeting07:21
*** wanghao has quit IRC07:22
*** wanghao has joined #openstack-meeting07:23
*** salv-orlando has joined #openstack-meeting07:23
*** tssurya has joined #openstack-meeting07:26
*** wanghao has quit IRC07:26
*** wanghao has joined #openstack-meeting07:27
*** phil_ has joined #openstack-meeting07:30
*** jhesketh_ has joined #openstack-meeting07:31
*** wanghao has quit IRC07:31
*** wanghao has joined #openstack-meeting07:32
*** Tom-Tom has joined #openstack-meeting07:33
*** dangtrinhnt has joined #openstack-meeting07:33
*** wanghao has quit IRC07:37
*** jhesketh has quit IRC07:37
*** wanghao has joined #openstack-meeting07:37
*** fzdarsky_ is now known as fzdarsky07:39
*** Dinesh_Bhor has quit IRC07:40
*** kaisers has joined #openstack-meeting07:40
*** wanghao has quit IRC07:40
*** wanghao has joined #openstack-meeting07:41
*** belmoreira has quit IRC07:43
*** Dinesh_Bhor has joined #openstack-meeting07:46
*** wanghao has quit IRC07:46
*** electrofelix has joined #openstack-meeting07:47
*** wanghao has joined #openstack-meeting07:47
*** keiko has joined #openstack-meeting07:49
*** rossella_s has quit IRC07:50
*** wanghao has quit IRC07:50
*** wanghao has joined #openstack-meeting07:50
*** kaisers has quit IRC07:52
*** kaisers has joined #openstack-meeting07:52
*** wanghao has quit IRC07:53
*** wanghao has joined #openstack-meeting07:54
*** gongysh has joined #openstack-meeting07:55
*** wanghao has quit IRC07:58
*** wanghao has joined #openstack-meeting07:58
*** wanghao has quit IRC08:04
*** hemna_ has quit IRC08:04
*** wanghao has joined #openstack-meeting08:05
*** epico has quit IRC08:08
*** wanghao has quit IRC08:08
*** wanghao has joined #openstack-meeting08:09
*** wanghao has quit IRC08:10
*** wanghao has joined #openstack-meeting08:12
*** dangtrinhnt has quit IRC08:13
*** lpetrut has joined #openstack-meeting08:16
*** wanghao has quit IRC08:17
*** longkb_ has left #openstack-meeting08:17
*** hoangcx_ has joined #openstack-meeting08:19
*** gongysh has quit IRC08:20
*** hoangcx_ is now known as hoangcx08:20
*** gongysh has joined #openstack-meeting08:20
*** gongysh has quit IRC08:20
*** hoangcx has quit IRC08:22
*** hoangcx_ has joined #openstack-meeting08:22
*** hoangcx_ is now known as hoangcx08:22
*** wanghao has joined #openstack-meeting08:22
*** jesusaur has quit IRC08:23
*** epico has joined #openstack-meeting08:24
*** jesusaur has joined #openstack-meeting08:26
*** wanghao has quit IRC08:26
*** priteau has joined #openstack-meeting08:27
*** wanghao has joined #openstack-meeting08:27
*** wanghao has quit IRC08:30
*** wanghao has joined #openstack-meeting08:31
*** krenczewski has quit IRC08:38
*** wanghao has quit IRC08:38
*** krenczewski has joined #openstack-meeting08:38
*** wanghao has joined #openstack-meeting08:38
*** hoangcx_ has joined #openstack-meeting08:41
*** ssbarnea_ has joined #openstack-meeting08:43
*** wanghao has quit IRC08:43
*** wanghao has joined #openstack-meeting08:43
*** hoangcx has quit IRC08:43
*** rbartal has joined #openstack-meeting08:44
*** Li_Jiale has joined #openstack-meeting08:45
*** epico has quit IRC08:45
*** wanghao has quit IRC08:45
*** gongysh has joined #openstack-meeting08:46
*** wanghao has joined #openstack-meeting08:46
*** Guest66700 has quit IRC08:49
*** radeks has quit IRC08:50
*** radeks has joined #openstack-meeting08:50
*** wanghao has quit IRC08:50
*** wanghao has joined #openstack-meeting08:51
*** ssbarnea_ has quit IRC08:51
*** krenczewski has quit IRC08:53
*** wanghao has quit IRC08:54
*** wanghao has joined #openstack-meeting08:55
*** krenczewski has joined #openstack-meeting08:56
*** wanghao has quit IRC08:59
*** caowei has quit IRC08:59
*** wanghao has joined #openstack-meeting09:00
*** Li_Jiale has quit IRC09:02
*** belmoreira has joined #openstack-meeting09:03
*** HeOS has joined #openstack-meeting09:03
*** wanghao has quit IRC09:03
*** wanghao has joined #openstack-meeting09:04
*** keiko has quit IRC09:04
*** pcaruana has quit IRC09:04
*** epico has joined #openstack-meeting09:06
*** wanghao has quit IRC09:07
*** wanghao has joined #openstack-meeting09:07
*** aeng has quit IRC09:12
*** wanghao has quit IRC09:14
*** gongysh has quit IRC09:15
*** wanghao has joined #openstack-meeting09:15
*** yamamoto has joined #openstack-meeting09:15
*** gongysh has joined #openstack-meeting09:16
*** qwebirc32653 has joined #openstack-meeting09:17
*** wanghao has quit IRC09:17
*** shu-mutow has quit IRC09:17
*** links has quit IRC09:18
*** wanghao has joined #openstack-meeting09:18
*** qwebirc32653 has quit IRC09:18
*** wanghao has quit IRC09:22
*** wanghao has joined #openstack-meeting09:23
*** ricolin has quit IRC09:23
*** wanghao has quit IRC09:27
*** wanghao has joined #openstack-meeting09:27
*** Dinesh_Bhor has quit IRC09:31
*** wanghao has quit IRC09:31
*** wanghao has joined #openstack-meeting09:32
*** Zames_ has joined #openstack-meeting09:33
*** links has joined #openstack-meeting09:33
*** caowei has joined #openstack-meeting09:33
*** wanghao has quit IRC09:34
*** wanghao has joined #openstack-meeting09:34
*** Zames_ has quit IRC09:37
*** wanghao has quit IRC09:40
*** yamamoto has quit IRC09:41
*** wanghao has joined #openstack-meeting09:41
*** yamamoto has joined #openstack-meeting09:41
*** dosaboy has quit IRC09:42
*** ad_ri3n_ has quit IRC09:45
*** ad_ri3n_ has joined #openstack-meeting09:45
*** wanghao has quit IRC09:45
*** dosaboy has joined #openstack-meeting09:45
*** wanghao has joined #openstack-meeting09:46
*** wanghao has quit IRC09:46
*** hoangcx__ has joined #openstack-meeting09:47
*** dosaboy has quit IRC09:48
*** dosaboy has joined #openstack-meeting09:49
*** dosaboy has quit IRC09:49
*** Tom-Tom has quit IRC09:50
*** dosaboy has joined #openstack-meeting09:50
*** Tom-Tom has joined #openstack-meeting09:51
*** dosaboy has quit IRC09:51
*** hoangcx_ has quit IRC09:52
*** alexchadin has quit IRC09:52
*** hoangcx__ has quit IRC09:52
*** Tom-Tom has quit IRC09:52
*** hoangcx_ has joined #openstack-meeting09:55
*** trinaths has quit IRC09:55
*** dosaboy has joined #openstack-meeting09:56
*** epico has quit IRC09:57
*** hoangcx_ has quit IRC09:57
*** hoangcx has joined #openstack-meeting09:57
*** salv-orl_ has joined #openstack-meeting09:59
*** salv-orl_ has quit IRC10:01
*** strigazi_ is now known as strigazi10:01
*** salv-orl_ has joined #openstack-meeting10:01
*** kaisers1 has quit IRC10:02
*** jesusaur has quit IRC10:02
*** salv-orlando has quit IRC10:02
*** radeks has quit IRC10:03
*** kaisers1 has joined #openstack-meeting10:03
*** salv-orl_ has quit IRC10:06
*** fzdarsky has quit IRC10:09
*** fzdarsky has joined #openstack-meeting10:10
*** fzdarsky has quit IRC10:15
*** jesusaur has joined #openstack-meeting10:15
*** gongysh has quit IRC10:15
*** yamamoto has quit IRC10:17
*** fzdarsky has joined #openstack-meeting10:20
*** diablo_rojo has quit IRC10:20
*** yamamoto has joined #openstack-meeting10:21
*** epico has joined #openstack-meeting10:23
*** jamesmcarthur has joined #openstack-meeting10:24
*** yamamoto has quit IRC10:27
*** yamamoto has joined #openstack-meeting10:27
*** jamesmcarthur has quit IRC10:29
*** gongysh has joined #openstack-meeting10:35
*** hoangcx_ has joined #openstack-meeting10:36
*** hoangcx has quit IRC10:36
*** diablo_rojo has joined #openstack-meeting10:37
*** hoangcx_ is now known as hoangcx10:44
*** radeks has joined #openstack-meeting10:49
*** bkopilov has quit IRC10:51
*** hoangcx_ has joined #openstack-meeting10:53
*** hoangcx has quit IRC10:57
*** yamamoto has quit IRC10:58
*** cloudrancher has joined #openstack-meeting10:59
*** strigazi is now known as strigaz_10:59
*** strigaz_ is now known as strigazi_10:59
*** strigazi_ is now known as strigazi10:59
*** yamamoto has joined #openstack-meeting11:00
*** tpsilva has joined #openstack-meeting11:01
*** yamamoto has quit IRC11:01
*** salv-orlando has joined #openstack-meeting11:02
*** sambetts|afk is now known as sambetts11:04
*** salv-orlando has quit IRC11:06
*** hoangcx has joined #openstack-meeting11:07
*** epico has quit IRC11:09
*** hoangcx_ has quit IRC11:09
*** dprince has joined #openstack-meeting11:20
*** links has quit IRC11:26
*** jchhatbar has quit IRC11:27
*** dprince has quit IRC11:28
*** hoangcx_ has joined #openstack-meeting11:28
*** arxcruz|ruck has quit IRC11:29
*** hoangcx has quit IRC11:31
*** alexchadin has joined #openstack-meeting11:31
*** caowei has quit IRC11:32
*** artom has joined #openstack-meeting11:38
*** links has joined #openstack-meeting11:39
*** markvoelker has joined #openstack-meeting11:40
*** arxcruz has joined #openstack-meeting11:47
*** arxcruz is now known as arxcruz|ruck11:48
*** sidx64 has joined #openstack-meeting11:50
*** Alex_Staf has quit IRC11:51
*** zhurong has joined #openstack-meeting11:54
*** salv-orlando has joined #openstack-meeting12:02
*** weshay_pto is now known as weshay12:03
*** rfolco|off is now known as rfolco|rover12:03
*** artom has quit IRC12:05
*** salv-orlando has quit IRC12:07
*** janki has joined #openstack-meeting12:11
*** gongysh has quit IRC12:11
*** raildo has joined #openstack-meeting12:17
*** edmondsw has joined #openstack-meeting12:17
*** jchhatbar has joined #openstack-meeting12:19
*** bkopilov has joined #openstack-meeting12:20
*** janki has quit IRC12:22
*** gouthamr has joined #openstack-meeting12:23
*** edmondsw has quit IRC12:28
*** VW has joined #openstack-meeting12:29
*** rbudden has joined #openstack-meeting12:35
*** ad_ri3n_ has quit IRC12:35
*** yamamoto has joined #openstack-meeting12:35
*** ad_ri3n_ has joined #openstack-meeting12:36
*** sidx64_ has joined #openstack-meeting12:38
*** psachin has quit IRC12:38
*** sidx64_ has quit IRC12:39
*** sidx64 has quit IRC12:39
*** pchavva has joined #openstack-meeting12:39
*** yamamoto has quit IRC12:41
*** gouthamr has quit IRC12:43
*** gouthamr has joined #openstack-meeting12:44
*** yamamoto has joined #openstack-meeting12:44
*** pcaruana has joined #openstack-meeting12:44
*** gouthamr has quit IRC12:45
*** sidx64 has joined #openstack-meeting12:46
*** gman-tx has joined #openstack-meeting12:48
*** edmondsw has joined #openstack-meeting12:51
*** mriedem has joined #openstack-meeting12:52
*** julim has quit IRC12:52
*** julim has joined #openstack-meeting12:52
*** salv-orlando has joined #openstack-meeting12:53
*** zhurong has quit IRC12:54
*** sidx64 has quit IRC12:55
*** rbowen has quit IRC12:57
*** yamamoto has quit IRC12:57
*** radeks has quit IRC12:58
*** radeks has joined #openstack-meeting12:58
*** dustins has joined #openstack-meeting12:59
*** zhurong has joined #openstack-meeting12:59
*** rbowen has joined #openstack-meeting13:00
*** mjturek has joined #openstack-meeting13:01
*** alexchadin has quit IRC13:02
*** fabian has joined #openstack-meeting13:02
XueFeng#startmeeting senlin13:03
openstackMeeting started Tue Apr 10 13:03:18 2018 UTC and is due to finish in 60 minutes.  The chair is XueFeng. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
*** openstack changes topic to " (Meeting topic: senlin)"13:03
openstackThe meeting name has been set to 'senlin'13:03
*** fabian is now known as chenyb4_13:04
*** salv-orl_ has joined #openstack-meeting13:04
chenyb4_hi, XueFeng13:05
*** salv-orlando has quit IRC13:05
*** sidx64 has joined #openstack-meeting13:05
*** finucannot is now known as stephenfin13:05
*** hoangcx has joined #openstack-meeting13:07
*** yamamoto has joined #openstack-meeting13:07
XueFengNo things need to discuss this week. We will end meeting13:07
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"13:07
openstackMeeting ended Tue Apr 10 13:07:33 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2018/senlin.2018-04-10-13.03.html13:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2018/senlin.2018-04-10-13.03.txt13:07
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2018/senlin.2018-04-10-13.03.log.html13:07
*** chenyb4_ is now known as chenyb413:09
*** Alex_Staf has joined #openstack-meeting13:09
*** hoangcx_ has quit IRC13:11
*** toscalix_ has joined #openstack-meeting13:11
*** xinhuili has joined #openstack-meeting13:12
*** zhurong has quit IRC13:13
*** yamamoto has quit IRC13:16
*** lhx_ has quit IRC13:19
*** yamamoto has joined #openstack-meeting13:20
*** sidx64 has quit IRC13:22
*** yamamoto has quit IRC13:23
*** cloudrancher has quit IRC13:25
*** kopecmartin has quit IRC13:26
*** cloudrancher has joined #openstack-meeting13:26
*** esberglu has joined #openstack-meeting13:26
*** toscalix_ has quit IRC13:27
*** sidx64 has joined #openstack-meeting13:29
*** kopecmartin has joined #openstack-meeting13:29
*** phil_ has quit IRC13:29
*** xinhuili has quit IRC13:30
*** dklyle has quit IRC13:33
*** alexchadin has joined #openstack-meeting13:34
*** lbragstad has joined #openstack-meeting13:42
*** lhx_ has joined #openstack-meeting13:43
*** annabelleB has joined #openstack-meeting13:46
*** toscalix_ has joined #openstack-meeting13:47
*** toscalix_ has quit IRC13:47
*** simonmcc has quit IRC13:48
*** simonmcc has joined #openstack-meeting13:49
*** toshii has joined #openstack-meeting13:50
*** hongbin has joined #openstack-meeting13:50
*** serverascode has quit IRC13:50
*** serverascode has joined #openstack-meeting13:51
*** yamamoto has joined #openstack-meeting13:51
*** janzian has joined #openstack-meeting13:53
*** jamesmcarthur has joined #openstack-meeting13:53
*** yamamoto has quit IRC13:54
*** fdegir has quit IRC13:54
*** kopecmartin has quit IRC13:54
*** fdegir has joined #openstack-meeting13:54
*** betherly has quit IRC13:56
*** lajoskatona_ has joined #openstack-meeting13:57
*** betherly has joined #openstack-meeting13:57
*** annabelleB has quit IRC13:57
*** annabelleB has joined #openstack-meeting13:58
*** mlavalle has joined #openstack-meeting13:59
*** pasuder has joined #openstack-meeting13:59
*** annp_ has joined #openstack-meeting13:59
*** jlibosva has joined #openstack-meeting13:59
jlibosva#startmeeting networking14:00
openstackMeeting started Tue Apr 10 14:00:21 2018 UTC and is due to finish in 60 minutes.  The chair is jlibosva. 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
jlibosvaHi everybody14:00
annp_hi jlibosva14:00
*** eharney has joined #openstack-meeting14:00
jlibosva#topic Announcements14:00
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:00
*** awaugama has joined #openstack-meeting14:01
jlibosvaThe Rocky 1 milestone is approaching, should be done in the week of Apr 1614:01
jlibosva#link https://releases.openstack.org/rocky/schedule.html#r-114:01
*** yamamoto has joined #openstack-meeting14:02
jlibosvaand so is Vancouver Summit where will be the usual The Forum, which is still collecting ideas14:02
jlibosva#link http://forumtopics.openstack.org/14:02
jlibosvaThe deadline is the end of this week14:02
*** ianychoi has quit IRC14:02
jlibosvaso if you have a topic you think should be discussed there, feel free to propose it14:02
mlavalleI have a few ideas that I am going to propose14:02
jlibosvaI also see mlavalle started an etherpad to collect topics Neutron rleated14:03
jlibosva#link https://etherpad.openstack.org/p/YVR-neutron-brainstorming14:03
*** ianychoi has joined #openstack-meeting14:03
*** amitry has quit IRC14:03
jlibosvaNext thing I wanted to highlight is this email from openstack-dev ML related to Zuul14:03
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129217.html14:03
*** amitry has joined #openstack-meeting14:04
*** DuncanT has quit IRC14:04
jlibosvaand the last announcement I see on the wikipage is that we're looking for release team liaison14:04
*** DuncanT has joined #openstack-meeting14:04
jlibosvaMore information about the role can be found here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management14:05
mlavalleyeap, armax will be transiotioning out of that role soon14:05
jlibosvathat's all from my side14:05
mlavallehe will provide guidance to the new person during the transition14:05
jlibosvamlavalle: do you have anything else to announce?14:05
amotokiI can volunteer it for the release liaison if nobody is interested in it.14:05
*** yamamoto has quit IRC14:05
mlavalleamotoki: great! Thank you!14:06
jlibosvaanybody else has anything to announce here?14:06
*** chohoor has joined #openstack-meeting14:06
jlibosvaok, let's move on then :)14:06
* mlavalle is happy our releases will be in good hands :-)14:06
jlibosva#topic Blueprints14:06
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:06
*** chohoor has left #openstack-meeting14:06
*** kopecmartin has joined #openstack-meeting14:06
jlibosvacurrent blueprints for this milestones can be found here:14:06
jlibosva#link #link https://launchpad.net/neutron/+milestone/rocky-114:07
jlibosva#link https://launchpad.net/neutron/+milestone/rocky-114:07
jlibosvaway too much #links :)14:07
mlavalleI want to note that last week I added https://blueprints.launchpad.net/neutron/+spec/neutron-lib-decouple-db14:08
pasuderFor last few weeks I did not touch this adoption of existing subnet into a subnetpool.. sorry for that.14:08
mlavalleper boden's request14:08
*** ildikov has quit IRC14:08
mlavallein that blueeprint there is a gerrit topic14:08
mlavalleif you click on it you will see the patches under reviw14:09
mlavalleat the top you will see a couple of specs14:09
*** ildikov has joined #openstack-meeting14:09
mlavalleThat I +2ed last week14:09
mlavalleif you have time, please check them out14:09
*** amodi has joined #openstack-meeting14:09
mlavalleand give your feedback14:09
amotoki.... I forgot to review them after PTG.14:10
*** yamamoto has joined #openstack-meeting14:10
*** bobh has joined #openstack-meeting14:10
bcafarellate o/14:10
jlibosvabcafarel: \o/14:10
mlavalleI also added https://blueprints.launchpad.net/neutron/+spec/extend-logging-to-fwassv2.014:10
mlavallelast week14:10
mlavalleannp_: Is that something you care about ^^^?14:11
*** patrickeast has quit IRC14:11
* mlavalle welcomes bcafarel14:11
jlibosvaI think it's hoangcx who's working on it, no? ^^14:11
*** patrickeast has joined #openstack-meeting14:11
mlavallejlibosva: yesh, I think you are right14:12
mlavalleanyway, it is visible now in our dashboard14:12
jlibosvacool :)14:12
jlibosvaI plan to keep an eye on that one as it's related to logging I reviewed last cycle14:12
mlavallepasuder: thanks for the update. let us know if we can help in any way14:12
*** reedip has joined #openstack-meeting14:12
annp_mlavalle, hoangcx and cuongnv who are main responsible for that14:12
amotokihttps://review.openstack.org/#/q/topic:bug/1720727 looks a better link14:12
toshiithis time it's iptables isn't it. ;)14:13
amotokiwhich includes neutron-fwaas14:13
*** davidlenwell has quit IRC14:13
mlavalleI also want to give a quick update on https://blueprints.launchpad.net/neutron/+spec/live-migration-portbinding14:13
*** davidlenwell has joined #openstack-meeting14:13
*** yamamoto has quit IRC14:13
*** links has quit IRC14:13
mlavalleas of last week, I tested in my dev environent activating bindings and moving the port to the activated host14:14
*** zxiiro has quit IRC14:14
mlavallethis was done from ovs to ovs14:14
*** tomhambleton_ has quit IRC14:14
mlavalleand it works fine with the current version of the code14:14
*** tomhambleton_ has joined #openstack-meeting14:14
*** zxiiro has joined #openstack-meeting14:14
mlavalleYesterday a setup everythin to do the same from OVS to LB and back14:15
mlavalleI will be testing it the rest of this week14:15
*** mnaser has quit IRC14:15
amotokiinteresting, you tested from ovs to LB and back before LB to LB :)14:16
jlibosvamlavalle: just a personal note that OVS + iptables fw driver to OVS + ovs fw driver would be also an interesting use case :)14:16
pasuderI need to leave meeting right now, sorry, bye!14:16
jlibosvapasuder: o/14:16
mlavalleamotoki: I'll still test LB to LB14:16
mlavallejlibosva: good advice, thanks14:16
*** mnaser has joined #openstack-meeting14:17
slaweqmlavalle: what about sr-iov to/from ovs/lb ?14:17
slaweqwill You test it also or it's not the case here?14:17
*** AndyWojo has quit IRC14:17
*** AndyWojo has joined #openstack-meeting14:17
mlavalleslaweq: yeah, that also needs to be tested. taking bay steps for the time being14:17
mlavallemoving from ovs to lb will show we can change backend14:18
*** markvoelker_ has joined #openstack-meeting14:18
mlavallepasuder: np, good night!14:18
amotokibut it sounds challenging to migrate SR-IOV from/to normal virt driver(s) as it requires VM side support14:18
mlavalleyeah, it won't be trivial14:19
*** portdirect has quit IRC14:19
*** gouthamr has joined #openstack-meeting14:19
*** csatari has quit IRC14:19
*** hoangcx has quit IRC14:19
*** portdirect has joined #openstack-meeting14:19
amotokiperhaps we can focus on migrations among virt drivers like ovs-fw, ovs iptables and LB.14:19
*** csatari has joined #openstack-meeting14:19
*** hoangcx has joined #openstack-meeting14:19
*** guyr-infinidat has quit IRC14:19
*** karlamrhein has quit IRC14:20
mlavallethat is an option14:20
*** guyr-infinidat has joined #openstack-meeting14:20
amotoki* as first step14:20
*** karlamrhein has joined #openstack-meeting14:20
*** boden has joined #openstack-meeting14:20
mlavalleof course14:20
* jlibosva nods14:20
slaweqI agree :)14:20
*** jpmaxman has quit IRC14:21
*** markvoelker has quit IRC14:21
*** jpmaxman has joined #openstack-meeting14:21
* mlavalle will stop hogging the blueprints topic now14:21
jlibosvaanything else related to BPs?14:21
*** samueldmq has quit IRC14:21
bodenjlibosva hi14:21
*** diablo_rojo_phon has quit IRC14:21
jlibosvaboden: hi14:21
amotokiannp_: do you want to share your progress/status on https://blueprints.launchpad.net/neutron/+spec/run-in-wsgi-server ?14:21
*** samueldmq has joined #openstack-meeting14:21
*** diablo_rojo_phon has joined #openstack-meeting14:22
bodenjlibosva a friendly reminder that the decouple db plubming patches are out for review (https://review.openstack.org/#/q/topic:bp/neutronlib-decouple-db+(status:open+OR+status:merged))14:22
mlavalleboden: I covered that already14:22
bodenmlavalle: ack sorry I just joined14:22
mlavalleand highlighted the specs14:22
annp_amotoki, actually, I'm still get stuck with neutron-rpc-server14:23
jlibosvarather to have it highlighted twice than zero :)14:23
mlavalleabsolutely +++14:23
bodenmy bad.. this meeting time isn’t easy for me so will be  late14:23
*** mrmartin has quit IRC14:23
*** mrmartin has joined #openstack-meeting14:23
jlibosvaboden: no worries :)14:23
*** pasuder has left #openstack-meeting14:24
annp_today, I have discussed with amotoki about that. I will dig more the amotoki's point. So I think no worth thing to mention here.14:24
jlibosvaannp_: do you need any help with the rpc server?14:24
*** hazmat has quit IRC14:24
annp_This week I will spend more time for this task14:24
*** eharney has quit IRC14:24
jlibosvaok, so seems like amotoki is helping out :) nice14:24
*** beisner has quit IRC14:24
annp_So please go ahead!14:24
jlibosvaok, I think we can move on now14:24
jlibosva#topic Community Goals14:24
*** openstack changes topic to "Community Goals (Meeting topic: networking)"14:24
*** beisner has joined #openstack-meeting14:24
*** donghao has joined #openstack-meeting14:24
*** hazmat has joined #openstack-meeting14:24
jlibosvais there anything related to community goals that anybody wants to inform us about?14:25
mlavallejust highlight the RFE in the wiki14:25
slaweqabout mutable configs I think we are done14:26
*** wiggin15 has quit IRC14:26
*** wiggin15 has joined #openstack-meeting14:26
slaweqpatch is merged to neutron-dynamic-routing and neutron repos14:26
mlavalleslaweq: Nice! Thanks!14:26
*** tommylikehu has quit IRC14:26
*** tommylikehu has joined #openstack-meeting14:26
mlavallethe RFE I want to highlight is:  https://bugs.launchpad.net/neutron/+bug/174519214:26
openstackLaunchpad bug 1745192 in neutron "Can't create a vlan transparent network in mixed driver environment" [Wishlist,Confirmed]14:26
slaweqit wasn't necessary anywhere else, I send patch neutron-lbaas also but I don't know if they will accept it14:26
mlavalleitthat RFE is deemed to be good for beginners14:27
*** wxy has quit IRC14:27
mlavalleand it's up for grabs14:27
*** jayahn has quit IRC14:27
*** sidx64 has quit IRC14:27
mlavallewe have had good success with this section14:27
*** wxy has joined #openstack-meeting14:27
*** jayahn has joined #openstack-meeting14:27
mlavalleall the RFEs that we hav highlighted have been taken14:27
jlibosvamlavalle: so I think you're talking now about the starter RFEs, right? :)14:28
mlavallethe last one was taken by hongbin, thanks!14:28
mlavallejlibosva: duhhh, yeah14:28
mlavallesorry about that14:28
annp_jlibosva, thank you so much. I'll reach out you on neutron channel later. :)14:28
amotokimox removal is good progress. the last one is networking-midonet and we are waiting for the merge.14:28
mlavalleso carry on with community goals14:28
amotokipolicy-in-code is a bit slow-progress due to my busy life...14:29
*** lamt has quit IRC14:29
*** lamt has joined #openstack-meeting14:29
*** kopecmartin has quit IRC14:29
jlibosvaI have no updates on py3 front, I was OOO last week but I plan to dig into it. I saw the oslo.rootwrap issue with eventlet is stall14:29
amotokii will to move this forward next two weeks, but if it fails I will raise it here14:29
*** lamt is now known as Guest2981014:29
amotoki*will try to move*14:29
bodenFYI: I think there’s some related discussion on the plumbing for this on https://review.openstack.org/#/c/539281/14:30
*** knikolla has quit IRC14:30
*** knikolla has joined #openstack-meeting14:30
amotokiboden: yeah, thanks for your comments.14:30
amotokiit seems reasonable to move the policy stuff to me now.14:30
*** sidx64 has joined #openstack-meeting14:31
*** zhangyang has quit IRC14:32
*** zhangyang has joined #openstack-meeting14:32
jlibosvathanks boden for highlighting it here14:32
jlibosvaanybody else has anything related to community goals?14:32
jlibosvaI think we can move on then :)14:33
*** ekcs_ has quit IRC14:33
jlibosva#topic Starter Approved RFEs14:33
*** openstack changes topic to "Starter Approved RFEs (Meeting topic: networking)"14:33
*** wenranxiao has joined #openstack-meeting14:33
*** ekcs_ has joined #openstack-meeting14:33
mlavalleI already jumped the gun with this topic14:33
jlibosva#link https://bugs.launchpad.net/neutron/+bug/174519214:33
openstackLaunchpad bug 1745192 in neutron "Can't create a vlan transparent network in mixed driver environment" [Wishlist,Confirmed]14:33
*** coreycb has quit IRC14:34
jlibosvaI'll just leave the link here for the meeting minutes :)14:34
mlavalleyeap, thanks!14:34
*** coreycb has joined #openstack-meeting14:34
jlibosvais there anything else to be added or shall me move on?14:34
mlavallelet's move on14:34
jlibosva#topic Bugs14:34
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:34
jlibosvalujinluo was bug deputy last week14:35
jlibosvahe sent out a report earlier14:35
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129197.html14:35
*** jamespage has quit IRC14:36
mlavalleshe sent.... ;-)14:36
*** felipemonteiro has joined #openstack-meeting14:36
jlibosvaoh ... my apologies14:36
*** jamespage has joined #openstack-meeting14:36
* jlibosva blushes14:36
*** markvoelker has joined #openstack-meeting14:36
jlibosvaso I think from the report we should prioritize https://bugs.launchpad.net/neutron/+bug/176004714:36
openstackLaunchpad bug 1760047 in neutron "some ports does not become ACTIVE during provisioning" [Undecided,Confirmed]14:36
mlavallewe should take a look at that one14:37
*** lpetrut_ has joined #openstack-meeting14:38
jlibosvait has a good troubleshooting in the comments, I would say this is a high importance?14:38
*** lpetrut_ has quit IRC14:38
*** eharney has joined #openstack-meeting14:38
*** markvoelker_ has quit IRC14:39
jlibosvaok, then we have two bugs that are not triaged: https://bugs.launchpad.net/neutron/+bug/176155514:39
openstackLaunchpad bug 1761555 in neutron "[dvr][fast-exit] router add/remove subnet operations are not idempotent" [Medium,New]14:39
jlibosvaand https://bugs.launchpad.net/neutron/+bug/176159114:39
openstackLaunchpad bug 1761591 in neutron "[dvr] enable_snat attribute is ignored - centralized snat port gets created" [Undecided,New]14:39
jlibosvaSwami is helping there14:39
*** gouthamr has quit IRC14:40
mlavallewe can discuss those two during the L3 meeting on THursday14:40
*** armax has joined #openstack-meeting14:40
mlavallethey will come up there14:40
jlibosvaok, thanks14:40
jlibosvaall other bugs from the report seem to be triaged well14:40
mlavalleand the RFE is actually the result of the Neutron Drivers meeting discussion last Friday14:40
jlibosvathe bug deputy for this week is yamamoto14:41
jlibosvadoes anybody know if he's aware of it? he's not online now14:41
mlavallemhhhh, amotoki and I know he travelling in Barcelona this week14:41
*** lpetrut has quit IRC14:41
mlavalleso, I will assume I will do his duty next week14:41
jlibosvathen maybe he won't have time for triaging?14:41
*** yamamoto has joined #openstack-meeting14:41
mlavalleand he can do mine next week14:41
*** yamamoto has quit IRC14:41
jlibosvamlavalle: sounds great :) thanks14:42
jlibosvaanybody has anything else wrt bugs?14:42
mlavalleyes, mlavalle is bugs deputy this week14:42
amotokior can we expect he can triage bugs during travelling :p14:42
*** markvoelker_ has joined #openstack-meeting14:42
*** Guest29810 is now known as lamt14:42
jlibosvaI'm sure he'll be jetlagged so he could do that instead of sleeping :-p14:42
jlibosvaok, moving on :)14:43
jlibosva#topic Docs14:43
*** openstack changes topic to "Docs (Meeting topic: networking)"14:43
jlibosvaamotoki: boden do you have any updates regarding docs?14:43
amotokinone from me14:43
bodenjlibosva nothing exciting that I’m aware of14:43
jlibosvaok, thanks14:43
jlibosvajumping to the next topic14:43
jlibosva#topic neutron-lib14:43
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:43
*** markvoelker has quit IRC14:44
bodenthat’s me I suppose14:44
jlibosvaboden: how about neutron-lib beside those decouple db patches :)14:44
jlibosvayeah :)14:44
bodenthe only other thing I wanted to mention is that I’d like to rehash the topic of “rehoming neutron.common.rpc” into lib…14:45
bodenI’ve updated https://review.openstack.org/#/c/319328/  with some comments/code…14:45
bodenlooking for some agreement on this before spending mroe time… so if folks get time please add your 2 cents14:45
bodenand that’s if from me on the lib topic14:46
*** markvoelker has joined #openstack-meeting14:46
mlavallethat's an oldie14:46
bodenmlavalle ya, I’m oldschool man14:46
*** dklyle has joined #openstack-meeting14:46
*** yamamoto has joined #openstack-meeting14:47
*** andreas_s has quit IRC14:47
bodenmlavalle: IMO it makes sense to rehome it, but interested in what others think14:47
bodenif you want me to bring it up at drivers meeting I can try to attend when/if needed14:47
mlavallecool, will take a look14:47
*** felipemonteiro_ has joined #openstack-meeting14:47
*** alexchadin has quit IRC14:47
jlibosvathanks boden for updates14:47
*** fnaval has joined #openstack-meeting14:47
*** andreas_s has joined #openstack-meeting14:47
jlibosva#topic CLI/SDK14:47
*** openstack changes topic to "CLI/SDK (Meeting topic: networking)"14:47
jlibosvaamotoki: hi, do you have any updates here?14:48
amotokilet me paste some.14:48
amotokihttps://etherpad.openstack.org/p/neutron-openstacksdk-migration is not necessarily targeted to Rocky. It is a best-effort topic.14:48
amotokiit is a good starter thing. If you are interested in it, feel free to add your name to the etherpad. slaweq and I can help you.14:48
amotokithis is just call for volunteers :)14:48
amotokithat's all.14:48
jlibosvaok, thanks :)14:49
*** markvoelker_ has quit IRC14:49
slaweqjust FYI: trunk support is merged to SDK already14:49
*** markvoelker_ has joined #openstack-meeting14:49
amotokiyeah, thanks slaweq. we need to update the etherpad :)14:49
slaweqyes, I forgot about it, sorry14:50
slaweqwill do it right now14:50
*** markstur has joined #openstack-meeting14:50
jlibosvathanks guys14:51
jlibosvaanything else related to CLI or SDK?14:51
*** felipemonteiro has quit IRC14:51
jlibosvaok, jumping to the open agenda14:52
jlibosva#topic Open discussion14:52
*** openstack changes topic to "Open discussion (Meeting topic: networking)"14:52
annp_Regarding to https://blueprints.launchpad.net/neutron/+spec/extend-logging-to-fwassv2.014:52
jlibosvaI see toshii left a topic about future plans for ryu that has been discussed at the last meeting but I'd like to bring it back again so people that can't attend US meeting are aware of it14:52
annp_I have some update.14:52
annp_Currently, I and FwaaS team are focusing to review spec https://review.openstack.org/#/c/509725/. and the spec is targeted to merge in R-1, I think the spec is quite close. However it should get more comment from you So please take a look at this.14:52
jlibosva#link https://etherpad.openstack.org/p/neutron-ryu-future-plans14:52
toshiiI remind you to think about future of the ryu library if you haven't. ;)14:52
toshiijlibosva, thanks for bringing this up14:53
annp_In addtion,  There are two patch https://review.openstack.org/#/c/534227/ and https://review.openstack.org/#/c/529814/ also need your comments.14:53
jlibosvathat's all :) sorry annp_, go ahead14:53
mlavalletoshii: I will propose this week the topic for the Forum14:53
jlibosvatoshii: ;)14:53
jlibosvathat's a good idea14:53
*** markvoelker has quit IRC14:53
annp_jlibosva, that's all from me.14:53
jlibosvaannp_: I think those rpc patches will need some thought about backward compatibility. I'll comment on it14:54
annp_jlibosva, Just my update for extend firewall logging blueprint.14:54
jlibosvaannp_: thanks for bringing this up14:54
*** artom has joined #openstack-meeting14:55
amotokitoshii: it would be nice if there are inputs on what kind of knowledges or backgrounds are required /expected on ryu maintenance. it might help discussoins.14:55
annp_jlibosva, thanks in advance.14:55
toshiiryu is quite stable these days IMO14:56
toshiii'll add to the etherpad14:56
annp_toshii, +114:56
*** wenranxiao has quit IRC14:56
*** markvoelker has joined #openstack-meeting14:56
amotokitransitions in the maintenance team is not surprising. it is nice this kind of thing is raised in the right timing :)14:56
*** andreas_s has quit IRC14:56
*** Alex_Staf has quit IRC14:57
toshiidealing with brekage due to  dependency library would be the main maintenance work14:57
toshiilike pbr or pip as we saw recently14:57
jlibosvaor adopting new openflow standards? ;)14:57
*** wenranxiao has joined #openstack-meeting14:58
jlibosvaany other topic anybody wants to discuss here? we have 2 minutes left14:58
toshiistandards are not changing. it's just ryu hasn't implemented everything14:58
amotokianother topic: did we discuss http://lists.openstack.org/pipermail/openstack-dev/2018-March/128335.html ?14:58
*** markvoelker_ has quit IRC14:58
jlibosvawe didn't14:58
amotokiit is related to some release model and neutron-lib.14:58
amotokii think sub project developers need extra steps to run tests.14:59
amotokihopefully we can discuss it after rocky-1.14:59
jlibosvaamotoki: we could also put it as the item to open agenda for the next meeting14:59
jlibosvato not forget :)14:59
amotokithis is just a reminder for coming weeks14:59
amotokijlibosva: sure14:59
jlibosvaaaaand we're out of time14:59
jlibosvathanks everyone for showing up :)15:00
*** wxy| has joined #openstack-meeting15:00
*** boden has left #openstack-meeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Tue Apr 10 15:00:18 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-04-10-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-04-10-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-04-10-14.00.log.html15:00
*** donghao has quit IRC15:00
slaweq#startmeeting neutron_qos15:00
openstackMeeting started Tue Apr 10 15:00:46 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. 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
slaweqhi on qos meeting now :)15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
rubasovhello again15:00
*** yamamoto has quit IRC15:01
*** toshii has quit IRC15:01
slaweqmlavalle: are You with us?15:01
*** annp_ has quit IRC15:01
*** anilvenkata has quit IRC15:01
slaweqok, so let's start15:01
slaweq#topic RFEs15:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
*** yamamoto has joined #openstack-meeting15:01
slaweqthere wasn't any new RFE reported recently so I will go through old one15:02
slaweq#link https://bugs.launchpad.net/neutron/+bug/172757815:02
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:02
slaweqzhaobo6 pushed new PS to his specs https://review.openstack.org/#/c/531074/15:02
*** lajoskatona_ has quit IRC15:02
*** ad_ri3n_ has quit IRC15:02
slaweqIIRC it was almost fine for me (except some nits) but it will need some "vpn expert" to take a look at it also :)15:03
slaweqI will read it once again this week15:03
slaweqreedip: hi15:03
*** chenyb4 has quit IRC15:03
slaweqnext one is #link https://bugs.launchpad.net/neutron/+bug/150562715:04
openstackLaunchpad bug 1505627 in neutron "[RFE] QoS Explicit Congestion Notification (ECN) Support" [Wishlist,Triaged] - Assigned to Reedip (reedip-banerjee)15:04
reedipI asked mlavalle to assist in its review just today15:04
slaweqyes, I saw You pushed new PS to specs15:05
reedipfew things need to be sorted out ,and then it should be ready, I would however request all others to review it15:05
slaweqI will also try to review it ASAP15:05
reedipIts a long time pending , lets get it over with :)15:05
slaweqagree :)15:05
*** markvoelker_ has joined #openstack-meeting15:05
mlavallereedip: will you implement it?15:05
*** ad_ri3n_ has joined #openstack-meeting15:06
reedipmlavalle : I hope so, but would need assistance to be honest15:06
slaweqreedip: I hope I will be able to help on that one15:06
slaweqbut I don't know exactly what will be my priorities in next months so I don't say that I will help for sure15:07
reedipslaweq : exactly , same with me for some time15:07
*** markvoelker_ has quit IRC15:08
slaweqok, moving on to the next one15:08
slaweq#link https://bugs.launchpad.net/neutron/+bug/156096315:08
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress]15:08
*** aagate has joined #openstack-meeting15:08
slaweqI didn't work on it yet15:08
slaweqI was talking with Rodolfo about how he wanted to do it some time ago. Basically it looks to be very tricky/hard to implement on backend side for both LB and OVS.15:09
*** markvoelker has quit IRC15:09
*** markvoelker has joined #openstack-meeting15:10
*** markvoelker_ has joined #openstack-meeting15:10
*** longkb has quit IRC15:11
slaweqTo be honest I'm not sure15:11
mlavallehas anybody done this kind of QoS in OVS at all?15:11
slaweqmaybe with some workarounds or limitations15:11
mlavalleI might be worth asking in the OVS community15:12
*** jlibosva has left #openstack-meeting15:12
slaweqI didn't found anything like that anywhere15:12
slaweqyes, I will try to ask about that in ovs ML this week15:12
slaweqgood idea15:12
mlavallemaybe also in the LB community15:13
mlavalleif there is such a thing15:13
slaweqmaybe some Linux communities15:13
mlavallein the case of LB, we would use TC, right?15:13
slaweqthere are possibilities to do it with IFB devices but as Rodolfo told me that will have some limitations - I don't know exactly what will it be15:14
slaweqyes, it has to use TC15:14
slaweqin fact in OVS probably also TC would be used underneath15:14
mlavallethere must be a group maintaining / developing it15:14
*** julim has quit IRC15:15
mlavalleI mean TC15:15
*** markvoelker has quit IRC15:15
slaweqI will try to search and ask somewhere :)15:15
mlavallemaybe we should ask them for ideas15:15
rubasovmaybe this mailing list is alive (I never subscribed to it, not sure): https://www.spinics.net/lists/lartc/15:16
slaweqrubasov: thx, it looks that there are quite fresh mails there15:16
slaweqI will ask there also15:16
slaweqthank You15:17
rubasovhope it helps15:17
*** belmoreira has quit IRC15:17
slaweqok, moving on15:18
slaweqnext one is #link https://bugs.launchpad.net/neutron/+bug/157898915:18
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)15:18
slaweqstill two small patches related to it, done by lajoskatona in review:15:18
*** VW_ has joined #openstack-meeting15:18
slaweq#link https://review.openstack.org/#/c/554532/15:18
slaweq#link https://review.openstack.org/#/c/552938/15:18
slaweqso please review it if You will have some time15:19
slaweqrubasov, mlavalle, how specs is going for this one?15:19
*** yamamoto has quit IRC15:19
slaweqany updates?15:19
reedipyep, will review15:19
slaweqthx reedip15:19
*** yamamoto has joined #openstack-meeting15:19
mlavallerubasov and I had a lively discussion exactky a week ago15:19
mlavallethe rest of last week I got distracted with multiple port binding15:20
*** VW has quit IRC15:20
rubasovI think we were on the same page at that discussion15:20
mlavallerubasov: yes we were15:20
mlavalleI think we are getting closer to a solution15:20
rubasovbut I'm not sure if we have an overall consensus with all the reviewers of the spec15:21
mlavallejaypipes and seankmooney commented on the nova spec15:21
mlavalleI have to go back to their comments15:21
mlavalleI will do it today or tomorrow15:21
slaweqI will try to read it also once again15:21
*** salv-orl_ has quit IRC15:22
rubasovIMO the contentious point is: how the RP-tree should look like15:22
*** salv-orlando has joined #openstack-meeting15:23
mlavallerubasov: yes15:23
mlavalleI will try to address that in my next comments15:23
rubasovthere's a bit of progress in the neutron spec too15:24
mlavalleI saw that. Thanks!15:24
mlavalleI will take a look soon15:24
rubasovjust uploaded a new patch set yesterday15:24
*** hoangcx_ has joined #openstack-meeting15:24
rubasovmlavalle: thank you15:24
mlavallerubasov: I needed to make progress on multiple port binding last week15:25
*** hoangcx__ has joined #openstack-meeting15:25
mlavallethat is why I didn't go back to this spec over the past few days15:25
rubasovmlavalle: no problem15:25
mlavallebut I will go back this week15:25
*** hoangcx_ has quit IRC15:25
rubasovmlavalle: looking forward to your comments15:26
mlavalleI think that's all as far as progres report on this topic15:26
mlavallein this meeting ;-)15:26
*** yamamoto has quit IRC15:26
slaweqok, thx for updates :)15:26
*** rwsu has quit IRC15:26
slaweqso I think we can go to next topic then15:26
slaweq#topic Bugs15:26
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:27
slaweqthere was no any new bug reported for QoS since last meeting15:27
slaweqwhich is good IMO :)15:27
mlavalleindeed :-)15:27
slaweqwe have only on in progress now:15:27
*** salv-orlando has quit IRC15:27
slaweq#link https://bugs.launchpad.net/neutron/+bug/175831615:27
openstackLaunchpad bug 1758316 in neutron "Floating IP QoS don't work in DVR router" [High,In progress] - Assigned to LIU Yulong (dragon889)15:27
slaweqI know that LIU Yulong is working on it still, there is WIP patch pushed: https://review.openstack.org/#/c/558724/15:27
*** hoangcx has quit IRC15:27
slaweqand I think that it's more for some DVR expert to check rather than for QoS side15:28
*** salv-orlando has joined #openstack-meeting15:28
mlavalleseems to be about ready to review15:29
slaweqthere is WIP in title15:29
slaweqthat's why I assumed it's still in progress15:29
mlavalleI'll ask him?15:29
slaweqYou are asking if You will ask him?15:30
slaweqwho except You can know that :D15:30
*** wenranxiao has quit IRC15:30
mlavalleslaweq: I asked him15:30
slaweqok :)15:30
*** yamamoto has joined #openstack-meeting15:31
slaweqYou asked or You will ask?15:31
*** gyee has joined #openstack-meeting15:31
mlavalleI did15:31
slaweqah, so it's ready to review then15:31
mlavalleI asked in the patch15:32
mlavallejust left a comment asking15:32
slaweqahh, ok, sorry15:32
* slaweq needs another coffee15:32
mlavallewell, maybe you are still very young and can have coffee in the evening. Ican't do that anymore15:33
reedipyou are not old mlavalle :)15:33
slaweqI can drink coffee always :) It's not a problem for me :)15:33
*** hoangcx has joined #openstack-meeting15:33
*** jchhatbar has quit IRC15:33
slaweqabout this patch, I will also do patch to neutron-tempest-plugin which will depend on this one to remove skip of FIP qos test and check if it's working now15:34
*** hoangcx__ has quit IRC15:34
slaweqI think we can move on15:35
slaweq#topic Open Discussion15:35
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:35
slaweqanyone wants to talk about something else maybe?15:35
reedipnm ...15:36
mlavalleI'm good for now15:36
rubasovme too15:36
*** beekhof has quit IRC15:36
mlavallerubasov: when does gibi_awa1 come back?15:36
rubasovhe'll be back next week15:36
*** e0ne has quit IRC15:37
*** hoangcx_ has joined #openstack-meeting15:37
slaweqok, so I think we are done for today15:37
*** wenranxiao has joined #openstack-meeting15:37
slaweqwe have 20 minutes free now15:37
slaweqmlavalle: You can do some review in Your free time now :P15:37
mlavalleslaweq: good point :-)15:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:38
openstackMeeting ended Tue Apr 10 15:38:01 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-04-10-15.00.html15:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-04-10-15.00.txt15:38
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-04-10-15.00.log.html15:38
slaweqthx for attending15:38
rubasovthank you guys15:38
*** psachin has joined #openstack-meeting15:38
*** reedip has quit IRC15:38
*** rwsu has joined #openstack-meeting15:39
*** hoangcx has quit IRC15:40
*** tssurya has quit IRC15:41
*** annabelleB has quit IRC15:42
*** yamamoto has quit IRC15:43
*** yamamoto has joined #openstack-meeting15:44
*** annabelleB has joined #openstack-meeting15:54
*** wenranxiao has quit IRC15:54
*** lhx_ has quit IRC15:58
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Apr 10 16:00:43 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
*** edmondsw has quit IRC16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
*** ihrachys has joined #openstack-meeting16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
slaweq#topic Actions from previous meetings16:01
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:01
*** edmondsw has joined #openstack-meeting16:01
slaweqjlibosva, haleyb: are You around?16:01
*** jlibosva has joined #openstack-meeting16:02
slaweqok, so I think we can start now16:02
slaweqfirst action from previous week:16:02
slaweqhaleyb to check router migrations issue16:02
haleybi haven't reproduced the issue yet, seemed to work fine manually, so $more_testing=116:03
slaweq#action haleyb to continue testing why router migrations tests fails16:04
slaweqnext one was16:05
slaweqslaweq will check difference between neutron-tempest-multinode-full and neutron-tempest-dvr-ha-multinode-full16:05
slaweqso I compared those jobs definitions: https://pastebin.com/zQTHJ1Rg16:05
*** ad_ri3n_ has quit IRC16:05
slaweqBasically difference is that on neutron-tempest-multinode-full L3 agent is only on main node (subnode is only for compute), in neutron-tempest-dvr-ha-multinode-full L3 agent on subnodes is in dvr_snat mode16:05
slaweqAFAIR ihrachys wants to check if we needs both those jobs - IMO we should have both of them16:06
*** e0ne has joined #openstack-meeting16:06
slaweqah, one more thing - there is also flag DEVSTACK_GATE_TLSPROXY  set in one of those jobs but I have no idea what is it for :)16:07
ihrachysI think tlsproxy is on by default. afair it's some nova thing.16:08
ihrachyscan't even find it mentioned in latest devstack-gate so maybe completely irrelevant16:09
ihrachysslaweq, as for the dvr vs. legacy, for what I understand, we have tempest-full job for legacy too. do we need that one then?16:09
*** yamamoto has quit IRC16:10
slaweqtempest-full is singlenode16:10
slaweqthis one is multinode16:10
*** yamamoto has joined #openstack-meeting16:10
slaweqbut maybe we don't need singlenode job then as multinode should covers it as well16:11
slaweqwhat do You think?16:11
*** rbartal has quit IRC16:11
ihrachysyeah that's what I was alluding to.16:12
ihrachystempest-full may come from tempest repo though. we also have full-py3 from the same source16:12
ihrachysbut I guess I don't feel strongly about it anymore since there are legit differences we may want to keep between jobs we maintain.16:13
ihrachysthanks for checking slaweq16:13
slaweqYour welcome ihrachys16:13
slaweqso we will left it as it is for now, right?16:13
mlavalleI think so, slaweq16:15
slaweqok, fine16:15
slaweqnext action then16:15
slaweqmlavalle to take a look why rally jobs are taking so long time16:15
mlavalleI didn't have time last week16:15
slaweqok, but I'm not sure if there is something really wrong with it now - let's talk about it later :)16:16
slaweqmoving on16:16
slaweqslaweq will add openstack-tox-lower-constraints to grafana dashboard16:16
slaweqpatch merged today https://review.openstack.org/#/c/559162/16:16
slaweqand the last one from last week:16:17
slaweqslaweq will check old gate-failure bugs16:17
slaweqI didn't have time to check them during last week - sorry16:17
slaweq#action slaweq will check old gate-failure bugs16:17
ihrachysdo we have a document capturing rationale for the low-constraints job?16:17
slaweqihrachys: are You asking about job?16:18
ihrachysit's just first time I hear about it. I was not very involved lately.16:18
ihrachyswanted to understand what the job is for. but maybe I can google myself.16:19
slaweqI think there was some email about it few weeks ago16:19
*** sridharg has quit IRC16:19
ihrachysok I will take a look, nevermine16:19
mlavalleyes, there is a message in the ML explaining the rationale16:19
slaweqthx, I can't find it now16:20
slaweqbut I think it was given in commit message in patch which added it to neutron repo16:20
slaweqso You will find it easily there16:21
ihrachysok ok, sorry, I shouldn't have asked dumb questions16:21
slaweqihrachys: it wasn't dumb question for sure :)16:21
slaweqok, moving on to next topic16:21
slaweq#topic Grafana16:21
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:21
slaweqI was checking today last few days there16:22
slaweqthere was some spike yesterday but it was on all jobs similar IMO16:23
slaweqthere are still same jobs on quite high failure rate but I think there is nothing "new" what would require special attention16:25
slaweqany thoughts?16:25
ihrachysthere is periodic failure it seems16:25
ihrachyswith neutron-lib-master16:25
*** hemna_ has joined #openstack-meeting16:25
ihrachysand looks like for py35 only16:25
slaweqyes, I forgot about that one now16:26
slaweqbut I have it for later discussion prepared :)16:26
ihrachysok nevermind then16:26
slaweqso IMHO it is due to patch https://review.openstack.org/#/c/541766/16:26
slaweqihrachys: we can talk about it now16:26
*** felipemonteiro_ has quit IRC16:27
slaweqI checked failures since 6.04 for this job and there are exactly same errors there each time16:27
*** felipemonteiro_ has joined #openstack-meeting16:27
ihrachysyeah looks like related16:27
slaweqit looks for me that it's because of this patch: https://review.openstack.org/#/c/541766/ - maybe there is something missing in neutron now16:28
slaweqI can try to check it or at least I will report a bug for that16:28
*** cloudran_ has joined #openstack-meeting16:28
slaweqor maybe someone else wants to fix it? :)16:28
*** cloudrancher has quit IRC16:29
slaweqI can assign action to someone from You. Any volunteers? :)16:29
jlibosvaif everybody is busy, I can have a look16:29
haleybor maybe ping yamahata ?16:29
slaweqI think yamahata is not available now16:30
slaweqso jlibosva can You at least report a bug and ask yamahata to check it?16:30
*** julim has joined #openstack-meeting16:30
yamahatayamahata: I'm here. what's the issue?16:30
mlavalleyamahata is based out of California16:31
slaweqhi yamahata :)16:31
slaweqmlavalle: I didn't know that16:31
*** jessegler has joined #openstack-meeting16:31
jlibosvame neither :)16:31
slaweqyamahata: since few days we have failure in periodic job: http://logs.openstack.org/periodic/git.openstack.org/openstack/neutron/master/openstack-tox-py35-with-neutron-lib-master/66d328a/testr_results.html.gz16:31
slaweqit looks like related to patch https://review.openstack.org/#/c/541766/16:31
slaweqdo You have any idea why it's failing?16:32
*** cloudrancher has joined #openstack-meeting16:32
ihrachysfor what I understand, a fix would be test only, and it would just capture any new arguments and ignore them when matching mock call args16:32
* yamahata opening links16:32
*** cloudran_ has quit IRC16:32
*** VW_ has quit IRC16:32
yamahatalet me check it.16:33
*** yamamoto has quit IRC16:33
*** VW has joined #openstack-meeting16:33
yamahatanow callback registration accepts priority priority_group.DEFAULT_PRIORITY=55500016:34
*** yamamoto has joined #openstack-meeting16:34
yamahataso function call check needs to be updated to include priority.16:34
*** e0ne has quit IRC16:35
ihrachysyamahata, no. if we do that, unit tests will fail with old neutron-lib16:35
yamahataOh, right.16:35
ihrachysinstead of explicitly matching, we should ignore the argument value (if it's present)16:35
slaweqor we should release new neutron-lib version and update test as yamahata propose :)16:36
*** e0ne has joined #openstack-meeting16:36
ihrachysthe test goal is to validate that subscription happened for the right callback / event. it has nothing to do with priorities, so we should ignore it.16:36
slaweqihrachys: right16:36
ihrachysslaweq, meaning, old queens neutron gate will be incompatible with newer neutron-lib? not ideal.16:37
slaweqbut old queens neutron gate uses newest neutron-lib also?16:37
ihrachysI prefer the test is liberal / compatible with different versions. we CAN then release / bump requirements / force checking priority, but what's the point16:37
slaweqI agree with You16:38
ihrachysslaweq, it doesn't; but we don't block anyone from updating neutron-lib16:38
slaweqI was just curious :) thx16:38
ihrachysit's not like we have <=XXX in requirements16:38
ihrachysso anything fresh is fair game16:38
slaweqso do we have any volunteer who will fix this test?16:39
mlavalleI thought yamahata will fix it16:39
yamahatalet me cook first patch to address test_register16:39
yamahatatest__init__ failure looks different issue16:39
slaweqok, thx yamahata16:39
yamahataanyway I'll look into test__init__ too.16:40
slaweq#action yamahata to fix issues with openstack-tox-py35-with-neutron-lib-master periodic job16:40
mlavallethanks yamahata!16:40
slaweqso I think that periodic jobs are fine and we can go to next topic16:41
*** marios has quit IRC16:41
*** SumitNaiksatam has quit IRC16:41
slaweq#topic Fullstack16:41
*** openstack changes topic to "Fullstack (Meeting topic: neutron_ci)"16:41
*** SumitNaiksatam has joined #openstack-meeting16:41
slaweqI was today looking for fullstack issues in last 2 days16:41
slaweqI found one POST_FAILURE: http://logs.openstack.org/14/559414/2/check/neutron-fullstack/1cbd1b0/job-output.txt.gz#_2018-04-09_21_06_31_611265 which looks like some issue with infra16:42
slaweqand at least twice failed fullstack tests for patch https://review.openstack.org/#/c/499908/ which looks for me that is related to patch it self16:42
slaweqdo You found any other fullstack failures in last days?16:43
*** SumitNaiksatam has quit IRC16:44
ihrachysI wasn't paying attention so no16:44
mlavalleI didn't see any16:44
jlibosvame neither16:45
slaweqok, so I will try to keep an eye on it and check when something new will happen :)16:45
slaweqnext topic then16:45
slaweq#topic Scenarios16:45
*** openstack changes topic to "Scenarios (Meeting topic: neutron_ci)"16:45
slaweqhere we still have same "big players" :)16:45
slaweqneutron-tempest-plugin-dvr-multinode-scenario failing on 100% still16:45
slaweqbut what is interesting there was moment that it was little below 100% at 6.04 and then get back to 100%16:46
jlibosvaare those just the migration tests?16:46
*** psachin has quit IRC16:46
jlibosvaperhaps we should mark them with our favorite unstable_test decorator16:46
slaweqin most cases failed tests are those with migration16:46
*** aagate has quit IRC16:47
slaweqsometimes there is also test_trunk_subport_lifecycle which fails16:47
jlibosvaright, I still have that on my plate16:47
slaweqI was checking few jobs and didn't found other issues16:47
*** hoangcx_ is now known as hoangcx16:48
slaweqhaleyb: as You are checking those failures with migration, do You think it is worth to mark them as unstable for now?16:49
haleybslaweq: yes, i suppose we could16:49
slaweqok, will You do it then?16:49
*** sambetts is now known as sambetts|afk16:50
slaweq#action haleyb will mark router migration tests are unstable16:50
slaweqthx jlibosva, good idea :)16:51
ihrachysdo we do same with trunk then or it's a different beast?16:51
slaweqI think we can do the same with it for now16:51
slaweqjlibosva: do You agree?16:51
jlibosvaI'd suggest to do one by one16:51
jlibosvalet's see how the failure rate goes without considering router migration16:52
jlibosvaif it's still high, let's cross trunk out too16:52
slaweqok, so moving on16:52
slaweq#topic Rally16:52
*** openstack changes topic to "Rally (Meeting topic: neutron_ci)"16:52
jlibosvaeh, I had one item I wanted to bring re scenarios16:53
slaweqsorry jlibosva16:53
slaweq#topic scenarios16:53
*** openstack changes topic to "scenarios (Meeting topic: neutron_ci)"16:53
slaweqgo on then :)16:53
*** felipemonteiro__ has joined #openstack-meeting16:53
jlibosvaso I've been watching the ovsfw tempest job and it seems to me that it copies other tempest failures16:53
jlibosvathat said, I think the failures are not related to the fact it uses ovsfw driver. I wanted to know opinions about making it voting in the check Q16:54
slaweqI agree, it is quite stable since few weeks16:55
ihrachyswould it make sense, long term, to have ovsfw for multinode dvr-ha job?16:55
ihrachysand then have just one16:55
jlibosvaI think long term it would make sense to make ovsfw the default16:55
ihrachysI understand that ovsfw is stable already so we can have it enabled and plan for ovsfw for dvr-ha16:55
ihrachysjlibosva, for all jobs?16:56
jlibosvawhich will lead to have ovsfw in all current tempest tests16:56
jlibosvafor devstack, yes, for all jobs16:56
jlibosvaI think that should be the goal, then we can deprecate iptables hybrid driver. I don't think it makes sense to maintain both16:56
jlibosvaiptables driver will stay for LB of course16:57
jlibosvabut that's a long term :)16:57
*** felipemonteiro_ has quit IRC16:57
jlibosvaso for now, we can make the ovsfw voting16:57
mlavalleis it failing around ~15%?16:57
ihrachysbut there's no migration path from hybrid so how can you deprecate16:57
ihrachysagreed to make it voting and deal with wider plans separately16:58
jlibosvathere is since Pike16:58
jlibosvathat leaves hybrid plugging behind16:58
slaweqmlavalle: it is usually around 10-15%16:58
jlibosvaand with multiple port bindings being planned for rocky, we'll have a way to deal with it too16:59
slaweqok, maybe up to 25% sometimes but it follows other jobs also16:59
slaweqI think we are out of time now16:59
ihrachysjlibosva, ok looks like I was cryo-frozen for a while lol16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:00
openstackMeeting ended Tue Apr 10 17:00:06 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-04-10-16.00.html17:00
jlibosvaor maybe I just didn't document it properly :)17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-04-10-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-04-10-16.00.log.html17:00
slaweqthanks for attending17:00
*** yamamoto has quit IRC17:00
*** andreas_s has joined #openstack-meeting17:03
*** mlavalle has left #openstack-meeting17:03
*** arxcruz|ruck is now known as arxcruz|off17:03
*** julim has quit IRC17:03
*** julim has joined #openstack-meeting17:04
*** wxy| has quit IRC17:05
*** ad_ri3n_ has joined #openstack-meeting17:06
*** erlon has joined #openstack-meeting17:08
*** yamamoto has joined #openstack-meeting17:08
*** david-lyle has joined #openstack-meeting17:10
*** sgrasley1 has quit IRC17:12
*** sgrasley1 has joined #openstack-meeting17:12
*** dklyle has quit IRC17:14
*** yamamoto has quit IRC17:15
*** yamamoto has joined #openstack-meeting17:15
*** spilla has joined #openstack-meeting17:16
*** spilla has left #openstack-meeting17:16
*** tesseract has quit IRC17:16
*** andreas_s has quit IRC17:16
*** artom_ has joined #openstack-meeting17:19
*** artom has quit IRC17:21
*** andreas_s has joined #openstack-meeting17:21
*** artom__ has joined #openstack-meeting17:22
*** sidx64 has quit IRC17:23
*** SumitNaiksatam has joined #openstack-meeting17:23
*** artom_ has quit IRC17:24
*** awaugama has quit IRC17:27
*** awaugama has joined #openstack-meeting17:28
*** artom__ is now known as artom17:32
*** dustins has quit IRC17:32
*** andreas_s has quit IRC17:36
*** jlibosva has quit IRC17:39
*** ekcs has joined #openstack-meeting17:42
*** cloudrancher has quit IRC17:45
*** cloudrancher has joined #openstack-meeting17:47
*** ad_ri3n_1 has joined #openstack-meeting17:48
*** ad_ri3n_ has quit IRC17:48
*** david-lyle has quit IRC17:53
*** SumitNaiksatam has quit IRC17:53
*** dklyle has joined #openstack-meeting17:54
*** cloudrancher has quit IRC17:54
*** tobiash has joined #openstack-meeting17:54
*** e0ne has quit IRC17:54
*** cloudrancher has joined #openstack-meeting17:55
*** mmethot has quit IRC17:59
*** anteaya has joined #openstack-meeting18:01
*** Shrews has joined #openstack-meeting18:02
*** dmacpher_ has joined #openstack-meeting18:07
*** electrofelix has quit IRC18:09
*** dmacpher has quit IRC18:10
*** gouthamr has joined #openstack-meeting18:13
*** gouthamr has quit IRC18:19
*** ianychoi has quit IRC18:22
*** ianychoi has joined #openstack-meeting18:23
*** harlowja has joined #openstack-meeting18:25
*** jamesmcarthur has quit IRC18:26
*** jamesmcarthur has joined #openstack-meeting18:27
*** gman-tx has quit IRC18:27
*** gman-tx has joined #openstack-meeting18:27
*** mjturek has quit IRC18:30
*** jamesmcarthur has quit IRC18:34
*** jamesmcarthur has joined #openstack-meeting18:36
*** gouthamr has joined #openstack-meeting18:38
*** ianychoi has quit IRC18:41
*** ianychoi has joined #openstack-meeting18:42
*** gouthamr has quit IRC18:43
*** ad_ri3n_1 has quit IRC18:45
*** amodi has quit IRC18:48
*** salv-orlando has quit IRC18:57
*** salv-orlando has joined #openstack-meeting18:58
*** e0ne has joined #openstack-meeting18:59
clarkbanyone here for the infra meeting?19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Apr 10 19:01:25 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
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
anteayaclarkb, I just added an item under open discussion19:02
clarkbI don't have any announcements. Anything we want to announce?19:02
clarkbanteaya: ok19:02
clarkbI guess a reminder that may 3, 2018 is gerrit upgrade day19:02
*** salv-orlando has quit IRC19:02
clarkb*gerrit server upgrade, not gerrit service upgrade19:03
fungithere'll probably be a social media push for the ci/cd opendev later today if people want to help promote it19:03
fungias not a social media person myself, i won't be doing that, but i figure some people do that sort of thing ;)19:04
clarkb#info Gerrit server upgrade to Xenial on May 3, 201819:04
anteayafacebook is looking fragile today19:04
clarkb#info OpenDev social media push if you want to help promote it19:04
fungitwitter is apparently the new facebook, or something like that19:05
clarkb#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-04-03-19.01.txt minutes from last meeting19:05
clarkbWe didn't have any formally noted #actions but we did have a bunch of stuff come out of last weeks meeting and I think many of those happened19:06
clarkbthe gerrit upgrade was announced to the dev list, we sent a mini irc abuse faq email to the dev list, discussion on new priority efforts was started and so on19:06
clarkbthank you everyone that helped get all that done19:06
clarkb#topic Specs Approval19:07
*** openstack changes topic to "Specs Approval (Meeting topic: infra)"19:07
clarkbI don't think there are any new specs up for approval. But I did merge a the specs that I said I would get merged last week19:07
clarkbalso if you ahve a moment dmsimard's eavesdrop updates spec and anteaya/pleia2's survey spec could use reviews19:08
clarkb#link https://review.openstack.org/349831 Survery service spec19:08
clarkb#link https://review.openstack.org/550550 IRC discoverability spec19:08
clarkb#topic Priority Efforts19:09
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:09
clarkb#topic Storyboard19:09
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:09
clarkbfungi: sounds like the migration process continues? any luck sorting out bug updates from gerrit events?19:09
fungiaside from importing cyborg i haven't done much since the last meeting, no19:09
fungiit's on my list for the next day or so to start playing with story commenting from review-dev to storyboard-dev19:10
clarkbcool, offer still stands to help there should that be useful since I did the gerrit 2.13 upgrade and missed this (I feel abd :P )19:10
fungii'll definitely loop you in with what i find, at least19:11
clarkb#topic New Priority Efforts19:11
*** openstack changes topic to "New Priority Efforts (Meeting topic: infra)"19:11
mordredfungi: I think19:11
* mordred doesn't computer well19:11
clarkbmordred: should I undo if there is more storyboarding to talk about?19:11
clarkbI guess not? /me continues with new priority effort discussion19:12
fungiwe can catch up in open discussion if need be19:13
clarkbthe mailing list thead on this has pointed out an important topic which is modernizing our control plane deployment tooling. Options that have come up are supporting puppet 4 or 5, and ansibilifying our control plane19:13
clarkbthese were not on my original list but thinking about it more this is likely our biggest current pressing issue19:13
pabelangerI haven't had a chance to comment myself, but lively discussion19:14
clarkbBoth of the specs related to this have gone a bit stale I think. Merge conflicts if nothing else. A good next step may be to update both specs so that we can consider our options with up to date information19:14
fungii wonder whether dropping the central puppetmaster and removing puppet from our test node images means that we're now only testing everything across a common puppet version because we try to install it all on one test node19:14
clarkbfungi: we run the apply tests on a variety of distros19:15
fungiand whether we could incrementally move systems to newer puppet if we stopped assuming we use a common puppet version everywhere. no need for a big bang upgrade19:15
clarkbfungi: which should use the puppet for that $distro19:15
clarkbfungi: thats a good point, and I think that would be doable19:16
fungii suppose system-config is a bit of a linchpin where we'd need backward-compatibility19:16
pabelangerI thought distro puppet was still lagging on the version they use19:16
ianwfungi: as in, making install_modules.sh not the canonical source of puppet modules?19:16
clarkbpabelanger: it is and its largely why we've been fine on puppet319:16
clarkbpabelanger: but we don't have to use distro puppet (and haven't in the past)19:17
pabelangeryah, bionic jumps up to 4.1019:17
fungiianw: maybe more than one module list, or dropping the central module list, yeah19:17
pabelangerI do like the idea of a central puppet list, if only to keep things in sync across hosts. But do agree, it is a little harder to deal with upgrading19:18
fungiusing the limesurvey module we were trying to use as a recent example, it's over a year old and claims to need puppet 4.5 or newer since it was initially created, so even bionic's system puppet would be too old19:18
mordredclarkb: I think we should take a step back and think holistically about how we manage things. as it stands now I'd be more in favor of work to shift to ansible than work to rewrite puppet to support a new puppet ...19:19
clarkbmordred: yes I'm suggesting we update both specs19:19
clarkband evaluate them together19:19
clarkbboth specs are out of date and if we were to implement them would need updates I think19:19
clarkbbut then we can consider them both and decide which is worth the effort19:19
mordredclarkb: but I can also make arguments that it's time to consider if/how containers fit in to what we're doing and whether adopting their use in places would make our lives better19:20
fungiwell, updating existing puppet modules would still presumably be way less effort than rewriting them all in ansible (i strongly doubt most of the service we rely on have equivalent ansible modules already)19:20
mordredclarkb: so maybe for completeness I should write a straw-man spec for that too (even if the answer winds up being nope)19:20
clarkbmordred: ya that could be useful as well19:20
pabelangerI'll rebase the ansibilfy spec later today19:20
clarkband then there is another meta idea where we take fungi's puppet idea and could expand that to be service specific deployment tooling (I don't think we really want to do that at least not long term but may make sense for incremental deployment to get to some future state)19:21
*** annabelleB has quit IRC19:21
fungii'd be curious to read the containers spec, because so far i can't even begin to imagine how they make production deployment any simpler for us19:21
mordredfungi: agree - however, it could be the case that we could simplify what we're asking of the puppet modules currently (the game where people's apps are better after they migrate from one tech to the other - not bcause the new tech is better, but because they refactor the app armed with more knowledge than when the app was written the first time)19:21
clarkbbut I think one of the struggles with this topic has been its a difficult one in general and we haven't actually written down proper start to finish specs that we can read side by side19:21
mordredclarkb: ++19:22
clarkbwhich I think will help everyone understand the needs and what is involved and allow us to make a better decision (if a bit more upfront work)19:22
corvusfungi: broadly speaking i think containers could make things easier by completely decoupling apps from system.  our biggest problems seem to be that we keep running into os-upgrades interfering with app upgrades.19:22
fungiclarkb: yeah, i wouldn't expect us to try to run multiple puppet versions forever, just suggesting that finding an incremental upgrade solution might be easier than an all-at-once19:22
corvusthey are not the only solution to that, but they are one.  :)19:22
clarkbfungi: ya19:22
clarkbsounds like we have a volunteer for ansible and a volunteer for container spec19:22
mordredcorvus, fungi: yah - and also the coupling of installing softare and configuring software in our puppet modules19:23
clarkbanyone willing to go back over our puppte spec and consider fungi's idea there as well as puppet 5?19:23
*** dbecker has quit IRC19:23
corvusi also think this touches on the openstackci question19:23
clarkb(I'm guessing that one might fall on me by default if no one else wants it)19:23
clarkbcorvus: ya I think so too19:23
pabelangerThe bonus with ansible, is there are container connection plugins, if users choose to use them. Or how OSA does lxc things on the remove node19:23
corvusianw brought this up in zuul meeting yesterday, and it'd be nice for us to discuss it more on its own.  but regardless, we need to decide what we want the future of that to be19:24
*** dbecker has joined #openstack-meeting19:24
clarkbpabelanger: I think I'd like to avoid using less common container tooling fwiw19:24
mordredclarkb: it's also possible if nobody steps up to write the puppet spec that we've learned that nobody really wants to champion it as whatwe use moving forward19:24
ianwcorvus: it's on the agenda :)19:24
clarkbpabelanger: one of the benefits of using conatiners would be others know how to work with them and we lose a lot of that if using special magic for containers19:24
clarkbmordred: indeed :)19:24
mordredclarkb: basically saying that I don't think you should write the puppet5 spec by default (although you certainly _can_)19:24
pabelangerclarkb: understood, but is an option you'd toggle based on inventory variables19:25
clarkbok I'll respond to the list with these thoughts (basically elts update the specs so we can consider them directly against each other and then make a decision)19:25
*** krenczew1 has joined #openstack-meeting19:25
mordredcool. and yay. somehow now I'm on the hook for writing a spec19:25
clarkbthis sort of assumes we want to make this the priority spec going forward but honestly I think not making it the priority effort would be a mistake19:25
mordredwhat's wrong with me?19:25
fungimy biggest fear there is that we end up blocking fixing bugs in services by forcing fixes to come with a complete rewrite of deployment/configuration management tooling19:25
mordredclarkb: +10019:25
mordredfungi: I agree with that - and I think any plan we adopt should not have that quality19:26
clarkbfungi: ya I think we need to make it incremental19:26
clarkbso that we don't put a force lock on everything for a long period of time19:26
* mordred is very supportive of incremental as long as we have an end-goal in mind19:26
ianwwe *definitely* need to make it incremental19:26
corvusmordred: ++19:26
clarkbnow incremental may be do it all in a month or two19:26
mordredclarkb: I definitely think it should be a priority effort19:26
ianwDevelopment Effort Estimate, Person-Years (Person-Months) = 33.57 (402.89)19:26
ianw (Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))19:26
clarkbbut you should know where to push the update to say fix etherpad19:26
ianwthat's sloccount on /etc/modules19:26
*** jamesmcarthur has quit IRC19:26
ianwre-writing all that in ansible isn't particuarly appealing19:27
fungilike we discovered yesterday that we may need to upgrade to latest etherpad and that took some moderate puppet updating. i would hate to think of what would have instead been involved in replacing puppety-etherpad_lite with ansible-role-etherpad_lite written from scratch19:27
clarkbfungi: ya19:27
clarkbthis is why I'd like to evaluate the specs together19:27
clarkbso that we can consider the effort of pushing puppet forward against what using containers or ansible would get us19:27
corvusfungi: there are lots of existing ansible roles19:27
fungicorvus: i'd be excited to find out that etherpad has an ansible role already19:28
corvusfungi: i'd wager that once the *rest* of the infrastructure is in place (basic system, users, etc), the effort for upgrading to puppet5 vs ansible for most services would be within a small percentage.19:28
clarkbthis is also likely something we should include in the specs19:28
*** krenczewski has quit IRC19:28
clarkba survey of existing tooling for our various services19:28
corvusfungi: there are at least 419:29
clarkbbut I think the thing to get us over the hump on actually moving forward here is being able to consider them together rather than just getting annoyed/scared/overwhelmed by the amount of work for $effort19:29
pabelangerthat's actually how the ansible spec is written, deal with common services first, port them to ansible, but still run puppet for other bits. Then slowly replace or decide to uplift to another version19:29
clarkbbecomes a lot less scary when you know that doing something else is either more work or bigger risk or has fewer features19:29
clarkbhopefully next week I can ask everyoen to go and read three specs and we can then make a decision sometime not too long after that19:30
clarkbanything else we want to consider that won't be covered by ^19:30
clarkbcool that takes us to the next topic19:31
clarkb#topic General Topics19:31
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:31
clarkbthe future of third part ci instructions19:32
clarkbianw: corvus this came out of the zuul meeting yesterday19:32
ianwyes, there's some notes in the agenda19:33
fungiit sounded like we had two different cases... it would be nice for the zuul family of projects to have a thorough instructional walkthrough... it might also be necessary to have some more neatly-packaged solution for people who are deploying an openstack third-party ci system and don't want to have to learn anything19:33
clarkbthe basic concern appears to be that puppet-openstackci cannot deploy a zuul v3 as it exists today19:33
clarkbfungi: right and puppet-openstackci has been our existing "use this" tool for the openstack third party ci specific use case19:33
corvusit is also how we deploy our system (sort-of), with additional things third-party folks don't normally want19:34
anteayadoes puppet-openstackci still work?19:34
ianwclarkb: i guess that's the root cause ... the bigger question is if someone is offering to help fix that, how should we assist19:34
anteayadoes it deploy something?19:34
clarkbanteaya: for zuulv2 yes19:34
corvusso it's 3 things: our system.  simple openstack third-party ci.  project that wants to have an "openstack infra".19:34
fungipuppet-openstackci was also driven mostly by third-party ci operators, so it seems to me that it would be fine if we waited for some of them to want to write the zuul v3 edition19:34
corvusit still deploys part of our system19:35
corvusi've only worked around some parts of it for zuulv319:35
*** annabelleB has joined #openstack-meeting19:35
fungitrue. we'd need to end up using less and less of it if we don't upfit it ourselves19:35
corvusdo we want to continue with the premise that module should work for all 3 audiences?  it's possible, but it's work.19:36
clarkbfor me I've always struggled with the overlap between our system and people that want an openstack infra19:36
clarkbsystem-config is not a public interface which is why we have puppet-openstackci I think19:36
anteayaperhaps a session at opendev?19:37
corvusor do we want to make separate systems: a 3pci-in-a-box, and then whatevere we're using to run ours.19:37
corvusi don't have a problem with changes to puppet-zuul.  nor would i with ansible-role-zuul.  where this gets really hard for me is puppet-openstackci where i feel like i'm the sysadmin for 100 systems i've never met.19:38
clarkbcorvus: right that19:38
fungii think if we make a "whatever we're using to run ours" (which we need to do anyway) then we can let "3pci-in-a-box" happen as people come along who are interested in implementing it19:38
fungii consider the puppet-openstackci shim module well-intentioned but ultimately problematic19:39
ianwfungi: the problem is we have someone interested in developing it, asking for help on what to do, and i'm not really sure we have an answer for them19:39
fungiwe should focus on having a good and flexible base layer which can have multiple entry points19:39
anteayaianw who is the person?19:39
corvusfungi: i think we should set some direction there.  i think we're in a good position to suggest an implementation for 3pci.  i don't know that there's anyone but a handful of us that could tell people how to do that with zuulv3 for now.19:39
clarkbianw: I think bernd is interested more out of learning how infra tools work and the third party ci docs got them furthest along there19:39
clarkbianw: and not necessarily for third party ci specifically19:40
fungiyeah, bernd happened across the documentation and decided to see if it still works and provides any insights into how our systems operate19:40
corvus(and to be clear, i'm not personally ready to send out the email that says "hey 3pci folks, you should all upgrade to zuulv3 now!" i think we have a little more work for that yet)19:40
*** markvoelker_ has quit IRC19:41
anteayacorvus, ++19:41
pabelangerif we want to support 3pci using puppet, I can work on it in puppet-openstackci. But, as I spend more time one windmill, I personally prefer working on it.19:41
*** markvoelker has joined #openstack-meeting19:41
fungiyeah, i'm not saying we shouldn't set direction... more that the idea of modelling our deployment as just a special case of a third-party ci deployment is a bit confining19:41
corvusbut if we don't at least create one 3pci-in-a-box recipe, then the space is going to get really muddled, and we won't see good results.  or, people will keep trying to just run our system-config.19:41
mordredis it worth considering softwarefactory to be part of the solution some of this? they've been more focused on 'easily installable copy of infra' as a primary goal than we have ... I think we'd need to sort out how to get sf to not be carrying unlanded patches first, but may be worth considering?19:41
corvusfungi: i agree with that19:42
mordredfungi: ++19:42
*** amodi has joined #openstack-meeting19:42
clarkbmordred: thats my concern with software factory, its presented as infra made easy but reality is it tends to be a fairly large forkl and people ask us questins about it all the time19:42
corvusmordred: maybe that's a good answer for "i want to run a fuul openstack-infra".  i'm not sure it's the best 3pci in a box?19:42
ianwfungi: ++ ... i think the future more looks like "here's a nicely wrapped up zuul/nodepool/jobs that plugs into openstack" rather than "here's how to run a mini openstack-infra"19:42
fungiianw: right, i think they're separate branches from a base layer rather than one being branched off the other19:43
mordredclarkb: yes- I think we'd have to sort that story out19:43
corvusi mean, the 3pci instructions for puppet-openstackci get you zuul+apache talking to our gerrit.  i think that's what that product needs, and not anything else.19:43
*** awaugama has quit IRC19:43
mordredyah - and that's a good definition of what a 3pci needs19:44
corvusianw: indeed, with zuulv3 we have an opportunity to have something that will write an appropriate tenant config to pull in devstack, tempest, etc, to get all the jobs they should base their tests on.19:44
corvusthat's an advantage of a purpose-built 3pci solution19:44
clarkbsounds like we'd maybe punt on an infra made easy for now, suggest a third party ci specific tool, then have our own tools for deploying infra itself?19:45
clarkband we'd work with interested 3pci groups to build that tool?19:45
corvusclarkb: yeah, i think decoupling this from infra actual makes both things easier, and this is the right time on both accounts.19:45
*** markvoelker has quit IRC19:45
*** jessegler has quit IRC19:45
mordredclarkb: yah - that sounds good to me19:46
clarkbianw: ^ does that make sense as a path forward to you (you posted the topic so want to make sure your input is heard :) )19:46
ianwpabelanger: is windmill in a position to be this 3pci thing?19:46
corvusmaybe we should write up an infra spec for "build a new 3pci solution for zuulv3" ?19:46
fungiprobably helps to look back at where puppet-openstackci came from too... it was in part at attempt to codify and automate some install howtos from random blogs frozen in time, and partly at attempt to keep us from making lock-step changes in services and system-config/project-config which subsequently broke people who were running outdated forks of system-config/project-config19:46
mordredianw, pabelanger: it could certainly be the basis of it19:46
pabelangerianw: pretty close, yes19:46
pabelangerworking on documentation for it to be used in opendevconf workshop19:47
mordredfungi: yah - a lot of that got rolled in to the design of zuul v3 too - so some of the issues p-oci was working on solving are just different now19:47
corvusfungi: indeed -- i think discipline around low-level service modules + testing can help with that.19:47
mordredand we already have to make sure we dont' make changes to zuul-jobs that will break people consuming that repo19:47
corvusand what mordred said19:47
fungiyeah, we're in a much better place wrt all of that than we were several years ago19:47
pabelangerianw: can give you a run though this week if you'd like19:48
anteayahas anyone talked to any third party operators about this topic?19:48
*** andreas_s has joined #openstack-meeting19:48
clarkbanteaya: I think that is the next step, we are just trying to figure out where we as infra and zuul devs stand19:48
anteayasome of our folks who use puppet-openstackci now?19:48
anteayaah okay sorry19:49
fungithe ones who were most communicative in the past were maintaining puppet-openstackci19:49
corvusspeccing this out would be a great way to get input19:49
anteayafungi, mostly ramy yes19:49
mordredit's also worth considering that some of them may want to continue to use puppet for a third-party-ci - so if our 3pci isn't based on it, we could turn that repo over to whoever *does* want to use it19:49
clarkb#agreed Spec out third party ci tooling as its own tool and solicit feedback from third party ci operators.19:50
funginow that they're mostly gone, we're sort of left with a rift between what we need to do and a bunch of users who are probably not very connected with what they're running19:50
corvusmordred: yes, easier to do too if we decouple infra19:50
corvuswhot's writing the spec?19:50
clarkbianw: corvus et al does that seem to reflect what we've ended up at?19:50
anteayafungi, yes19:50
mordredclarkb: yah19:50
ianwcorvus/clarkb: i'll volunteer to write the spec, i think i've got the gist of the ideas from this and zuul conversation19:50
corvusclarkb: ++ (but i'd love an assignment)19:50
clarkbcorvus: ^ looks like we have one, thanks ianw19:50
fungithanks ianw!19:50
corvusianw: great, thanks.  expect interest/help from me.19:51
clarkb#topic Open Discussion19:51
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:51
anteayaI have a thing19:51
clarkbanteaya: go for it19:51
anteayahttps://review.openstack.org/#/c/557979/ is the current stand up a survey server patch19:52
anteayait fails zuul puppet apply because the puppet module is written in puppet 419:52
anteayaso currently fungi has advised me to scope the module and pull what I need from it, rewrite it in the system-config patch and don't worry about using a module19:53
*** andreas_s has quit IRC19:53
fungiskimming that module, most of its complexity is around managing the database and webserver which we'd want to override anyway19:53
anteayajust wanted folks to know current thought, the spec says we will use a module or create one19:53
anteayaanyone object?19:53
mordredthat seems like a great path forward for now- especially given the discussion around considering puppet4-5/ansible/containers19:53
*** sidx64 has joined #openstack-meeting19:54
*** markvoelker has joined #openstack-meeting19:54
anteayamordred, thank you19:54
anteayaI'll offer a new patch to the spec to state the new module-less direction19:54
mordredit doesn't seem like investing in a module creation for this would be the right place to spendeffort19:54
fungiwe could revisit leveraging the limesurvey module if/when we're on newer puppet or at least have the opportunity to run different puppet versions to deploy different services19:54
anteayawith rationale19:54
mordredanteaya: cool19:54
mordredfungi: ++19:54
clarkbseems like a reasonable way forward19:54
anteayathank you19:54
corvusi'm torn.  i feel like we finally got all 'general purpose' puppet code out of system-config.  i feel like that's a bit of a step backward.  maybe it's a calculated regression we want to make.19:55
ianwanteaya: if we fork the module and remove the "String " bits, does it work?19:55
anteayaianw I don't know, I haven't tried that yet19:55
ianwyou could try that by forking it privately on github and updating modules.env, then re-running ci19:55
anteayaI have zero puppet, I'm copy pasting here19:55
fungiwe could make our own module for it, though that gets into the territory of competing with a module on the forge (specifically so that we can support an eol puppet version with it)19:55
anteayaany direction I take means that fungi or someone else has to hold my hand19:56
pabelangermy internet is terrible today, apologies to people that have send a message my way19:56
anteayathe limesurvey puppet person is looking for a new maintainer19:56
anteayaI emailed him last week and cc'd clark on it and heard no reply19:56
anteayacorvus I totally get your stance, I wish I had cmurphys puppet ability here19:57
anteayabut the thing is I'm on my own dime, trying to get something up so I can get consulting contracts which I want to shop at the summit19:57
anteayanot trying to bend infra policy19:57
clarkbI'd be wary of volunteering to maintain that module long term given we need to decide our own long term plans there but maybe that is an option should we decide to continue with puppet19:57
anteayabut I need to get a product I'm able to offer a paying customer soon19:58
fungiit's hard to say how much general-purpose puppet we'd be introducing into a class in system-config for this. it could be fairly minimal depending on how complex deploying limesurvey actually is19:58
clarkband we can convert to that module under new maintainerhsip (us) at that point19:58
*** salv-orlando has joined #openstack-meeting19:58
ianwanteaya: i can give you a hand seeing if the changes to the module are minimal for puppet3 support; see https://review.openstack.org/#/c/559178/20:00
corvusi'm not going to object to putting some puppet in system-config, just that if we do, that's something that we're likely going to want to change if we upgrade puppet.20:00
corvusit's also how we ended up with people wanting to run our system-config repo, and how we ended up with puppet-openstackci.  :)20:00
clarkbcorvus: ++ we can capture that in the spec too20:00
clarkband we are at time. Thank you everyone20:00
anteayaianw thanks I'll accept your offer, if it doesn't work, I'd like to leave the meeting with a back up plan if we can20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Apr 10 20:00:55 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
fungioh, yeah i expect it to be wrapped in a big flashing #TODO comment for rip-and-replace once we can puppet 420:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-04-10-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-04-10-19.01.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-04-10-19.01.log.html20:01
*** pcaruana has quit IRC20:01
corvusanteaya: my read is that put it in system-config is a backup plan we can work with20:01
anteayacorvus, thank you20:01
*** Shrews has left #openstack-meeting20:02
*** tobiash has left #openstack-meeting20:02
*** salv-orlando has quit IRC20:03
*** rbowen has quit IRC20:03
*** rbowen has joined #openstack-meeting20:04
*** salv-orlando has joined #openstack-meeting20:07
*** rpioso|afk is now known as rpioso20:10
*** markvoelker_ has joined #openstack-meeting20:17
*** markvoelker has quit IRC20:21
*** tssurya has joined #openstack-meeting20:21
*** erlon has quit IRC20:23
*** sidx64_ has joined #openstack-meeting20:27
*** liuzz has quit IRC20:27
*** sidx64 has quit IRC20:29
*** artom has quit IRC20:29
*** e0ne has quit IRC20:30
*** annabelleB has quit IRC20:39
*** gman-tx has quit IRC20:42
*** raildo has quit IRC20:44
*** annabelleB has joined #openstack-meeting20:47
*** kaisers has quit IRC20:51
*** sidx64 has joined #openstack-meeting20:55
*** felipemonteiro__ has quit IRC20:56
*** annabelleB has quit IRC20:57
*** annabelleB has joined #openstack-meeting20:58
*** sidx64_ has quit IRC20:58
*** priteau has quit IRC20:59
*** priteau has joined #openstack-meeting21:00
*** dustins has joined #openstack-meeting21:01
*** julim has quit IRC21:01
*** slaweq has quit IRC21:02
*** slaweq has joined #openstack-meeting21:02
*** priteau has quit IRC21:04
*** ad_ri3n_ has joined #openstack-meeting21:06
*** slaweq has quit IRC21:07
*** sshank has joined #openstack-meeting21:08
*** rfolco|rover is now known as rfolco|off21:08
*** sidx64 has quit IRC21:11
*** jamesmcarthur has joined #openstack-meeting21:11
*** jamesmca_ has joined #openstack-meeting21:14
*** jamesmcarthur has quit IRC21:15
*** gman-tx has joined #openstack-meeting21:19
*** kaisers has joined #openstack-meeting21:22
*** pchavva has quit IRC21:26
*** eharney has quit IRC21:30
*** tssurya has quit IRC21:31
*** edmondsw has quit IRC21:42
*** edmondsw has joined #openstack-meeting21:42
*** edmondsw has quit IRC21:43
*** esberglu has quit IRC21:52
*** yamamoto has quit IRC21:54
*** gman-tx has quit IRC21:54
*** yamamoto has joined #openstack-meeting21:54
*** dustins has quit IRC21:56
*** priteau has joined #openstack-meeting21:58
*** jamesmca_ has quit IRC22:02
*** gman-tx has joined #openstack-meeting22:07
*** bobh has quit IRC22:07
*** ad_ri3n_ has quit IRC22:07
*** priteau has quit IRC22:08
*** edmondsw has joined #openstack-meeting22:09
*** sshank has quit IRC22:10
*** edmondsw has quit IRC22:10
*** VW has quit IRC22:10
*** jamesmcarthur has joined #openstack-meeting22:11
*** jamesmcarthur has quit IRC22:13
*** ekcs has quit IRC22:16
*** VW has joined #openstack-meeting22:16
*** tssurya has joined #openstack-meeting22:17
*** jamesmcarthur has joined #openstack-meeting22:17
*** jamesmcarthur has quit IRC22:17
*** tpsilva has quit IRC22:17
*** tssurya has quit IRC22:21
*** rcernin has joined #openstack-meeting22:23
*** annabelleB has quit IRC22:28
*** rpioso is now known as rpioso|afk22:34
*** yamamoto has quit IRC22:35
*** yamamoto has joined #openstack-meeting22:39
*** yamamoto has quit IRC22:40
*** lbragstad has quit IRC22:42
*** hongbin has quit IRC22:42
*** yamahata has quit IRC22:45
*** erlon has joined #openstack-meeting22:55
*** slaweq has joined #openstack-meeting23:03
*** fnaval has quit IRC23:06
*** slaweq has quit IRC23:08
*** beekhof has joined #openstack-meeting23:08
*** lbragstad has joined #openstack-meeting23:09
*** radeks has quit IRC23:21
*** fnaval has joined #openstack-meeting23:25
*** HeOS has quit IRC23:38
*** bobh has joined #openstack-meeting23:39
*** yamamoto has joined #openstack-meeting23:40
*** hoangcx has quit IRC23:41
*** bobh has quit IRC23:44
*** yamamoto has quit IRC23:46
*** dmacpher_ has quit IRC23:49
*** rbudden has quit IRC23:50
*** iyamahat has joined #openstack-meeting23:52
*** gman-tx has quit IRC23:53
*** annabelleB has joined #openstack-meeting23:59
*** amodi has quit IRC23:59

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