Thursday, 2019-01-31

*** TxGirlGeek has quit IRC00:01
*** hongbin has quit IRC00:05
*** sdake has joined #openstack-meeting-alt00:05
*** sdake has quit IRC00:29
*** sdake has joined #openstack-meeting-alt00:49
*** masahito has joined #openstack-meeting-alt01:04
*** masahito has quit IRC01:08
*** sdake has quit IRC01:09
*** jcoufal has quit IRC01:22
*** gyee has quit IRC01:33
*** liuyulong has joined #openstack-meeting-alt01:50
*** jcoufal has joined #openstack-meeting-alt02:01
*** TxGirlGeek has joined #openstack-meeting-alt02:02
*** whoami-rajat has joined #openstack-meeting-alt02:11
*** liuyulong has quit IRC02:21
*** dims has quit IRC02:38
*** bhavikdbavishi has joined #openstack-meeting-alt02:50
*** dims has joined #openstack-meeting-alt02:55
*** iyamahat has quit IRC02:59
*** yamahata has quit IRC03:00
*** sdake has joined #openstack-meeting-alt03:00
*** masahito has joined #openstack-meeting-alt03:05
*** masahito has quit IRC03:09
*** apetrich has quit IRC03:15
*** yamahata has joined #openstack-meeting-alt03:35
*** tetsuro has quit IRC04:04
*** TxGirlGeek has quit IRC04:18
*** hongbin has joined #openstack-meeting-alt04:48
*** hongbin has quit IRC05:04
*** lbragstad has quit IRC05:16
*** e0ne has joined #openstack-meeting-alt06:12
*** igordc has quit IRC06:30
*** tetsuro has joined #openstack-meeting-alt06:31
*** zzzeek has quit IRC06:33
*** tetsuro has quit IRC06:35
*** zzzeek has joined #openstack-meeting-alt06:37
*** radeks_ has joined #openstack-meeting-alt06:54
*** sridharg has joined #openstack-meeting-alt07:00
*** e0ne has quit IRC07:05
*** ccamacho has joined #openstack-meeting-alt07:15
*** markvoelker has joined #openstack-meeting-alt07:26
*** kopecmartin|off is now known as kopecmartin07:30
*** jcoufal has quit IRC07:39
*** slaweq has joined #openstack-meeting-alt07:39
*** slaweq has quit IRC07:43
*** jcoufal has joined #openstack-meeting-alt07:56
*** markvoelker has quit IRC07:59
*** slaweq has joined #openstack-meeting-alt08:03
*** apetrich has joined #openstack-meeting-alt08:17
*** lhinds has quit IRC08:51
*** iyamahat has joined #openstack-meeting-alt08:52
*** lhinds has joined #openstack-meeting-alt08:55
*** ttsiouts has joined #openstack-meeting-alt08:56
*** markvoelker has joined #openstack-meeting-alt08:56
*** haleyb has quit IRC09:03
*** ttsiouts has quit IRC09:06
*** ttsiouts has joined #openstack-meeting-alt09:07
*** ttsiouts has quit IRC09:11
*** iyamahat has quit IRC09:11
*** e0ne has joined #openstack-meeting-alt09:15
*** ttsiouts has joined #openstack-meeting-alt09:15
*** tssurya has joined #openstack-meeting-alt09:21
*** janki has joined #openstack-meeting-alt09:29
*** markvoelker has quit IRC09:29
*** panda|off is now known as panda09:46
*** derekh has joined #openstack-meeting-alt09:48
*** bhavikdbavishi has quit IRC09:52
*** masahito has joined #openstack-meeting-alt09:58
*** masahito has quit IRC10:02
*** erlon has joined #openstack-meeting-alt10:10
*** markvoelker has joined #openstack-meeting-alt10:26
*** apetrich has quit IRC10:27
*** rnoriega has quit IRC10:35
*** rnoriega has joined #openstack-meeting-alt10:36
*** apetrich has joined #openstack-meeting-alt10:41
*** e0ne has quit IRC10:46
*** e0ne has joined #openstack-meeting-alt10:52
*** priteau has joined #openstack-meeting-alt10:53
*** purplerbot has quit IRC10:57
*** purplerbot has joined #openstack-meeting-alt10:57
*** markvoelker has quit IRC10:59
*** rfolco has joined #openstack-meeting-alt11:05
*** yamahata has quit IRC11:20
*** ttsiouts has quit IRC11:23
*** e0ne has quit IRC11:24
*** ttsiouts has joined #openstack-meeting-alt11:24
*** ttsiouts has quit IRC11:28
*** e0ne has joined #openstack-meeting-alt11:34
*** sdake has quit IRC11:41
*** sdake has joined #openstack-meeting-alt11:48
*** janki has quit IRC11:51
*** markvoelker has joined #openstack-meeting-alt11:57
*** igordc has joined #openstack-meeting-alt11:58
*** masahito has joined #openstack-meeting-alt11:59
*** masahito has quit IRC12:04
*** lpetrut has joined #openstack-meeting-alt12:17
*** ttsiouts has joined #openstack-meeting-alt12:21
*** markvoelker has quit IRC12:29
*** armstrong has joined #openstack-meeting-alt12:54
*** e0ne has quit IRC13:01
*** e0ne has joined #openstack-meeting-alt13:04
*** igordc has quit IRC13:16
*** igordc has joined #openstack-meeting-alt13:18
*** bhavikdbavishi has joined #openstack-meeting-alt13:20
*** bhavikdbavishi has quit IRC13:22
*** bhavikdbavishi has joined #openstack-meeting-alt13:22
*** e0ne has quit IRC13:25
*** haleyb has joined #openstack-meeting-alt13:25
*** markvoelker has joined #openstack-meeting-alt13:26
*** e0ne has joined #openstack-meeting-alt13:29
*** e0ne has quit IRC13:30
*** e0ne has joined #openstack-meeting-alt13:32
*** e0ne has quit IRC13:34
*** e0ne has joined #openstack-meeting-alt13:35
*** jcoufal has quit IRC13:37
*** bhavikdbavishi has quit IRC13:39
*** lujinluo has joined #openstack-meeting-alt13:53
*** lbragstad has joined #openstack-meeting-alt13:57
*** markvoelker has quit IRC13:58
lujinluo#startmeeting neutron_upgrades14:00
openstackMeeting started Thu Jan 31 14:00:25 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
lujinluoo/14:00
lujinluoI will be waiting for others to join. If you everyone happens to be busy, I will quickly go through the updates we have today for record.14: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#link https://review.openstack.org/#/c/544206/ port binding14:02
lujinluoThanks nate for reviewing the patch! I resolved the merge conflict yesterday and obviously i missed something thus it failed at zuul14:03
lujinluoI will push another patch set to fix it later today14:03
lujinluoand we don't have updates on other patches last week14:04
lujinluoHopefully i will be able to spend more time on new patches this week14:06
lujinluo#topic open discussion14:06
*** openstack changes topic to "open discussion (Meeting topic: neutron_upgrades)"14:06
lujinluonate and I are now have a discussion about whether we should pass ovo object in register.notify()14:07
lujinluoan example patch is #link https://review.openstack.org/#/c/624815/ Utilize bulk port creation ops in ml2 plugin14:07
lujinluoto be more specific #link https://review.openstack.org/#/c/624815/28/neutron/db/db_base_plugin_v2.py@130714:08
*** sdake has quit IRC14:08
lujinluowe will see where this is going14:09
lujinluoand that's all i have for today14:09
lujinluook, let's call it a short meeting today :)14:11
*** e0ne has quit IRC14:13
lujinluo#endmeeting14:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:14
openstackMeeting ended Thu Jan 31 14:14:04 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_upgrades/2019/neutron_upgrades.2019-01-31-14.00.html14:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_upgrades/2019/neutron_upgrades.2019-01-31-14.00.txt14:14
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_upgrades/2019/neutron_upgrades.2019-01-31-14.00.log.html14:14
*** dave-mccowan has joined #openstack-meeting-alt14:18
*** lujinluo has quit IRC14:20
*** sridharg has quit IRC14:27
*** dtrainor has quit IRC14:34
*** dtrainor has joined #openstack-meeting-alt14:38
*** sridharg has joined #openstack-meeting-alt14:39
*** sridharg has quit IRC14:39
*** sdake has joined #openstack-meeting-alt14:39
*** dave-mccowan has quit IRC14:41
*** e0ne has joined #openstack-meeting-alt14:45
*** igordc has quit IRC14:48
*** igordc has joined #openstack-meeting-alt14:49
*** jcoufal has joined #openstack-meeting-alt14:53
*** bswartz has joined #openstack-meeting-alt14:55
*** markvoelker has joined #openstack-meeting-alt14:56
*** ganso has joined #openstack-meeting-alt14:57
tbarron#startmeeting manila15:00
openstackMeeting started Thu Jan 31 15:00:26 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
bswartz.o/15:00
tbarronbswartz: hi15:00
tbarronping ganso15:00
tbarronping gouthamr15:00
tbarronping amito15:00
amitohey o/15:00
*** carthaca has joined #openstack-meeting-alt15:01
carthacahi15:01
tbarronzhongjun isn't online but recently did a review :)15:01
tbarronhi amito carthaca15:01
tbarronping vkmc15:01
tbarronping toabctl15:01
toabctlhey15:01
tbarronping erlon15:01
gansohello15:02
tbarronping tpsilva (wonder if he's still doing manila ...)15:02
*** cNilesh has joined #openstack-meeting-alt15:02
tbarronthat's the ping list15:02
tbarroni'll give it a couple minutes ...15:02
gansotbarron: he doesn't work for NetApp anymore15:02
* bswartz hands gouthamr a coffee15:03
tbarronganso: that's what I heard, but w'd like canonical folks here too!15:03
* tbarron is certainly wearing his upstream hat today15:03
gansolol15:03
*** carlos_silva has joined #openstack-meeting-alt15:04
tbarrontoabctl: hi!15:04
*** armstrong has quit IRC15:04
gouthamro/15:04
gouthamrty bswartz :)15:04
tbarronping xyang15:04
tbarronOK let's go15:05
tbarronHi All!15:05
tbarron#link https://wiki.openstack.org/wiki/Manila/Meetings15:05
tbarron#topic announcements15:06
*** openstack changes topic to "announcements (Meeting topic: manila)"15:06
tbarroncinder meetup is next week in RTP area of North Carolina15:06
tbarronif you are around and can attend talk to jungleboyj15:07
tbarronI have a bunch of conflicts but may do some of it15:07
tbarronthe manila zorillas always consider WWCD15:07
jungleboyj:-)15:07
tbarronwhat would cinder do15:07
tbarroneven if we like to do it better :)15:07
jungleboyjIf people are interested we would be happy to have you attend.15:08
tbarronThat's all I have for announcements.15:08
tbarronjungleboyj: thanks15:08
tbarronAnyone else have announcements?15:08
tbarron#topic share shrinking issue - gouthamr you are up.15:09
*** openstack changes topic to "share shrinking issue - gouthamr you are up. (Meeting topic: manila)"15:09
gouthamro/ ty tbarron, this was a review question15:10
jungleboyjtbarron:  Hope you can make it for some of the meetings.  :-)  Or post meeting fun.15:10
gouthamr#LINK LINK: https://review.openstack.org/#/c/632615/13/manila/share/drivers/dell_emc/plugins/unity/client.py@30915:10
gouthamr#LINK: https://review.openstack.org/#/c/632615/13/manila/share/drivers/dell_emc/plugins/unity/client.py@30915:10
bswartzI would have expected a shrink to fail in this case15:11
gouthamrbswartz: ack, that's what i'm familiar with too15:11
tbarrongouthamr: do they not have the ability to detect this condition?15:11
bswartzUnless we're able to shrink the share all the way down to the desired size, I would expect failure and no resize at all15:12
tbarrongouthamr: in advance of modifying the share ...15:12
gansoit should fail15:12
gouthamrtbarron: per the response, seems like no..15:12
gansobecause the manila DB will believe the share is a 2GB share15:12
gansowhile it is not15:12
bswartzThen the user can retry again for a shrink to a larger size15:12
tbarronbswartz: I agree that should be the requirement15:13
bswartzso gouthamr: what is the specific issue we need to decide here?15:13
gouthamrthat's it, actually - i was wondering what we'd do here15:14
*** IgorYozhikov__ has quit IRC15:14
tbarrongouthamr: so they can do the shrink, detect that it was partial, do an implicit expand back to the original size, and fail  the shrink :)15:14
gouthamrbecause the committer says they can't detect the usage and fail the operation15:14
gouthamrtbarron: that's one option in case they can't predetermine what the usage on the share is15:15
tbarrongouthamr: I think you should explain the semantics manila expects and propose that if they can't do anything better.15:15
gouthamrack15:15
tbarronit's kinda like a db transaction rollback.15:15
tbarronback ends with limitations have to do more work15:16
*** bhavikdbavishi has joined #openstack-meeting-alt15:16
gouthamron those lines, however, how does one recover from that error condition they've put themselves in?15:16
*** IgorYozhikov__ has joined #openstack-meeting-alt15:16
gouthamr"STATUS_SHRINKING_POSSIBLE_DATA_LOSS_ERROR"15:16
* gouthamr is sorry for the caps - copy pasta15:16
tbarronwhy are they in that condition?  I don't understand.15:16
tbarronThey are shrinking ... not done yet in manila15:17
gouthamrtbarron: when a user tries to shrink a share beyond the usage size, the 'status' is set to that ^15:17
tbarronin their back end they shrunk to 3gb instead of 215:17
*** TxGirlGeek has joined #openstack-meeting-alt15:18
tbarrontheir usage is 3gb15:18
tbarronthe driver brings the share back to 4gb on their back end15:18
gouthamrafaict, the only ways seem to be: try to shrink again to a valid size, or contact a privileged user (admin) to reset the status15:18
tbarronand failis the shrink15:18
*** priteau has quit IRC15:19
gouthamrtbarron: yes, the driver failing with that error, puts the share in "share_shrinking_possible_data_loss" status15:19
tbarrongouthamr their driver shouldn't fail with that error15:19
tbarronoh15:19
tbarroni see now15:19
tbarronwhy do we say possible data loss just b/c the shrink failed15:20
gansogouthamr: so you think that, if they were able to detect and by raising a proper exception, manila should set the share status back to available instead of shrink error, correct?15:20
tbarronif a driver can know it can't do an op b/c it's unsafe and refuses it seems like there should be a different status15:21
gansotbarron: because the driver raises the exception and we currently (AFAIK) have no way to tell if the shrink has been attempted and failed, or if the driver just detected that it cannot do.15:21
tbarronganso: yeah I understand now15:21
tbarronseems like we have a limitation then.15:21
gansotbarron: we should handle different exceptions for this method15:21
gansotbarron: but we aren't15:22
gouthamrganso: yeah, would that be weird? we can set a user-message15:22
gansotbarron: I wouldn't say it is a limitation, we need a code improvement15:22
tbarronso they should also propose some core work for that code improvement15:22
gansogouthamr: but we need a code improvement to avoid the shrink error status.15:22
gansogouthamr: user message is not enough15:23
tbarronganso: one person's limitation is another's enhancement opportunity15:23
gansotbarron: =)15:23
gansoeither way, I think we have several drivers that fall into the same category15:24
gouthamrganso: why though? i know it is terribly weird if something appears to be happening, and then randomly goes back to "available"15:24
*** sdake has quit IRC15:24
tbarrongouthamr: ganso: today the user will have to go to an admin to get it fixed but they could do a little bit of work and add exception handling for a diffrent exception and it would be  better15:24
gouthamrganso: but the alternatives to get yourselves out of that situation is 1) Shrink the share again to a valid size (which isn't too obvious)15:25
gouthamr2) go to the admin15:25
gansotbarron: gouthamr thinks the lack of status change is wierd15:25
gansoI partially agree with that15:25
gansoboth solutions have advantages and disadvantages15:25
gouthamryeah, because you can't do anything else in manila with a share that's actually not in an error state if the driver bailed out correctly15:26
gansogoing back to available and triggering a user message sounds good to me15:26
tbarronwhat's weird is that every kind of error leaves the user needing to go to an admin15:26
*** hongbin has joined #openstack-meeting-alt15:26
gansotbarron: +115:26
tbarronif a back end is smart enough to block an operation and leavae hte user safe we ought to be able to handle that15:26
*** lpetrut has quit IRC15:27
tbarrongouthamr: but we're moving into a bigger issue than thhis particular review15:27
gouthamrtbarron: yes we are15:27
* gouthamr its a trap15:27
tbarronlet's have them do the right thing given our current framework15:27
gansogouthamr you brought a can of worms15:27
tbarronand I'll put the can of worms on next agenda15:27
tbarronnext week's agenda15:28
tbarronwe can all think about it and have headaches in the mean time15:28
*** lseki_ has joined #openstack-meeting-alt15:28
tbarrongouthamr: you ok with that?15:28
gouthamrhaha, works for me - to the current question on the review on what the Unity driver should do, i like the solution and will let them know15:28
tbarron#topic pylint again15:29
*** openstack changes topic to "pylint again (Meeting topic: manila)"15:29
tbarronganso brought up all the spurious pylint failures last week15:29
*** markvoelker has quit IRC15:29
tbarronbut I think we can make some headway15:29
tbarronas an experiment:15:29
tbarron#link https://review.openstack.org/#/c/633576/15:30
tbarrontouches every file, so they all get examined15:30
tbarronand filters out the test files, alembic migrations, etc15:30
tbarronwhich are full of noise15:30
tbarronthe report is small enough that one can find genuine issues15:30
tbarronand fix them15:31
tbarronand some issues that should be handled with # pylint ignore comments15:31
tbarronso I propose that we leave this job to go red for a while15:31
tbarronbut make progress on cleaning up the codebase15:32
tbarronThat means reviewers should look at it when it's red.15:32
tbarronOnly the files touched by the review are examined.15:32
gouthamrtbarron: did things change significantly in pylint 1.9.0, or should we bring back the ignores we had in the old tools/lintstack.py15:32
tbarronTry to clean up the non test code files in the course of a review15:32
tbarronIt can be a followup.15:32
tbarrongouthamr: I don't really know but I think the main thing was not so much the ignores as that15:33
tbarronthe old job used to work as a ratchet, only looking for newly introduced issues15:34
gansotbarron: do you plan to merge that "skip workaround"?15:34
tbarronganso: not until it's more refined15:34
bswartzSo these pylint warning are legit?15:35
tbarronbswartz: enough of them that they're worth looking at15:35
bswartzAny new contributors looking for low hanging fruit?15:35
tbarronI've done two reviews fixing stuff already15:35
tbarronSometimes a fix is just to add pylint ignores, as in15:36
bswartzYeah but in those cases the warnings aren't legit15:36
bswartzI was asking if it's finding things that we would actually want to fix, absent any lint checker15:36
tbarron#link https://review.openstack.org/#/c/634210/15:36
tbarronbswartz: we do want to fix duplicate methods in general15:36
tbarronbswartz: just did  that in a driver review15:37
bswartzThen why not globally disable E0102?15:37
tbarronbswartz: the author didn't know he had a method by the same name15:37
gouthamrtbarron: afair we used to disable E010215:37
bswartzOh I got it backwards15:37
bswartzI see15:37
tbarronbswartz: b/c usually you want to know and remove the method15:37
tbarronbswartz: but in api code with microversion decorators it's ok15:37
gouthamroh, can we disable it in a subdirectory?15:38
tbarronbswartz: and only two # pylint ignore comments were missing, we usually do it15:38
tbarrongouthamr: well even in a file you only want to ignore sometimes15:38
tbarrongouthamr: but to your question,  yes for pylint but no for our script15:39
tbarrongouthamr: our script picks individual files and runs pylint against them in a way that the .pylintrc directives to skip certain dirs don't have effect15:39
tbarronat least in my experimentation15:39
tbarronthat's why I'm modifying the script to ignore subdirs15:40
tbarronwe could give the script an ignore-list15:40
gouthamryes, that'd be helpful15:40
carthacamaybe it it possible to let the microversion decorator do the job to pylint ignore?15:40
tbarronlike for the alembic stuff and maybe the wsgi stuff15:40
tbarroncarthaca: be my guest :)15:41
*** ccamacho has quit IRC15:41
tbarronI'm hearing lots of good optimization ideas, feel free to propose improvements!15:41
tbarronMy point wasn't to declare a policy but rather to give you folks a heads up and engage interest and efforts in cleanup.15:41
tbarronbswartz point that a lot of these are low-hanging fruit is a good one.15:42
tbarronok15:42
tbarron#topic skip  third party jobs on WIP patches??15:42
*** openstack changes topic to "skip third party jobs on WIP patches?? (Meeting topic: manila)"15:42
tbarronNow that our job queue definitions are in tree it's easy15:42
tbarronto modify .zuul.yaml in WIP patches to run only the jobs relevant to your patch15:43
bswartzAre you talking about 3rd party CI?15:43
tbarronYou're working on the lvm driver, just run the lvm job in the check queue until15:43
*** priteau has joined #openstack-meeting-alt15:43
tbarronyou're ready to merge.15:44
bswartzOr the upstream CI?15:44
tbarronsave resources, run faster.15:44
tbarronbswartz: so far laying groundwork, upstream so far.15:44
bswartzCould the approach be used by 3rd party CIs too?15:44
tbarronbswartz: bingo15:44
bswartzWhat exactly do I do to .zuul.yaml if I have a WIP patch?15:45
tbarronbswartz: and if a third party job sees WIP status on a patch it would skip15:45
gouthamrbswartz: yank out all the jobs except the one you care about :)15:45
tbarronunless there's an explicit run-netappm etc15:45
bswartzSeems like a good way to economize on compute resources15:45
gansotbarron: I'm confused. The approach I saw in your pylint patch skips 1st party jobs, not 3rd party15:45
gouthamrbswartz: like this:15:46
gouthamr#LINK https://review.openstack.org/#/c/545695/28/.zuul.yaml15:46
tbarronganso: cause I don't have a way to skip third pary, that's why I brought this up15:46
tbarronganso: I think your CI has to check for something and decide to skip15:46
bswartzgouthamr: that doesn't help with skipping 3rd party CI15:46
tbarronganso: gouthamr's idea is that we also mark the review WIP15:47
gouthamrdoesn't, thought your question pertained to our jobs15:47
tbarronganso: bswartz: your CI would then skp15:47
tbarronskip15:47
tbarronthe code poster would do two things:15:47
gansotbarron: yep, but all the effort to skip 3rd party jobs would be on 3rd parties side, I believe there is nothing we can do right now to achieve that without changes in 3rd parties' sidde15:47
tbarron1) modify zuul.yaml15:47
tbarron2) mark the review WIP15:47
tbarronganso: that's what I'm saying also15:48
bswartzYou mean just the word "WIP" in the commit message should skip the jobs?15:48
bswartzOr workflow -1?15:48
gansowhy not the workflow -1?15:48
gouthamrwe could use Workflow -115:48
gansobswartz: +115:48
tbarronbswartz: ganso: gouthamr: that's better15:48
gouthamrthat's easier to detect/parse in the older zuul that most third party CIs are running15:48
gouthamrjust a simple change to their config15:48
bswartzThe problem is you can't workflow -1 until after the review is live15:49
bswartzSo there's a race condition15:49
gouthamrbswartz: not really15:49
bswartzI guess as long as 3rd party CIs aren't too fast it doesn't matter15:49
gouthamrbswartz: we encourage third party CIs not to run until upstream CI has voted15:49
bswartzBut then it's a totally different approach to modifying .zuul.yaml to disable first party jobs15:49
gansobswartz: but most 3rd party CIs have their jobs triggered only when Zuul +1's15:49
*** ccamacho has joined #openstack-meeting-alt15:50
tbarronbswartz: yes, it would be nice to have an elegant central solution but I don't have one in hand15:50
*** yamahata has joined #openstack-meeting-alt15:51
tbarronganso: do you want to adjust netapp to not run if Workflow -1?15:51
bswartzOkay, 2 different approaches are fine15:51
gansotbarron: when I have some time to, sure15:52
* tbarron sends ganso some of gouthamr's free time15:52
* ganso receives plenty of free time!15:52
tbarronI'm guessing this is a small change for each third party CI that will actually15:52
gouthamrfree, what's that?15:52
tbarronsave its maintainers time.15:52
tbarron#topic bugs15:53
*** openstack changes topic to "bugs (Meeting topic: manila)"15:53
tbarronjgrosso is on PTO but15:53
tbarrongouthamr has been working with him in his free time15:53
gouthamrit's just as easy with zuulv3: https://zuul-ci.org/docs/zuul/user/config.html#pipeline15:53
tbarronand jgrosso has a spreadsheet of bugs in the works15:54
gouthamr#zuulIsCool15:54
tbarronhe's going to email cores and other active reviewers soon15:54
tbarronand we'll post the spreadsheet and a proposed bug backlog reduction plan15:55
tbarrona lot of it will be agreeing to some cleanup and prioiritization15:55
tbarroncan't spell ^^^15:55
tbarronSo don't put mail from jgrosso in your spam folder please :)15:56
tbarrongouthamr: anyting you have on $topic?15:56
gouthamrtbarron: nope, that's mostly it - i'm excited to get this work started15:56
tbarron#topic open discussion15:56
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:56
tbarron:)15:56
* gouthamr jgrosso is clearly not as lazy as him15:56
tbarronhe's quite organized15:57
gouthamractually, i suggested he mail openstack-discuss15:57
tbarrongouthamr: agree15:57
tbarronok, seems like we're through for today.15:58
tbarronThanks everyone!!15:58
bswartzPerfectly on time15:58
tbarron#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:58
openstackMeeting ended Thu Jan 31 15:58:25 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-01-31-15.00.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-01-31-15.00.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2019/manila.2019-01-31-15.00.log.html15:58
gouthamrping _pewp_15:58
gouthamr:P15:58
* bswartz slaps gouthamr around a bit with a large trout15:59
gouthamraw man, just wanted to flip some tables is all15:59
bswartzOh I forgot that was the bot's name!15:59
bswartzDoes it still respond to commands?15:59
* gouthamr pages jungleboyj 15:59
jungleboyjWhat?16:00
ganso@!16:00
_pewp_ganso (ه’́⌣’̀ه )/16:00
tbarronbeelzebug16:00
jungleboyjYou mean pewp bot?16:00
jungleboyj@!16:00
_pewp_jungleboyj (♦亝д 亝)ノ16:00
jungleboyjUse '@' to call him.16:00
gouthamrah!16:00
gouthamr@!!16:00
bswartz@help16:01
*** carthaca has left #openstack-meeting-alt16:01
tbarronnot a very helpful guy16:01
gouthamr:P needs more free time16:01
*** rdopiera has quit IRC16:18
*** sdake has joined #openstack-meeting-alt16:21
*** igordc has quit IRC16:24
*** rdopiera has joined #openstack-meeting-alt16:25
*** markvoelker has joined #openstack-meeting-alt16:27
*** ganso has left #openstack-meeting-alt16:31
*** TxGirlGeek has quit IRC16:35
*** cNilesh has quit IRC16:38
*** e0ne has quit IRC16:46
*** priteau has quit IRC16:50
*** lseki_ has left #openstack-meeting-alt16:54
*** markvoelker has quit IRC17:00
*** TxGirlGeek has joined #openstack-meeting-alt17:04
*** kopecmartin is now known as kopecmartin|off17:04
*** iyamahat has joined #openstack-meeting-alt17:07
*** iyamahat has quit IRC17:09
*** iyamahat has joined #openstack-meeting-alt17:09
*** ttsiouts has quit IRC17:13
*** ccamacho has quit IRC17:13
*** ttsiouts has joined #openstack-meeting-alt17:13
*** tssurya has quit IRC17:17
*** ttsiouts has quit IRC17:18
*** gyee has joined #openstack-meeting-alt17:19
*** sdake has quit IRC17:28
*** ccamacho has joined #openstack-meeting-alt17:53
*** iyamahat has quit IRC17:54
*** yamahata has quit IRC17:54
*** bhavikdbavishi has quit IRC17:58
*** bhavikdbavishi has joined #openstack-meeting-alt17:59
*** derekh has quit IRC18:00
*** sdake has joined #openstack-meeting-alt18:07
*** iyamahat has joined #openstack-meeting-alt18:07
*** igordc has joined #openstack-meeting-alt18:07
*** Swami has joined #openstack-meeting-alt18:10
*** iyamahat_ has joined #openstack-meeting-alt18:15
*** iyamahat has quit IRC18:18
*** yamahata has joined #openstack-meeting-alt18:26
*** macza has joined #openstack-meeting-alt18:30
*** bhavikdbavishi has quit IRC18:30
*** e0ne has joined #openstack-meeting-alt18:39
*** panda is now known as panda|off18:41
*** e0ne has quit IRC18:48
*** TxGirlGeek has quit IRC18:51
*** TxGirlGeek has joined #openstack-meeting-alt18:53
*** lpetrut has joined #openstack-meeting-alt18:57
*** bhavikdbavishi has joined #openstack-meeting-alt19:21
*** bhavikdbavishi has quit IRC19:23
*** erlon has quit IRC19:23
*** markvoelker has joined #openstack-meeting-alt19:27
*** TxGirlGeek has quit IRC19:48
*** jcoufal has quit IRC19:50
*** rnoriega has quit IRC19:57
*** rnoriega has joined #openstack-meeting-alt19:57
*** markvoelker has quit IRC20:00
*** TxGirlGeek has joined #openstack-meeting-alt20:05
*** igordc has quit IRC20:37
*** igordc has joined #openstack-meeting-alt20:39
*** rfolco has quit IRC20:40
*** carlos_silva has quit IRC20:43
*** markvoelker has joined #openstack-meeting-alt20:57
*** TxGirlGeek has quit IRC21:00
*** efried has quit IRC21:02
*** efried has joined #openstack-meeting-alt21:02
*** jcoufal has joined #openstack-meeting-alt21:02
*** efried has quit IRC21:16
*** efried has joined #openstack-meeting-alt21:17
*** TxGirlGeek has joined #openstack-meeting-alt21:25
*** iyamahat_ has quit IRC21:29
*** markvoelker has quit IRC21:30
*** radeks_ has quit IRC21:35
*** iyamahat has joined #openstack-meeting-alt21:38
*** lpetrut has quit IRC21:54
*** lpetrut has joined #openstack-meeting-alt21:58
*** ccamacho has quit IRC22:10
*** lpetrut has quit IRC22:14
*** jcoufal has quit IRC22:19
*** macza has quit IRC22:23
*** macza has joined #openstack-meeting-alt22:24
*** IgorYozhikov__ has quit IRC22:27
*** markvoelker has joined #openstack-meeting-alt22:27
*** sdake has quit IRC22:30
*** IgorYozhikov__ has joined #openstack-meeting-alt22:36
*** macza_ has joined #openstack-meeting-alt22:40
*** markvoelker has quit IRC22:41
*** macza has quit IRC22:43
*** sdake has joined #openstack-meeting-alt22:45
*** IgorYozhikov__ has quit IRC22:52
*** IgorYozhikov__ has joined #openstack-meeting-alt23:00
*** whoami-rajat has quit IRC23:00
*** masahito has joined #openstack-meeting-alt23:08
*** masahito has quit IRC23:12
*** slaweq has quit IRC23:14

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