Friday, 2019-08-23

*** markvoelker has joined #openstack-tc00:00
*** markvoelker has quit IRC00:05
*** dtruong has quit IRC00:07
*** dtruong has joined #openstack-tc00:07
*** markvoelker has joined #openstack-tc00:22
*** mriedem_away is now known as mriedem00:32
*** mriedem has quit IRC00:33
*** markvoelker has quit IRC00:47
*** flwang has joined #openstack-tc01:50
flwangmnaser: are you there? I think we need to discuss your patches in magnum, something you mentioned in the TC meeting are not true01:54
mnaserhappy to listen, but it's almost 10pm here and I'm on mobile01:55
mnaserPlease feel free to clarify here01:55
flwangthe patch about flannel you mentioned, me and spyros were trying to help and we have raised our comments, but we didn't see your reply01:55
flwangand as for the core reviewer issue, we had discussion about brtknr and another people you mentioned, i even had a private discussion with  brtknr about the core nomination01:57
mnaserI mean we didn't make any changes to flannel yet that code was dropped/removed.01:57
flwangbut based on my observation, he is still a bit new about how magnum works, so i decided to wait a bit and encourage more code contribution from him01:57
mnaserAnd in my personal experiments, if you don't have that iptables command, it won't ever forward any traffic01:58
mnaserThat's documented with people struggling with it all over the place.01:58
flwangmnaser: but i did the test and it works for me, i think same for spyros, that's why we asked how did you setup your environment to try to figure out the root cause01:58
mnaserCan I ask why did we do our conformance tests using calico and not flannel, which is the default driver?  It should be working.01:59
mnaserIt also turns out it largely had to do with the patch I pushed up about introspection of hostname instead of a hardcoded novalocal01:59
flwangyour hostname patch is good and we have already merged it quickly, no?02:00
flwangagain, we're welcome for any contribution since we need the resource02:00
flwangsome of your patches getting slow merging because those comments we have asked in the patch, and you know, there are only me and spyros are active reviewers and we all have full time jobs, so i apologize for the slow review02:02
mnaserI understand, but when I see new features being shipped at the expense of patches not being reviewed, that makes for a pretty poor personal experience, if you put yourself in my place.02:03
flwangi understand that, and i will partially blame the time zone02:04
flwangif we're in same tz, we can trouble shot your flannel issue more easier02:04
flwangfor me, you may don't know, i have to work over night to catch up with the guys from CERN to make things easier and quicker02:04
flwangi have been a long term contributors since 2012, and i feel very bad about the comments from TC team about the project and my ptl role with my showing in the meeting02:05
flwangi worked very hard for glance, for zaqar, for magnum, for ceilometer, for a lot of openstack projects i love02:06
flwangi help openstack magnum to get the CNCF certification, but then I got comments saying that why i didn't use another driver, is it fair?02:07
mnaserThe conformance tests don't mention that the cluster template used was calico. The default driver is flannel02:07
mnaserAnd I have spent way too much time trying to get the certification to work on the default cluster template, my own personal time too :)02:08
flwangthat's not my intention, i will update that. and again, i'm happy to help your flannel issue, but please don't judge that your patch haven't been merged is because we don't care flannel02:09
mnaserIt's important that we have functional default behaviour. If magnum works in some odd combination of cluster templates, then we should fix that rather than have that cluster template02:09
flwangso we have same goal02:09
flwangto make magnum (openstack) better, don't doubt the passion of a long term contributor02:09
mnaserOk, I will spin up a devstack tomorrow and run conformance tests with the default cluster template. I'd be happy to se it work02:09
flwangmnaser: as for function test, as you know, I did also put effort on that02:10
flwangand I can feel the same pain02:10
mnaserI just struggled because personally I felt that every time I pushed code I hit a wall, it would sit around till it hits a merge conflict and I know you're strapped for resources in the project02:11
mnaserTrust me, It's rough in OSA land. Everyone wants a functional deployment tool and no one contributes as much. But it's times like that where you give the key to some members that aren't necessarily as strong but are driven02:11
flwangcore reviewer is another story, i'm very keen to get new core, but i need to make sure their qualified, i can't nominate core if they're not ready02:12
mnaserI've done it twice with two cores and they've grown to be really good. Yes. They'll break your gate or merge something wrong here and there. But that can be fixed.02:12
flwangmnaser: that's good to know and i'm trying to follow that as well02:12
mnaserIt's better to empower people early and give them a chance at being core rather than waiting for the perfect moment, imho.  I think the biggest issue with magnum is the integration.02:13
flwangbesides, i would like you can talk to me or the team directly if you have any problem about using magnum instead of blaming our work with somebody don't know how mangum works02:13
flwangit does hurt me, TBH02:14
mnaserMy apologies. I've just grown to be frustrated because all I hear is "this is not working" and pushing patches results in not much feedback till they merge conflict02:15
mnaserSo put yourself in my shoes when I am doing my best to stand up for OpenStack and that is the sort of thing my users see02:15
flwangthat's why we need irc, and instant talk02:15
ricolinflwang, I can tell how hard it's for you to encourage new people to do review and contribute, looking forward to see those potential candidates ware encouraged and go for it02:16
flwangi understand that, and again, i'm happy to help you for any issue you have, but that doesn't mean i should chase you to help you, you should be more active in the magnum channel to talk to me, isn't it?02:17
mnaserAll I ask is for reviews to be done fairly and prioritizng the reviewing of patches just as much as pushing patches.02:17
mnaserI've pinged a few times the channel for trivial patches to be reviewed and help out when I can in the channel. I don't know what more I can do.02:18
flwangmnaser: my appologies if it's not the case, it should be.02:18
mnaserThere's a long queue of unmerged patches that's growing and seeing patches pushed up from you or other cores and merged while others sit and wait is a very frustrating experience.02:18
mnaserI think that's what it narrowed it down to02:19
flwangthat's because you can have more trust for the patches from other cores, at least for some cases02:21
mnaser(and because of how magnum works, when other big changes merge, they cause a ton of merge conflicts across other patches and it's not motivating to keep rebasing them)02:21
flwangi understand that02:23
mnaserI agree but that's not sustainable for the project. I would prioritize non core patches cause those are the harder ones to come by.  Those are the more casual contributors who might not be as invested in the project and won't have time to rebase and clean up02:23
mnaserVs a core who doesn't mind rebasing and reiterating.02:23
flwangi agree with you and i know it's common in openstack community now02:23
mnaserAnyways, this is all my personal opinion. I could be wrong. That's just my experience. I am sorry that you feel sad because of my comments, I said them out of frustration because I want this project to succeed, it's instrumental in the growth of OpenStack02:24
mnaserI think you're doing as much as you can within your resources and I appreciate it, I really do02:25
flwangthe only thing make me said is, i got those comments from others, i wish you can talk to the team directly02:25
mnaserThere's just a few things that I think if we work together on improving, we'd both do the project and everyone a favour.02:25
mnaserRight, I should reach out personally in the future. By no means was that some sort of private behind-your-back thing.02:26
flwangsuggesting tc to replace the PTL instead of talking to the PTL first, is it a good way the TC would like to do?02:28
mnaserI don't recall making that suggestion.02:29
flwanganyway, i think we're all from a good intention for the project and for openstack. we just need more open communication02:29
flwangmnaser: sorry, i'm not saying you02:30
mnaserI'll leave it for other members to comment about this. I feel personally involved meaning that anything I may say might be biased02:30
flwangi think we better back to the technical issue of magnum, i won't be interested in any political issue02:33
flwangi will run test again for your patch and run sonobuoy against flannel, if there is any issue, i'm happy to help to fix02:34
ricolinI think the conversation is for discuss policy instead of specific cases in general, because I know you're working hard for maintain project.02:35
mnaserThanks, I appreciate it. If you think calico is better, then let's just drop it from magnum so we have an easier matrix of supported configurations02:36
mnaser(fwiw it's 10:36pm and I'm on mobile so I might be in and out)02:37
*** markvoelker has joined #openstack-tc02:40
flwangmnaser: cool, thank you for your time02:45
*** markvoelker has quit IRC02:46
mnaserAnytime02:47
*** lxkong has joined #openstack-tc02:57
*** markvoelker has joined #openstack-tc03:20
*** markvoelker has quit IRC03:25
*** ricolin has quit IRC04:14
*** ricolin has joined #openstack-tc04:21
*** markvoelker has joined #openstack-tc04:40
*** markvoelker has quit IRC04:45
*** jaosorior has joined #openstack-tc05:01
*** ricolin has quit IRC05:02
*** ricolin has joined #openstack-tc05:03
*** adriant has joined #openstack-tc05:24
*** e0ne has joined #openstack-tc05:33
*** e0ne has quit IRC05:44
*** markvoelker has joined #openstack-tc06:40
*** e0ne has joined #openstack-tc06:42
*** e0ne has quit IRC06:43
*** markvoelker has quit IRC06:45
*** e0ne has joined #openstack-tc06:53
*** e0ne has quit IRC06:59
*** ricolin has quit IRC07:15
*** lpetrut has joined #openstack-tc07:29
*** sapd1_ has joined #openstack-tc07:33
*** sapd1 has quit IRC07:37
*** e0ne has joined #openstack-tc08:05
*** diablo_rojo has joined #openstack-tc08:12
*** lpetrut has quit IRC08:31
*** diablo_rojo has quit IRC08:48
asettleMorning o/08:56
aspiersHey all, who can I talk to about Shanghai registration? I registered earlier but still haven't received a confirmation email which I need for the Visa invitation letter request10:10
*** jaosorior has quit IRC10:10
asettleaspiers, you probably want to talk to Allison Price10:12
asettleallison@openstack.org10:12
aspiersasettle: thanks!10:12
asettleNp10:12
*** jaosorior has joined #openstack-tc10:27
*** lpetrut has joined #openstack-tc10:56
*** bauzas has quit IRC11:18
*** bauzas has joined #openstack-tc11:18
jrollflwang: I agree with ricolin. I believe the part about replacing the PTL was a more general statement that if the TC needs to override a PTL to add core reviewers, it means we've already decided the PTL is not doing their job and should just replace them. it wasn't about you or magnum, that was just the case that brought it up. that's a very last resort, we don't want to replace you :)11:19
jrollmnaser | It's better to empower people early and give them a chance at being core rather than waiting for the perfect moment, imho.  I think the biggest issue with magnum is the integration. <- +1000 on this. it's worked well in ironic too.11:19
*** jaosorior has quit IRC11:26
asettleClarification point, tc-members - on a post like this where it's a typo-fix https://review.opendev.org/#/c/677820/1 - do we really require the full team + chair to approve?11:42
asettleSorry, I realise in the house rules it says it does not require the team - apologies11:43
asettleBut the chair?11:43
*** jaosorior has joined #openstack-tc11:43
jrolladding a magnum core, thanks flwang! :) http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008680.html11:54
*** markvoelker has joined #openstack-tc11:57
mugsieasettle: that patch has a parent one that hasn't merged either doesn't it?12:02
asettleSigh. Yes so it does. I didn't look properly, thanks. Any reason why you won't update the initial patch, zaneb ?12:03
mnaserasettle: have you checked out the tox target to check review status ?12:03
asettlePor que?12:04
mugsieasettle: he didn't want to loose the votes from the base patch12:13
asettleAh12:14
asettleCoolio hoolio12:14
dhellmannasettle : historically only the chair could approve patches because of gerrit settings, but with vice-chair and chair-emeritus members in that gerrit group now I expect we could update the house rules12:17
fungii expect as long as it's a known rule that more folks are allowed to approve things with certain topics set (as long as they confirm it really meets the rules for those topics) then we could trust tc members not to approve things the chairs are obligated to approve12:21
fungii don't really feel strongly either way on that12:22
fungibut nothing in git is permanent, and revert is pretty easy12:22
mugsieyeah, my default is trust the people. (also, see ^ discussion about fast tracking cores)12:22
fungii also prefer an environment where people are empowered and allowed to occasionally make mistakes (i make mistakes after years of being core on a project, after all)12:24
asettle... well worded fungi - literally what I was just typing.12:24
fungimy main expectation is that people fix the mistakes they make when at all possible ;)12:24
asettleFair12:28
fungior *at least* learn what was necessary for their colleagues to do to fix it12:29
openstackgerritGraham Hayes proposed openstack/governance master: Any member of the TC can approve fast tracked patches  https://review.opendev.org/67821212:32
mugsieasettle: fungi mnaser ^^ minor change with https://review.opendev.org/678214 should open this up12:35
mnaserwait, all TC's have +W?12:39
mnaseri thought i only had that magic button12:39
mnaser>:(12:39
mugsiewe dont12:39
mugsiethat change adds it to all of us (if approved)12:39
asettleOh I have it...12:45
asettle>.>12:45
asettleFor that one, yes12:45
asettleWow I should read before typing12:45
asettleOh wait no I have it on all of them12:46
asettleAh, based on the topic12:46
asettleTIL12:46
mugsieasettle: you have it, as you are vice chair12:47
asettleI do12:47
mugsiehttps://review.opendev.org/#/admin/groups/206,members12:47
asettleThat's fun12:47
asettleWho gave me that responsibility hahhhh12:47
* mugsie says nothing :) 12:47
asettleHey hey12:49
asettle-.-12:50
*** jaosorior has quit IRC13:14
*** lbragstad_ has joined #openstack-tc13:24
*** lbragstad has quit IRC13:25
*** lbragstad_ is now known as lbragstad13:31
*** bnemec has joined #openstack-tc13:34
*** gagehugo has quit IRC13:34
*** bnemec is now known as beekneemech13:35
*** mriedem has joined #openstack-tc13:37
openstackgerritMerged openstack/governance master: Add ansible-role-uwsgi to projects  https://review.opendev.org/67619313:54
*** lpetrut has quit IRC14:54
*** cmurphy is now known as cmorpheus15:09
*** gagehugo has joined #openstack-tc15:24
*** jamesmcarthur has joined #openstack-tc15:47
*** lbragstad is now known as elbragstad16:00
*** kmalloc is now known as needscoffee16:00
*** needscoffee is now known as needsSoMuchMoreC16:00
*** needsSoMuchMoreC is now known as needscoffee16:00
*** beekneemech has quit IRC16:07
*** bnemec has joined #openstack-tc16:20
openstackgerritJeremy Stanley proposed openstack/project-team-guide master: Add [elections] ML subject tag  https://review.opendev.org/67827016:28
*** markvoelker has quit IRC16:39
*** markvoelker has joined #openstack-tc16:47
*** bnemec has quit IRC16:53
*** jamesmcarthur has quit IRC17:11
*** jamesmcarthur has joined #openstack-tc17:11
*** jamesmcarthur has quit IRC17:22
*** e0ne has quit IRC18:46
*** bnemec has joined #openstack-tc19:10
*** bnemec is now known as beekneemech19:11
*** jamesmcarthur has joined #openstack-tc19:28
*** jamesmcarthur has quit IRC19:32
*** jamesmcarthur has joined #openstack-tc19:32
*** jamesmcarthur has quit IRC19:43
*** jamesmcarthur has joined #openstack-tc19:45
*** jamesmcarthur has quit IRC19:50
*** weshay is now known as weshay_MOD20:10
*** jamesmcarthur has joined #openstack-tc20:14
*** jamesmcarthur has quit IRC20:18
*** jamesmcarthur has joined #openstack-tc20:19
*** needscoffee is now known as kmalloc21:32
*** jamesmcarthur has quit IRC21:46
*** jamesmcarthur has joined #openstack-tc21:48
*** jamesmcarthur has quit IRC21:50
*** jamesmcarthur has joined #openstack-tc21:51
*** jamesmcarthur has quit IRC22:07
*** jamesmcarthur has joined #openstack-tc22:07
*** jamesmcarthur has quit IRC22:13
*** mriedem has quit IRC22:27
*** jamesmcarthur has joined #openstack-tc22:31
*** jamesmcarthur has quit IRC22:37
*** jamesmcarthur has joined #openstack-tc22:39
*** jamesmcarthur has quit IRC22:46
*** jamesmcarthur has joined #openstack-tc22:50
*** tonyb[m] has joined #openstack-tc22:55
*** jamesmcarthur has quit IRC23:01
*** jamesmcarthur has joined #openstack-tc23:15
*** jamesmcarthur has quit IRC23:17
*** jamesmcarthur has joined #openstack-tc23:19
*** jamesmcarthur has quit IRC23:22
*** jamesmcarthur has joined #openstack-tc23:22
*** beekneemech is now known as keanu23:26
*** keanu is now known as beekneemech23:27
*** jamesmcarthur has quit IRC23:32
*** jamesmcarthur has joined #openstack-tc23:38
*** jamesmcarthur has quit IRC23:42

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