Tuesday, 2018-12-04

*** munimeha1 has quit IRC00:09
*** jamesmcarthur has joined #openstack-meeting00:26
*** jamesmcarthur has quit IRC00:31
*** yamamoto has quit IRC00:38
*** lbragstad has quit IRC01:07
*** yamamoto has joined #openstack-meeting01:10
*** yamamoto has quit IRC01:21
*** isq_ has joined #openstack-meeting01:23
*** jamesmcarthur has joined #openstack-meeting01:24
*** yamahata__ has quit IRC01:24
*** yamamoto has joined #openstack-meeting01:28
*** jamesmcarthur has quit IRC01:34
*** jamesmcarthur has joined #openstack-meeting01:35
*** takamatsu has quit IRC01:37
*** jamesmcarthur has quit IRC01:38
*** hongbin has joined #openstack-meeting01:43
*** jamesmcarthur has joined #openstack-meeting01:49
*** jamesmcarthur has quit IRC01:51
*** jamesmcarthur has joined #openstack-meeting01:53
*** jamesmcarthur has quit IRC01:57
*** jamesmcarthur has joined #openstack-meeting02:04
*** jamesmcarthur has quit IRC02:07
*** jamesmcarthur has joined #openstack-meeting02:07
*** gyee has quit IRC02:14
*** dmacpher has joined #openstack-meeting02:29
*** mhen has quit IRC02:37
*** mhen has joined #openstack-meeting02:41
*** jamesmcarthur has quit IRC02:42
*** liuyulong has joined #openstack-meeting02:42
*** hyunsikyang has quit IRC02:43
*** jamesmcarthur has joined #openstack-meeting02:45
*** psachin has joined #openstack-meeting02:48
*** imacdonn has quit IRC02:52
*** imacdonn has joined #openstack-meeting02:52
*** cloudrancher has quit IRC02:54
*** cloudrancher has joined #openstack-meeting02:55
*** tashiromt has joined #openstack-meeting03:01
*** hongbin_ has joined #openstack-meeting03:11
*** hongbin has quit IRC03:13
*** nguyenhai_ has joined #openstack-meeting03:18
*** hongbin has joined #openstack-meeting03:22
*** nguyenhai has quit IRC03:22
*** dklyle has joined #openstack-meeting03:23
*** onovy has quit IRC03:23
*** hongbin_ has quit IRC03:23
*** onovy has joined #openstack-meeting03:25
*** david-lyle has quit IRC03:25
*** iyamahat has quit IRC03:28
*** armax has quit IRC03:28
*** yamahata has quit IRC03:29
*** tpatil has joined #openstack-meeting03:55
*** mriedem_away has quit IRC03:58
samPHi all for Masakari04:00
samP#startmeeting masakari04:00
openstackMeeting started Tue Dec  4 04:00:07 2018 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: masakari)"04:00
openstackThe meeting name has been set to 'masakari'04:00
samPtpatil: Hi04:00
samPLet's start!04:01
samPtashiromt: Hi04:01
samP#topic Critical bugs and patches04:01
*** openstack changes topic to "Critical bugs and patches (Meeting topic: masakari)"04:02
samPAny critical patch or bug needs to discuss04:02
tpatilI have noticed you have approved back ported patch to fix osc command issue04:02
tpatil#link : https://review.openstack.org/#/c/621490/04:02
samPyes, just now04:02
tpatilsamP: Can you please review this patch : https://review.openstack.org/#/c/616068/04:05
*** ShilpaSD has joined #openstack-meeting04:06
tpatilsamP: Thanks04:06
samPmoving to next topic. you may bring up bug or patch related issues any time in this meeting..04:07
samP#topic Stein Work Items04:07
*** openstack changes topic to "Stein Work Items (Meeting topic: masakari)"04:08
samPPlease state if you have any update on Stein work items04:08
tpatilAdd events and progress_details for various notification failures04:09
tpatilI waschecking taskflow library to figure out how to store this event info and progress_details and finally got a way to do this04:10
tpatilI will write a specs to describe about it04:10
samPtpatil: thanks04:11
*** jamesmcarthur has quit IRC04:11
*** whoami-rajat has joined #openstack-meeting04:12
tpatilNotification API Implementation04:13
tpatilShilpa will update the task status04:14
tpatilShilpaSD: Do you have any update about this feature?04:15
*** Nel1x has quit IRC04:15
ShilpaSDWorking in review comments, and removal of code for which there were notifications set for recovery04:16
samPIs this review in gerrit?04:16
ShilpaSDAnd also working on documentation for same04:16
ShilpaSDyes its in local gerrit04:17
tpatilsamP: This patch is not up for gerrit review. She is fixing internal review comments04:17
samPShilpaSD: Thanks. Got it.04:17
samPtpatil: got it. thanks04:18
ShilpaSDthanks Tushar san04:18
samPAbout the release and deadlines.04:21
samP#link https://releases.openstack.org/stein/schedule.html04:22
samPStein-2 is Jan 07-11. I prefer to merge all the specs before this04:22
tpatilAdd events and progress_details for various notification failures, this feature will take some time04:23
samPStein-3 is Mar 04-08. A week before RC1. We better finish all the all the work planed to ship in Stein04:23
samPtpatil: spec need time?04:24
tpatilsamP: Yes, I still need to design the feature04:24
tpatilWe will manage to complete everything in milestone-3 i.e. Mar 04-0804:25
samPtpatil: no problem. That was a general dead line for the specs.04:25
tpatilSpecs will be done soon but the implementation might take time beyond Jan 07-1104:27
samPtpatil: Thanks.04:27
samPIf nothing else to share, we can finish today's meeting04:27
tpatilNo more info to share from my end04:29
tashiromtthere is no topic from our side04:29
samPOK Then. Thank you all for your time.04:30
samPPlease use openstack-dev ML with [masakari] or find us in IRC #openstack-masakari @freenode for further discussion.04:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:31
openstackMeeting ended Tue Dec  4 04:31:14 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-12-04-04.00.html04:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-12-04-04.00.txt04:31
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2018/masakari.2018-12-04-04.00.log.html04:31
tpatilUse openstack-discuss and not openstack-dev ML04:31
*** jamesmcarthur has joined #openstack-meeting04:39
*** tashiromt has quit IRC04:41
*** tpatil has quit IRC05:01
*** diablo_rojo has quit IRC05:05
*** janki has joined #openstack-meeting05:22
*** binh_ has joined #openstack-meeting05:32
*** hongbin has quit IRC05:39
*** gcb_ has joined #openstack-meeting06:06
*** sridharg has joined #openstack-meeting06:11
*** gcb_ has quit IRC06:11
*** liuyulong has quit IRC06:24
*** iyamahat has joined #openstack-meeting06:25
*** apetrich has quit IRC06:37
*** Liang__ has joined #openstack-meeting06:44
*** Luzi has joined #openstack-meeting06:46
*** jamesmcarthur has quit IRC06:47
*** takamatsu has joined #openstack-meeting06:53
*** radeks_ has joined #openstack-meeting07:04
*** radeks__ has joined #openstack-meeting07:07
*** radeks_ has quit IRC07:09
*** pcaruana has joined #openstack-meeting07:10
*** apetrich has joined #openstack-meeting07:24
*** arne_wiebalck has joined #openstack-meeting07:29
*** rcernin has quit IRC07:38
*** joxyuki has joined #openstack-meeting07:38
*** ttsiouts has joined #openstack-meeting07:40
*** hadai has joined #openstack-meeting07:56
*** phuoc has joined #openstack-meeting07:57
*** ttsiouts_ has joined #openstack-meeting07:58
*** bhagyashris_ has joined #openstack-meeting07:59
*** longkb has joined #openstack-meeting08:00
*** ttsiouts has quit IRC08:01
*** belmoreira has joined #openstack-meeting08:01
*** dkushwaha has joined #openstack-meeting08:02
dkushwaha#startmeeting tacker08:03
openstackMeeting started Tue Dec  4 08:03:07 2018 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:03
*** openstack changes topic to " (Meeting topic: tacker)"08:03
openstackThe meeting name has been set to 'tacker'08:03
dkushwaha#topic Roll Call08:03
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:03
dkushwahawho is here for Tacker weekly meeting?08:03
dkushwahahi bhagyashris_08:04
dkushwahaphuoc, hi08:04
phuocdkushwaha, bhagyashris_ hi :)08:04
dkushwahaseems no more members available08:06
dkushwaha#chair phuoc08:06
openstackCurrent chairs: dkushwaha phuoc08:06
joxyukihi, I'm late08:06
dkushwahajoxyuki, hello08:06
dkushwaha#topic BPs08:07
*** openstack changes topic to "BPs (Meeting topic: tacker)"08:07
phuocabout force delete BP08:08
dkushwahaphuoc, have you pushed any patch? If so link please08:09
phuocI uploaded 2 patch sets: https://review.openstack.org/#/c/620381 and https://review.openstack.org/#/c/62038508:09
dkushwahaphuoc, great08:09
phuocwe can start with client first, and I can update in Tacker server later08:10
dkushwahaphuoc, https://review.openstack.org/#/c/620385/1/tacker/api/v1/base.py08:11
dkushwahaphuoc, in #39708:11
dkushwahawhat body will have?08:11
*** tpatil has joined #openstack-meeting08:11
phuocdkushwaha, body likes {'vnf': {'attributes': {'force': True}}}08:13
phuocyou can see it here, https://review.openstack.org/#/c/620381/2/tackerclient/tacker/v1_0/vnfm/vnf.py08:13
*** iyamahat has quit IRC08:14
*** takamatsu has quit IRC08:15
dkushwahaphuoc, sounds good08:16
dkushwahaphuoc, do you have plan to push patch, resource specific or combine patch for all08:16
dkushwahalike VNF, VNFFG08:17
*** ttsiouts_ has quit IRC08:17
phuocI prefer separate them into 3 parts08:17
*** ttsiouts has joined #openstack-meeting08:18
dkushwahaphuoc, fine. Ok I will update the spec accordingly08:18
dkushwahamoving on08:20
*** ralonsoh has joined #openstack-meeting08:20
dkushwahaBP Mistral workflow monitoring08:20
dkushwaha#link https://review.openstack.org/#/c/486924/08:20
dkushwahaphuoc, regarding your comment08:21
dkushwahaDo you mean to use new context (i.e. generate_tacker_service_contex) for monitoring ??08:22
*** ttsiouts has quit IRC08:22
phuocI think you can update it like this way08:23
phuocbecause I see in your patch, some parameters are fixed08:25
dkushwahaphuoc, yea, i have to remove those hardcoded values.08:25
*** liuyulong has joined #openstack-meeting08:26
dkushwahabut I am not sure, how generate_tacker_service_contex will be helpful here08:26
phuocremoving hard coded is fine to me08:27
dkushwahaok, I will re-look my patch again, and will fix your comments08:28
dkushwahamoving on08:29
dkushwahabhagyashris_, do you have something to discuss ?08:29
bhagyashris_Thank you dkushwaha, joxyuki and phuoc for your response regarding HealVnfRequest data http://paste.openstack.org/show/735705/  .08:29
bhagyashris_Now I will start the implement of vdu_autoheal monitoring policy action according to the request data mentioned in reference link.08:30
bhagyashris_One thing would like to propose here is Should we use versioned object for HealVnfRequest data.08:30
*** ianychoi has quit IRC08:30
*** nguyenhai_ has quit IRC08:30
*** ianychoi has joined #openstack-meeting08:30
*** nguyenhai_ has joined #openstack-meeting08:31
*** trident has quit IRC08:31
dkushwahabhagyashris_, what is mean by "version object" ?08:31
*** trident has joined #openstack-meeting08:32
joxyukiI don't think so, because API has its version in URI08:33
*** jasonyan has quit IRC08:34
bhagyashris_I mean version object means https://github.com/openstack/oslo.versionedobjects/tree/master/oslo_versionedobjects08:34
tpatildkushwaha: What Bhagyashri is suggesting is instead of passing dict everywhere let's start using oslo Versioning objects08:34
tpatildkushwaha: We can start using oslo_versionedobjects for HealVNFRequest08:35
dkushwahatpatil, is there any related link? kindly share the same08:36
dkushwahai needs to look into that08:36
phuocI didn't tried it, so I want to see how it works08:36
tpatilIn nova project it is used widely08:36
bhagyashris_Currently all the core projects are using the Oslo versioned objects https://github.com/openstack/nova/tree/master/nova/objects08:37
dkushwahaphuoc, any suggestion on that. ^^08:38
dkushwahatpatil, bhagyashris_ I will check first and then let you know08:38
phuocI think we can do that way08:39
joxyukiI will check it too.08:39
tpatilThe drawback of dict is you don't know what attributes are present in HealVNFRequest or a VNF. If you convert it to oslo versioned object, it will be clear08:40
tpatilFor now, we suggest to implement it for HealVNFRequest and in future we can implement it for all cases08:41
phuocit's fine to me08:42
tpatilphuoc: Thanks08:42
joxyukitpatil, do you have an exmple of other case?08:42
tpatilVNF dict, it's a big one08:42
joxyukiOK, got it.08:43
dkushwahabhagyashris_, tpatil sounds good as other core projects also using the same. so it seems fine to me.(although in between i will explore it and let you know in case of any query)08:43
tpatilVNFD, Triggers etc etc08:43
dkushwahabinh_, hi08:44
bhagyashris_dkushwaha, joxyuki phuoc: ok. Thank you :)08:44
*** jamesmcarthur has joined #openstack-meeting08:44
*** takamatsu has joined #openstack-meeting08:46
binh_I'm research08:46
joxyukibinh_, hello08:46
binh_Im same lab with phuoc08:46
dkushwahabinh_, welcome to Tacker team. Could you please introduce yourself08:46
binh_Nice to meet you guys08:46
binh_I'm currently a research of DCN lab at Soongsil university08:47
phuocbinh_ is my colleague08:47
*** a-pugachev has joined #openstack-meeting08:47
phuoche have an idea about service graph https://docs.openstack.org/networking-sfc/latest/contributor/ietf_sfc_encapsulation.html08:47
dkushwahabinh_, nice.08:47
phuocI hope you guys can help him to finish that feature :)08:47
binh_yeah, thank you all :D08:48
binh_my full name is Nguyen Hiep Binh08:48
binh_you can call me binh08:48
binh_I intent to implement branching and joining SFC path08:49
binh_base on networking-sfc ietf encapsulation as Phuoc mention above08:49
*** jamesmcarthur has quit IRC08:50
dkushwahabinh_, phuoc will it go in Tacker side or networking-sfc?08:50
*** jasonyan has joined #openstack-meeting08:50
binh_It's will go on Tacker side and call networking-sfc08:50
dkushwahabinh_, i see08:50
binh_We need define some template to call that APIs08:51
dkushwahabinh_, Have you drafted any doc etc?08:52
*** ttsiouts has joined #openstack-meeting08:52
binh_I will upload the spec on next week or next next week08:54
dkushwahabinh_, cool08:54
*** rubasov has left #openstack-meeting08:55
dkushwahabinh_, good to see you in Team, and welcome once again.08:55
dkushwahamoving on08:56
binh_i will inform you guys when it finish08:56
binh_ok thank you08:56
dkushwaha#topic Open Discussion08:56
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:56
phuocI have a patch to update SFC encapsulation https://review.openstack.org/#/c/62068008:57
phuocneed some reviews on that patch, thanks :)08:57
*** jamesmcarthur has joined #openstack-meeting08:58
dkushwahaphuoc, Ok, I will review it08:58
phuocthank you08:59
dkushwahaI am thinking to land CSAR package BP in Stein08:59
dkushwaha#link https://review.openstack.org/#/c/582930/08:59
dkushwahaI seems owner is not available now a days09:00
dkushwahaSo hopefully, I will start working on that byt next week09:00
phuocthat's great09:00
joxyukidkushwaha, great09:00
dkushwahaThats all from my side09:01
dkushwahaDo we have something more to discuss?09:01
*** jamesmcarthur has quit IRC09:02
phuocnothing from me09:02
dkushwahaok, Thanks all.09:02
dkushwahaClosing this meeting for now09:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:03
openstackMeeting ended Tue Dec  4 09:03:17 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-12-04-08.03.html09:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-12-04-08.03.txt09:03
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-12-04-08.03.log.html09:03
*** joxyuki has quit IRC09:07
*** takamatsu has quit IRC09:14
*** takamatsu has joined #openstack-meeting09:16
*** lbragstad has joined #openstack-meeting09:24
*** jawad_axd has joined #openstack-meeting09:27
*** priteau has joined #openstack-meeting09:30
*** tssurya has joined #openstack-meeting09:31
*** aojea has joined #openstack-meeting09:32
*** jamesmcarthur has joined #openstack-meeting09:33
*** tpatil has quit IRC09:37
*** jamesmcarthur has quit IRC09:38
*** e0ne has joined #openstack-meeting09:44
*** kopecmartin|off is now known as kopecmartin09:46
*** takamatsu has quit IRC09:49
*** takamatsu has joined #openstack-meeting09:50
*** bhagyashris_ has quit IRC09:54
*** yamamoto has quit IRC09:59
*** yamamoto has joined #openstack-meeting10:08
*** yamamoto has quit IRC10:08
*** hadai has quit IRC10:12
*** takamatsu has quit IRC10:13
*** ralonsoh has quit IRC10:23
*** ralonsoh has joined #openstack-meeting10:23
*** erlon has joined #openstack-meeting10:25
*** electrofelix has joined #openstack-meeting10:34
*** jamesmcarthur has joined #openstack-meeting10:34
*** ttsiouts has quit IRC10:36
*** ttsiouts has joined #openstack-meeting10:37
*** ttsiouts_ has joined #openstack-meeting10:38
*** ttsiouts has quit IRC10:42
*** jawad_axd has quit IRC10:43
*** takamatsu has joined #openstack-meeting10:50
*** ttsiouts_ has quit IRC11:01
*** ttsiouts has joined #openstack-meeting11:01
*** takamatsu has quit IRC11:04
*** takamatsu has joined #openstack-meeting11:05
*** ttsiouts has quit IRC11:06
*** yamamoto has joined #openstack-meeting11:22
*** longkb has quit IRC11:22
*** yamamoto has quit IRC11:35
*** e0ne has quit IRC11:35
*** e0ne has joined #openstack-meeting11:38
*** ttsiouts has joined #openstack-meeting11:45
*** ttsiouts has quit IRC11:54
*** ttsiouts has joined #openstack-meeting11:55
*** ttsiouts has quit IRC11:59
*** vabada has joined #openstack-meeting11:59
*** vabada has quit IRC11:59
*** vabada has joined #openstack-meeting12:00
*** jawad_axd has joined #openstack-meeting12:11
*** lbragstad has quit IRC12:21
*** lbragstad has joined #openstack-meeting12:22
*** phuoc has left #openstack-meeting12:23
*** lbragstad has quit IRC12:23
*** ttsiouts has joined #openstack-meeting12:23
*** lbragstad has joined #openstack-meeting12:24
*** lbragsta_ has joined #openstack-meeting12:27
*** shrasool has joined #openstack-meeting12:29
*** lbragsta_ has quit IRC12:31
*** lbragstad has quit IRC12:31
*** lbragstad has joined #openstack-meeting12:38
*** jamesmcarthur has quit IRC12:39
*** Douhet has quit IRC12:41
*** Douhet has joined #openstack-meeting12:42
*** tpsilva has joined #openstack-meeting12:44
*** shrasool has quit IRC12:47
*** ttsiouts has quit IRC12:49
*** ttsiouts has joined #openstack-meeting12:50
*** shrasool has joined #openstack-meeting12:52
*** psachin has quit IRC12:59
*** arne_wiebalck_ has joined #openstack-meeting13:01
*** rubasov has joined #openstack-meeting13:07
*** Liang__ has quit IRC13:13
*** Liang__ has joined #openstack-meeting13:14
*** liuyulong_ has joined #openstack-meeting13:20
*** ttsiouts has quit IRC13:24
*** ttsiouts has joined #openstack-meeting13:25
*** ttsiouts_ has joined #openstack-meeting13:29
*** ttsiouts has quit IRC13:30
*** shrasool has quit IRC13:31
*** psachin has joined #openstack-meeting13:38
*** priteau has quit IRC13:40
*** priteau has joined #openstack-meeting13:43
*** munimeha1 has joined #openstack-meeting13:45
*** jamesmcarthur has joined #openstack-meeting13:46
*** eharney has joined #openstack-meeting13:47
*** janki has quit IRC13:50
*** jamesmcarthur has quit IRC13:51
*** psachin has quit IRC13:51
*** arne_wiebalck_ has quit IRC13:53
*** mlavalle has joined #openstack-meeting13:55
*** lajoskatona has joined #openstack-meeting13:57
*** manjeets_ has joined #openstack-meeting13:58
*** boden has joined #openstack-meeting13:59
*** dkushwaha has left #openstack-meeting13:59
*** tidwellr has joined #openstack-meeting13:59
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Dec  4 14:00:06 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
liuyulong_hello everyone14:01
*** finix has joined #openstack-meeting14:01
*** finixlei has joined #openstack-meeting14:01
*** finixlei has quit IRC14:01
mlavalleAs usual, today's agenda can be found here: https://wiki.openstack.org/wiki/Network/Meetings14:01
mlavalle#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
*** hle2 has joined #openstack-meeting14:01
mlavalleOur weekly reminder that the next milestone is around the corner... In this case Stein-2 January 7th to 11th14:02
slaweqsorry for being late14:02
mlavalleYesterday I nominated two team members to become Neutron cores: njohnston and hongbin14:03
*** annp_ has joined #openstack-meeting14:03
mlavalle#link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000484.html14:03
mlavalle#link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000486.html14:03
mlavalleand finally I want to remind the team that the old mailing lists are now retired:14:05
mlavalle#link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000500.html14:05
mlavalleso if you want to communicate through the mailing list, use openstack-discuss@lists.openstack.org from now on14:07
mlavalleof course, you have to regsiter first14:07
mlavalleany other announcements for today?14:07
mlavalleok let's move on14:08
mlavalle#topic Blueprints14:08
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:08
mlavallemunimeha1: do you want to talk about port mirroring?14:09
munimeha1yes we have implemented this https://review.openstack.org/#/c/574477/14:09
*** a-pugachev has quit IRC14:09
munimeha1and we been testing now14:09
munimeha1and found one issue with sync on host boot14:09
munimeha1we fixed that as well14:09
munimeha1so its ready, we are only waiting for Manjeet to add thirdparty CI14:10
*** Liang__ has quit IRC14:10
mlavallemunimeha1: I'll go over the spec today.... and I encourage others to do the same14:10
munimeha1if the team can review the implementation also https://review.openstack.org/#/c/603501/14:10
mlavallemunimeha1: ahhh, I was about to ask for that. Yes I will go over it, most likely tomorrow or Thursday14:11
*** raildo_ has joined #openstack-meeting14:11
mlavalleThanks for the update and the contribution!14:11
njohnstonFor the bulk port work, had 2 of the 3 outstanding changes merge last week.  The last one needs quite a bit of cleanup and testing so it's not really ready for review yet, but progress is strong.14:12
hle2@mlavalle, not sure if have time to discuss https://review.openstack.org/#/c/605589/14:12
*** raildo_ has quit IRC14:13
*** raildo has joined #openstack-meeting14:13
tidwellrsubnet onboard is moving along, https://review.openstack.org/348080 is failing CI because it needs a neutron-lib release that contains https://review.openstack.org/620612. It's very close14:14
mlavallenjohnston, tidwellr: thanks for the updates14:14
mlavalleI'll keep an eye on those patches14:14
bcafareltidwellr: \o/14:15
mlavallehle2: you patch is a bug, rather than a blueprint. I added it to my review pile and I ask other team members to please take a look14:15
*** irclogbot_1 has quit IRC14:15
mlavallehle2: thanks for giving it visibility, though14:15
hle2mlavalle, thanks much!14:16
mlavalleI also want to mention that last week we merged this spec: https://specs.openstack.org/openstack/neutron-specs/specs/stein/network-segment-range-management.html14:16
mlavalleIt is one of the specs we originally discussed in Denver with the StarlingX team14:17
mlavallethey are going to post "bite size" patches with the code next week14:17
mlavalleso we will start tracking it in this section14:18
mlavallejust a heads up to the team14:18
mlavalleany other blueprints we should discuss today?14:18
*** trident has quit IRC14:18
mlavalleok, let's move on14:19
mlavalle#topic Community goals14:20
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:20
mlavalleamotoki: any updates on policy in code?14:20
mlavallemaybe he is not around....14:21
mlavalleslaweq, njohnston: do you have any updates for the team this week on your respective goals?14:21
*** trident has joined #openstack-meeting14:21
slaweqabout neutron-status upgrade check there is not too much14:22
slaweqI still need to change my patch https://review.openstack.org/#/c/615196/14:22
slaweqin the way like amotoki proposed last week14:22
njohnstonFor the python 3 goal, I just want to say that if someone is looking for a challenge please take a look at the failures in the python 3 version of the functional test job.  You can look at change https://review.openstack.org/#/c/577383/ for the activity... the failure seems to be in the functional test harness, with the failure reported as priginating in subunit.parser.14:23
njohnstonexample of the failure: http://logs.openstack.org/83/577383/14/check/neutron-functional/e0096d1/job-output.txt.gz#_2018-11-25_10_39_41_94995614:23
slaweqexcept that, I wanted to ask You if it would be good idea to maybe integrate to this neutron-status tool sanity_checks also?14:23
mlavallenjohnston: thanks. I may take a look14:24
mlavalleslaweq: mhhh, yeah it may make sense. Let me think about it14:24
*** larainema has joined #openstack-meeting14:25
mlavalleok, let's move on14:25
slaweqmlavalle: thx, that's not something to do now, but I can take it as next step later14:25
mlavalleslaweq: ack14:25
mlavalle#topic Bugs14:25
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:26
openstackRemoving item from minutes: #topic Bugs14:26
mlavalledue to time constraints, let's do neutron-lib before bugs14:26
mlavalle#topuc neutron-lib14:26
mlavalle#topic neutron-lib14:27
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:27
mlavalleboden: you are up14:27
bodenhi so quickly...14:27
bodenthere's a lib release patch out for review: https://review.openstack.org/#/c/621687/14:27
bodenbest I can tell everything looks good14:27
mlavallethanks, just added my +114:28
bodenthanks mlavalle14:28
bcafarelwill help with subnet onboard patch then :)14:28
bodenI wanted to ask to get some intiial feedback on the rehome of neutron.objects.base and friends14:28
bodenI have a WIP patch here https://review.openstack.org/#/c/621000/14:28
bodenif folks agree this is an OK approach I'll add the UTs and clean it up14:29
*** janki has joined #openstack-meeting14:29
bodenso please have a looksee if you get  a min14:29
njohnstonI'll definitely take a look, thanks14:29
mlavalleI will14:29
mlavalleadded to my pile14:29
bodenfinally I've noticed some folks starting to submit consumption patches for the db rehome work... thanks for this!! however I was hoping ppl could sync with me on the db stuff since I'm in the middle of it and hate to step on toes14:30
bodenthere's plenty of other neutron-lib work if folks are wanting to get their hands dirty :)14:30
bodenthat's it for me14:30
mlavallecool. thanks for the update14:31
njohnstonISTR from the PTG there was an idea to get a list of neutron-lib work for those who would like to help you carry the load... did I miss that?14:31
bcafarelyeah I was about to ask the same thing ^14:31
bcafarelespecially if people start helping14:31
bodenyeah there was an etherpad for that, but folks haven't mentioned wanting to help so I haven't pursued it much14:32
njohnstonI think we may have had a race condition, because I was waiting for the etherpad ;-)14:32
*** mriedem has joined #openstack-meeting14:33
slaweqnjohnston: it's more like a dead lock then :P14:33
bodenI can't seem to find the etherpad ATM... does anyone have a link handy?14:33
mlavalleI'll dig the notes from the PTG and will send a remionder to the ML asking for volunteers, how's that?14:34
bodenhere it is https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list14:34
mlavalleah great!14:34
bodenI will add a section with some work topics in the next day or 214:34
bodento that etherpad14:34
njohnstonthanks boden!14:34
mlavalleI think so14:34
bodenI'll send a note to the ML once I get it update14:35
bodenthe "new" ML14:35
bodennothing else from me14:35
mlavalleThanks for the update14:36
mlavalle#topic Bugs14:36
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:36
mlavalleYour truly was the bug deputy last week:14:37
mlavalle#link  http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000509.htm14:37
mlavalleIt was a relatively quite week14:37
bcafarelmissing a "l"?14:37
mlavalle#link http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000509.html14:38
mlavallethanks bcafarel.... as usual with you... good catch!14:38
njohnstonalso thanks for updating the bug deputy schedule mlavalle14:38
mlavalleI have a bug that needs further investigation: https://bugs.launchpad.net/neutron/+bug/180513214:39
openstackLaunchpad bug 1805132 in neutron "bulk creation of security group rules fails StaleDataError" [Undecided,New]14:39
mlavalleand two that I marked incomplete but the submitters may return with more info:14:40
openstackLaunchpad bug 1805769 in neutron "maximum RPC response timeout is not reasonable" [Undecided,Incomplete] - Assigned to nicky (ss104301)14:40
mlavalle https://bugs.launchpad.net/neutron/+bug/180535614:40
openstackLaunchpad bug 1805356 in neutron "Convert instance method to staticmethod in linux bridge agent" [Low,Incomplete] - Assigned to Yang Youseok (ileixe)14:40
mlavalleas njohnston already pointed out, I rolled over the bugs deputy duty calendar14:41
bcafarelwhich means I'm next then :)14:41
rubasovmlavalle: ack for followup14:41
mlavallePlease take note of your new duty week:14:41
mlavalleand no, rubasov, this doesn't mean your duty of this week has been postponed to mid-March14:42
mlavalle.... just kidding rubasov14:42
rubasovmlavalle: ;-)14:42
mlavalleslaweq: would you ping pasuder and confirm he is ok with being on duty the week of December 17th?14:43
*** awaugama has joined #openstack-meeting14:43
slaweqmlavalle: yes, I will14:43
*** ttsiouts_ has quit IRC14:44
*** janki has quit IRC14:44
mlavalle#topic os-ken14:44
*** openstack changes topic to "os-ken (Meeting topic: networking)"14:44
*** ttsiouts has joined #openstack-meeting14:44
mlavallemhhh I don't see hongbin around today14:44
mlavalledoes any one have a comment on this topic?14:45
lajoskatonamlavalle: how shall I be on the deputy list?14:45
mlavallelajoskatona: yes, we can add you to the list14:45
lajoskatonamlavalle: thanks14:45
mlavallenew volunteers are always welcome14:45
mlavallethanks for volunteering :-)14:46
*** ttsiouts_ has joined #openstack-meeting14:46
mlavalleok, let's move on14:46
mlavalle#topic On demand agenda14:46
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:46
mlavalleAnything else we should disucss today?14:46
*** hongbin has joined #openstack-meeting14:47
mlavalleok team, thanks for attending. Have a great week14:47
mlavallelet's return ~10 minutes to our agendas today14:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:48
openstackMeeting ended Tue Dec  4 14:48:06 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-12-04-14.00.html14:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-12-04-14.00.txt14:48
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2018/networking.2018-12-04-14.00.log.html14:48
*** hle2 has quit IRC14:48
*** ttsiouts has quit IRC14:49
*** ttsiouts_ has quit IRC14:50
*** irclogbot_1 has joined #openstack-meeting14:55
*** boden has left #openstack-meeting14:55
*** eharney has quit IRC14:56
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Dec  4 15:00:02 2018 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
ralonsohlet's wait 30 secs more15:01
ralonsohok, let's go15:01
ralonsoh#topic RFEs15:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/172757815:01
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Triaged]15:01
ralonsohwe have the spec merged, but no progress on the code15:02
ralonsoh#link https://review.openstack.org/#/c/558986/15:02
ralonsohis ZhaoBo here?15:03
ralonsohhas this RFE high priority?15:03
ralonsohno, whislist15:03
mlavalleit has priority after the work he is doing in Octavia15:04
*** jawad_axd has quit IRC15:04
ralonsohok, so we'll wait for it15:04
ralonsohnext one15:04
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/175704415:04
openstackLaunchpad bug 1757044 in neutron "[RFE] neutron L3 router gateway IP QoS" [Wishlist,Fix released] - Assigned to LIU Yulong (dragon889)15:04
mlavalleI'll ping him over WeChat anyway tonight15:04
ralonsohmlavalle, thanks15:04
ralonsohFix released! Thanks liuyulong_15:05
slaweqthis one is almost done by liuyulong_15:05
ralonsohit's released, all patches are merges15:05
slaweqthere is only some docs patch waiting and osc patch15:05
mlavalleyeah, last night I W+ server and agent patches15:05
*** jawad_axd has joined #openstack-meeting15:05
mlavallethere is a docs patch in review15:05
mlavallehang on15:05
ralonsohok, so only the docs, do you have the link?15:05
*** liuyulong has quit IRC15:06
mlavalleand the server and agent patches merged last night15:06
ralonsohI'll add it to the etherpad15:06
ralonsohgood job!15:06
ralonsohnext one15:06
slaweqthere is also this OSC patch https://review.openstack.org/#/c/62213015:07
slaweqjust FYI15:07
ralonsohI'll put this in the etherpad now15:07
liuyulong_Maybe ZhaoBo still has no time on this.15:07
mlavalleliuyulong_: I'll WeChat him and ask ;-)15:08
ralonsohliuyulong_, yes, mlavalle said that he's working in Octavia right now15:08
ralonsohok, next one15:08
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/177762715:08
openstackLaunchpad bug 1777627 in neutron "RFE: QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel)15:08
ralonsohFix released!15:08
ralonsohany other patch? docs? something?15:08
mlavalleso I implemented the Neutron side....15:09
mlavalleand discovered that the api def in neutron-lib have some errors15:09
mlavalleso I fixed the neutron-lib side15:09
*** jawad_axd has quit IRC15:10
mlavalleand with the neutron-lib release that will take place any moment now, I will fix the neutron patch15:10
ralonsohI'm trying to find the patch15:10
*** jawad_axd has joined #openstack-meeting15:10
ralonsohyes, this one. But the n-lib patches are merged15:10
ralonsohperfect, I'll add this one to the etherpad15:11
ralonsohis this the last patch?15:11
mlavalleand half of the comments in the neutron patch had to do with duplicating the api def15:11
mlavalleyes, this will be the last patch15:11
mlavallethe api-def is also merged and correct15:11
ralonsohyes, I see slaweq's comments in https://review.openstack.org/#/c/613820/15:12
ralonsohI'll review it today15:12
ralonsohnext one15:12
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:12
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Lajos Katona (lajos-katona)15:12
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:minimum-bandwidth-allocation-placement-api15:12
lajoskatonayes, it is progressing15:13
*** manjeets_ has quit IRC15:13
ralonsohany comment you want to share? problems?15:13
lajoskatonalast week rubasov mostly worked on neutron-lib15:13
ralonsohand the nova side?15:14
*** jamesmcarthur has joined #openstack-meeting15:14
lajoskatonayes, I uploaded a wip patch for tempest to add placement client to tempest, I suppose there will be some discussion so if you have time to keep an eye on it15:14
*** annp_ has quit IRC15:14
lajoskatonafor nova: as I know from gibi it is progressing15:14
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/bandwidth-resource-provider15:14
gibitwo sets of patches are in the nova runway queue https://etherpad.openstack.org/p/nova-runways-stein15:15
rubasovwe'll also do a progress check before the next meeting to see where we'll be at milestone-215:15
lajoskatonathanks gibi15:15
*** jawad_axd has quit IRC15:15
lajoskatonafor the tempest client the patch: https://review.openstack.org/62231615:16
mlavallerubasov, gibi, lajoskatona: thanks!15:16
*** mriedem is now known as mriedem_afk15:16
lajoskatonaI plan to upload a wip scenario test as well as soon as possible15:16
slaweqlajoskatona: nice topic in this tempest patch "dontdelete/bwm_scenario" :)15:16
slaweqlajoskatona: You could name it "bmw_scenario" :D15:17
lajoskatonaslaweq: thanks, it was again git review's default topic as I see....15:17
ralonsohto recap, we have the nova, neutron and tempest patches15:18
lajoskatonaralonsoh: yes15:18
ralonsohI'll add the tempest one to etherpad now15:18
mlavallelajoskatona: just something to consider.... if we don't make progress in the tempest repo, we might consider housing the placement client in neutron-tempest-plugin15:18
lajoskatonabye the way: where is the etherpad?15:19
lajoskatonamlavalle: ok,15:19
lajoskatonamlavalle: let's see what the QA and nova/placement folks think about and mova accordingly15:19
mlavalleyeah, let's follow that path first15:20
ralonsohlajoskatona, I'll create the section for the new meeting every day in the morning (UTC time)15:20
ralonsohlajoskatona, you can add any comment to it15:20
lajoskatonaralonsoh: thanks15:20
ralonsoh every day/every other week15:20
ralonsohI'll spend time tomorrow reviewing the list of patches15:21
ralonsohany other comment on this (big) one?15:21
rubasovnot from me15:22
lajoskatonanothing I think15:22
ralonsohok thanks, let's move to the next one15:22
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:23
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:23
ralonsohOne patch resurrected15:23
ralonsoh#link https://review.openstack.org/#/c/406841/15:23
ralonsohn-lib patch is merged15:23
ralonsohI added functional tests for the ovs-lib part, IMO needed15:23
ralonsohThis is ONLY the physical bridges implementation15:24
ralonsohthere will be a next one for tunnel traffic15:24
ralonsohand the feature should be completed15:24
mlavalleahh cool15:24
ralonsohnothing else from my side15:25
mlavallegood progress, though15:25
ralonsohwe still have the same not approved RFE's15:25
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178779215:25
openstackLaunchpad bug 1787792 in neutron "[RFE] Does not support ipv6 N-S qos" [Wishlist,New]15:25
mlavalleyes I intend to work on this15:26
*** Luzi has quit IRC15:26
mlavallethe Holidays in the US werent't very helpful though15:26
ralonsohI commented last week15:26
mlavallecool, I'll take a look15:26
ralonsohIMO, for IPv6 we already have the L2 QoS15:26
mlavallewell, that may be good news15:27
ralonsohof course is not as granular as a specific IPv6 QoS, but could be enough15:27
ralonsohbut of course, new toughs could be added to the bug15:28
ralonsohand the last one15:28
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178779315:28
openstackLaunchpad bug 1787793 in neutron "[RFE] Does not support shared N-S qos per-tenant" [Wishlist,New]15:28
ralonsohsorry, I didn't have time to comment, mlavalle15:29
ralonsohyou asked me to do it15:29
mlavallelet's try again15:29
ralonsohfor sure!15:29
ralonsohthis is what I have in my list15:29
ralonsohany other one I'm missing?15:30
mlavallenope, very comprenhensive15:30
ralonsohperfect, let's move to bugs15:30
ralonsoh(although there are no bug in QoS)15:30
ralonsoh#topic Bugs15:30
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:30
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178400615:31
openstackLaunchpad bug 1784006 in neutron "Instances miss neutron QoS on their ports after unrescue and soft reboot" [Medium,Confirmed] - Assigned to Miguel Lavalle (minsel)15:31
ralonsohmlavalle, I think you didn't have time for this one15:31
mlavalleThis is my next item after I finish the the qos alias stuff15:31
ralonsohno problem15:32
ralonsohnext one15:32
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178518915:32
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Undecided,In progress] - Assigned to Brian Haley (brian-haley)15:32
ralonsoh#link https://review.openstack.org/#/c/596637/15:32
ralonsohstill no reply...15:33
ralonsohThis is what I have in my list15:33
* mlavalle pinging haleyb on it now15:33
ralonsohis there any other bug?15:33
mlavalleI just pinged Brian in the Neutron channe,15:34
ralonsohlet's see if he can join now15:35
ralonsohmeanwhile, I'll start the open discussion15:35
ralonsoh#topic Open Discussion15:35
mlavalleralonsoh: I didn't ask him to join the meeting15:35
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:35
ralonsohmlavalle, ok, ok15:35
ralonsohI think I speed up a lot the meetings... I'll try to slow down next time15:36
ralonsohDo you have any topic you want to discuss?15:36
mlavallenot from me15:37
liuyulong_https://review.openstack.org/#/c/622130/, openstackclient for route gateway IP QoS15:37
mlavalleliuyulong_: slaweq mentioned it already in the meeting15:38
liuyulong_If this merged first, I think I will update the [Doc] patch.15:38
*** finix has quit IRC15:38
ralonsohsure, I'll add it to the etherpad and on my review list15:38
ralonsohsure, we can have CLI examples in the docs15:39
ralonsohOK, thank you all for attending and participating!15:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:40
openstackMeeting ended Tue Dec  4 15:40:25 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-12-04-15.00.html15:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-12-04-15.00.txt15:40
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2018/neutron_qos.2018-12-04-15.00.log.html15:40
*** liuyulong_ has quit IRC15:41
*** lajoskatona has quit IRC15:44
*** rubasov has left #openstack-meeting15:45
*** shrasool has joined #openstack-meeting15:50
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Dec  4 16:00:43 2018 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
slaweqlets wait few minutes for others16:01
*** shrasool has quit IRC16:02
slaweqI pinged them in neutron channel16:03
haleybslaweq found us :)16:03
slaweqok, lets start then16:04
njohnstonmy coffeemaker was slow :-/16:04
slaweq#topic Actions from previous meetings16:04
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:04
slaweqmlavalle to continue tracking not reachable FIP in trunk tests16:04
mlavalleI did after we merged your patch16:05
mlavallethe error is still taking place16:05
slaweqyes, but I think that it's less often now, right?16:05
mlavalleit may be slightly lower16:05
mlavallewhen did you fix exactly merge in master?16:06
*** hongbin has quit IRC16:06
slaweq3.12 I think16:07
mlavallein master it seems it merged 11/2716:08
slaweqahh, right16:08
slaweqthis one was for pike16:08
mlavalleand yes, there seem to be lower number of hist since then16:08
mlavalleso the next step is to change the scenario test16:08
slaweqyes, will You do it?16:09
mlavalleto create the fip when the port is already bound16:09
mlavalleand yes, I will do that today16:09
slaweq#action mlavalle to change trunk scenario test and see if that will help with FIP issues16:09
slaweqok, next one then16:10
slaweqhaleyb takes all this week :D16:10
slaweqhaleyb: did You fixed all our bugs?16:10
haleybyeah, you didn't see the changes? :p16:10
slaweqok, thx haleyb++16:10
slaweqwe can go to the next one then16:10
slaweqnjohnston to remove neutron-grenade job from neutron's CI queues16:10
njohnstonSo I have a change up to do that, but there are pre-requisites16:11
njohnstonI can remove the job from our queues but leave the job definition there16:11
njohnstonbecause it is used elsewhere16:11
njohnstonI have a change up already for the grenade repo, which uses neutron-grenade16:12
njohnstonbut it looks like nova, cinder, glance, keystone all use neutron-grenade16:12
njohnstonso I'll need to spin changes for all of those before we can delete the job definition16:12
*** pcaruana has quit IRC16:12
slaweqbut in our gate we have already neutron-grenade-py3, right?16:12
njohnstonoh, and tempest, openstacksdk, and the requirements repo16:13
*** hongbin has joined #openstack-meeting16:13
njohnstonwe have grenade-py3 yes, provided by the grenade repo16:13
slaweqso maybe we can remove this neutron-grenade job from our check and gate queues to not overload gates16:14
slaweqand add some comments that definition of this job is used by other projects so can't be removed now16:14
slaweqmlavalle: what do You think?16:14
njohnstonyes, I think I'll do that to start with, and I'll gradually work towards the other projects replacing neutron-grenade with grenade-py316:14
mlavallesounds good16:15
slaweqgreat, so go on with it njohnston :)16:15
slaweq#action njohnston will remove neutron-grenade from neutron ci queues and add comment why definition of job is still needed16:15
njohnstonwill do16:16
slaweqso, next one16:16
slaweqslaweq to continue debugging bug 1798475 when journal log will be available in fullstack tests16:16
openstackbug 1798475 in neutron "Fullstack test test_ha_router_restart_agents_no_packet_lost failing" [High,Confirmed] https://launchpad.net/bugs/179847516:16
slaweqI found this failure on patch where journal log is already storred16:16
slaweqbut I still have no idea why keepalived switched VIP address from one "host" to the other16:17
slaweqI will keep investigating that16:17
slaweq#action slaweq to continue debugging bug 179847516:17
openstackbug 1798475 in neutron "Fullstack test test_ha_router_restart_agents_no_packet_lost failing" [High,Confirmed] https://launchpad.net/bugs/179847516:17
slaweqif I will need help I will ping haleyb :)16:18
slaweqnext one16:18
slaweqslaweq to continue fixing funtional-py3 tests16:18
slaweqno progress on this one still16:18
njohnstonI hope you didn't mind that I raised the flag on this one in the neutron team meeting16:18
slaweqwe know that we need to limit output from functional tests, remove all deprecations and things like that and check then what will be the result16:18
slaweqnjohnston: no, great that You did it16:19
slaweqwe definitely needs more eyes looking at it16:19
*** shrasool has joined #openstack-meeting16:19
slaweqif there is anyone else who wants to try to fix it this week, feel free16:20
slaweqI will assign it to myself as an action just to not forget about it16:20
mlavalleso based on how much progress I make on other assignments, I may take a look at this one16:20
slaweq#action slaweq to continue fixing funtional-py3 tests16:20
slaweqmlavalle: thx, ping me if You will need any info16:21
slaweqok, next one16:21
slaweqnjohnston to research py3 conversion for neutron grenade multinode jobs16:21
njohnstonno progress on that one yet16:21
slaweqok, lets move it to the next week then, right?16:22
*** armax has joined #openstack-meeting16:22
njohnstonsounds good16:22
slaweq#action njohnston to research py3 conversion for neutron grenade multinode jobs16:22
slaweqslaweq to convert neutron-tempest-plugin jobs to py316:22
slaweqPatch https://review.openstack.org/#/c/621401/16:22
slaweqI rechecked it few times and it looks that it works fine16:22
slaweqall neutron-tempest-plugin jobs for master branch are switched to py3 in this patch16:22
slaweqand jobs for stable branches are still on py27 of course16:23
slaweqplease review it if You will have some time16:23
mlavalleslaweq: I will look at it today16:24
slaweqthx mlavalle16:24
*** eharney has joined #openstack-meeting16:24
slaweqok, so lets move on16:24
slaweqnjohnston add tempest-slow and networking-ovn-tempest-dsvm-ovs-release to grafana16:24
njohnstonhmm, I added that config but it looks like I never did a 'git review'.  I'll do that right away, sorry I missed it.16:25
slaweqno problem, thx njohnston for working on this :)16:25
slaweqplease add me as reviewer to it when You will push it16:25
njohnstonwill do16:26
slaweqok, lets move on to the last one16:26
slaweqmlavalle to discuss about neutron-tempest-dvr job in L3 meeting16:26
mlavallemhhh, I couldn't attend the meeting16:26
mlavalleI'll discuss with haleyb in the Neutron channel16:27
slaweqok, so will You talk about it this week?16:27
*** electrofelix has quit IRC16:27
slaweqahh, thx16:27
slaweqso I will not add action for it anymore16:27
mlavalleplease do16:27
slaweqany questions/something to add?16:27
mlavalleso I can report concusion next week16:27
slaweqok, lets move on then16:29
slaweq#topic Python 316:29
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:29
slaweqnjohnston: any updates?16:29
*** tetsuro has joined #openstack-meeting16:29
slaweqI think we should update our etherpad, to mark what is already done16:30
slaweqI will do that this week16:30
njohnstonI don't think there are any updates this week16:30
njohnstonfrom my end16:30
slaweq#action slaweq to update etherpad with what is already converted to py316:31
slaweqok, from my side there is also nothing more to talk today16:31
slaweqso lets move on, next topic16:31
slaweq#topic Grafana16:31
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:31
slaweqgood news is that tempest jobs, and scenario jobs looks much better this week16:34
slaweqeven those multinode dvr jobs16:34
*** larainema has quit IRC16:34
mlavallewhat happened last week?16:35
mlavalleseems we had a spike around Thursday in gate16:35
slaweqhmm, I don't know16:37
hongbinpossibly there are some infra related issues16:37
mlavallewell, let's keep it in mind16:38
*** tetsuro has quit IRC16:38
slaweqone day last week I saw some failures because of missing dependencies or something like that16:38
slaweqbut I don't remember what it was exactly and in which day16:38
njohnstonHey, just a quick sanity check: we have the tempest-slow job in the check queue as voting but not in gate.  Is that the intended configuration?16:39
*** tetsuro has joined #openstack-meeting16:39
njohnstonAs in it is not present in the gate queue in any form16:40
hongbinin theory, if a job is voting in check, it should be in the gate as well16:40
slaweqyes, we should add it to gate queue as well16:41
njohnstonyes, that is my impression, I just wanted to see if there is some reason for this to be an exception that I don't know about16:41
slaweqbut maybe lets add it to grafana first16:41
njohnstonit turns out, it already is in grafana, at least for the check queue16:41
slaweqthen check how it works for one/two weeks and we will then decide16:41
slaweqindeed, I missed it16:42
njohnstonSo I will submit a change to add it to gate, and we can slow-walk that change until we are comfortable on it16:42
*** bdperkin has joined #openstack-meeting16:42
mlavallesounds like a plan16:43
slaweqok, one more thing I want to mention16:44
slaweqnot related stricly to grafana but related to job failures16:44
slaweqtogether with hongbin we decided to collect examples of failures which we spot in CI in etherpad:16:44
slaweqthere is already quite many examples of issues from this week16:45
slaweqsome of them are not related to neutron but we wanted to have info how many times such issue happens for us16:45
slaweqsome are related to neutron for sure16:45
slaweqmost common issue related to neutron are problems with connectivity to FIP16:46
slaweqI don't know if that is the same issue every time but visible culprit is the same - no connection to FIP16:46
slaweqit is in many different jobs16:46
mlavalleI don't think it is always the same root cause16:47
*** gyee has joined #openstack-meeting16:47
slaweqyes, probably not, but we should take a look at them, collect such examples for few weeks and report bugs if it hits more often in same job/test16:47
slaweqfrom other things, I wanted to mention that there is (again) some issue with ovsdbapp timeouts16:48
*** iyamahat has joined #openstack-meeting16:48
*** munimeha1 has quit IRC16:48
slaweqit hits us in many different jobs16:48
slaweqand otherwiseguy was checking it already16:49
hongbinthere is a patch to turn on the python-ovs debugging to do further troubleshooting for that16:49
hongbin#link https://review.openstack.org/#/c/621572/16:50
slaweqand bug reported already: https://bugs.launchpad.net/bugs/180264016:50
openstackLaunchpad bug 1802640 in neutron "TimeoutException: Commands [<ovsdbapp.schema.open_vswitch.commands.SetFailModeCommand in q-agt gate failure" [Medium,Confirmed]16:50
*** mriedem_afk is now known as mriedem16:50
slaweqok, lets talk about some specific jobs now16:51
slaweq#topic fullstack/functional16:51
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:51
slaweqaccording to fullstack tests we have new issue I think16:51
slaweqI saw at least 3 times that test: neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_gateway_ip_changed failed:16:52
slaweqis there anyone who wants to take a look on it?16:52
hongbini can try to look at it16:52
mlavalleis it always the IP address already alocated exception?16:53
slaweqthx hongbin16:53
slaweqpatch which introduced this test is https://review.openstack.org/#/c/606876/16:54
slaweqmlavalle: I don't know, I didn't have time to investigate it16:54
slaweqyes, it looks that it is the same culprit every time16:55
slaweqit should be easy to fix I hope :)16:55
slaweq#action hongbin to report and check failing neutron.tests.fullstack.test_l3_agent.TestHAL3Agent.test_gateway_ip_changed test16:55
slaweqI want also to highligh again failing functional db migrations tests16:56
slaweqI found it at least 5 or 6 times failing this week16:56
slaweqthere are already logs from those tests stored properly16:56
slaweqbut there is not too much info there16:56
slaweqfor example: http://logs.openstack.org/49/613549/6/gate/neutron-functional/315ddc4/logs/testr_results.html.gz16:57
slaweqit looks that migrations are working but very slow16:57
slaweqI think we should compare such failed tests with passed once and check if there are always the same migrations slowest ones or maybe it's random16:58
slaweqbut I don't know if I will have time for it this week16:58
*** cloudrancher has quit IRC16:59
slaweqok, and that's all what I wanted to highligh from issues in CI16:59
slaweqthx for attending and see You next week16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:59
openstackMeeting ended Tue Dec  4 16:59:58 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-12-04-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-12-04-16.00.txt17:00
*** cloudrancher has joined #openstack-meeting17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2018/neutron_ci.2018-12-04-16.00.log.html17:00
*** mlavalle has quit IRC17:01
*** shrasool has quit IRC17:02
*** shrasool has joined #openstack-meeting17:03
*** takamatsu has quit IRC17:06
*** pcaruana has joined #openstack-meeting17:12
*** e0ne has quit IRC17:13
*** shrasool has quit IRC17:17
*** sridharg has quit IRC17:22
*** munimeha1 has joined #openstack-meeting17:24
*** kopecmartin is now known as kopecmartin|off17:26
*** shrasool has joined #openstack-meeting17:32
*** cloudrancher has quit IRC17:32
*** cloudrancher has joined #openstack-meeting17:33
*** francois has quit IRC17:34
*** bobh has joined #openstack-meeting17:36
*** bobh_ has joined #openstack-meeting17:37
*** bobh_ has quit IRC17:38
*** bobh_ has joined #openstack-meeting17:39
*** bobh has quit IRC17:41
*** bobh_ has quit IRC17:43
*** bobh has joined #openstack-meeting17:45
*** cloudrancher has quit IRC17:49
*** cloudrancher has joined #openstack-meeting17:49
*** iyamahat has quit IRC17:49
*** pcaruana has quit IRC17:56
*** cloudrancher has quit IRC17:59
*** tobiash has joined #openstack-meeting18:00
*** cloudrancher has joined #openstack-meeting18:00
*** iyamahat has joined #openstack-meeting18:03
*** iyamahat_ has joined #openstack-meeting18:06
*** iyamahat has quit IRC18:09
*** mjturek has joined #openstack-meeting18:11
*** e0ne has joined #openstack-meeting18:13
*** mjturek has quit IRC18:18
*** yamahata has joined #openstack-meeting18:20
*** shrasool has quit IRC18:26
*** shrasool has joined #openstack-meeting18:27
*** e0ne has quit IRC18:30
*** mjturek has joined #openstack-meeting18:46
*** Shrews has joined #openstack-meeting18:51
clarkbAnyone here for the infra meeting? we'll get started in a minute or wo19:00
*** diablo_rojo has joined #openstack-meeting19:01
*** diablo_rojo has quit IRC19:01
fungii vote for wo19:01
Shrewsmuch wo19:01
gary_perkinso/ Hi!19:01
clarkbsilly t key19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Dec  4 19:01:55 2018 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
*** diablo_rojo has joined #openstack-meeting19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:02
clarkb#topic Announcements19:02
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:02
clarkbYesterday fungi merged the openstack mailing lists (tc, ops, dev, general, sigs) into the new openstack-discuss list19:03
clarkbif you have not yet joined that list now is a good time to do so19:03
fungiwe're up to 515 subscribers now!19:03
clarkbAlso k8s just had its first major CVE so if you are running a k8s you should upgrade (I upgraded nodepool's small cluster yesterday)19:03
corvusthat's pretty close to our expected level based on active posters, yeah?19:03
*** e0ne has joined #openstack-meeting19:03
fungimy stats suggest we had 933 unique posters to any of the original lists in the first 2/3 of 201819:04
corvusoh i thought it was 600.  i guess i misremembered19:04
fungifactor in address changes and people who only joined to ask a question and it's likely a lot lower19:04
corvusfungi: did you send a final email to all the old lists?19:04
corvusyes, i see it now :)19:05
fungiyep, to each one before closing them19:05
clarkbdidn'y you have an active (eg more than 2 emails sent) list that was closer to 500?19:05
clarkbstill problems with that 't' key19:05
* mordred waves from aeroplane19:05
fungiyeah, i had graduated counts. i can always do some fresh ones19:05
dmsimardaeroplane internet!19:05
clarkbNote that the infra list is still there as its own thing19:05
clarkb#topic Actions from last meeting19:05
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:05
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-11-27-19.01.txt minutes from last meeting19:06
clarkbfungi did the thing with the mailing lists. Thank you19:06
clarkbianw I think you did end up cleaning up pypi volume in afs. What about the fedora 27 volume?19:06
ianwclarkb: pypi volume is all cleared out and gone.  f27 was just some directory components, but that's gone too19:07
ianwafs servers have plenty of space now, so that's good19:07
*** pabelanger has joined #openstack-meeting19:07
clarkbhttp://grafana.openstack.org/d/ACtl1JSmz/afs?orgId=1 graphs look much happier19:07
clarkbianw: thank you for cleaning that stuff up19:07
ianwnp, there's nothing like running out of space for the thing you're interested in to prompt action ;)19:08
clarkb#topic Specs Approval19:08
*** openstack changes topic to "Specs Approval (Meeting topic: infra)"19:08
clarkb#link https://review.openstack.org/#/c/607377/ Storyboard Attachments spec19:08
clarkbI'll advertise this one again, but it looks like sphinx may be failing on it?19:08
clarkbdiablo_rojo: ^ fyi probably want to clean that up so it shows up in people's review queues19:09
*** erlon has quit IRC19:09
diablo_rojoYeah I will have that fixed today19:09
clarkb#link https://review.openstack.org/#/c/581214/ Anomoly detection in CI logs19:09
clarkbthis is the other one I'll "advertise" I intend on reviewing that one myself shortly.19:09
clarkbI was in tristanC and dirks summit presentation and its neat stuff19:10
clarkb#link https://review.openstack.org/622439 Zuul governance proposal19:10
clarkbprobably worth noting that change here as well.19:11
clarkbThese changes all deserve (y)our feedback :)19:11
clarkb#topic Priority Efforts19:11
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:11
clarkb#topic Storyboard19:11
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:11
clarkbdiablo_rojo: fungi SotK seems like last week was the summit feedback digestion week.19:12
clarkbanything to add here?19:12
*** tssurya has quit IRC19:12
fungiSotK has posted rather a few excellent looking improvements based on feedback we got at the ptg and summit19:12
diablo_rojoYeah, definitely have patches to review19:12
diablo_rojoWhat needs to be done to actually move the trove db?19:13
* diablo_rojo has brought this up twice but keeps forgetting to actually get action items out of the conversation19:13
clarkbdiablo_rojo: create the new db server somewhere, schedule a storyboard outage window, stop storyboard, migrate data to new db, start storyboard pointed at new db19:14
fungii think we need to add the mysql module to the manifest for the server first so that we get a local db created19:14
ssbarnea|roverregarding attachments, why not using logs.openstack.org for storing attachments? attachment retention policy could be decided later, but it would be a system that is already serving files.19:14
clarkbfungi: ya that would be step zero if doing local db19:14
fungithen a manual step to shut down the service and dump/source the db content19:14
diablo_rojoclarkb, this sounds like a thing I need an infra core friend for.19:14
corvusclarkb, diablo_rojo: i'd add to that that you can do test migrations beforehand without an outage to verify that it works and establish timing (so you know what the outage window will be)19:14
clarkbssbarnea|rover: I think the big concern with that is we'd like to not start with "legacy" file storage and just move ahead with scalable storage instead19:15
clarkbcorvus: ++19:15
clarkbdiablo_rojo: yup you'll need an infra root in particular for the outage window tasks19:15
diablo_rojocorvus, good idea19:16
fungissbarnea|rover: i recommend reading through the spec if you haven't already. the requirements/expectations are already laid out there19:16
corvuslogs.o.o is on its way out (slowly)19:16
diablo_rojoI can add why we aren't planning on using logs.o.o into the spec too19:16
fungiwell, the current implementation of logs.o.o is on its way out anyway. we may still have something *named* logs.o.o with all new backend implementation?19:17
* mordred can't wait for logs.o.o to go away19:17
ssbarnea|roverclarkb: i do not find those two conflicting. i read it, is ok. still i have a more practical view: some attachment support today is much more useful than a very well designed (and scalable) solution that is delivered in 2020 or later ;)19:17
clarkbdiablo_rojo: fungi: I think as far as actionable next steps go getting the new db set up via puppet ansible is step 0 then step 0.5 is write up a etherpad document for the process you'll need infra-root for and we can schedule a time for that and get volunteers?19:17
clarkbdiablo_rojo: fungi: similar to how we do gerrit project renames and other outages with a documented process19:17
diablo_rojoclarkb, happy to take point, but I might need a little help getting the ball rolling19:18
clarkbdiablo_rojo: I can help fill in the details of the process too19:18
fungissbarnea|rover: the main point is that we provide automatic indices on logs.o.o. we would need to _not_ do that to satisfy the need for attachments on private stories, which is one of the primary reasons we want attachments for sb at all19:18
ianw++ some of the zanata work we had great checklists for, it was very easy19:18
diablo_rojoclarkb, sweet19:18
clarkbanything else storyboard before we move on to config management modernization?19:19
fungissbarnea|rover: so an attachments "solution" which doesn't meet our need for private story attachments isn't really any solution at all19:20
clarkbssbarnea|rover: fungi diablo_rojo I do think we can take that to the spec review (and maybe add a section for that so its clear)19:20
ssbarnea|roverfungi: yep, but indexes can be diabled on "/sb/" folder. anyway.19:20
diablo_rojoI got nothing else clarkb :)19:21
fungissbarnea|rover: sure, there's lots of things we *can* change to make something which isn't a solution into something which is19:21
clarkb#topic Update Config Management19:21
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:21
clarkbLast week we ran into a couple of issues with dynamic ansible inventories19:21
clarkbwe fixed one, which ran puppet/ansible once which installed new things which broke it in different ways19:21
clarkbor rather one was fixed (we didn't fix it)19:21
clarkbThe end result was a switch to using static inventory19:22
clarkbthat seems to be working well so far though I don't think anyone has created new servers since19:22
corvusoh, yeah, we need a script for that19:22
clarkbmordred: ^ were you planning on adding a script to generate the static inventory dynamically? I seem to recall that was on your list of todos?19:22
corvusthat's how i remember it too :)19:23
ssbarnea|rover.... or we could get a free jira instance running and use it, with all features already implemented. it would not be OSI kind of opensource but... also it would allow us to focus on making openstack better.19:23
mordredclarkb: yes19:23
clarkbmordred: awesome19:23
mordredclarkb: I should probably write that :)19:23
clarkb#action mordred Add script to generate static inventory dynamically19:23
ianwso /etc/ansible/hosts/openstack.yaml on bridge is now not used, right?19:24
ianwcan i move that to make it clear?19:24
clarkbianw: it is used but it is no longer dynamically generated it should be static content19:24
clarkbor did we rename the file too? /me checks19:24
ianwit's not, i assumed we're taking it out of system-config19:24
clarkboh sorry it is the fiel in system-config/inventory that is used not /etc/ansible/hosts19:24
corvushuh, was that ever used?19:25
ianwi got a little confused on it last night, because the emergency file was broken and had stopped puppet19:25
clarkbianw: I believe that file is safe to remove19:25
corvusbecause we changed a file that looked just like that in system-config19:25
ianwok, i've moved it so it's clear, i'll note in infra19:25
clarkbinventory=/opt/system-config/inventory/openstack.yaml,/opt/system-config/inventory/groups.yaml,/etc/ansible/hosts/emergency.yaml <- doesn't include that file19:25
clarkbfrom ansible.cfg19:25
mordredyah - the file originally was a pointer for ansible, so it would read it, see it was a plugin description file, then run the dymanic inventory19:26
mordredit is now not needed because we point directly to the file in system-config19:26
corvus(yes, and i think that was true even before the change to static inventory)19:26
clarkbcorvus: I think that is correct19:27
mordredah - yes, you're probably right about that19:27
ianw++ i like it when reality matches with what i think is going on :)19:27
mordredianw: me too19:27
clarkbianw: mordred: for the docker base changes any news there? Do we need to review things?19:27
*** jawad_axd has joined #openstack-meeting19:27
ianwnot quite yet19:28
fungiianw: oh, i must have broken the emergency disable list when i removed the entry for static.o.o... i guess the disabled list can't be empty?19:28
mordredI'm so behind on that - I need to catch up with ianw on what he's been doing19:28
fungiianw: sorry about that!19:28
clarkbfungi: or maybe needed [] ? ( I don't know what the list looked like)19:29
corvusshould probably put a comment in there when we figure it out :)19:29
clarkbcorvus: ++19:29
ianwfungi: np, i just got all confused because puppet seemed broken, then it seemed like the static inventory hadn't rolled out, but eventually i saw what was going on :)19:29
clarkbAnything else on this effort? I think the emergency inventory changes sort of took precedence last week so not surprising we moved slowly otherwise19:30
dmsimardianw's topic is /sort of/ related to cfg mgmt19:30
fungiclarkb: yeah, [] would likely have solved it19:30
clarkbdmsimard: ya but ianw put them under general topics so I figured we'd discuss them there :)19:30
ianwfungi: happy to try that, i've just commented out the dict keys atm so that you don't have to figure out what to put in19:31
clarkbok lets move on then.19:31
clarkb#topic General Topics19:31
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:31
clarkbssbarnea|rover: asks if we should run with ops on all our channels (did I read that correctly?)19:32
corvusi have no interest in appearing special in irc at all19:32
*** jawad_axd has quit IRC19:32
dmsimardDoes the "infra-root" ping not work ?19:33
clarkbcorvus: ya I too want to avoid the impression this is a reward to work towards19:33
ssbarnea|roverclarkb: yeah. just an idea, for visibility.19:33
corvusthere are lots of folks well equipped to answer infrastructure questions regardless of whether they have approval rights to certain repos.  i don't want to establish the marking of a two-tier system in irc.19:33
clarkbssbarnea|rover: is there a specific visibility concern you have in mind? is it finding people who can help you with IRC, or with infra services or something else?19:33
ssbarnea|roverfor example i didn't know about the infra-root, and I think many others do not.19:33
ssbarnea|roverbut i also worry a little bit about potential abuse.19:34
ssbarnea|roverclarkb: the only concern was to make it visible who from infra is online.19:34
corvusthere's not much that needs an infra-root anyway.19:34
clarkbwe do have operators, they just don't get the hat by default all the time. So the ops have to escalate privs in order to handle things like abuse19:34
dmsimardssbarnea|rover: There's two keywords that are set up to light our irc clients like christmas trees, "infra-root" and "config-core". We already get a lot of pings every day, is it an issue that people do not know where to ask things ?19:35
fungissbarnea|rover: https://docs.openstack.org/infra/manual/irc.html#technical-support19:35
ssbarnea|roverthese keywards are probably enough19:35
clarkbok, fwiw I also try to skim through scrollback to get a sense for when questions were asked and left unanswered so I can pick those up19:36
clarkbnot always possible though19:36
clarkbI think others (fungi in particular) do similar19:36
fungibeing able to see who from the infra root sysadmins is online and active sounds like a risk, not a reward19:36
dmsimardfungi: the topic in #openstack-infra is already long enough but perhaps we could add that link to it19:36
ianwyeah, looking at the topic ... maybe making it something like "Welcome, we're happy to help, please see ... ^" might be a better topic19:36
fungii frequently go on "silent running" in irc so i can get other work done without being interrupted19:36
ssbarnea|roverok, you convinced me. subject closed/19:37
ianwnot sure links to git are that helpful there19:37
clarkbto summarize though, those of us with ops would rather not wear the hat all the time and instead maybe we can pouint people to docs more effectively using the channel topic19:37
clarkbianw: ya that does sound more welcoming19:37
pabelangerespecially part-time ops :)19:37
clarkbwe can brainstorm a replacement after the meeting then one of us ops can apply it19:37
ssbarnea|roverindeed, channel topic could clearly help.19:37
corvusgit is super important in the topic19:38
clarkbNext item is OpenDev. corvus has configured DNS19:38
corvuswe need to let folks know everything we do is open19:38
corvusand inspectable and self-service19:38
corvusi could see collapsing the topic down to one link, and then linking off from there19:39
corvusbut the main thing is that whatever we do, that needs to be front and center19:39
clarkbcorvus: I actually like that idea as it will make the topic fit in my window :)19:40
clarkblets move on to opendev though as we only have 20 minutes left19:40
corvusdns is working19:40
corvuswe're hosting a website with no content19:40
clarkbI have a todo item to reboot the one opendev dns server that is unhappy with an update19:40
clarkbI will do that after the meeting19:40
corvusi think someone who is not me should write some initial content for the website19:40
corvusit goes here: http://git.openstack.org/cgit/openstack-infra/opendev-website/19:41
clarkb#link http://git.openstack.org/cgit/openstack-infra/opendev-website/ The new website needs content19:41
clarkbI can take a stab at writing some stuff19:41
pabelangershould we say which framework we want to use? or up to initial commit?19:41
clarkbI'm far less useful at the formatting for browser rendering aspect of it19:41
dmsimardWhat's the starting point ? opendevconf's code ?19:41
fungii rather like our http 401 website ;)19:42
clarkbpabelanger: dmsimard: I think we have a clean slate here and using somethign like what zuul has done is probably simplest to start19:42
clarkbwe don't need complex tooling for it and can splat out a fairly straightforward set of html and css?19:42
pabelangerclarkb: agree, I think what zuul has done is a fine start19:42
corvusi believe we suggested that having a page that described the effort and current status was desirable19:42
fungiyeah, splatting raw html/css from a git repo onto the fileserver seems plenty fine for now19:42
dmsimardfrom a maintenance perspective, it's probably best to keep things similar19:42
clarkbcorvus: yup for content that was the intent19:42
corvusand we could post updates there so people can track the effort19:42
pabelangergreat idea19:43
clarkbWhy don't I start with a change with some unformatted content then yall can help with the the rendering aspects19:43
corvusclarkb: thanks; you want to action yourself? :)19:44
clarkb#action clarkb Write up opendev website content then seek help for formatting it nicely19:44
mordredwe were looking at using gatsby for the zuul website ... so we could do netlify-cms integration19:44
corvusalso, if folks want to use a static site generater for a blog thing, that will work fine19:44
mordredI  have a todo list item for zuul to get that done - I agree, not blocking on that for this is better19:44
corvusmordred: yes, i think we should move to that when it exists19:44
clarkb#info move to gatsy with netlify-cms integration when that exists19:45
corvusmordred: in the mean time, i don't think there are any wrong choices that might prevent us from doing that later19:45
mordredI agree with that19:45
corvus(at least, any static site generator, or just plain static site, should be easy to port into that)19:45
clarkbok anything else opendev before we talk about ara?19:45
dmsimardI've used hugo for the new ara website -- mostly because that's what I was familiar with. Works well.19:45
mordredthat said - getting just gatsby up with clarkb's unformatted text will be easy19:46
corvusnext i'm going to try to write up a plan to move gerrit19:46
mordredso consider my hand raised to work with clarkb after there is some content19:46
clarkbmordred: thanks19:46
mordredclarkb: ++19:46
mordredcorvus: ++19:46
corvusand that's [eot] on opendev from me19:46
clarkbCollecting inner ara from system-config integration jobs19:47
clarkb#link https://review.openstack.org/#/q/topic:inner-ara-results+(status:open+OR+status:merged)19:47
clarkbianw: dmsimard: is this a matter of getting reviews and adding the feature or are there design aspects/cocnerns we should be aware of?19:47
ianwso dmsimard did all the work to install ara on bridge.o.o, but we got a bit stuck on where to save the data and how or if we would export it19:47
mordreddmsimard: I like gatsby because it's react with javascript tooling like the zuul dashboard - but basically just consider it to be a javascript tooling version of hugo - basically all the same idea19:47
fungiianw: stuck how?19:48
*** jawad_axd has joined #openstack-meeting19:49
dmsimardfungi: we can't move forward until we get consensus around what to do with bridge.o.o and ara -- do we re-install on a larger flavor, use a trove instance, a local mysql, etc19:49
ianwfungi: as in, do we do it locally, via trove, to local sqlite, do we export it, does it have sensitive stuff ...19:49
*** ekcs has joined #openstack-meeting19:49
dmsimardin the meantime, ianw got in-job "nested" ara reports working for system-config19:49
ianwright, that's my proposal, can we move forward with retargetting this for the CI jobs first19:49
fungiianw: dmsimard: we already said in at least a couple prior meetings that we would use the trove instance for now but plan to make the replacement bridge.o.o large enough to house its own mysql server we can move to using in the future19:49
clarkbya I think there are two things here. The first is updating the CI jobs to have ara for the integration runs. I think we should just go ahead and do that19:50
clarkbthat will then give us data on the sorts of information that ara will expose on the production server19:50
clarkbso that will be a sanity check of whetehr or not its safe to use an exteranlly hosted db for ara19:50
*** zaneb has quit IRC19:50
ianwok, great, well all the changes are out there in that linked topic list, i'd appreciate reviews19:51
dmsimardok so to validate my understanding -- 1) enable ara in nested ansible CI 2) enable ara on bridge.o.o pointing to a trove instance19:51
clarkbdmsimard: assuming that 1) doesn't reveal any deal breakers for 2)19:52
dmsimardalthough for #2, the web application should not be available publicly19:52
ianwright ... is ara that useful without visualisation?19:52
dmsimardianw: the idea would be to browse the data over tunnel to audit it first19:52
dmsimardi.e, passwords without no_log, etc19:53
*** jawad_axd has quit IRC19:53
clarkbya I think we likely want to do a sanity check of the actual production data too once we have it19:53
clarkbbut then if everything looks good consider making it more public19:53
*** erlon has joined #openstack-meeting19:53
dmsimardfwiw, nested results are already available, for example: http://logs.openstack.org/16/617216/20/check/system-config-run-base/0b8074c/bridge.o.o/ara-report/19:54
fungito recap, the discussion was in october19:54
fungi#link http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-10-23-19.01.log.html#l-7019:54
clarkb#link http://logs.openstack.org/16/617216/20/check/system-config-run-base/0b8074c/bridge.o.o/ara-report/ example CI ara for system-config integration jobs19:54
dmsimardfungi: my understanding from back then was that we'd wait to resize bridge.o.o first and then privilege a local mysql installation19:55
ianwfungi: i think my point was mostly that nobody is really driving it, but here is something we can use right now, and would be helpful especially as we do things like incorporate more complex docker stuff into ci jobs19:55
clarkbthe plan: Update CI jobs for nested ARA, check that ara data set for leaked data, fix any leaks, deploy ara against trove in production but don't expose it publicly. Check this again for any leaks, fix leaks, make public19:55
*** zaneb has joined #openstack-meeting19:55
clarkbIf we only implement that first step and improve the CI jobs I think that is worthwhile19:55
*** shrasool has quit IRC19:55
dmsimardclarkb: works for me19:56
fungiyep, i think we concluded in october that the risk associated with using an external db to store the ara data was acceptable since the work had already been done to build it19:56
ianwclarkb: it's the rinse and repeat bit i'd be worried about ... it seems like we could very easily leak things into the logs19:56
clarkbianw: as we make new system-config changes you mean?19:56
ianwclarkb: yep, unless someone is constantly auditing it19:56
clarkbits possible, though hopefully our experiences lceaning things up show us what not to do? I'm mostly trying to avoid assuming its all bad until we have some examples to look at (and the CI examples are great for that)19:57
dmsimardwe could consider setting up http authentication to the ara web page, unless that defeats the purpose19:57
clarkbdmsimard: what the old dashboard gave us was the ability for anyone to check if their thing had worked even if they weren't root19:57
clarkband I think if we set up http auth for this we'd still need to restrict it to roots (since they are the individuals that can see the secrets)19:58
dmsimardclarkb: yeah, that's what I meant by purpose but I forget the amount of details that puppetboard provided19:58
clarkbtimecheck: we have two minutes left and a couple other topics. I think we can pick this back up in the infra channel or on the mailing list but I'd like to call out the other topics realyl quickly before we run out of time19:58
dmsimardwe can follow up in -infra19:58
*** jamesmcarthur has quit IRC19:58
*** e0ne has quit IRC19:58
clarkb#link https://review.openstack.org/#/q/status:open+topic:fedora29 ianw has work to add network manager support to glean. This work is in an effort to support newer fedora and rhel/centos 819:58
*** aojea has quit IRC19:59
clarkbI've reviewed the stack. They look good to me. Maybe someone else that has glean paged in can also take a look19:59
ianwthis is just a request for reviews.  it needs reviews, glean releases, staged dib builds etc so i need some help, but everything is there19:59
clarkb#link https://review.openstack.org/#/c/617218/4 This updates ansible to 2.7.3 on bridge.o.o to fix the cloud launcher playbook. It has the +2's and just needs to be approved now. I didn't approve it in case there was some reason that others knew to not use newer ansible20:00
ianwok, one other thing i wanted to call out was20:00
ianw#link http://grafana.openstack.org/d/qzQ_v2oiz/bridge-runtime?orgId=120:00
clarkbI think ianw should likely approve that one when ready if no one objects in the near future :)20:00
corvusianw: what sends those stats?20:00
ianwwhich shows runtimes, and actually illustrates pretty well when things are broken (without ara :)20:00
ianwcorvus: we have instrumented the scripts that run under cron to send those stats20:00
ianwso if you check on it occasionally, it can be helpful20:01
corvusianw: can you point me to where those stats are transmitted?20:01
clarkbAnd we are slightly over time. THanks everyone. We'll see you next week20:02
corvusianw: ah is it here? http://git.openstack.org/cgit/openstack-infra/system-config/tree/run_all.sh#n5320:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:02
openstackMeeting ended Tue Dec  4 20:02:20 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-12-04-19.01.html20:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-12-04-19.01.txt20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2018/infra.2018-12-04-19.01.log.html20:02
fungithanks clarkb!20:02
ianwcovus: https://git.openstack.org/cgit/openstack-infra/system-config/tree/run_all.sh20:02
*** Shrews has left #openstack-meeting20:02
corvusianw: nice :)20:03
*** jawad_axd has joined #openstack-meeting20:09
*** manjeets_ has joined #openstack-meeting20:13
*** jawad_axd has quit IRC20:13
*** manjeets has quit IRC20:14
*** tetsuro has quit IRC20:29
*** cloudrancher has quit IRC20:37
*** cloudrancher has joined #openstack-meeting20:37
*** takamatsu has joined #openstack-meeting20:44
*** ralonsoh has quit IRC20:47
*** eharney has quit IRC20:53
*** shrasool has joined #openstack-meeting20:55
*** eharney has joined #openstack-meeting21:04
*** armax has quit IRC21:28
*** tpsilva has quit IRC21:32
*** jawad_axd has joined #openstack-meeting21:32
*** jawad_axd has quit IRC21:37
*** shrasool has quit IRC21:38
*** eharney has quit IRC21:40
*** radeks__ has quit IRC21:47
*** jawad_axd has joined #openstack-meeting21:53
*** jawad_axd has quit IRC21:57
*** bobh has quit IRC21:57
*** shrasool has joined #openstack-meeting22:02
*** raildo has quit IRC22:02
*** jawad_axd has joined #openstack-meeting22:14
*** jawad_axd has quit IRC22:19
*** slaweq has quit IRC22:20
*** awaugama has quit IRC22:21
*** takamatsu has quit IRC22:29
*** bobh has joined #openstack-meeting22:30
*** erlon has quit IRC22:33
*** rcernin has joined #openstack-meeting22:34
*** jawad_axd has joined #openstack-meeting22:35
*** slaweq has joined #openstack-meeting22:36
*** jawad_axd has quit IRC22:39
*** slaweq has quit IRC22:42
*** mriedem has quit IRC22:44
*** rcernin_ has joined #openstack-meeting22:45
*** rcernin has quit IRC22:45
*** shrasool has quit IRC22:46
*** slaweq has joined #openstack-meeting22:53
*** jawad_axd has joined #openstack-meeting22:55
*** jawad_axd has quit IRC23:00
*** priteau has quit IRC23:03
*** bobh has quit IRC23:07
*** slaweq has quit IRC23:10
*** rcernin_ has quit IRC23:12
*** rcernin has joined #openstack-meeting23:13
*** munimeha1 has quit IRC23:24
*** shrasool has joined #openstack-meeting23:29
*** shrasool has quit IRC23:30
*** hongbin has quit IRC23:57
*** jawad_axd has joined #openstack-meeting23:57
*** lhinds has quit IRC23:57
*** pabelanger has quit IRC23:57
*** haleyb has quit IRC23:57
*** lhinds has joined #openstack-meeting23:58

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