Thursday, 2019-01-24

*** yamamoto has quit IRC00:03
*** macza has quit IRC00:13
*** tetsuro has joined #openstack-meeting-alt00:19
*** hongbin has quit IRC00:22
*** TxGirlGeek has quit IRC00:29
*** TxGirlGeek has joined #openstack-meeting-alt00:40
*** dklyle has quit IRC00:42
*** igordc has quit IRC00:51
*** tetsuro has quit IRC01:29
*** TxGirlGeek has quit IRC01:39
*** whoami-rajat has joined #openstack-meeting-alt01:53
*** hongbin has joined #openstack-meeting-alt02:08
*** bhavikdbavishi has joined #openstack-meeting-alt02:09
*** hongbin_ has joined #openstack-meeting-alt02:35
*** bhavikdbavishi has quit IRC02:37
*** hongbin has quit IRC02:38
*** iyamahat has quit IRC02:50
*** yamahata has quit IRC02:51
*** yamamoto has joined #openstack-meeting-alt02:59
*** dklyle has joined #openstack-meeting-alt03:07
*** tetsuro has joined #openstack-meeting-alt03:10
*** tetsuro has quit IRC03:12
*** apetrich has quit IRC03:15
*** dklyle has quit IRC03:21
*** baojg has quit IRC03:24
*** bhavikdbavishi has joined #openstack-meeting-alt03:27
*** bhavikdbavishi has quit IRC03:31
*** bhavikdbavishi has joined #openstack-meeting-alt03:35
*** baojg has joined #openstack-meeting-alt03:43
*** tetsuro has joined #openstack-meeting-alt03:57
*** tetsuro has quit IRC03:57
*** dklyle has joined #openstack-meeting-alt04:20
*** irclogbot_1 has quit IRC04:35
*** hongbin_ has quit IRC04:35
*** hongbin has joined #openstack-meeting-alt04:35
*** ijw has quit IRC04:37
*** hongbin has quit IRC04:40
*** yamahata has joined #openstack-meeting-alt04:44
*** lbragstad has quit IRC04:57
*** gyee has quit IRC05:01
*** sridharg has joined #openstack-meeting-alt05:02
*** baojg has quit IRC05:02
*** e0ne has joined #openstack-meeting-alt05:03
*** e0ne has quit IRC05:03
*** baojg has joined #openstack-meeting-alt05:04
*** baojg has quit IRC05:04
*** baojg has joined #openstack-meeting-alt05:05
*** vishalmanchanda has joined #openstack-meeting-alt05:44
*** jbadiapa has joined #openstack-meeting-alt06:13
*** markvoelker has joined #openstack-meeting-alt06:16
*** ccamacho has quit IRC06:26
*** markvoelker has quit IRC06:45
*** ccamacho has joined #openstack-meeting-alt07:12
*** apetrich has joined #openstack-meeting-alt07:12
*** baojg has quit IRC07:15
*** baojg has joined #openstack-meeting-alt07:16
*** baojg has quit IRC07:16
*** baojg has joined #openstack-meeting-alt07:17
*** tetsuro has joined #openstack-meeting-alt07:18
*** kopecmartin|off is now known as kopecmartin07:19
*** tetsuro has quit IRC07:19
*** baojg has quit IRC07:25
*** baojg has joined #openstack-meeting-alt07:25
*** e0ne has joined #openstack-meeting-alt07:35
*** markvoelker has joined #openstack-meeting-alt07:42
*** ttsiouts has joined #openstack-meeting-alt08:14
*** ttsiouts has quit IRC08:14
*** markvoelker has quit IRC08:15
*** ttsiouts has joined #openstack-meeting-alt08:28
*** rcernin has quit IRC08:29
*** yamamoto has quit IRC08:42
*** baojg has quit IRC08:43
*** baojg has joined #openstack-meeting-alt08:45
*** ttsiouts has quit IRC08:46
*** ttsiouts has joined #openstack-meeting-alt08:47
*** ttsiouts has quit IRC08:51
*** yamamoto has joined #openstack-meeting-alt08:54
*** ianychoi has quit IRC08:55
*** iyamahat has joined #openstack-meeting-alt08:56
*** ttsiouts has joined #openstack-meeting-alt09:21
*** derekh has joined #openstack-meeting-alt09:29
*** ttsiouts has quit IRC09:32
*** ttsiouts has joined #openstack-meeting-alt09:32
*** ttsiouts has quit IRC09:36
*** e0ne has quit IRC09:41
*** ttsiouts has joined #openstack-meeting-alt09:43
*** tssurya has joined #openstack-meeting-alt09:51
*** erlon_ has joined #openstack-meeting-alt09:52
*** jrbalderrama has joined #openstack-meeting-alt09:55
*** e0ne has joined #openstack-meeting-alt09:56
*** masahito has joined #openstack-meeting-alt10:04
*** tssurya has quit IRC10:05
*** tssurya has joined #openstack-meeting-alt10:06
*** masahito has quit IRC10:09
*** markvoelker has joined #openstack-meeting-alt10:12
*** bhavikdbavishi has quit IRC10:22
*** helenafm has joined #openstack-meeting-alt10:41
*** markvoelker has quit IRC10:46
*** ttsiouts has quit IRC11:15
*** ttsiouts has joined #openstack-meeting-alt11:16
*** ttsiouts has quit IRC11:20
*** bhavikdbavishi has joined #openstack-meeting-alt11:36
*** markvoelker has joined #openstack-meeting-alt11:43
*** ttsiouts has joined #openstack-meeting-alt11:56
*** markvoelker has quit IRC12:16
*** panda is now known as panda|lunch12:17
*** jesusaur has quit IRC12:48
*** panda|lunch is now known as panda12:55
*** e0ne has quit IRC12:59
*** bhavikdbavishi has quit IRC12:59
*** bhavikdbavishi has joined #openstack-meeting-alt13:00
*** armstrong has joined #openstack-meeting-alt13:01
*** yamamoto has quit IRC13:09
*** markvoelker has joined #openstack-meeting-alt13:13
*** e0ne has joined #openstack-meeting-alt13:20
*** markvoelker has quit IRC13:23
*** markvoelker has joined #openstack-meeting-alt13:23
*** derekh has quit IRC13:26
*** baojg has quit IRC13:28
*** ttsiouts has quit IRC13:35
*** ttsiouts has joined #openstack-meeting-alt13:35
*** liuyulong has joined #openstack-meeting-alt13:38
*** ttsiouts has quit IRC13:39
*** ttsiouts has joined #openstack-meeting-alt13:39
*** yamamoto has joined #openstack-meeting-alt13:40
*** lujinluo has joined #openstack-meeting-alt13:43
*** jrbalderrama has quit IRC13:56
*** derekh has joined #openstack-meeting-alt13:58
*** jcoufal has joined #openstack-meeting-alt13:59
lujinluo#startmeeting neutron_upgrades14:00
openstackMeeting started Thu Jan 24 14:00:30 2019 UTC and is due to finish in 60 minutes.  The chair is lujinluo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_upgrades)"14:00
openstackThe meeting name has been set to 'neutron_upgrades'14:00
*** ttsiouts has quit IRC14:01
lujinluoThis would be the first meeting we start in a new channel! But honestly I am not sure how many of my team mates would join today, so I will wait for a few minutes14:01
*** ttsiouts has joined #openstack-meeting-alt14:01
lujinluoIf no one showed up, I will just briefly list the patches ready for review, just in case people come back and read logs14:02
*** helenafm has left #openstack-meeting-alt14:02
lujinluo#topic OVO14:02
*** openstack changes topic to "OVO (Meeting topic: neutron_upgrades)"14:02
lujinluo#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db14:02
lujinluo^ these are the patches open for review now14:03
lujinluoand among them, #link https://review.openstack.org/#/c/544206/ port binding OVO is ready14:03
lujinluoothers need more work14:03
*** njohnston has joined #openstack-meeting-alt14:04
njohnstonsorry I am late14:04
lujinluohi njohnston ! no problem at all14:04
lujinluoso I am go through the patches we have now14:04
lujinluo#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db14:04
*** jrbalderrama has joined #openstack-meeting-alt14:04
lujinluoNo many updates recently and I apologies for that :(14:05
njohnstonI'm just as much to blame :-)14:05
*** ttsiouts has quit IRC14:05
lujinluoI am looking at your #link https://review.openstack.org/#/c/624815/ patch though14:06
lujinluorecently, and I am thinking about your email14:06
lujinluoI have not come to a final decision, but for now, i think we may not want to use port OVO in those registries14:06
lujinluoregistry calls, i mean14:07
lujinluothe main concern i have is if we use them in those calls, will it affect other ML2 plugins? I happened to write some codes for networking-fujitsu, which receives the pre_commit notifications from Neutron and run its own switch command accordingly14:09
*** ttsiouts has joined #openstack-meeting-alt14:09
njohnstonHmm, the data should be converted to a dict before it is sent to the registry using _make_port_dict14:10
njohnstonI was hoping that would be sufficient to maintain compatibility14:10
*** yamamoto has quit IRC14:11
lujinluoi see. if so, i guess my current concern would be resolved14:11
lujinluoi will look more into the related codes and get back to you soon!14:12
njohnstonthank you!14:13
lujinluoalso, it would be really appreciated if you could review #link https://review.openstack.org/#/c/544206/ when you are available :-)14:13
*** yamamoto has joined #openstack-meeting-alt14:13
*** yamamoto has quit IRC14:13
njohnstonI will definitely take a look at it!14:13
lujinluodo you have any specific patch you want to discuss in the list here? #link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/adopt-oslo-versioned-objects-for-db14:14
lujinluothank you!14:14
*** e0ne has quit IRC14:14
njohnstonNo, https://review.openstack.org/#/c/624815/ is consuming my world as I start feeling like I need to change more and more plumbing :-(14:14
lujinluounderstood, hopefully we can get it in a good shape soon!14:15
njohnstonI am hoping I will conquer it and be released to other things soon14:15
*** yamamoto has joined #openstack-meeting-alt14:15
lujinluo:-) that will happen, and all we need is time haha14:15
lujinluothen let's wrap it up earlier today and do more hacking this week!14:16
njohnstonthanks!14:16
lujinluothank you! njohnston14:16
lujinluohave a good day!14:16
njohnstonthank you as always lujinluo14:16
lujinluo:)14:16
lujinluo#endmeeting14:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:16
openstackMeeting ended Thu Jan 24 14:16:54 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2019/neutron_upgrades.2019-01-24-14.00.html14:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2019/neutron_upgrades.2019-01-24-14.00.txt14:16
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2019/neutron_upgrades.2019-01-24-14.00.log.html14:17
*** yamamoto has quit IRC14:20
*** lbragstad has joined #openstack-meeting-alt14:20
*** helenafm has joined #openstack-meeting-alt14:25
*** baojg has joined #openstack-meeting-alt14:31
*** ccamacho has quit IRC14:32
*** helenafm has left #openstack-meeting-alt14:34
*** e0ne has joined #openstack-meeting-alt14:34
*** ccamacho has joined #openstack-meeting-alt14:35
*** carthaca has joined #openstack-meeting-alt14:38
*** lujinluo has quit IRC14:39
*** lujinluo has joined #openstack-meeting-alt14:40
*** lujinluo has quit IRC14:45
*** jgrosso has joined #openstack-meeting-alt14:51
*** ganso has joined #openstack-meeting-alt14:56
*** hongbin has joined #openstack-meeting-alt14:58
*** jrbalderrama has quit IRC14:59
*** jrbalderrama has joined #openstack-meeting-alt15:00
tbarron#startmeeting manila15:00
openstackMeeting started Thu Jan 24 15:00:39 2019 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: manila)"15:00
openstackThe meeting name has been set to 'manila'15:00
vkmco/15:00
tbarronping ganso15:00
tbarronping xyang15:00
tbarronvkmc hi15:00
tbarronping gouthamr15:01
toabctlo/15:01
tbarronping jgrosso15:01
tbarronhi toabctl15:01
jgrossohi tbarron15:01
tbarronping bswartz15:01
tbarronping erlon15:01
tbarronpint tpsilva :)15:01
tbarronping amito15:01
tbarronif anyone else wants to be added to the ping list you can do it yourself at https://wiki.openstack.org/w/index.php?title=Manila/Meetings&action=edit&section=115:02
tbarronoe AK MW RO SO IR15:02
tbarron:)15:02
tbarronor ask me to do it15:02
xyanghi15:02
tbarronthat was rot something on querty with caps :)15:02
tbarronhi xyang15:02
gansohello15:03
tbarronlet's wait a couple more minutes15:03
gouthamro/15:03
tbarronhi gouthamr15:03
gouthamrhi tbarron!15:04
* tbarron wonders if bswartz is around15:04
tbarronOK, we've got quorum, let's start.15:04
tbarronhi everyone!15:04
tbarron#topic agenda15:05
*** openstack changes topic to "agenda (Meeting topic: manila)"15:05
tbarron#link https://wiki.openstack.org/wiki/Manila/Meetings15:05
*** carlos_silva has joined #openstack-meeting-alt15:05
tbarronif you update it give me a nudge so i can refresh my browser15:05
tbarron#topic announcements15:05
*** openstack changes topic to "announcements (Meeting topic: manila)"15:05
tbarronI don't have any.  Anyone else?15:05
tbarronok, hearing none ...15:06
tbarronwe've got a fair number of topics but let's try to move right along, i want to have time for the bugs topic15:06
tbarron#topic scheduler speedup15:06
*** openstack changes topic to "scheduler speedup (Meeting topic: manila)"15:06
tbarron#link https://review.openstack.org/#/c/619576/15:07
tbarroncarthaca: you around?15:07
gansothere is something wrong with the numbering on the agenda15:07
tbarronganso, yeah I see that now :)15:07
tbarronWe'll go top to bottom and I'll fix it after unless you want to do it now :)15:08
tbarronfeel free15:08
tbarronSo review 619576 has two plus 2s but it touches some important code so I haven't workflowed it yet15:09
tbarronI plan to do that tomorrow if there aren't any downvotes15:09
gansotbarron: done15:09
tbarronPlease take a look if you care about the manila scheduler15:09
tbarronganso: ty15:09
tbarron#topic AZ work15:10
*** openstack changes topic to "AZ work (Meeting topic: manila)"15:10
gouthamrack, was looking if we can automate testing it somehow15:10
tbarronThere are three patches listed in the agenda15:11
tbarronThey are pretty significant -- exercise AZs in a way we haven't done before15:11
tbarronWe agreed in principle to the approach at spec time and I think it makes sense.15:11
tbarronBut expect that there may be some fallout.15:12
tbarronThird party folks please look as well.15:12
tbarrongouthamr: do you have something you want to share on these?15:12
gouthamrty tbarron15:12
gouthamryes, one more set of patches is due: Share type AZ support - i'm still working on the tests for these15:13
gouthamrbut the others listed:15:13
gouthamr#LINK: https://review.openstack.org/#/c/629958/15:13
gouthamr#LINK: https://review.openstack.org/#/c/630886/15:13
gouthamr#LINK: https://review.openstack.org/#/c/630039/15:13
gouthamrare complete and needy for attention, thanks for teh reviews tbarron toabctl15:13
toabctlonly the last one is not merged yet15:13
toabctlI already workflowed 629958 and 630886 and both are already merged.15:14
gouthamrooh, thanks!15:14
tbarroni think we can merge them but want people to be aware of the changes in case there's any unanticipated fallout we need to repair15:14
gouthamr++15:15
toabctlyeah. sure.15:15
tbarronit's hard to test all this fully I think15:15
tbarronlike what happens to netapp replication15:15
gouthamrall third party CIs that use: ENABLED_BACKENDS should automatically have an AZ assigned to each of their enabled backends15:15
tbarronetc15:15
tbarronso heads up15:15
toabctland imo https://review.openstack.org/#/c/630039/ can be merged, too. just somebody needs to press the workflow button :)15:16
tbarronIt's good stuff, just have your eyes open.15:16
tbarrontoabctl: yup15:16
tbarronOK, anything else on this topic?15:16
gouthamryes15:16
gouthamrwhile we're here, please help by reviewing15:17
gouthamr#LINK: https://review.openstack.org/#/q/topic:bp/export-locations-az+(status:open+OR+status:merged)15:17
gouthamr:)15:17
gouthamrthat's trying to introduce new experimental APIs and clean up the export locations API a bit15:17
tbarrongouthamr: plug ....15:17
gouthamr:D15:17
tbarrongouthamr: thanks for your work in this important area and toabctl thanks for your quality reviews.15:18
tbarron#topic pylint15:18
*** openstack changes topic to "pylint (Meeting topic: manila)"15:18
tbarronganso you're up15:18
gansookay15:18
gansothanks15:18
gansoso, I am not sure if everyone has noticed, but lately our pylint job has been broken15:19
gansohere is one example: #LINK http://logs.openstack.org/58/629958/2/check/openstack-tox-pylint/d3056f6/job-output.txt.gz#_2019-01-23_19_20_57_40344215:19
gansohold on I am trying to get the gerrit link for the patch that broke it15:20
tbarronSo we used to run with a very old version of pylint but had a "ratchet" - the job only failed if there were *new* pylint warnings introduced by your patch15:20
gansothere we go https://review.openstack.org/#/c/609791/15:20
ganso#LINK https://review.openstack.org/#/c/609791/15:20
tbarronwe ported over changes from cinder to support newer pyling15:20
tbarronpylint15:20
tbarronand there's no longer a "ratchet"15:21
tbarronthe (nonvoting) job will say "FAIL" if you touched a file that has warnings15:21
tbarronTalking to the cinder folks, the idea is to over time address the backlog of warnings.15:22
gouthamrseesh: https://review.openstack.org/#/c/609791/1/tools/coding-checks.sh@715:22
*** bhavikdbavishi has quit IRC15:22
gouthamrwe can't run cinder's checks - they'll fail of course :P15:22
gansotbarron: there are multiple problems, 1) if fails to import some dependencies. tbarron fixed it this morning. #LINK https://review.openstack.org/632992 and 2) it will fail if you add code, complaining about the way we mock and assert code in unit tests15:22
tbarronIf you get "FAIL" look at the report and see if you can fix some of the issues or fix pylint if it's doing the wrong thing.15:22
* gouthamr was kidding :P15:22
*** bhavikdbavishi has joined #openstack-meeting-alt15:22
tbarrongouthamr: yeah my patch changes that too :)15:23
gouthamrah: https://review.openstack.org/#/c/632992/1/tools/coding-checks.sh15:23
gansotbarron: so, I'll give one practical example and raise some questions15:23
tbarronI noticed that cinder's .pylintrc and ours don't exactly match15:23
tbarronwe may be able to make some mods there to reduce noise15:23
tbarronganso: +115:24
gansoI am working on Manage/Unmanage of Share servers. And as I finished coding, along with unit tests, and everything is working, pylint is printing hundreds of warnings15:24
gansothere is really nothing wrong with the code, because it is exactly as we used to do, the mocks and asserts15:24
gansobut pylint doesn't like it that way15:25
gansoour previous version of pylint didn't complain about mocks and asserts15:25
gansoso, it would be good to get agreement here as to:15:25
tbarronganso: I'd like to filter those out, this issue seems to be https://github.com/PyCQA/pylint/issues/69715:26
gouthamrganso: installing test_requirements should have gotten rid of those specific errors? or do the errors not appear always?15:26
gansotbarron: yea that's the error15:26
tbarrongouthamr: this is a different issue I think15:26
gansotbarron: so, looking at the git discussion15:27
gansotbarron: they don't plan on fixing it15:27
gansotbarron: so we would need to filter those out15:27
gansotbarron: although, filtering those, could potentially filter real problem15:27
gansotbarron: s/problem/problems15:27
tbarronganso: right, we'd need to post-process.  Cause in general that kind of thing is worth catching.15:27
gansoso what I would like to ask is how we would approach:15:28
tbarronWe'd need a smart filter that just exempts mock15:28
ganso1) would we keep pylint as a non-voting job, look at its warning and decide if it is relevant or not15:28
gansoor 2) would we enforce that people submit code that does not generatet pylint warnings15:28
tbarronwell #1 for now I think15:28
* ganso needs to increase the keyboard repeat interval15:29
tbarronit's criteria for pass/fail isn't good enough yet15:29
tbarronits15:29
tbarron(possesive, not the contraction)15:29
ganso#1 requires more work, if we intend to do it in the long term15:30
tbarronganso: I think we've raised awareness and maybe people will seize the day and make improvements as we go forwards.15:30
gansoas we need to check the job result15:30
tbarron#2 is great but it assumes we know how to achieve it.15:30
gansoand validate if the code being proposed is good or not15:31
tbarronganso: if you know how to achieve #2 please propose a patch; otherwise we are stuck making incremental improvements and reminding people to look at the output and think about the results15:31
gansotbarron: we kinda do. Pylint is only checking the changes, so let's say, if we start coding it in a way that does not generate warnings as soon as Train cycle starts, we will not have problems15:31
tbarronganso: we'll still have warnings about asserts in mocks15:32
gansotbarron: at least on my changes, I can just mock it in a different way and the warnings go away15:32
tbarronfor one example15:32
gansotbarron: but I don't want to rewrite all my 1000 lines of unit tests before Stein's feature freeze15:32
tbarronganso: well I suspect there are things we don't know how to code around yet15:33
tbarronganso: agree15:33
gansotbarron: the main problem I see is: people will get confused because of those warnings15:33
tbarronganso if you change one line in Train it will report on the whole file15:33
gansotbarron: as I was when I saw then, and the thing it is complaining about is everywhere in the code, but I can't just code in a similar way to what's already there15:34
tbarronso yes, there is danger of confusion but I don't see a fix yet15:34
gansotbarron: oh yea I forgot about that15:34
gansotbarron: if someone changes one line in test_manager, that person will never be able to get pylint job to pass haha15:34
tbarronOK, unless there's a slam dunk solution now let's settle for raised awareness now.15:35
gouthamris it sane for us to revert the pylint change, and re-introduce it after fixing such issues?15:35
gansogouthamr: it will take us a very long time and a lot of effort to fix all those issues...15:35
gouthamronce we revert, we can run it on the whole tree instead of one commit and catch these errors and fix them15:35
tbarrongouthamr: who is "we" that is going to do the fix?15:35
tbarrongouthamr: whoever that is can propose the revert and fix patches together15:36
tbarronin the mean time we live with this imperfection15:36
gansotbarron: whoever that is will need to rewrite thousands of lines in test_manager :P15:36
gouthamrganso: yes, but what was once nearly okay is now failing15:36
tbarronit's not the only imperfect thing in our world, nor IMO the most important15:36
tbarrongouthamr: well IMO it's not a matter of RED or GREEN but of degreee15:37
gansowe could revert the change and and stick to old pylint?15:37
gouthamrack, but i was under the impression we deleted a bunch of checks/ignores and this was incremental work15:37
tbarronok, you guys propose it and we'll see15:37
gouthamrbut OP is probably busy and didn't follow up on the patches15:37
tbarronwell he's busy in cinder, we *asked* him to bring the change over here15:38
tbarronok, moving on15:38
tbarron#toppic gate issues15:38
ganso*topic15:39
tbarron#topic gate issues15:39
*** openstack changes topic to "gate issues (Meeting topic: manila)"15:39
tbarronganso: ty15:39
* gouthamr is guilty - thanks for raising awareness tbarron ganso15:39
tbarronhere's a fix for the failure to publish the service images when we change them15:39
tbarronit also will bring capability to ssh w/o password15:40
tbarron#link https://review.openstack.org/#/c/631846/15:40
tbarronplease review15:40
tbarronany questions on this one?15:40
tbarronkk15:41
tbarron#topic bugs15:41
*** openstack changes topic to "bugs (Meeting topic: manila)"15:41
jgrossoHi all15:41
gouthamro/ jgrosso15:41
tbarronjgrosso has been working to systematize our bug backlog15:41
tbarronand here he is!15:41
tbarronto tell us about it.15:41
*** dklyle has quit IRC15:41
jgrossook well let me start byt saying I spent a few days looking at the upstream bus15:42
jgrossobugs :)15:42
jgrosso my goal is to make the bugs more visible and organize them in a way that makes it easier for the upstream manila community to process and fix bugs more efficiently.15:42
jgrosso I have read bugs that need to be fixed because they were working on a master thesis :) , to high bugs that are not assigned15:42
* ganso wants to catch a ride in the upstream bus15:43
jgrossoso basically I think the upstream bus needs a driver :)15:43
jgrossoI first kept the same triage pad the same https://etherpad.openstack.org/p/manila-bug-triage-pad15:43
jgrossofor now and added high lights to show the existing bugs15:43
jgrossoOn a side note I was able to go through about 100 manila bugs and create a google sheet15:44
jgrossoMy question is do we have an order to how bugs are triaged, confirmed and assigned?15:44
*** ianychoi has joined #openstack-meeting-alt15:44
jgrossoI am seeing  high bugs that are not assigned, some high status bug that were fix committed and not assigned15:45
tbarronjgrosso: we lack systematic process :)15:45
tbarronand welcome your approach15:45
jgrossoI know OpenStack  releases hang a long time in some cases, but I would like a plan a system for dealing with bugs so I need some input...I would also like some email so I can send a google doc sheet for people to look at15:46
tbarronjgrosso: i can get you the emails of cores and active reviewers15:47
jgrossothat would be great15:47
tbarronjgrosso: but there's nothing secret so you can also share your sheet here and I can put it in the agenda15:47
jgrossosounds good15:47
jgrossoso are there any defects from the triage pad that can be talkerd about I would like to understand why we have so many unassigned15:48
jgrossois it we just dont have the time to work on them?15:48
tbarronjgrosso: there is no manager, there are no employees15:48
tbarronbugs are "assigned" by people taking them15:48
tbarronI think your presenting a fresh, systematic view will help a lot15:49
tbarronbut I should shut up15:49
jgrossook so are there any bugs that need to be addressed in https://etherpad.openstack.org/p/manila-bug-triage-pad15:50
tbarronganso: xyang: toabctl: etc may have other or better answers to your questions15:50
jgrossono that is fine Tom like I said just learning the ropes15:50
gouthamrtremendous work jgrosso!15:51
jgrossoI think organizing this into an easier way to choose bugs may be a better solution, I think taking some of the bugs that have been sitting for years need to be archived some how15:51
tbarronjgrosso: let's have a meeting to go over your sheet and do some clean up of stale bugs15:52
jgrossoI think seeing 300 + bugs makes it hard to choose what bugs to work on. I want to keep going try to organize15:52
jgrossothanks Gouthamr15:52
tbarronjgrosso: when you are ready I'll get you a list of emails for invitees :)15:52
jgrossotbarron: thanks that would be helpful15:53
gouthamrwe welcome new/sporadic contributions/fixes to these bugs, and when we pick up the bugs ourselves we tend to prioritize and fix stuff on a distributed manner - i've let stuff fall through the cracks over time as you'll notice :D15:53
gouthamrtbarron: +115:53
* gouthamr uses wrong smiley15:53
jgrosso:)15:53
tbarronWe'll close most of the bugs older than ocata with a note that if the issue is reproducible in supported releases please re-open.15:54
jgrossoOh yeah I also want to look at Storyboard :)15:54
tbarronbut we need to look and see if there are old serious issues that we know are still valid.15:54
jgrossoI like that tbarron15:54
jgrossoagreed15:54
tbarrondivide and conquer15:54
jgrosso:)15:54
jgrossoThanks so much all15:55
tbarronjgrosso: thank you!15:55
tbarron#topic open discussion15:55
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:55
tbarronanything else for today?15:55
toabctlI wanted to ask what we want to do with the open reviews for the netapp driver15:55
toabctlwho is the maintainer for that driver?15:55
gansotoabctl: I am15:56
toabctlganso, could you have a look at https://review.openstack.org/#/c/558465/ and https://review.openstack.org/#/c/619573/ then please?15:56
gansotoabctl: I will as soon as I have some time15:56
*** liuyulong has quit IRC15:57
toabctlok. theses are already month old and not to complicated. thanks!15:57
carthacaganso: thanks :)15:57
tbarroncarthaca: thanks for your work, you guys should get a discount from netapp :)15:58
gouthamr#freeONTAP15:58
*** TxGirlGeek has joined #openstack-meeting-alt15:58
gouthamrheh, #freeBeer15:58
toabctllol15:58
tbarronWell let's end smiling today.15:59
tbarronThanks everyone! See you in #openstack-manila ....15:59
tbarron#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Thu Jan 24 15:59:55 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-01-24-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-01-24-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-01-24-15.00.log.html16:00
*** carthaca has left #openstack-meeting-alt16:01
*** dave-mccowan has joined #openstack-meeting-alt16:04
*** dklyle has joined #openstack-meeting-alt16:04
*** jrbalderrama has quit IRC16:06
*** gyee has joined #openstack-meeting-alt16:06
*** tssurya has quit IRC16:08
*** e0ne has quit IRC16:09
*** dave-mccowan has quit IRC16:09
*** ttsiouts has quit IRC16:11
*** gyee has quit IRC16:14
*** efried has joined #openstack-meeting-alt16:18
*** efried is now known as efried_2dmtg16:18
*** ccamacho has quit IRC16:23
*** gyee has joined #openstack-meeting-alt16:25
*** macza has joined #openstack-meeting-alt16:33
*** panda is now known as panda|off16:40
*** lujinluo has joined #openstack-meeting-alt17:00
*** bhavikdbavishi has quit IRC17:01
*** yamamoto has joined #openstack-meeting-alt17:13
*** kopecmartin is now known as kopecmartin|off17:18
*** yamamoto has quit IRC17:18
*** bhavikdbavishi has joined #openstack-meeting-alt17:20
*** ccamacho has joined #openstack-meeting-alt17:28
*** dklyle has quit IRC17:40
*** whoami-rajat has quit IRC17:43
*** dims has quit IRC17:43
*** dims has joined #openstack-meeting-alt17:48
*** dklyle has joined #openstack-meeting-alt17:50
*** ganso has left #openstack-meeting-alt17:51
*** dims has quit IRC17:54
*** dims has joined #openstack-meeting-alt17:55
*** lujinluo has quit IRC17:57
*** e0ne has joined #openstack-meeting-alt17:59
*** yamahata has quit IRC18:03
*** iyamahat has quit IRC18:03
*** igordc has joined #openstack-meeting-alt18:04
*** derekh has quit IRC18:09
*** e0ne has quit IRC18:13
*** lujinluo has joined #openstack-meeting-alt18:13
*** lujinluo has quit IRC18:14
*** sridharg has quit IRC18:14
*** iyamahat has joined #openstack-meeting-alt18:17
*** whoami-rajat has joined #openstack-meeting-alt18:20
*** iyamahat_ has joined #openstack-meeting-alt18:21
*** iyamahat has quit IRC18:24
*** e0ne has joined #openstack-meeting-alt18:27
*** yamahata has joined #openstack-meeting-alt18:36
*** ccamacho has quit IRC18:38
*** armstrong has quit IRC18:40
*** efried_2dmtg1 has joined #openstack-meeting-alt18:57
*** efried_2dmtg has quit IRC18:59
*** efried_2dmtg1 is now known as efried_2dmtg18:59
*** TxGirlGe_ has joined #openstack-meeting-alt18:59
*** TxGirlGeek has quit IRC19:00
*** e0ne has quit IRC19:02
*** ijw has joined #openstack-meeting-alt19:07
*** bhavikdbavishi has quit IRC19:11
*** hongbin has quit IRC19:20
*** hongbin has joined #openstack-meeting-alt19:22
*** hongbin has quit IRC19:22
*** baojg has quit IRC19:22
*** hongbin has joined #openstack-meeting-alt19:25
*** e0ne has joined #openstack-meeting-alt19:26
*** TxGirlGe_ has quit IRC19:32
*** dklyle has quit IRC19:37
*** iyamahat__ has joined #openstack-meeting-alt19:40
*** isq_ has joined #openstack-meeting-alt19:41
*** iyamahat_ has quit IRC19:42
*** yamahata has quit IRC19:42
*** isq has quit IRC19:42
*** e0ne has quit IRC19:54
*** jgrosso has quit IRC19:55
*** yamahata has joined #openstack-meeting-alt19:56
*** yamamoto has joined #openstack-meeting-alt20:00
*** erlon_ has quit IRC20:02
*** dklyle has joined #openstack-meeting-alt20:15
*** TxGirlGeek has joined #openstack-meeting-alt20:26
*** whoami-rajat has quit IRC20:43
*** rcernin has joined #openstack-meeting-alt21:02
*** baojg has joined #openstack-meeting-alt21:23
*** carlos_silva has quit IRC21:23
*** baojg has quit IRC21:27
*** jesusaur has joined #openstack-meeting-alt21:45
*** slaweq has quit IRC22:10
*** rcernin has quit IRC22:11
*** rcernin has joined #openstack-meeting-alt22:12
*** bswartz has quit IRC22:14
*** slaweq has joined #openstack-meeting-alt22:17
*** jcoufal has quit IRC22:36
*** dklyle has quit IRC22:52
*** baojg has joined #openstack-meeting-alt22:53
*** hongbin has quit IRC22:54
*** slaweq has quit IRC23:04
*** masahito has joined #openstack-meeting-alt23:10
*** dklyle has joined #openstack-meeting-alt23:11
*** slaweq has joined #openstack-meeting-alt23:11
*** masahito has quit IRC23:15
*** TxGirlGeek has quit IRC23:15
*** slaweq has quit IRC23:15
*** dklyle has quit IRC23:19
*** dave-mccowan has joined #openstack-meeting-alt23:31
*** erlon has joined #openstack-meeting-alt23:36
*** dklyle has joined #openstack-meeting-alt23:51
*** baojg has quit IRC23:55
*** dave-mccowan has quit IRC23:59

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