Tuesday, 2017-08-01

*** yamamoto has quit IRC00:01
*** fnaval has joined #openstack-meeting00:02
*** yamamoto has joined #openstack-meeting00:05
*** xyang1 has quit IRC00:11
*** chyka has quit IRC00:13
*** ricolin has joined #openstack-meeting00:14
*** gmann has quit IRC00:16
*** gmann has joined #openstack-meeting00:16
*** vishwana_ has joined #openstack-meeting00:18
*** noslzzp has joined #openstack-meeting00:19
*** edmondsw has joined #openstack-meeting00:21
*** caowei has joined #openstack-meeting00:22
*** vishwanathj has quit IRC00:22
*** edmondsw has quit IRC00:25
*** aeng has quit IRC00:29
*** mtanino_ has quit IRC00:30
*** mriedem has quit IRC00:30
*** kiennt has joined #openstack-meeting00:32
*** armax has quit IRC00:34
*** VW has joined #openstack-meeting00:35
*** wanghao has joined #openstack-meeting00:36
*** slaweq has joined #openstack-meeting00:36
*** mriedem has joined #openstack-meeting00:38
*** harlowja has quit IRC00:38
*** VW has quit IRC00:39
*** slaweq has quit IRC00:42
*** zhurong has joined #openstack-meeting00:43
*** thorst_afk has joined #openstack-meeting00:46
*** kiennt has quit IRC00:47
*** emagana has quit IRC00:47
*** haukebruno has joined #openstack-meeting00:50
*** kiennt has joined #openstack-meeting00:51
*** emagana has joined #openstack-meeting00:53
*** thorst_afk has quit IRC00:54
*** _pewp_ has quit IRC00:54
*** https_GK1wmSU has joined #openstack-meeting00:56
*** https_GK1wmSU has quit IRC00:56
*** dmacpher has joined #openstack-meeting00:56
*** _pewp_ has joined #openstack-meeting00:57
*** emagana has quit IRC00:58
*** annabelleB has quit IRC00:59
*** https___GK1wmSU has joined #openstack-meeting01:03
*** kevzha01_ has joined #openstack-meeting01:03
*** https___GK1wmSU has quit IRC01:03
*** unicell has quit IRC01:05
*** YanXing_an has joined #openstack-meeting01:06
*** sdague has quit IRC01:08
*** iceyao has joined #openstack-meeting01:09
*** kaisers_ has joined #openstack-meeting01:12
*** kevzha01_ has quit IRC01:16
*** kaisers has quit IRC01:16
*** kevinz has joined #openstack-meeting01:16
*** s3wong has quit IRC01:21
*** yamamoto has quit IRC01:25
*** julim has joined #openstack-meeting01:27
*** thorst_afk has joined #openstack-meeting01:29
*** yamamoto has joined #openstack-meeting01:29
*** gcb has joined #openstack-meeting01:30
*** ekcs has quit IRC01:33
*** litao__ has joined #openstack-meeting01:33
*** ricolin has quit IRC01:34
*** gcb has quit IRC01:37
*** thorst_afk has quit IRC01:38
*** thorst_afk has joined #openstack-meeting01:38
*** gcb has joined #openstack-meeting01:39
*** https_GK1wmSU has joined #openstack-meeting01:41
*** YanXing_an has quit IRC01:41
*** https_GK1wmSU has left #openstack-meeting01:41
*** shu-mutou-AWAY is now known as shu-mutou01:42
*** thorst_afk has quit IRC01:43
*** Apoorva has quit IRC01:48
*** ykatabam has quit IRC01:49
*** yamamoto has quit IRC01:51
*** cloudrancher has quit IRC01:52
*** armax has joined #openstack-meeting01:52
*** YanXing_an has joined #openstack-meeting01:53
*** ykatabam has joined #openstack-meeting01:53
*** cloudrancher has joined #openstack-meeting01:53
*** thorst_afk has joined #openstack-meeting01:55
*** thorst_afk has quit IRC01:55
*** yamamoto has joined #openstack-meeting01:56
*** rmascena has quit IRC01:58
*** slaweq has joined #openstack-meeting01:59
*** ykatabam has quit IRC02:00
*** slaweq has quit IRC02:04
*** yamamoto has quit IRC02:07
*** yamahata has quit IRC02:08
*** cloudrancher has quit IRC02:09
*** cloudrancher has joined #openstack-meeting02:09
*** mriedem has quit IRC02:10
*** thorst_afk has joined #openstack-meeting02:11
*** bkopilov_ has quit IRC02:11
*** VW has joined #openstack-meeting02:17
*** rossella_s has quit IRC02:19
*** galstrom_zzz is now known as galstrom02:19
*** yamamoto has joined #openstack-meeting02:19
*** rossella_s has joined #openstack-meeting02:21
*** hongbin has joined #openstack-meeting02:21
*** harlowja has joined #openstack-meeting02:22
*** thorst_afk has quit IRC02:25
*** bobh has joined #openstack-meeting02:26
*** galstrom is now known as galstrom_zzz02:30
*** esberglu has joined #openstack-meeting02:39
*** tovin07_ has joined #openstack-meeting02:40
*** spn has quit IRC02:41
*** spn has joined #openstack-meeting02:41
*** kiennt has quit IRC02:41
*** kiennt has joined #openstack-meeting02:42
*** ricolin has joined #openstack-meeting02:42
*** galstrom_zzz is now known as galstrom02:44
*** harlowja has quit IRC02:44
*** esberglu has quit IRC02:44
*** esberglu has joined #openstack-meeting02:49
*** baoli_ has quit IRC02:50
*** diablo_rojo has quit IRC02:51
*** annabelleB has joined #openstack-meeting02:52
*** raddaoui has quit IRC02:54
*** hongbin_ has joined #openstack-meeting02:55
*** shubhams has joined #openstack-meeting02:56
*** Namrata has joined #openstack-meeting02:57
*** hongbin has quit IRC02:57
*** Shunli has joined #openstack-meeting02:58
*** hongbin has joined #openstack-meeting02:59
*** aeng has joined #openstack-meeting03:00
hongbin#startmeeting zun03:00
openstackMeeting started Tue Aug  1 03:00:21 2017 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#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-08-01_0300_UTC Today's agenda03:00
hongbin#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
mkraiMadhuri o/03:00
NamrataNamrata03:00
*** hongbin_ has quit IRC03:00
shubhamsshubham03:00
*** markstur has quit IRC03:00
kevinzkevinz03:00
*** lakerzhou has joined #openstack-meeting03:00
spno/03:01
*** Namrata_ has joined #openstack-meeting03:01
*** markstur has joined #openstack-meeting03:01
Shunlishunli03:01
hongbinthanks for joining the meeting mkrai Namrata shubhams kevinz spn Shunli03:01
lakerzhoulakerzhou03:01
hongbinthanks for joining lakerzhou03:01
hongbinok, let's get started03:01
hongbin#topic Announcements03:01
*** openstack changes topic to "Announcements (Meeting topic: zun)"03:01
*** yamamoto has quit IRC03:01
hongbin1. python-zunclient 0.4.0 is released for Pike.03:01
hongbin#link https://review.openstack.org/#/c/487979/03:02
hongbinyou should see the stable/pike branch has been cut for python-zunclient03:02
mkraiGreat :)03:02
hongbinthat means all patches for python-zunclient are for Q now03:02
hongbinif you want to submit for pike, we need to do backporting03:03
hongbin2. The deadline of releasing Zun server is at the week of Aug 2103:03
hongbin#link https://releases.openstack.org/pike/schedule.html03:03
hongbini plan to cut the server by Aug 2103:04
hongbinif you have patches that needs to go into pike, please submit it before Aug 2103:04
hongbinso far, any comment for hte release schedule?03:04
mkraiI would like the clear container one to go. Will submit patches soon03:04
mkraiWorks for me03:05
hongbinmkrai: if it can make the pike, that would be great, but remember the zunclient has cut03:05
mkraiOhh I think the server might suffice03:06
mkraiBut will check03:06
*** yamamoto has joined #openstack-meeting03:06
hongbinok03:06
hongbinbtw, this is the first release of zun that integrates with official openstack release03:06
hongbinok, next one03:07
hongbin3. Etcd job has been moved to experimental queue (type "check experimental" to run this job)03:07
hongbin#link https://review.openstack.org/#/c/471840/03:07
hongbini put it in experimental queue because it was failing for a while03:07
hongbinputting it as experimental means this job won't be triggered on submiting patch03:08
*** galstrom is now known as galstrom_zzz03:08
hongbinhowever, it can be manually trigger by typping "check experimental"03:08
hongbinthis will save the infra resources, and clear some noice for contributors03:08
hongbinany comment for this?03:09
hongbinor concern?03:09
mkraiAfter the issue is fixed, we might want to make it voting03:09
kienntGreat, what about this patch?03:09
kiennt#link https://review.openstack.org/#/c/472538/03:09
hongbinmkrai: yes, absolutely03:09
mkraiI will be resubmitting the patch for this fix03:09
hongbinwe can move it back to voting anytime we want03:09
mkraikiennt: Will look this week03:09
kienntmkrai: Hope it will works.03:10
hongbinok, i clear all the annoucements03:10
hongbinanyone else has an annoucement?03:10
*** emagana has joined #openstack-meeting03:10
mkraiVote for Zun presentation for Sydney summit :)03:11
hongbinoh, yes03:11
mkraiVoting is open till Aug 303:11
hongbin#link https://www.openstack.org/summit/sydney-2017/vote-for-speakers/03:11
hongbinok, move on03:12
hongbin#topic Review Action Items03:12
*** openstack changes topic to "Review Action Items (Meeting topic: zun)"03:12
hongbin1. mkrai works on a patch to make image validation configurable03:12
hongbinmkrai: status?03:12
*** Namrata_ has quit IRC03:12
mkraiSorry didn't get much time to work on this. I will create a bug for this03:12
mkraiAnd will submit the patch this week03:12
hongbinack, np03:12
hongbinsure03:13
hongbinthis issue doesn't look urgent for me, so take your time :)03:13
hongbinmkrai: ^^03:13
mkraiOk thanks03:13
hongbinok, next topic03:13
hongbin#topic Cinder integration03:13
*** openstack changes topic to "Cinder integration (Meeting topic: zun)"03:13
hongbinfor this one, i didn't have a chance to get back to it03:14
*** lbragstad_ has joined #openstack-meeting03:14
*** lbragstad has quit IRC03:14
*** vishnoianil has quit IRC03:15
hongbini will skip it this week, if there is no comment for it03:15
hongbinhopefully, i can get a wip patch up at next week03:15
hongbinok, move on03:16
hongbin#topic Introduce container composition (kevinz)03:16
*** openstack changes topic to "Introduce container composition (kevinz) (Meeting topic: zun)"03:16
hongbinkevinz: ^^03:16
*** vishnoianil has joined #openstack-meeting03:16
kevinzHi hongbin03:16
hongbinkevinz: hey03:17
kevinzSubmit several patches about capsule, and I will push some test cases this week03:17
kevinzAlso add etcd database operation about capsule03:17
*** markstur has quit IRC03:17
kevinzAlso add support for create multiple capsule, such as "zun capsule create -f **.yaml --count 3"03:18
hongbinlike a replication controller?03:19
kevinzhongbin: Aha, good point,,,03:19
kevinzhongbin: Just support create more capsules with one command, like container create03:20
hongbinkevinz: oh, i see, that is different03:20
kevinzhongbin: Have not consider it as  replication controller,,,03:20
*** yamamoto has quit IRC03:21
hongbinkevinz: keep in mind that implementing RC might need a significant amount of work ...03:21
kevinzhongbin: Yeah I see..03:22
hongbinkevinz: which might need another spec if you propose to go to that path03:22
mkraihongbin: kevinz Do we want to implement rc like concept in Zun?03:22
kevinzhongbin: OK03:22
*** bobh has quit IRC03:23
hongbinmkrai: i don't have strong opinion on that03:23
kevinzmkrai: Have not decide also03:23
mkraiOk03:23
*** rbudden has quit IRC03:23
hongbinany other comment on this topic?03:24
kevinzthat's all from me03:24
*** yamamoto has joined #openstack-meeting03:24
hongbinok, thanks kevinz03:25
hongbin#topic NFV use cases (lakerzhou)03:25
*** openstack changes topic to "NFV use cases (lakerzhou) (Meeting topic: zun)"03:25
hongbinlakerzhou: there?03:25
lakerzhouyes03:25
hongbinlakerzhou: want to lead this discussion?03:25
hongbinlakerzhou: btw, i saw you have a patch for that03:26
hongbin#link https://review.openstack.org/#/c/484496/03:26
lakerzhouThe spec is ready for final review. I am planning to run test on docker container directly first03:26
hongbinack03:27
*** gouthamr has quit IRC03:28
*** Namrata has quit IRC03:28
lakerzhouI don't have more update on that one, team, please review and let me know if you have any questions or concerns03:28
hongbin:)03:28
*** kiennt_ has joined #openstack-meeting03:29
*** Namrata has joined #openstack-meeting03:29
*** bkopilov_ has joined #openstack-meeting03:29
lakerzhouI think we are ready for implementation03:29
hongbinyes, i think so03:29
hongbinmost kuryr people have given +1, i guess they will be happy to take the patches03:29
lakerzhougreat news if they can take it.03:30
hongbinyes03:30
lakerzhoushould we create a BP for kuryr03:30
*** annabelleB has quit IRC03:31
hongbinperhaps you can, but don't need to duplicate another spec to kuryr03:31
lakerzhouhongbin, sounds good, I will do it tomorrow.03:31
hongbinthanks lakerzhou03:31
hongbinall, any comment for this topic? or question for lakerzhou ?03:31
kevinzthx lakerzhou03:32
kevinzthat will add great value to zun03:32
lakerzhounp, thanks all the helps and comments in reviewing the spec03:32
*** YanXing_an has quit IRC03:32
hongbinok, next topic03:33
hongbin#topic Default API version policy03:33
*** openstack changes topic to "Default API version policy (Meeting topic: zun)"03:33
hongbin#link http://lists.openstack.org/pipermail/openstack-dev/2017-July/120207.html03:33
hongbinShunli: there?03:33
*** kiennt_ has quit IRC03:33
Shunliyes03:33
hongbinShunli: want to lead the discussion of this topic?03:34
Shunliok03:34
Shunlithe topic is about when and how to bump the default api version.03:34
Shunlinow zun client always use the latest api version as the default api version.03:35
ShunliI want to know how you guys think about the defautl api version policy.03:36
*** yamamoto has quit IRC03:36
Shunlishould we bump the default api version everytime the api version changed?03:36
Shunlior we bump the default api version when a major version released?03:36
*** marst has joined #openstack-meeting03:36
*** slaweq has joined #openstack-meeting03:37
mkraiI am not sure how the microversion works. How does other project handle it?03:37
ShunliI only found a ironic client which seem do not bump the default api version when every api version changed.03:38
*** harlowja has joined #openstack-meeting03:38
hongbin#link https://specs.openstack.org/openstack/ironic-specs/specs/approved/cli-default-api-version.html03:38
Namratathey are taking latest as the default api version03:39
hongbinthis is how i understand their approach03:40
hongbinfirst, at client side, it defines a list of versions it supports03:40
hongbinsecond, in server side, define the latest api versions03:41
hongbinthe final chosen api version is negotiated between client and server03:41
hongbinbasically, it will pick the latest version that both client and server support03:42
hongbinfor example, client support 1.1 - 1.3, server has up to 1.403:42
hongbinthe chosen version will be 1.303:42
*** slaweq has quit IRC03:42
hongbinthat is how i understand their spec03:42
mkraiis this approach already supported in zunclient?03:42
hongbinmkrai: no, we hard-code to 'latest' right now03:43
mkraiit seems if we have this approach supported in zunclient, its good03:44
mkraiAnd also we should bump the default version to latest.03:44
*** yamamoto has joined #openstack-meeting03:44
Shunliok, seems you guys all think we should always use the latest as the default api version.03:45
mkraiShunli: yes it makes no harm I suppose03:45
Namratai also agree using the latest one03:46
mkraihongbin: Can we ask Kenichi Ohmichi from Nova core about this?03:46
mkraiHe has been doing all the work in api microversioning03:46
hongbinmkrai: yes, i can take an AI for that03:47
mkraihongbin: Thanks03:47
hongbin#action hongbin ask nova core about how to deal with api microversion03:47
Shunlimy only concern is that we should alway expose stable cli/api to user.03:47
mkraiShunli: Agree03:48
hongbinthis is a good point03:48
hongbini think there is a middle ground03:48
spnn - 1 approach?03:48
hongbinfor stable branch, we could hard-code a stable version03:48
hongbinfor master branch, pick the latest version03:48
hongbinspn: go ahead if you have one :)03:49
spnhongbin: we have a stable branch right?03:49
Shunli+1 for hongbin's proposal03:49
hongbinspn: yes, starting for this release, we have03:49
spnthat should be fine I guess03:49
*** lakerzhou has quit IRC03:50
hongbinok, seems we all agree on this one03:50
mkrai+103:51
hongbinany further remark?03:51
Shunlii will submit patch use the latest as the default api version for host list&show03:51
*** dbecker has quit IRC03:51
hongbinShunli: thx03:51
hongbin#topic Open Discussion03:51
*** openstack changes topic to "Open Discussion (Meeting topic: zun)"03:51
hongbinanyone has an additional topic to bring up?03:52
mkrainone from me03:52
Shunlino03:52
spnone thing03:52
hongbinspn: go ahead03:53
spnI was looking for a architecture diagram of zun on the main page of ours03:53
spnlike how magnum has it03:53
spnpossible?03:53
hongbinsure03:53
mkraispn: +103:53
hongbini can take an AI for that03:53
hongbin#action hongbin pose an architecture diagram at the zun wiki page03:54
spnalso I am did not find a page03:54
spnwhich has our roadmap listed03:54
hongbin#link https://wiki.openstack.org/wiki/Zun03:54
spndid I miss a page which has it?03:54
hongbinspn: i can try to summarize the roadmap in some way, how other projects present their roadmap?03:55
spnI showed the zun page to my exec director and the first question he asked me is what is in the roadmap03:55
hongbini see03:55
spnI could not find it on wiki.03:55
*** vishnoianil has quit IRC03:56
hongbinyes, i am thinking how to summarize it03:56
*** iceyao has quit IRC03:56
spn+1 that would be great.03:56
hongbinsince i don't think other projects summarize their roadmap in wiki as well03:56
spnwhatever is the best location03:57
*** vishnoianil has joined #openstack-meeting03:57
hongbinok, i will try that03:57
kiennthongbin,: Just one thing, do you think we should change zun/image/glance/utils to a class like NeutronAPI? Like your new patches03:57
*** ijw has quit IRC03:57
hongbinkiennt: i don't have strong opinion on it, if you have a specific patch up for review, i will leave my comment03:58
kiennthongbin: sure, i'll try to do it.03:58
*** samP has joined #openstack-meeting03:58
hongbinkiennt: btw, thanks for your reviews and patches, they are all helpful :)03:59
*** diga has joined #openstack-meeting03:59
kiennthongbin: my pleasure :)03:59
digasorry I got very late03:59
hongbinall, time is up03:59
hongbinthanks for joining the meeting, hope to see you next time03:59
hongbin#endmeeting03:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:59
digahongbin: will ping you separately03:59
mkraiThnks everyone03:59
openstackMeeting ended Tue Aug  1 03:59:53 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-08-01-03.00.html03:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-08-01-03.00.txt03:59
spnhave a nice day03:59
openstackLog:            http://eavesdrop.openstack.org/meetings/zun/2017/zun.2017-08-01-03.00.log.html03:59
*** abhishekk_ has joined #openstack-meeting04:00
samPHi all for Masakari04:00
abhishekk_O/04:00
*** rkmrHonjo has joined #openstack-meeting04:00
*** ykatabam has joined #openstack-meeting04:01
samPcan anyone start the meeting today?04:01
samPI need to attend some other meeting.. I will join after that..04:02
*** noslzzp has quit IRC04:02
*** izumi_ has joined #openstack-meeting04:03
*** tpatil_ has joined #openstack-meeting04:03
samPtpatil_: rkmrHonjo could you please start the Masakari meeting today?04:03
abhishekk_rkmrHonjo: could you please start the meeting04:03
rkmrHonjoOK, I start this meeting.04:03
samPrkmrHonjo: thanks04:04
*** mtanino has quit IRC04:04
*** yamamoto has quit IRC04:04
rkmrHonjoPlease wait...04:04
*** abhishekk has joined #openstack-meeting04:04
rkmrHonjo#startmeeting masakari04:05
openstackMeeting started Tue Aug  1 04:05:03 2017 UTC and is due to finish in 60 minutes.  The chair is rkmrHonjo. Information about MeetBot at http://wiki.debian.org/MeetBot.04:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:05
*** openstack changes topic to " (Meeting topic: masakari)"04:05
openstackThe meeting name has been set to 'masakari'04:05
rkmrHonjoOK, let's start.04:05
*** hongbin has quit IRC04:05
*** abhishekk_ has quit IRC04:05
rkmrHonjo#topic High priority items04:05
*** openstack changes topic to "High priority items (Meeting topic: masakari)"04:05
rkmrHonjoDo you have any items to discuss?04:05
*** shubhams has quit IRC04:06
rkmrHonjook, let's go to next topic.04:06
rkmrHonjo#topic Bugs (stuck/critical)04:06
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: masakari)"04:06
*** links has joined #openstack-meeting04:07
*** dbecker has joined #openstack-meeting04:07
rkmrHonjoDo you have any bugs(bug fixes) to discuss?04:07
tpatil_# link : https://review.openstack.org/#/c/469029/04:08
tpatil_#link: https://review.openstack.org/#/c/469029/04:09
*** yamamoto has joined #openstack-meeting04:09
tpatil_Needs review04:09
*** izumi_ has quit IRC04:09
rkmrHonjoSorry, I'll review it.04:09
*** ykatabam has quit IRC04:09
Dinesh_BhorrkmrHonjo: thanks04:10
*** ykatabam has joined #openstack-meeting04:10
tpatil_This patch fixes multiple LP bugs04:10
*** psachin has joined #openstack-meeting04:10
rkmrHonjoYeah. I think this is important.04:10
rkmrHonjoDo you have any other items?04:12
rkmrHonjo#link https://review.openstack.org/#/c/481509/04:13
*** abhishekk has quit IRC04:13
rkmrHonjoThis patch was created by samP. This requires one more +2.04:13
tpatil_I will review this patch today04:14
rkmrHonjotpatil: thank you!04:14
*** abhishekk has joined #openstack-meeting04:16
rkmrHonjoCan we go to next topic?04:16
*** ekcs has joined #openstack-meeting04:16
tpatil_yes04:17
rkmrHonjo#topic Discussion points04:17
*** openstack changes topic to "Discussion points (Meeting topic: masakari)"04:17
rkmrHonjoI skip "Application for become OpenStack oficial project". Because samP is not there.04:18
rkmrHonjo"Install guide document"04:19
rkmrHonjoShould we write installation documents for each distributions now? Ubuntu, Debian package is not prepared now.04:19
abhishekkyes that's the reason I have kept workflow -104:20
tpatil_We will need to check how to submit patches in Ubuntu to publish Debian package04:20
abhishekkon patch, https://review.openstack.org/48697204:20
abhishekk#link https://review.openstack.org/48697204:20
rkmrHonjoabshihekk: Can you split the patch? I afraid that public package will take long time.04:21
*** iceyao has joined #openstack-meeting04:21
abhishekkrkmrHonjo: I can remove installation guide for now04:21
rkmrHonjoabhishekk: Can you leave common steps? e.g. Write configuration file04:22
*** ekcs has quit IRC04:23
tpatil_Also, let's split patches for developer guide, architecture and operators guides04:23
abhishekkok04:23
rkmrHonjotpatil, abhishekk: thanks.04:23
rkmrHonjoBy the way, takahara wrote installation documents for masakari-monitors. I'm reviewing it.04:24
rkmrHonjo#link https://review.openstack.org/#/c/489095/04:25
*** iceyao has quit IRC04:26
rkmrHonjoI think that this document may be help to create devstack plugin of masakari-monitors.04:26
*** thorst_afk has joined #openstack-meeting04:26
Dinesh_BhorrkmrHonjo: ok, thanks. I will check this04:27
*** ijw has joined #openstack-meeting04:27
rkmrHonjoDinesh: thanks!04:27
rkmrHonjoOK, let's go to next item.04:27
rkmrHonjo"Make nova "on_shared_storage" option configurable for evacuate API"04:28
rkmrHonjoOops, this was already merged.04:28
rkmrHonjo#link https://review.openstack.org/#/c/483313/04:28
rkmrHonjoI'll remove this item next week.04:29
rkmrHonjoNext item is..."04:30
rkmrHonjoInstance gets auto-confirmed(uses new flavor) if masakari evacuates an instance which was partially resized(resize-confirm is not performed)"04:30
rkmrHonjoAre there any updates?04:30
abhishekkNo updates yet04:30
*** thorst_afk has quit IRC04:31
rkmrHonjoOK. Next item is "recovery method customization"04:31
*** ijw has quit IRC04:31
abhishekkWe will update the specs based on the recent PoC we have done04:33
tpatil_Abhishek will update specs https://review.openstack.org/#/c/458023/ based on the POC done to register actions in mistral service04:33
*** adisky__ has joined #openstack-meeting04:33
*** caowei has quit IRC04:33
tpatil_There is no need to make any changes in mistral service to add new actions as it support RestFul api to register actions using admin credentials04:34
tpatil_but there is one caveat, you need to restart mistral service in order to run those action in a workflow04:34
tpatil_we are checking how we can auto-register these newly added actions in mistral without restarting the mistral service04:35
tpatil_but for this to work, we may have to submit patch in mistral04:35
tpatil_Abhishek: Have you already updated the specs?04:36
abhishekknot yet04:36
tpatil_abhishekk: Ok04:37
rkmrHonjotpatil: Should we restart mistral only once? or every time?04:37
Dinesh_BhorrkmrHonjo: Whenever you add new actions and want them to be registered in mistral you need to restart mistral services04:38
tpatil_rkmrHonjo: you need to restart mistral service every time you register a new action, but in our case, we will register all required actions once, so you will need to restart mistral service only one time04:39
Dinesh_Bhoryes04:39
rkmrHonjoDinesh_Bhor, tpatil: Thanks. I understood.04:39
*** iceyao has joined #openstack-meeting04:39
rkmrHonjotpatil, abhishekk: When will you update?04:40
abhishekkrkmrHonjo: in a day or two04:41
rkmrHonjoabhishekk: Great. thank you.04:41
*** julim has quit IRC04:41
rkmrHonjoOK. Can I go to next item?04:42
tpatil_yes, please04:42
rkmrHonjo"Auto compute node registration"04:42
rkmrHonjo#link https://review.openstack.org/#/c/486483/04:43
rkmrHonjoThis feature automatically create host in specified segment. This will help operators.04:43
rkmrHonjoTakahara submit spec, please review it.04:44
rkmrHonjos/submit/submitted/04:44
*** iceyao has quit IRC04:44
tpatil_In the notification request, there is no information about failureover_segment, it contains host name04:44
rkmrHonjotpatil: Right.04:44
tpatil_Are you planning to add a failover_segment in the notification request?04:45
*** iceyao has joined #openstack-meeting04:45
rkmrHonjotpatil: No. This feature add failover_segment id to masakari-monitors configuration file. And it will be used for host registration.04:45
rkmrHonjoThis feature doesn't change notification API.04:46
tpatil_Ok, so masakari-monitors will call Add host Restful API to add this host in a particular failover_segment, correct?04:46
rkmrHonjotpatil: correct.04:46
tpatil_rkmrHonjo: Make sense04:47
*** abhishekk has quit IRC04:47
rkmrHonjotpatil: thanks.04:48
rkmrHonjoBy the way, implementation was already submitted.04:48
rkmrHonjo#link https://review.openstack.org/#/c/486484/04:48
rkmrHonjoOK, let's go to next item.04:49
rkmrHonjoNext item is..."masakari-manage db purge": support for purging notification records"04:49
*** unicell has joined #openstack-meeting04:49
*** abhishekk has joined #openstack-meeting04:50
tpatil_Specs are approved, implementation patch is up for review04:50
tpatil_#link: https://review.openstack.org/#/c/487430/04:50
*** kaisers_ has quit IRC04:51
rkmrHonjoDinesh_Bhor: I wrote some comments for that patch. Please check it.04:51
*** VW has quit IRC04:52
Dinesh_BhorrkmrHonjo: yes, I will, thanks04:52
*** VW has joined #openstack-meeting04:52
*** vishnoianil has quit IRC04:53
rkmrHonjoOK. Any other items?04:53
Dinesh_BhorTo enable Openstack proposal bot for masakari project, first we need to make all masakari projects python 3.5 compatible: https://git.openstack.org/cgit/openstack/requirements/tree/README.rst#n265.04:54
Dinesh_BhorSo for this I have submitted below patches in python-masakariclient and masakari-monitors: https://review.openstack.org/#/c/489118/, https://review.openstack.org/#/c/489117/04:55
tpatil_Dinesh_Bhor: I will review these patches04:55
*** epico has joined #openstack-meeting04:55
rkmrHonjoDinesh_Bhor: thanks. I'll review these, too.04:55
Dinesh_Bhortpatil_, rkmrHonjo: thanks you04:56
*** Namrata has quit IRC04:56
rkmrHonjoLet's go to AOB.04:56
rkmrHonjo#topic AOB04:56
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:56
rkmrHonjoDo you have items to discuss?04:57
tpatil_Do you think adding a horizon plugin for masakari project will be useful for operator?04:57
tpatil_In this plugin, it should be possible to add entities like failover segment, host etc.04:57
*** chyka has joined #openstack-meeting04:58
rkmrHonjoI think that will be useful.04:58
Dinesh_Bhorand check notification statuses04:58
tpatil_but most importantly, we should display the failover segment in graphical representation which will help operator to know if any of the hosts is in failed state04:58
*** VW_ has joined #openstack-meeting04:59
*** VW has quit IRC04:59
*** slaweq has joined #openstack-meeting04:59
tpatil_if it's in failed state, on click on that node, it will show all information about the current status of the notification to the operator04:59
rkmrHonjoBy the way...Some operators said that finding host is hard when they forgot relationships.05:00
rkmrHonjooops, time is over.05:00
rkmrHonjoIf you want to continue discussion, please talk it in ML or openstack-masakari channel.05:00
rkmrHonjothank you for all...05:01
tpatil_ok05:01
rkmrHonjo#endmeeting05:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:01
openstackMeeting ended Tue Aug  1 05:01:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-08-01-04.05.html05:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-08-01-04.05.txt05:01
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2017/masakari.2017-08-01-04.05.log.html05:01
*** abhishekk is now known as abhishekk|meetin05:01
*** tpatil_ has quit IRC05:02
*** chyka has quit IRC05:02
*** rkmrHonjo has quit IRC05:03
*** slaweq has quit IRC05:04
*** prateek has joined #openstack-meeting05:06
*** janki has joined #openstack-meeting05:06
*** ykatabam has quit IRC05:07
*** iceyao has quit IRC05:08
*** harlowja has quit IRC05:10
*** https_GK1wmSU has joined #openstack-meeting05:11
*** https__GK1wmSU has joined #openstack-meeting05:12
*** https_GK1wmSU has quit IRC05:12
*** https__GK1wmSU has quit IRC05:12
*** emagana has quit IRC05:15
*** https___GK1wmSU has joined #openstack-meeting05:16
*** https__GK1wmSU has joined #openstack-meeting05:16
*** https___GK1wmSU has left #openstack-meeting05:16
*** https__GK1wmSU has left #openstack-meeting05:16
*** arnewiebalck_ has joined #openstack-meeting05:18
*** VW_ has quit IRC05:20
*** kaisers has joined #openstack-meeting05:21
*** kaisers has quit IRC05:26
*** gcb has quit IRC05:29
*** gcb_ has joined #openstack-meeting05:29
*** chyka has joined #openstack-meeting05:29
*** lpetrut has joined #openstack-meeting05:32
*** chyka has quit IRC05:34
*** sridharg has joined #openstack-meeting05:35
*** iceyao has joined #openstack-meeting05:35
*** iceyao has quit IRC05:40
*** https_GK1wmSU has joined #openstack-meeting05:41
*** caowei has joined #openstack-meeting05:42
*** https___GK1wmSU has joined #openstack-meeting05:44
*** https___GK1wmSU has quit IRC05:44
*** https_GK1wmSU has quit IRC05:45
*** unicell has quit IRC05:47
*** unicell has joined #openstack-meeting05:48
*** YanXing_an has joined #openstack-meeting05:48
*** harlowja has joined #openstack-meeting05:51
*** kiennt has quit IRC05:57
*** yamahata has joined #openstack-meeting06:01
*** kiennt has joined #openstack-meeting06:01
*** iceyao has joined #openstack-meeting06:03
*** arnewiebalck_ has quit IRC06:04
*** esberglu has quit IRC06:06
*** esberglu has joined #openstack-meeting06:06
*** iceyao has quit IRC06:08
*** Alex_Staf has joined #openstack-meeting06:08
*** trinaths has joined #openstack-meeting06:09
*** rbartal has joined #openstack-meeting06:11
*** iceyao has joined #openstack-meeting06:12
*** esberglu has quit IRC06:15
*** markstur has joined #openstack-meeting06:16
*** markstur has quit IRC06:16
*** marios has joined #openstack-meeting06:19
*** yushb has joined #openstack-meeting06:19
*** tobberydberg has joined #openstack-meeting06:23
*** kaisers has joined #openstack-meeting06:23
*** tobberydberg has joined #openstack-meeting06:24
*** thorst_afk has joined #openstack-meeting06:28
*** https_GK1wmSU has joined #openstack-meeting06:28
*** oidgar has joined #openstack-meeting06:29
*** epico has quit IRC06:29
*** https_GK1wmSU has quit IRC06:30
*** thorst_afk has quit IRC06:32
*** https_GK1wmSU has joined #openstack-meeting06:35
*** kaisers has quit IRC06:35
*** oidgar has quit IRC06:35
*** https_GK1wmSU has quit IRC06:36
*** oidgar has joined #openstack-meeting06:37
*** ykatabam has joined #openstack-meeting06:40
*** lpetrut has quit IRC06:42
*** epico has joined #openstack-meeting06:51
*** harlowja has quit IRC06:51
*** ralonsoh has joined #openstack-meeting06:52
*** lpetrut has joined #openstack-meeting06:54
*** rcernin has joined #openstack-meeting06:55
*** alexchadin has joined #openstack-meeting06:56
*** anilvenkata has joined #openstack-meeting07:02
*** Shunli has quit IRC07:03
*** YanXing_an has quit IRC07:03
*** Shunli has joined #openstack-meeting07:03
*** YanXing_an has joined #openstack-meeting07:04
*** pcaruana has joined #openstack-meeting07:06
*** diga has quit IRC07:07
*** gibi_ is now known as gibi07:11
*** takahara has joined #openstack-meeting07:12
*** takahara has quit IRC07:12
*** treiz has joined #openstack-meeting07:15
*** emagana has joined #openstack-meeting07:27
*** aarefiev_afk is now known as aarefiev07:28
*** flanders_ has joined #openstack-meeting07:28
*** emagana has quit IRC07:31
*** kaisers has joined #openstack-meeting07:32
*** dpertin has joined #openstack-meeting07:38
*** slaweq_ has joined #openstack-meeting07:41
*** lpetrut has quit IRC07:43
*** igordcard has quit IRC07:47
*** slaweq_ has quit IRC07:47
*** igordcard has joined #openstack-meeting07:48
*** rcernin has quit IRC07:48
*** dmacpher has quit IRC07:49
*** rcernin has joined #openstack-meeting07:50
*** clarkb has quit IRC08:04
*** hashar has joined #openstack-meeting08:06
*** aloga has quit IRC08:17
*** aloga has joined #openstack-meeting08:17
*** clarkb has joined #openstack-meeting08:17
*** toscalix has joined #openstack-meeting08:17
*** abhishekk|meetin is now known as abhishekk08:24
*** abhishekk has left #openstack-meeting08:24
*** thorst_afk has joined #openstack-meeting08:27
*** abhishekk has joined #openstack-meeting08:29
*** markvoelker has quit IRC08:30
*** markvoelker has joined #openstack-meeting08:31
*** thorst_afk has quit IRC08:32
*** zhhuabj has quit IRC08:35
*** markvoelker has quit IRC08:35
*** e0ne has joined #openstack-meeting08:43
*** toscalix has quit IRC08:44
*** electrofelix has joined #openstack-meeting08:44
*** kaisers has quit IRC08:46
*** zhhuabj has joined #openstack-meeting08:47
*** priteau has joined #openstack-meeting08:48
*** jiaopengju has joined #openstack-meeting08:49
*** ricolin has quit IRC08:51
*** zeih has joined #openstack-meeting08:53
*** alexchadin has quit IRC08:53
*** toscalix has joined #openstack-meeting08:55
*** liujiong has joined #openstack-meeting08:55
*** vishnoianil has joined #openstack-meeting08:55
*** alexchadin has joined #openstack-meeting08:56
yuval#startmeeting karbor09:00
openstackMeeting started Tue Aug  1 09:00:24 2017 UTC and is due to finish in 60 minutes.  The chair is yuval. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** chenying has joined #openstack-meeting09:00
*** openstack changes topic to " (Meeting topic: karbor)"09:00
openstackThe meeting name has been set to 'karbor'09:00
*** yangyapeng has joined #openstack-meeting09:00
yuvalHello everybody and welcome to Karbor's biweekly meeting09:00
chenyinghi09:00
liujionghi yuanying chenying09:01
yuvalhey chenying09:01
liujionghi yuval09:01
zhonghua2hi09:01
yuvalhey liujiong09:01
liujiong:)09:01
yushbhey09:01
yuvalhey yushb09:02
jiaopengjuhi09:02
yuval#info chenying liujiong yushb jiaopengju in meeting09:02
*** edisonxiang has joined #openstack-meeting09:02
*** martinkopec has joined #openstack-meeting09:02
yuvalgood to see all of you here09:02
edisonxianghello:)09:02
yuvalhey edisonxiang!09:02
chenying#info zhonghua209:02
edisonxianghello yuval09:03
yuval#info zhonghua2 edisonxiang in meeting09:03
yuvalLet's start with the first topic on the agenda09:03
yuval#topic Pike Status09:04
*** openstack changes topic to "Pike Status (Meeting topic: karbor)"09:04
yuvalNext week is RC1 target week09:04
*** toscalix has quit IRC09:04
yuvaland on August 21th we enter final RC week09:05
chenyingyuval So the feature patches need be merged this week?09:05
yuvalwe have made quite a progress in the last two weeks09:05
yuvalchenying: this week or the next09:05
chenyingok.09:06
yuvalchenying: the RC will be created at the end of next week, afaik09:06
yuvalif there are any patches you think should be merged, please say so09:07
yuvalI'm currently aware about the operation log patches, the heat patches09:07
chenyingOperation Engine: Support Trigger Multi Node   what about this patch?09:08
yuvalchenying: as you pointed out to me, more work is required on that. I'll try to finish by the end of next week09:08
chenyingIt  seems that it need be updated.09:08
chenyingyuval Sound good.09:09
yuvalanything else?09:09
jiaopengjuI will try to add retry for s3 bank plugin09:10
chenyingThere is a topic submitted by09:10
chenyingyushb.09:10
yuvaljiaopengju: hope to see this one09:10
yuvalchenying: getting to it next09:10
jiaopengjuyuval: ok09:10
yuvalanother thing09:10
*** ralonsoh has quit IRC09:10
yuvalThe Sydney summit is on, and the voting for talks is open09:11
yuvalhttps://www.openstack.org/summit/sydney-2017/vote-for-speakers09:11
*** ralonsoh has joined #openstack-meeting09:11
yuvalA few sessions about Karbor have been submitted. You can use search for "Karbor" to see them09:11
yuvalif there is any talk you'd like to hear, please vote for it09:11
yuval#topic Barbican integration09:12
*** openstack changes topic to "Barbican integration (Meeting topic: karbor)"09:12
*** abhishekk has left #openstack-meeting09:12
yushbyes, I added this topic.09:13
yuvalthat's by yushb?09:13
*** vishnoianil has quit IRC09:13
yuvalgo ahead :)09:13
yushbwe want to integrate barbican to backup keys09:13
chenyingyushb Can you give some usecases about it?09:14
yuvalyushb: to be honest, I'm not very familiar with barbican. Does barbican have some sort of backup, or would you like to backup them to the bank?09:14
liujiongbarbican is key manager service in openstack, currently it doesn't have backup function implemented yet.09:15
*** zengchen has joined #openstack-meeting09:15
liujiongDoes karbor require the backup function implemented in barbican side?09:16
*** yamahata has quit IRC09:17
yuvalliujiong: not really. But some services do have their own backup API (i.e Cinder), and that's something Karbor can support09:17
liujiongok, actually, backing up key materials is a normal usecase. That's why we're seeking the possibility to integrate with karbor.09:18
chenyingyushb The the backup function about barbican resource could be  implemented  in plugins. It can call backup api like cinder, or you can implement it in plugin it self.09:19
*** toscalix has joined #openstack-meeting09:19
yushbchenying yeah, I know about it.09:20
*** slaweq_ has joined #openstack-meeting09:20
yuvalPlacing the keys in the bank + metadata sounds quite easy. What about security? Is it used to backup private keys as well?09:20
*** sdague has joined #openstack-meeting09:20
chenyinghttps://ethercalc.openstack.org/karbor-queens  it seem that the task 'Support barbican protection plugin09:21
chenying' has been added to this link.09:21
yuvallooking at barbican's api, maybe I mean: we intend to backup the secret payload, right? Placing it in the bank as is, seem to induce a security issue09:21
chandankumarHello,09:22
liujiongyuval: yep, indeed backing up private key is something need discussion09:22
chenyinghi chandankumar09:23
chandankumarchenying: i was checking karbor project there is no tempest plugin there09:23
chandankumarchenying: is there any plan to add create tempest plugin in a seperate repo for karbor in Queens cycle?09:24
chenyingYes karbor only have fullstack tests.09:24
*** slaweq_ has quit IRC09:24
chandankumarchenying: sorry what is fullstack tests?09:24
yuvalchandankumar: we are now discussing barbican integration. Mind discussing tempest after that?09:25
chandankumaryuval: sure09:25
yuvalchandankumar: thanks09:25
yuvalyushb: liujiong: any idea about storing secret payload on the bank?09:25
*** toscalix has quit IRC09:26
*** sambetts|afk is now known as sambetts09:27
liujiongyuval: you mean karbor as a storage backend for barbican?09:27
*** ykatabam has quit IRC09:28
liujiongyuval: what's bank plugin used for?09:28
yuvalliujiong: Karbor is using the bank (i.e swift, s3, etc.) for storing backup metadata and sometimes data itself (depending on the protection plugin). One possible implementation for Barbican secrets would be, store the secret payload and metadata on the bank.09:28
yuvalliujiong: = store the data on swift or s3 (for example)09:28
yuvalliujiong: this induces a security issue: anyone with access to the bank could get the secret payload09:29
*** Shunli has quit IRC09:30
*** toscalix has joined #openstack-meeting09:32
*** coolsvap has joined #openstack-meeting09:32
liujiongyuval: ok, so people can access bank means they can access all the data stored in bank?09:32
yuvalliujiong: I guess there are other solutions. Maybe ask the Barbican backend store for an encrypted dump09:32
*** toscalix has quit IRC09:32
jiaopengjuyuval liujiong: maybe we can store it as binary file?09:33
*** prateek has quit IRC09:33
yuvaljiaopengju: sounds good, but that binary file must be encrypted, right?09:34
yushbyuval : Now in barbican service, keys are stored after encrypted.09:34
jiaopengjuyuval: it seems yes09:36
yuvalyushb: afaik, they are stored in a backend secret store https://docs.openstack.org/barbican/latest/install/barbican-backend.html09:36
yuvalyushb: a few problems with that:09:36
liujiongyuval jiaopengju: then another problem, how to protect the encryption keys of karbor.09:36
chenyingliujiong:  can the encrypted data can be restore by  barbican service directly?09:36
yuvalyushb: 1. we don't want to speak to the backend store, behind barbican's back09:36
yuvalyushb: 2. we would be able to restore only into the same backend store09:37
*** yamamoto has quit IRC09:37
yuvalliujiong: good point09:37
*** toscalix has joined #openstack-meeting09:38
*** marst_ has joined #openstack-meeting09:38
yuvalI'll have to stop here and move to the next subject, but there is plenty to continue to speak about. I suggest we meet in Karbor channel, tomorrow at 07:00 UTC (15:00 China time) to discuss it in depth09:38
*** marst has quit IRC09:38
yuvalliujiong: jiaopengju: jiaopengju: chenying: are you ok with that?09:39
liujiongyuval: fine with me09:39
yuvalyushb:09:39
yushbfine09:39
chenyingsure09:39
jiaopengjuok09:39
yuvalgreat09:39
yuvalwill move to tempest chandankumar09:40
yuval#topic Tempest09:40
*** openstack changes topic to "Tempest (Meeting topic: karbor)"09:40
yuvalchandankumar: Currently Karbor uses a DSVM gate and tests Karbor's APIs without tempest09:40
chandankumaryuval: is there any plan to use tempest plugin in future?09:41
chenyingIMO they are repetitive about integration tests.09:42
*** kaisers has joined #openstack-meeting09:42
yuvalchandankumar: tbh, a bit embarassing, but I'm not very familiar with tempest09:43
chandankumaryuval: no problem i was asking because in queens there is a tempest split goal to a seperate repo, i am volunteering for the same09:44
liujionglooks like fullstack is integration test09:44
chandankumaryuval: tempest provides a set of stable api through which you can create tempest plugin09:44
*** toscalix has quit IRC09:44
chandankumarthrough plugin tempest discovers the tests and all the api/scenario tests related to karbor will resides with the plugin09:45
yuval#link https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html09:45
chandankumaryuval: since there is currently on tempest plugin in karbor so there is no issue09:45
yuvalchandankumar: thanks for pointing that out09:45
*** toscalix has joined #openstack-meeting09:46
yuvalchandankumar: adding a tempest plugin for karbor means that we have to be aware of the split and do it correctly, I guess09:46
chandankumaryuval: but if you need any help, please let me know i will be hanging around on #openstack-qa channel09:46
chandankumaryuval: yes09:46
yuvalchandankumar: that's great, thank you :D09:47
chandankumaryuval: since there is no tempest plugin for karbor so creating it from scratch is not hard09:47
yuval#topic Open Discussion09:47
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)"09:47
yuvalAnything else you would like to speak about?09:47
*** esberglu has joined #openstack-meeting09:48
yuvalthanks for attending :)09:49
yuval#endmeeting09:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:49
openstackMeeting ended Tue Aug  1 09:49:15 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-08-01-09.00.html09:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-08-01-09.00.txt09:49
openstackLog:            http://eavesdrop.openstack.org/meetings/karbor/2017/karbor.2017-08-01-09.00.log.html09:49
liujiongyuval: thank you!09:49
*** lpetrut has joined #openstack-meeting09:51
*** esberglu has quit IRC09:53
*** kaisers has quit IRC09:54
*** yamamoto has joined #openstack-meeting09:57
*** lpetrut_ has joined #openstack-meeting09:59
*** lpetrut has quit IRC10:01
*** toscalix has quit IRC10:02
*** caowei has quit IRC10:05
*** kevinz has quit IRC10:07
*** wanghao has quit IRC10:07
*** yamamoto has quit IRC10:08
*** zhhuabj has quit IRC10:10
*** kiennt has quit IRC10:12
*** tovin07_ has quit IRC10:12
*** liujiong has quit IRC10:12
*** toscalix has joined #openstack-meeting10:12
*** wanghao has joined #openstack-meeting10:13
*** YanXing_an has quit IRC10:14
*** jiaopengju has quit IRC10:16
*** yushb has quit IRC10:17
*** prateek has joined #openstack-meeting10:19
*** prateek has quit IRC10:20
*** prateek has joined #openstack-meeting10:21
*** yangyapeng has quit IRC10:22
*** mugsie has quit IRC10:22
*** mugsie has joined #openstack-meeting10:25
*** mugsie has quit IRC10:25
*** mugsie has joined #openstack-meeting10:25
*** wanghao has quit IRC10:25
*** chyka has joined #openstack-meeting10:25
*** yamamoto has joined #openstack-meeting10:25
*** slaweq_ has joined #openstack-meeting10:27
*** thorst_afk has joined #openstack-meeting10:28
*** chyka has quit IRC10:30
*** zhhuabj has joined #openstack-meeting10:30
*** mugsie has quit IRC10:31
*** markvoelker has joined #openstack-meeting10:31
*** thorst_afk has quit IRC10:32
*** mugsie has joined #openstack-meeting10:33
*** mugsie has quit IRC10:33
*** mugsie has joined #openstack-meeting10:33
*** slaweq_ has quit IRC10:34
*** alexchadin has quit IRC10:35
*** alexchadin has joined #openstack-meeting10:36
*** Manuel_112 has joined #openstack-meeting10:36
*** jkilpatr has quit IRC10:44
*** zhhuabj has quit IRC10:45
*** trinaths has quit IRC10:45
*** trinaths has joined #openstack-meeting10:46
*** leanderthal has joined #openstack-meeting10:46
*** jiaopengju has joined #openstack-meeting10:46
*** leanderthal is now known as leanderthal|afk10:48
*** Manuel_112 has quit IRC10:49
*** kaisers has joined #openstack-meeting10:51
*** iceyao has quit IRC10:52
*** iceyao has joined #openstack-meeting10:55
*** flanders_ has quit IRC10:56
*** zhhuabj has joined #openstack-meeting10:58
*** bkopilov_ has quit IRC10:58
*** iceyao has quit IRC11:00
*** prateek_ has joined #openstack-meeting11:03
*** jiaopengju has quit IRC11:03
*** markvoelker has quit IRC11:05
*** prateek has quit IRC11:05
*** julim has joined #openstack-meeting11:07
*** alexchadin has quit IRC11:08
*** slagle has quit IRC11:08
*** edmondsw has joined #openstack-meeting11:09
*** alexchadin has joined #openstack-meeting11:12
*** edmondsw has quit IRC11:14
*** jkilpatr has joined #openstack-meeting11:15
*** yamamoto has quit IRC11:17
*** kaisers has quit IRC11:18
*** alexchadin has quit IRC11:22
*** yangyapeng has joined #openstack-meeting11:23
*** Manuel_112 has joined #openstack-meeting11:23
*** Manuel_1_ has joined #openstack-meeting11:24
*** Manuel_1_ has quit IRC11:26
*** Manuel_112 has quit IRC11:28
*** markvoelker has joined #openstack-meeting11:30
*** Manuel_112 has joined #openstack-meeting11:32
*** yamamoto has joined #openstack-meeting11:32
*** trinaths has quit IRC11:33
*** zengchen has quit IRC11:35
*** zengchen has joined #openstack-meeting11:36
*** Manuel_112 has quit IRC11:36
*** esberglu has joined #openstack-meeting11:37
*** baojg has joined #openstack-meeting11:39
*** thorst_afk has joined #openstack-meeting11:40
*** efried has quit IRC11:40
*** prateek_ has quit IRC11:41
*** esberglu has quit IRC11:42
*** pchavva has joined #openstack-meeting11:42
*** baojg has quit IRC11:45
*** Manuel_112 has joined #openstack-meeting11:45
*** baojg has joined #openstack-meeting11:45
*** yamamoto has quit IRC11:49
*** Manuel_112 has quit IRC11:49
*** Manuel_112 has joined #openstack-meeting11:51
*** litao__ has quit IRC11:51
*** efried has joined #openstack-meeting11:52
*** slagle has joined #openstack-meeting11:53
*** Manuel_112 has quit IRC11:56
*** rbudden has joined #openstack-meeting11:56
*** _pewp_ has quit IRC12:02
*** fnaval has quit IRC12:02
*** _pewp_ has joined #openstack-meeting12:05
*** claudiub has joined #openstack-meeting12:06
*** raildo has joined #openstack-meeting12:10
*** chyka has joined #openstack-meeting12:11
*** chyka has quit IRC12:15
*** kaisers has joined #openstack-meeting12:15
*** slagle has quit IRC12:17
*** lakerzhou has joined #openstack-meeting12:22
*** thorst_afk has quit IRC12:22
*** esberglu has joined #openstack-meeting12:24
*** kaisers has quit IRC12:25
*** dpaterson has quit IRC12:25
*** slagle has joined #openstack-meeting12:25
*** mriedem has joined #openstack-meeting12:27
*** slaweq_ has joined #openstack-meeting12:31
*** liuyulong has joined #openstack-meeting12:31
*** slaweq_ has quit IRC12:36
*** julim has quit IRC12:37
*** edmondsw has joined #openstack-meeting12:38
*** dprince has joined #openstack-meeting12:38
*** baoli has joined #openstack-meeting12:39
*** esberglu has quit IRC12:39
*** links has quit IRC12:40
*** YanXing_an has joined #openstack-meeting12:43
*** slagle has quit IRC12:47
*** yamamoto has joined #openstack-meeting12:49
*** hoangcx_ has joined #openstack-meeting12:50
*** electrofelix has quit IRC12:52
*** esberglu has joined #openstack-meeting12:55
*** chohoor has joined #openstack-meeting12:56
*** mriedem has quit IRC12:57
*** thorst_afk has joined #openstack-meeting12:57
*** ruijie has joined #openstack-meeting12:58
*** electrofelix has joined #openstack-meeting12:58
*** yamamoto has quit IRC12:59
Qiming#startmeeting senlin13:00
openstackMeeting started Tue Aug  1 13:00:25 2017 UTC and is due to finish in 60 minutes.  The chair is Qiming. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: senlin)"13:00
openstackThe meeting name has been set to 'senlin'13:00
Qimingevening13:00
*** baojg_ has joined #openstack-meeting13:00
chohoorHi13:00
ruijiehi Qiming13:00
Qiminghi, chohoor, ruijie13:01
*** kylek3h has joined #openstack-meeting13:01
*** elynn has joined #openstack-meeting13:01
*** mkrai has quit IRC13:01
Qimingevening, elynn13:01
elynnHi Qiming13:02
QimingI don't have specific agenda for this meeting13:02
*** mattoliverau has quit IRC13:02
*** masayukig[m] has quit IRC13:02
elynnHow is your princess ? Saw your pics in wechat.13:02
Qimingif you have topics, feel free to add them here: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda13:02
*** baojg has quit IRC13:03
Qimingveeeeeeeery naughty13:03
Qiminguncontrollable13:03
*** gouthamr has joined #openstack-meeting13:03
elynnI dont ,just to ask about my patch.13:03
elynnhaha, your gene is in it13:03
Qimingthat big one13:03
ruijieI got questions about zone placement policy & health manager ~13:03
elynnabout https://review.openstack.org/#/c/467108/13:04
Qiming+677, -34313:04
elynnWill any one of you could review and test....13:04
Qiminghave you tested it?13:04
*** VW has joined #openstack-meeting13:04
elynnI test some basic functions, create ports ,create floating IPs, at least it works fine13:04
*** VW has quit IRC13:05
Qiminggreat13:05
elynnbasic update.13:05
*** VW has joined #openstack-meeting13:05
*** chenyb4_ has joined #openstack-meeting13:06
*** mriedem has joined #openstack-meeting13:06
elynnI will add you all to review this patch later :)13:06
Qimingthat is fair13:06
elynnWhen is the RC?13:06
chohoorI want to discuss some details about fast scaling and standby nodes.13:07
elynnAlso I'm working on k8s this week, hopefully I can get a running k8s this week with kubeadm.13:07
Qimingchohoor, later13:07
QimingRC1 is next week13:07
elynnThat's all from my part :)13:08
*** eharney has joined #openstack-meeting13:08
Qimingokay, thanks13:08
Qimingfinal rc is aug 28-sep 0113:08
Qimingoh, no, aug 21-aug 2513:08
Qimingaug 28 is final release13:08
elynnokay, I see.13:09
*** iceyao has joined #openstack-meeting13:09
Qimingokay, let's switch to chohoor's proposal13:09
Qimingfast scaling of clusters13:09
Qimingit is a great idea13:09
Qimingalthough there are some details to  be discussed13:09
chohoorI have write a spec in doc.13:10
QimingI've read it13:10
*** Manuel_112 has joined #openstack-meeting13:11
chohoorIn todo list, the num of standby nodes is max_size - desired_capacity, but I think if the max_size is too big....13:11
Qimingsay I have a cluster created: min=10, max=2013:11
Qiminghow many standby nodes should we create at the very beginning?13:12
*** epico has quit IRC13:12
chohoori think it shuould specify by user.13:13
Qimingright, that was my point13:13
chohoorbut less than max_size13:13
Qimingmaybe we can put that constraint aside13:14
Qiminglet's focus on user's experience13:14
*** Manuel_1_ has joined #openstack-meeting13:14
*** yushb has joined #openstack-meeting13:14
Qimingif I'm a user, am I supposed to be aware of how many standby nodes there?13:14
chohoorthat's ok13:14
*** Manuel_112 has quit IRC13:15
Qimingcan we share standby nodes among two or more clusters?13:15
chohooryes, I think use should know that.13:15
chohoorNo, the profile is diffrent.13:16
Qimingprofile can be the same13:16
ruijiethe properties are very different13:16
Qimingsay I have created two clusters from the same profile13:16
ruijielike the disk type, network .etc13:16
Qimingright, they could be ...13:16
*** Manuel_112 has joined #openstack-meeting13:17
chohoormaybe the cluster should have own standby nodes.13:17
Qimingokay ... if we agree that standby nodes are still members of a cluster13:17
*** sridharg has quit IRC13:17
Qimingand they are visible to the cluster's owner13:18
*** sridharg has joined #openstack-meeting13:18
*** Manuel_1_ has quit IRC13:18
Qimingare you gonna charge them for these standby nodes?13:18
*** sridharg has quit IRC13:18
*** yushb has quit IRC13:18
*** sridharg has joined #openstack-meeting13:19
*** sridharg has quit IRC13:19
chohooryes, we need make sure standby nodes in active state.13:19
Qimingthat would lead us to another question: if the user is consuming additional resources, why don't we charge them?13:20
*** sridharg has joined #openstack-meeting13:20
*** julim has joined #openstack-meeting13:20
*** bkopilov_ has joined #openstack-meeting13:21
Qimingif we charge them, they would be confused at least ... because they are not "running" workloads on those standby nodes13:21
*** kaisers has joined #openstack-meeting13:21
ruijieand if they costs extra money, why not just create extra nodes ..13:22
Qimingyes13:23
chohoorI have think this question, the standby nodes is for standby, but if the nodes in cluster is error, we could replace them  immediately.13:23
Qimingso ... one of the key question to answer is about the definition of "standby"13:23
*** Manuel_1_ has joined #openstack-meeting13:25
Qimingif you allocate 10 nodes, all active, but only treat 8 of them as member of your cluster, the other 2 are only for "standby"13:25
Qimingthen why don't you run workloads on them as well?13:25
*** claudiub has quit IRC13:25
*** Manuel_112 has quit IRC13:26
*** chenyb4_ has quit IRC13:27
*** Manuel_112 has joined #openstack-meeting13:27
chohooryou are right. i'll continue to consider.13:27
*** yangyapeng has quit IRC13:27
*** Manuel___ has joined #openstack-meeting13:27
Qimingone baby step is for this case13:28
Qimingsuppose I have 10 nodes running now13:28
Qimingmy cluster have min=5, max=1513:29
*** janki has quit IRC13:29
Qimingfor whatever reason, I want to scale it in by 2 nodes now, that means I'm setting the desired_capacity to 813:29
Qimingremoving 2 nodes from the cluster13:30
Qimingwe can lazily remove those nodes13:30
*** julim_ has joined #openstack-meeting13:30
Qimingif later on I want to scale the cluster back to 10 nodes, I can reuse them13:30
*** Manuel_1_ has quit IRC13:31
Qimingsounds the idea is very similar to yours13:31
chohoorremove the nodes to standby nodes first, then real delete them?13:31
*** julim has quit IRC13:31
ruijieQiming, you mean keep them for a while, but still will be removed for a user defined period ?13:31
Qiminglet the cluster owner decide for how long we will keep those nodes13:31
chohoorok13:32
*** Manuel_112 has quit IRC13:32
Qimingbecause we have node-delete API, user can still delete them at will at any time13:32
*** slaweq_ has joined #openstack-meeting13:32
*** sridharg has quit IRC13:32
Qimingthis use case is less risky because we are sure the nodes are homogeneous13:33
*** sridharg has joined #openstack-meeting13:33
Qimingwe are sure the nodes are configured the same way13:33
Qimingwe are sure there won't be data leaked from one user to another13:34
*** pchavva has quit IRC13:35
*** sridharg has quit IRC13:35
*** pchavva has joined #openstack-meeting13:35
*** cdub has quit IRC13:35
Qimingif there are such extra nodes, we may want to stop them instead of deleting them13:35
*** sridharg has joined #openstack-meeting13:35
Qimingthat leads us back to the definition of "standby" nodes13:36
*** slaweq_ has quit IRC13:37
*** Alex_Staf has quit IRC13:37
*** hongbin has joined #openstack-meeting13:38
chohoorI'll rewrite the spec and please give me more suggest in irc later. thank you.13:38
Qimingmy pleasure13:38
Qimingjust want to be sure that we have thought it through before writing the code13:38
chohoorsure13:39
ruijieis it my turn now :)13:40
Qiminganything else?13:40
Qimingshoot13:40
chohoorand another question, about protect a special node not to be delete.13:40
ruijieyes Qiming, the first one is this patch : https://review.openstack.org/#/c/481670/13:40
chohooryour turn.13:41
ruijiethe change will rerun the actions which is action.status = READY13:41
*** Manuel___ has quit IRC13:41
ruijiethah is caused by failed to acquire lock13:41
Qimingyes13:42
*** VW_ has joined #openstack-meeting13:42
*** XueFeng has joined #openstack-meeting13:42
ruijiebut it will try to process the action again and again ..13:42
ruijiethe cluster is still locked in this period .. that will create a lot of events?13:42
Qimingwhat do you mean by "again and again"13:42
Qimingwhat is the interval?13:42
ruijie0 sec13:43
*** masayukig[m] has joined #openstack-meeting13:43
Qimingso .. that is the problem13:43
ruijieyes Qiming13:43
*** YanXing_an has quit IRC13:43
Qimingor we should add a global option lock_max_retries13:43
*** lhx_ has joined #openstack-meeting13:44
*** sridharg has quit IRC13:44
ruijieand maybe a lock_retry_interval ..13:44
Qiming:)13:44
Qimingmaybe both13:44
*** sridharg has joined #openstack-meeting13:44
*** janzian has joined #openstack-meeting13:44
*** liuyulong has quit IRC13:45
Qimingthe logic is not incorrect, just it ... is too frequent, too noisy13:45
*** VW has quit IRC13:45
Qimingchohoor, you want to "lock" a node?13:46
ruijieimprovement is needed :)13:46
chohooryes13:46
Qiminguse case?13:47
chohoorA node not to be delete.13:47
*** noslzzp has joined #openstack-meeting13:47
chohoormaybe this is a special node in user point...13:47
Qimingsounds like a use case of node roles13:48
*** VW_ has quit IRC13:48
*** VW has joined #openstack-meeting13:48
chohoorIn tencent cloud, user could add a normal instance to cluster as a node.13:49
chohoorand the code could be protect not to be delete.13:49
chohoors/code/node/13:50
ruijielike node adoption13:50
*** emagana has joined #openstack-meeting13:50
Qimingwho is deleting it then? if the user doesn't want to delete it?13:50
chohoorauto scale, because it could be random13:51
*** Alex_Staf has joined #openstack-meeting13:51
*** cleong has joined #openstack-meeting13:51
chohooror oldest first policy.13:52
QimingI see13:52
*** kaisers has quit IRC13:52
elynnSo by 'protect' here just mean cluster scaling actions won't delete it, but this node still can be deleted by 'node delete' command?13:52
*** sridharg has quit IRC13:53
Qimingso it is gonna be some label or tag that will change some action's behavior13:53
chohoorelynn: i think so13:53
elynnyes, I guess.13:53
*** sridharg has joined #openstack-meeting13:53
*** ijw has joined #openstack-meeting13:54
*** jlibosva has joined #openstack-meeting13:54
Qimingalright, please think if we can use node.role for this purpose13:54
elynna 'protect' tag, will exclude it from scaling candidate list.13:54
Qimingbecause ... that is a more general solution13:54
Qimingem ... we don't support tags yet13:55
chohoorok13:55
Qimingmaybe we should13:55
chohoormetedata?13:55
Qimingno objection on implemeting tags13:55
Qimingmetadata is also fine13:55
Qimingsay 'protected: true'13:56
chohoorif a node in protected state, what if the cluster/node execute update action?13:57
Qimingfeel free to propose a solution then13:57
elynnNeed to think about health policy, can we rebuild it?13:57
*** sridharg has quit IRC13:57
chohoorI suggest not.13:57
*** sridharg has joined #openstack-meeting13:58
*** yushiro has joined #openstack-meeting13:58
elynnThen update should also be rejected I guess?13:58
*** chyka has joined #openstack-meeting13:59
Qiming...13:59
chohoorjust don't update the protected node.13:59
*** Manuel_112 has joined #openstack-meeting13:59
Qimingthanks guys13:59
*** yushb has joined #openstack-meeting13:59
XueFenghi, senlin rdo has been finished13:59
XueFenghttps://bugzilla.redhat.com/show_bug.cgi?id=142655113:59
openstackbugzilla.redhat.com bug 1426551 in Package Review "Review Request: Senlin - is a clustering service for OpenStack" [Unspecified,Closed: errata] - Assigned to amoralej13:59
Qimingwe are running out of time13:59
*** shintaro has joined #openstack-meeting13:59
Qiming#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Aug  1 14:00:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-08-01-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-08-01-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/senlin/2017/senlin.2017-08-01-13.00.log.html14:00
*** mkrai has joined #openstack-meeting14:00
*** mattoliverau has joined #openstack-meeting14:00
jlibosva#startmeeting networking14:00
yushirohi14:00
amotokihi14:00
openstackMeeting started Tue Aug  1 14:00:24 2017 UTC and is due to finish in 60 minutes.  The chair is jlibosva. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
haleybhi14:00
*** Manuel_112 has quit IRC14:00
jlibosvahello everybody14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
jlibosva#topic Announcements14:00
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:00
*** davidsha has joined #openstack-meeting14:00
jlibosvaThe pike 3 milestone happened last week14:01
*** ruijie has left #openstack-meeting14:01
jlibosvaIf you're working on a feature that didn't make it to p3 milestone and you think it should go to Pike, you can ask for a feature freeze exception14:01
*** zeih has quit IRC14:02
*** zeih has joined #openstack-meeting14:02
*** annp has joined #openstack-meeting14:02
jlibosvanext one14:02
amotokidev mail on FFE http://lists.openstack.org/pipermail/openstack-dev/2017-July/120340.html14:02
*** galstrom_zzz is now known as galstrom14:02
jlibosvaamotoki: thanks :)14:02
*** boden has joined #openstack-meeting14:02
jlibosvaPTG is happening next month in Denver, CO14:03
*** chyka has quit IRC14:03
jlibosvaplease see email from Kevin: http://lists.openstack.org/pipermail/openstack-dev/2017-July/120270.html14:03
*** sridharg has quit IRC14:03
jlibosvathere is a link to etherpad where, if you're gonna attend the event, you can write down your name. It also serves as a place to collect topics to discuss14:04
*** sridharg has joined #openstack-meeting14:04
*** lbragstad_ is now known as lbragstad14:04
jlibosvaThe deadline to get travel support is this week14:04
jlibosvaI also saw an email that User Committee nomination was started: http://lists.openstack.org/pipermail/openstack-dev/2017-August/120393.html14:05
jlibosvaso if you feel like, you can self-nominate yourself :)14:05
jlibosvathat's all from me, anybody has anything to announce?14:05
*** yushb has left #openstack-meeting14:05
amotokiin addition, PTL self-nomination week14:06
*** XueFeng has quit IRC14:06
*** chohoor has left #openstack-meeting14:06
*** arnewiebalck_ has joined #openstack-meeting14:06
-amotoki- thinks perhaps no announce is needed though14:06
jlibosvahttp://lists.openstack.org/pipermail/openstack-dev/2017-August/120383.html14:07
jlibosvaif nobody has other announcements to make, we can move on14:07
jlibosva#topic Blueprints14:07
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:07
jlibosvaI'm not sure there is anything to discuss here as we're in FF :)14:08
jlibosvaso unless anybody has anything to say about blueprints, we will skip this topic14:08
*** Alex_Staf has quit IRC14:08
jlibosvaok14:09
jlibosva#topic Bugs and gate failures14:09
*** openstack changes topic to "Bugs and gate failures (Meeting topic: networking)"14:09
jlibosvaamotoki: you were the bug deputy?14:09
*** awaugama has joined #openstack-meeting14:09
haleybi was bug deputy14:09
jlibosvaaah14:09
jlibosvahaleyb: hi :)14:09
* jlibosva mixed Jun and Jul14:09
amotokii think the wiki page is not updated recently :(14:09
jlibosvayeah, I'll update it after meeting14:10
haleybi think most bugs have been triaged, i'm going through the backlog now14:10
*** arnewiebalck_ has quit IRC14:11
*** janki has joined #openstack-meeting14:11
haleybthe one that's still an issue is sometimes there are multi-node job failures, mostly non-voting jobs14:11
haleybhttps://bugs.launchpad.net/neutron/+bug/170700314:11
openstackLaunchpad bug 1707003 in neutron "gate-tempest-dsvm-neutron-dvr-ha-multinode-full-ubuntu-xenial-nv job has a very high failure rate" [High,Confirmed] - Assigned to Brian Haley (brian-haley)14:11
haleybi own that and continue to work on it14:11
jlibosvahaleyb: are there any particular test that are failing?14:12
haleybjlibosva: it's sub-node setup failure, we talked about it in last week's CI meeting14:13
jlibosvaah, so more related to infra building stuff than neutron?14:13
*** reedip_ has joined #openstack-meeting14:13
jlibosvaok, if that has an assignee, then it's good :)14:14
haleybyes, seems so, there was a patch a while ago, but it needs updating.  hopefully there is nothing in neutron14:14
haleybkevin has also been working on log file cleanup, https://bugs.launchpad.net/neutron/+bug/170730714:14
openstackLaunchpad bug 1707307 in neutron "Neutron log obesity epidepmic" [High,In progress] - Assigned to Kevin Benton (kevinbenton)14:14
haleybhas a few patches out, but if anyone notices other non-essential log messages feel free to remove them14:15
*** Julien-zte has joined #openstack-meeting14:15
*** sridharg has quit IRC14:15
jlibosvalooks like ovsdbapp is chatty :)14:15
jlibosvaslightly related to non-voting jobs instability, I sent an email last week calling for a help with one job: http://lists.openstack.org/pipermail/openstack-dev/2017-July/120294.html14:16
haleybdid you get any help?14:16
jlibosvait reveled some real issues in trunk/ovs fw, I'm looking at the bug14:16
jlibosvahttps://bugs.launchpad.net/neutron/+bug/170733914:16
openstackLaunchpad bug 1707339 in neutron "test_trunk_subport_lifecycle fails on subport down timeout" [High,In progress] - Assigned to Armando Migliaccio (armando-migliaccio)14:16
*** sridharg has joined #openstack-meeting14:16
jlibosvahaleyb: yep, slawek started looking at qos and armax looked at trunk14:17
jlibosvabut it would be good to get moar help, so if anybody has spare cycles, there are some failures that need love ;)14:17
jlibosvahaleyb: thanks for updates about bugs14:18
*** ihrachys has joined #openstack-meeting14:18
haleybi did just notice a spike in the functional job, about 30% now14:18
haleybi hadn't refreshed grafana this morning14:18
*** rbartal has quit IRC14:18
haleybhttp://grafana.openstack.org/dashboard/db/neutron-failure-rate?panelId=8&fullscreen14:18
ihrachysfunc tests are timeouts I believe; I think jlibosva was going to recheck a testing patch to trigger a worker killed14:18
jlibosvayep, I got a hit on my patch but that didn't revealed the killer14:19
jlibosvait looks like the kill was not called via CLI14:19
haleybjlibosva: is there a bug yet?14:19
jlibosvapatch here: https://review.openstack.org/#/c/487065/14:19
jlibosvahaleyb: probably not, we should open one14:20
*** sridharg has quit IRC14:20
jlibosvathere is this etherpad ihrachys created for all func failures: https://etherpad.openstack.org/p/neutron-functional-gate-failures-july14:20
*** martinkopec has quit IRC14:20
jlibosvaany ideas how to nail down what is killing process?14:21
jlibosvathe weird thing is that it always happens during firewall tests14:21
ihrachysyou say smth not calling .execute() kills testers?14:21
jlibosvasomething not calling "/usr/bin/kill"14:21
jlibosvawhich execute() is a subset of14:22
*** sridharg has joined #openstack-meeting14:22
*** Alex_Staf has joined #openstack-meeting14:22
*** donghao has joined #openstack-meeting14:22
*** sridharg has quit IRC14:23
ihrachysok maybe it's killall :)14:23
ihrachysdo we log all commands?14:23
jlibosvain tests we do14:23
*** fnaval has joined #openstack-meeting14:23
*** sridharg has joined #openstack-meeting14:24
ihrachysok, so it's not just kill that you capture14:24
ihrachysanyway, I don't think we will make progress right now14:24
ihrachyslet's report the bug as first step14:24
*** Alex_Staf has quit IRC14:24
ihrachysI will take it14:24
jlibosvayeah, sounds good14:24
jlibosvaihrachys: thanks14:24
jlibosvaI was just wondering if anybody has a good trick for it :)14:25
jlibosvaok, let's move on from functional failures, we can talk about that at Neutron CI meeting in ~1.5hrs14:25
jlibosvaanybody wants to be a bug deputy for this week?14:25
jlibosvait looks like it's not the most favourite role :)14:27
haleybi will put names on dart board and throw...14:27
jlibosvahaleyb: tell me who won14:27
jlibosvaor we can open an rfe to openstack bot, to pick names randomly :-p14:28
*** marst_ has quit IRC14:28
jlibosvaif nobody wants it, then I'll take it14:28
jlibosva#info jlibosva is a bug deputy for the week of Jul-3114:28
ihrachysmaybe worth talking to PTL if there is a problem of getting candidates14:28
jlibosvagood idea14:28
jlibosvalet's move on then14:29
jlibosva#topic Docs14:29
*** openstack changes topic to "Docs (Meeting topic: networking)"14:29
jlibosvaamotoki: do you have any updates? I don't see mlavalle here14:29
amotokiwe have good progress on doc-migration :)14:29
*** diablo_rojo has joined #openstack-meeting14:29
*** sridharg has quit IRC14:30
amotokineutron itself have completed the effort.14:30
amotokiwe have some projects still having patches on doc-migration14:30
amotokiSee14:30
amotoki"Missing URLs" at https://doughellmann.com/doc-migration/14:30
jlibosvanice :)14:30
amotokiwe only have four projects remaining14:31
*** sridharg has joined #openstack-meeting14:31
amotokiI believe time will solve it14:31
amotokiI already post patches on these remaining things.14:31
amotokithats' the update on doc-migration14:32
jlibosvasounds good, thanks14:32
jlibosvaamotoki: do you think you should reach out to people from those four projects or are you good doing it yourself?14:32
amotokiat some time, we need to discuss on the future of LBaaS document with octavia team14:32
amotokijlibosva: i already sent the required patches to the four projects14:32
*** eharney has quit IRC14:33
jlibosvaok :)14:33
jlibosvaAnybody has any other updates regarding docs?14:33
*** slaweq has joined #openstack-meeting14:33
*** trinaths has joined #openstack-meeting14:33
*** trinaths has left #openstack-meeting14:33
*** slaweq has quit IRC14:33
jlibosvaif not, we can move to osc14:34
jlibosva#topic Transition to OSC14:34
*** openstack changes topic to "Transition to OSC (Meeting topic: networking)"14:34
jlibosvaamotoki: hi :) how are the tags and routers doing?14:34
*** fnaval has quit IRC14:34
amotokiboth landed :) yay14:34
jlibosvawow14:34
jlibosvaso does it mean all resources now have support in osc?14:34
*** fnaval has joined #openstack-meeting14:34
amotokiat now, we've migrated all regarding neutron stuff14:35
*** marst has joined #openstack-meeting14:35
amotokithe remaining part is about advanced services (as OSC plugin)14:35
*** slaweq has joined #openstack-meeting14:35
amotokiI think we can officially discuss and declare when we drop neutron CLI14:35
jlibosvamaybe could be a topic at etherpad for the ptg? :)14:36
*** annabelleB has joined #openstack-meeting14:36
amotokiwill add it14:36
jlibosvaamotoki: thanks14:36
jlibosvaamotoki: and thanks for updates and good news :)14:36
jlibosvaI think we can move to the lib14:36
amotokithanks everyone14:36
jlibosva#topic neutron-lib14:37
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:37
jlibosvaboden: hello :)14:37
bodenhi14:37
*** sridharg has quit IRC14:37
bodenjust a few minor FYIs14:37
*** markstur has joined #openstack-meeting14:37
bodennow that neutron-lib 1.9.1 is out, you should see some “consumption” patches coming down the pipeline14:38
bodenthere are a number of them out already; and more in the works14:38
bodenrather than sending a note to the ML for each, I was just going to get them all out there and send a single note14:38
*** sridharg has joined #openstack-meeting14:38
bodenso, any help reviewing is appreciated :)14:38
ihrachyssince we are in freeze mode, we probably don't rush with them14:39
*** slagle has joined #openstack-meeting14:39
*** trinaths has joined #openstack-meeting14:39
bodenihrachys: ah, so they won’t be able to get in for pike?14:39
jlibosvaisn't 1.9.1 the one that's gonna be released with pike?14:39
ihrachysboden, it's probably a question for PTL, but my understanding is that now we allow features with exceptions approved by drivers team + bug fixes14:39
bodenjlibosva: yes that’s my understanding, but here I was talking aobut neutron and other project patches (not lib)14:40
bodenihrachys: ack thanks14:40
ihrachysthat being said, I saw patches landing that are of other type14:40
jlibosvaboden: aah, sorry, I misunderstood14:40
ihrachysI assume those are mistakes14:40
bodenihrachys: I’ll follow up with kevin later14:40
amotokirefactoring is really a gray zone14:40
amotokiif it help us backports to Pike a lot, it might be acceptable.14:41
amotokianyway it loosk like a question to kevin14:41
bodenthat’s really all I have that’s worth taking everyones time14:41
jlibosvaI'll have a chat with him tomorrow EMEA morning, I'll deliver the message14:41
jlibosvaboden: thanks for updates14:41
jlibosvaanybody has anything to neutron-lib?14:42
*** gaoyan has joined #openstack-meeting14:42
jlibosva#topic open discussion14:42
*** openstack changes topic to "open discussion (Meeting topic: networking)"14:42
*** psachin has quit IRC14:42
*** fnaval has quit IRC14:42
jlibosvaany topics to discuss here or we can end the meeting earlier :)14:43
ihrachysgo for it14:43
jlibosvathanks everyone for coming :)14:44
jlibosva#endmeeting14:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:44
openstackMeeting ended Tue Aug  1 14:44:31 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-08-01-14.00.html14:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-08-01-14.00.txt14:44
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2017/networking.2017-08-01-14.00.log.html14:44
annpthanks, bye14:44
*** sridharg has quit IRC14:46
*** sridharg has joined #openstack-meeting14:48
*** eharney has joined #openstack-meeting14:48
*** kaisers has joined #openstack-meeting14:49
*** janzian has left #openstack-meeting14:49
*** jlibosva has left #openstack-meeting14:49
*** yushiro has left #openstack-meeting14:50
*** YanXing_an has joined #openstack-meeting14:50
*** boden has left #openstack-meeting14:51
*** zeih has quit IRC14:52
*** chyka has joined #openstack-meeting14:53
*** annegentle has joined #openstack-meeting14:53
*** annegentle has quit IRC14:54
*** fnaval has joined #openstack-meeting14:54
*** annegentle has joined #openstack-meeting14:55
*** armstrong has joined #openstack-meeting14:55
*** chyka has quit IRC14:57
*** kaisers has quit IRC14:58
*** VW_ has joined #openstack-meeting14:59
*** SerenaFe_ has joined #openstack-meeting14:59
*** SerenaFe_ has quit IRC14:59
*** cloudrancher has quit IRC15:00
*** cloudrancher has joined #openstack-meeting15:00
davidshaHi15:00
slaweqhello15:01
ralonsohhi15:01
ralonsohLet's start15:01
*** reedip_ has quit IRC15:01
*** hoangcx_ has quit IRC15:01
slaweqok15:01
ralonsoh#openstack-meeting15:01
ralonsoh#startmeeting neutron_qos15:01
openstackMeeting started Tue Aug  1 15:01:44 2017 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:01
openstackThe meeting name has been set to 'neutron_qos'15:01
ralonsohUfff bad command15:01
*** VW has quit IRC15:01
ralonsohJust for information15:02
*** sridharg has quit IRC15:02
ralonsoh#link https://etherpad.openstack.org/p/neutron_qos_meeting_chair15:02
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:02
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:02
ralonsohslaweq, I don't see mlavalle here15:02
*** felipemonteiro has joined #openstack-meeting15:02
*** VW has joined #openstack-meeting15:02
*** sridharg has joined #openstack-meeting15:02
*** shintaro has quit IRC15:02
ralonsohThis spec needs to be re-approved this cycle15:02
ralonsohbut we need to work on this15:03
*** VW has quit IRC15:03
ralonsohDo you mind to wait until the PTG?15:03
ralonsohWe can talk to ajo and mlavalle too15:03
slaweq'this cycle' - You mean Queens, right?15:03
ralonsohYes15:03
ralonsohfor queens15:03
*** VW has joined #openstack-meeting15:03
davidshaSure.15:03
slaweqyes, we should have time to talk about it in Denver15:03
*** VW_ has quit IRC15:03
ralonsohperfect, because I need to clarify some aspects of the spec made by ajo15:04
slaweqajo was today on IRC15:04
ralonsohand, finally, we could start coding (the first patch has a +2, but need rebase)15:04
slaweqso maybe You will be able to catch him15:04
ralonsohyes, I talked to him15:04
davidshaFixing a Devstack issue if I recall.15:04
ralonsohyes, he will be and he'll have time for this15:04
*** sridharg has quit IRC15:04
ralonsohyes, related with the kernel version of centos/rh15:05
ralonsohok so, this rfe for Denver15:05
slaweqok15:05
ralonsohnext, one15:05
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/159661115:05
openstackLaunchpad bug 1596611 in neutron "[RFE] Create L3 IPs with qos (rate limit)" [Wishlist,Triaged] - Assigned to LIU Yulong (dragon889)15:05
*** cloudrancher has quit IRC15:05
*** sridharg has joined #openstack-meeting15:05
ralonsoh2 patches:15:05
ralonsoh#link https://review.openstack.org/#/c/453458/15:05
ralonsohThis one is the TC implementation15:06
*** cloudrancher has joined #openstack-meeting15:06
ralonsohslaweq, davidsha: can you take a look at this one?15:06
slaweqsure15:06
ralonsohLIU submitted a new version15:06
davidsharalonsoh: sure15:06
ralonsohAs is commented in the patch, I think the code is ok15:06
ralonsohbut15:06
ralonsohI don't agree with spliting the TC code15:06
*** bobh has joined #openstack-meeting15:06
*** sridharg has quit IRC15:07
ralonsohsecond15:07
ralonsoh#link https://review.openstack.org/#/c/424466/15:07
ralonsohwaiting for my comments15:07
slaweqme neighter but I will check it once again15:07
ralonsohbut please, if you have time, take a look at this second patch15:07
ralonsohslaweq: you know about adding qos extensions hehehe15:07
slaweq yes15:08
*** sridharg has joined #openstack-meeting15:08
slaweqI will check it today evening15:08
ralonsohthanks!!15:08
davidshaI was looking over the second patch, was wondering should this be an l3 extension but I'll go over it more thoroughly.15:08
*** felipemonteiro has quit IRC15:08
ralonsohdavidsha: I have this doubt too. But this is going to use the QoS API15:09
ralonsohand needs to be aligned with L2 QoS15:09
davidsharalonsoh: It can use the QoS API and use an l3 extension.15:09
davidshaand an L2 extension as well.15:10
ralonsohhow?15:10
davidshaL2 agent, L3 agent and q-svc all listen on RPC right?15:10
ralonsohyes15:11
davidshaJust make an L3 extension for QoS that listens to QoS events.15:11
davidshaSame as L2 and only acts on the L3 qos rules.15:11
ralonsohthis extension is going to affect only the FIP ports15:12
ralonsohisn't it?15:12
slaweqsorry but maybe I don't understand, this patch is about API extension and DB, right?15:12
ralonsohboth15:13
davidshaAh, sorry!15:13
slaweqso about what L2 and L3 extensions are You talking?15:13
ralonsohFIP qos extension15:13
slaweqAPI extension, yes?15:13
*** oidgar has quit IRC15:13
*** sridharg has quit IRC15:14
*** rcernin has quit IRC15:14
ralonsohdavidsha: IMO, the QoS extension (which is in charge of managing the qos rules) should be in charge of managing the qos rules for FIP15:14
*** sridharg has joined #openstack-meeting15:14
davidshaI'll go over it again, sorry!15:14
ralonsohand extending fip object15:15
slaweqso, You are talking about to which service plugin it should be added as supported extension, right?15:15
ralonsoh(BTW, FIP is going to be an OVO)15:15
ralonsohyes15:15
slaweqok, I understand now15:15
slaweqthx ralonsoh15:15
ralonsohthe point is qos_plugin can attend FIP events15:16
*** chyka has joined #openstack-meeting15:16
*** elynn has quit IRC15:16
*** sridharg has quit IRC15:16
ralonsohand talk to ml2 drivers (send the information to the agents)15:16
ralonsohand modify the qos rules15:17
slaweqbut what about validation mechanism for FIP?15:17
*** sridharg has joined #openstack-meeting15:17
slaweqit is based on vif type15:17
slaweqwill it work in same way for FIP like for ports now?15:17
ralonsohone sec....15:18
*** sridharg has quit IRC15:18
ralonsohok15:19
ralonsohcan we extract the port information from FIP?15:19
*** anilvenkata has quit IRC15:19
*** makowals has quit IRC15:19
ralonsohthrough the network/subnet15:19
*** sridharg has joined #openstack-meeting15:19
*** gaoyan has quit IRC15:19
slaweqI don't know for now15:19
davidshaI'm not sure, this is why I was wondering about L3 extensions, fip is handeled by the l3-agent.15:20
slaweqI'm doing "neutron floatingip-show" now on devstack and I don't have port_id15:20
ralonsohdavidsha: the same problem: how do you talk to the agent?15:20
*** sridharg has quit IRC15:20
ralonsohslaweq: no, you need to talk to the l3 agent to retrieve it15:21
ralonsohdavidsha?15:21
slaweqralonsoh: ok15:21
ralonsohcan we davidsha?15:21
*** iceyao has quit IRC15:21
*** sridharg has joined #openstack-meeting15:21
slaweqbut then what about supported rules? we have for now drivers only for L2 agents15:21
*** galstrom is now known as galstrom_zzz15:21
ralonsohthe l3 router has this information15:21
davidsharalonsoh: Adding fip RPC events is the only thing I can think of but I'll need to look into it more.15:21
davidshaListening* to fip rpc events15:21
slaweqwe should have separate driver for L3 agent to set there what rules are supported by it15:21
*** pcaruana has quit IRC15:22
ralonsohslaweq: yes, that's the backend implementation15:22
slaweqnot only because validation of supported rules is done on server15:22
*** sridharg has quit IRC15:22
ralonsohslaweq: and you need to have a driver for this15:22
*** sridharg has joined #openstack-meeting15:23
slaweqso IMHO we will need something like L2/ovs_driver, L2/linuxbridge_driver (we have it now)15:23
*** makowals has joined #openstack-meeting15:23
slaweqand also new L3/ovs_driver15:23
ralonsohslaweq: yes, that's the point15:23
davidshayou need an l3-agent extension in it's entirety to listen for QoS events and then Apply the rules when necessary.15:23
slaweqL3/linuxbridge_driver15:23
ralonsohslaweq: Lui was interested "only" in LB15:24
slaweqit's fine only for LB for the beginning but we need "base" for that15:24
davidsharalonsoh: If we do this on the L3-agent, there is only 1 backend.15:24
ralonsohdavidsha: I think is in the other way. QoS listening to FIP events to add/modify/delete rules15:24
ralonsohdavidsha: 1 backend??15:25
davidshaIt just uses IP lib to configure network namespaces for everything.15:25
*** sridharg has quit IRC15:25
ralonsohdavidsha: and your implementation of DVR using OF??15:26
ralonsohwith OVS15:26
davidsharalonsoh: Yes, I meant right now.15:26
*** sridharg has joined #openstack-meeting15:26
ralonsohdavidsha: ok15:26
ralonsohlet me put this in the other way: qos extension with l3/LB15:26
davidshakk15:27
ralonsohanyway, the developer is not here and it's not reading this15:27
slaweqI agree it should be qos extension15:27
ralonsohif any core has time, I will explain both options and ask for feedback15:28
ralonsohlet's move on... agree?15:28
slaweqyes15:28
davidshaagrred15:28
ralonsohlast one15:28
ralonsohhttps://bugs.launchpad.net/neutron/+bug/164951715:28
openstackLaunchpad bug 1649517 in neutron "qos policy attached to network, qos_policy_id is reflecting on neutron net-show , but not on the port with neutron port-show" [Wishlist,In progress] - Assigned to Reedip (reedip-banerjee)15:28
davidshaagreed*15:28
ralonsohreedip needs to have this one approved15:28
*** sridharg has quit IRC15:28
slaweqit's moving forward but slowly15:28
ralonsohand also he needs to take a look at the fails in jenkins15:29
slaweqhe pushed some new patch so I will take a look on it also15:29
*** sridharg has joined #openstack-meeting15:29
ralonsohI saw it15:29
ralonsohbut it's failing15:29
slaweqyes15:29
*** tobberyd_ has joined #openstack-meeting15:29
ralonsohI prefer to have something working, the errors are easy to solve15:29
*** claudiub has joined #openstack-meeting15:29
ralonsoh"I prefer to have something working" <-- captain obvious!!!15:30
ralonsohhehehehe15:30
davidsha:P15:30
ralonsohanyway, I'll leave a comment in the patch15:30
ralonsohto push this rfe in the drivers meeting15:30
ralonsohto be approved15:30
ralonsohno more rfes! next topic15:31
ralonsoh#topic Bugs15:31
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:31
ralonsohno bugs15:31
*** sridharg has quit IRC15:31
davidshaAlways good.15:31
slaweq\o/15:31
*** baojg has joined #openstack-meeting15:31
ralonsohwell, yamamoto is enabling the qos tests15:31
slaweqyes, I want to check it more deeply15:32
ralonsohso let's take a look during next days15:32
slaweqbut it passes for me each time15:32
ralonsohI know, you are doing a fantastic work in testing15:32
ralonsohthanks slaweq15:32
slaweqthanks :)15:32
*** sridharg has joined #openstack-meeting15:32
davidshaThanks slaweq15:32
ralonsohnext topic??15:32
slaweqwe also made some small changes (not directly in QoS) to make qos working with py3515:32
slaweqit's just FYI15:33
ralonsohcan you send the patch?15:33
slaweqpatch was for oslo15:33
*** baojg_ has quit IRC15:33
slaweqgive me 1 second15:33
*** tobberydberg has quit IRC15:33
*** zz_dimtruck has quit IRC15:33
*** tobberyd_ has quit IRC15:34
slaweqhttps://bugs.launchpad.net/neutron/+bug/170120215:34
openstackLaunchpad bug 1701202 in neutron "Create QoS rule fails on python 3.5" [Undecided,Fix released] - Assigned to Slawek Kaplonski (slaweq)15:34
slaweqthis was this bug15:34
slaweqand it should be fixed already15:34
*** kaisers has joined #openstack-meeting15:34
ralonsohyes, now I remember15:34
ralonsohI closed this bug today15:34
ralonsohperfect!!15:35
slaweqnow all QoS related fullstack tests are passing on py3515:35
davidsha\o/15:35
ralonsohthat's great15:35
ralonsohlet's move on15:35
ralonsoh#topic Other Changes15:35
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)"15:35
ralonsohI have in the cheat sheet15:36
ralonsoh"Ask slaweq infra-shade patch"15:36
*** lpetrut_ has quit IRC15:36
slaweqI started adding support for QoS in openstack-shade client15:36
*** armax has quit IRC15:36
*** lpetrut has joined #openstack-meeting15:36
slaweqit's almost done15:36
ralonsohI saw this15:36
ralonsohAn I think the code is ok15:36
slaweqI'm still missing min bw rules15:36
slaweqand this new call with supported rule details15:36
ralonsohyes, very nice15:37
ralonsohone question15:37
slaweqlater I will have to add some functional tests for all of it also15:37
slaweqyes ralonsoh?15:37
ralonsohyou don't test if a call is made without one needed parameter15:37
ralonsohfor example, missing min_bw15:37
slaweqthat's good point15:38
slaweqI will check it and maybe also fix it for bw limit also15:38
ralonsohI don't have experience on this project, but when I took a look I missed that15:38
ralonsohjust for info hehehe15:38
ralonsohI think that's all folks15:39
ralonsohanything else?15:39
slaweqyes, I will add such checks also15:39
slaweqthx15:39
slaweqI have one question to davidsha15:39
davidshaslaweq: sure15:39
slaweqcan You check https://review.openstack.org/#/c/483817/ as native speaker? :)15:39
*** sridharg has quit IRC15:40
*** pcaruana has joined #openstack-meeting15:40
*** rmascena has joined #openstack-meeting15:40
davidshaslaweq: Sure!15:40
slaweqthx15:40
ralonsohhahaha I "use" davidsha for the same porpuse some times hahahahaha15:40
slaweqthat's all for me15:40
*** armax has joined #openstack-meeting15:40
slaweq:)15:41
davidsha:P15:41
ralonsohthanks davidsha, slaweq!15:41
*** sridharg has joined #openstack-meeting15:41
davidshaThanks!15:41
ralonsoh#endmeeting15:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:41
openstackMeeting ended Tue Aug  1 15:41:27 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-08-01-15.01.html15:41
slaweqbye15:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-08-01-15.01.txt15:41
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-08-01-15.01.log.html15:41
*** andreas_s has quit IRC15:41
ralonsohbye15:41
*** sridharg has quit IRC15:42
*** raildo has quit IRC15:42
*** eharney_ has joined #openstack-meeting15:43
*** donghao has quit IRC15:44
*** annegentle has quit IRC15:46
*** oidgar has joined #openstack-meeting15:46
*** eharney has quit IRC15:46
*** designbybeck_ has joined #openstack-meeting15:48
*** unicell has quit IRC15:48
*** eharney_ is now known as eharney15:48
*** rossella_s has quit IRC15:48
*** e0ne has quit IRC15:50
*** annegentle has joined #openstack-meeting15:50
*** rcernin has joined #openstack-meeting15:50
*** rossella_s has joined #openstack-meeting15:50
*** iceyao has joined #openstack-meeting15:54
*** jlibosva has joined #openstack-meeting15:54
*** emagana has quit IRC15:58
*** iceyao has quit IRC15:58
*** emagana has joined #openstack-meeting15:59
*** YanXing_an has quit IRC16:00
*** Apoorva has joined #openstack-meeting16:00
jlibosvao/16:00
ihrachys#startmeeting neutron_ci16:00
openstackMeeting started Tue Aug  1 16:00:58 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
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
ihrachys#topic Actions from prev week16:01
*** openstack changes topic to "Actions from prev week (Meeting topic: neutron_ci)"16:01
ihrachys"haleyb to reach out to QA PTL about switching grenade integrated gate to multinode"16:01
ihrachyslast comments in https://review.openstack.org/#/c/483600/ suggest there is more leg work there16:01
ihrachystalking to all projects affected16:01
* haleyb did, needs to contact additional PTLs to get their sign-off as well16:02
* haleyb is lurking for a few more minutes16:02
ihrachys#action haleyb to reach out to all affected parties, and FBI, to get multinode grenade by default16:02
ihrachysnext is "jlibosva to recheck the tools/kill.sh patch until it hits timeout and report back"16:02
jlibosvaI did16:03
jlibosvabut didn't find anything useful16:03
*** lpetrut has quit IRC16:03
ihrachysI believe on the team meeting today we figured it did not help much16:03
jlibosvasec16:03
ihrachysI reported https://bugs.launchpad.net/neutron/+bug/170793316:03
openstackLaunchpad bug 1707933 in neutron "functional tests timeout after a test worker killed" [Critical,Confirmed]16:03
*** emagana has quit IRC16:03
jlibosvaI see that worker was killed here: http://logs.openstack.org/65/487065/5/check/gate-neutron-dsvm-functional-ubuntu-xenial/f9b22b8/console.html#_2017-07-31_08_05_43_07444716:03
jlibosvaat 08:05:4316:04
jlibosvathere were 'kill' called around that time, but none with worker's pid16:04
ihrachyswhat is so special about FirewallTestCase ?16:05
ihrachysor probably BaseFirewallTestCase16:05
ihrachysbecause ipv6 class also affected16:05
jlibosvawhat do you mean?16:06
*** emagana has joined #openstack-meeting16:06
ihrachyswell, almost all breakages have firewall tests timing out in the end, no?16:06
ihrachysso the workers die on running firewall tests16:06
jlibosvait's unclear to me if the test kills itself or it kills other running test16:07
jlibosvabut there is a RootHelperProcess class (or something like that)16:07
*** makowals has quit IRC16:07
jlibosvathat takes care of finding correct pid to kill16:07
ihrachysok, but again, why firewall tests are killed, even if those are not the source of kills?16:07
ihrachysmaybe it's just because they are slow?16:07
ihrachysso the chance of hitting them is high?16:08
jlibosvaI don't think it has anything to do with how fast they are16:08
jlibosvathere is an eventlet timeout per test16:08
jlibosvaso slow tests should raise an exception if they don't finish in time16:08
jlibosvaIIRC16:08
*** claudiub has quit IRC16:08
*** makowals has joined #openstack-meeting16:09
*** janki has quit IRC16:10
ihrachysno, I mean, it seems like we see firewall tests involved when kill happens; it's either because there is some bug in the test; or because a bug happens somewhere else, but it's just that firewall tests take a huge chunk of total time that it hits them so often.16:10
jlibosvaaha16:10
jlibosvaone interesting thing I just noticed is that the "Killed" message in console is actually almost a minute after last log in the killed test16:11
*** Patifa has joined #openstack-meeting16:11
ihrachysby the brief look at the log, it doesn't seem that those tests are too long, or their number is huge16:11
*** cbest47__ has joined #openstack-meeting16:11
jlibosvamaybe I'll also add a ps output to the kill.sh, so we know which process is being killed16:12
ihrachysjlibosva, how do you determine the killed test? the one that is 'inprogress' at the end of the run?16:12
*** links has joined #openstack-meeting16:12
jlibosvaihrachys: yes, also you can see that e.g. in the console log I sent, executor {3} doesn't run any other tests after Killed message16:12
jlibosvaihrachys: while there are tests from {0} {1] and {2} workers16:12
ihrachysI wonder if this ~1 minute delay stands for other failure instances16:13
jlibosvaone other thing would be to change signals in firewall tests to SIGTERM and then register handler in base test class for such signal16:13
ihrachyswhatis 'change signals'16:14
jlibosvadefault uses SIGKILL16:14
jlibosvafor killing nc processes that are used to test whether traffic can or cannot pass through16:14
*** Manuel_112 has joined #openstack-meeting16:15
*** lakerzhou has quit IRC16:16
jlibosvaso if we change from SIGKILL to SIGTERM, we would be able to catch it and reveal more info16:16
*** lakerzhou has joined #openstack-meeting16:16
jlibosvawhat do you think?16:17
ihrachyssorry, I am not that into the test, so I can't find which piece of it starts nc16:17
ihrachysoh that's assert_connection ?16:17
*** ricolin has joined #openstack-meeting16:17
*** vishwana_ has quit IRC16:18
ihrachysok I see where it finally bubbles down to RootHelperProcess16:19
jlibosvaihrachys: it's NetcatTester16:19
*** vishwanathj has joined #openstack-meeting16:19
*** Manuel_112 has quit IRC16:20
jlibosvaanyways, I'll try to come up with some more patches, we've already spent a lot of meeting time on this :)16:21
jlibosvawe can come up with ideas on the LP eventually16:21
ihrachysok16:21
ihrachysnext was "haleyb to look at why dvr grenade flavour surged to 30% failure rate comparing to 0% for other grenades"16:21
ihrachysI don't think there was progress on that one?16:22
ihrachysok let's repeat it, haleyb is probably gone16:23
ihrachys#action haleyb to look at why dvr grenade flavour surged to 30% failure rate comparing to 0% for other grenades16:23
ihrachysoh I missed one16:23
ihrachys"jlibosva to classify current scenario failures and send email to openstack-dev@ asking for help"16:23
*** aarefiev is now known as aarefiev_afk16:23
jlibosvaI did and did16:23
ihrachysI saw the email16:24
ihrachyswas there any progress that emerged from it?16:24
jlibosvahttp://lists.openstack.org/pipermail/openstack-dev/2017-July/120294.html16:24
jlibosvaslaweq sent a patch to enable qos as he wants to work on it16:24
ihrachysthat is abandoned now16:24
ihrachysprolly because yamamoto had the same16:24
jlibosvayeah16:24
jlibosvahttps://review.openstack.org/#/c/46832616:25
ihrachysthe yamamoto patch https://review.openstack.org/#/c/46832616:25
jlibosvait also seems there might be no work item and it works now16:25
ihrachysok16:25
jlibosvaI don't know what fixed the scenario or it just has a low repro rate16:25
ihrachyslet's land then and see?16:25
jlibosvayep16:25
ihrachysI +2d16:26
ihrachysapart from those qos tests?16:26
jlibosvaarmax looked at trunk failure which turned out a regression in ovs firewall16:26
ihrachysbtw the etherpad tracking the progress at https://etherpad.openstack.org/p/neutron-dvr-multinode-scenario-gate-failures16:26
jlibosvahttps://bugs.launchpad.net/neutron/+bug/170733916:27
openstackLaunchpad bug 1707339 in neutron "test_trunk_subport_lifecycle fails on subport down timeout" [High,In progress] - Assigned to Armando Migliaccio (armando-migliaccio)16:27
jlibosvaI've been working on it today16:27
jlibosvaI'll send out patch soon, I'm writing just some basic UTs16:27
ihrachysnice16:28
jlibosvaother than that, it doesn't seem as popular as python3 effort16:28
ihrachystempest is hard16:28
jlibosvaI plan to take one failure at a time and do something about it, but I've been recently quite busy16:29
ihrachyswe can maybe ask once again, mentioning the progress and asking for more :)16:29
ihrachysI imagine16:29
ihrachysI can do the shout out16:29
jlibosvaif you have some cookies to promise, maybe that will help :)16:29
*** kaisers has quit IRC16:29
ihrachyscookie or a stick, hm. tough choice.16:30
ihrachysnext was "haleyb to check why dvr-ha job is at ~100% failure rate"16:30
*** VW has quit IRC16:30
ihrachysI talked to haleyb about that16:30
*** davidsha has quit IRC16:30
ihrachysand it seems like this a devstack-gate provisioning issue16:30
ihrachyshttps://bugs.launchpad.net/neutron/+bug/170700316:30
openstackLaunchpad bug 1707003 in neutron "gate-tempest-dsvm-neutron-dvr-ha-multinode-full-ubuntu-xenial-nv job has a very high failure rate" [High,Confirmed] - Assigned to Brian Haley (brian-haley)16:30
ihrachysthere is a patch that tackles a similar problem, in grenade (abandoned)16:30
ihrachysand we will probably need smth similar, but in devstack-gate, since this job is not even grenade16:31
ihrachysand Brian is going to work on it16:31
ihrachysI imagine it may take a while16:31
ihrachysfirst, because d-g16:31
ihrachyssecond, because reviews there are rare16:31
ihrachys:)16:31
*** yamahata has joined #openstack-meeting16:31
ihrachys#topic Grafana16:32
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:32
ihrachyshttp://grafana.openstack.org/dashboard/db/neutron-failure-rate16:32
*** dpertin has quit IRC16:32
ihrachysthere is a periodic failure for -pg- job again16:32
ihrachysI noticed it today and sent an email to armax about it16:32
ihrachysseems like another instance of sqlalchemy not being ready for -pg-16:32
ihrachysthere is a sql syntax error in cinder api16:33
ihrachysthere is fullstack still at 80%, and I actually started playing with the test locally yesterday (no progress yet)16:33
jlibosvaabout pg, have you seen the patch about testing pg?16:33
ihrachysgood thing it reproduces just fine16:33
ihrachysjlibosva, which one?16:33
* jlibosva looking16:33
jlibosvahttps://review.openstack.org/#/c/427880/16:34
ihrachysoh that's old news yeah16:34
jlibosvatldr, warns users that pg is not thoroughly tested, I wonder whether it is worth the effort to support pg in gate16:34
ihrachysstill it seems like we have armax interested in doing it16:34
ihrachysI proposed removal of the job in the past16:34
ihrachysand armax was all against it and jumped fixing issues16:35
jlibosvaI remember, but it was before this was approved16:35
jlibosvaok16:35
ihrachysI don't think it changes much if we just do it best effort16:35
ihrachysif someone benefits from it and maintains it above the water, I am good16:35
jlibosvaokies16:36
ihrachysthere is one failure spike that I think is new16:36
ihrachysfor linuxbridge grenade multinode job16:36
ihrachyscurrently at 45%16:36
ihrachysI know that the job was never stable because of https://bugs.launchpad.net/neutron/+bug/168325616:37
openstackLaunchpad bug 1683256 in neutron "linuxbridge multinode depending on multicast support of provider" [High,Confirmed] - Assigned to omkar_telee (omkar-telee)16:37
ihrachysKevin was going to look at it in the past, but it never happened16:37
ihrachysand I wonder if that's a sign that we should deprovision the job16:37
ihrachysbecause the only reason why we haven't a cycle ago was that Kevin was going to make it work16:37
ihrachysI guess I will send another patch removing other people jobs and see how they react ;)16:38
ihrachys#action ihrachys to propose a removal for linuxbridge grenade multinode job16:38
ihrachysI suspect there is this multicast AND something else going on there but I have no will to dig16:39
*** armstrong has quit IRC16:40
ihrachys#topic Open discussion16:40
*** openstack changes topic to "Open discussion (Meeting topic: neutron_ci)"16:40
*** sshank has joined #openstack-meeting16:40
ihrachysjlibosva, progress on ovs isolation for fullstack?16:40
jlibosvanah16:40
jlibosva:)16:40
ihrachysack :)16:40
ihrachysanything else?16:40
jlibosvaI have one topic thou16:40
jlibosvayep16:40
jlibosvaI was pinged by ironic guys16:40
*** armstrong has joined #openstack-meeting16:40
jlibosvathey are getting hit in grenade job by neutron16:40
*** marios has quit IRC16:40
ihrachysbug number?16:40
jlibosvahttps://bugs.launchpad.net/neutron/+bug/170716016:40
openstackLaunchpad bug 1707160 in neutron "test_create_port_in_allowed_allocation_pools test fails on ironic grenade" [Undecided,Confirmed]16:40
jlibosvawhich probably leads to https://bugs.launchpad.net/neutron/+bug/170535116:41
openstackLaunchpad bug 1705351 in neutron "agent notifier getting amqp NotFound exceptions propagated up to it" [High,In progress] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)16:41
*** annp has quit IRC16:41
jlibosvaI looked at the logs of the failed job and it seemed to me that client times out after 60 seconds and then retries the operation16:41
jlibosvathe thing is that the first operation succeeds after some time > 60 secs and then the second "retry" fails16:42
jlibosvaso they bumped the cli timeout to 120s but still are getting hit16:42
jlibosvaI didn't have time to look at why they get hit again16:42
jlibosvabut I thought it was worth raising here even though it's not Neutron CI but some neutron failure :)16:42
*** lpetrut has joined #openstack-meeting16:42
* ihrachys tries to understand why the 2nd bug is assigned to him16:43
jlibosvayou sent a patch to catch some exceptions16:43
jlibosvaiirc16:43
ihrachysoh, a partial bug16:43
jlibosvahttps://review.openstack.org/#/c/486687/16:43
ihrachysjlibosva, how does the 1st bug lead to 2nd? can you elaborate?16:44
ihrachysthe 2nd is about an exception raised16:44
ihrachysbecause of exchange missing16:44
*** ijw has quit IRC16:44
*** hashar has quit IRC16:44
ihrachysthe former looks more like dns misconfigured or smth else locking the processing thread for long time16:44
jlibosvawhat I saw was subnet delete in the ironic gate - the delete was trying to notify dhcp agents they should delete their resources16:45
jlibosvabut due to some amqp issue, rpc was failing or stuck (don't remember), which cause the operation of subnet deletion to take 97 seconds16:45
jlibosvaand the tempest rest client called subnet delete again after 60 seconds, but the first call eventually succeeded, while the second failed16:46
jlibosvacause subnet was already gone16:46
ihrachysso, one of reasons I am aware of for a thread to lock on rpc is dns misconfigured, so oslo.messaging takes a while to get response from libresolv with ipv4/ipv6 addresses.16:46
jlibosvaso the delay on the server side was caused by the amqp issue16:46
*** armstrong has quit IRC16:46
ihrachysjlibosva, not THE issue, but A issue, right?16:47
*** bobh has quit IRC16:47
*** abalutoiu has joined #openstack-meeting16:47
ihrachysin the server log, I see AMQP server on 149.202.183.40:5672 is unreachable: timed out16:47
ihrachyswhich probably suggests it's not dns16:48
ihrachys(the broker is referred to via ip)16:48
jlibosvaI'm referring to amqp as THE :)16:48
jlibosvaIIRC there was a trace about missing queue or something16:48
ihrachysoh yeah, i see "NotFound: Basic.publish: (404) NOT_FOUND - no exchange 'q-agent-notifier-port-delete_fanout' in vhost '/'"16:49
ihrachysthen the 2nd bug is indeed relevant16:49
ihrachyswith the fix landed on neutron side for this, I guess we may ask ironic folks if they are still affected?16:50
*** sshank has quit IRC16:50
jlibosvamakes sense16:51
jlibosvabut I don't have much knowledge about the failure there16:51
jlibosvajust wanted to raise it here16:51
ihrachysack, thanks for that16:52
ihrachysI will update them about the fix in LP16:52
ihrachysanything else?16:52
jlibosvanot from me16:52
ihrachyscool. thanks for joining.16:52
ihrachys#endmeeting16:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:52
openstackMeeting ended Tue Aug  1 16:52:45 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-08-01-16.00.html16:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-08-01-16.00.txt16:52
jlibosvathanks, bye16:52
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-08-01-16.00.log.html16:52
*** jlibosva has left #openstack-meeting16:52
*** oidgar has quit IRC16:53
*** oidgar has joined #openstack-meeting16:53
*** zeih has joined #openstack-meeting16:53
*** sshank has joined #openstack-meeting16:55
*** slaweq has quit IRC16:56
*** zeih has quit IRC16:58
*** bobh has joined #openstack-meeting16:58
*** pcaruana has quit IRC16:58
*** toscalix has quit IRC16:58
*** lpetrut has quit IRC16:59
*** emagana has quit IRC16:59
*** baoli has quit IRC17:00
*** oidgar has quit IRC17:01
*** ralonsoh has quit IRC17:02
*** Akilles has joined #openstack-meeting17:04
*** baoli has joined #openstack-meeting17:05
*** slaweq has joined #openstack-meeting17:07
*** Akilles has quit IRC17:08
*** baoli has quit IRC17:11
*** lpetrut has joined #openstack-meeting17:11
*** cdub has joined #openstack-meeting17:13
*** jamesmcarthur has joined #openstack-meeting17:14
*** cbest47__ has quit IRC17:14
*** baoli has joined #openstack-meeting17:15
*** Manuel_112 has joined #openstack-meeting17:16
*** vishnoianil has joined #openstack-meeting17:17
*** Manuel_112 has quit IRC17:21
*** annabelleB has quit IRC17:24
*** sambetts is now known as sambetts|afk17:24
*** kaisers has joined #openstack-meeting17:26
*** cloudrancher has quit IRC17:32
*** cloudrancher has joined #openstack-meeting17:33
*** kaisers has quit IRC17:35
*** emagana has joined #openstack-meeting17:37
*** VW has joined #openstack-meeting17:38
*** VW has quit IRC17:40
*** VW has joined #openstack-meeting17:40
*** gyee has joined #openstack-meeting17:41
*** yamahata has quit IRC17:43
*** spilla has joined #openstack-meeting17:43
*** electrofelix has quit IRC17:43
*** palexster has quit IRC17:44
*** palexster has joined #openstack-meeting17:44
*** kaisers has joined #openstack-meeting17:48
*** Julien-zte has quit IRC17:50
*** Julien-zte has joined #openstack-meeting17:52
*** gagehugo has joined #openstack-meeting17:54
*** slaweq has quit IRC17:56
*** slaweq has joined #openstack-meeting17:57
*** links has quit IRC17:57
*** cloudrancher has quit IRC17:57
*** cloudrancher has joined #openstack-meeting17:58
*** baoli has quit IRC17:59
*** Apoorva_ has joined #openstack-meeting17:59
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Aug  1 18:00:08 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
*** baoli has joined #openstack-meeting18: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
lbragstadping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, notmorgan, rderose, rodrigods, samueldmq, spilla, aselius, dpar18:00
cmurphyohai18:00
edmondswo/18:00
knikollao/18:00
rodrigodshey18:00
gagehugoo/18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
*** baoli has quit IRC18:00
lbragstadagenda ^18:00
spillao/18:00
* cmurphy actually here today18:00
lamto/18:00
*** Apoorva_ has quit IRC18:00
lbragstadwow - y'all *almost* broke down the door18:00
*** baoli has joined #openstack-meeting18:01
rmascenao/18:01
*** Apoorva has quit IRC18:01
*** Apoorva_ has joined #openstack-meeting18:01
*** slaweq has quit IRC18:01
*** slaweq has joined #openstack-meeting18:01
lbragstadlet's give it a minute or two for others to show up18:01
knikollathe light agenda maybe :P18:01
lbragstadknikolla: possibly!18:01
lbragstadi won't lie - i don't mind the meeting being done in 30 minutes or less18:02
*** markvoelker has quit IRC18:02
*** markvoelker has joined #openstack-meeting18:02
lbragstad#topic announcements: release status18:03
*** openstack changes topic to "announcements: release status (Meeting topic: keystone)"18:03
rarorao/18:03
*** ekcs has joined #openstack-meeting18:03
lbragstadlast week we released pike-3 on schedule18:03
lbragstad#link https://review.openstack.org/#/c/488411/18:04
lbragstadwe also released the final version of python-keystoneclient for pike18:04
lbragstad#link https://review.openstack.org/#/c/488413/18:04
lbragstadthe only this is that pike-3 went out the door without project tags18:04
*** apetrich has quit IRC18:04
*** cdub has quit IRC18:04
lbragstadso - that's going to have to be one of the first things on our plate for queens18:05
lbragstadthanks to rarora gagehugo lamt spilla and others for putting in all the work there18:05
*** apetrich has joined #openstack-meeting18:05
*** jamesmcarthur has quit IRC18:05
*** pvaneck has joined #openstack-meeting18:05
lbragstadthat should be a pretty easy win to start queens off with18:06
lbragstad#topic announcements: specs18:06
*** openstack changes topic to "announcements: specs (Meeting topic: keystone)"18:06
gagehugoyeah it's pretty close18:06
*** VW_ has joined #openstack-meeting18:06
lbragstadbut - we also need to clean up the specs repository to accurately reflect the things we didn't make into pike18:06
lbragstad#link https://review.openstack.org/#/c/487534/18:06
lbragstad#link https://review.openstack.org/#/c/487533/18:06
*** ijw has joined #openstack-meeting18:07
*** ijw has quit IRC18:07
lbragstadi've proposed bumping application creds and federated attributes to backlog until we're ready to start parsing what we want to go through for queens18:07
*** ijw has joined #openstack-meeting18:07
lbragstadproject tags will also needs a patch to bump it18:07
lbragstadto backlog18:07
gagehugoI can edit https://review.openstack.org/#/c/484529/ for that18:07
gagehugomove it to backlog with those edits18:08
lbragstadgagehugo: cool - thanks18:08
edmondswmight want to move it to backlog separately and then get agreement on the edits18:08
lbragstad#action gagehugo to propose https://review.openstack.org/#/c/484529/ to backlog until queens opens for development18:08
*** VW has quit IRC18:09
*** slagle has quit IRC18:09
lbragstadwe have a lot of work that spilled over from pike this release - i think a big part of the PTG is going to be keeping discussions fresh to that we can carry things over gracefully18:09
*** cdub has joined #openstack-meeting18:10
knikollayeah18:10
gagehugoedmondsw will do18:10
lbragstadi'll get into that a bit more later18:10
lbragstadnow that we are in feature freeze18:10
lbragstad#topic bugs18:10
*** openstack changes topic to "bugs (Meeting topic: keystone)"18:10
lbragstadwe should be ultra focused on bugs, bug review, and triage18:10
lbragstad#link https://goo.gl/F7Pc8x18:11
lbragstad^ that's a list of all bugs that are targetting pike-rc18:11
*** slagle has joined #openstack-meeting18:11
*** cdub has quit IRC18:11
lbragstadso - ideally, we need to have those fixed before we can get pike out the door18:11
lbragstadif there is a bug in that list that you don't feel needs to be included in pike, let me know18:11
lbragstadon the contrary, if there *is* a release blocking bug that pops up - let me know18:12
lbragstadi'll be attending to that list daily for the rest of the release - reviewing and picking up whatever changes i can18:12
*** galstrom_zzz is now known as galstrom18:13
lbragstadany questions on the current bug list?18:13
*** armstrong has joined #openstack-meeting18:13
*** EmilienM is now known as emacchi18:14
lbragstadthe good thing is that most of those bugs are in progress, so reviews should really help trim that list down18:14
edmondswmicroversions made the rc bug cut?18:14
*** emacchi is now known as EmilienM18:14
lbragstadedmondsw: this one?18:14
lbragstad#link https://bugs.launchpad.net/keystone/+bug/168964418:14
openstackLaunchpad bug 1689644 in OpenStack Identity (keystone) "Keystone does not report microversion headers" [Medium,In progress] - Assigned to Rohan Arora (ra271w)18:14
lbragstadedmondsw: or microversion support in general?18:14
edmondswyeah... how quickly things can change. It was nearly unanimous at the PTG that we wouldn't do microversions :)18:15
knikollawell… that's not really doing microversions :P18:15
*** cdub has joined #openstack-meeting18:15
lbragstadknikolla: right - it's just communicating it to the caller18:15
lbragstadreal support for microversions still needs to be done18:15
edmondswhow can you report microversions if you don't have microversions?18:15
lbragstadedmondsw: the current approach returns 3.0 and 3.818:16
lbragstadas the min and max api versions18:16
*** trinaths has left #openstack-meeting18:16
lbragstadfor v318:16
lbragstadand 2.0 for v2.018:16
lbragstadbut the approach is still in review18:16
edmondswsounds fun18:17
*** Manuel_112 has joined #openstack-meeting18:17
lbragstadmoving on18:18
lbragstad#topic ptg planning18:18
*** openstack changes topic to "ptg planning (Meeting topic: keystone)"18:18
lbragstadi have an etherpad up to capture ideas we want to discuss at the PTG18:18
lbragstad#link https://etherpad.openstack.org/p/keystone-queens-ptg18:18
*** kaisers has quit IRC18:19
lbragstadand we're getting to the point where I need to start grouping things in bucket and organizing meeting times with other groups if we want to discuss cross-project things18:19
lbragstadi assume the PTG is going to break down much like it did in Atlanta18:19
lbragstadwhere the first couple days are going to be dedicated to cross-project initiatives18:19
lbragstadand the last three are going to be project-focused18:19
*** lhx_ has quit IRC18:20
gagehugowill there be a policy meeting for cross-project?18:20
lbragstadgagehugo: i fully expect to have one - yes18:20
gagehugocool18:20
*** yamahata has joined #openstack-meeting18:20
lbragstadit's one of the first topics i added for the cross-project section in the planning etherpad18:20
cmurphythere's a schedule https://docs.google.com/spreadsheets/d/1xmOdT6uZ5XqViActr5sBOaz_mEgjKSCY7NEWcAEcT-A/edit#gid=39724131218:20
lbragstadalong with unified limits, application creds, etc...18:21
lbragstadcmurphy: oh - good call18:21
cmurphyand yeah looks like cross project stuff will be more monday/tuesday18:21
lbragstadcool18:21
lbragstadalso - i sent out a reminder asking who was going to be attending18:22
*** Manuel_112 has quit IRC18:22
gagehugothere was short 1 hr meetings too at ATL, for some cross-project stuff18:22
lbragstadthe foundation would like to have an accurate estimate so that they can line up rooms properly18:22
gagehugoidk how that works with the schedule18:22
*** AJaeger has joined #openstack-meeting18:22
lbragstadif you're planning on attending the PTG please add your name to https://etherpad.openstack.org/p/keystone-queens-ptg if you haven't already done so18:23
lbragstadgagehugo: yeah - i wasn't there the first two days in ATL18:23
edmondswlbragstad I will be there, but will probably be sitting in the nova room more than keystone18:23
lbragstadedmondsw: ack18:24
lbragstadedmondsw: i think we have a few people in that boat18:24
lbragstadwhich is fine18:24
knikollaas long as you join us for beer after, we're good18:24
lbragstadthis is what i wanted to spend the majority of the time on today18:24
edmondsw:)18:25
lbragstadis there anything on the current planning doc that people don't agree with?18:25
lbragstadis there anything you *do* agree with?18:25
*** slaweq has quit IRC18:25
lbragstadI'd like to get an idea of where people's interests lie and what they are hoping to work on and accomplish in pike18:25
lbragstad(as a way to keep expectations in line and sane)18:26
*** slaweq has joined #openstack-meeting18:26
knikollahmm.. is dstanek going to be there for the native saml topic?18:26
lbragstadPersonally for me - i'm going to be dedicating time to global role assignments  (along with championing community goals for policy)18:27
knikollahe was championing it18:27
lbragstadknikolla: he was - but I doubt he will make it to the PTG18:27
lbragstadknikolla: i haven't heard anything yet18:27
*** cdub has quit IRC18:27
cmurphyapp creds definitely a high priority for pike18:27
lbragstadi completely agree18:27
knikollacmurphy: ++18:27
*** armstrong has quit IRC18:28
knikollai also want to see federated attributes. i'll probably pick it up if intel folks don't find the time to work on it.18:28
lbragstadthen again - unified limits has some pretty awesome payoffs and advantages that would be nice to have18:28
lbragstadwe also have to take a peak at oslo.policy to see if we can enhance it so that we can emit deprecation warnings when policy changes18:28
* lbragstad is already feeling overwhelmed18:29
cmurphy@.@18:29
knikollathat's why we have 3 days at the ptg18:29
*** slaweq has quit IRC18:29
*** slaweq has joined #openstack-meeting18:30
knikollalbragstad: how is read-only role a project specific thing?18:30
edmondswlbragstad looking at the room schedule, which of those rooms do you plan to have policy discussions in?18:30
*** slaweq has quit IRC18:31
gagehugoyeah we should grab a room for that18:31
lbragstadknikolla: good catch - moved18:31
lbragstadedmondsw: the biggest one we can find?18:31
edmondswlol18:31
edmondswrow 18?18:32
knikollalol18:32
lbragstadedmondsw: the discussion we had in ATL was packed18:32
knikollai think that'll be detrimental18:32
lbragstador18:32
lbragstadwe coax people off-site?18:32
edmondswthe API WG room was packed in ATL, and covered more than API WG stuff... maybe talk to them about carving out time there?18:33
lbragstadbut row 18 looks like it will work18:33
*** annegentle has quit IRC18:33
gagehugoyeah the API-WG room in ATL was interesting18:33
lbragstadwe also don't need *every* project developer there18:33
lbragstadi also assume there are going to be project developers who don't care about policy18:33
knikollacontact your elected policy representative today :P18:33
lbragstadbut I'd figure at least 3 - 5 developers from each interested project?18:33
edmondswI'd kinda like it to be a dedicated room so people know that's going to be the topic and come accordingly18:33
knikollayeah, it being the nova room last time wasn't good.18:34
edmondswlbragstad that's some serious optimism! would be great18:34
edmondswhaving policy changes as a goal for queens should help attendance18:34
knikollahonestly, i think teams should have a policy liason going forward18:34
edmondswand we can talk about more than policy-in-code18:34
lbragstadyeah18:35
edmondswknikolla ++18:35
*** slaweq has joined #openstack-meeting18:35
lbragstadright - we really need to talk about breaking the scope check and putting it into code18:35
* edmondsw nods vigorously18:35
lbragstadit'd be nice to make some progress on a standard set of roles we should provide by default18:35
*** armstrong has joined #openstack-meeting18:35
edmondswlbragstad that's a short list in my opinion... admin, member, observer18:36
lbragstadyeah - but we can couple that with fixing admin-ness and isolating scope to in-code only and we're in a much better place18:37
edmondswmaybe add a few internal roles, e.g. service, that we wouldn't expect end-users to ever have18:37
edmondswabsolutely18:37
lbragstadi'm really looking forward to doing what's needed to have those discussions in Denver18:38
lbragstadbut i'm also thinking it's going to take up most of my bandwidth for queens18:38
knikollaseems fair. given that it's the single most important thing for now.18:38
lbragstadyeah - in addition to application creds18:39
lbragstadwhich i think have massive usability benefits18:39
knikollayeah, but requires less coordination with other teams18:39
*** markstur has quit IRC18:39
*** annabelleB has joined #openstack-meeting18:39
lbragstadyeah - we need to come to consensus on how to use them18:39
*** ijw has quit IRC18:39
*** slaweq has quit IRC18:40
knikollabesides the lifetime of an app cred. i thought that pretty much there was consensus?18:40
lbragstadknikolla: yeah- i think the lifecycle is really the only thing left to discuss18:40
lbragstad(there is some additional details about roping it into policy in the future, too)18:41
lbragstads/is/are/18:41
*** julim_ has quit IRC18:41
*** annabelleB has quit IRC18:41
*** vishnoianil has quit IRC18:41
lbragstaddoes anyone have things they'd like to get on the map for the PTG?18:42
*** julim has joined #openstack-meeting18:42
* lbragstad feels like he's been doing a lot of talking18:42
*** vishnoianil has joined #openstack-meeting18:42
knikollai think the list is pretty comprehensive.18:42
lbragstad++ some topics are going to be pretty dense18:43
knikollai'd like to get another shot at revising 'role check in middleware' if folks want18:43
*** annabelleB has joined #openstack-meeting18:43
lbragstadknikolla: hrybacki was talking to me about that a few weeks ago18:43
lbragstadknikolla: you should be sure to check in with him18:44
knikollasounds good.18:44
*** VW_ has quit IRC18:44
lbragstad#topic open discussion18:44
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:44
lbragstadfloor is open18:44
*** spilla has quit IRC18:44
*** ijw has joined #openstack-meeting18:46
lbragstadlooks like we can get some time back18:46
lbragstadoffice hours starts in about 14 minutes18:46
lbragstadthanks for coming!18:46
lbragstad#endmeeting18:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:47
openstackMeeting ended Tue Aug  1 18:47:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-08-01-18.00.html18:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-08-01-18.00.txt18:47
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-08-01-18.00.log.html18:47
*** VW has joined #openstack-meeting18:47
*** VW has quit IRC18:47
*** gagehugo has left #openstack-meeting18:47
*** jkilpatr has quit IRC18:47
*** VW has joined #openstack-meeting18:48
*** jamesmcarthur has joined #openstack-meeting18:51
*** armstrong has quit IRC18:52
*** annabelleB has quit IRC18:52
*** sshank has quit IRC18:52
*** armstrong has joined #openstack-meeting18:53
*** annabelleB has joined #openstack-meeting18:53
*** armstrong has quit IRC18:54
*** zeih has joined #openstack-meeting18:54
*** armstrong has joined #openstack-meeting18:55
*** pchavva has quit IRC18:55
*** annabelleB has quit IRC18:58
*** adisky__ has quit IRC18:58
*** bobh has quit IRC18:58
*** jkilpatr has joined #openstack-meeting18:58
*** vishnoianil has quit IRC18:58
*** vishnoianil has joined #openstack-meeting18:59
*** zeih has quit IRC19:00
fungiinfra team, $ASSEMBLE_SYNONYM!19:00
AJaeger\o/19:00
ianwmorning!19:00
fungii've spent, like, no time preparing this week, so apologies for being disorganized19:00
fungithis week we have action items assigned to and topics proposed by fungi and (i think) clarkb19:01
cmurphyo/19:01
clarkbgcc -c -o infra.o ?19:01
fungiprobably need to link in a standard meeting library19:01
fungianyhoo, let's get this party started19:02
AJaegerclarkb: without -o ;)19:02
fungi#startmeeting infra19:02
openstackMeeting started Tue Aug  1 19:02:43 2017 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
pabelangero/19:02
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
fungi#topic Announcements19:03
jeblairo/19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
*** tosky has joined #openstack-meeting19:03
fungi#info Don't forget to register for the PTG if you're planning to attend19:03
fungi#link https://www.openstack.org/ptg/  PTG September 11-15 in Denver, CO, USA19:03
fungi#info Inactive accounts for several former infra-root sysadmins are being disabled; we thank them for their awesome service to the community and welcome them back any time!19:05
clarkbdoes that come with a plaque to hang on their walls?19:05
fungi#link https://review.openstack.org/489698 Disable inactive infra-root accounts19:05
jeblairclarkb: more like a plague19:06
fungiif only we had funding for placards19:06
fungibut yes, they can hang a plague on their walls i suppose19:06
jeblairfungi: you can send them stickers19:06
* mordred waves19:06
AJaegersigned by everybody?19:06
fungii do indeed have stickers19:06
funginot a terrible idea19:06
fungi"see, if you come back, you can get even _more_ stickers"19:07
pabelanger++19:07
fungias always, feel free to hit me up with announcements you want included in future meetings19:07
fungi#topic Actions from last meeting19:07
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:07
*** sshank has joined #openstack-meeting19:07
fungi#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-07-25-19.03.html Minutes from last meeting19:07
fungi#action fungi get switchport counts for infra-cloud19:08
fungistill waiting to get word back from hpe at this point19:08
fungithat was the only one we had from last meeting, looks like19:08
fungi#topic Specs approval19:08
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:08
fungiwe don't seem to have anything new up this week19:08
*** _pewp_ has quit IRC19:09
fungi#topic Priority Efforts - Gerrit 2.13 Upgrade: Request for testing (clarkb)19:09
*** openstack changes topic to "Priority Efforts - Gerrit 2.13 Upgrade: Request for testing (clarkb) (Meeting topic: infra)"19:09
clarkbthe zuul testing got done and everything worked great once we got tobiash's change in place19:10
clarkbwithout that we did indeed see funny behavior and lack of ability to submit changes19:10
*** kaisers has joined #openstack-meeting19:10
jeblairwe still need to merge that to zuul master, right?19:10
jeblairand we should only do that after we change the label case in our current layout.yaml19:10
clarkbjeblair: yes. I think it is still an open question about how to do that to master since it is backward incompatible (but allows greater gerrit compatibility)19:11
fungioh, hrm, might need to be toggleable?19:11
jeblair1) send email telling folks to change case; 2) change our case; 3) wait 1 week; 4) merge change ?19:11
clarkbthinking about schedules for upgrading zuul and gerrit I think we (infra we) may not need it on zuulv2 but we likely want to support our other zuul users on v2 with newer gerrit as well19:11
jeblairclarkb: ah, if we're pushing gerrit upgrade to post-ptg, then maybe leave master hanging?19:12
*** _pewp_ has joined #openstack-meeting19:12
*** sshank has quit IRC19:12
*** ijw has quit IRC19:12
clarkbjeblair: ya I'm thinking we can point zuulv2 users to the patch and they can apply locally if they find they need it19:12
clarkbthat way we don't have to worry about breaking people with existing installs19:13
jeblairwfm19:13
*** Shrews has joined #openstack-meeting19:13
clarkbthe other big item is removing reliance on the gerrit contact store feature which no logner exists in gerrit 2.1319:13
fungiwe got a bit near to release frenzy to feel safe taking a long downtime and significant behavior changes to the review system until next cycle19:14
clarkbfungi has edits to the election roll generation scripts pushed up to update election roll generation which relied on the coupling of accounts via contact store19:14
clarkbfungi: yup19:14
fungiat this point the only thing we needed the contact store for is that19:14
clarkbfor the contact store stuff when can we update gerrit config to disable it? we can do that before we upgrade to 2.13 right?19:14
fungiso we can in theory disable it whenever we want, though i'd like to have ptl elections behind us using the updated script19:15
clarkbfungi: maybe you can push a change to update the config when you are comfortable doing so?19:15
fungiyeah, i'll write that up in the next few days19:15
clarkband that leads us to scheduling the actual upgrade19:15
clarkblast week was openstack feature freeze so we are deep into release activities and infra being slushy19:15
fungireally the risk that someone will create a new account, not join the foundaiton, create a change, get it merged in a project with more than one ptl candidate and be surprised they didn't get a ballot is likely vanishingly small at this point19:16
fungibetween now and the contribution cut-off for qualifying to vote in the upcoming elections anyway19:16
clarkbpike releases august 31, we then have a week without release or other major activity, then ptg, then another empty week19:16
clarkbI think our good options for upgrading gerrit are teh week before or the week after ptg. I don't know how much stuff we want before ptg with plans for zuul upgrade19:17
*** jamesmcarthur has quit IRC19:17
clarkbwhcih leaves us with doing it week after ptg whcih is why I don't think we need to worry about case sensitivty fix on zuul master19:18
*** annegentle has joined #openstack-meeting19:18
*** kaisers has quit IRC19:18
fungiwell, not without any release activity... the cycle-trailing projects are scrambling during that timeframe, as is documentation19:18
*** Manuel_112 has joined #openstack-meeting19:18
pabelangerI don't mind week after PTG, unless we need 2.13 before PTG19:18
clarkbfungi: those happen during ptg I think19:18
AJaegernot sure about documnetation - we should have moved all release critical stuff to the project repos...19:18
fungiclarkb: fair point, they do indeed19:18
*** jamesmcarthur has joined #openstack-meeting19:19
fungiclarkb: though there is still run-up to that release activity in the intervening week19:19
clarkbI spoke to the release team this morning as well and they were happy with week before or after ptg19:19
clarkbfungi: ya19:19
fungicool19:19
clarkbalso we have to do a full offline reindex so expect the downtime to easily be 5 hours or so probably longer19:19
fungiAJaeger: that helps too, thanks19:19
fungiright, this'll be one of those where we have it down for a good chunk of a weekend or something19:20
clarkbseptember 17 18 19 20 21 22 23 is week after ptg19:21
fungimay need to make sure we start early in the day on whatever day we pick, and/or plan to have people available to take over monitoring the reindex and ready to pick up the remaining tasks after that completes19:21
clarkbyup I think early day to start is good idea and that way we don't have to leave it offline overnight19:21
*** tobiash has joined #openstack-meeting19:21
*** hashar has joined #openstack-meeting19:21
fungi"early in the day" relative to the bulk of the people volunteering19:22
clarkbI'm thinking doing it monday the 18th might be a good option because people will be traveling and returning to work and shouldn't have as much a reliance on gerrit (but thats an assumption based on not really any data)19:22
clarkbI fly home saturday myself19:22
*** Manuel_112 has quit IRC19:22
fungiyeah, i'll be available that monday if there's consensus around it19:22
pabelangersame, fly home on saturday19:23
pabelangerMonday works for me19:23
fungii can also get some prep going before the western americas volunteers if wanted19:23
fungisince i'll be awake a little earlier19:23
clarkbany other input from infra-roots on doing it monday?19:23
fungithough if we have emea folk wanting to help with some of the early tasks that's cool too19:24
jeblairlogistically it works for me; a little concerned about doing it at start of week and not friday19:24
jeblairclarkb: but i think you may be on to something with your post-ptg travel/burnout idea19:25
fungii recall a not so distant upgrade where we though doing it right before the weekend would be a good idea, and then didn't spot issues with it until activity picked up on monday19:25
jeblairwe'll just have to push through our own burnout.  :)19:25
fungis/though/thought/19:25
clarkbright so doing it at the end of the week is the alternative. The upside to that is it will give us more tiem to prep without worrying about travel. Downsides are less friendly to emea and potentially makes that week really short for many PTGers19:25
jeblairfungi: see, we enjoyed the weekend!  :)19:25
fungithis is true19:25
clarkbthe other nice thing about friday is if we have to go into the next day it is saturday and not tuesday19:25
*** kaisers has joined #openstack-meeting19:25
fungiyou certainly have an interesting definition of "nice" ;)19:26
clarkbwell for our users not necessarily us :)19:26
jeblairi think you've pushed me over the fence; slight preference for monday here19:26
clarkbfungi: the no users on saturday problem is a good point too I hadn't really considered19:26
clarkbfungi: I think that makes me prefer monday19:26
clarkbshould we tentatively say 1500UTC monday and europe and east coast can get things rolling (I'll likely wake up early myself)19:27
fungiwfm19:27
clarkbthat then gives us basically all day for north americans to finish it up19:27
clarkbok why don't we pencil that in and I'll send email about it tomorrow if no one can think of a reason to change it by then19:28
fungiohh19:28
AJaegerclarkb: and then hand over to Australia and back to Europe ;)19:28
fungii need to check my calendar real quick :/19:28
fungiyup, just confirmed that date sounded familiar... i may need to get permission for monday the 18th as that's my wife's birthday19:29
clarkbuh oh19:29
clarkbfungi: should we leave it penciled in while you talk about it? or should we not even push it :)19:30
fungilet's say that's still the tentative plan, best case i just need to skip out early for dinner reservations or something19:30
clarkbok19:30
fungiworst case i can't help with the upgrade, but we have more people19:30
*** emagana has quit IRC19:30
jeblairfungi: you volunteered for the early shift anyway :)19:31
fungitoo true19:31
clarkbI think that is about it for gerrit then. If you haven't get given 2.13 a go on review-dev  please do so and give feedback19:31
*** baoli has quit IRC19:31
clarkbI confirmed it fixes the verified +1 but rechecked doesn't go into gate problem19:31
clarkbso event stream does what zuul needs there to make the right choices19:31
fungi#agreed Tentative Gerrit 2.13 upgrade date is Monday, September 18; outage starting around 15:00 UTC19:31
fungithat sound about like what we agreed on?19:32
clarkbyup19:32
jeblairya19:32
fungihow long before the upgrade do we need to announce it on the lists?19:32
clarkbthink about it if there is a reason not to do it then let everyone know and we can rethink. But I want to send notice to the dev list soon. Probably tomorrow evening19:32
clarkbjust to give them as much lead time as possible19:32
*** emagana has joined #openstack-meeting19:33
fungithat's some 7 weeks from yesterday i guess?19:33
clarkbyup19:33
AJaegerwhat about asking release team t oadd to their calendar at https://releases.openstack.org/pike/schedule.html - or queens?19:33
fungiso definitely a nice advance warning19:33
clarkbAJaeger: we could do that, not sure what they will say about it. I'lldo that after our meeting19:34
clarkb*ask them, but only update once ml post is sent19:34
fungiand what's the deal with the change screen? i guess polygerrit doesn't happen until 2.14 right?19:34
AJaegerclarkb: agreed19:34
clarkbfungi: you can run polygerrit against 2.13 but it isn't bundled as an option like it is in 2.1419:34
clarkbso I was mostly ignoring polygerrit for 2.1319:35
tobiashwe don't have polygerrit in our 2.1319:35
clarkbwe can always deploy polygerrit bits later if we want (requires separate daemon and all that)19:35
fungiokay, good, so not a lot of ui adjustment for people this time anyway19:35
fungii'm not so certain infra maintenance stuff is a fit for the release calendar, but we'll see what they say19:35
clarkb2.14 is going to be a big upgrade in all the ways19:36
*** rcernin has quit IRC19:36
clarkbnotedb, java 8, polygerrit, etc. That is why I didn't try pivoting to it, 2.13 is much simpler and easier to get done19:36
*** slaweq has joined #openstack-meeting19:36
fungiyup19:36
fungi#action clarkb send advance notice of Gerrit 2.13 upgrade to mailing lists19:36
fungiokay, anything else you wanted to cover before we switch topics?19:37
clarkbnope that is all I had, thanks19:37
fungithanks!19:37
fungi#topic Priority Efforts - Zuul v3 (jeblair)19:37
*** openstack changes topic to "Priority Efforts - Zuul v3 (jeblair) (Meeting topic: infra)"19:37
*** jamesmcarthur has quit IRC19:37
fungilast-minute addition at jeblair's request19:38
jeblairhi!  i mostly wanted to point out mordred's draft email about the ptg zuulv3 cutover19:38
*** baoli has joined #openstack-meeting19:38
jeblair#link draft zuulv3 cutover announcement https://etherpad.openstack.org/p/ImHsFudauN19:38
fungithanks for the reminder. i need to make sure to read that shortly after the meeting19:38
jeblairhopefully we can send that out soon (like today, tomorrow?)19:39
mordred++19:39
fungimordred: you're planning to send that one i take it?19:39
AJaegerwould be nice to merge https://review.openstack.org/#/c/489677 - so that mordred can link to it from his email19:39
mordredfungi: yah - as soon as folks are ok with it19:39
mordredAJaeger: ++19:39
fungi#action mordred send advance notice of Zuul v3 cutover to mailing lists19:39
jeblairand i had a suggestion at the end to link to an infra-manual page where we can have a living document to help devs with the transition19:40
jeblairwhich is what AJaeger just linked19:40
fungiawesome. also on my priority review list19:40
jeblairprobably that first change is enough for now.  it has an introduction, answers some basic questions, and has a skeleton we can fill in later.19:41
jeblairso i think once that change lands, it's enough to link to from the announcement email as long as we contextualize it as a work in progress which will be more complete as we approach cutover19:41
*** slaweq has quit IRC19:41
jeblairit's also 1 of three sets of docs i think we need before we go live:19:42
jeblairopenstack developer transition guide, zuul documentation, and job documentation19:42
jeblairi'm working on getting the last published and cross-linked this week19:43
jeblair(and continuing to improve zuul docs)19:43
jeblairthat's eot from me19:43
fungiexcellent. sounds entirely tractable19:43
fungiquestions?19:43
*** kaisers has quit IRC19:44
*** jkilpatr_ has joined #openstack-meeting19:44
fungicrickets? tumbleweeds?19:44
fungithanks jeblair!19:44
fungi#topic PTG planning (fungi)19:45
*** openstack changes topic to "PTG planning (fungi) (Meeting topic: infra)"19:45
fungi#link https://etherpad.openstack.org/p/infra-ptg-queens Infra planning pad for Queens PTG in Denver19:46
*** jkilpatr has quit IRC19:46
fungiseems we've grown a few more ideas there, this is shaping up nicely19:46
*** kaisers has joined #openstack-meeting19:46
fungii see a number of things that clearly fit into either the helproom timeframe on monday/tuesday or as stuff we can hack on wednesday-friday19:47
*** sshank has joined #openstack-meeting19:48
jeblairi agree with fungi's typing19:48
fungii've tried to tag them just now19:49
*** julim has quit IRC19:49
clarkbI see the tags19:49
jeblairwhat do we need to do to schedule that zuulv3 session thingy?19:49
fungi[reserve] is for stuff where we should reserve a slot in one of the cross-project rooms19:49
fungithere will be an ethercalc page19:49
fungialready is19:49
jeblairwhen do we do it?19:50
fungi#link https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms Pike PTG - Extra Discussion Rooms schedule19:50
fungii think just pick times and stick stuff there19:51
fungifirst come, first served19:51
fungi30-minute slots, and the instructions say don't do more than two consecutive19:51
fungiso we can book hour-long double slots if we need19:51
jeblairmonday is locked19:52
fungii wonder if there's a reason for that19:53
fungidiablo_rojo or ttx might know, if either are around19:53
jeblairi assume we can unlock it, but yeah, it may be best to assume that's on purpose and ask first.  :)19:53
*** kaisers has quit IRC19:53
jeblairassuming it's possible, something like macon, monday, 2pm?19:54
fungisounds reasonable19:54
fungithat's early enough in the week but after lunch19:54
jeblairyeah, i assume we'll be very busy before lunch.19:54
fungithat's my expectation as well19:55
jeblairmaybe still after lunch too, but gotta do it sometime.  :)19:55
clarkbas will everyone else19:55
fungiwe could try to do 1:30-2:30 in macon but it'll likely be a slow start with everyone wrapping up lunch19:55
jeblairand oh yeah, should we try to keep it to 30m?19:55
fungialternative would be to overlap neutron/ironic or service catalog discussions19:56
jeblairmaybe increase the likelihood that people will actually show up if we keep it brief19:56
*** eharney has quit IRC19:56
fungicould also do 4:30-5:30 but the first half of that overlaps a watcher discussion and the second half people will likely be scouting nearby bars alerady19:56
fungialready19:56
fungiif you think half an hour is a good target for the session, i'm down with that plan19:57
jeblairit will be rushed, but i think that will be good.  i can literally talk for hours about this stuff.19:57
jeblairno one wants that19:57
fungiand not expecting more than ~50 attendees?19:58
jeblairwould be useful to have more.  think it'll happen?19:58
fungialso plan to expect neutron/ironic people who may be disinterested in the topic wandering into macon before 2:3019:58
clarkbmy ptg room on debugging the gate was packed the first day, almost empty the second19:58
*** vishnoianil has quit IRC19:59
clarkbso I expect yuo'll get quite a few people to show up if you do it once :)19:59
fungiokay, we're about out of time19:59
jeblairi'll try to get something scheduled19:59
*** vishnoianil has joined #openstack-meeting19:59
*** baojg has quit IRC20:00
fungithanks jeblair! i'll see if diablo_rojo or ttx can enlighten us on any reason for the locked monday cells20:00
*** bobh has joined #openstack-meeting20:00
fungithanks everyone for a productive meeting!20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Aug  1 20:00:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
*** VW_ has joined #openstack-meeting20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-08-01-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-08-01-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-08-01-19.02.log.html20:00
*** baojg has joined #openstack-meeting20:00
*** Shrews has left #openstack-meeting20:00
*** AJaeger has left #openstack-meeting20:01
funginote, no tc meeting scheduled for this week, but join the tc for office hours coming up at 01:00 utc in #openstack-tc20:01
*** priteau has quit IRC20:01
*** dprince has quit IRC20:04
*** VW has quit IRC20:04
*** VW_ has quit IRC20:04
*** e0ne has joined #openstack-meeting20:09
*** tobiash has left #openstack-meeting20:09
*** emagana has quit IRC20:10
*** tosky has left #openstack-meeting20:10
*** eharney has joined #openstack-meeting20:11
*** emagana has joined #openstack-meeting20:11
*** awaugama has quit IRC20:12
*** kaisers has joined #openstack-meeting20:15
*** emagana has quit IRC20:16
*** vishnoianil has quit IRC20:17
*** annabelleB has joined #openstack-meeting20:18
*** vishnoianil has joined #openstack-meeting20:18
*** Manuel_112 has joined #openstack-meeting20:19
*** emagana has joined #openstack-meeting20:21
*** mtanino has joined #openstack-meeting20:22
*** Manuel_112 has quit IRC20:24
*** kaisers has quit IRC20:25
*** e0ne has quit IRC20:25
*** armstrong has quit IRC20:26
*** slaweq has joined #openstack-meeting20:27
*** baoli has quit IRC20:29
*** e0ne has joined #openstack-meeting20:30
*** vishnoianil has quit IRC20:34
*** lpetrut has quit IRC20:35
*** vishnoianil has joined #openstack-meeting20:35
*** baoli has joined #openstack-meeting20:38
*** cleong has quit IRC20:39
*** emagana has quit IRC20:39
*** emagana has joined #openstack-meeting20:40
*** ijw has joined #openstack-meeting20:43
*** gordc has joined #openstack-meeting20:45
*** gordc has left #openstack-meeting20:49
*** zhhuabj has quit IRC20:54
*** zeih has joined #openstack-meeting20:55
*** galstrom is now known as galstrom_zzz20:58
*** zeih has quit IRC21:00
*** armstrong has joined #openstack-meeting21:00
*** ekcs has quit IRC21:01
*** galstrom_zzz is now known as galstrom21:01
*** abalutoiu has quit IRC21:02
*** galstrom is now known as galstrom_zzz21:03
*** zhhuabj has joined #openstack-meeting21:08
*** marst has quit IRC21:09
*** baoli has quit IRC21:13
*** baoli has joined #openstack-meeting21:13
*** ihrachys has quit IRC21:15
*** awaugama has joined #openstack-meeting21:16
*** yamamoto has joined #openstack-meeting21:17
*** baoli has quit IRC21:19
*** Manuel_112 has joined #openstack-meeting21:20
*** yamamoto has quit IRC21:21
*** yamamoto has joined #openstack-meeting21:21
*** lakerzhou has quit IRC21:22
*** Manuel_112 has quit IRC21:24
*** yamamoto has quit IRC21:26
*** eharney has quit IRC21:27
*** e0ne has quit IRC21:28
*** sshank has quit IRC21:29
*** vishnoianil has quit IRC21:31
*** emagana has quit IRC21:34
*** kaisers has joined #openstack-meeting21:35
*** emagana has joined #openstack-meeting21:36
*** sshank has joined #openstack-meeting21:37
*** ykatabam has joined #openstack-meeting21:45
*** jkilpatr_ has quit IRC21:49
*** jamesmcarthur has joined #openstack-meeting21:51
*** ijw has quit IRC21:52
*** unicell has joined #openstack-meeting21:52
*** designbybeck_ has quit IRC21:54
*** jamesmcarthur has quit IRC21:56
*** esberglu has quit IRC21:58
*** rmascena has quit IRC22:00
*** slaweq has quit IRC22:03
*** slaweq has joined #openstack-meeting22:03
*** mikal has quit IRC22:04
*** thorst_afk has quit IRC22:05
*** mikal has joined #openstack-meeting22:06
*** annegentle has quit IRC22:06
*** slaweq has quit IRC22:08
*** jkilpatr has joined #openstack-meeting22:08
*** kylek3h has quit IRC22:12
*** esberglu has joined #openstack-meeting22:12
*** kylek3h has joined #openstack-meeting22:13
*** kylek3h has quit IRC22:13
*** emagana has quit IRC22:14
*** emagana has joined #openstack-meeting22:16
*** bobh has quit IRC22:16
*** esberglu has quit IRC22:17
*** emagana has quit IRC22:17
*** emagana has joined #openstack-meeting22:17
*** emagana has quit IRC22:17
*** emagana has joined #openstack-meeting22:18
*** thorst_afk has joined #openstack-meeting22:19
*** Manuel_112 has joined #openstack-meeting22:20
*** kaisers has quit IRC22:22
*** yamamoto has joined #openstack-meeting22:23
*** esberglu has joined #openstack-meeting22:23
*** ijw has joined #openstack-meeting22:23
*** thorst_afk has quit IRC22:24
*** yamamoto has quit IRC22:25
*** yamamoto has joined #openstack-meeting22:25
*** Manuel_112 has quit IRC22:26
*** hashar has quit IRC22:28
*** julim has joined #openstack-meeting22:29
*** sdague has quit IRC22:35
*** edmondsw has quit IRC22:36
*** annegentle has joined #openstack-meeting22:45
*** https_GK1wmSU has joined #openstack-meeting22:53
*** https_GK1wmSU has left #openstack-meeting22:53
*** zeih has joined #openstack-meeting22:56
*** sshank has quit IRC22:57
*** ijw has quit IRC22:58
*** zeih has quit IRC23:01
*** annegentle has quit IRC23:04
*** esberglu has quit IRC23:06
*** fnaval has quit IRC23:06
*** pvaneck has quit IRC23:06
*** mattoliverau_ has joined #openstack-meeting23:09
*** armstrong has quit IRC23:10
*** esberglu has joined #openstack-meeting23:12
*** sshank has joined #openstack-meeting23:13
*** mattoliverau has left #openstack-meeting23:13
*** sshank has quit IRC23:17
*** Patifa has quit IRC23:19
*** chyka has quit IRC23:19
*** Manuel_112 has joined #openstack-meeting23:21
*** fnaval has joined #openstack-meeting23:21
*** mattoliverau_ is now known as mattoliverau23:25
*** kaisers has joined #openstack-meeting23:26
*** Manuel_112 has quit IRC23:26
*** mtanino has quit IRC23:26
*** hongbin has quit IRC23:30
*** jaypipes has quit IRC23:31
*** baojg_ has joined #openstack-meeting23:33
*** baojg has quit IRC23:34
*** kaisers has quit IRC23:36
*** chyka has joined #openstack-meeting23:42
*** gouthamr has quit IRC23:43
*** cloudrancher has quit IRC23:45
*** julim has quit IRC23:46
*** cloudrancher has joined #openstack-meeting23:46
*** chyka has quit IRC23:49
*** ijw has joined #openstack-meeting23:52
*** markvoelker has quit IRC23:53
*** julim has joined #openstack-meeting23:59

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