Tuesday, 2018-01-16

*** genek has joined #openstack-meeting00:00
*** sdague has quit IRC00:01
*** genek has quit IRC00:05
*** VW has quit IRC00:06
*** fnaval has quit IRC00:08
*** claudiub has quit IRC00:10
*** markvoelker has joined #openstack-meeting00:11
*** genek has joined #openstack-meeting00:12
*** genek has quit IRC00:17
*** awaugama has joined #openstack-meeting00:19
*** dmacpher has quit IRC00:23
*** dtrainor has quit IRC00:23
*** dtrainor has joined #openstack-meeting00:27
*** yangyapeng has quit IRC00:27
*** wanghao has joined #openstack-meeting00:33
*** armax has joined #openstack-meeting00:36
*** wanghao has quit IRC00:36
*** yamamoto has joined #openstack-meeting00:36
*** wanghao has joined #openstack-meeting00:37
*** genek has joined #openstack-meeting00:38
*** Dinesh_Bhor has joined #openstack-meeting00:39
*** Swami_ has quit IRC00:40
*** wanghao has quit IRC00:40
*** Dinesh_Bhor has quit IRC00:41
*** wanghao has joined #openstack-meeting00:41
*** Dinesh_Bhor has joined #openstack-meeting00:43
*** genek has quit IRC00:43
*** wanghao has quit IRC00:44
*** wanghao has joined #openstack-meeting00:44
*** genek has joined #openstack-meeting00:45
*** shu-mutou has joined #openstack-meeting00:46
*** wanghao has quit IRC00:50
*** genek has quit IRC00:50
*** wanghao has joined #openstack-meeting00:50
*** Dinesh_Bhor has quit IRC00:51
*** Dinesh_Bhor has joined #openstack-meeting00:52
*** wanghao has quit IRC00:52
*** wanghao has joined #openstack-meeting00:53
*** Swami_ has joined #openstack-meeting00:54
*** tovin07_ has joined #openstack-meeting00:57
*** wanghao has quit IRC00:57
*** wanghao has joined #openstack-meeting00:57
*** awaugama has quit IRC01:00
*** genek has joined #openstack-meeting01:00
*** yangyapeng has joined #openstack-meeting01:00
*** wanghao has quit IRC01:00
*** wanghao has joined #openstack-meeting01:01
*** yangyapeng has quit IRC01:04
*** genek has quit IRC01:05
*** wanghao has quit IRC01:05
*** wanghao has joined #openstack-meeting01:06
*** genek has joined #openstack-meeting01:06
*** wanghao has quit IRC01:10
*** genek has quit IRC01:10
*** wanghao has joined #openstack-meeting01:11
*** yangyapeng has joined #openstack-meeting01:14
*** wanghao has quit IRC01:16
*** wanghao has joined #openstack-meeting01:16
*** genek has joined #openstack-meeting01:17
*** julim has quit IRC01:17
*** wanghao has quit IRC01:18
*** wanghao has joined #openstack-meeting01:18
*** genek has quit IRC01:22
*** wanghao has quit IRC01:23
*** wanghao has joined #openstack-meeting01:24
*** caowei has joined #openstack-meeting01:25
*** wanghao has quit IRC01:29
*** wanghao has joined #openstack-meeting01:30
*** Swami_ has quit IRC01:30
*** caowei has quit IRC01:32
*** wanghao has quit IRC01:35
*** wanghao has joined #openstack-meeting01:36
*** wanghao has quit IRC01:43
*** sapd__ has joined #openstack-meeting01:43
*** sapd_ has quit IRC01:43
*** wanghao has joined #openstack-meeting01:43
*** kiennt26 has joined #openstack-meeting01:46
*** wanghao has quit IRC01:49
*** wanghao has joined #openstack-meeting01:50
*** zhurong has joined #openstack-meeting01:51
*** ricolin has joined #openstack-meeting01:52
*** wanghao has quit IRC01:52
*** wanghao has joined #openstack-meeting01:53
*** julim has joined #openstack-meeting01:54
*** julim has quit IRC01:54
*** wanghao has quit IRC01:55
*** wanghao has joined #openstack-meeting01:56
*** hongbin has joined #openstack-meeting01:56
*** wanghao has quit IRC01:59
*** wanghao has joined #openstack-meeting01:59
*** masber has joined #openstack-meeting02:00
*** haint_ has joined #openstack-meeting02:01
*** wanghao has quit IRC02:01
*** masuberu has quit IRC02:02
*** wanghao has joined #openstack-meeting02:02
*** haint has quit IRC02:04
*** wanghao has quit IRC02:05
*** wanghao has joined #openstack-meeting02:06
*** wanghao has quit IRC02:10
*** wanghao has joined #openstack-meeting02:11
*** wanghao has quit IRC02:17
*** wanghao has joined #openstack-meeting02:18
*** wanghao has quit IRC02:24
*** wanghao has joined #openstack-meeting02:24
*** chyka_ has quit IRC02:25
*** wanghao has quit IRC02:31
*** wanghao has joined #openstack-meeting02:31
*** edmondsw has quit IRC02:34
*** liyi has joined #openstack-meeting02:35
*** wanghao has quit IRC02:35
*** wanghao has joined #openstack-meeting02:36
*** fengshengqin has joined #openstack-meeting02:37
*** fengshengqin has quit IRC02:38
*** fengshengqin has joined #openstack-meeting02:38
*** wanghao has quit IRC02:38
*** wanghao has joined #openstack-meeting02:39
*** bbzhao has quit IRC02:40
*** bzhao has quit IRC02:40
*** fengshengqin has quit IRC02:41
*** julim has joined #openstack-meeting02:41
*** wanghao has quit IRC02:42
*** tovin07__ has joined #openstack-meeting02:42
*** wanghao has joined #openstack-meeting02:43
*** genek has joined #openstack-meeting02:43
*** tovin07_ has quit IRC02:45
*** gongysh has joined #openstack-meeting02:45
*** wanghao has quit IRC02:46
*** wanghao has joined #openstack-meeting02:46
*** fzdarsky_ has joined #openstack-meeting02:46
*** fzdarsky|afk has quit IRC02:50
*** wanghao has quit IRC02:51
*** gongysh_ has joined #openstack-meeting02:51
*** wanghao has joined #openstack-meeting02:53
*** Dinesh_Bhor has quit IRC02:53
*** gongysh has quit IRC02:53
*** hongbin has quit IRC02:53
*** hongbin has joined #openstack-meeting02:54
*** Dinesh_Bhor has joined #openstack-meeting02:55
*** wanghao has quit IRC02:55
*** wanghao has joined #openstack-meeting02:55
*** bkopilov has quit IRC02:58
hongbin#startmeeting zun03:00
*** wanghao has quit IRC03:00
hongbin#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2018-01-23_0300_UTC Today's agenda03:00
openstackMeeting started Tue Jan 16 03:00:01 2018 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
mkraio/03:00
*** wanghao has joined #openstack-meeting03:00
*** Dinesh_Bhor has quit IRC03:00
*** kevzha01 has joined #openstack-meeting03:00
*** kevzha01 is now known as kevinz03:01
kevinzo/03:01
hongbinhi mkrai kevinz03:01
*** pengdake_ has joined #openstack-meeting03:01
hongbinwe could have a short meeting today03:01
*** wanghao has quit IRC03:01
kevinzOK03:01
hongbinmkrai: what is news on your side ?03:02
*** wanghao has joined #openstack-meeting03:02
mkraiI was working on the CC intergartion patches03:02
mkraiAnd both the patches are merged03:02
hongbingreat03:03
mkraiSo we now have a basic support of running CC in Zun03:03
hongbinthat is awesome03:03
mkraiWe have put this on hold because of new Kata containers03:03
*** wanghao has quit IRC03:03
mkraiWe will revisit this feature when Kata is ready for use03:03
hongbinsounds good03:03
mkraiThat's all from my side03:03
hongbinmkrai: thanks madhuri03:04
mkraiThanks hongbin for reviewing :)03:04
hongbinkevinz: any update from your side?03:04
*** wanghao has joined #openstack-meeting03:04
hongbinmkrai: np03:04
kevinzI'm working on k8s integration03:04
kevinzI pushed some patch to modify capsule create and parameters03:04
kevinzAlso works on Gophercloud03:05
kevinzgophercloud support with zun03:05
hongbinthat is cool03:05
kevinzhttps://github.com/gophercloud/gophercloud/issues/70003:05
*** wanghao has quit IRC03:05
kevinzThis one03:05
*** wanghao has joined #openstack-meeting03:06
kevinzBut now capsule is not in the stable api, so gophercloud will open a new branch to deal with it03:06
hongbinoh, i see03:06
mkraithat is awesome kevinz :)03:06
kevinzI will submit one patch this week03:06
kevinzthanks mkrai03:06
hongbinso if capsule is in the stable api, gopher cloud will merge the zun-exp tree ?03:07
kevinzhongbin: yes, they will03:07
*** wanghao has quit IRC03:07
hongbinkevinz: i see, another question03:07
kevinzhongbin: But I think stay in zun-exp is also OK now for development03:08
*** wanghao has joined #openstack-meeting03:08
hongbinkevinz: +103:08
*** kiseok7 has quit IRC03:08
hongbinkevinz: who will review the zun-exp tree ?03:09
kevinzkevinz: will do more to make capsule more stable, then move to experimental to stable03:09
kevinzhongbin: you mean in the gophercloud03:09
*** wanghao has quit IRC03:09
kevinz?03:09
hongbinyes03:09
kevinzjrperritt  and jtopjian03:09
*** wanghao has joined #openstack-meeting03:09
hongbinok, i assume both zun-exp and master are the same set of reviewers in gophercloud ?03:10
hongbinthe rational to have a separated tree is to mark the features as experimental i guess03:10
kevinzBut they are not familiar with zun, so they request us to submit patch which follow the gophercloud rule03:11
kevinzyes they are the same set of reviewer03:11
hongbini see03:11
kevinzhongbin: Yeah I think so03:11
hongbini see03:11
hongbinkevinz: great job in gophercloud03:12
*** wanghao has quit IRC03:12
kevinzhongbin: Thanks03:12
hongbinkevinz: good to see things are working in good progress there03:12
*** wanghao has joined #openstack-meeting03:12
kevinzSure, hope to update more information about this next meeting03:13
hongbinkevinz: great, look forward to it03:13
hongbinkevinz: thanks kevin03:13
*** markvoelker has quit IRC03:13
hongbinfrom my side, i was mainly working on a few heat patches03:14
*** wanghao has quit IRC03:14
kevinzhongbin: yw03:14
hongbin#link https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:master+topic:zun03:14
*** wanghao has joined #openstack-meeting03:15
hongbinhopefully, we could have all the patches merged in this release03:15
hongbinwhich will be due in a few weeks03:15
mkraihongbin: when is the realease due?03:15
mkraiok03:15
hongbinbtw, this release will be the first 1.x release for zun03:15
*** wanghao has quit IRC03:15
hongbinmkrai: https://releases.openstack.org/queens/schedule.html03:16
*** wanghao has joined #openstack-meeting03:16
hongbinmkrai: i guess the release will be in early feb03:16
mkraihongbin: Thank you for the link03:17
hongbinok, that is all from my side03:17
hongbinanything else before i close the meeting?03:17
mkraino03:17
hongbinok03:17
hongbinmkrai: kevinz thanks for joininig the meeting, see you next time03:18
hongbin#endmeeting03:18
*** wanghao has quit IRC03:18
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"03:18
openstackMeeting ended Tue Jan 16 03:18:13 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2018/zun.2018-01-16-03.00.html03:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2018/zun.2018-01-16-03.00.txt03:18
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2018/zun.2018-01-16-03.00.log.html03:18
*** wanghao has joined #openstack-meeting03:18
*** pengdake_ has left #openstack-meeting03:18
*** hongbin has quit IRC03:19
*** wanghao has quit IRC03:19
*** hongbin has joined #openstack-meeting03:20
*** wanghao has joined #openstack-meeting03:20
*** wanghao has quit IRC03:26
*** wanghao has joined #openstack-meeting03:26
*** epico has joined #openstack-meeting03:26
*** wanghao has quit IRC03:31
*** wanghao has joined #openstack-meeting03:32
*** wanghao has quit IRC03:36
*** wanghao has joined #openstack-meeting03:37
*** bobh has joined #openstack-meeting03:38
*** yamamoto_ has joined #openstack-meeting03:39
*** wanghao has quit IRC03:39
*** wanghao has joined #openstack-meeting03:40
*** gongysh_ has quit IRC03:42
*** rbudden has quit IRC03:42
*** wanghao has quit IRC03:42
*** yamamoto has quit IRC03:43
*** wanghao has joined #openstack-meeting03:43
*** edmondsw has joined #openstack-meeting03:47
*** wanghao has quit IRC03:47
*** wanghao has joined #openstack-meeting03:48
*** wanghao has quit IRC03:52
*** edmondsw has quit IRC03:52
*** wanghao has joined #openstack-meeting03:52
*** tpatil has joined #openstack-meeting03:53
*** wanghao has quit IRC03:58
*** samP has joined #openstack-meeting03:58
*** sagara has joined #openstack-meeting03:59
*** wanghao has joined #openstack-meeting03:59
samPhi all for masakari04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Jan 16 04:00:17 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
tpatilHi04:00
openstackThe meeting name has been set to 'masakari'04:00
*** wanghao has quit IRC04:00
samPtpatil: Hi04:00
sagarahi04:00
*** rkmrHonjo has joined #openstack-meeting04:00
samPsorry for long absent04:00
*** bobh has quit IRC04:00
samP#topic High priority items04:00
*** wanghao has joined #openstack-meeting04:01
*** openstack changes topic to "High priority items (Meeting topic: masakari)"04:01
samPAny Hight Priority items to discuss?04:01
samPif any please bring them up any time. proceeding to next topic04:01
samP#topic Critical bugs04:02
*** openstack changes topic to "Critical bugs (Meeting topic: masakari)"04:02
samPAny Bugs to discuss?04:02
tpatil#link https://review.openstack.org/#/c/531310/04:02
tpatilI think this bug should be fixed in queens release04:02
tpatilI have voted -104:02
*** wanghao has quit IRC04:02
rkmrHonjotpatil: I heard that Takahara is addressing your comments now.04:03
*** wanghao has joined #openstack-meeting04:03
samPtpatil: thanks for the review.04:03
tpatilrkmrHonjo: Ok04:03
*** Dinesh_Bhor has joined #openstack-meeting04:04
samPcomments are not critical, its a easy fix.04:04
samPtpatil: rkmrHonjo: let's merge this in Q04:04
tpatilsamP: Yes04:04
*** wanghao has quit IRC04:04
rkmrHonjosamP: ok, I tell it to takahara.04:05
tpatilAnother patch : https://review.openstack.org/#/c/486576/04:05
samPtpatil: rkmrHonjo: thanks04:05
*** wanghao has joined #openstack-meeting04:05
tpatilwe should merge this patch as py35 tests are failing on all patches04:05
tpatilI have already voted +2, need another +204:06
samPtpatil: I will look into thsi04:06
samPs/thsi/this04:06
tpatilsamP: ok, Thanks04:06
rkmrHonjosamP: thanks.04:06
*** wanghao has quit IRC04:06
samPtpatil: thanks for review04:06
*** links has joined #openstack-meeting04:06
samPrkmrHonjo: thanks for the fix04:07
*** wanghao has joined #openstack-meeting04:07
rkmrHonjoDinesh suggested to change the py35 test to vote.(current py35 test is non-vote.) I think that we can change it after merging it.04:08
samPrkmrHonjo: sure, let's see how things work after merge above patch04:09
rkmrHonjook.04:09
samPif no problem, then let's put py35 to vote04:09
samPAny other bugs?04:10
tpatilhttps://bugs.launchpad.net/masakari/+bug/173834004:10
openstackLaunchpad bug 1738340 in masakari "When no reserved_host available, nova-compute service on failed host remains enabled" [Undecided,In progress] - Assigned to takahara.kengo (takahara.kengo)04:10
*** wanghao has quit IRC04:10
*** wanghao has joined #openstack-meeting04:11
tpatilin the fix, a new config option is introduced so I have commented on the patch asking to write down lite-specs04:11
tpatilis it ok to fix this issue as a bug or feature?04:11
rkmrHonjotpatil: I think that this patch doesn't add a new config option.04:12
tpatilsorry, no new config option04:12
*** wanghao has quit IRC04:12
*** wanghao has joined #openstack-meeting04:13
rkmrHonjotpatil: ok. And, I think that this is just a bug fix. Because this patch doesn't add new action.04:13
*** VW has joined #openstack-meeting04:14
rkmrHonjoIn current rh_workflow, failure host is still enable and VMs are not evacuated if reserved host is nothing.04:14
samPrkmrHonjo: tpatil: sorry fot the delay, tried to understand the problem here04:14
*** wanghao has quit IRC04:15
tpatilThe notification request will be marked as complete which will give false impression to operator04:15
samPrkmrHonjo: this patch propose to disable to nova-compute on failed host04:15
*** wanghao has joined #openstack-meeting04:15
tpatilafter disabling compute host04:15
rkmrHonjoBut, failure host is disable if this patch will be merged. I think that it is not new action, and it is good from point of safety view.04:15
rkmrHonjotpatil: Ah, thanks, I understand your opinion.04:16
tpatilif notification request is complete, it means that the failed host is evacuated successfully, but if reserved host is not available, then it is simply disabling compute host which I think isn't sufficient04:17
samPtpatil: agree.04:17
rkmrHonjotpatil: Do you think this idea:  "Disable host, and not complete the notification"  ?04:18
*** wanghao has quit IRC04:18
samPyou may disable to compute node but should not complete the recovery04:18
rkmrHonjosamP: yes.04:18
*** wanghao has joined #openstack-meeting04:18
tpatilsamP: agree04:19
rkmrHonjook, can I(and Takahara) create a new patch according to samP's idea?04:19
tpatilin the periodic task, it will again try to execute the workflow and finally it will give up and set it failed04:19
*** ricolin has quit IRC04:20
*** wanghao has quit IRC04:20
samPtpatil: correct04:20
*** wanghao has joined #openstack-meeting04:20
*** ricolin has joined #openstack-meeting04:20
tpatilrkmrHonjo: I will add this comment on the patch04:21
samPI think we should bring this step to very beginning of the flow. (1) disable the compte node (2) runt evacuation04:21
samPI will add my comments too04:22
*** wanghao has quit IRC04:22
rkmrHonjotpatil: thanks! In that case, should I write a lite-spec?04:22
*** zhurong has quit IRC04:22
*** VW has quit IRC04:22
tpatilJust noticed that it is raising ReservedHostsUnavailable exception04:22
*** wanghao has joined #openstack-meeting04:22
tpatilso I think whatever we discussed is already taken care of. I will review the patch again04:23
rkmrHonjotpatil: I got it.04:24
samPrkmrHonjo: I will add a comment if spec required04:24
rkmrHonjosamP: ok.04:25
*** bkopilov has joined #openstack-meeting04:25
*** wanghao has quit IRC04:25
rkmrHonjoI think that releasenote is required.04:25
samPrkmrHonjo: it depends on how you implement this.04:27
rkmrHonjosamP: Yeah. I wait your comments.04:27
samPlet's do review first and check what kind of changes needed04:28
rkmrHonjoI got it.04:28
samPthen we could discuss about spec and release notes04:28
samPrkmrHonjo: BTW thanks for bringing up the release note point04:29
samPany other bugs/patches for discuss?04:30
tpatilsam04:30
tpatilsamP: not my side04:30
rkmrHonjono.04:30
samPthanks.. let's move to next topic04:31
samP#topic Dicussion Points04:31
*** openstack changes topic to "Dicussion Points (Meeting topic: masakari)"04:31
samPSorry that I couldn't follow the work.04:32
samPPlease proceed if you have any updates on your work.04:32
tpatilRegarding horizon dashboard04:33
tpatilNiraj has pushed initial cookie cutter patch04:33
tpatilI have voted + 2, need another +204:33
samPtpatil: I will check04:34
rkmrHonjooh, sorry, I couldn't review it last week...04:34
samPtpatil: Niraj: Thanks04:34
*** andreas_s has joined #openstack-meeting04:35
samPany other updates?04:37
rkmrHonjoCan I talk about my update?04:37
samPrkmrHonjo: sure, goahead04:37
rkmrHonjosamP: thanks.04:37
rkmrHonjoCall Force down API when host-failure will be notified04:37
rkmrHonjotpatil: Takahara replied to you on gerrit. Please check it.04:38
rkmrHonjo#link https://review.openstack.org/#/c/526598/04:38
tpatilrkmrHonjo: I have read his reply and I agree the evacuation will succeed. But still compute service might be still up and running which could update instance states04:39
*** andreas_s has quit IRC04:40
*** bzhao__ has quit IRC04:40
*** bzhao_ has quit IRC04:40
rkmrHonjotpatil: I think that it is prevented. There is force down flag. I re-confirm it and write it on gerrit.04:41
*** gyee has quit IRC04:42
tpatilafter force down api is called , is compute service still running?04:42
tpatilI will test this case and let you know my results04:44
*** abhishekk has joined #openstack-meeting04:45
rkmrHonjotpatil: I think that is case-by-case. force down api doesn't kill the process. But, basically, operator will configure the crm to stop the node. And, it is same on current implementation(waiting 3 minutes).04:45
tpatilrkmrHonjo: If operator is going to handle force down notification and kill the compute service on the failed node, then I don't see there will be any problem04:47
samPrkmrHonjo: not clear, operator config the crm to catch "force-down" flag?04:48
samPs/force-down/forced_down04:49
rkmrHonjotpatil: No, crm doesn't catch force-down flag. Operator will config the crm to catch host down. If pacemaker catch the host down, masakari-monitor send a notification(host down).04:50
samPrkmrHonjo: got it.04:51
rkmrHonjoI think that force down flag is referred from nova. If it is true, nova doesn't change the status to up.04:51
samPyour point is, when masakari gets the HostDown notification, the host is already down for sure04:51
tpatilrkmrHonjo: I got it04:52
samPand its totally safe to use force-down api to bring down the binary and proceed the evacuation work flow04:52
*** epico has quit IRC04:52
samPcorrection: not bring down the binary, but just the put foreced-down flag on that binary04:54
samPrkmrHonjo: understood04:54
samPwe only have 5mis left04:54
*** epico has joined #openstack-meeting04:55
*** wanghao has joined #openstack-meeting04:56
samPI think if we do this change to masakari, this means pacemaker or anyone controlling the cluster must make sure that it kill the node before it sends the host failed notification to masakari04:57
samPI think we have already put this point in our docs. (if not we must)04:58
samPany other updates?04:58
tpatilNo04:58
rkmrHonjono.04:59
*** wanghao has quit IRC04:59
samPThank you all...04:59
rkmrHonjothank you.04:59
samPplease use #openstack-masakari or ML with [masakari] for further discussion04:59
samPThank you all04:59
*** wanghao has joined #openstack-meeting04:59
samP#endmeeting04:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:59
openstackMeeting ended Tue Jan 16 04:59:45 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-01-16-04.00.html04:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-01-16-04.00.txt04:59
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-01-16-04.00.log.html04:59
tpatilThank you04:59
rkmrHonjoBye.04:59
*** rkmrHonjo has quit IRC05:00
*** wanghao has quit IRC05:02
*** cburgess has quit IRC05:02
*** hongbin has quit IRC05:04
*** sagara has quit IRC05:04
*** Dinesh_Bhor has quit IRC05:07
*** Dinesh_Bhor has joined #openstack-meeting05:07
*** cburgess has joined #openstack-meeting05:08
*** janki has joined #openstack-meeting05:10
*** cburgess has quit IRC05:12
*** cburgess has joined #openstack-meeting05:13
*** markvoelker has joined #openstack-meeting05:14
*** abhishekk has left #openstack-meeting05:14
*** ekcs has quit IRC05:16
*** ekcs has joined #openstack-meeting05:17
*** markvoelker has quit IRC05:18
*** psachin has joined #openstack-meeting05:26
*** qwebirc66584 has joined #openstack-meeting05:27
*** qwebirc66584 has left #openstack-meeting05:28
*** coolsvap has joined #openstack-meeting05:28
*** claudiub has joined #openstack-meeting05:30
*** wanghao has joined #openstack-meeting05:31
*** longkb has joined #openstack-meeting05:38
*** wanghao has quit IRC05:39
*** wanghao has joined #openstack-meeting05:43
*** markvoelker has joined #openstack-meeting05:44
*** gongysh has joined #openstack-meeting05:47
*** wanghao has quit IRC05:47
*** wanghao has joined #openstack-meeting05:48
*** markvoelker has quit IRC05:49
*** wanghao has quit IRC05:53
*** absubram has joined #openstack-meeting05:53
*** wanghao has joined #openstack-meeting05:54
*** ekcs has quit IRC05:55
*** marios has joined #openstack-meeting05:55
*** wanghao has quit IRC05:55
*** wanghao has joined #openstack-meeting05:56
*** wanghao has quit IRC06:01
*** ekcs has joined #openstack-meeting06:01
*** wanghao has joined #openstack-meeting06:02
*** lpetrut has joined #openstack-meeting06:04
*** Dinesh_Bhor has quit IRC06:06
*** anilvenkata has quit IRC06:06
*** anilvenkata has joined #openstack-meeting06:06
*** wanghao has quit IRC06:06
*** rmk has quit IRC06:06
*** wanghao has joined #openstack-meeting06:08
*** wanghao has quit IRC06:08
*** armax has quit IRC06:08
*** hemna_ has quit IRC06:11
*** sridharg has joined #openstack-meeting06:14
*** wanghao has joined #openstack-meeting06:16
*** Dinesh_Bhor has joined #openstack-meeting06:17
*** wanghao has quit IRC06:18
*** wanghao has joined #openstack-meeting06:18
*** tpatil has quit IRC06:19
*** Tom-Tom has joined #openstack-meeting06:21
*** wanghao has quit IRC06:21
*** Dinesh_Bhor has quit IRC06:22
*** Dinesh_Bhor has joined #openstack-meeting06:22
*** wanghao has joined #openstack-meeting06:23
*** wanghao has quit IRC06:30
*** wanghao has joined #openstack-meeting06:31
*** wanghao has quit IRC06:35
*** wanghao has joined #openstack-meeting06:35
*** caisan has joined #openstack-meeting06:40
*** wanghao has quit IRC06:40
*** wanghao has joined #openstack-meeting06:41
*** liyi has quit IRC06:41
*** liyi has joined #openstack-meeting06:43
*** absubram has quit IRC06:43
*** wanghao has quit IRC06:43
*** wanghao has joined #openstack-meeting06:44
*** wanghao has quit IRC06:51
*** wanghao has joined #openstack-meeting06:52
*** caisan_ has joined #openstack-meeting06:55
*** wanghao has quit IRC06:56
*** wanghao has joined #openstack-meeting06:56
*** caisan has quit IRC06:58
*** fnaval has joined #openstack-meeting06:59
*** wanghao has quit IRC06:59
*** wanghao has joined #openstack-meeting07:00
*** liyi_ has joined #openstack-meeting07:01
*** liyi has quit IRC07:05
*** wanghao has quit IRC07:05
*** wanghao has joined #openstack-meeting07:05
*** links has quit IRC07:06
*** lpetrut has quit IRC07:07
*** wanghao has quit IRC07:09
*** wanghao has joined #openstack-meeting07:10
*** lpetrut has joined #openstack-meeting07:12
*** rcernin has quit IRC07:14
*** wanghao has quit IRC07:16
*** wanghao has joined #openstack-meeting07:17
*** caisan has joined #openstack-meeting07:22
*** wanghao has quit IRC07:22
*** links has joined #openstack-meeting07:22
*** wanghao has joined #openstack-meeting07:24
*** edmondsw has joined #openstack-meeting07:24
*** makowals has joined #openstack-meeting07:24
*** caisan_ has quit IRC07:25
*** wanghao has quit IRC07:25
*** andreas_s has joined #openstack-meeting07:27
*** wanghao has joined #openstack-meeting07:27
*** edmondsw has quit IRC07:28
*** Alex_Staf has quit IRC07:33
*** wanghao has quit IRC07:34
*** liyi_ has quit IRC07:34
*** wanghao has joined #openstack-meeting07:35
*** slaweq has joined #openstack-meeting07:36
*** slaweq has quit IRC07:36
*** slaweq has joined #openstack-meeting07:36
*** epico has quit IRC07:37
*** wanghao has quit IRC07:37
*** wanghao has joined #openstack-meeting07:38
*** janki has quit IRC07:39
*** links has quit IRC07:39
*** epico has joined #openstack-meeting07:40
*** wanghao has quit IRC07:42
*** wanghao has joined #openstack-meeting07:43
*** markvoelker has joined #openstack-meeting07:46
*** lpetrut has quit IRC07:49
*** wanghao has quit IRC07:49
*** samP has left #openstack-meeting07:49
*** samP has quit IRC07:50
*** wanghao has joined #openstack-meeting07:50
*** fnaval has quit IRC07:56
*** wanghao has quit IRC07:56
*** wanghao has joined #openstack-meeting07:57
*** caisan_ has joined #openstack-meeting07:57
*** wanghao has quit IRC08:00
*** caisan has quit IRC08:00
*** wanghao has joined #openstack-meeting08:01
*** tesseract has joined #openstack-meeting08:05
*** wanghao has quit IRC08:06
*** wanghao has joined #openstack-meeting08:06
*** slaweq has quit IRC08:13
*** slaweq has joined #openstack-meeting08:13
*** wanghao has quit IRC08:13
*** wanghao has joined #openstack-meeting08:14
*** links has joined #openstack-meeting08:15
*** wanghao has quit IRC08:16
*** wanghao has joined #openstack-meeting08:17
*** slaweq has quit IRC08:18
*** fzdarsky_ is now known as fzdarsky08:19
*** markvoelker has quit IRC08:19
*** wanghao has quit IRC08:20
*** liyi has joined #openstack-meeting08:21
*** wanghao has joined #openstack-meeting08:21
*** rbartal has joined #openstack-meeting08:24
*** liyi has quit IRC08:25
*** wanghao has quit IRC08:26
*** wanghao has joined #openstack-meeting08:26
*** deathsparton has joined #openstack-meeting08:31
*** wanghao has quit IRC08:31
*** deathsparton has quit IRC08:31
*** deathsparton has joined #openstack-meeting08:31
*** deathsparton has quit IRC08:31
*** deathsparton has joined #openstack-meeting08:32
*** wanghao has joined #openstack-meeting08:32
*** slaweq has joined #openstack-meeting08:33
*** wanghao has quit IRC08:37
*** wanghao has joined #openstack-meeting08:37
*** phil has joined #openstack-meeting08:41
*** wanghao has quit IRC08:41
*** phil is now known as Guest5604208:41
*** wanghao has joined #openstack-meeting08:42
*** egallen has joined #openstack-meeting08:44
*** wanghao has quit IRC08:46
*** janki has joined #openstack-meeting08:46
*** wanghao has joined #openstack-meeting08:46
*** janki has quit IRC08:46
*** janki has joined #openstack-meeting08:47
*** e0ne has joined #openstack-meeting08:48
*** Alex_Staf has joined #openstack-meeting08:50
*** wanghao has quit IRC08:51
*** wanghao has joined #openstack-meeting08:51
*** oidgar has joined #openstack-meeting08:53
*** deathsparton has quit IRC08:55
*** wanghao has quit IRC08:56
*** wanghao has joined #openstack-meeting08:56
*** liyi has joined #openstack-meeting08:58
*** priteau has joined #openstack-meeting08:59
*** wanghao has quit IRC09:00
*** wanghao has joined #openstack-meeting09:01
*** bbzhao has joined #openstack-meeting09:02
*** liyi has quit IRC09:03
*** wanghao has quit IRC09:04
*** liyi has joined #openstack-meeting09:04
*** wanghao has joined #openstack-meeting09:05
*** wanghao has quit IRC09:11
*** wanghao has joined #openstack-meeting09:11
*** edmondsw has joined #openstack-meeting09:12
*** egallen has quit IRC09:16
*** wanghao has quit IRC09:16
*** wanghao has joined #openstack-meeting09:16
*** edmondsw has quit IRC09:17
*** shu-mutou is now known as shu-mutou-AWAY09:19
*** wanghao has quit IRC09:20
*** wanghao has joined #openstack-meeting09:21
*** deathsparton has joined #openstack-meeting09:22
*** caisan has joined #openstack-meeting09:23
*** dtrainor has quit IRC09:24
*** Dinesh_Bhor has quit IRC09:24
*** Dinesh_Bhor has joined #openstack-meeting09:25
*** wanghao has quit IRC09:25
*** caisan_ has quit IRC09:25
*** wanghao has joined #openstack-meeting09:26
*** egallen has joined #openstack-meeting09:26
*** ssathaye has quit IRC09:26
*** ssathaye has joined #openstack-meeting09:27
*** deathsparton has quit IRC09:28
*** wanghao has quit IRC09:29
*** wanghao has joined #openstack-meeting09:30
*** wanghao has quit IRC09:35
*** slaweq_ has joined #openstack-meeting09:35
*** egallen has quit IRC09:39
*** dtrainor has joined #openstack-meeting09:40
*** slaweq_ has quit IRC09:41
*** caisan_ has joined #openstack-meeting09:52
*** sshnaidm|afk is now known as sshnaidm09:52
*** caisan has quit IRC09:55
*** egallen has joined #openstack-meeting09:56
*** slaweq_ has joined #openstack-meeting09:58
*** Dinesh_Bhor has quit IRC09:58
*** Dinesh_Bhor has joined #openstack-meeting09:58
*** Tom-Tom has quit IRC10:00
*** Dinesh_Bhor has quit IRC10:03
*** slaweq_ has quit IRC10:03
*** erlon has joined #openstack-meeting10:04
*** tovin07__ has quit IRC10:04
*** yangyapeng has quit IRC10:04
*** yangyapeng has joined #openstack-meeting10:04
*** gongysh has quit IRC10:07
*** ssathaye has quit IRC10:07
*** gongysh has joined #openstack-meeting10:09
*** absubram has joined #openstack-meeting10:10
*** kiennt26 has quit IRC10:11
*** priteau has quit IRC10:12
*** rossella_s has quit IRC10:16
*** markvoelker has joined #openstack-meeting10:16
*** caisan has joined #openstack-meeting10:17
*** genek has quit IRC10:17
*** genek has joined #openstack-meeting10:18
*** caisan_ has quit IRC10:19
*** Tom-Tom has joined #openstack-meeting10:20
*** caisan has quit IRC10:21
*** Tom-Tom has quit IRC10:21
*** Tom-Tom has joined #openstack-meeting10:21
*** Tom-Tom has quit IRC10:24
*** tpsilva has joined #openstack-meeting10:25
*** kevinz has quit IRC10:27
*** Tom-Tom has joined #openstack-meeting10:33
*** arxcruz|rover is now known as arxcruz|off10:33
*** psachin has quit IRC10:37
*** andreas_s has quit IRC10:37
*** Tom-Tom has quit IRC10:38
*** gongysh has quit IRC10:39
*** liyi has quit IRC10:41
*** andreas_s has joined #openstack-meeting10:42
*** psachin has joined #openstack-meeting10:42
*** gcb has joined #openstack-meeting10:46
*** alexchadin has joined #openstack-meeting10:47
*** alexchadin has quit IRC10:49
*** alexchadin has joined #openstack-meeting10:49
*** markvoelker has quit IRC10:50
*** chyka has joined #openstack-meeting10:50
*** andreas_s has quit IRC10:51
*** andreas_s has joined #openstack-meeting10:53
*** chyka has quit IRC10:55
*** genek has quit IRC10:55
*** egallen has quit IRC10:59
*** edmondsw has joined #openstack-meeting11:00
*** electrofelix has joined #openstack-meeting11:01
*** andreas_s has quit IRC11:02
*** psachin has quit IRC11:04
*** sdague has joined #openstack-meeting11:05
*** edmondsw has quit IRC11:05
*** bkopilov has quit IRC11:09
*** psachin has joined #openstack-meeting11:13
*** Tom-Tom has joined #openstack-meeting11:15
*** epico has quit IRC11:15
*** andreas_s has joined #openstack-meeting11:16
*** liyi has joined #openstack-meeting11:17
*** Tom-Tom has quit IRC11:19
*** egallen has joined #openstack-meeting11:23
*** julim has quit IRC11:25
*** dbecker has joined #openstack-meeting11:25
*** julim has joined #openstack-meeting11:25
*** yamamoto_ has quit IRC11:27
*** wanghao has joined #openstack-meeting11:28
*** julim has quit IRC11:29
*** chenyb4 has joined #openstack-meeting11:35
*** caisan has joined #openstack-meeting11:43
*** egallen has quit IRC11:43
*** rossella_s has joined #openstack-meeting11:44
*** caisan has quit IRC11:47
*** lihi has quit IRC11:48
*** irenab has quit IRC11:48
*** oanson has quit IRC11:48
*** irenab has joined #openstack-meeting11:48
*** oanson has joined #openstack-meeting11:50
*** lihi has joined #openstack-meeting11:52
*** anilvenkata has quit IRC11:53
*** kevzha01 has joined #openstack-meeting12:00
*** edmondsw has joined #openstack-meeting12:03
*** sambetts|afk is now known as sambetts12:06
*** lihi has quit IRC12:10
*** oanson has quit IRC12:10
*** irenab has quit IRC12:10
*** oanson has joined #openstack-meeting12:12
*** raildo has joined #openstack-meeting12:13
*** irenab has joined #openstack-meeting12:14
*** rossella_s has quit IRC12:15
*** rossella_s has joined #openstack-meeting12:21
*** rfolco_nho has joined #openstack-meeting12:22
*** wanghao has quit IRC12:25
*** yamamoto has joined #openstack-meeting12:26
*** lpetrut has joined #openstack-meeting12:29
*** pcaruana has joined #openstack-meeting12:33
*** rossella_s has quit IRC12:35
*** rossella_s has joined #openstack-meeting12:37
*** anilvenkata has joined #openstack-meeting12:40
*** Tom-Tom has joined #openstack-meeting12:43
*** rossella_s has quit IRC12:43
*** kevzha01 has quit IRC12:44
*** kevzha01 has joined #openstack-meeting12:44
*** rossella_s has joined #openstack-meeting12:45
*** markvoelker has joined #openstack-meeting12:47
*** genek has joined #openstack-meeting12:53
*** yangyapeng has quit IRC12:56
*** strigazi has quit IRC12:56
*** weshay_PTO is now known as weshay13:01
*** elynn has joined #openstack-meeting13:02
*** rossella_s has quit IRC13:03
*** strigazi has joined #openstack-meeting13:04
*** fouadben has joined #openstack-meeting13:05
*** rossella_s has joined #openstack-meeting13:07
*** aloga has quit IRC13:09
*** dprince has joined #openstack-meeting13:09
*** aloga has joined #openstack-meeting13:10
*** hichihara has joined #openstack-meeting13:10
*** dbecker has quit IRC13:11
*** hoangcx_ has joined #openstack-meeting13:15
*** markvoelker has quit IRC13:20
*** askb has quit IRC13:21
*** rossella_s has quit IRC13:21
*** pchavva has joined #openstack-meeting13:21
*** yangyapeng has joined #openstack-meeting13:22
*** makowals has quit IRC13:22
*** sdague has quit IRC13:22
*** rossella_s has joined #openstack-meeting13:22
*** deathsparton has joined #openstack-meeting13:23
*** makowals has joined #openstack-meeting13:25
*** lpetrut_ has joined #openstack-meeting13:26
*** askb has joined #openstack-meeting13:26
*** lpetrut has quit IRC13:28
*** yamamoto_ has joined #openstack-meeting13:32
*** deathsparton has quit IRC13:32
*** deathsparton has joined #openstack-meeting13:32
*** rbowen has joined #openstack-meeting13:33
*** makowals has quit IRC13:33
*** markvoelker has joined #openstack-meeting13:33
*** yamamoto_ has quit IRC13:35
*** yamamoto has quit IRC13:35
*** makowals has joined #openstack-meeting13:35
*** kevzha01_ has joined #openstack-meeting13:39
*** caisan has joined #openstack-meeting13:39
*** rossella_s has quit IRC13:40
*** rossella_s has joined #openstack-meeting13:42
*** kevzha01 has quit IRC13:42
*** yamamoto has joined #openstack-meeting13:47
*** deathsparton has quit IRC13:49
*** deathsparton has joined #openstack-meeting13:51
*** annp has joined #openstack-meeting13:51
*** ndefigueiredo has joined #openstack-meeting13:51
*** ssathaye has joined #openstack-meeting13:52
*** yamamoto has quit IRC13:52
*** cleong has joined #openstack-meeting13:52
*** kevzha01__ has joined #openstack-meeting13:55
*** caisan has quit IRC13:55
*** rbudden has joined #openstack-meeting13:55
*** dbecker has joined #openstack-meeting13:57
*** kiennt26 has joined #openstack-meeting13:58
*** elynn has quit IRC13:58
*** esberglu has joined #openstack-meeting13:59
*** kevzha01_ has quit IRC13:59
*** jlibosva has joined #openstack-meeting13:59
*** caisan_ has joined #openstack-meeting13:59
*** kevzha01 has joined #openstack-meeting14:00
*** shintaro has joined #openstack-meeting14:00
*** eharney has joined #openstack-meeting14:00
*** mlavalle has joined #openstack-meeting14:00
jlibosva#startmeeting networking14:00
openstackMeeting started Tue Jan 16 14:00:44 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
jlibosvahi everyone14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
mlavalleo/14:00
amotokihi14:00
jlibosva#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
slaweqhi14:01
annphi14:01
jlibosvawe're approaching milestone 3, which is due Jan 2514:01
hichiharahi14:01
jlibosva#link https://releases.openstack.org/queens/schedule.html#q-314:01
mlavallenext week !14:01
jlibosvayeah, scary :) but we will manage14:01
haleybhi14:01
jlibosvaI guess we'll talk more about bugs and blueprints in a dedicated topic14:01
*** kevzha01__ has quit IRC14:02
annpjilibosva, slaweq, mlavalle, thanks for your great help on logging.14:02
jlibosvaso about a month after the q3, there will be the PTG event in Dublin and I hope a lot of people will come :)14:02
bcafarelhi14:02
slaweqI will be there :)14:02
mlavallejlibosva: you going?14:02
*** deathsparton has quit IRC14:03
jlibosvamlavalle sent a mail to ML with a link to the etherpad to collect topics we want to discuss14:03
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126055.html14:03
jlibosvamlavalle: unfortunately I can't :( because of family reasons14:03
mlavallejlibosva: will miss you :-(14:03
jlibosvabut I'll be able to join remotely if possible14:03
jlibosvaand I'll buy some Guinesses I'll be drinking in the evening :)14:03
*** chenyb4 has quit IRC14:04
jlibosvamlavalle: thanks :)14:04
amotokiremote beer party :)14:04
jlibosvaanyways - here is the link to the etherpad14:04
jlibosva#link https://etherpad.openstack.org/p/neutron-ptg-rocky14:04
annp:)14:04
jlibosvaamotoki++14:04
*** links has quit IRC14:05
jlibosvaalso related to the Rocky planning topic, there is an ongoing discussion thread about community goals for Rocky. I think it's worth reading14:05
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126090.html14:05
mlavalle++14:05
jlibosvaand the last thing I wanted to mention is that the Rocky release planning has been merged a few days ago14:05
jlibosva#link https://review.openstack.org/#/c/528772/14:05
*** reedip_ has joined #openstack-meeting14:06
jlibosvathere was a discussion about making development cycles longer14:06
reedip_o/14:06
jlibosvabut conclusion is that Rocky will still be a 6 months long14:06
*** hagridaaron has joined #openstack-meeting14:06
jlibosvathat's all from my side14:06
jlibosvaanybody has anything to announce?14:06
mlavallenope, you were pretty thorough, jlibosva . thanks :-)14:07
*** rossella_s has quit IRC14:07
*** deathsparton has joined #openstack-meeting14:07
jlibosvacool, let's jump to blueprints then14:07
jlibosva#topic Blueprints14:07
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:07
jlibosva#link https://launchpad.net/neutron/+milestone/queens-314:07
mlavalleOn the nova port bindings information for live migration I made great progress up until Tuesday of last week14:09
mlavalleThen I slowed down a bit14:09
mlavalleI will continuw pushing this week. But it looks tight14:09
annpjlibosva, mlavalle, slaweq: thanks for your help on logging. There are 2 remmaining patch related to fullstack and tempest.14:09
*** rossella_s has joined #openstack-meeting14:10
jlibosvamlavalle: do you need any help?14:10
mlavalleannp: but the main funtionality is in, right?14:10
jlibosvait is14:10
mlavallecool14:10
mlavallejlibosva: I can use some help14:11
jlibosvaannp: perhaps we could split the tempest patch into scenario and api as the api part is voting14:11
jlibosvait would be great to get the api part in first14:11
jlibosvaI just think the split could speed up the process :)14:11
jlibosvamlavalle: ok, we can sync after the meeting14:11
mlavallejlibosva: :-)14:11
annpjlibosva, thanks, I will do that as your suggest.14:11
*** psachin has quit IRC14:12
annpthat's all from me14:12
mlavallehttps://blueprints.launchpad.net/neutron/+spec/floating-ip-rate-limit14:12
mlavalleis mostly in14:12
mlavallethe remaining pieces are two:14:13
amotokiIIRC OSC patch landed. the remaining one is doc?14:13
mlavalledocs, which last time I looked wasn't far14:13
mlavalleand an api tempest test14:13
mlavalleamotoki: thanks for your help with the OSC patch :-)14:14
amotokino problem14:14
amotokiregarding policy-in-code, it cannot land in Queens as it needs neutron-lib support.14:14
mlavallewhat kind of support?14:15
amotokiI was requested from the assignee to investigate the detail but I failed due to my busy time on internal affairs.14:15
*** fnaval has joined #openstack-meeting14:15
*** rossella_s has quit IRC14:15
amotokineutron stadium projects need to inform their in-code policies to the neutron API layer14:15
*** deathsparton has quit IRC14:16
*** coolsvap has quit IRC14:16
mlavalleok14:16
amotokiI posted neutron-lib patch but it turned out the policy loading code is now spread into neutorn-lib (context) and neutron main tree.14:16
mlavallethanks for the update14:17
*** yamamoto has joined #openstack-meeting14:17
*** rossella_s has joined #openstack-meeting14:17
mlavalleas far as FWaaS V2, I don't have the latest status but I think it's done14:17
mlavallexgerman_: you around?14:17
jlibosvathere appears to be 3 patches still on review: https://review.openstack.org/#/q/topic:bp/fwaas-api-2+(status:open)14:18
xgerman_ O/14:18
annphi xgerman_\14:18
mlavallexgerman_: we wanted to see the status of FWaaS v2.014:19
xgerman_We are14:19
mlavallewill it get finished by Q-3?14:19
*** andreas_s has quit IRC14:19
xgerman_Yes14:19
*** caisan_ has quit IRC14:19
annpxgerman_ +114:19
*** andreas_s has joined #openstack-meeting14:19
*** ndefigueiredo has quit IRC14:19
*** absubram has quit IRC14:19
xgerman_We have enough but like some more patches to get in…14:19
amotokinice14:20
amotokiif they are not critical to FWaaS v2.0 we can split them into separate blueprint(s)14:20
*** fnaval has quit IRC14:20
*** caisan has joined #openstack-meeting14:20
hichiharaI guess that FWaas v2 has L2 port in milestones but it seems abandoned https://review.openstack.org/#/c/361071/14:20
mlavallexgerman_: so at this point, can we consider FWaaS v2 done?14:20
xgerman_We will do so if they slip Q-314:20
*** cdub has joined #openstack-meeting14:21
xgerman_Yeah14:21
mlavallecool!14:21
amotokixgerman_: what about hichihara's point?14:21
*** caisan has quit IRC14:21
annphichihara, the patch regarding to iptables based implementation.14:21
*** caisan has joined #openstack-meeting14:21
*** yamamoto has quit IRC14:22
xgerman_Yes14:22
xgerman_We are if’s14:22
hichiharaI understand. It's not in v2 scope, right?14:22
xgerman_No, it’s all OVS14:22
*** reedip_ has quit IRC14:22
xgerman_As suggested in Atlanta14:22
hichiharaAh, I got it.14:22
annpxgerman_, yeah.14:22
amotokihmm... isn't ovs support required to make fwaas v2 work?14:23
amotokiI am confused14:23
xgerman_Yes14:23
mlavallexgerman_: congrats to you and all the fwaas team !14:23
xgerman_We are 100% OVS14:23
xgerman_Thanks14:23
annpmlavalle, thanks14:23
amotokiah.... I got it. It is iptables-based impl. ovs-native support has been implemented.14:24
xgerman_+114:24
hichiharaxgerman_: thanks14:24
mlavalleannp: you've been working hard this cycle :-)14:25
annpmlavalle, :)14:25
hoangcx_mlavalle: indeed :)14:25
xgerman_+114:25
jlibosvaannp++14:25
hichiharaannp++14:25
annpfolks++14:26
annp:)14:26
hichiharaHow about other bp?14:26
hichiharaamotoki: https://blueprints.launchpad.net/neutron/+spec/neutron-in-tree-api-ref ?14:26
*** andreas_s has quit IRC14:26
*** andreas_s has joined #openstack-meeting14:27
jlibosvamlavalle: I have a question regarding blueprints - if a bp misses q3, does it automatically flip to Rocky or driver team discusses it first and treats it as a new bp?14:27
jlibosva"new" in terms of planning14:27
mlavalleI think we are going to flip it to Rocky14:27
jlibosvaok, thanks14:27
amotokire: neutron-in-tree-api-ref, I am thinking to convert the remaining todos into bugs and close it.14:27
xgerman_Thanks14:27
mlavalleexpecially if there is sigificant progress achieved14:27
amotokisomehow I dropped it from my todo list14:28
hichiharaamotoki: +114:28
amotokimy busy time on internal affairs got over today, so I can promise to clean them up.14:28
mlavallethanks amotoki :-)14:28
hichiharacool14:28
amotokii don't know the status of https://blueprints.launchpad.net/neutron/+spec/subnet-onboard14:29
amotokireedip: around?14:29
jlibosvait has this patch attached that's been untouched for a while: https://review.openstack.org/#/c/348080/14:30
*** yamahata has quit IRC14:30
*** mjturek has joined #openstack-meeting14:30
mlavalleyeah, doesn't look very promising for q-314:31
jlibosvaI have a feeling it won't meet the q3 :)14:31
amotokiyeah, indeed14:31
amotokire versioned object, i think we can check the status to ihar in the next week meeting14:32
*** ndefigueiredo has joined #openstack-meeting14:33
jlibosvasounds good14:33
jlibosvaanything else BPs related?14:33
*** david-lyle has quit IRC14:33
jlibosvalet's move on then14:33
jlibosva#topic Bugs14:33
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:33
jlibosvathe bug deputy was hichihara14:34
hichiharaI was bug deputy last week14:34
jlibosvahe sent an email with report14:34
hichiharaI reported some bugs in ML http://lists.openstack.org/pipermail/openstack-dev/2018-January/126206.html14:34
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126206.html14:34
jlibosvaah, thanks :)14:35
hichiharajlibosva: thanks14:35
*** shintaro has quit IRC14:35
*** alisanhaji has joined #openstack-meeting14:35
hichiharaThree high priority bugs14:35
hichiharahttps://bugs.launchpad.net/neutron/+bug/174195414:35
openstackLaunchpad bug 1741954 in neutron "create_and_list_trunk_subports rally scenario failed with timeouts" [High,In progress] - Assigned to Armando Migliaccio (armando-migliaccio)14:35
hichiharahttps://bugs.launchpad.net/neutron/+bug/174240114:35
openstackLaunchpad bug 1742401 in neutron "Fullstack tests neutron.tests.fullstack.test_securitygroup.TestSecurityGroupsSameNetwork fails often" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)14:35
hichiharahttps://bugs.launchpad.net/neutron/+bug/174188914:35
openstackLaunchpad bug 1741889 in neutron "functional: DbAddCommand sometimes times out after 10 seconds" [High,New]14:35
*** archit has joined #openstack-meeting14:36
hichiharaThere was no critical bug.14:36
jlibosvathe first one already has a fix that got almost merge14:36
jlibosvaI think it only failed because of conflict14:36
jlibosvaand the last two seem like caused by the same thing14:37
jlibosvaoh, sorry, ignore me :)14:37
jlibosvaI clicked on a wrong link14:37
hichiharaLast one is no assignee14:38
jlibosvamaybe otherwiseguy can help us with the last one 174188914:38
hichiharagood14:39
slaweqabout 1742401 I didn't have too much time to check it yet14:39
mlavalleit was mentioned during last week's CI meeting14:39
*** hongbin has joined #openstack-meeting14:39
slaweqbut I will work on it14:39
jlibosvaworth to mention that sometimes the last one causes functional job to get stuck and then it times out on a global timeout14:39
jlibosvaslaweq: ok, thanks :)14:40
jlibosvaI'll talk to otherwiseguy14:40
mlavallethanks jlibosva14:40
jlibosvagaryk is the bug deputy for this week14:40
jlibosvaI saw an email that he'd like to get a backup on Friday14:41
hichiharamlavalle: Could you check a bug https://bugs.launchpad.net/neutron/+bug/1742093 ? It's about vm-without-l3-address.14:41
openstackLaunchpad bug 1742093 in neutron "ip_allocation attribute is not accessible over REST requests" [Wishlist,Confirmed]14:41
amotokijlibosva: i just sent a mail14:41
jlibosvaamotoki: cool, thanks :)14:41
amotokii will cover from this friday14:41
mlavallehichihara: will do14:41
mlavalleamotoki: thanks14:42
hichiharamlavalle: Thanks :)14:42
jlibosvawe're quite short on time so let's move on14:42
jlibosva#topic Starter Approved RFEs14:42
*** openstack changes topic to "Starter Approved RFEs (Meeting topic: networking)"14:42
jlibosvawe still have the one rfe there so please consider it, probably for Rocky :)14:43
jlibosva#link https://bugs.launchpad.net/neutron/+bug/165393214:43
openstackLaunchpad bug 1653932 in neutron "[rfe] network router:external field not exported" [Wishlist,Triaged]14:43
jlibosva#topic Docs14:43
*** openstack changes topic to "Docs (Meeting topic: networking)"14:43
jlibosvaI don't see boden around, amotoki do you want to give any updates?14:43
amotokinothing from me on docs14:43
jlibosvaok, let's move on unless anybody has anything docs related14:43
jlibosva#topic Transition to OSC14:44
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:44
jlibosvaamotoki: hello again :)14:44
jlibosvaany updates here?14:44
amotokiOSC VPNaaS integration has been merged :)14:44
jlibosva\o/14:44
amotokiin addition, several patches are close to merge.14:44
amotokiit is nice if some of you look at them https://review.openstack.org/#/q/status:open+project:openstack/python-neutronclient+branch:master14:45
amotokiwith +2 patch14:45
amotokithat's all from me.14:46
mlavalleamotoki: I will take a look14:46
*** VW has joined #openstack-meeting14:46
amotokiis there anything else to raise?14:46
jlibosvaamotoki: thanks for updates, I think we're good to move on14:47
amotokislaweq: sorry for my late. I will check you OSC patch https://review.openstack.org/51540114:47
slaweqamotoki: thx14:47
mlavallehoangcx_: so the VPNaaS patch was taken care of while I was sleeping14:47
slaweqno problem14:47
hoangcx_mlavalle: Yeah, yamamoto took care14:47
mlavallehe probably read our conversation of last nigh (my time)14:48
jlibosvaok, we have 10 minutes left14:49
*** kevzha01 has quit IRC14:49
jlibosvaanything else to osc related?14:50
jlibosvamoving on14:50
jlibosva#topic Neutron-lib14:50
*** openstack changes topic to "Neutron-lib (Meeting topic: networking)"14:50
jlibosvaas boden is around, does anybody have any updates or anything related to the lib?14:50
mlavalleI have something to say, hang on a sec14:51
*** awaugama has joined #openstack-meeting14:51
mlavalleboden has a group of neutron-lib patches classified as requiring neutron core input:14:52
mlavalle#link https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%2214:52
mlavalleI took a stab at them over the past few days14:52
*** caisan has quit IRC14:52
*** felipemonteiro has joined #openstack-meeting14:53
mlavallebut if other cores have time, please give feedback14:53
* mlavalle doesn't want to lead boden off the rails alone :-)14:53
hichiharawill do14:53
mlavallethat's all I have on this regard14:54
jlibosvamlavalle: thanks :)14:54
*** felipemonteiro_ has joined #openstack-meeting14:54
amotokinote that neutron-lib freeze is this week14:55
*** caisan has joined #openstack-meeting14:55
amotokijust FYI14:55
jlibosvaamotoki: do you know exact date?14:55
jlibosvaor day :)14:55
mlavalleamotoki: we released last week14:55
amotokijlibosva: i don't know the exact day but it is usually Thursday14:56
mlavalleand I don't think we need another one14:56
jlibosvaaha, ok, thanks14:56
amotokimlavalle: yes, I agree14:56
mlavallehowever, point take amotoki and I will check again with boden14:56
*** deathsparton has joined #openstack-meeting14:56
*** deathsparton has quit IRC14:57
*** deathsparton has joined #openstack-meeting14:57
jlibosvaI don't see any topic in the on demand agenda section on the wiki page14:58
jlibosvaand we're running out of time14:58
*** felipemonteiro has quit IRC14:58
jlibosvaso maybe if there is something needed to be discussed, we could do it in the #openstack-neutron channel?14:58
jlibosva#topic Free discussion14:58
*** openstack changes topic to "Free discussion (Meeting topic: networking)"14:58
mlavalleamotoki: do we release neutron python client this week?14:58
amotokimlavalle: I am okay with either, but it seems better to release it14:59
amotokiI can prepare it14:59
mlavalleamotoki: ok, let's coordinate with armax this week14:59
amotokimlavalle: sure14:59
mlavalle:-)14:59
*** rossella_s has quit IRC14:59
mlavallethat's all14:59
jlibosvaaaaand we're out of time :) thanks everybody for coming15:00
jlibosva#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Tue Jan 16 15:00:07 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-01-16-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-01-16-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-01-16-14.00.log.html15:00
mlavalleo/15:00
*** hichihara has quit IRC15:00
slaweqthx15:00
annpsee you15:00
amotokithanks bye15:00
*** annp has quit IRC15:00
slaweq#startmeeting neutron_qos15:00
openstackMeeting started Tue Jan 16 15:00:55 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
openstackThe meeting name has been set to 'neutron_qos'15:01
slaweqhi15:01
alisanhajiHi15:01
fouadbenHi all15:01
*** hoangcx_ has quit IRC15:01
slaweqplease give me one minute and I will be back15:01
mlavalleo/15:02
*** rossella_s has joined #openstack-meeting15:03
*** yamamoto has joined #openstack-meeting15:03
*** yamamoto has quit IRC15:03
*** armax has joined #openstack-meeting15:04
slaweqok, I'm back15:04
slaweqlet's start15:04
slaweq#topic RFEs15:04
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:04
*** felipemonteiro_ has quit IRC15:04
*** jlibosva has left #openstack-meeting15:05
slaweqwe have still couple approved RFEs15:05
slaweq#link https://bugs.launchpad.net/neutron/+bug/156096315:05
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress]15:05
slaweqthere is nothing new with this one15:05
slaweqnot assigned to anyone15:05
slaweqso if anyone would be interested in doing that, would be great :)15:06
slaweqnext one #link https://bugs.launchpad.net/neutron/+bug/157898915:06
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel)15:06
slaweqit's waiting for next cycle as we decided some time ago with mlavalle15:06
mlavallecorrect15:07
slaweqbut ralonsoh did some patches related to it15:07
slaweqand he pushed placement api client to neutron-lib15:07
*** alexchadin has quit IRC15:07
slaweqone patch is already merged:  #link https://review.openstack.org/#/c/511936/15:07
*** deathsparton has quit IRC15:07
slaweqand second is in review: #link https://review.openstack.org/#/c/512396/15:07
slaweqso please review it if You will have some time15:08
slaweqnext is almost done: #link https://bugs.launchpad.net/neutron/+bug/159661115:08
openstackLaunchpad bug 1596611 in neutron "[RFE] Create L3 IPs with qos (rate limit)" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:08
slaweqonly docs and tempest tests are still in review15:08
slaweqtempest tests are marked as WIP so I didn't review it yet15:09
mlavalleI will take a look at the tempest tests15:09
slaweqdocs are almost ready IMO15:09
slaweqok, thx mlavalle15:09
slaweqnext is #link https://bugs.launchpad.net/neutron/+bug/169295115:10
openstackLaunchpad bug 1692951 in neutron "[RFE] DSCP mark on the outer header" [Wishlist,In progress] - Assigned to Ali Sanhaji (ali-sanhaji)15:10
mlavallethat is my impresion also15:10
alisanhajiI just rebased for this one15:10
alisanhajiafter raryk comment15:10
alisanhajigaryk15:10
slaweqgreat that it's not only for me :)15:11
slaweqalisanhaji: yes, thx a lot15:11
alisanhajino need to :)15:11
slaweqmlavalle: please review https://review.openstack.org/#/c/501267/ if You will have some time15:12
slaweqI will check it today or tomorrow also15:12
slaweqI hope it can be merged finally soon :)15:12
*** yamamoto has joined #openstack-meeting15:12
alisanhajiyes me too15:12
*** deathsparton has joined #openstack-meeting15:13
slaweqalisanhaji: I saw that garyk gave +1 already :)15:13
* mlavalle will take a loom also15:13
alisanhajiyes just saw it too15:13
slaweqok, and the last (but not least) one is #link https://bugs.launchpad.net/neutron/+bug/172757815:14
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:14
slaweqthere is specs proposed for it already: #link https://review.openstack.org/#/c/531074/15:14
slaweqmlavalle: again, please add it to Your review list :)15:14
mlavallethis RFE was approved last drivers meeting15:15
mlavalleso the spec is timely15:15
slaweq:)15:16
mlavallethere was some doubts from yamamoto about how that would be implemented15:16
mlavalleso if you can give some guidance, slaweq, it would be very usful15:16
mlavalleI mean from your QoS perspective15:17
slaweqfrom QoS point of view it looks like it can be some beginning of classful bw limits15:17
slaweqas I understand it, there will be rules based on src/dest IP addresses added in router's namespace15:17
mlavallecool, please provide that guidance in the spec15:17
*** yamamoto has quit IRC15:17
slaweqyes, I was already reviewing it once or twice15:17
mlavalle:-)15:17
slaweqI will check it also this week15:18
slaweqok, so that was all RFEs which I had for today15:18
slaweq#topic Bugs15:19
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:19
slaweqfortunately there is not too many bugs reported for QoS :)15:19
slaweqfirst one is #link https://bugs.launchpad.net/neutron/+bug/166210915:19
openstackLaunchpad bug 1662109 in neutron "tempest scenario test_qos fails intermittently" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)15:19
slaweqI still can't check if this is still an issue in gate - I didn't found it in my tests and logstash query for it is still not working IMO15:20
*** liyi has quit IRC15:20
slaweqmlavalle: we talked about that some time ago :)15:20
slaweqdo You remember?15:20
mlavalleyes15:21
slaweqcan we maybe check it this week once again?15:21
mlavalleyes15:21
slaweqok, thx15:21
slaweqI will ping You later15:21
slaweqnext one: #link https://bugs.launchpad.net/neutron/+bug/173789215:22
openstackLaunchpad bug 1737892 in neutron "Fullstack test test_qos.TestBwLimitQoSOvs.test_bw_limit_qos_port_removed failing many times" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)15:22
slaweqpatch for this one is almost merged15:22
slaweqin fact it is not an issue in QoS code but in ovs agent15:23
slaweqI will probably add also similar fullstack test for DSCP marking rule as such rule can be also not removed when port is removed from bridge15:23
slaweqah, and patch related to this bug is on #link https://review.openstack.org/#/c/533318/15:24
slaweqany questions/suggestions so far?15:25
*** caisan has quit IRC15:26
slaweqmlavalle: alisanhaji: still here? :)15:27
*** deathsparton has quit IRC15:27
mlavalleyes15:27
alisanhajiyes15:27
fouadbeny15:27
slaweqshould I continue?15:27
mlavalleplease go ahead15:27
*** rbartal has quit IRC15:27
slaweqok15:27
alisanhajiI am following15:27
slaweqso if there is no questions then next bug15:28
slaweq#link https://bugs.launchpad.net/neutron/+bug/173679215:28
openstackLaunchpad bug 1736792 in neutron "DSCP marking QOS policy applied to port not properly updating OVS flow table" [Medium,New]15:28
slaweqfor me it is duplicate of https://bugs.launchpad.net/neutron/+bug/173941115:28
openstackLaunchpad bug 1739411 in neutron "QoS DSCP mark disappear stable/ocata" [Low,Confirmed] - Assigned to Pavlukhin Max (mpavlukhin)15:28
slaweqand I would mark if as duplicate15:28
slaweqmlavalle: do You agree?15:28
mlavallemhhh, hang on....15:28
slaweqsure15:28
mlavalleyes, I agree15:29
*** links has joined #openstack-meeting15:29
slaweqok, so I will close it after meeting15:29
slaweqso about https://bugs.launchpad.net/neutron/+bug/173941115:30
openstackLaunchpad bug 1739411 in neutron "QoS DSCP mark disappear stable/ocata" [Low,Confirmed] - Assigned to Pavlukhin Max (mpavlukhin)15:30
slaweqthere is already proposed patch:  #link https://review.openstack.org/#/c/529315/15:30
slaweqbut there is no response from author for it15:30
*** liyi has joined #openstack-meeting15:30
*** hagridaaron has quit IRC15:30
slaweqI will try to catch him and ask if he can continue this work15:30
slaweqor I will handle it15:30
slaweq#action slaweq check progress on #link https://review.openstack.org/#/c/529315/15:31
slaweqnext is #link https://bugs.launchpad.net/neutron/+bug/172472915:31
openstackLaunchpad bug 1724729 in neutron "ovs-lib not support qos type egress-policer for ovs-dpdk" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)15:31
slaweqand patch is waiting for review:  #link https://review.openstack.org/#/c/513398/15:32
slaweqmlavalle: thx for Your review last week15:32
*** hagridaaron has joined #openstack-meeting15:32
slaweqI changed units according to Your comments as it's in fact different for dpdk ports :)15:32
*** esberglu has quit IRC15:32
mlavalleyeah, I was surprised by that15:33
slaweqme too15:33
mlavalleI don't know why they decided to do it that way15:33
slaweqme neighter15:33
mlavalleI will take a look again today15:33
slaweqand I was double checking that it's differently for dpdk ports and for "normal" ports15:33
slaweqthx15:34
mlavalleon the other hand, their doc is pretty good15:34
slaweqyes, everything is described there quite clearly15:34
mlavalleor blog entry or whatever it is15:34
*** liyi has quit IRC15:35
slaweqnext one is our "old friend": #link https://bugs.launchpad.net/neutron/+bug/163918615:35
openstackLaunchpad bug 1639186 in neutron "qos max bandwidth rules not working for neutron trunk ports" [Low,Confirmed]15:35
slaweqthere is no volunteer to work on it still15:35
slaweqso nothing new15:35
*** rossella_s has quit IRC15:36
slaweqand the last one on my list for today is #link https://bugs.launchpad.net/neutron/+bug/173285215:36
openstackLaunchpad bug 1732852 in neutron "neutron don't support Router gateway rate limit " [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)15:36
slaweqthere is also nothing new here15:36
slaweqI don't have time for it still :/15:37
*** hemna_ has joined #openstack-meeting15:37
slaweqand as it is documented how it should be configured to make it working I think it's not high priority now15:38
mlavalleok15:38
slaweqso that are all bugs which I have for You today15:39
slaweqany questions?15:39
mlavallenone from me15:39
alisanhajino questions15:39
slaweqso last topic in agenda is15:40
slaweq#topic Open Discussion15:40
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:40
slaweqI don't have anything here15:40
fouadbenI would like to discuss a new spec that I proposed with alisanhaji for congestion reaction in overlay networks using neutron qos policy. #link https://review.openstack.org/#/c/534213/215:40
*** deathsparton has joined #openstack-meeting15:40
fouadbenA previous version was proposed by reedip to activate ECN in openstack network and routers. https://review.openstack.org/#/c/445762/15:41
*** bobh has joined #openstack-meeting15:41
*** mjturek has quit IRC15:42
slaweqso it is continuation of reedip's work?15:42
fouadbenWe can see that.15:42
fouadbenSo, this one proposes new qos policy that handles the congestion in all phases, starting by ensuring  ECN activation because it’s essential to congestion detection, going through the congestion calculation. Finally we react to the congestion if it exceeded the defined threshold using bandwidth limit qos rule.15:42
*** deathsparton has quit IRC15:43
slaweqso You want to change bandwidth limit rules dynamically when it is necessary?15:44
fouadbenYes, we use the bandwidth limit rule dynamically en ensure that the source of congestion reduced its traffic, then we release it if the congestion goes below15:45
slaweqso source VM will don't need to know about this ECN and don't need to support it15:46
slaweqas it will be "supported" by Neutron's QoS rules, right?15:46
slaweqfouadben: I will read this spec this week and will left comments there15:47
fouadbenThis solution enfore the ECN activation what ever the VM OS configuration. Everything starts out of the VM.15:47
fouadbenThanks slaweq15:47
slaweqok15:47
alisanhajislaweq: yes that's it, the VM doesn't need to know about ECN15:47
slaweqthat is good :)15:48
*** esberglu has joined #openstack-meeting15:48
slaweqI think that You will also need to fill RFE bug about that15:48
slaweqmlavalle: right?15:48
mlavalleyes, I think so15:48
fouadbenAlready pub https://bugs.launchpad.net/neutron/+bug/170846015:48
openstackLaunchpad bug 1708460 in neutron " [RFE] Reaction to network congestion for qos" [Wishlist,New] - Assigned to Fouad Benamrane (ftreqah)15:48
*** david-lyle has joined #openstack-meeting15:49
mlavalleok, I will look at it soon15:49
slaweqah, I didn't saw it linked as related-bug in commit message in specs so I thought it's not done yet15:49
slaweqthx mlavalle15:49
slaweqand thx fouadben and alisanhaji for this proposal :)15:49
fouadbeny welcome15:50
slaweqanything else?15:50
alisanhajinone from me15:50
slaweqif not we can finish earlier today :)15:50
fouadbenno15:50
*** links has quit IRC15:51
slaweqmlavalle: do You have anything else to add?15:51
mlavallenope15:51
slaweqok, so thanks everyone15:51
mlavallethanks for chairing this meeting, slaweq :-)15:51
slaweq#endmeeting15:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:51
openstackMeeting ended Tue Jan 16 15:51:49 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-01-16-15.00.html15:51
alisanhajiYes thanks slaweq !15:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-01-16-15.00.txt15:51
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-01-16-15.00.log.html15:51
*** fnaval has joined #openstack-meeting15:52
*** jamesmcarthur has joined #openstack-meeting15:52
*** fnaval has quit IRC15:52
*** fnaval has joined #openstack-meeting15:53
*** jlibosva has joined #openstack-meeting15:53
*** fnaval has quit IRC15:54
*** Alex_Staf has quit IRC15:57
*** anilvenkata has quit IRC15:58
*** yamamoto has joined #openstack-meeting15:58
*** fnaval has joined #openstack-meeting15:58
*** ihrachys has joined #openstack-meeting16:01
ihrachys#startmeeting neutron_ci16:01
openstackMeeting started Tue Jan 16 16:01:18 2018 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:01
openstackThe meeting name has been set to 'neutron_ci'16:01
mlavalleo/16:01
*** yamamoto has quit IRC16:01
slaweqhi16:01
*** ndefigueiredo has quit IRC16:01
*** yamamoto has joined #openstack-meeting16:01
*** yamamoto has quit IRC16:01
ihrachysheya16:01
ihrachys#topic Actions from prev meeting16:02
*** openstack changes topic to "Actions from prev meeting (Meeting topic: neutron_ci)"16:02
haleybhi16:02
*** lamt` has joined #openstack-meeting16:02
ihrachys(I think the first one that was on me since it's overridden by another AI)16:02
ihrachysnext is "mlavalle to follow up with stadium projects on switching to new tempest repo"16:02
mlavalleI did follow up with vpnaas and midonet16:02
mlavallethey are on board with the move16:03
*** gman-tx has joined #openstack-meeting16:03
ihrachyseh wait :)16:03
ihrachysare we talking the same thing?16:03
*** Tom-Tom_ has joined #openstack-meeting16:03
mlavalleI think the patches from the gentleman leading this have to be updated16:03
ihrachysoh ok we DO talk the same thing16:03
*** marios has quit IRC16:03
ihrachysI figured the AI was not worded unambiguously :)16:04
mlavalleLOL16:04
jlibosvao/16:04
mlavalleI made sure yamamoto and hoangcx keep and eye on the respective patches16:04
ihrachysfor the record, we are talking about switching imports in other stadium repos to neutron-tempest-plugin, then killing neutron in-tree remaining tempest bits from neutron.tests.tempest16:04
mlavallecorrect16:04
ihrachysmlavalle, keep an eye or follow up / update?16:04
ihrachysI am not sure chandankumar is going to follow up on those patches16:05
*** makowals has quit IRC16:05
mlavalleok, do they have to continue with the respective patches16:05
mlavalle?16:05
ihrachysI was thinking that yes, they would take over / drive to merge16:05
mlavalleok, I will talk to them again tonight16:06
ihrachysfor what I understand, chandankumar spearheads several initiatives and projects and may not have equal time for all patches16:06
ihrachyspl great16:06
ihrachys*ok great16:06
*** Tom-Tom has quit IRC16:06
*** kiennt26 has quit IRC16:06
mlavallecool, since I saw the chandankumar was pushing the patches I thought he was going to continue with them16:07
ihrachys#action mlavalle to follow up with stadium projects on taking over / merge patches to switch imports to new tempest repo16:07
ihrachysoh if he was active recently that's another story. I haven't seen it, probably happened the latest week.16:07
mlavallewill do16:07
ihrachysok next was "ihrachys to report bug for dvr scenario job timeouts and try concurrency increase"16:07
*** bollig has quit IRC16:07
*** yamahata has joined #openstack-meeting16:08
mlavallenevermind. I'll have the stadium guys take over16:08
*** oidgar has quit IRC16:08
*** bollig has joined #openstack-meeting16:08
*** bkopilov has joined #openstack-meeting16:08
ihrachyswe merged https://review.openstack.org/#/c/532261/ the bug report was https://launchpad.net/bugs/174220016:08
openstackLaunchpad bug 1742200 in neutron "dvr scenario job fails with timeouts" [High,Fix released]16:08
ihrachyswe will revisit whether it helped in grafana section16:08
ihrachys"ihrachys to report bug for mtu scenario not executed for linuxbridge job"16:08
ihrachysI reported https://bugs.launchpad.net/neutron/+bug/174219716:09
openstackLaunchpad bug 1742197 in neutron "linuxbridge scenario job doesn't execute NetworkMtuBaseTest" [Medium,Confirmed] - Assigned to Dongcan Ye (hellochosen)16:09
*** marios has joined #openstack-meeting16:09
ihrachysand there is already a fix in review for that: https://review.openstack.org/#/c/532406/ though it relies on plugin to support mtu-writable extension16:09
ihrachysI also tried https://review.openstack.org/#/c/532259/ but figured that vlan type driver is not working in gate16:10
ihrachysso for linuxbridge we are left with flat and vxlan to pick from16:10
ihrachys(well, I *assume* flat works, I haven't checked)16:10
*** gman-tx has left #openstack-meeting16:10
*** gouthamr has joined #openstack-meeting16:10
ihrachysin light of this, I guess mtu-writable approach is the best16:11
ihrachysok, the last item was "slaweq to take over sec group failure in fullstack (report bug / triage / fix)"16:11
ihrachysthat was in regards to failure as in http://logs.openstack.org/43/529143/3/check/neutron-fullstack/d031a6b/logs/testr_results.html.gz16:11
slaweqI only reported it on launchpad: https://bugs.launchpad.net/neutron/+bug/174240116:11
openstackLaunchpad bug 1742401 in neutron "Fullstack tests neutron.tests.fullstack.test_securitygroup.TestSecurityGroupsSameNetwork fails often" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:11
slaweqI didn't had time to work on it16:12
slaweqbecause I was fixing https://bugs.launchpad.net/neutron/+bug/173789216:12
openstackLaunchpad bug 1737892 in neutron "Fullstack test test_qos.TestBwLimitQoSOvs.test_bw_limit_qos_port_removed failing many times" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)16:12
slaweqI hope I will work on this issue with SG this week16:12
ihrachysgreat! thanks for taking it.16:12
ihrachyswe'll have a look at fullstack patches after briefly checking grafana16:13
ihrachys#topic Grafana16:13
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:13
ihrachyshttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:13
ihrachysreminder that we switched to non-legacy job names on the board where applicable: https://review.openstack.org/#/c/532632/16:13
ihrachyswe need to check whether all boards still work as intended16:14
*** mjturek has joined #openstack-meeting16:14
*** deathsparton has joined #openstack-meeting16:14
ihrachysthere are several boards there right now (coverage, grenade) that don't have any datapoints16:14
ihrachysall for gate queue16:14
ihrachysI suspect it's because no failure hits happened for those jobs16:14
haleybthat's usually the reason16:15
ihrachysyeah, I think that's a reasonable explanation for coverage16:15
ihrachysfor grenade, it wouldn't be the case but the update for the dashboard is quite fresh16:15
ihrachysI mean, tempest / grenade fail from time to time16:16
ihrachysso long term we should expect some failing data points\16:16
ihrachysso I guess let's give it a week or two before paniching16:16
ihrachys*panicking16:16
ihrachysin the meantime, we have check queue for grenade jobs so we can still spot issues16:16
*** anilvenkata has joined #openstack-meeting16:17
*** e0ne has quit IRC16:18
ihrachyslooking at other dashboards, fullstack is steady 80%, scenario dvr is 30% (I think we had it like that before)16:18
ihrachyslinuxbridge scenario spiked to 100%16:18
ihrachysand I found out it's a recent logapi service plugin patch that broke it16:19
ihrachysbecause we now enable log l2 extension for linuxbridge despite it not being compatible with the agent16:19
ihrachysI have a fix here: https://review.openstack.org/#/c/533799/16:19
ihrachysslaweq, it now has ci results so maybe you can bump vote16:19
slaweqihrachys: I just +W16:20
ihrachysthere is still more work for the bug, but I will let others to fix that16:20
ihrachysI left the bug opened16:20
ihrachysslaweq, thanks16:20
ihrachysI also notice there is a spike in failure rate for functional16:21
ihrachysboth check and gate queues16:21
*** deathsparton has quit IRC16:21
ihrachys30% in gate, 40% in check queues16:21
ihrachysanyone aware of what's that about?16:21
jlibosvaperhaps the AddBridge issue?16:22
slaweqisn't it related to this issue with connections to ovs?16:22
jlibosvaI saw a functional test stuck today again16:22
jlibosvabut I haven't check how often it happens16:22
ihrachysjlibosva, you mean https://bugs.launchpad.net/neutron/+bug/1741889 ?16:22
openstackLaunchpad bug 1741889 in neutron "functional: DbAddCommand sometimes times out after 10 seconds" [High,New]16:22
jlibosvayep16:22
ihrachysslaweq, issue with connections? what's that?16:22
slaweqthis one which You just posted16:23
*** vabada has joined #openstack-meeting16:23
slaweqsorry16:23
jlibosvaI promised today I'll ask otherwiseguy for help, I haven't got to it yet16:23
ihrachysslaweq, oh I see you referred to ovs log messages there with connection failures16:23
slaweqyes16:23
slaweqbut it's this one, right?16:23
*** rossella_s has joined #openstack-meeting16:23
slaweqor I mixed something?16:23
ihrachysjlibosva, that would be nice to get otherwiseguy on it because it's really painful and we don't seem to have a path forward. there was another bug that he was going to look into.16:24
ihrachyshttps://bugs.launchpad.net/neutron/+bug/168707416:24
openstackLaunchpad bug 1687074 in neutron "Sometimes ovsdb fails with "tcp:127.0.0.1:6640: error parsing stream"" [High,Confirmed]16:24
ihrachysI think we usually spot those stream errors in tests that fail with retries16:24
ihrachysso can be related16:24
ihrachysslaweq, yeah I think it's this one16:24
slaweq:)16:24
slaweqthx for confirmation16:24
ihrachysI think there was a patch for stream issue somewhere..16:25
ihrachyslooking16:25
*** links has joined #openstack-meeting16:25
ihrachysok it was not really a fix, just debug statements: https://review.openstack.org/#/c/525775/4/neutron/agent/common/ovs_lib.py16:25
ihrachysI think Terry triggered a failure with the patch and got ": RuntimeError: Port nonexistantport does not exist" from ovs socket.16:26
ihrachyswhich is very weird16:26
ihrachysit's definitely neutron error16:26
ihrachysso how is it possible it results in ovsdb socket16:26
*** absubram has joined #openstack-meeting16:26
ihrachysmaybe eventlet screwing up file descriptors somehow16:26
ihrachyswell actually, maybe I assume too much saying it's a neutron issue16:28
ihrachysI mean, neutron error, sorry16:28
*** janki has quit IRC16:29
ihrachysbut anyway, jlibosva is going to reach out to Terry. please mention both bugs since they are arguably related.16:29
jlibosvayep, will do16:29
*** Guest56042 has quit IRC16:29
ihrachys#action jlibosva to talk to otherwiseguy about making progress for functional ovsdb issues (timeouts, retries, stream parsing failures)16:30
ihrachysthanks!16:30
*** hagridaaron has quit IRC16:30
ihrachysjlibosva, you mentioned a functional job being stuck. I believe you mean http://logs.openstack.org/99/533799/1/check/neutron-functional/990c856/16:30
ihrachysdo you think it can be related to ovsdb issues, or there is more to it?16:30
*** deathsparton has joined #openstack-meeting16:30
jlibosvayep, that's it http://logs.openstack.org/99/533799/1/check/neutron-functional/990c856/job-output.txt.gz#_2018-01-15_23_30_49_84037816:31
jlibosvaI mean, that's what I meant16:31
*** liyi has joined #openstack-meeting16:31
*** carl_baldwin has quit IRC16:32
ihrachysso it's just a random kill16:32
jlibosvalast job I checked, there was a 1.5GB large log file containing output of one particular test and it was full of TRY_AGAIN messages16:32
ihrachysjlibosva, aha that's a good sign that it's same issue16:32
jlibosvanow I wonder why timeout per test wasn't triggered16:32
*** hagridaaron has joined #openstack-meeting16:32
ihrachysright16:32
jlibosvamaybe it didn't switch greenthreads16:33
*** deathsparton has quit IRC16:33
jlibosvaor we have an issue there16:33
ihrachysyeah. does anyone have cycles to check why the job timed out? or we just leave it at it while we figure out ovsdb issue16:34
ihrachysok let's leave it for now and revisit if it happens more16:34
ihrachys#topic Fullstack16:34
*** openstack changes topic to "Fullstack (Meeting topic: neutron_ci)"16:35
jlibosvaI can check it16:35
ihrachyswell ok :)16:35
jlibosvaI believe it will be the TRY_AGAIN :)16:35
ihrachys#action jlibosva to check why functional job times out globally instead of triggering a local test case timeout for TRY_AGAIN ovsdb issue16:35
*** liyi has quit IRC16:35
*** gagehugo has joined #openstack-meeting16:36
*** krtaylor has quit IRC16:36
ihrachysjlibosva, a lot of pointers to it maybe being the case of eventlet running amok16:36
ihrachysanyway, back to fullstack16:36
ihrachysslaweq was doing amazing job lately tackling failures we have one by one16:36
slaweqbut slowly :)16:37
ihrachysthe latest fix for qos dscp bug is https://review.openstack.org/53331816:37
ihrachysand it's already +W, just need to get it merged16:37
ihrachysthere was a concern during review that l2 extension manager may bubble up exceptions from extensions16:38
*** gouthamr has quit IRC16:38
ihrachyshow do we tackle that? I guess the least reporting a low priority bug?16:38
ihrachysanyone willing to chew it beyond that?16:38
slaweqI can report it16:38
ihrachysgo for it!16:38
slaweqbut I don't know if I will have time to propose fix soon16:39
ihrachys#action slaweq to report a bug about l2 ext manager not catching exceptions from extensions16:39
slaweqok, I will report it today16:39
ihrachysthat's fine16:39
ihrachysjust don't assign yourself if you don't plan to work on a fix, and someone should pick it up eventually16:39
slaweqsure16:39
ihrachysok. apart from this fix, do we have anything in review that would help the job?16:40
slaweqI want to mention that patch for https://bugs.launchpad.net/neutron/+bug/1733649 was also merged few days ago16:40
openstackLaunchpad bug 1733649 in neutron "fullstack neutron.tests.fullstack.test_qos.TestDscpMarkingQoSOvs.test_dscp_marking_packets(openflow-native) failure" [High,Fix released] - Assigned to Gary Kotton (garyk)16:40
slaweqso I hope it will be better now16:40
slaweqI will check if for few days and will remove "unstable_test" decorator if all will be fine16:40
*** gyee has joined #openstack-meeting16:41
ihrachysfullstack is still steady 80% so I guess other issues are more frequent to fail to mitigate the fix impact16:41
slaweqand I will also propose this fix for stable branches then16:41
*** yamamoto has joined #openstack-meeting16:41
ihrachysslaweq, oh you mean the test that was ignored. ok.16:41
slaweqihrachys: yes16:41
ihrachysok taking one of the fresh runs for fullstack: http://logs.openstack.org/99/533799/1/check/neutron-fullstack/f827430/logs/testr_results.html.gz16:42
ihrachysI noticed this agent restart test started failing too often in the job16:42
ihrachysoften it's the only failure16:42
ihrachysso I suspect tackling this one should drop failure rate significantly16:42
ihrachysI don't think we ever reported the bug for the failure16:42
*** hagridaaron has quit IRC16:44
jlibosvauhm, shall we mark it as unstable to get some better failure rate? :)16:44
ihrachysmaybe. after reporting a bug at least16:44
ihrachysI checked ovs agent logs for the test16:44
ihrachysthe only suspicious one is this agent (there are 4 logs total there): http://logs.openstack.org/99/533799/1/check/neutron-fullstack/f827430/logs/dsvm-fullstack-logs/TestUninterruptedConnectivityOnL2AgentRestart.test_l2_agent_restart_OVS,VLANs,openflow-native_/neutron-openvswitch-agent--2018-01-15--21-43-21-502569.txt.gz?level=WARNING16:45
ihrachys2018-01-15 21:45:49.869 28570 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.br_int RuntimeError: ofctl request version=None,msg_type=None,msg_len=None,xid=None,OFPFlowStatsRequest(cookie=0,cookie_mask=0,flags=0,match=OFPMatch(oxm_fields={}),out_group=4294967295,out_port=4294967295,table_id=23,type=1) error Datapath Invalid 9026944645255816:45
ihrachysand then later16:45
ihrachys2018-01-15 21:45:49.942 28570 WARNING neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-f3915075-576d-4155-86c3-c2272e53a1d8 - - - - -] OVS is dead. OVSNeutronAgent will keep running and checking OVS status periodically.16:45
*** yamamoto has quit IRC16:46
*** andreas_s has quit IRC16:46
*** andreas_s has joined #openstack-meeting16:47
ihrachysthere are some log messages in ovsdb server log like: 2018-01-15T21:45:33.394Z|00012|reconnect|ERR|tcp:127.0.0.1:59162: no response to inactivity probe after 5 seconds, disconnecting16:47
ihrachyswhat's the probe?16:47
ihrachysis it ovsdb server talking to ryu?16:47
ihrachyslike checking if controller is still there?16:47
jlibosvaI think that's ovsdb talking to manager16:47
jlibosvaor rather vice-versa16:48
slaweqthis ovsdb log is very similar like in stucked functional tests IMHO16:48
slaweqmaybe it's related somehow?16:48
jlibosvait's more related to native ovsdb interface than openflow16:48
ihrachysslaweq, maybe it's always like that :)16:48
ihrachysjlibosva, yeah sorry mixed things16:48
slaweqmaybe, I don't know16:48
ihrachysanyway... I will report a bug for that. I may dedicate some time to dig it too.16:49
ihrachys#action ihrachys to report bug for l2 agent restart fullstack failures and dig it16:49
ihrachys#topic Scenarios16:50
*** openstack changes topic to "Scenarios (Meeting topic: neutron_ci)"16:50
ihrachyshaleyb, I saw some activity on dvr bugs that lingered scenarios. any updates?16:50
ihrachysor was it something else... I think I saw Swami posting something but now I don't.16:51
ihrachysI guess I dreamt16:51
ihrachysanyway, if anything this is the bug that affected us for a while: https://bugs.launchpad.net/neutron/+bug/171730216:52
openstackLaunchpad bug 1717302 in neutron "Tempest floatingip scenario tests failing on DVR Multinode setup with HA" [High,Confirmed] - Assigned to Brian Haley (brian-haley)16:52
ihrachysit's on Brian but there seems to be no fixes or updates since Dec16:52
mlavalleif haleyb is not around, I can bring it up in the L3 meeting this coming Thursday16:53
*** chyka has joined #openstack-meeting16:53
ihrachysyeah please do16:53
mlavalle++16:53
ihrachys#action mlavalle to bring up floating ip failures in dvr scenario job to l3 team16:54
ihrachysI am looking at a fresh run16:54
ihrachyshttp://logs.openstack.org/60/532460/1/check/legacy-tempest-dsvm-neutron-dvr-multinode-scenario/bf95db0/logs/testr_results.html.gz16:54
ihrachyssee the trunk test failed16:54
*** links has quit IRC16:54
ihrachysI don't think it's reported16:55
ihrachysanyone up for the job to report it or maybe even having a look?16:55
jlibosvathat might be fixed by https://review.openstack.org/#/c/531414/116:55
ihrachysack!16:56
ihrachys#topic Rally16:56
*** openstack changes topic to "Rally (Meeting topic: neutron_ci)"16:56
ihrachyswe had https://bugs.launchpad.net/neutron/+bug/1741954 raised a while ago16:56
openstackLaunchpad bug 1741954 in neutron "create_and_list_trunk_subports rally scenario failed with timeouts" [High,In progress] - Assigned to Armando Migliaccio (armando-migliaccio)16:56
ihrachysthis is mostly to update folks that we have a fix for that here: https://review.openstack.org/#/c/532045/16:56
ihrachys(well, it's kinda a fix, it's just optimization)16:57
ihrachysI think we started hitting more timeouts and perf issues since meltdown patching in infra / clouds we use16:57
ihrachysbut the patch should help one of those instance16:57
ihrachys*instances16:57
ihrachys#topic Gate16:57
*** openstack changes topic to "Gate (Meeting topic: neutron_ci)"16:57
ihrachysmlavalle, I recollect you were going to follow up on remaining legacy- jobs in neutron gate that we figured out are still present and not converted to new format16:58
ihrachysany progress?16:58
ihrachys(like tempest py3)16:58
mlavalledidn't have time this past week16:58
mlavalleI will do it over the next few days16:58
ihrachys#action mlavalle to transit remaining legacy- jobs to new format16:58
ihrachysgotcha, that's ok, not pressing!16:59
mlavalle:-)16:59
ihrachysok we are out of time16:59
ihrachysit's always pretty packed this meeting riiiight? :)16:59
mlavalleyeah16:59
ihrachysthat's good16:59
ihrachysok thanks everyone16:59
ihrachys#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:59
mlavalleihrachys: you lead it well16:59
slaweqthx16:59
jlibosvao/16:59
openstackMeeting ended Tue Jan 16 16:59:43 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-01-16-16.01.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-01-16-16.01.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-01-16-16.01.log.html16:59
slaweqsee You next week :)16:59
mlavalleihrachys: keep us on out toes ;-)17:00
mlavalleour^^^17:00
*** gouthamr has joined #openstack-meeting17:00
ihrachysmlavalle, it's morning, I am trying to keep myself not asleep :)17:00
slaweqlucky You ihrachys :)17:00
*** andreas_s has quit IRC17:01
jlibosvawhat are you talking about? it's getting late :)17:01
slaweqjlibosva: exactly :)17:01
*** fouadben has quit IRC17:02
ihrachysjlibosva, they say there is that thing called time zones. not sure what they are talking about, but worth a check.17:02
*** deathsparton has joined #openstack-meeting17:02
*** yamahata has quit IRC17:02
jlibosvaI don't believe them, I have my own conspiracy theory17:03
*** sudipto_ has joined #openstack-meeting17:06
*** sudipto has joined #openstack-meeting17:06
*** deathsparton has quit IRC17:07
*** liyi has joined #openstack-meeting17:13
*** mjturek has quit IRC17:16
*** liyi has quit IRC17:17
*** iyamahat has joined #openstack-meeting17:19
*** tesseract has quit IRC17:21
*** anilvenkata has quit IRC17:21
*** spilla has joined #openstack-meeting17:24
*** srwilkers has joined #openstack-meeting17:24
*** julim has joined #openstack-meeting17:25
*** julim has quit IRC17:29
*** marios has quit IRC17:30
*** lamt` has quit IRC17:31
*** julim has joined #openstack-meeting17:31
*** lamt` has joined #openstack-meeting17:32
*** zigo has quit IRC17:33
*** sshnaidm is now known as sshnaidm|afk17:34
*** sshnaidm|afk has quit IRC17:34
*** yamahata has joined #openstack-meeting17:37
*** zigo has joined #openstack-meeting17:37
*** sshank has joined #openstack-meeting17:39
*** sridharg has quit IRC17:39
*** sshank has quit IRC17:40
*** rfolco_nho has quit IRC17:41
*** sudipto_ has quit IRC17:41
*** sudipto has quit IRC17:41
*** yamamoto has joined #openstack-meeting17:44
*** andreas_s has joined #openstack-meeting17:47
*** mlavalle has quit IRC17:52
*** ekcs has quit IRC17:52
*** ricolin has quit IRC17:54
*** jlibosva has quit IRC17:55
*** yamamoto has quit IRC17:58
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Jan 16 18:00:11 2018 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
*** markstur has joined #openstack-meeting18:00
lbragstadping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rderose, rodrigods, samueldmq, spilla, aselius, dpar, jdennis, ruan_he18:00
lbragstadagenda ^18:00
knikollao/18:00
lamt`o/18:00
gagehugoo/18:00
spillaO/18:00
kmallocbah i need more coffee.18:00
lbragstadpretty light agenda today18:01
lbragstadso we can give folks a few minutes to show up18:01
cmurphyo/18:02
*** sshnaidm|afk has joined #openstack-meeting18:03
lbragstadalright - let's get started18:03
lbragstad#topic announcements: non-client library freeze18:04
*** openstack changes topic to "announcements: non-client library freeze (Meeting topic: keystone)"18:04
lbragstadjust a reminder that this week is going to be non-client library freeze18:04
lbragstadso, keystonemiddleware, keystoneauth, oslo libraries, etc...18:04
lbragstadif you're looking for things to review, those would be high priority18:04
*** andreas_s has quit IRC18:05
lbragstad#topic announcements: client freeze18:05
*** openstack changes topic to "announcements: client freeze (Meeting topic: keystone)"18:05
lbragstad^ that is going to be next week, which is also going to be feature freeze18:05
lbragstadand we do have three big efforts still in flight (excluding the documentation work)18:05
lbragstadapplication credentials18:05
lbragstad#link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bp/application-credentials18:06
lbragstadunified limits18:06
lbragstad#link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bp/unified-limits18:06
lbragstadand system scope18:06
lbragstad#link https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:master+topic:bp/system-scope18:06
lbragstadthere are a bunch of things to review there, so there's no shortage of reviews18:06
lbragstadany questions or concerns regarding what we have in flight?18:06
*** designbybeck has joined #openstack-meeting18:07
lbragstadcool - moving on then18:07
lbragstad#topic core adjustments18:07
*** openstack changes topic to "core adjustments (Meeting topic: keystone)"18:07
lbragstadour current core team isn't really reflective of the current state of things18:08
lbragstadi've been in touch with a few members and the decision was mutual to remove a couple18:08
*** david-lyle has quit IRC18:08
kmallocbe sure to send the removals to the ML as well :)18:09
lbragstadtoday I'll be removing stevemar and bknudson from keystone core18:09
lbragstadand btopol from keystone specs core18:09
lbragstadkmalloc: ++18:09
lbragstadi don't think any of them are hanging around in IRC, but i personally appreciate everything they've done for the project18:10
*** mjturek has joined #openstack-meeting18:10
lbragstadand it'll suck to see them go18:10
lbragstadbut on a lighter note18:10
*** jessegler has joined #openstack-meeting18:10
lbragstadI'm happy to announce that we'll be adding gagehugo to keystone-core!18:10
cmurphyyay gagehugo \o/18:11
lamt`grats18:11
jessegleryay \o/18:11
gagehugothanks everyone18:11
lbragstadhe's been doing some great work and picking up a lot of slack to keep us moving forward18:11
*** markstur_ has joined #openstack-meeting18:11
lbragstadwhich is awesome, thanks for all your hard work gagehugo18:11
*** mjturek has quit IRC18:12
knikollacongrats! keep up the good work \o/18:12
gagehugohappy to help :)18:12
lbragstadi'm glad we're making this change prior to the release going into RC18:12
lbragstadi think it will make a difference and help with the review queue18:12
lbragstadalright - moving on18:13
lbragstad#topic Rocky community goals18:13
*** openstack changes topic to "Rocky community goals (Meeting topic: keystone)"18:13
lbragstadjust a heads up in case anyone hasn't seen it yet18:13
lbragstad#link https://review.openstack.org/#/c/532627/118:13
lbragstadbut that's a proposal for one of the community goals - which will impact keystone given our complex history with pagination18:14
*** lpetrut_ has quit IRC18:14
kmallocand i'll still -2 pagination changes that require it in keystone18:14
kmallocftr18:14
kmallocfor things that hit ldap things.18:14
lbragstadkmalloc: you'll need to weigh in on the community goal18:14
lbragstadi highlight it a bit in a comment, but more context would be good18:15
lbragstad(i also know we have the pagination discussion scattered everywhere)18:15
*** markstur has quit IRC18:15
kmalloci'm going to let you proxy our concerns to a consistent voice.18:15
kmallocbut basically users cannot be paginated.18:15
kmallocand ... i think roles.18:15
lbragstadanything that has to read from ldap can't be paginated...18:15
kmallocyep18:15
kmallocotherwise i will say pagination is a terrible design and never works like people expect, but users / ldap backed data is a hard -2, regardless of community goals18:16
kmalloceverything else, if someone signs up to write it, i'll at least review it and not -1/-2 because i dislike the design18:17
lbragstadi was thinking about this a bit, but we wouldn't be able to work around that technical requirement while keeping keystone stateless18:17
*** links has joined #openstack-meeting18:17
kmallocpretty much.18:17
lbragstadok - i can follow up with mordred about that18:17
kmallockeystone always has "special" cases18:17
kmallocit is part of just how we're designed18:17
kmallocalso... pagination is not guaranteed consistent even with SQL because we are stateless18:18
kmallocwhich is why the design is so bad. but, whatever18:18
lbragstad... so won't that affect every project that uses SQL?18:18
kmallocas long as we communicate "pagination doesn't work like you think" in docs for the things not ldap backed, we're good.18:18
lbragstadand not just keystone?18:18
kmallocit will.18:18
kmalloci always use the "how many pages deep in google do you look when looking at items"18:19
kmallocand no one goes beyond page 218:19
kmallocthis is why pagination doesn't work.18:19
cmurphykmalloc: i think you should bring this up on the goal review18:19
kmallocsearch/filter.18:19
gagehugothings get weird after page 218:19
lbragstadi've heard people argue the exact opposite18:19
kmallocbut like i said, ldap is the only bit that is a hard -2 and that is because of active cursors and non-deterministic ordering18:19
lbragstadthat they can't write filters specific enough to get what they want out of the first page18:19
gagehugocmurphy ++18:20
kmallocthe rest, i don't have the energy to argue the rest and we should just communicate it in docs18:20
kmallocand expect people to complain it's bad :P18:20
kmallocwe already mostly lost the argument.18:20
*** bobh has quit IRC18:21
lbragstadwhat would be required to make it so sql always returns the same result?18:21
lbragstaddatabase migrations?18:21
kmallocsomething MySQL doesn't do well.18:21
kmallocviews.18:21
kmallocmost things you end up doing is creating a temp view of the data for referencing for a series of requests.18:22
kmallocwould eb the oracle method18:22
kmallocthen you can have a consistent response for a set of data referenced in the request vs a list that changes behind the scenes if say a project is deletec and shifts the elements on a page18:23
kmallocover a refresh18:23
kmallocso, basically not an argument worth having.18:24
*** liyi has joined #openstack-meeting18:24
kmallocbut LDAP cannot support pagination for keystone18:24
lbragstadhmm18:24
lbragstadyeah - we need to voice this on the goal18:24
lbragstadi can follow up afterwords and do that18:25
*** ayoung has joined #openstack-meeting18:25
kmallocthe only thing i recommend commenting on the goal is the user bit.18:25
lbragstadthat's the hard requirement18:25
kmallocyep.18:25
*** armax has quit IRC18:25
lbragstadbecause in order to do that, keystone would have to be stateless18:25
ayoungLets make Keystone stateless!18:26
kmallocstateful and communicate cursors across multiple projects18:26
cmurphykmalloc: I really think it would be worth it to comment on the goal with all your concerns, saying it's not an argument worth having means that the argument is never heard18:26
kmallocs/projects/processes18:26
kmalloccmurphy: i've had the argument multip[le times. i am voicing history here18:26
*** armax has joined #openstack-meeting18:26
kmalloci really don't want to start down that path again. I want to make sure LDAP backed data is carved out18:26
lbragstadwell - we will need to voice the concern in the goal before it is accepted18:27
lbragstadeven if it is, we'll probably have to apply for an exception of some sort18:27
*** absubram has quit IRC18:27
ayoungLets deprecate LDAP, spin it off to its own IdP thing18:28
*** liyi has quit IRC18:28
cmurphyayoung: go for it, i'll review :)18:28
kmallocsure. i'm not signing up to write that code though18:29
ayoungcmurphy, code is the easy part18:29
lbragstadkmalloc: so are you going to add your concerns to the goal review?18:31
kmalloci can add the ldap bit, but thats really as far as i will go.18:31
lbragstadthat's fine - thanks for doing that18:31
ayoungthere was a bug filed recently about LDAP user-list being slow.  I really want to find a way to tell people "you really don't want to do that"18:32
ayoungrecently by my definition is post Folsom18:32
lbragstadthat sounds like a PTG topic :)18:32
*** cleong has quit IRC18:33
*** tobiash has joined #openstack-meeting18:33
lbragstad#topic open discussion18:34
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:34
*** links has quit IRC18:34
lbragstadfloor is open!18:34
cmurphyoh i was wondering about the ansible upgrade jobs we have18:34
cmurphyi don't think i've ever seen them passing18:34
cmurphywho owns those?18:34
gagehugoyeah they pass like 1/100 times it seems18:34
cmurphylol not useful18:34
lbragstadthose were put in place by the openstack ansible folks18:34
lbragstadbut i think some changes happened around the infra changes that broke some of them18:35
kmalloccommented18:35
lbragstadcc evrardjp ^18:35
lbragstadi can't remember if it was around the time we moved to Zuul or before that18:35
lbragstadkmalloc: thank you18:35
kmallocayoung: yeah "don't list users with LDAP... no really" but i think we should add a proper search API for users18:36
cmurphyi feel like it was right before18:36
kmallocrather than telling people to "list and filter"18:36
kmallocit can be a list/filter behind the scenes18:36
*** links has joined #openstack-meeting18:36
*** Shrews has joined #openstack-meeting18:36
kmallocanyway... /me goes back to being the grumpy old core.18:36
clarkblbragstad: it was before we moved to zuul18:36
clarkber moved to zuulv318:37
ayoungkmalloc, the fact that it is a filter should be exoposed to the user, and the assumption of stateful pagination be explicitly expunged,.18:37
lbragstadyeah - it was solid at one point18:37
kmallocayoung: ++ YES.18:37
lbragstadbut i think something happened there and I want to say it was around that time18:37
lbragstad(the time of switching over to zuul)18:37
gagehugoyeah it was around zuulv3 time18:37
ayoung@cmurphy, link to a common failing example that we can all look at?18:37
cmurphyayoung: sure let me find one18:38
cmurphyhttp://logs.openstack.org/27/524927/21/check/openstack-ansible-keystone-rolling-upgrade/7f25e2b/18:38
*** sshnaidm|afk is now known as sshnaidm18:39
ayoungtask path: /home/zuul/.ansible/roles/os_previous_keystone/tasks/keystone_fernet_keys_create.yml:2118:39
ayoung__init__() got an unexpected keyword argument 'scope_types'"18:40
ayoungI think that is a lbragstad issue to tackle18:40
lbragstadoslo.policy needs to be updated18:40
lbragstadit looks like they are testing master with older requirements18:41
cmurphyokay it sounds like it's easy to fix, i was wondering if there was a go-to person attending to them18:42
lbragstadodyssey4me, evrardjp, or cloudnull18:42
cmurphyi think that job was the only thing between us and the rolling-upgrade tag?18:43
lbragstador andymccr18:43
lbragstadyeah - with one other stipulation18:43
lbragstadwhich was how the patches from review were applied to the environment18:43
lbragstadif patch A is proposed to master and has a Depends-On on patch B which is proposed to a stable branch, and both contain migrations of some sort, then it's possible to brick the migrations because patch B won't be installed in the setup18:44
lbragstadof the test environment by OSA18:44
ayoungthat looks like it is a CLI param for keystone-manage.  Did we drop something?18:44
*** rmcall_ has joined #openstack-meeting18:45
*** jbadiapa_ has joined #openstack-meeting18:46
*** ekcs has joined #openstack-meeting18:47
*** lbragstad_ has joined #openstack-meeting18:47
gagehugopossibly?18:47
* lbragstad_ is having internet connection trouble18:48
*** jbadiapa has quit IRC18:48
mordredkmalloc, lbragstad_: sorry I missed it earlier - but the pagination goal is "if a collection is paginated, pagination links should be returned"18:48
mordredkmalloc, lbragstad_: definitely not "add pagination to all resources" or anything18:49
gagehugoah18:49
lbragstad_mordred: ack - that helps18:49
*** dbecker has quit IRC18:49
lbragstad_sorry if i jumped to assumptions there18:49
mordredin which case - it might very well be a no-op :)18:49
*** lbragstad has quit IRC18:49
mordredno - it's a good question for sure!18:49
*** lbragstad_ is now known as lbragstad18:50
kmallocmordred: ++18:50
kmallocok18:50
*** spilla_ has joined #openstack-meeting18:50
kmallocmordred: i was worried because we just can't paginate users w/o massive headaches18:50
kmalloci'll recind my -1 and say you updated us18:50
ayoungmordred, LDAP and pagination has been a pain point since the mid 1990s18:51
mordred++18:51
*** bobh has joined #openstack-meeting18:52
mordredI'm actually not a big fan of pagination for REST calls across the board - it makes things harder - but I also can somewhat understand the humans who desire such a thing18:52
mordredbut pagination without pagination links is just the worst18:52
lbragstadcool - that clears things up then18:54
lbragstadanything else we want to go over before office hours starts in 6 minutes?18:54
lbragstadcmurphy: i think i dropped in the middle of the osa rolling upgrade discussion18:55
cmurphylbragstad: oh i don't think you missed much18:55
cmurphyif anything18:55
lbragstadok18:56
cmurphyafter feature freeze i can try to work on them and/or reach out to the osa people about it18:56
lbragstadyeah18:56
lbragstadthey are usually super responsive to those things18:57
*** electrofelix has quit IRC18:57
*** bobh has quit IRC18:57
lbragstadanything else?18:57
*** efried is now known as efried_nomnom18:57
lbragstadcool - thanks for coming18:57
lbragstad#endmeeting18:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"18:57
openstackMeeting ended Tue Jan 16 18:57:57 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-01-16-18.00.html18:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-01-16-18.00.txt18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2018/keystone.2018-01-16-18.00.log.html18:58
*** jessegler has quit IRC18:58
*** AlanClark has joined #openstack-meeting18:58
*** sambetts is now known as sambetts|afk18:58
*** electrofelix has joined #openstack-meeting18:58
*** david-lyle has joined #openstack-meeting18:59
* fungi peers around19:00
clarkbhello infra19:00
ianwhello hello19:00
fungihowdy, y'all!19:00
pabelangero/19:01
clarkbwe have a fairly full agenda so I'm going to dive right in19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Jan 16 19:01:18 2018 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
*** spzala has joined #openstack-meeting19: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
tobiasho/19:01
Zarao/19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
*** spilla_ has left #openstack-meeting19:01
clarkb#info clarkb and fungi missing January 23rd meeting due to travel.19:02
clarkbpabelanger and ianw have volunteered to run the meeting next week iirc. I'll let them sort out between themselves who wants to do it19:02
clarkb#info OpenDev focused on CI/CD happening April 26-27 in San Francisco19:02
corvusmeetings can have co-chairs :)19:02
clarkbcorvus: oh ya they can cochair too :)19:02
fungicochise19:03
*** alisanhaji has quit IRC19:03
clarkbLast year the openstack foundation had an "opendev" event in san francisco with a focus on edge computing. This year they are hosting a similar event with a focus on CI/CD19:03
* mordred waves19:03
clarkbIf that is something you are interested in mark those dates on your calendar. Sounds like there should be good industry representation too so not openstack focused19:03
corvusit'll be nice to have folks there to talk about our experiences19:04
clarkb#link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126192.html Vancouver Summit CFP open. Submit your papers and/or volunteer to be on the programming committee.19:04
pabelanger++19:04
clarkbThe OpenStack summit CFP has also opened. One of the tracks is CI so now is the time to propose papers and/or volunteer to sit on a programming committee19:04
*** diablo_rojo has quit IRC19:05
clarkbI think they are looking for people that have never been on a summit programming committee to volunteer so if you are interested you should go for it19:05
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2018-January/005800.html Zuul has mailing lists19:05
dmsimardclarkb: I guess the OpenDev website isn't up to date, it doesn't mention the April dates19:05
clarkbdmsimard: ya I think we got the prerelease info on that19:05
dmsimardok19:05
clarkbdmsimard: but I'm told the dates and rough location shouldn't change19:05
pabelangerI've added my name to volunteer for programming committee19:05
fungidmsimard: aiui, they're still finalizing the venue contract19:05
*** gouthamr has quit IRC19:06
clarkbZuul has mailing lists now. I just tested that sign up works and it does!19:06
dmsimardDo we know if there's a CFP or if they need help organizing ? Sounds like a great venue to advertise the work we do in OpenStack in terms of CI/CD19:06
dmsimard(Sorry for slightly sidetracking, didn't get time to reply when it was on-topic)19:06
clarkbdmsimard: I can ask for that info and pass it along19:06
clarkbdmsimard: its ok (we just have a large agenda so trying to keep moving)19:06
dmsimardok, thanks19:06
clarkbdmsimard: I'll let them know that updates to the website with more info would be useful and ask about cfp19:06
corvusi'm on the opendev programming committee19:07
*** links has quit IRC19:07
corvusas of 3 hours ago19:07
corvusi'll be happy to keep this group updated19:08
clarkbawesome, thanks19:08
dmsimardcorvus: grats :p19:08
fungiappreciated!19:08
pabelangernice19:08
corvuswe're having our first meeting friday, so probably more info after that?19:08
clarkb#topic Actions from last meeting19:08
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:08
clarkbThere were none \o/19:09
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-01-09-19.01.txt minutes from last meeting19:09
fungiand a fine week it was19:09
corvusdidn't i...19:09
corvus  * corvus patchbomb project name removals from zuul.yaml19:09
clarkboh did I read the wrong agenda?19:09
clarkbI may have opened the wrong link when I looked19:09
corvusi haven't done that, fwiw -- i decided with zuul going oom i should sit on that a bit.19:10
corvusmaybe this friday...19:10
clarkbya I must've19:10
corvus#action corvus patchbomb project name removals from zuul.yaml19:10
clarkbthanks19:10
clarkb#topic Specs approval19:10
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:10
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2018-January/005779.html Cleanup old specs.19:10
clarkbI sent mail about starting to cleanup some old specs and pinged others out of band for a couple others. Things have started moving on this.19:11
clarkbIf you have input please send it in19:11
clarkb#link https://review.openstack.org/#/c/531242/ IRC Bot Improvements19:11
clarkbfungi and I reviewed ^ last week. I think jeblair was hoping to put it up for a vote this week?19:11
corvusi haven't had a lot of input since last week's rfc19:11
*** bobh has joined #openstack-meeting19:11
clarkbit seemed like a really well thought out and written spec19:12
fungiyeah, something did just dawn on me earlier today on that one too19:12
corvusdoes anyone want to delay another week for more collaboration, or should we vote?19:12
clarkbI'm comfortable with it as is, but more input would probably be good especially if fungi has new thoughts19:12
corvus(it's not urgent, but if we agree on a plan, it's very divisible, so we can pick of parts of it in parallel in our copious spare time)19:13
fungiwrt auto-kickbanning abusers based on spotting highlight spam, is there an easy way to differentiate it from when meeting chairs do the same to give people a heads up that a meeting's starting? or should we just get people out of that habit19:13
*** andreas_s has joined #openstack-meeting19:13
corvusfungi: i feel like we can make that a tunable thing19:13
clarkbmaybe whitelist the meeting bot and have it do it?19:13
fungioh, maybe19:14
clarkbsomething like #notify fungi corvus clarkb19:14
corvuspercentages could factor in -- also, we could be more generous for folks with registered nicks19:14
fungianyway, not a big enough concern for me to bring it up in review i guess19:14
pabelanger+1 spec is well written19:14
corvusyeah, i don't think we need to change the general approach laid out in the spec, just fine-tune the algorithm19:15
clarkbI'm happy to move forward with it this week. Does anyone think they want more time to review it (I think its perfectly acceptable to do more review too)19:15
clarkbianw: dmsimard frickler ^19:16
corvusmnaser: ^19:16
* fungi kickbans clarkb for hightlight spam ;)19:16
clarkb:)19:16
*** andreas_s has quit IRC19:17
* dmsimard catches up with backlog19:18
*** andreas_s has joined #openstack-meeting19:18
dmsimardI had quickly skimmed the spec but didn't give it a good review, I'll take a look after the meeting.19:19
clarkbcorvus: where do you sit on it?19:19
clarkbcorvus: you still want to move ahead this week?19:19
dmsimardUsing the supybot fork is reasonable -- using errbot would be nice but a lot of work.19:19
*** fnaval has quit IRC19:19
corvusclarkb: let's put it up for vote and if dmsimard -1s it we'll take another pass19:19
clarkbsounds good to me19:19
dmsimardSomething about errbot that's nice is the built-in cross-platform thing (slack, irc, xmpp, etc.)19:20
dmsimardI'll vote on the spec.19:20
clarkb#agreed put https://review.openstack.org/#/c/531242/ IRC Bot improvements up for vote this week and if dmsimard -1s we'll take another pass19:20
clarkb#topic Priority Efforts19:20
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:20
clarkb#topic Storyboard19:20
mordredyah - that was the original motivation for errbot- but the amount of work has resulted in no progress since we started talking about it around the paris summit19:20
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:20
*** diablo_rojo has joined #openstack-meeting19:21
fungithis is a quick one19:21
clarkbfungi: has a topic for storyboard "should we allow search indexes to index storyboard"19:21
fungiin the course of the -dev ml thread covering tripleo's testing out of sb, i noticed that we have a robots.txt denying indexing by web crawlers on sb.o.o19:22
fungia little archaeology indicates that has been baked into the webclient source/build since its very initial commit19:22
Zara:)19:22
pabelangeryah, seems like some we should be allowing, helping users find the reports19:22
fungisubsequent discussion in #storyboard indicates that it may not be particularly straightforward since the content is rendered via javascript calling the sb api19:23
corvusindexing of #! based sites is not easy19:23
clarkbmaybe we want to unblock it on storyboard-dev first, make sure that it doesn't cause the server to fall over then do it on storyboard.openstack.org?19:23
corvusthough google changed how they do stuff with that recently19:23
clarkbfungi: oh right19:23
corvusit may be easier19:23
fungithere was a suggestion that google at least does some of this, yeah19:23
corvus(apparently, the google indexer can now render js pages with some fidelity)19:23
fungii'd be less keen on allowing indexing of sb-dev.o.o because we could end up with misleading stale copies of stories and other test story content turning up in web searches19:24
corvusprobably someone needs to do a little bit of research and determine if it's feasible and not destructive to enable with respect to the current state of the art, or whether we need to make storyboard changes19:24
clarkbfungi: because we put duplicate test stories in there?19:24
clarkbor even the test migrations I guess19:24
fungiclarkb: both testing migrations there and importing copies of the production db19:25
Zarayeah I definitely think dev should stay unindexed19:25
Zaraour routing is old anyway so it would be nice to update that more generally19:25
clarkbin that case we need to watch production carefull when we make the change but that should be doable and is an easy change to undo19:25
clarkbbut I'm in favor of that19:26
fungiyeah i'm not super sure how to test whether this would have a negative impact without just doing it and keeping a close eye on the server resources19:26
clarkbdo we have a volunteer for doing that? watching cacti and general server responsiveness from your local browser should get you msot of the way there (so doesn't require root)19:27
clarkbthen if things really go sideways or we need more info a root can dig that up19:27
ZaraI sould be able to if someone sends me links19:28
Zara(or I can go digging)19:28
fungii can volunteer to be infra-root primary point of contact for that stuff too since i opened the can of worms to start with19:28
clarkbZara: fungi thanks! I think that means fungi can dig up links19:28
fungiand try to keep an eye on it during waking hours19:28
Zaragreat, thanks! :D19:28
fungiyes, i'll put together links Zara19:28
clarkbanything else on this or are we good to move on to zuul v3?19:29
fungithat's all i had19:29
Zara_o_19:29
* mordred owes Zara another patch ...19:29
clarkb#topic Zuul v319:29
*** openstack changes topic to "Zuul v3 (Meeting topic: infra)"19:29
clarkbquick note that I almost have the zuul v3 issues etherpad cleared out and migrated to other data tracking systems19:29
clarkbhope to finish that up today19:30
clarkbfungi is working on making a bigger zuul v3 instance19:30
clarkbfungi: anything you need to help move that along?19:30
fungiyep, and relearning puppet apparently19:30
fungiclarkb: nothing else i know about yet19:30
clarkbinfra-root ^ helping that is somewhat important so that we can stabilize zuul.o.o19:31
fungiwill hopefully have it booted shortly after the meeting19:31
pabelanger++19:31
clarkbThe other thing I had on the agenda to talk about is merging feature/zuulv3 into master19:31
fungithen i'll rebase the remaining system-config change for cacti/firewalls19:31
clarkbfungi: cool, sounds like it should be done soon then19:31
fungihere's hoping19:31
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2018-January/005790.html Communicating a feature/zuulv3 merge plan19:32
clarkb#link https://etherpad.openstack.org/p/zuulv2-outstanding-change-triage Triaging existing changes on v2 master branches19:32
fungii added that last one to the agenda mainly to get a touchpoint on what we want to do19:32
clarkbI think we are really close to being able to merge the feature/zuulv3 at least from a technical standpoint19:32
clarkbthe etherpad above was news to me (or I had forgotten about it at least)19:32
clarkbhave we declared bankruptcy on that?19:33
corvusi think it's worth going through old changes and see what might be relevant19:33
fungiit's a lot of changes open on master and not only do we generally have enough trouble reviewing urgent changes in a timely fashion, i at least feel like i lack sufficient context to judge which ones would still be relevant in v319:33
pabelangerI am hoping to push up changes need to bring nb01 back online with nodepool feature/zuulv3 running. Will need some changes to nodepool.yaml syntax first19:33
clarkbok so maybe take a step back on the thursday merge goal ( as I expect going through all those changes will take longer?)19:34
corvusoh no sorry19:34
corvuswe're not merging anything to the current master19:34
clarkbcorvus: oh do you mean look through them and forward port?19:34
Shrewspabelanger: what's changed in the nb* configs?19:34
fungii.e. master branch is frozen for further commits until feature/zuulv3 is merged to master19:34
corvusi mean look through them and triage.  we can abandon lots of them.  the rest we can indicate are good targets for forward-porting.19:34
clarkbcorvus: got it19:35
corvusi think that can happen at any time -- even after the v3.0 release19:35
clarkbya shouldn't need to happen ebfore the merge19:35
clarkbor at any other specific time19:35
corvusbut i do think that we owe it to our contributors to do it at some point.  at least spend a few seconds on each one.19:35
fungigranted many (most?) will merge-conflict if they don't already19:35
pabelangerShrews: nodepool-builder still using old syntax, need to updated to new format19:35
*** andreas_s has quit IRC19:35
pabelangerShrews: and switched to python319:36
clarkbI can try taking a first pass through it and categorize once I am done with the zuulv3-issues etherpad19:36
fungii started trying to go through those back in december but was honestly pretty lost19:36
clarkb#action clarkb to take pass through old zuul and nodepool master branch changes to at least categorize changes19:36
pabelangerShrews: old: http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/nodepool.yaml new: http://git.openstack.org/cgit/openstack-infra/project-config/tree/nodepool/nl01.openstack.org.yaml19:36
corvusclarkb: thanks19:36
corvusmaybe we can establish a tree19:36
pabelangerShrews: and we cannot use nb01.openstack.org.yaml as it doesn't have all providers listed for uploading images19:37
clarkbother than the old master changes are there any concerns realted to merging the two branches on nodepool and zuul? I put details on what I think the process will be in the mailing list19:37
clarkbI also think we want to do both at the same time19:37
corvusclarkb: agreed, both at once.  and yeah, i think we'll just have a bunch of changes we'll need to re-propose.19:38
clarkbcorvus: might also be worth an email to the openstack dev list and the new zuul announce list saying "we are doing this" maybe send that nowish?19:38
corvuswe can let folks know if they had open changes on v3, they'll need to repropose them.19:39
corvusclarkb: sounds good, i'll do that.19:39
clarkbthanks19:39
corvus#action corvus send email to openstack-dev, openstack-infra, zuul-announce about feature branch merge19:39
corvusmaybe also third-party-ci-announce?19:40
clarkb++19:40
*** lpetrut has joined #openstack-meeting19:40
clarkbany other zuul items before we move on?19:40
corvusnak19:40
*** lpetrut has quit IRC19:40
clarkb#topic General topics19:41
*** openstack changes topic to "General topics (Meeting topic: infra)"19:41
clarkbThank you everyone that helped get us patched against meltdown19:41
clarkbas of this morning we no longer have any instances that ansible inventory knows about running old kernels19:41
clarkb(we had to delete a couple instances that were no longer used)19:41
fungiand nothing has melted down yet19:41
clarkbpabelanger also finished up infracloud patching19:41
corvusit's possible the zuul executors are a bit... overheated... :)19:42
fungithough we have a sinking suspicion it may be to blame for increased load on the zuul executors?19:42
fungiright, that19:42
clarkbwhile nothing has properly melted down I think we have seen some etra performance impact19:42
clarkbya19:42
*** andreas_s has joined #openstack-meeting19:42
clarkbwe should keep an eye out for that, unfortunately I think our only way to address that is bigger instances/more instances19:42
*** slaweq_ has joined #openstack-meeting19:42
clarkbsupposedly google managed to patch with minimal performance impact but not sure they have shared those details pubicly19:43
clarkband also spectre patches are rolling out to cpus and they may too have more performance impacts19:43
clarkbits a fun time all around19:43
pabelanger"fun"19:43
fungifor masochistic definitions of that word19:44
clarkbthanks again for everyone helping out on that19:44
clarkbthe next item is somewhat related to that: Infracloud19:44
pabelangeruntil the next firedrill19:44
*** harlowja has joined #openstack-meeting19:44
clarkbduring meltdown patching we lost the infracloud controller node due to bad disks ( we also lost at least 2 compute hosts)19:44
clarkbthe initial idea we had when patching last week was to rehome vanilla computes to the chocolate controller19:45
clarkbbut this morning an interesting email was forwarded to me19:45
clarkb"Unfortunately, HPE will not move forward with the donation of hardware at this time as there is a need to use this equipment for other organizational support purposes."19:45
mordredoh. my19:45
mordredreally?19:45
pabelangerouch19:45
clarkbthis has not been communicated directly to any of us from what I can tell19:45
mordredthey think they want to use those computers?19:45
clarkbmordred: ya that was my reaction :)19:45
clarkbBUT it is an indication we won't have the hardware for much longer and I think we should plan for that19:46
mordred++19:46
pabelangeragree19:46
corvushow hard is it to re-home choc compute?19:46
clarkbI'm inclined to just get my fix to nodepool for handling cloud outages in then use chocolate until they take it away from us19:46
*** slaweq_ has quit IRC19:46
corvuser, backwards19:46
clarkbcorvus: I'm not sure. I think we have to update tyhe config on all the computes then accept them on the controller?19:46
fungiyeah, this was in a heads-up i received from our contact at osu-osl whom we'd been talking to about relocating the deployment there19:46
pabelangerYah, i think it would just be config updates to add vanilla into chocolate19:47
corvusis it maybe worth doing that and keeping it up until they pull the plug?19:47
fungiso basically hpe told osu-osl this, but not us... no idea what the story really is19:47
*** slaweq_ has joined #openstack-meeting19:47
corvusbusy time and all19:47
clarkbcorvus: maybe? the vanilla hardware is far more flaky than chocolate based on patching experience19:47
pabelangerI mean, I'm happy to try adding vanilla to chocolate, if we want to give it a shot19:48
clarkbthere is a possibility that bad hard drives and or ram would cause problems if running on vanilla computes. I think we want ot monitor that closely if we rehome them19:48
clarkbI won't stop anyone from doing it :)19:48
clarkbjust want to make sure we have a common understanding of what may end up happening there soon19:48
corvusok, maybe not worth it19:48
fungipart of the complexity with the hpe/osu/osf triangle is that hpe can't donate hardware to a 501c(6) like osf, but can donate it to an educational institution like osu19:49
pabelangerI mean, they can't delete the domain name, so we have that going for us :D19:49
fungiso some communication was bypassing openstack people entirely and going between hpe and osu19:49
clarkbI do think if people want ot learn more about openstack they should have it, don't let me stop you. But I don't think it needs to be a priority.19:50
*** pcaruana has quit IRC19:50
clarkb(patching meltdown on infracloud felt like a priority last week due to the way meltdown could be exploited by VMs)19:51
fungiit's also a great opportunity if we have another organization who wants to donate hardware/hosting we might reboot it on19:51
*** andreas_s has quit IRC19:51
clarkbany other infracloud concerns/ideas/topics?19:52
fungiwe've heard from some off and on but nothing has really panned out so far19:52
clarkbfungi: ya19:52
*** slaweq_ has quit IRC19:52
*** dprince has quit IRC19:52
pabelangerfungi: yah, there have been some talks about what to do with tripleo-test-cloud-rh1 after OVB jobs move into RDO, but nothing 100% yet19:52
*** gouthamr has joined #openstack-meeting19:52
clarkbonly 8 minutes left /me continues on19:53
clarkb#topic Project Renames19:53
*** openstack changes topic to "Project Renames (Meeting topic: infra)"19:53
clarkbmordred: fungi ^ any new progress on making these doable with zuul v3?19:53
clarkbI think I had changes pulled up to review last week then metldown patching happened and my brain turned to mus19:53
*** dustins has joined #openstack-meeting19:53
fungii haven't touched it at all, no19:53
mordredclarkb: I think the jeblair patch to remove names is the biggest thing19:54
clarkbmordred: is that in or do i still need to go review it?19:54
* clarkb seems to recall the zuul changes made it in now we have to update configs?19:54
mordredthe patch to remove the need for names is in and running19:54
mordredI think he patch-bombed already too19:55
clarkbwoot19:55
mordredwe also may need to  make non-existent required-projects non-fatal from a zuul config loading perspective19:55
clarkboh right taht was the thing that came up last week19:55
clarkbfatal to the job but not zuul as a whole19:55
corvusno i haven't patch-bombed; i mentioned that earlier.  but we don't have to wait on that -- just go ahead and remove the project name from any projects that need renaming.19:55
fungiand there was talk about ditching the system-required template in favor of implicit templates?19:55
mordredjobs that are referencing renamed projects in required-projects will still need to be fixed for the job to work - but there is a difference between a broken job and zuul not eing able to start19:56
mordredcorvus: ++19:56
corvuscoincidentally, we found another reason to make required-projects non-fatal -- it lets us do some cool things with cross-repo-dependencies19:56
clarkbcorvus: is that something you think you'll be adding too then?19:56
fungican we stop using system-required? afaik it does nothing at the moment because we're no longer running merge-check jobs19:56
clarkb(we don't need a volunteer for the feature?)19:56
corvusso i think that's likely to happen (it's got 2 things going for it now)19:57
*** david-lyle has quit IRC19:57
clarkbsounds like we might be able to do renames soon then :)19:57
clarkb#topic open discussion19:57
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:57
*** david-lyle has joined #openstack-meeting19:57
clarkbreally quickly before we run out of time? anything else?19:57
fungiand if we need something like system-required in the future we can switch to an implicit template at that time?19:57
corvushow urgent is it?  can we do a rename without that?  could we say we'll do a rename with disabling/re-enabling the job for now?19:57
clarkbianw and linaro are working on uefi + gpt support in dib so that we can built arm64 images19:58
clarkbmordred: ^ I think you have the best grasp of how badly that affects your rename19:58
pabelangerlooking to start gerrit upgrade testing for next week on review-dev.o.o19:58
fungii don't suppose dropping system-required is urgent, just simplifies project renames and new project creation to have on fewer place to potentially need to list a project19:58
fungis/on fewer/one fewer/19:59
corvusi'm hoping to do that soon, but honestly, i'd like to devote more time to 3.0-blocker reviews and memory improvements first, if possible.  that would probably set it back a few weeks.19:59
mordredcorvus: looking at codesearch, I think the one I was most concerned about from a rename perspective is only listed in required-projects in jobs in 2 repos19:59
mordredcorvus: so I think yes, removing/altering the test jobs then doing rename seems fine19:59
clarkbpabelanger: maybe we can sync up on that again this week as I will be largely afk next week19:59
ianwwill keep fiddling on gpt stuff; we also got new node builds out with pti ... i guess nothing has exploded yet19:59
*** bobh has quit IRC19:59
corvusok.  i'll keep it in mind as a target of opportunity, but not put it at the top of the list.20:00
clarkbcorvus: mordred fungi sounds like a plan, maybe we can schedule a project rename next meeting?20:00
pabelangerclarkb: sure, recap would be fine20:00
clarkband now we are out of time20:00
fungiclarkb: wfm20:00
clarkbThank you everyone!20:00
corvusclarkb: thanks!20:00
fungithanks clarkb!20:00
clarkb#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
openstackMeeting ended Tue Jan 16 20:00:41 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-01-16-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-01-16-19.01.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-01-16-19.01.log.html20:00
*** Shrews has left #openstack-meeting20:02
*** slaweq_ has joined #openstack-meeting20:13
*** gagehugo has left #openstack-meeting20:13
*** liyi has joined #openstack-meeting20:16
*** e0ne has joined #openstack-meeting20:17
*** liyi has quit IRC20:20
*** fzdarsky is now known as fzdarsky|afk20:28
*** dprince has joined #openstack-meeting20:31
*** ykatabam has joined #openstack-meeting20:31
*** deathsparton has joined #openstack-meeting20:33
*** e0ne has quit IRC20:33
*** efried_nomnom is now known as efried20:42
*** bobh has joined #openstack-meeting20:45
*** rmcall_ has quit IRC20:45
*** makowals has joined #openstack-meeting20:45
*** deathsparton has quit IRC20:48
*** rmcall_ has joined #openstack-meeting20:49
*** bobh has quit IRC20:51
*** artom has quit IRC20:52
*** bobh has joined #openstack-meeting20:54
*** deathsparton has joined #openstack-meeting20:57
*** bobh has quit IRC20:59
*** deathsparton has quit IRC21:00
*** haint_ has quit IRC21:01
*** haint_ has joined #openstack-meeting21:02
*** artom has joined #openstack-meeting21:02
*** armax has quit IRC21:10
*** markstur_ has quit IRC21:11
*** bobh has joined #openstack-meeting21:12
*** david-lyle has quit IRC21:12
*** david-lyle has joined #openstack-meeting21:23
*** diablo_rojo has quit IRC21:27
*** diablo_rojo has joined #openstack-meeting21:27
*** felipemonteiro has joined #openstack-meeting21:35
*** archit has quit IRC21:35
*** esberglu has quit IRC21:37
*** dprince has quit IRC21:44
*** armstrong has joined #openstack-meeting21:45
*** pchavva has quit IRC21:48
*** archit has joined #openstack-meeting21:50
*** esberglu has joined #openstack-meeting21:50
*** armax has joined #openstack-meeting21:51
*** slaweq_ has quit IRC21:51
*** rmk has joined #openstack-meeting21:52
*** rmk has quit IRC21:52
*** rmk has joined #openstack-meeting21:52
*** rossella_s has quit IRC21:53
*** rossella_s has joined #openstack-meeting21:54
*** rmcall_ has quit IRC21:55
*** eharney has quit IRC21:55
*** makowals has quit IRC21:57
*** mchiappero has quit IRC22:00
*** rbowen has quit IRC22:02
*** rossella_s has quit IRC22:04
*** rossella_s has joined #openstack-meeting22:08
*** bobh has quit IRC22:09
*** armstron_ has joined #openstack-meeting22:10
*** armstron_ has quit IRC22:10
*** armstrong has quit IRC22:13
*** fnaval has joined #openstack-meeting22:14
*** archit has quit IRC22:18
*** dustins has quit IRC22:18
*** spilla_ has joined #openstack-meeting22:20
*** spilla_ has quit IRC22:21
*** haint_ has quit IRC22:22
*** haint_ has joined #openstack-meeting22:22
*** spilla has quit IRC22:23
*** gouthamr has quit IRC22:27
*** liyi has joined #openstack-meeting22:28
*** rcernin has joined #openstack-meeting22:31
*** fnaval has quit IRC22:31
*** liyi has quit IRC22:32
*** pchavva has joined #openstack-meeting22:33
*** fnaval_ has joined #openstack-meeting22:33
*** blowfish has joined #openstack-meeting22:35
blowfishhi22:35
*** jamesmcarthur has quit IRC22:36
*** blowfish has quit IRC22:41
*** felipemonteiro has quit IRC22:42
*** jamesmcarthur has joined #openstack-meeting22:43
*** rossella_s has quit IRC22:52
*** jroll has quit IRC22:53
*** tpsilva has quit IRC22:54
*** edmondsw has quit IRC22:55
*** rossella_s has joined #openstack-meeting22:55
*** edmondsw has joined #openstack-meeting22:56
*** jroll has joined #openstack-meeting22:58
*** jamesmcarthur has quit IRC22:59
*** VW has quit IRC22:59
*** edmondsw has quit IRC23:00
*** rbudden has quit IRC23:00
*** rossella_s has quit IRC23:00
*** jamesmcarthur has joined #openstack-meeting23:00
*** rossella_s has joined #openstack-meeting23:02
*** rbudden has joined #openstack-meeting23:07
*** rossella_s has quit IRC23:08
*** rossella_s has joined #openstack-meeting23:12
*** claudiub has quit IRC23:31
*** sshnaidm is now known as sshnaidm|off23:42
*** andreas_s has joined #openstack-meeting23:49
*** liyi has joined #openstack-meeting23:49
*** rossella_s has quit IRC23:51
*** andreas_s has quit IRC23:53
*** erlon has quit IRC23:53
*** liyi has quit IRC23:54
*** rossella_s has joined #openstack-meeting23:54

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