Tuesday, 2019-10-08

*** baojg has joined #openstack-meeting00:03
*** ileixe_ has quit IRC00:03
*** gyee has quit IRC00:07
*** baojg has quit IRC00:08
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:15
*** markvoelker has joined #openstack-meeting00:23
*** baojg has joined #openstack-meeting00:24
*** lseki has quit IRC00:27
*** markvoelker has quit IRC00:28
*** jamesmcarthur has joined #openstack-meeting00:29
*** brinzhang has joined #openstack-meeting00:33
*** browny_ has joined #openstack-meeting00:45
*** browny_ has quit IRC00:47
*** tetsuro has quit IRC01:05
*** jamesmcarthur has quit IRC01:07
*** jamesmcarthur has joined #openstack-meeting01:07
*** jamesmcarthur has quit IRC01:12
*** tetsuro has joined #openstack-meeting01:16
*** markvoelker has joined #openstack-meeting01:26
*** yaawang has quit IRC01:30
*** yaawang has joined #openstack-meeting01:31
*** yamamoto has joined #openstack-meeting01:36
*** markvoelker has quit IRC01:37
*** markvoelker has joined #openstack-meeting01:37
*** jamesmcarthur has joined #openstack-meeting01:38
*** markvoelker has quit IRC01:42
*** yaawang has quit IRC01:42
*** yaawang has joined #openstack-meeting01:44
*** ykatabam has quit IRC01:47
*** boxiang has joined #openstack-meeting01:48
*** enriquetaso has joined #openstack-meeting01:50
*** yonglihe has joined #openstack-meeting01:52
*** macz has joined #openstack-meeting01:55
*** macz has quit IRC02:00
*** markvoelker has joined #openstack-meeting02:02
*** slaweq has joined #openstack-meeting02:11
*** tetsuro has quit IRC02:14
*** slaweq has quit IRC02:16
*** jamesmcarthur has quit IRC02:16
*** tetsuro has joined #openstack-meeting02:17
*** lhinds has joined #openstack-meeting02:19
*** ykatabam has joined #openstack-meeting02:31
*** jamesmcarthur has joined #openstack-meeting02:36
*** ykatabam has quit IRC02:39
*** ykatabam has joined #openstack-meeting02:39
*** jamesmcarthur has quit IRC02:41
*** ricolin has joined #openstack-meeting02:47
*** igordc has quit IRC02:52
*** dviroel has quit IRC03:00
*** yaawang has quit IRC03:07
*** yaawang has joined #openstack-meeting03:07
*** rfolco has quit IRC03:12
*** igordc has joined #openstack-meeting03:19
*** tetsuro has quit IRC03:37
*** tetsuro has joined #openstack-meeting03:38
*** enriquetaso has quit IRC03:43
*** markvoelker has quit IRC03:49
*** tpatil has joined #openstack-meeting03:50
*** shilpasd has joined #openstack-meeting03:59
samP#startmeeting masakari04:02
openstackMeeting started Tue Oct  8 04:02:08 2019 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:02
*** openstack changes topic to " (Meeting topic: masakari)"04:02
openstackThe meeting name has been set to 'masakari'04:02
*** nitinuikey has joined #openstack-meeting04:02
samPHi all for masakari04:02
samP#topic Critical bugs or patches04:02
*** openstack changes topic to "Critical bugs or patches (Meeting topic: masakari)"04:02
samPAny critical bugs or patches?04:03
tpatilLP Bug : 183971504:03
tpatil#link : https://launchpad.net/bugs/183971504:03
openstackLaunchpad bug 1839715 in masakari "masakari fails if hypervisor name does not match nova service name" [Undecided,In progress] - Assigned to Liam Young (gnuoy)04:03
tpatilPatch is already up : https://review.opendev.org/#/c/675734/04:04
tpatilI have added my comment on this patch04:04
tpatilplease check04:04
*** tashiromt has joined #openstack-meeting04:04
samPtpatil: thanks, I will check your comment04:05
*** yaawang has quit IRC04:06
*** yaawang has joined #openstack-meeting04:08
samPif any other issues, please bring them up any time04:09
samP#topic Train work items04:09
*** openstack changes topic to "Train work items (Meeting topic: masakari)"04:09
samPI think we have review all the docs work.04:10
samPI am reviwing them now.04:10
shilpasdyes, but there is one comment from horizon PTL saying need change in summary for masakari doc https://review.opendev.org/#/c/681198/4//COMMIT_MSG04:11
*** slaweq has joined #openstack-meeting04:11
shilpasdfrom his point of view, even if it is done from point of view of operators, the masakari doc is not equal to an operator document., so suggesting change in summary04:12
shilpasdhis suggestion ""Reorganize masakari documentation""04:12
samPIMHO, this is about operating masakari.04:13
samPas for this patch, reorganize masakari documentation would also fine, I think04:15
shilpasdso will change as suggested, thanks04:16
samPshilpasd: np, thanks04:16
*** slaweq has quit IRC04:16
shilpasdsamP: also need your review for https://review.opendev.org/#/c/673562/, which fixes LP bug 183841804:16
openstackLaunchpad bug 1838418 in masakari "Instances are not cleanup properly after functional tests finished execution" [Undecided,In progress] https://launchpad.net/bugs/1838418 - Assigned to Shilpa Devharakar (shilpasd)04:16
samPFinal RC deadline is 10/11. Let's try to merge the docs before that.04:17
samPshilpasd: thanks. I have just approved it.04:18
shilpasdsamP: thank you04:18
samPAny other Train related items?04:19
*** hyunsikyang__ has joined #openstack-meeting04:19
tpatil#link : https://review.opendev.org/#/c/670680/04:19
tpatilnoauth middleware support04:20
tpatilMainly used by developers04:20
tpatilPretty straight forward patch04:20
tpatilwe can merge it in Train release04:20
samPtpatil: thanks. Approved.04:21
tpatilsamP: Thanks04:21
samPtpatil: np04:21
*** radeks_ has joined #openstack-meeting04:21
*** fungi has quit IRC04:21
*** ykatabam has quit IRC04:22
*** hyunsikyang has quit IRC04:22
samPif no other items, let's move to AOB04:22
samP#topic AOB04:22
*** openstack changes topic to "AOB (Meeting topic: masakari)"04:22
samPAbout summit and PTG04:22
samPUnfortunately I will not be able to join.04:23
tpatilI won't be able to make it this time as well04:24
samPHowever, I can join remotely for any session. especially for project update session.04:24
tpatilWhen is the project update session planned?04:25
*** ykatabam has joined #openstack-meeting04:25
*** fungi has joined #openstack-meeting04:25
tpatiland who will present it?04:25
samP#link https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24387/masakari-project-update-november-201904:26
tpatilOk, During this session, we will need to explain the audience what's done in Train and what is the future roadmap04:27
samPtpatil: That would be fine.04:28
tpatilBut since I'm not attending this session, we will need to change the speaker04:29
samPtpatil: Sure, please email Kendall Nelson about it.04:29
tpatilOk, Will do04:31
tpatilI will suggest Nitin's name and if Shilpa is interested, I can suggest her name too04:33
samPtpatil: thanks.04:33
*** yamamoto has quit IRC04:33
nitinuikeytpatil: ok04:34
shilpasdsure, we coordinately will do04:34
shilpasdtpatil: thanks04:34
*** yamamoto has joined #openstack-meeting04:35
samPshilpasd: nitinuikey: Let's discuss further in our next meeting about the session content.04:36
samPshilpasd: nitinuikey: Thanks for doing this.04:36
samPAny other items to discuss?04:37
samPif not we could finish today's meeting here.04:37
tpatilno more topics from my side04:37
samPtpatil: thanks04:38
samPPlease use openstack-discuss@lists.openstack.org ML or #openstack-masakari @freenode IRC for further discussions.04:38
samPThank you all for attending today's meeting04:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:39
openstackMeeting ended Tue Oct  8 04:39:16 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-10-08-04.02.html04:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-10-08-04.02.txt04:39
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-10-08-04.02.log.html04:39
*** yamamoto has quit IRC04:40
*** tpatil has quit IRC04:45
*** yamamoto has joined #openstack-meeting05:11
*** brinzhang_ has joined #openstack-meeting05:12
*** brinzhang has quit IRC05:15
*** ykatabam has quit IRC05:18
*** ykatabam has joined #openstack-meeting05:19
*** bnemec has quit IRC05:19
*** brinzhang has joined #openstack-meeting05:28
*** shilpasd has quit IRC05:29
*** brinzhang has quit IRC05:29
*** brinzhang has joined #openstack-meeting05:30
*** brinzhang has quit IRC05:31
*** brinzhang has joined #openstack-meeting05:31
*** brinzhang has quit IRC05:31
*** brinzhang_ has quit IRC05:31
*** brinzhang has joined #openstack-meeting05:32
*** brinzhang_ has joined #openstack-meeting05:34
*** brinzhang has quit IRC05:37
*** armax has joined #openstack-meeting05:40
*** markvoelker has joined #openstack-meeting05:50
*** markvoelker has quit IRC05:55
*** yamamoto has quit IRC05:58
*** psachin has joined #openstack-meeting05:59
*** yamamoto has joined #openstack-meeting06:01
*** yaawang has quit IRC06:06
*** brinzhang has joined #openstack-meeting06:06
*** yaawang has joined #openstack-meeting06:07
*** armax has quit IRC06:08
*** brinzhang_ has quit IRC06:10
*** slaweq has joined #openstack-meeting06:11
*** brinzhang has quit IRC06:12
*** brinzhang has joined #openstack-meeting06:12
*** slaweq has quit IRC06:15
*** keiko-k has joined #openstack-meeting06:23
*** slaweq has joined #openstack-meeting06:35
*** nitinuikey has quit IRC06:35
*** trident has quit IRC06:46
*** trident has joined #openstack-meeting06:49
*** ykatabam has quit IRC07:02
*** yamamoto has quit IRC07:04
*** yamamoto has joined #openstack-meeting07:05
*** rcernin has quit IRC07:05
*** ttsiouts has joined #openstack-meeting07:10
*** tesseract has joined #openstack-meeting07:10
*** hyunsikyang has joined #openstack-meeting07:11
*** _pewp_ has quit IRC07:12
*** _pewp_ has joined #openstack-meeting07:13
*** hyunsikyang__ has quit IRC07:15
*** tetsuro has quit IRC07:16
*** tetsuro has joined #openstack-meeting07:16
*** ttsiouts has quit IRC07:26
*** ttsiouts has joined #openstack-meeting07:27
*** ttsiouts has quit IRC07:31
*** lpetrut has joined #openstack-meeting07:45
*** kaisers has joined #openstack-meeting07:47
*** ralonsoh has joined #openstack-meeting07:48
*** keiko-k has quit IRC07:49
*** ttsiouts has joined #openstack-meeting07:52
*** keiko-k has joined #openstack-meeting07:54
*** tpatil has joined #openstack-meeting07:56
*** takahashi-tsc has joined #openstack-meeting08:00
*** nitinuikey has joined #openstack-meeting08:01
tpatil /join #tacker08:15
*** ociuhandu has joined #openstack-meeting08:16
*** tssurya has joined #openstack-meeting08:22
*** zhubx has joined #openstack-meeting08:28
*** e0ne has joined #openstack-meeting08:31
*** boxiang has quit IRC08:32
*** rpittau|afk is now known as rpittau08:38
*** yamamoto has quit IRC08:40
*** yamamoto has joined #openstack-meeting08:42
*** yamamoto has quit IRC08:43
*** priteau has joined #openstack-meeting08:47
*** nitinuikey has quit IRC08:48
*** e0ne has quit IRC08:52
*** tpatil has quit IRC08:52
*** ociuhandu has quit IRC08:57
*** tashiromt has quit IRC09:06
*** keiko-k has left #openstack-meeting09:12
*** e0ne has joined #openstack-meeting09:13
*** yamamoto has joined #openstack-meeting09:28
*** yamamoto_ has joined #openstack-meeting09:29
*** pcaruana has joined #openstack-meeting09:30
*** ociuhandu has joined #openstack-meeting09:30
*** rfolco has joined #openstack-meeting09:32
*** yamamoto has quit IRC09:33
*** brinzhang_ has joined #openstack-meeting09:33
*** yamamoto_ has quit IRC09:34
*** ociuhandu has quit IRC09:35
*** brinzhang has quit IRC09:37
*** takahashi-tsc has quit IRC09:38
*** ociuhandu has joined #openstack-meeting09:43
*** markvoelker has joined #openstack-meeting09:53
*** markvoelker has quit IRC09:58
*** brinzhang_ has quit IRC10:01
*** yamamoto has joined #openstack-meeting10:05
*** tetsuro has quit IRC10:06
*** tetsuro has joined #openstack-meeting10:06
*** slaweq_ has joined #openstack-meeting10:09
*** slaweq has quit IRC10:09
*** yamamoto has quit IRC10:10
*** tetsuro has quit IRC10:11
*** tetsuro has joined #openstack-meeting10:13
*** tetsuro_ has joined #openstack-meeting10:20
*** tetsuro has quit IRC10:21
*** ttsiouts has quit IRC10:22
*** ykatabam has joined #openstack-meeting10:34
*** ykatabam has joined #openstack-meeting10:35
*** bbowen has quit IRC10:38
*** zhubx has quit IRC10:39
*** zhubx has joined #openstack-meeting10:40
*** whoami-rajat has joined #openstack-meeting10:42
*** dklyle has quit IRC10:49
*** dklyle has joined #openstack-meeting10:49
*** rcernin has joined #openstack-meeting10:53
*** yamamoto has joined #openstack-meeting10:56
*** ociuhandu has quit IRC10:56
*** ociuhandu has joined #openstack-meeting11:05
*** ttsiouts has joined #openstack-meeting11:06
*** yamamoto has quit IRC11:10
*** yamamoto has joined #openstack-meeting11:14
*** slaweq_ is now known as slaweq11:15
*** jamesmcarthur has joined #openstack-meeting11:15
*** jamesmcarthur has quit IRC11:19
*** ociuhandu has quit IRC11:34
*** ociuhandu has joined #openstack-meeting11:35
*** ociuhandu has quit IRC11:40
*** bbowen has joined #openstack-meeting11:40
*** tetsuro_ has quit IRC11:52
*** tetsuro has joined #openstack-meeting11:52
*** markvoelker has joined #openstack-meeting11:54
*** ociuhandu has joined #openstack-meeting11:56
*** markvoelker has quit IRC11:59
*** markvoelker has joined #openstack-meeting12:03
*** ociuhandu has quit IRC12:11
*** ociuhandu has joined #openstack-meeting12:17
*** tetsuro has quit IRC12:20
*** yamamoto has quit IRC12:22
*** lseki has joined #openstack-meeting12:26
*** jamesmcarthur has joined #openstack-meeting12:26
*** belmoreira has joined #openstack-meeting12:26
*** tetsuro has joined #openstack-meeting12:26
*** yamamoto has joined #openstack-meeting12:29
*** jamesmcarthur has quit IRC12:31
*** ociuhandu has quit IRC12:44
*** jamesmcarthur has joined #openstack-meeting12:51
*** dviroel has joined #openstack-meeting12:52
*** pcaruana has quit IRC12:53
*** mriedem has joined #openstack-meeting12:59
*** moguimar|gone is now known as moguimar13:02
*** lpetrut has quit IRC13:08
*** raildo has joined #openstack-meeting13:09
*** rcernin has quit IRC13:19
*** vishakha has joined #openstack-meeting13:30
*** ykatabam has quit IRC13:32
*** enriquetaso has joined #openstack-meeting13:37
*** senrique_ has joined #openstack-meeting13:40
*** enriquetaso has quit IRC13:42
*** bnemec has joined #openstack-meeting13:43
*** yamamoto has quit IRC13:48
*** ociuhandu has joined #openstack-meeting13:56
*** lajoskatona has joined #openstack-meeting13:56
*** yamamoto has joined #openstack-meeting13:56
*** rbudden has joined #openstack-meeting13:57
*** yamamoto has quit IRC13:57
*** yamamoto has joined #openstack-meeting13:57
*** mlavalle has joined #openstack-meeting13:58
*** ttsiouts has quit IRC13:58
*** ttsiouts has joined #openstack-meeting13:59
*** ttsiouts has quit IRC14:00
*** ttsiouts has joined #openstack-meeting14:00
slaweq#startmeeting networking14:00
openstackMeeting started Tue Oct  8 14:00:59 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: networking)"14:01
openstackThe meeting name has been set to 'networking'14:01
*** yamamoto has quit IRC14:01
*** diablo_rojo has joined #openstack-meeting14:01
slaweq#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
slaweqShanghai PTG:14:02
slaweqplanning etherpad https://etherpad.openstack.org/p/Shanghai-Neutron-Planning - just a reminder, if You have any ideas about topic for ptg, please add them to this etherpad14:02
*** shintaro has joined #openstack-meeting14:02
slaweqptg schedule is now ready: https://usercontent.irccloud-cdn.com/file/z9iLyv8e/pvg-ptg-sched-214:03
slaweqwe have full 3 days for Neutron14:03
*** davidsha has joined #openstack-meeting14:04
*** senrique__ has joined #openstack-meeting14:04
slaweqand the last one:14:04
slaweqwe have accepted one neutron related session for forum: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24412/neutron-stadium-projects-the-path-forward14:04
slaweqand that's all related to the PTG14:05
slaweqnext announcements topic is "Train departure" :)14:06
*** senrique_ has quit IRC14:06
*** jamesmcarthur has quit IRC14:06
slaweqaccording to the https://releases.openstack.org/train/schedule.html this week is week of last RC releases if needed14:06
slaweqI don't think we need to release rc2 for anything, except midonet which we already did last week14:07
bcafarelyes deadline is Thursday for last minute release-breaking fixes to get in a rc214:07
slaweqbut if You know about any patches which would require such rc2 for any project, please speak about it now :)14:07
slaweqor ping me or amotoki on irc later14:08
bcafarelcoast looks clear from currently open stable/train backports (nothing critical in progress)14:08
amotokinote that it applies to all stadium projects. it is not only for neutron repo.14:09
slaweqamotoki: exactly :)14:09
slaweqbcafarel: thx for info14:09
haleybso i guess it's time to tag the stable branches?  we should take a look at the open changes this week bcafarel14:09
amotokihaleyb: is it about stable branches like stein or older ones?14:10
bcafarelhaleyb: I was writing a similar message :) yes I plan to check queens/rocky/stein status today or tomorrow14:10
haleybstein and older, just so there are new tags for downstream14:10
haleybbcafarel: +114:11
slaweqthx haleyb and bcafarel for taking care of it14:11
slaweqand the most important announcement:14:12
slaweqnext week is Train release week finally14:12
bcafarelI will miss all the train jokes in 2 weeks14:13
slaweqand one last announcement from me for today:14:13
slaweqfew days ago we merged https://review.opendev.org/#/c/685917/ - so now "mechanial" changes can be approved with 1 x +214:13
slaweqany other announcements from the team?14:14
*** senrique__ has quit IRC14:14
slaweqok, let's move on14:15
slaweq#topic Blueprints14:15
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:15
slaweqWe don't have yet milestone Ussuri-1 created so there is no list of targeted BPs14:16
slaweqbut maybe anyone wants to talk about any BP now?14:16
slaweqany updates maybe?14:16
mlavalleI recently sent an email to wwriverrat14:17
mlavallewhom I don't see around14:17
mlavalleabout his blueprint for multiple segments per host in routed networks14:17
mlavalleI am interested in continuing that work14:18
mlavalleso I amy add it soon to the the next milestone dasboard14:18
slaweqmlavalle: thx for update and for volunteering to work on this14:19
davidshaFor the DSCP + Neutron Classifier integration, I'm just working through refactoring based on comments atm.14:20
slaweqdavidsha: so this one we probably also should add soon to the next milestone dashboard, right?14:21
slaweqdavidsha: sure, I will14:21
slaweqok, I think we can move on than14:23
slaweqthx for updates about BPs14:23
slaweq#topic Community goals14:23
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:24
slaweqamotoki: I think that generating pdf docs goal is done now, right?14:24
slaweqall patches on list https://review.opendev.org/#/q/topic:build-pdf-docs+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*) are merged14:24
amotokiwe finished the PDF docs goal :)14:24
ralonsohwell done14:25
slaweqgreat work amotoki - thx a lot14:25
slaweqso I will remove this goal from agenda for next meetings, ok?14:25
amotokithanks all for detail feedback :)14:25
amotokiyeah, we can drop it14:25
slaweqaccording py3 goal, I updated recently etherpad for stadium projects: https://etherpad.openstack.org/p/neutron_stadium_python3_status14:27
slaweqaccording to our completion criteria, networking-odl should be already done as voting jobs as switched14:27
lajoskatonaslaweq: yesh, as we discussed last week14:27
slaweqfor networking-bagpipe, I proposed patch to switch neutron-tempest-plugin job to py3: https://review.opendev.org/#/c/685702/14:28
slaweqand with this patch https://review.opendev.org/#/c/686990/ it should be also fine14:28
amotokiAFAIK, legacy-networking-bagpipe-dsvm-fullstack still depends on py27 too.14:28
slaweqamotoki: but it is non-voting job, right?14:29
amotokiyes, it is non-voting. the job itself is broken now, so it does not matter.14:29
slaweqI want for now focus only on voting jobs14:30
slaweqas I'm not e.g. bagpipe expert and I don't have time to fix non-voting jobs for this project :/14:31
slaweqso, please review https://review.opendev.org/#/c/686990/ and than https://review.opendev.org/#/c/685702/ if You have some time :)14:32
slaweqand also, I saw that haleyb did very important patch for neutron already: https://review.opendev.org/#/c/686833/14:33
haleybmight as well get it started :)14:33
slaweqthx haleyb for that - it's small patch for human big step for humanity ;)14:33
njohnstonnetworking-ovn is also moving forward: https://review.opendev.org/#/c/686987/14:33
haleybthere is still the py27 job defined elsewhere, that's about it14:34
haleybi'll probably get one out for octavia as well14:34
bcafarelthis one is common job definition so it will probably stay last?14:34
amotokiI think tox-py27 will be dropped when a project template for ussuri is defined.14:34
slaweqyes, py27 is comming from template defined by qa team14:34
njohnstonjust as an FYI, not everything is dropping pu27 support.  Since tempest is branchless it will need to operate on py27 for some time yet, and so the same extends to neutron-tempest-plugin14:36
slaweqI think we should create some new etherpad to coordinate removal of such jobs from all stadium repos14:36
*** jamesmcarthur has joined #openstack-meeting14:37
amotokinjohnston: yes, templest plugins should work with stable branches, so we need py35 and py27 supports.14:37
slaweqnjohnston: in neutron-tempest-plugin we are running jobs on py27 for stable branches, and we will keep that still14:37
slaweqbut jobs for train and master are running on py314:37
slaweqin overall, I think we are in good shape for supporting py3 and dropping support for py2 in Ussuri14:39
slaweqok, lets move on14:39
slaweqaccording to ipv6 only deployments there is no too much progress in last week14:39
slaweqgmann proposed new job for neutron-tempest-plugin https://review.opendev.org/#/c/686043/ - I have to review it and check what is missing there still14:40
slaweqnothing else on this topic for today14:40
*** ociuhandu has quit IRC14:40
slaweq#topic Bugs14:40
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:40
slaweqbcafarel was bug deputy last week14:40
slaweqand he send report which is available at: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/009970.html14:40
slaweqit seems like quite week14:41
slaweqbcafarel: any bugs You want to highlight now?14:41
bcafarelyes, not too many bugs and most have fixes in or in progress14:41
bcafarelonly one I had doubts on is https://bugs.launchpad.net/neutron/+bug/184649414:41
openstackLaunchpad bug 1846494 in neutron "neutron-openvswitch-agent and IPv6" [Medium,Confirmed]14:41
bcafareland some nice PTL came in to comment :)14:42
slaweqthx :)14:42
bcafarelalso I saw https://bugs.launchpad.net/neutron/+bug/1794569 from week before was reopened, tested on ocata this time (dvr issue)14:42
openstackLaunchpad bug 1794569 in neutron "DVR with static routes may cause routed traffic to be dropped" [Undecided,New]14:42
bcafarelOne RFE in discussion also for the interested: https://bugs.launchpad.net/neutron/+bug/184628514:44
openstackLaunchpad bug 1846285 in neutron "[RFE] routed network for hypervisor" [Undecided,Confirmed]14:44
bcafareland that's it for the highlights14:44
slaweqthx bcafarel14:44
slaweqaccording to this rfe, I wanted to ask mlavalle if You can take a look at it14:44
slaweqas You are routed networks expert here :)14:44
mlavalleI am actually looking at it right now14:45
bcafarelI have to catch on latest updates, it is in my toread tabs :)14:45
slaweqmlavalle: thx a lot14:45
*** yamamoto has joined #openstack-meeting14:45
slaweqany other bugs anyone wants to talk about today?14:46
*** pcaruana has joined #openstack-meeting14:46
slaweqok, I take that as "no"14:47
slaweq#topic On Demand agenda14:48
*** openstack changes topic to "On Demand agenda (Meeting topic: networking)"14:48
slaweqon demand agenda is empty for today14:48
slaweqbut maybe You have anything else to talk about?14:48
*** hjensas has joined #openstack-meeting14:48
njohnstonI have one thing14:48
njohnstonWith other responsibilities I'd like to give someone else a chance to act as the oslo liaison14:49
njohnstonIt takes very little work - just another IRC meeting to attend14:49
bcafarelwhen is the meeting?14:50
ralonsohnjohnston, I'll ping you latter to know what is needed14:50
ralonsohwhat this person needs to do14:50
njohnstonMondays; 1500 UTC14:51
*** ociuhandu has joined #openstack-meeting14:51
njohnstonralonsoh: Sure thing14:51
njohnstonOnce you hear, ping slaweq if you want to volunteer14:51
*** yamamoto has quit IRC14:51
*** ociuhandu has quit IRC14:51
njohnstonthat's all for me14:52
*** ociuhandu has joined #openstack-meeting14:52
slaweqthx njohnston for Your work on this so far14:53
slaweqand thx bcafarel and ralonsoh for (potentially) volunteering for this role :)14:53
slaweqanything else You want to talk today?14:54
bcafarel:) reading https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo atm, it has some details on role14:54
slaweqthx bcafarel for the link14:55
slaweqI think we can finish this meeting now14:55
slaweqthx for attending and have a great week!14:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:56
openstackMeeting ended Tue Oct  8 14:56:00 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-10-08-14.00.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-10-08-14.00.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-10-08-14.00.log.html14:56
*** ociuhandu has quit IRC14:57
*** ociuhandu has joined #openstack-meeting14:57
*** senrique__ has joined #openstack-meeting14:57
*** shintaro has quit IRC14:58
*** macz has joined #openstack-meeting15:00
ralonsoh#startmeeting neutron_qos15:01
openstackMeeting started Tue Oct  8 15:01:14 2019 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
* njohnston lurks15:01
* slaweq will be lurking as is also on different meeting15:01
*** artom has joined #openstack-meeting15:01
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsohI would like to add davidsha RFE to this section15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/147652715:02
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:02
ralonsohI think this cycle we'll be able to push this feature in neutron15:03
ralonsohdavidsha, do you think so?15:03
davidsharalonsoh, yup!15:03
ralonsohbtw, you didn't update the spec15:03
ralonsohthis is the first thing we need to approve15:04
ralonsohdavidsha, are you going to push an update this week?15:04
davidshakk, I was going to get the refactor done first in case it resulted in the spec being updated15:04
ralonsohbecause we should build this from the basement15:04
ralonsohonce the spec is approved, we can start merging the code15:05
ralonsohperfect, I'll wait for this15:05
ralonsoh(this week??)15:05
davidshayup, I'll get the spec done tomorrow15:05
ralonsohthanks davidsha15:05
ralonsohso next section15:06
ralonsohwe don't have more RFEs15:06
ralonsoh#topic Bugs15:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:06
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/184517615:06
openstackLaunchpad bug 1845176 in neutron "Removing of QoS queue in neutron-ovs-agent fails due to existing references" [Medium,Confirmed]15:06
ralonsohthis one usually happens during the FT tests15:07
ralonsohthis is because when a qos register is going to be removed, all queues should be removed first15:07
ralonsohI'll take a look at this one this week15:07
ralonsohok, next one15:08
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/184516115:08
openstackLaunchpad bug 1845161 in neutron "Neutron QoS Policy lost on interfaces" [High,Confirmed] - Assigned to Nguyen Duy Binh (binhnd)15:08
ralonsohqos lost in interfaces when migrating or rebbot15:08
ralonsohI need to review this one better15:08
ralonsohthe network backend is OVS15:09
ralonsohand this is testing only ingress max BW15:10
davidshaYa, it looks like maybe the QoS extension isn't being runn when the interfaces are being recreated on a hard reboot?15:10
*** senrique__ has quit IRC15:10
ralonsohthis is set in the interface, if I'm not wrong (policyng, not shapping)15:11
ralonsohhmmm I need to investigate this15:11
ralonsohbut according to c#4, this is not happening always15:11
ralonsohyou need to repeat this operation some times15:12
ralonsohok, I'll take this one but not today or tomorrow15:12
davidshaYa, it's whats making me think that maybe it's skipping the QoS backend driver.15:12
davidshaThere is a patch submitted also15:12
ralonsohI see where this is going15:13
ralonsohif no change -> do nothing15:13
ralonsohbut, of course, the interface qos must be applied again15:13
ralonsohI'll review this patch tomorrow15:14
davidshaYa, we had an issue before when we changed the behavior to "do nothing if no change"15:14
davidshaRestarting the service would wipe the state of the port15:15
ralonsohthis should be affecting only Train15:15
ralonsohbecause this change (mine) was added last cycle15:16
ralonsohI remember adding this check: if no change, return15:16
ralonsohI think we need to check something else15:16
davidshakk, I'm thinking of a similar, older version of this, the solution back then was just apply every time.15:17
ralonsohbut what I don't know is what is happening when the port is deleted15:17
*** ociuhandu has quit IRC15:17
ralonsohbecause if the port is recreated15:17
ralonsohnever mind15:18
ralonsohthe port is never deleted15:18
ralonsohonly unbound and the bound again15:18
*** moguimar has quit IRC15:18
davidshathat isn't necessarily triggering the handle_port call then is it?15:19
*** moguimar has joined #openstack-meeting15:19
ralonsohno, if I'm not worng, those are the qos agent api callbacks15:19
ralonsohanyway, I'll take a look at this this week15:21
*** gyee has joined #openstack-meeting15:21
ralonsohsomething else related to bugs?15:21
davidshaI think, handle_notifcation is the api callback, no, nothing from me.15:21
ralonsohyes, this is the api callback15:22
ralonsohthe other method are the agent interface calls15:22
davidshayup, handle and delete port15:23
ralonsohok, let's move15:23
*** jamesmcarthur_ has joined #openstack-meeting15:23
ralonsoh#topic Open Discussion15:23
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:23
ralonsohI have nothing in the agenda15:23
ralonsohdo you?15:24
*** markvoelker has quit IRC15:24
davidshaNothing important, I put this patch up just to make sure I don't lose it again: https://review.opendev.org/#/c/687256/15:24
ralonsohI'll add it to the etherpad15:25
ralonsohbtw, davidsha15:25
davidshaIt's an improved CLI for the classifie15:25
ralonsohcheck the etherpad and add the list of patches under your RFE, if you want15:25
ralonsohlajoskatona, hi15:25
lajoskatonaMore a question or a note: we plan to make guaranteed minimum bandwidth feature work with ovn, and any suggestion can be helpful15:26
*** jamesmcarthur has quit IRC15:26
ralonsohlajoskatona, that means OVN needs to support min-bw15:28
ralonsohlajoskatona, although this qos rule won't do anything15:28
ralonsohthe min-bw won't be applied on the backend15:28
lajoskatonaralonsoh: even min-bw is not wokring with ovn, right now?15:28
ralonsohlajoskatona, I need to check but this is the same as OVS15:29
lajoskatonaralonsoh: I see now in the code that only bandwidth-limit is there, ok so first it should be added to ovn qos-driver15:30
ralonsohlajoskatona, the problem is we need to introduce the qos code in the plugin project15:30
ralonsohthat's the point15:30
lajoskatonaralonsoh: thanks, I check as well to have more details15:30
ralonsohbtw, I don't know the status of QoS in OVN project15:30
ralonsohok, something else in the agenda?15:31
davidshanothing from me15:32
lajoskatonaralonsoh: side question: is there some "official" SIG like meeting or similar between OVN and networking-ovn (~neutron) team?15:32
ralonsohlet me check that15:32
ralonsohslaweq, do you know that? ^^15:32
lajoskatonaok, thanks15:32
lajoskatonaSorry for trolling the meeting15:32
slaweqlajoskatona: there is meeting once in the month15:32
slaweqexactly what ralonsoh just linked :)15:33
slaweqnothing else for now15:33
lajoskatonaslaweq: thanks, good to know15:33
lajoskatonaah, I see the link now15:33
lajoskatonathnks for the info15:33
ralonsohlajoskatona, if you have plans to introduce qos to ovn, ping me to join those meetings15:34
*** ttsiouts has quit IRC15:34
lajoskatonaralonsoh: thanks, I will ping you, and as I know our company plans rubasov will be there as well :-)15:34
ralonsohsomething else??15:35
ralonsohthank you all15:36
ralonsohand see you in 25 mins in the CI meeting15:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:36
openstackMeeting ended Tue Oct  8 15:36:27 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-10-08-15.01.html15:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-10-08-15.01.txt15:36
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-10-08-15.01.log.html15:36
*** belmoreira has quit IRC15:45
*** kopecmartin is now known as kopecmartin|off15:47
*** rpittau is now known as rpittau|afk15:47
*** e0ne has quit IRC15:55
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Oct  8 16:00:10 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.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
slaweqwelcome back :)16:00
ralonsoh(3 meetings in a row)16:01
slaweqralonsoh: yes16:01
slaweqthat's a lot16:01
slaweqbut fortunatelly this one is the last one16:01
slaweqso lets start and do this quick :)16:01
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:01
slaweqplease open ^^ now16:01
slaweq#topic Actions from previous meetings16:02
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:02
slaweqthere is only one action from last week16:02
slaweqslaweq to fix networking-bagpipe python3 scenario job and update etherpad16:02
slaweqI did this patches as I mentioned before on neutron meeting alread16:02
slaweqnow patch https://review.opendev.org/#/c/686990/ is in gate already - thx for reviews16:03
slaweqand with that https://review.opendev.org/#/c/685702/ can also be merged16:03
njohnstongood catch there16:03
slaweqnjohnston: it wasn't me but CI :)16:03
bcafarelstill good catch on the fix :)16:03
slaweqok, lets move on16:04
slaweq#topic Stadium projects16:04
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:04
slaweqaccording python 3 migration we already talked 2 hours ago16:04
slaweqbut I think that now, as we are in Ussuri cycle, we should prepare new etherpad to track dropping of py2 jobs from various repos16:04
slaweqwhat do You think about it?16:05
ralonsohI'm ok with this16:05
ralonsohjust to track it16:05
*** Vadmacs has joined #openstack-meeting16:05
slaweqyes, exactly16:06
ralonsoh(btw, this should be fast)16:06
njohnstonsounds good16:06
slaweqI will prepare it for next week16:06
slaweq#action slaweq to prepare etherpad to track dropping py27 jobs from ci16:06
slaweqaccording to tempest-plugins migration16:06
slaweqwe recently finished step 1 for neutron-dynamic-routing16:07
slaweqthx tidwellr16:07
slaweqso we are only missing removal of tempest tests from neutron-dynamic-routing repo16:07
bcafarelstep 2 patch is usually easier16:08
slaweqand we are still missing neutron-vpnaas16:08
slaweqbcafarel: indeed16:08
*** tesseract has quit IRC16:08
*** mattw4 has joined #openstack-meeting16:09
slaweqanything else regarding stadium projects?16:09
bcafarelmaybe check with mlavalle if he still plans to work on it? last update on patch is some time ago now16:09
bcafarel(regargind vpnaas)16:09
slaweqbcafarel: IIRC he told me recently that he will work on this16:10
bcafarelok so nothing to do for us then :)16:10
slaweqbut I will ping him if there will be no any progress in next few weeks16:10
slaweqok, lets move on then16:11
slaweq#topic Grafana16:11
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:11
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:11
njohnstonzero unit test failures since Saturday!16:12
*** ociuhandu has joined #openstack-meeting16:12
njohnstonwow we write some awesome code. :-)16:12
ralonsohfore sure!!!16:12
ralonsohfor sure!!16:12
slaweqnjohnston: it looks for me more like some issue with data for the graphs16:13
njohnstonslaweq: pessimist. ;-) but how can we tell how large any discrepancy might be?16:14
slaweqnjohnston: tbh I don't know16:14
slaweqmaybe it's just we didn't have any jobs running in gate queue during the weekend?16:15
*** ociuhandu_ has joined #openstack-meeting16:15
njohnstonslaweq: I was looking at the check queue unit test graph16:15
slaweqbecause for check queue graphs looks more "natural"16:15
slaweqnjohnston: ok, so for check queue it seems that it indeed could be that all tests were passing16:16
slaweqas in number of runs graph there are some values16:16
slaweqlets keep an eye on those graphs for next days and if values will still be 0, we will probably need to investigate that :)16:18
*** ociuhandu has quit IRC16:18
njohnstonsounds good16:19
slaweqfrom other things failure rates looks quite good16:19
slaweqI have one additional thing to add regarding grafana16:20
slaweqwe have dashboard for neutron-tempest-plugin: http://grafana.openstack.org/d/zDcINcIik/neutron-tempest-plugin-failure-rate?orgId=116:20
slaweqbut it's unmaintained for now16:20
njohnstonoh, neat16:20
slaweqand as we are adding more and more jobs to this project16:20
slaweqI think we should update this dashboard16:20
slaweqeven if we will not check it often, it may be useful to check from time to time if we have any issues there or not16:21
slaweqas currently I think that we probably have quite often failing fwaas scenario job16:21
slaweqbut I don't have it on dashboard to check that for sure16:21
slaweqany volunteer to update this dashboard?16:21
*** ociuhandu_ has quit IRC16:22
njohnstonI'll do it16:22
slaweqnjohnston: thx a lot16:22
njohnston#action njohnston Update the neutron-tempest-plugin dashboard in grafana16:22
slaweqthat's all about grafana on my side16:23
slaweqdo You have anything else to add/ask?16:23
slaweqok, so lets move on16:23
slaweqI was looking today for any examples of failed jobs from last week16:24
slaweqand I didn't found too much to investigate16:24
slaweq(which is good :))16:24
slaweqI only found one such issue16:24
slaweq#topic Tempest/Scenario16:24
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:24
slaweqSSH failure: https://storage.gra1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_9c2/664646/6/check/tempest-ipv6-only/9c2f68f/testr_results.html.gz16:24
ralonsohwith ip[v6?16:25
slaweqlets check it now if there are maybe any obvious reasons of failure16:25
ralonsohno, ipv416:25
*** igordc has quit IRC16:25
slaweqjob is ipv6-only but IIUC this means that all services are using IPv6 to communicate16:25
slaweqbut vms can use IPv4 still16:25
*** rfolco is now known as not_rlandy16:29
*** not_rlandy is now known as rfolco16:29
slaweqfrom console-log:16:29
slawequdhcpc (v1.23.2) started16:29
slaweqSending discover...16:29
slaweqSending discover...16:29
slaweqSending discover...16:29
slaweqUsage: /sbin/cirros-dhcpc <up|down>16:29
slaweqNo lease, failing16:29
slaweqit seems that fixed IP wasn't configured on instance at all16:30
slaweqso it could be problem in dhcp agent or ovs agent16:30
njohnstonI wonder if the DHCP requests ever got to their destination16:32
slaweqnjohnston: that we can check by downlading devstack.journal.xz.gz and checking it in journalctl tool locally16:32
*** macz has quit IRC16:34
*** macz has joined #openstack-meeting16:34
ralonsohslaweq, sorry but where can we see the dnsmasq logs in devstack.jouirnal?16:38
slaweqralonsoh: if You do like is described in http://storage.gra1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_9c2/664646/6/check/tempest-ipv6-only/9c2f68f/controller/logs/devstack.journal.README.txt.gz16:38
slaweqYou can than check this journal log file and look for e.g. dnsmasq entries there16:38
ralonsohno no, I mean an example of dnsmasq log register16:39
slaweqralonsoh: I see in this file e.g. something like16:40
slaweqOct 07 22:23:25 ubuntu-bionic-rax-ord-0012196912 dnsmasq-dhcp[29182]: DHCPDISCOVER(tap4319b184-00) fa:16:3e:8a:0d:b816:40
slaweqOct 07 22:23:25 ubuntu-bionic-rax-ord-0012196912 dnsmasq-dhcp[29182]: DHCPOFFER(tap4319b184-00) fa:16:3e:8a:0d:b816:40
slaweqOct 07 22:23:25 ubuntu-bionic-rax-ord-0012196912 dnsmasq-dhcp[29182]: DHCPREQUEST(tap4319b184-00) fa:16:3e:8a:0d:b816:40
slaweqOct 07 22:23:25 ubuntu-bionic-rax-ord-0012196912 dnsmasq-dhcp[29182]: DHCPACK(tap4319b184-00) fa:16:3e:8a:0d:b8 host-10-1-0-1016:40
slaweq(it's for other port for sure, but from this job)16:40
slaweqbut I don't see there anything related to resource from this failed test16:42
slaweqany volunteer to check that carefully?16:42
*** kmalloc has left #openstack-meeting16:42
ralonsohslaweq, I can take it16:42
slaweqralonsoh: thx16:43
slaweqaction ralonsoh to check root cause of ssh issue in https://storage.gra1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_9c2/664646/6/check/tempest-ipv6-only/9c2f68f/testr_results.html.gz16:43
slaweq#action ralonsoh to check root cause of ssh issue in https://storage.gra1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_9c2/664646/6/check/tempest-ipv6-only/9c2f68f/testr_results.html.gz16:43
slaweqok, that was all from my side for today16:43
slaweqanything else You want to talk about today?16:43
njohnstonnothing from me16:44
slaweqok, thx a lot for attending16:46
slaweqI will give You almost 15 minutes back :)16:46
slaweqsee You online and on the meeting next week16:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:46
ralonsohsee you!16:46
openstackMeeting ended Tue Oct  8 16:46:39 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-10-08-16.00.html16:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-10-08-16.00.txt16:46
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-10-08-16.00.log.html16:46
*** lajoskatona has left #openstack-meeting16:47
*** tssurya has quit IRC16:49
*** mlavalle has left #openstack-meeting16:58
*** ricolin has quit IRC17:03
*** davidsha has quit IRC17:06
*** priteau has quit IRC17:07
*** ralonsoh has quit IRC17:22
*** markvoelker has joined #openstack-meeting17:25
*** markvoelker has quit IRC17:29
*** enriquetaso has joined #openstack-meeting17:35
*** igordc has joined #openstack-meeting17:46
*** jamesmcarthur_ has quit IRC18:02
*** jamesmcarthur has joined #openstack-meeting18:02
*** markvoelker has joined #openstack-meeting18:06
*** hyunsikyang has quit IRC18:08
*** jamesmcarthur has quit IRC18:14
*** mriedem has quit IRC18:31
*** mriedem has joined #openstack-meeting18:32
*** Shrews has joined #openstack-meeting18:36
*** yamamoto has joined #openstack-meeting18:49
*** markvoelker has quit IRC18:50
*** andrebeltrami has quit IRC18:52
*** yamamoto has quit IRC18:53
*** markvoelker has joined #openstack-meeting18:54
*** ayoung has joined #openstack-meeting18:55
*** ianw_pto is now known as ianw18:59
* fungi looks around19:00
clarkbanyone here for the infra meeting19:01
clarkbsorry got distracted for a minute19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Oct  8 19:01:17 2019 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link http://lists.openstack.org/pipermail/openstack-infra/2019-October/006489.html Our Agenda19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbThe OpenStack release happens in ~1 week. I don't think we have anything in flight we need to be concerned about impacting that, but figured I would mention it19:02
fungiyeah, i think we're in a good spot19:02
fungijob activity has died down a bit now that openstack's in its rc period too19:03
clarkbI'm also going to be afk tomorrow. Trying to find the salmon while they are around this fall.19:03
clarkbAnything else to announce?19:04
corvusi think i will be around19:04
corvusbut i could disappear through the weekend19:04
clarkbcorvus: you need a laptop powered by hamster wheels19:04
fungii'm on hand all week19:04
corvusdepending on the whims of the electric utility provider19:04
fungino plans19:04
fungigranted, electricity and internet access here are always a gamble19:05
clarkb#topic Actions from last meeting19:06
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:06
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-10-01-19.01.txt minutes from last meeting19:06
clarkbThere were none. Lets just keep moving to get into the bulk of the agenda19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkb#topic Update Config Management19:06
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:06
clarkbmordred has reported that review-dev is actually running from the docker image19:07
clarkbI don't think mordred is here today to talk about that more though19:07
corvusooh cool19:07
clarkbIt might be useful to start drafting up a plan to convert the production server though if anyone happens to see mordred19:07
corvusso i guess next step is to switch out the folgers crystals on review.o.o19:07
clarkbya I think so19:07
clarkbAre there any other config management updates from the last week?19:08
clarkb#topic OpenDev19:09
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:09
clarkbI have not yet written the email etherpad for opendev governance. Keep getting distracted by visa things and zuul and nodepool and glean19:10
* clarkb scribbles a note to block the world out on thursday and write a draft19:10
clarkbfungi: is this a good place to talk about the management of storyboard groups or should we do that under the storyboard topic? It sort of straddles these subjects19:11
*** vishakha has quit IRC19:11
fungimaybe storyboard19:11
clarkbOk the last topic I know of re opendev was whether or not we should consider podman over docker.19:12
fungithough this might be a good time to talk about dns/ssl for services hosted in opendev when their domains aren't in our dns management workflow?19:12
clarkbfungi: that is udner the static.o.o topic19:12
clarkb(its on the agenda we'll get to it)19:12
fungiahh, okay. sure it came out of that discussion anyway19:12
clarkbI have no objection to using podman over docker though it would make me happier if podman was more willing to fix bugs in behaviors. Seems they prefer to try and mimic docker behavior of existing functionality as much as possible19:13
fungiwhat is the recommended way to install podman on non-rh distros these days?19:13
corvusthe podman/docker thing isn't urgent -- i mostly brought it up for 2 reasons 1) to get feedback on whether the toolset is robust enough to be considered a complete replacement.  that soft of knowledge helps me know where to focus zuul efforts.   and 2) perhaps that ecosystem, being a bit more open, might be more aligned with our values.19:14
fungidoes its lack of current inclusion in debian/ubuntu pose any challenges?19:14
corvusfungi: i reckon we'd have to use the ppa for now19:14
fungigot it19:14
corvusfungi: but istr you said it's on its way into debian?19:14
clarkbfungi: depends on the distro. For ubuntu there is a PPA that tracks development. For suse its in the main repos aiui. Arch has it on the user package repo19:14
corvusfrom what i can see, there is heavy red hat and suse involvement in development of the tools and libraries19:14
fungicorvus: yeah, it seems to be getting worked on. still that's at best winding up in ubuntu 20.04 lts but maybe later still19:14
corvuswe already rely on the ppa for several other things, and i've been happy with that so far19:15
clarkbskopeo in particular19:15
fungiwe rely on the ppa containing podman, or just ppas in general?19:15
fungiaha, skopeo is in there then?19:15
corvuser, weird typo like 10 lines up ^ s/that soft of knowledge/that sort of knowledge/19:16
clarkbyes skopeo is part of the podman suite of tools19:16
clarkband comes from that particular ppa19:16
fungijust to be clear, we're talking about use of podman instead of docker for setting up the services we run as a part of opendev, right?19:17
clarkbfungi: yes19:17
clarkbgitea (and soon gerrit) for example19:17
corvusthere's a podman-compose tool, so that's pretty straightforward19:17
*** jamesmcarthur has joined #openstack-meeting19:17
corvusbiggest technical win is podman can run containers without a root-level daemon19:18
clarkbit still needs root if you do certain things but ya no daemon and can run without root if you restrict your feature set19:18
corvusthat's also the biggest technical change; some more attention to uids may be required.  but that's pretty straightforward.19:18
fungiyeah, i can't speak to the feature/bug parity between them, but from a which-one-is-more-openly-maintained perspective it sounds like a clear win19:18
clarkbI guess the next step here for me is to install it locally and start using it over docker for a bit19:19
corvustristanC is experimenting with swapping it in to the zuul-quick-start job19:19
corvuswhich happens to have really good coverage of how we use docker/docker-compose, so we can learn some there19:19
corvusand of course, we can do the same in our system-config testing19:19
corvusi'm reading the consensus as 'cautious support for more experimentation'19:20
fungisounds right to me19:21
clarkbanything else on the opendev subject?19:21
fungijust stuff we've got other topics for already19:21
clarkbk lets move on to them then19:21
clarkb#topic Storyboard19:21
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:21
clarkbfungi: want to fill us in on storyboard group management?19:22
funginot a lot to cover since last week. so far it's mostly been investigation of the current crufty automation we have for project and project-group creation19:22
fungiit's sort of a poster child for "what not to do" here19:22
fungipuppet exec calling a utility script in the storyboard repo which pokes values directly through the orm into the db19:23
fungiso best that we build a solution from scratch which can handle that and the group creation/project association bits via rest api interaction19:23
clarkbthat seems like a much safer interface to interact with :)19:24
fungiplan for now is a module which we can call from ansible, using the python-storyboardclient sdk to interact with it to align resources between what's in sb and whats in project-config19:24
fungiand deprecate the old overloading of the storyboard-db-manage utility19:25
corvusis python-sbclient sufficiently developed?19:25
fungiif it's not, then i'll be plumbing additional api calls through it19:25
fungithough i may just look at what boardtty's doing19:25
fungii guess that's going direct to the rest api?19:26
corvustbh, i'm not convinced of the utility of it, since the rest api is so simple.  boartty just does raw rest19:26
fungithat does sound like a great option in that case19:26
*** ociuhandu has joined #openstack-meeting19:26
clarkbthe gitea module in ansible is probably a good example for direct http interaction with apis?19:26
corvus(and at some point, the sb developers started to feel the same way so it lagged -- i honestly have no idea what the situation is now)19:26
clarkb(specifically use a python module to avoid fork overhead, but then do simply python requests?)19:27
fungiclarkb: thanks for the reminder, yes the gitea interaction we have in ansible is how i want to model it19:27
corvusclarkb: yeah, and the approach i like with those kinds of modules is to make them callable from the command line as well as ansible, so it's easy to develop/test without ansible19:27
fungisounds like a plan19:28
clarkbAnything else related to storyboard?19:28
diablo_rojoI think fungi covered it19:29
fungiyeah, nothing new since my update last week19:29
fungii hope to start punching at the keyboard to make the group management module in the coming days19:29
clarkbsounds good thanks19:29
clarkb#topic General Topics19:29
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:29
diablo_rojoThanks clarkb19:29
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup19:30
clarkbfungi: any progress with the wiki?19:30
clarkbLet's talk static.o.o then19:30
clarkb#link https://review.opendev.org/683852 Review spec19:30
fungialways happy to help bring other volunteers up to speed on the wiki too ;)19:30
clarkbwe brought this spec up wtih the TC last week19:30
clarkb#link https://etherpad.openstack.org/p/openstack-org-dns19:30
*** ociuhandu has quit IRC19:31
clarkbthis DNS management etherpad came out of those discussions19:31
mordredclarkb: o/ I'm here for a half a second19:31
*** whoami-rajat has quit IRC19:31
clarkbDo we need or want to update the spec to take into account what we've decided we can do with dns?19:31
clarkbin which case would getting agreement on dns chagnes from the foundation be step 0?19:32
mordredclarkb: yes - review-dev is running the image - but it's been manualled - next step there is to finish the cfg-mgmt change to make sure we're rolling it out properly19:32
corvusto be clear we should decide that now-ish :)19:32
corvusthis is basically a tc+fungi+corvus developed proposal for the infra/opendev team(s) to review19:32
ianwi'll be happy to update the spec to cover that etherpad19:33
*** psachin has quit IRC19:33
clarkbAfter reading it yesterday and clarifying the intent behind it (the foundation didn't ask us to stop managing dns for example) I think I'm in favor of this change. In particular I like that it provides a bridge to show how well dns management can work from the existing system19:33
clarkbto give us things like LE support19:33
corvusif we like it; yeah, let's update the spec.  strictly speaking, i'm not sure foundation agreement/approval is required since we're actually doing *less* openstack dns than we are now, but certainly a heads up/consultation would be good.  we are friendly and talk.  jimmy was part of that discussion too.  he did request a writeup, so just sending that etherpad along would be good i think.19:34
clarkband ya I agree I think we don't awnt to go down the road of opdnev.org/docs/foo and a few months later grow the ability to support docs.foo.org19:34
clarkbwill likely make users unhappy unless they wanted the opendev.org domain in the first place19:35
fungiyep, from my perspective it's mostly that we can precreate a bunch of cnames in openstack.org (and starlingx.io) for stuff and then probably never (or almost never) need to care about what the dns for those domains again19:35
clarkbfungi and I can bring it up with the foundation (I can do that immediately after this meeting)19:36
clarkbdoes anyone object from out end?19:36
corvusand yes, while this is not ideal (openstack-infra hat: i think the openstack project should have more direct involvement in its domain management), i think this helps us achieve our goals with opendev: opendev systems management doesn't rely on any resources which have restricted contribution channels.  it lets us make a sort of "hosting platform" for static content and let projects manage the19:36
corvuspublic-facing dns for that.19:36
*** artom has quit IRC19:37
fungiit also gives us a fairly easy answer for "so your project doesn't control its domain but you want to have a whitelabeled opendev service on a subdomain of it"19:37
fungii guess that's more or less what you said too ;)19:37
fungicname these records to us and we'll do the rest19:38
clarkbI'm not hearing any objections then. ianw maybe fungi and/or I can leave a comment on the spec with a request for a new patchset assuming the foundation has no objections either (and as corvus points out it shouldn't affect the fqdns they manage in that zone)19:38
fungis/we'll do the rest/you can do the rest through opendev/19:38
corvusfungi: or, you know, you can submit a patch to do the rest yourself too :)19:38
corvusright that19:38
*** ayoung has quit IRC19:39
ianwclarkb: sure; although if it would be easier to have more exact details to explain it in the spec to point people too, then i'd need a bit to update it first19:39
fungii'm perfectly happy to go through and precreate all the cnames we want19:39
clarkbianw: I think the etherpad should cover what we need to explain to our co managers of that dns zone19:40
clarkbbut I guess there isn't a strict dependency there if you want to go ahead and start updating it19:40
fungithough we may want to couple that with an audit of dns cruft entries we can clean up, since there's something like a 500 rr limit per zone in rackspace's dns platform19:40
fungiso precreating a bunch of cnames may push us over that limit19:40
clarkbfungi: many of our hosts are already cnames19:41
clarkbwe'll just end up changing their targets19:41
clarkbthen I guess we add the acme cnames19:41
ianwright, i was thinking the level of "this is the names we'll need", so if higher level is ok then etherpad is ok19:41
fungiyeah, but any where we want to move ssl to letsencrypt will need an additional cname each19:41
clarkbthose could push us over I suppose19:41
fungiright, that's what i was considering as a risk19:41
*** ayoung has joined #openstack-meeting19:41
clarkbfungi: ya in that case we should probably count the records we have now and estimate the total number of additions19:41
fungiprobably we should start with a list of which subdomain names we need to do this for19:42
clarkbwe'll also be deleting A and AAAA records19:42
clarkbso it may end up balancing out19:42
*** enriquetaso has quit IRC19:42
fungithat's a great point19:42
fungiA+AAAA vs 2xCNAME19:42
clarkbwe can sort those details out after the meeting19:43
fungisounds good19:43
clarkbianw was there other items to discuss around this spec?19:43
clarkbsounds like no. Lets move on then19:45
ianwi think that will suffice for now ... maybe we want to consider the volume generation on AFS but i think let's get this portion squared first since there's some momentum there19:45
clarkbNext up is CentOS 8. I wanted to bring this up because we are continuing to struggle with Network Manager on ipv6 only clouds and we may want to point out to projects that the images exist once they are there to avoid late transitions like we've had with ubuntu in the past19:46
clarkb#link https://review.opendev.org/#/c/686474/19:46
clarkb#link https://review.opendev.org/#/c/686749/19:46
clarkbare two glean changes that try to explicitly configure ipv6 for interfaces in NM to "trick" it into managing interfaces even if the kernel has gotten there first19:46
clarkbI think they are actually ready at this point if people want to review them. We should also build a centos and fedora 29 image and boot them in FN and rax and ovh and ensure the various different setups work19:47
ianwi've been out and haven't looked closely at that, sorry.  it seems weird we're the only ones who have this problem (although from the old debian bug report, maybe we weren't)19:47
clarkbI can help with getting test images built and booting on the various clouds (maybe we introduce a fault in the nodepool integration job then hold them and copy those images out)19:47
clarkbianw: ya I don't think we are the only ones19:47
clarkbthat bug has had a lot of traction over many years19:48
clarkbianw: and once we have centos8 images ready I think we should advertise that broadly and encourage people to start uplifting 7 to 8 to avoid the problems we've had with ubnutu19:50
fungii think it's more that there aren't a lot of folks continuously booting vast numbers of servers in the right kinds of environments19:50
clarkbor at least start hitting the problems earlier19:50
fungiand also that some projects (like cloud-init) may have worked around it with configuration19:50
ianwi am merging the centos 8 stuff with review from cgoncalves; it is booting in integration tests, i don't expect too many issues19:50
ianwwe don't currently have an upstream .qcow2 image for the image-based builds, which some things use19:51
*** trident has quit IRC19:51
ianwcgoncalves has tested with his kickstart images, i believe, however19:51
clarkband we build it up from scratch19:51
*** jamesmcarthur has quit IRC19:52
ianwright, so yeah the first release will only be -minimal support19:52
ianwalso we took the path discussed on the infra list of not doing pip/virtualenv magic and leaving that up to jobs to configure19:53
*** jamesmcarthur has joined #openstack-meeting19:53
clarkbthat would be a good thing to note when we announce availability19:53
ianwso it is a python-3 only image19:53
*** trident has joined #openstack-meeting19:54
clarkbWe are almost out of time. I wanted to point out I've started populating the ptg etherpad19:54
clarkb#link https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-201919:54
ianwi.e. "pip" and "virtualenv" don't exist ... that would be "pip3" and "python3 -m venv"19:54
clarkb#link https://www.openstack.org/ptg/ We have a schedule19:54
clarkbianw: good to know19:54
clarkbThere is also a published schedule now19:54
clarkbI've not heard anything recently on my visa status. Not sure if a good or bad thing. Will wait patiently19:55
clarkbI expect to hear back this week or next19:55
clarkbAnd with that I'll open it up to all the things19:55
clarkb#topic Open Discussion19:55
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:55
fungiyeah, the embassy still has my passport, no word yet on whether they'll return it with a visa or without or demand more proof i should be allowed to visit19:56
*** jamesmcarthur has quit IRC19:58
clarkbAnd we are at time. Thank you everyone!19:59
corvusclarkb: thanks!19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:59
openstackMeeting ended Tue Oct  8 19:59:46 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-10-08-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-10-08-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-10-08-19.01.log.html19:59
*** Shrews has left #openstack-meeting20:04
*** macz has quit IRC20:05
*** Vadmacs has quit IRC20:09
*** jamesmcarthur has joined #openstack-meeting20:15
*** enriquetaso has joined #openstack-meeting20:23
*** e0ne has joined #openstack-meeting20:23
*** e0ne has quit IRC20:28
*** pcaruana has quit IRC20:35
*** igordc has quit IRC20:59
*** slaweq has quit IRC20:59
*** ayoung has quit IRC21:00
*** igordc has joined #openstack-meeting21:00
*** ayoung has joined #openstack-meeting21:02
*** jbadiapa has quit IRC21:03
*** ykatabam has joined #openstack-meeting21:05
*** raildo has quit IRC21:05
*** enriquetaso has quit IRC21:11
*** slaweq has joined #openstack-meeting21:15
*** slaweq has quit IRC21:20
*** bbowen has quit IRC21:34
*** markvoelker has quit IRC21:43
*** jamesmcarthur has quit IRC22:04
*** ayoung has quit IRC22:06
*** ayoung has joined #openstack-meeting22:08
*** gyee has quit IRC22:14
*** rcernin has joined #openstack-meeting22:26
*** jamesmcarthur has joined #openstack-meeting22:35
*** jamesmcarthur has quit IRC22:36
*** jamesmcarthur has joined #openstack-meeting22:36
*** jamesmcarthur has quit IRC22:39
*** jamesmcarthur has joined #openstack-meeting22:45
*** jamesmcarthur has quit IRC22:50
*** lseki has quit IRC23:14
*** diablo_rojo has quit IRC23:17
*** yamamoto has joined #openstack-meeting23:22
*** ayoung has quit IRC23:28
*** ayoung has joined #openstack-meeting23:29
*** markvoelker has joined #openstack-meeting23:32
*** bbowen has joined #openstack-meeting23:37
*** bbowen has quit IRC23:39
*** bbowen has joined #openstack-meeting23:39
*** mriedem has quit IRC23:51

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