Tuesday, 2019-03-05

*** ttsiouts has joined #openstack-meeting00:07
*** sdake has joined #openstack-meeting00:08
*** sdake has quit IRC00:12
*** tetsuro has joined #openstack-meeting00:13
*** sdake has joined #openstack-meeting00:13
*** _alastor_ has quit IRC00:17
*** Adri2000 has quit IRC00:22
*** _alastor_ has joined #openstack-meeting00:23
*** Adri2000 has joined #openstack-meeting00:25
*** lbragstad has quit IRC00:26
*** _alastor_ has quit IRC00:27
*** ttsiouts has quit IRC00:29
*** bbowen has quit IRC00:36
*** bbowen has joined #openstack-meeting00:36
*** sdake has quit IRC00:41
*** cheng1 has joined #openstack-meeting00:48
*** markvoelker has joined #openstack-meeting00:48
*** ericyoung has quit IRC00:50
*** ericyoung has joined #openstack-meeting00:51
*** cheng1 has quit IRC00:54
*** cloudrancher has joined #openstack-meeting00:56
*** macza has joined #openstack-meeting00:59
*** macza has quit IRC01:03
*** ekcs has joined #openstack-meeting01:07
*** sdake has joined #openstack-meeting01:08
*** _alastor_ has joined #openstack-meeting01:12
*** _alastor_ has quit IRC01:17
*** cheng1 has joined #openstack-meeting01:21
*** markvoelker has quit IRC01:22
*** macza has joined #openstack-meeting01:35
*** macza has quit IRC01:39
*** njohnston has quit IRC01:41
*** gouthamr has quit IRC01:48
*** dmellado has quit IRC01:50
*** stevebaker has quit IRC01:50
*** jamesmcarthur has joined #openstack-meeting01:55
*** whoami-rajat has joined #openstack-meeting02:02
*** bbowen has quit IRC02:03
*** jamesmcarthur has quit IRC02:04
*** sdake has quit IRC02:05
*** jamesmcarthur has joined #openstack-meeting02:06
*** jamesmcarthur has quit IRC02:10
*** macza has joined #openstack-meeting02:11
*** hongbin has joined #openstack-meeting02:13
*** macza has quit IRC02:15
*** markvoelker has joined #openstack-meeting02:19
*** ircuser-1 has joined #openstack-meeting02:28
*** sdake has joined #openstack-meeting02:28
*** jamesmcarthur has joined #openstack-meeting02:37
*** psachin has joined #openstack-meeting02:39
*** gouthamr has joined #openstack-meeting02:50
*** markvoelker has quit IRC02:51
*** jamesmcarthur has quit IRC02:51
*** jamesmcarthur has joined #openstack-meeting02:54
*** dmellado has joined #openstack-meeting02:55
*** jamesmcarthur has quit IRC03:10
*** jamesmcarthur has joined #openstack-meeting03:10
*** apetrich has quit IRC03:15
*** yamamoto has joined #openstack-meeting03:17
*** ekcs has quit IRC03:24
*** stevebaker has joined #openstack-meeting03:25
*** yamamoto has quit IRC03:35
*** yamamoto has joined #openstack-meeting03:35
*** cheng1 has quit IRC03:37
*** markvoelker has joined #openstack-meeting03:48
*** vishalmanchanda has joined #openstack-meeting03:49
*** sdake has quit IRC03:51
*** tpatil has joined #openstack-meeting03:52
*** gyee has quit IRC03:54
*** jamesmcarthur has quit IRC03:57
tpatil#startmeeting Masakari04:00
openstackMeeting started Tue Mar  5 04:00:50 2019 UTC and is due to finish in 60 minutes.  The chair is tpatil. 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
*** shilpasd has joined #openstack-meeting04:01
*** imsurit_ofc has joined #openstack-meeting04:01
tpatilToday Sampath san is not available so I will chair today's meeting04:01
tpatilWho all are available for Masakari meeting?04:01
shilpasdGM Tushar san04:02
tpatilshilpasd : Good Morning04:02
*** tashiromt has joined #openstack-meeting04:02
*** vishakha has joined #openstack-meeting04:02
tpatil#topic Bugs/Patches04:03
*** openstack changes topic to "Bugs/Patches (Meeting topic: Masakari)"04:03
tpatilAny bugs that  you want to talk about?04:03
tpatilOk, Moving to next topic04:05
tpatil7 March 2019 is the Stein-3 milestone.04:05
tpatilSo please push all your feature and bug patches soon and ask for review04:06
tpatil#topic: Stein work items04:06
*** openstack changes topic to ": Stein work items (Meeting topic: Masakari)"04:06
tpatil1) Send notifications for all API changes04:06
shilpasdsaw your review comments here, will make changes accordingly and push the patch for further review04:07
tpatilshilpasd: I have given minor nit comments on your patch. if you can address them we can get that patch merge soon04:07
shilpasdyes, after this meeting will do so, thank you04:07
tpatilshilpasd: Ok, thank you.04:07
tpatil2) functional tests04:08
tpatil#link : https://review.openstack.org/#/c/633663/04:08
tpatilI think this patch needs to be rebased04:08
tpatilshilpasd: Can you please request Jayashree to do the needful as she is working in your team?04:08
shilpasdyes Tushar san, will do requested04:09
tpatilshilpasd: Thanks04:09
tpatil3) Add progress details for recovery workflows04:10
tpatilshilpasd: Some of the jobs are failing. please take a loot at it04:10
shilpasdyes, will look into it04:10
tpatilin requirements.txt, you should include SQLAlchemy-Utils to fix the requirements job failing issue04:11
tpatilshilpasd: Have you solved the taskflow db creation issue?04:12
shilpasdyes04:12
tpatilshilpasd: what was the issue?04:12
shilpasdissue was with 'alembic_version'04:12
shilpasdthat table needs to be clear04:12
tpatilshilpasd: Ok04:13
shilpasdthis table is also getting added along with persistence DB tables04:13
tpatilshilpasd: I have started reviewing your patches04:13
shilpasdthank you for review04:13
tpatilI think you have dependency on the openstacksdk inorder to render the progress details in masakari dashboard, correct?04:14
shilpasdyes and also on python-masakariclient04:14
tpatilon some of the patches I have added comment to set dependency correctly so that it's clear which patches should be merged first04:15
shilpasdok, will take a look on it, and will set dependency accordingly04:16
tpatilshilpasd: Ok ,Thank you04:17
tpatilshilpasd: You have added "connection_for_notification_persistence" config option under DEFAULT section, I think it should add it in a new section taskflow. I will add my comment on the patch04:19
tpatilas only taskflow will know how to add it's related db tables04:20
shilpasdactually saw that 'notification_driver' conf option is under [defult] section, so added there04:20
shilpasdwill change it as you suggested here, thank you04:20
*** markvoelker has quit IRC04:22
tpatilAny other items from Stein cycle left for discussion?04:26
tashiromt i dont have any topic04:27
shilpasdNo, you covered All topics04:27
tpatilOk, Then let's end this meeting early04:28
shilpasdok, thank you04:28
tpatilThank you, All04:28
tpatil#endmeeting04:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:28
openstackMeeting ended Tue Mar  5 04:28:31 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-03-05-04.00.html04:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-03-05-04.00.txt04:28
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-03-05-04.00.log.html04:28
tashiromtthank you all04:29
*** jamesmcarthur has joined #openstack-meeting04:35
*** sridharg has joined #openstack-meeting04:41
*** jamesmcarthur has quit IRC04:44
*** armax has quit IRC04:48
*** jamesmcarthur has joined #openstack-meeting04:48
*** jamesmcarthur has quit IRC04:52
*** tpatil has left #openstack-meeting04:53
*** jamesmcarthur has joined #openstack-meeting05:00
*** janki has joined #openstack-meeting05:08
*** hongbin has quit IRC05:09
*** markvoelker has joined #openstack-meeting05:19
*** ekcs has joined #openstack-meeting05:26
*** cheng1 has joined #openstack-meeting05:31
*** jamesmcarthur has quit IRC05:35
*** jhesketh has quit IRC05:47
*** jhesketh has joined #openstack-meeting05:48
*** sdake has joined #openstack-meeting05:48
*** cheng1 has quit IRC05:48
*** sdake has quit IRC05:50
*** markvoelker has quit IRC05:51
*** pcaruana has joined #openstack-meeting05:52
*** sdake has joined #openstack-meeting05:57
*** cheng1 has joined #openstack-meeting05:58
*** jamesmcarthur has joined #openstack-meeting06:03
*** pcaruana has quit IRC06:07
*** _alastor_ has joined #openstack-meeting06:08
*** jamesmcarthur has quit IRC06:09
*** _alastor_ has quit IRC06:12
*** ekcs has quit IRC06:12
*** dims has quit IRC06:24
*** e0ne has joined #openstack-meeting06:24
*** dims has joined #openstack-meeting06:26
*** e0ne has quit IRC06:33
*** dims has quit IRC06:36
*** dims has joined #openstack-meeting06:37
*** vishalmanchanda has quit IRC06:38
*** jamesmcarthur has joined #openstack-meeting06:40
*** cheng1 has quit IRC06:40
*** jamesmcarthur has quit IRC06:44
*** e0ne has joined #openstack-meeting06:46
*** markvoelker has joined #openstack-meeting06:48
*** Luzi has joined #openstack-meeting06:51
*** jamesmcarthur has joined #openstack-meeting06:56
*** sridharg has quit IRC06:57
*** jamesmcarthur has quit IRC07:01
*** sridharg has joined #openstack-meeting07:02
*** cheng1 has joined #openstack-meeting07:06
*** e0ne has quit IRC07:07
*** slaweq has joined #openstack-meeting07:11
*** markvoelker has quit IRC07:22
*** aojea has joined #openstack-meeting07:23
*** flaper87 has quit IRC07:32
*** flaper87 has joined #openstack-meeting07:33
*** yamamoto has quit IRC07:34
*** ralonsoh has joined #openstack-meeting07:34
*** kopecmartin|off is now known as kopecmartin07:34
*** yamamoto has joined #openstack-meeting07:36
*** apetrich has joined #openstack-meeting07:43
*** joxyuki_ has joined #openstack-meeting07:46
*** bhagyashris has joined #openstack-meeting08:00
*** shubham_potale has joined #openstack-meeting08:01
*** dkushwaha has joined #openstack-meeting08:05
*** JangwonLee has quit IRC08:09
*** tpatil_ has joined #openstack-meeting08:09
*** tssurya has joined #openstack-meeting08:16
*** e0ne has joined #openstack-meeting08:17
*** markvoelker has joined #openstack-meeting08:18
*** pcaruana has joined #openstack-meeting08:18
*** JangwonLee has joined #openstack-meeting08:23
*** pcaruana has quit IRC08:25
*** vishalmanchanda has joined #openstack-meeting08:26
*** bhagyashris has left #openstack-meeting08:30
*** sdake has quit IRC08:36
*** tpatil_ has quit IRC08:37
*** pcaruana has joined #openstack-meeting08:37
*** priteau has joined #openstack-meeting08:42
*** pcaruana has quit IRC08:44
*** markvoelker has quit IRC08:51
*** ttsiouts has joined #openstack-meeting08:52
*** cschwede has joined #openstack-meeting08:57
*** e0ne has quit IRC08:58
*** e0ne has joined #openstack-meeting09:00
*** pcaruana has joined #openstack-meeting09:01
*** macza has joined #openstack-meeting09:01
*** cschwede has quit IRC09:03
*** macza has quit IRC09:05
*** ttsiouts has quit IRC09:05
*** finixlei has joined #openstack-meeting09:05
*** finix has joined #openstack-meeting09:05
*** ttsiouts has joined #openstack-meeting09:06
*** cschwede has joined #openstack-meeting09:07
*** ttsiouts has quit IRC09:10
*** ttsiouts has joined #openstack-meeting09:12
*** finixlei has quit IRC09:17
*** finix has quit IRC09:17
*** geguileo has joined #openstack-meeting09:20
*** cschwede has quit IRC09:25
*** cschwede has joined #openstack-meeting09:29
*** cheng1 has quit IRC09:34
*** markvoelker has joined #openstack-meeting09:48
*** cheng1 has joined #openstack-meeting09:49
*** sdake has joined #openstack-meeting09:56
*** yamamoto has quit IRC10:07
*** cheng1 has quit IRC10:08
*** _alastor_ has joined #openstack-meeting10:09
*** _alastor_ has quit IRC10:14
*** markvoelker has quit IRC10:22
*** tetsuro has quit IRC10:25
*** tashiromt has quit IRC10:25
*** tetsuro has joined #openstack-meeting10:29
*** yamamoto has joined #openstack-meeting10:42
*** erlon has joined #openstack-meeting10:45
*** sdake has quit IRC10:51
*** macza has joined #openstack-meeting10:51
*** sdake has joined #openstack-meeting10:55
*** macza has quit IRC10:55
*** cheng1 has joined #openstack-meeting10:56
*** electrofelix has joined #openstack-meeting10:57
*** cheng1 has quit IRC11:05
*** markvoelker has joined #openstack-meeting11:19
*** ttsiouts has quit IRC11:19
*** ttsiouts has joined #openstack-meeting11:20
*** janki has quit IRC11:22
*** ttsiouts has quit IRC11:24
*** e0ne has quit IRC11:32
*** vishalmanchanda has quit IRC11:36
*** tetsuro has quit IRC11:40
*** e0ne has joined #openstack-meeting11:42
*** imsurit_ofc has quit IRC11:44
*** cheng1 has joined #openstack-meeting11:46
*** markvoelker has quit IRC11:51
*** cheng1 has quit IRC11:54
*** ttsiouts has joined #openstack-meeting12:01
*** zhubx has quit IRC12:09
*** zhubx has joined #openstack-meeting12:10
*** ociuhandu has quit IRC12:14
*** mmethot has quit IRC12:15
*** niska has quit IRC12:26
*** apetrich has quit IRC12:30
*** apetrich has joined #openstack-meeting12:31
*** niska has joined #openstack-meeting12:31
*** joxyuki_ has quit IRC12:33
*** apetrich has quit IRC12:38
*** sdake has quit IRC12:39
*** cheng1 has joined #openstack-meeting12:40
*** mriedem has joined #openstack-meeting12:41
*** yamamoto has quit IRC12:44
*** yamamoto has joined #openstack-meeting12:46
*** markvoelker has joined #openstack-meeting12:49
*** yamamoto has quit IRC12:52
*** apetrich has joined #openstack-meeting12:56
*** yamamoto has joined #openstack-meeting12:58
*** njohnston has joined #openstack-meeting13:01
*** bbowen has joined #openstack-meeting13:09
*** bbowen_ has joined #openstack-meeting13:11
*** yamamoto has quit IRC13:14
*** bbowen has quit IRC13:14
*** janki has joined #openstack-meeting13:17
*** jamesmcarthur has joined #openstack-meeting13:18
*** cheng1_ has joined #openstack-meeting13:19
*** sdake has joined #openstack-meeting13:20
*** markvoelker has quit IRC13:21
*** cheng1 has quit IRC13:22
*** jesusaur has quit IRC13:22
*** vishakha has quit IRC13:25
*** jesusaur has joined #openstack-meeting13:25
*** _alastor_ has joined #openstack-meeting13:30
*** cloudrancher has quit IRC13:30
*** jamesmcarthur has quit IRC13:31
*** _alastor_ has quit IRC13:35
*** bbowen_ is now known as bbowen13:37
*** priteau has quit IRC13:41
*** raildo has joined #openstack-meeting13:43
*** jamesmcarthur has joined #openstack-meeting13:46
*** priteau has joined #openstack-meeting13:53
*** yamamoto has joined #openstack-meeting13:53
*** vishakha has joined #openstack-meeting13:54
*** cloudrancher has joined #openstack-meeting13:57
*** cheng1_ has quit IRC13:58
*** yamamoto_ has joined #openstack-meeting14:01
*** yamamoto has quit IRC14:03
*** mmethot has joined #openstack-meeting14:05
*** lbragstad has joined #openstack-meeting14:06
*** jamesmcarthur has quit IRC14:06
*** sdake has quit IRC14:11
*** janki has quit IRC14:12
*** janki has joined #openstack-meeting14:12
*** dklyle has joined #openstack-meeting14:13
*** mjturek has joined #openstack-meeting14:17
*** markvoelker has joined #openstack-meeting14:18
*** cloudrancher has quit IRC14:20
*** ttsiouts has quit IRC14:21
*** sdake has joined #openstack-meeting14:22
*** ttsiouts has joined #openstack-meeting14:22
*** sdake has quit IRC14:23
*** ttsiouts has quit IRC14:25
*** ttsiouts has joined #openstack-meeting14:25
*** cloudrancher has joined #openstack-meeting14:27
*** sdake has joined #openstack-meeting14:34
*** hongbin has joined #openstack-meeting14:47
*** sdake has quit IRC14:48
*** raildo has quit IRC14:49
*** sdake has joined #openstack-meeting14:49
*** njohnston has quit IRC14:50
*** njohnston has joined #openstack-meeting14:50
*** markvoelker has quit IRC14:52
*** pcaruana has quit IRC14:57
*** awaugama has joined #openstack-meeting14:58
*** munimeha1 has joined #openstack-meeting14:59
*** cheng1 has joined #openstack-meeting15:01
*** e0ne has quit IRC15:02
*** Luzi has quit IRC15:02
*** awaugama has quit IRC15:03
*** mjturek has quit IRC15:03
*** sdake has quit IRC15:04
*** sdake has joined #openstack-meeting15:07
*** eharney has joined #openstack-meeting15:09
*** cloudrancher has quit IRC15:10
*** cloudrancher has joined #openstack-meeting15:11
*** e0ne has joined #openstack-meeting15:13
*** awaugama has joined #openstack-meeting15:15
*** cloudrancher has quit IRC15:24
*** carlos_silva has joined #openstack-meeting15:31
*** jgriffith has quit IRC15:36
*** jamesmcarthur has joined #openstack-meeting15:37
*** pcaruana has joined #openstack-meeting15:42
*** armax has joined #openstack-meeting15:46
*** markvoelker has joined #openstack-meeting15:48
*** sdake has quit IRC15:49
*** mjturek has joined #openstack-meeting15:49
*** zhubx has quit IRC15:55
*** zhubx has joined #openstack-meeting15:56
*** mlavalle has joined #openstack-meeting15:58
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Mar  5 16:00:19 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
mlavalleo/16:00
*** belmoreira has quit IRC16:00
slaweqhi16:00
slaweqlets wait few minutes for others to join16:01
*** sdake has joined #openstack-meeting16:01
mlavallewhile we wait, did you ping rubasov about the patches yet to be revieiwed?16:01
njohnstono/16:01
ralonsohhi16:01
*** _alastor_ has joined #openstack-meeting16:01
*** cheng1 has quit IRC16:01
slaweqmlavalle: yes I talked with rubasov about it16:02
slaweqI will give You later log from what we talked, ok?16:02
slaweqok, lets start16:02
bcafarelo/16:02
haleybhi16:02
slaweq#topic Actions from previous meetings16:03
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:03
slaweqfirst one was16:03
slaweqnjohnston to create etherpad with python3 status of stadium projects16:03
njohnston#link https://etherpad.openstack.org/p/neutron_stadium_python3_status16:03
njohnstonI identified the jobs that look like they are still running py216:03
njohnstonby going into the job log for every job and seeing what the full path to libraries were reported in tracebacks, seemed like the most reliable method16:04
njohnstonat this point all automatically generated changes are merged and py3 unit test jobs are present and passing16:04
slaweqthx njohnston, great job16:05
njohnstonI started on the list with bagpipe trying a zuul v3 migration as well.16:05
njohnstonso with your approval I will send this to the ML16:05
njohnstonand work on a few of the changes mysqlf16:05
njohnston*myself16:06
slaweqok, that sounds good for me16:06
mlavalleyes, great!16:06
slaweqand IMO we should focus only on voting jobs, non-voting jobs should be taken care by project's team16:06
slaweqwhat do You think?16:06
bcafarelthe list does not look too bad nice (of course, no guarantee what will happen when trying to move some of them to py3)16:07
njohnstonI agree, I just made a note of them for the sake of completeness16:07
njohnstonso that if a project wants to mark a job voting then they know they should also make it py316:07
mlavalleyes, only voting jobs16:07
slaweqyes, that's good we have it on the list but lets take care only about voting jobs from this list :)16:07
njohnston+116:07
slaweqok, lets move on then16:09
slaweqnext one was16:09
slaweqslaweq to check bug https://bugs.launchpad.net/neutron/+bug/181648916:09
openstackLaunchpad bug 1816489 in neutron "Functional test neutron.tests.functional.agent.l3.test_ha_router.LinuxBridgeL3HATestCase. test_ha_router_lifecycle failing" [High,Fix released] - Assigned to Slawek Kaplonski (slaweq)16:09
slaweqI did, and fix is merged: https://review.openstack.org/64040016:09
slaweqnext one was:16:09
slaweqslaweq to create bionic test patches for stadium projects16:09
slaweqtest patches are done for neutron and stadium projects: patches done: https://review.openstack.org/#/q/topic:legacy-job-bionic+status:open+owner:%22Slawek+Kaplonski+%253Cskaplons%2540redhat.com%253E%2216:10
slaweqI found some bugs, so reported it on launchpad16:11
slaweqI also listed summary to ML: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003129.html16:11
slaweqif someone wants to help, You can take a look at those bugs and propose fixes :)16:11
slaweqfor networking-ovn lucasgomes already proposed fix, so that is fine16:12
slaweqquestions, comments?16:12
mlavallegood job, thanks!16:12
njohnstonlooks great!  good work.16:12
slaweqthx16:12
slaweqok, lets move on16:13
slaweqslaweq to prepare etherpad and plan of moving tempest plugins from stadium projects to neutron-tempest-plugin repo16:13
slaweqso I did etherpad https://etherpad.openstack.org/p/neutron_stadium_move_to_tempest_plugin_repo with "plan of work to do"16:13
slaweqplease check if that makes sense for You16:13
slaweqgenerally it's only 5 projects which have some tempest tests to move16:14
mlavallethat's a manageable number16:14
slaweqI didn't list here 3rd party projects like for vmware-nsx16:14
njohnstonvery nice16:14
slaweqit's only related to stadium projects16:14
slaweqis that fine? or should we take care of 3rd party project too?16:15
mlavalleI think tidwellr can help us with dynamic routing16:15
njohnstonjust FYI for the meeting minutes; the link for the bionic migration email was incorrect.  The correct one is: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003479.html16:15
slaweqnjohnston: thx16:15
mlavalleI can ping tidwellr and ask him to help16:15
bcafarelI'd say 3rd party by definition means outside of common repo16:15
slaweqbcafarel: yes, I also think that16:15
slaweqbut according to what QA team wants they also should be moved to separate repositories16:16
mlavallethat leaves 4 repos16:16
njohnstonI think 3rd party projects would be outside the scope of this upstream committee, but might be in scope for distro vendors like Red Hat or SuSE to work with as part of the distro offerings outside the scope of the official stadium support16:16
njohnstonif you know what I mean16:16
slaweqnjohnston: yes, I know16:16
slaweqnjohnston: that we can discuss downstream too :)16:17
slaweqok, so getting back to the list16:17
slaweqmlavalle will ask tidwellr to help with dynamic-routing, that's good16:17
slaweqany other volunteers?16:17
mlavallebefore going on....16:18
slaweqif You want to help, please add You name in etherpad16:18
mlavalleI got confused16:18
slaweqmlavalle: why?16:18
mlavalleto make sure16:18
mlavallewe are moving these plugins to the neutron-tempest-plugin repor, right?16:18
slaweqyes16:18
mlavalleok16:18
slaweqwe agreed on that on last meeting I think16:19
slaweqit was already done for midonet some time ago, so we will do it for others too16:19
bcafarelit was a request from QA in Denver PTG right?16:19
slaweqbcafarel: right16:19
mlavalleI know, but I got cofused by something that was said above... nevermind16:19
slaweqmlavalle: sure, I understand :)16:20
bcafarelI can probably give a hand for sfc, I still remember a few things there :)16:20
mlavallefor bgpvpn.... have we asked tmorin?16:20
njohnstonI put my name down for fwaas16:20
mlavalleI took sfc16:20
slaweqok, I also put in this etherpad some "action plan" how to perform such migration but please read it and update if You think it should be done differently16:21
mlavalleunless bcafarel wants it16:21
mlavallethen I'd take vpnaas16:21
bcafarelmlavalle: no problem, I can do vpnaas16:21
mlavallebcafarel: let's switch. you know sfc well16:21
mlavallein case there are issues16:22
slaweqI can ping tmorin about bgpvpn tomorrow16:22
*** markvoelker has quit IRC16:22
bcafarel^ sounds good, before "volunteering" him16:22
bcafarelmlavalle: ack :)16:22
slaweqbasically there shouldn't be big problems with it, it's "just" rehoming tests to other repo :)16:22
slaweqbut we also need to define new jobs for those tests16:23
slaweqok, can we move forward then?16:24
mlavalleso each volunteer is responsible for the jobs of his repo?16:24
njohnston+116:24
slaweq+116:24
bcafarelall good16:24
slaweqok, that was easy :)16:25
slaweqthx guys :)16:26
slaweqlets go to next topics16:26
slaweqas we already talked about transiton to bionic and python 3, lets go to16:26
slaweq#topic Grafana16:26
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:26
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:26
*** liuyulong is now known as liuyulong_zzz16:27
bcafarelsometimes I think we should open this link in some tab when starting the meeting (to give it time to load)16:27
slaweqbcafarel: that's good idea16:28
slaweqI will try to remember to put it as first thing in the meeting next time :)16:28
slaweqso basically we have "only" 2 problems now :/16:29
slaweqneutron-fullstack and functional tests are in very bad shape16:29
mlavallefullstack/ functional?16:29
slaweqyes, most of tempest/scenario jobs are fine16:29
slaweqone thing to mention: I added py37 UT job to dashboard recently16:30
slaweqand moved lower-constraints job to the same graph too as it's also UT job in fact16:30
slaweqany questions/comments?16:31
bcafarelmakes sense (the "new" UT graph)16:32
slaweqthx bcafarel :)16:32
slaweqlets than talk about functional/fullstack issues16:32
slaweq#topic fullstack/functional16:32
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:32
slaweqso, first functional tests16:32
slaweqI recently noticed and reported 3 different bugs:16:33
slaweqhttps://bugs.launchpad.net/neutron/+bug/1818334 - this one isn't very big issue as it happend "only" few times16:33
openstackLaunchpad bug 1818334 in neutron "Functional test test_concurrent_create_port_forwarding_update_port is failing" [Medium,Confirmed]16:33
slaweqI wanted to ask liuyulong_zzz that maybe he can take a look as he was doing this test IIRC16:33
mlavallewe can bring it up tomorrow in the l3 meeting16:34
mlavalleI'll do it16:34
slaweqmlavalle: thx16:34
mlavalleso, we want to ask if he is still fixing it?16:34
slaweqnow, next bugs are much more urgent:16:34
slaweqhttps://bugs.launchpad.net/neutron/+bug/181861316:34
openstackLaunchpad bug 1818613 in neutron "Functional/fullstack qos related tests fails often" [Critical,Confirmed]16:34
*** imacdonn has quit IRC16:35
slaweqthis one is I think somehow related to ralonsoh patch https://review.openstack.org/#/c/406841/16:35
*** imacdonn has joined #openstack-meeting16:36
ralonsohslaweq, how?16:36
slaweqralonsoh: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22line%2052,%20in%20_minimum_bandwidth_initialize%5C%2216:37
slaweqit looks that it started failing like that when we merged Your patch16:37
slaweqbut it's only from my quick look, so please don't take it as 100% sure thing :)16:37
ralonsohslaweq, I'll take a look at this now16:38
slaweqralonsoh: thx16:38
slaweqin bug report You have link to example failure and to logstash query16:38
mlavallegracias ralonsoh16:38
mlavallecomo siempre, muy entron16:38
slaweqI know that dougwig also wanted to look at them so please maybe sync with him16:38
slaweqok, and second of those bugs is related to L3 HA: https://bugs.launchpad.net/neutron/+bug/181861416:39
openstackLaunchpad bug 1818614 in neutron "Various L3HA functional tests fails often" [Critical,Confirmed]16:39
slaweqin this case also many random tests are failing16:39
slaweqand only common thing between them is that they are all failing when waiting for router to be transitioned to master16:39
slaweqso from that I would say that first thing to check is keepalived and all things related to it16:40
*** janki has quit IRC16:41
*** kopecmartin is now known as kopecmartin|off16:41
*** janki has joined #openstack-meeting16:41
slaweqmlavalle: maybe You can also raise it on tomorrow's L3 meeting?16:41
mlavalleyou read my mind.... I'll add a tage to it16:42
slaweqmlavalle: thx16:42
slaweqI saw in neutron channel that dougwig is looking at this now, I will sync later with him if he will need any help on that16:43
slaweqand basically those are most urgent functional tests issues which fails a lot recently16:43
dougwigi was adding elastic queries, i'm not sure how much time i have for these particular bugs.16:43
slaweqdougwig: hi, ok16:43
mlavalleall help is welcome dougwig16:43
dougwigi'll try to give it some cycles today, but i'm not sure.16:43
slaweqdougwig: so if You would found something, please write it in bug report16:44
dougwigok.16:44
slaweqI will tomorrow morning continue work on it16:44
slaweqthx dougwig :)16:44
mlavalledougwig, slaweq: let's just update the bug with whatever progress we make16:44
slaweqmlavalle++16:44
mlavalleso others can follow from that point16:44
slaweqok, and now fullstack tests16:45
slaweq- https://bugs.launchpad.net/neutron/+bug/181833516:45
openstackLaunchpad bug 1818335 in neutron "Fullstack test test_dscp_marking_packets fails" [Medium,Confirmed]16:45
* mlavalle aslo added a l3 dvr backlog tag to the port forwarding bug16:45
slaweqI found quite many times some issues with this test16:45
*** tssurya has quit IRC16:45
slaweqit always fails because no marked packet was received16:46
mlavalleis the priority right?16:46
slaweqI don't know if that is issue in L2 agent or maybe in tcpdump which is checking those packets16:46
slaweqmlavalle: what is the priority?16:46
mlavalleof the bug, medium?16:46
slaweqyes, I marked it like that few days ago16:47
mlavalleok16:47
slaweqbut now I think we can change to high16:47
mlavalleahhh, that was my question16:47
slaweqas it happens more times in last few days :)16:47
slaweqchanged16:47
slaweqI guess that there will be no voluneers for that one so I will probably assign it to my self16:48
slaweqbut first I will focus on this bug with functional tests16:48
slaweqfrom other bugs, I found also that we recently hit couple of times old bug https://bugs.launchpad.net/neutron/+bug/179955516:48
openstackLaunchpad bug 1799555 in neutron "Fullstack test neutron.tests.fullstack.test_dhcp_agent.TestDhcpAgentHA.test_reschedule_network_on_new_agent timeout" [Medium,Confirmed]16:48
mlavalleslaweq: if you need help with the dscp one, I can try to help16:49
slaweqmlavalle: that would be great16:49
mlavalleok, I'll take it16:49
njohnstonI can try to help with the dscp one as well, I have some expertise in DSCP :-)16:50
slaweqactally looking at this last one now http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22line%20168,%20in%20test_reschedule_network_on_new_agent%5C%2216:50
slaweqit happens also quite often16:50
mlavallenjohnston: in that case, I'll let you take a stab at it16:50
slaweqso I will also change it to high16:50
* njohnston adds it to my task list16:50
slaweqmlavalle: so maybe You can take a look at https://bugs.launchpad.net/neutron/+bug/1799555 ?16:50
openstackLaunchpad bug 1799555 in neutron "Fullstack test neutron.tests.fullstack.test_dhcp_agent.TestDhcpAgentHA.test_reschedule_network_on_new_agent timeout" [High,Confirmed]16:51
slaweq:)16:51
mlavalleok16:51
slaweqI see at least 7 hits in last 7 days16:51
slaweqthx mlavalle16:51
slaweqok, so to sum up16:51
dougwigslaweq: i filed two new ci unstable bugs this morning, and added elastic rechecks for them.16:51
slaweqnjohnston will take a look at fullstack dscp issue,16:52
njohnston#action njohnston Debug fullstack DSCP issue16:52
slaweqmlavalle: will take a look at fullstack dhcp rescheduling issue16:52
slaweqright?16:52
njohnston+116:52
mlavalle+116:52
slaweqthx16:52
slaweq#action mlavalle to take a look at fullstack dhcp rescheduling issue https://bugs.launchpad.net/neutron/+bug/179955516:52
openstackLaunchpad bug 1799555 in neutron "Fullstack test neutron.tests.fullstack.test_dhcp_agent.TestDhcpAgentHA.test_reschedule_network_on_new_agent timeout" [High,Confirmed]16:52
slaweqdougwig: do You have links to bugs?16:53
dougwigone sec16:53
dougwighttps://bugs.launchpad.net/neutron/+bug/181869616:53
openstackLaunchpad bug 1818696 in neutron "frequent ci failures trying to delete qos port" [Undecided,New]16:53
dougwighttps://bugs.launchpad.net/neutron/+bug/181869716:53
openstackLaunchpad bug 1818697 in neutron "neutron fullstack frequently times out waiting on qos ports" [Undecided,New]16:53
dougwigif either is a dup, i can update the elastic queries.16:53
*** psachin has quit IRC16:54
slaweqit may be that second one is dup of https://bugs.launchpad.net/neutron/+bug/181861316:54
openstackLaunchpad bug 1818613 in neutron "Functional/fullstack qos related tests fails often" [Critical,Confirmed]16:54
slaweqbut one is related to functional tests and second to fullstack16:54
slaweqso I would say, lets keep open both - maybe they will be fixed with same patch16:55
slaweqdo You agree?16:55
dougwigyes.  one is not finding a port, the other is a timeout.  they may be related, but i'm not sure yet.16:55
slaweqdougwig: ok, thx :)16:55
mlavalle+116:56
slaweqok16:56
slaweqok, lets move on quickly16:57
slaweq#topic Tempest/Scenario16:57
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:57
slaweqmlavalle: any updates on on https://bugs.launchpad.net/neutron/+bug/1795870 ?16:57
openstackLaunchpad bug 1795870 in neutron "Trunk scenario test test_trunk_subport_lifecycle fails from time to time" [High,In progress] - Assigned to Miguel Lavalle (minsel)16:57
mlavallethe patches are ok16:57
*** jamesmcarthur has quit IRC16:57
mlavalleI am trying to find the best way to test16:57
slaweqready for review, right?16:57
mlavalleattempt this past Sunday on testing wasn\'t too good16:58
*** macza has joined #openstack-meeting16:58
mlavalleso I need to iterate once more16:59
slaweqok, if You will need any help, ping me :)16:59
mlavalleok16:59
mlavalleI'll probably ping you and dougwig in channel16:59
slaweqI think we are running out of time now16:59
slaweqthx for attending16:59
bcafarelo/16:59
slaweq#endmeeting16:59
njohnstonI have one thing I want to raise; can we continue the discussion on #openstack-neutron?16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:59
openstackMeeting ended Tue Mar  5 16:59:53 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-03-05-16.00.html16:59
slaweqo/16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-03-05-16.00.txt16:59
ralonsohbye16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-03-05-16.00.log.html16:59
slaweqnjohnston: sure17:00
slaweqsorry that it took so long today :)17:00
*** macza_ has joined #openstack-meeting17:04
*** jamesmcarthur has joined #openstack-meeting17:06
*** macza has quit IRC17:08
*** armax has quit IRC17:13
*** mlavalle has left #openstack-meeting17:13
njohnstonall good :-)17:13
*** jamesmcarthur has quit IRC17:14
*** e0ne has quit IRC17:18
*** markvoelker has joined #openstack-meeting17:19
*** yamamoto_ has quit IRC17:22
*** yamamoto has joined #openstack-meeting17:24
*** yamamoto has quit IRC17:24
*** yamamoto has joined #openstack-meeting17:25
*** jamesmcarthur has joined #openstack-meeting17:27
*** yamamoto has quit IRC17:29
*** sridharg has quit IRC17:29
*** aojea has quit IRC17:34
*** sdake has quit IRC17:35
*** artom has quit IRC17:35
*** ttsiouts has quit IRC17:38
*** markvoelker has quit IRC17:51
*** gyee has joined #openstack-meeting17:54
*** raildo has joined #openstack-meeting18:02
*** e0ne has joined #openstack-meeting18:19
*** artom has joined #openstack-meeting18:20
*** njohnston has quit IRC18:24
*** artom has quit IRC18:25
*** ekcs has joined #openstack-meeting18:31
*** mriedem has quit IRC18:37
*** artom has joined #openstack-meeting18:38
*** artom has quit IRC18:39
*** mriedem has joined #openstack-meeting18:39
*** artom has joined #openstack-meeting18:39
*** markvoelker has joined #openstack-meeting18:48
*** jamesmcarthur has quit IRC18:52
*** yamamoto has joined #openstack-meeting18:55
*** awaugama has quit IRC18:57
clarkbAnyone else here for the Infra meeting? We'll get started shortly18:59
cmurphyo/19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Mar  5 19:01:05 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-March/006291.html19:01
*** Shrews has joined #openstack-meeting19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbThe OpenStack TC election is happening right now. Those of you that have contributed to the infra project in the last year or so should have received a personal ballot in your email inbox. You have until 23:45UTC today to vote if you haven't yet19:02
*** electrofelix has quit IRC19:02
clarkb#link https://docs.openstack.org/infra/system-config/signing.html#attestation sign the Train release key19:03
fungi#link https://sks-keyservers.net/pks/lookup?op=vindex&search=0xcdc08088c3cb45a9be08332b2354069e5b504663&fingerprint=on OpenStack Infra (Train Cycle) artifact signing key19:03
clarkbfungi has set up a train release gpg key (thank you!) and those of us with root access should follow the steps in the link above to sign it19:03
clarkbThat is on my todo list for post meeting so hopefully I'll get that done soon. Something to do while waiting for afs to replicate a not small volume :)19:04
clarkb#link https://www.openstack.org/summit/denver-2019/call-for-presentations Submit Forum session ideas now19:04
diablo_rojoo/19:04
clarkbIt is also that time of year where we plan to get together and talk about designing software/services19:04
clarkbIf you've got topics for that feel free to submit them19:04
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-02-26-19.01.txt minutes from last meeting19:06
clarkbI set an everyone action to sign up for gitea story tasks. I think that has gone reasonably well and we are making progress on the gitea front19:06
corvusyep, all tasks accounted for19:07
clarkbLets bring that up during opendev discussion though19:07
clarkbcorvus: yay19:07
clarkb#topic Specs Approval19:07
*** openstack changes topic to "Specs Approval (Meeting topic: infra)"19:07
clarkbWe also merged the letsencrypt spec after reviews last week. THank you everyone for that19:07
*** yamamoto has quit IRC19:07
clarkbMostly just mentioning it here in case you missed it.19:08
clarkb#topic Priority Efforts19:08
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:08
clarkb#topic Storyboard19:08
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:08
clarkbI ran through running storyboard tests locally and pushed an update to the storyboard docs that appear to have merged19:09
diablo_rojoBeen slowly getting SotK's attachment patches through19:09
diablo_rojoAlso still being innundated with prospective outreachy interns19:09
clarkbI did that in support of making it easier for outreachy applicants. Hopefully they find it useful19:09
fungiyeah, mordred added an alternative solution relying on swift tempurls which will hopefully solve one of the security risks we missed with the previous client auth idea19:10
clarkbcool sounds like good progress on the attachments implementation then19:10
mordredfungi: oh - crappit - I need to finish that / follow up on those patches19:10
mordredfungi: thanks for the reminder19:11
clarkbfor outreachy are there specific tasks/deadlines we should be aware of as a "hosting project" (I don't know what the actual term is)19:11
*** awaugama has joined #openstack-meeting19:11
fungithe outreachy hopefuls are also burning through our new-contributor-friendly stories at am amazing pace19:11
mordred(fwiw, I've been saying "tempurl" when I mean "formsubmit" - but yes)19:11
diablo_rojoI think the application proposals for interns closes soon.19:11
fungioh, thanks for the clarification mordred19:11
diablo_rojoNot sure what day we need to pick an intern by though19:11
diablo_rojofungi, yeah that has been amazing19:12
fungioh, related to interns but not outreachy, hogepodge also has some capstone interns from ndsu he's sticking on some storyboard todo items as well19:12
diablo_rojoI guess I will need to go triage some more soon19:12
diablo_rojoOh yeah19:12
diablo_rojospecifically amending the migration script to handle bps as well19:12
diablo_rojooptionally19:12
fungiright, we've had a few teams request lp blueprints be migrated to stories19:12
diablo_rojoSo we could migrate bps and bugs, or just one or the other19:12
clarkbdiablo_rojo: we probably want to do a review pass of those changes as part of the application process? (and when I say we I really mean people that know storyboard)19:13
mordreddiablo_rojo: maybe after meeting let's sync on a plan for the formsubmit swift stuff19:13
diablo_rojomordred, sounds good19:14
diablo_rojoSotK, should probably be around too for that19:14
clarkbAre there other topics we should cover that aren't outreachy and the attachments implementation?19:14
diablo_rojoclarkb, yeah I have reviewed a few so far, but there are more to do if anyone can help out.19:14
diablo_rojoPlacement will be using sb? Yay!19:15
clarkbdiablo_rojo: maybe we can tag them all with an outreachy topic?19:15
clarkbdiablo_rojo: that might help reviewers? not sure how difficult it is to sort them out from the other work19:15
diablo_rojoclarkb, oh yeah thats a good call. I can go and do that19:15
clarkbgreat thanks19:15
fungiyeah, the last placement meeting talked about sb some, but ended in cdent's e-mail to the openstack-discuss ml19:15
fungiso probably doesn't need separate summarizing19:15
clarkbok lets move on then19:16
clarkb#topic Update Config Management19:17
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:17
clarkbWe are ready to start deploying puppet 4 in places. https://review.openstack.org/#/c/630391/ Does that for our dev servers but was updated to fix an issue frickler caught before I could approve it19:17
clarkbrereviews very welcome and I'm happy to approve that and watch it19:17
cmurphyyay19:17
*** e0ne has quit IRC19:17
clarkbWe continue to refine the docker-compose to deploy docker images with ansible process/tooling19:18
clarkbwe are running 4 services with that now?19:18
clarkbcorvus: ^ you probably know off the top of your head19:18
corvusgitea, haproxy, registry, preview19:19
clarkbAlso my changes to add a zuulcd user to bridge are merged so I think we can start with Zuul triggering CD jobs again19:19
clarkbI guess so far just one chagne and we need to have a discussion about auto updating key data19:19
clarkbbut that is sufficient for now if we want to start splitting out config management runs from the always run every 15 minutes to run when necessary19:20
corvusi think we might be able to pull the git playbook out of base and run it on changes to projects.yaml19:20
clarkbzuul-preview deployments likely another good candidate for that (run when zuul-preview updates)19:20
fungii also added some suggestions on the authorized_keys retrieval change19:20
corvusyep, we can chain it to follow the promote job19:20
*** jamesmcarthur has joined #openstack-meeting19:21
clarkbfungi: thanks I'll take a look today19:21
fungias a side note there, is there a reason we can't have it retrieve keys from zuul.opendev.org instead of zuul.openstack.org? i think that solves several of my concerns19:21
*** markvoelker has quit IRC19:21
corvusfungi: we absolutely can.  it was just written before it existed19:22
clarkbyup that19:22
fungicool, i thought (hoped) that might be the case19:22
clarkbif that will alleviate concern I'll go ahead and make that update19:22
fungii was having trouble putting together a working api url to do that yesterday but that was probably just my fault19:22
*** awaugama has quit IRC19:22
fungiclarkb: the other remaining concern will be easier to take care of later with letsencrypt19:22
fungiand is something we might want to consider doing for all our opendev le certs19:23
*** awaugama has joined #openstack-meeting19:23
fungithough i'm not 100% sure the python requests module supports it (yet)19:23
clarkbok I'll take a look today19:24
*** jamesmcarthur_ has joined #openstack-meeting19:24
clarkbAre there other config management related changes/items that we want to go over before we zoom in on opendev/gitea?19:24
*** jamesmcarthur has quit IRC19:25
funginone for which i'm aware19:25
*** vishakha has quit IRC19:25
clarkb#topic OpenDev19:25
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:25
corvus#link https://storyboard.openstack.org/#!/story/2004627 opendev tasks19:25
*** armax has joined #openstack-meeting19:26
corvussince last week, we're basically halfway done with the tasks needed before we are ready to actually move19:26
clarkbWe now have 8 gitea servers running behind haproxy hosting https://opendev.org19:26
corvusi think the most urgent thing is actually a new task not on there, which is to fix the default branch setting for the projects we're replicating now as well as new projects19:26
corvusmordred is working on that, with, presumably, clarkb and i helping19:27
clarkbyup I'm happy to help on that19:27
corvusonce replication is done and looks correct, i plan on starting on the last task on the list, which is the announcement email19:27
corvusi want to get that out as early as possible so folks know the plan and openstack and starlingx can make any preparations for repo moves19:28
clarkb++19:28
fungisounds great19:28
corvusbut i also want to wait until we have a fully-functioning site to demo in the email19:28
fungii've just updated the story to include previously missed airship domain name19:28
corvusmeanwhile, we can work on the rest of the preparatory tasks19:28
corvusfungi: thx :)19:29
clarkbis anyone stuck or needing help on any of their tasks?19:29
fungii just need to carve out time to knock mine out. shouldn't take long19:30
ianwI'll go through devstack plugins looking for git://'s19:30
fricklerthe issues and release tabs don't look correct for some projects, do we have a plan for that?19:31
fricklerissues always redirect to sb19:31
*** ttsiouts has joined #openstack-meeting19:31
ianwcorvus: is there a plan for port 9418 in the interim, to maybe forward to a proxy or something?19:31
clarkbfrickler: the issue there being we should link to launchpad in some cases?19:31
corvusianw: no, it's not possible to support19:31
clarkbfrickler: we should be able to fix that by looking up if a project uses storyboard or not in the project.yaml yaml file I expect. Then run the fixup playbook across all the projects once we haev that logic in place19:32
clarkbfrickler: probably worth a new task to track that though19:32
fricklerand releases look incomplete, compare https://opendev.org/openstack/designate/releases to https://github.com/openstack/designate/releases19:32
mordredyeah.19:32
mordredwell - the releases tab is a thing we probably need to think about - maybe we should remove it from the ui for now until we have a good plan for it19:33
clarkbfrickler: looking at that almost appears to be a gitea bug?19:33
clarkbthe tags are available on the code screen at least19:33
corvuscan someone tell me what the bug is?19:33
*** sdake has joined #openstack-meeting19:33
clarkbcorvus: only the rc releases seem to be listed19:33
corvusah19:34
clarkbwell rc and beta. None of the actual releases are listed19:34
mordredwell - the bug for ME is that I don't want us hosting links to things people shouldn't ever download19:34
corvusmordred: yeah, i think you were... that. yes.19:34
fricklerits not consistent it seems, but e.g. for designate 7.0.0 seems to be missing19:34
corvusso let's just drop the releases page19:34
mordredyeah19:34
mordredI think it could be a nice thing to do something with at some point to have releases point to our actual releases19:34
corvusi'll make new tasks for all of these things19:34
clarkbmordred: the concern being the tarball there isn't a valid python sdist? I agree that is a proble mand removing the tab would be good19:34
fungimakes sense to me19:34
mordredbut that's more work19:34
mordredclarkb: yes. that is the problem19:34
mordredsame bug as github's ui has - a git export isn't always a valid source tarball19:34
clarkbthis is good feedback and godo for us to catch these things before we announce it more widely :)19:35
corvusyep :)19:36
clarkbAnything else opendev or gitea related? If not we'll move on to our general topics list19:36
corvusstory updated with 3 new tasks, 2 of which are unassigned19:36
*** e0ne has joined #openstack-meeting19:37
corvusclarkb: none from me19:37
clarkb#topic General Topics19:38
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:38
clarkb#link https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup Trusty Server Upgrades19:38
clarkbThis is mostly a status update and thank you to those helping with this19:38
clarkbI've written down an afs fileserver upgrade plan on that etherpad (and am currently executing step 1)19:38
clarkbif you have a chance to review that the input I've received so far has been helpful19:39
clarkbAnd once again if you are able to upgrade a server or two please volunteer.19:39
clarkbAs for sprinting on this I haven't heard any responses to my email about that19:39
clarkbFor my schedule March 11 and 12 work best (next monday and tuesday)19:39
clarkbso I'm probably going to go ahead and scribble that in as the sprint days and I'll see you there if you can make it?19:40
clarkbNext up is ianw's backups topic19:40
clarkbianw seems we have some cleanup to do on the backup erver?19:41
ianwthe main problem is : /dev/mapper/main-backups            3.0T  2.8T  579M 100% /opt/backups19:41
ianwnow we have 3tb in "old" volumes, which we decided to clean up "in a few months" @ http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-10-31-19.01.log.html#l-18919:42
clarkbianw: I would be on board with cleaning that up by deleting the contents of those volumes, but then repurposing the voluming as the target for new backups19:43
clarkbthen we can do similar cleanup with the current volumes in the future?19:43
ianwi actually had a thought that we document our process here as periodically keeping the old volume, and swapping19:43
clarkbianw: ++19:43
ianwclarkb: cool, i think we said the same thing :)19:43
clarkbsince bup is append only having a formal rotation process would be good19:43
corvusi like it19:43
clarkbianw: is this something you'll be able to drive? or do we need volunteer(s)?19:44
ianwclarkb: i can take an action item to do that19:44
clarkb#action ianw rotate backup volumes on backup server19:44
clarkbianw: thanks19:44
ianwyeah, i didn't know if we wanted to investigate some sort of automated pruning19:45
clarkbNot to completely derail, but at times I wonder if borgbackup would be helpful here. I've been using it for personal backups and my understanding is it can do append only backups with pruning19:45
fungii wonder if we could abuse logrotate to do it19:45
ianwpersonally, i feel like some custom script has a non-trivial chance of wiping out much more than it intends19:45
clarkbI don't think you can prune bup backups19:46
clarkbat least not in bup itself19:46
ianwno, but we could do some sort of automated repo moving type thing19:46
fungiyeah, i guess rotating with retention means losing deduplication of the rotated copy19:46
clarkbianw: ya we could move the dest repo out of the way and replace it with a new empty target19:47
clarkbthen after X time delete the moved repo19:47
ianwit's probably spec worthy, maybe the whole backups process could do with a re-look in the opendev world19:47
clarkb++19:47
corvuswell, pruning with bup is experimental19:47
clarkbcorvus: ah19:47
ianwanyway, i won't sign up to take on a full overhaul :)  but just flagging it for now19:47
clarkbianw: ya the earlier fix should give us breathing room to think it through19:47
ianwthe other quick thing i noticed was we're not backing up stats on graphite.opendev.org (previously openstack.org)19:48
clarkbfwiw I'm likely to suggest borgbackup if we intend to do a big overhaul as I've really enjoyed working with it. You can fuse mount a backup to copy files and it encrypts at the source so you don't have to trust your remote :)19:48
ianwnot sure if that is a bug or feature19:48
corvusi don't think we need to back up stats19:49
clarkbianw: I'm not sure how important it is to backup that data19:49
clarkbits nice to have data that we can live without19:49
ianwok, if it's a feature, that's cool :)19:49
corvusi agree with every one of the possible ways of reading clarkb's sentence :)19:49
corvus(it's nice to have (data that we can live without)) and (it's (nice to have) data that (we can live without))19:50
clarkb:)19:50
clarkbAnything else backup related?19:50
ianwno, that's it for me19:51
clarkb#topic Open Discussion19:51
*** openstack changes topic to "Open Discussion (Meeting topic: infra)"19:51
clarkbI'm going to be in Seattle on the 19th but I should arrive early enough and be settled enough to run our meeting (especially with DST change this weekend). However the week after that (26th) we are doing a mini road trip for spring break back to the seattle area and I will likely be afk19:52
clarkbif anyone really wants to run the meeting in 3 weeks let me know19:52
ianwi have no other plans, so can do that if nobody else wants to19:53
clarkbAlso DST change in the USA (and maybe canada?) is this weekend apparently19:53
fricklerone other thing regarding gitea: can we clean up the exim paniclogs to reduce the amount of daily mails?19:53
clarkbThis means that our meeting will happen an hour later in the day that it happened today for those of you in the usa19:54
fungifrickler: i think it's a more general bootstrapping problem. we might want to wipe the exim paniclog if present at the end of launch-node.py19:54
fricklerclarkb: so the meeting won't stay at 19:00 UTC?19:55
clarkbfrickler: oh sorry it stays at 1900UTC19:55
fungipretty much every new server we've launched has a paniclog from (it appears) when exim configuraiton was first getting applied19:55
clarkbIt is an hour later in the day relative to my local timezone19:55
fricklerah, I read it the wrong way around19:55
clarkbfrickler: sorry I wasn't very clear on that. For pacific time meeting was at 11am today will be Noon next week19:55
fungicrazy folk like me who set their clocks to utc don't need to worry ;)19:56
fungiinstead i get to deal with fixing the offset on all the non-community meetings in my remind file19:56
corvusmy irc client's clock is utc19:56
mordredmy irc client's clock is utc - and I put the infra meeting into my calendar using the iceland timezone so it just works :)19:57
fungii probably should tag the recurring meetings in my remind file which *don't* follow utc and then just script their time changes accordingly19:57
fricklerthe EU might be stopping switching time zone soon ... maybe19:58
clarkbhttps://review.openstack.org/#/c/639454/ is an example of a chagne that does post launch launch tasks19:58
clarkbif anyone wants to do the cleanup exim paniclog change ^ is a good place to start probably19:58
corvusi also voted to recommend that my state legislature consider beginning a process to investigate putting together a proposal to petition the us commerce department to allow us to stop switching between pst/pdt19:58
fungiclarkb: thanks, we can probably just tack on a `rm -rf /var/log/exim4/paniclog` and call it a day19:58
corvusso i'm *very* proactive on this issue.19:58
clarkbcorvus: nice19:58
clarkboregon has a bill that gets rejected every year to ditch dst (or go to dst fulltime)19:59
clarkbAnd we are just about at time. Thank you everyone19:59
clarkb#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:59
openstackMeeting ended Tue Mar  5 19:59:19 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-03-05-19.01.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-03-05-19.01.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-03-05-19.01.log.html19:59
fungicorvus: there was a state referendum for that? would never happen in nc19:59
corvusfungi: yes, and it passed19:59
corvushttps://www.theguardian.com/us-news/2018/nov/09/california-permanent-daylight-saving-time-vote-prop-720:00
fungineat!20:00
*** Shrews has left #openstack-meeting20:01
corvusbut apparently, since it's a permanent dst (versus permanent standard), it needs to go through the state legislature and something about the feds.20:01
fungitoo bad they couldn't have just chosen to go with permanent pst20:02
lifelessyah20:04
lifelessputs me further out from silicon valley :(20:05
*** raildo has quit IRC20:09
*** shilpasd has quit IRC20:09
*** ttsiouts has quit IRC20:11
*** ttsiouts has joined #openstack-meeting20:11
*** eharney has quit IRC20:12
*** ttsiouts has quit IRC20:15
*** sdake has quit IRC20:17
*** sdake has joined #openstack-meeting20:19
*** markvoelker has joined #openstack-meeting20:19
*** whoami-rajat has quit IRC20:22
*** igordc has joined #openstack-meeting20:28
*** ralonsoh has quit IRC20:29
*** awaugama has quit IRC20:30
*** ttsiouts has joined #openstack-meeting20:32
*** rbudden has joined #openstack-meeting20:50
*** markvoelker has quit IRC20:52
*** jamesmcarthur has joined #openstack-meeting20:57
*** janders has joined #openstack-meeting20:58
*** jamesmcarthur_ has quit IRC21:00
*** eharney has joined #openstack-meeting21:03
*** artom has quit IRC21:08
*** pcaruana has quit IRC21:10
jandersoneswig, bla1ro, martial: is there anybody out there?21:11
rbuddeni was beginning to think I had my weeks mixed up21:11
jandersI think you're all good - just everyone got busy with other stuff21:12
*** e0ne has quit IRC21:13
*** janders has quit IRC21:19
*** e0ne has joined #openstack-meeting21:26
*** janki has quit IRC21:29
*** jmlowe has joined #openstack-meeting21:29
*** e0ne has quit IRC21:30
*** bbowen has quit IRC21:42
*** mjturek has quit IRC21:43
*** jakeyip has joined #openstack-meeting21:44
*** markvoelker has joined #openstack-meeting21:49
*** priteau has quit IRC22:01
*** carlos_silva has quit IRC22:03
*** eharney has quit IRC22:14
*** markvoelker has quit IRC22:22
*** erlon has quit IRC22:25
*** sdake has quit IRC22:28
*** mmethot has quit IRC22:34
*** sdake has joined #openstack-meeting22:38
*** jamesmcarthur has quit IRC22:41
*** sdake has quit IRC22:45
*** sdake has joined #openstack-meeting22:51
*** munimeha1 has quit IRC22:52
*** jamesmcarthur has joined #openstack-meeting22:57
*** jamesmcarthur has quit IRC22:58
*** jamesmcarthur has joined #openstack-meeting22:58
*** iyamahat has joined #openstack-meeting22:58
*** sdake has quit IRC23:02
*** yamamoto has joined #openstack-meeting23:05
*** iyamahat has quit IRC23:08
*** yamamoto has quit IRC23:10
*** igordc has quit IRC23:10
*** bbowen has joined #openstack-meeting23:15
*** markvoelker has joined #openstack-meeting23:19
*** sdake has joined #openstack-meeting23:33
*** ekcs has quit IRC23:34
*** jamesmcarthur has quit IRC23:37
*** jamesmcarthur has joined #openstack-meeting23:38
*** jamesmcarthur has quit IRC23:40
*** markvoelker has quit IRC23:52

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