Friday, 2018-08-31

*** mtreinish has quit IRC00:07
*** mtreinish has joined #openstack-tc00:08
*** lbragstad has quit IRC00:12
*** lbragstad has joined #openstack-tc00:14
*** harlowja has quit IRC00:34
*** annabelleB has quit IRC00:39
*** mriedem_lawnboy is now known as mriedem01:04
*** mriedem has quit IRC01:10
fungizaneb: i have never agreed more strongly with anything in my life01:42
*** ricolin has joined #openstack-tc01:58
*** annabelleB has joined #openstack-tc02:10
*** jamesmcarthur has joined #openstack-tc02:23
*** jamesmcarthur has quit IRC02:27
*** jamesmcarthur has joined #openstack-tc02:32
*** jamesmcarthur has quit IRC02:36
*** annabelleB has quit IRC03:34
*** jaypipes has quit IRC04:04
*** jaypipes has joined #openstack-tc04:04
*** Bhujay has joined #openstack-tc04:18
*** jamesmcarthur has joined #openstack-tc04:46
*** jamesmcarthur has quit IRC04:50
*** Bhujay has quit IRC06:20
*** e0ne has joined #openstack-tc06:50
*** e0ne has quit IRC06:52
*** jamesmcarthur has joined #openstack-tc07:34
*** jamesmcarthur has quit IRC07:38
*** Bhujay has joined #openstack-tc07:41
*** jpich has joined #openstack-tc07:41
*** Bhujay has quit IRC08:17
ttxHeh, funny that they consider they are fully-elected, while deciding on a make-up of "represented groups"08:20
ttxOverall, ODL's system sounds like a great way to ensure politics is present in every technical discussion08:22
ttxWhile we are trying to separate those as much as we can08:22
ttxmnaser: thx for the pointer08:23
*** e0ne has joined #openstack-tc09:01
*** dtantsur|afk is now known as dtantsur09:07
-openstackstatus- NOTICE: Jobs using devstack-gate (legacy devstack jobs) have been failing due to an ara update. We use now a newer ansible version, it's safe to recheck if you see "ImportError: No module named manager" in the logs.09:58
*** cdent has joined #openstack-tc10:21
*** Bhujay has joined #openstack-tc10:21
*** Bhujay has quit IRC10:26
cdentttx i add many words and a bit of historical perspective on https://review.openstack.org/#/c/598380/10:47
cdentthere are quite a few people who pretty badly want a planned deadline10:48
*** e0ne has quit IRC11:44
*** ricolin has quit IRC11:48
*** tonyb has quit IRC12:02
*** tonyb has joined #openstack-tc12:19
dhellmanncdent : to be clear, I'm asking for a *timeline* not a *deadline*12:39
*** jaypipes is now known as leakypipes12:44
cdentdhellmann: I know. But there are people who have asked for a deadline, so I'm trying to represent that.12:45
dhellmannok, that's fine12:46
dhellmannjust making sure I'm being clear, since melwitt also seemed to think I was asking for a deadline12:46
cdentdhellmann: it's difficult, to say the least, to balance the many inputs12:46
cdentI've tried to be fair and not let my own position overly impact the infra and governance gerrit changes while still reflecting the goals people have expressed12:48
* dhellmann wonders how long it will be before someone remembers to teach stackalytics about stein12:48
dhellmannyeah, that's another reason I want to see a plan written down and agreed to -- some of the folks involve seem reluctant to hold a position strongly12:49
dhellmannor at least strongly and publicly12:49
cdentAs far as I can tell, when I express my position strongly and publicly, that makes other people entrench, so I'm reluctant to do so, often. I wonder if other people have the same concern.12:50
* cdent has to disappear in ten minutes12:50
*** cdent has quit IRC12:55
*** e0ne has joined #openstack-tc12:55
*** EmilienM is now known as EvilienM12:57
*** tosky has joined #openstack-tc13:02
*** lbragstad is now known as elbragstad13:37
zanebttx: a few countries have had constitutions like ODL's system, and they pretty regularly seem to end up having coups, if not outright civil wars14:02
leakypipeszaneb: ODL or OpenStack?14:05
zanebODL14:05
zanebleakypipes: https://slides.com/dfarrell07/appointed-to-elected-gov14:06
ttxleakypipes: you'll love this model14:07
ttxbuilding vendor fights into the governance model :)14:08
*** jamesmcarthur has joined #openstack-tc14:08
ttxzaneb: the other weird thing is that they insist that candidates should be regular contributors. So they take good people and force them to wear company hats in governance discussions14:09
zanebyeah, in other circumstances that would have been a _good_ move14:10
zanebI liked that they're trying to encourage the people doing the work to be elected, instead of managers14:10
ttxI think it's a like they know what a good model looks like, but are set up with weird initial constraints14:11
zanebyes, I imagine this was the compromise needed to get those companies to give up autocratic control14:11
ttxdo what you want, but we need "represented groups".14:12
leakypipeszaneb: I agree with his Tips slides. However, I think he's built an overly complex and bureaucratic "electioneering" system, IMHO.14:13
zanebI'm sure they're doing the best they can with what they have, but I'm really glad to be a part of _this_ community <314:13
*** mriedem has joined #openstack-tc14:15
openstackgerritMerged openstack/governance master: make the board repo list file format consistent with others  https://review.openstack.org/59835014:17
*** cdent has joined #openstack-tc14:26
*** jaosorior has quit IRC14:43
*** annabelleB_ has joined #openstack-tc15:08
*** annabelleB_ has quit IRC15:08
*** e0ne has quit IRC15:14
*** ricolin has joined #openstack-tc15:37
*** e0ne has joined #openstack-tc15:45
*** annabelleB_ has joined #openstack-tc15:50
*** e0ne has quit IRC15:56
*** annabelleB_ is now known as annabelleB15:57
*** jpich has quit IRC15:59
*** openstackgerrit has quit IRC16:06
mnaserfwiw: I think the TC is stepping in with regards to the placement topic n16:10
mnaserBecause it looks like we’re overriding the decision of the PTL16:10
mnaserso my question is are we being asked to step in and intervene and vote something against the will of the PTL of this project, because it looks like we’re doing that in this case.16:11
smcginnisWell, counter argument - we're allowing the PTL of one project to dictate the actions of another project. A bit chicken and egg though.16:12
mnaserI still think we should move with the technical deliverable change and I would like to have a conversation with all those parties at Denver to help Nova vocalize what they think the best way to go about it is, and then moderate the conversation between the two teams16:12
mnaserIf the two teams can’t come to an agreement, we step in based on the information provided16:12
mnaserIt would circle back to the things dhellmann asked about timeline and steps needed16:13
zanebmnaser: the thing we're voting on *is* the technical deliverable change16:13
mnaserIf melwitt has a very rational reason that she’s deciding X results need to be met for the split to happen, then I think we should listen to her and the Nova team16:14
mnaserWell the deliverable change shouldn’t have anything about timeline in it then.16:14
smcginnisThe splits not going to happen if things aren't in place.16:14
zanebbut I do think we need to have an in-person discussion with the Nova/placement team at the PTG16:14
mnaserAnd they are going in place slowly16:14
smcginnisWhether they say they want it to happen next week or next year.16:14
mnaserThe repo has been created16:15
mnaserThat’s why I’m proposing to do an actual sit down16:15
smcginnisNo ones going to say today's the day and pull the rug out.16:15
persiaSemantics are tricky.  If there are two teams, then there are two teams.  If there is one team, tehre is one team.  Talk of two teams being one team needs more thought.16:15
mnaserHoping that both parties are present and we talk it out openly and honestly so both teams can come to terms16:15
mnaser(taking off soon so might fall off but be back in a bit)16:16
mnasersmcginnis: i worry that pulling the rug is what might happen. That’s why we need to16:16
mnaserBe clear about the technical challenges early.16:16
mnaserCome to agreement on those16:16
smcginnisI'm a mildly shoked by that concern.16:17
mnaserLet’s be honest: given how all of this has went down16:17
mnaserIt hasn’t been good for either “sides” and I put sides in quotes.16:17
mnaserSo again, we move with adding a deliverable and setup a time to sit down with both teams and help them16:18
mnaserCome to an agreement16:18
mnaserAnd if we feel that one side is being too far off, we can talk then but I don’t think any of that will happen and we’ll have a criteria to say this is the right time to do it16:18
mnaserBecause I don’t think the criteria is time but *actual* technical solution of the split16:19
zanebmnaser: to be fair, I thought there was an agreement to for an agreed timeline for the split, but the comment from melwitt appears to indicate that the Nova team is not willing to compromise even the tiniest bit to throw the placement folks a bone16:20
*** mriedem is now known as mriedem_away16:21
zanebthe other interpretation is that melwitt's comment is a minor nitpick over wording of the commit message16:21
melwittI don't think it's fair at all to accuse me of not compromising through this whole situation16:21
mnaserI think the team starting to split things off is a step from the Nova team that was TC blessed.16:26
mnaserErr PTL blessed16:26
zanebmelwitt: ok, but I'm feeling very blindsided here because it was my understanding that a compromise had been agreed, but apparently it had not and the official position of the Nova project does not appear to have budged at all from the pre-compromise position16:27
dansmithzaneb: seriously?16:28
zanebalternatively, it's just a disagreement over whether 'expected' means 'carved in stone'16:28
melwittzaneb: I think I was very clear in my ML posts. I said that I thought the governance switchover should be done after we get critical work items done with nova/placement teams as one group16:28
melwittI never said or agreed to "we expect to switch governance at chosen milestone s-2"16:29
zanebmy understanding of the existence of the compromise agreement was based on IRC discussions16:29
zanebit appears that those discussion were not representative of the opinion of the whole group16:29
melwittmy lack of comment was not to be taken as agreement. this whole situation has been extremely stressful for me and I'm having a hard time keeping up with the constant pressuring, despite all of the time I've taken to write detailed emails about my position16:30
dhellmannI think I've reached the point where I need something more definitive than another mailing list thread or IRC conversation where not everyone is participating in order to understand what the agreement actually is. I don't know if that means a spec, or something else. That's why I'm asking for "a plan" to be written down, so we get get everyone to sign off and stop going back and forth about the details.16:36
melwittyeah, I think that's a good idea. we usually do things like that via etherpad16:40
melwittI'm not sure how we could do it in gerrit, we haven't used a spec in that way before16:41
scasetherpad was my armchair thought. specs tend to introduce a lot of latency due to being embedded in the code review process16:42
scasmaybe a spec somewhere as a means to codify the resolution itself, if one were so inclined, but that's more work16:44
zanebI guess the advantage of Gerrit is we can see exactly who has and has not reviewed it, and thus avoid the non-representative-subset-in-the-discussion problem16:45
scasfrom my perspective, i interpreted things as "this was always meant to happen". the opposition, to me, seemed to be more of a "not right now" approach, and not a "thou shalt not" one. but, that's my take. without things being defined as verbosely as, say, constitutional law, interpretation is everything16:48
scasi'm mostly just following along to see how/where i need to adapt my thing16:49
melwittthat's correct. we are in the middle of challenging integration work (first use of a placement feature) where being one group helps us to get the work done16:51
melwitt(we're integrating nested resource providers into nova to enable vGPU enhancements, for one)16:52
melwittI have been saying, let's extract the code, make sure it works with it being its own package, upgrades work, then let's agree on some critical work items that would be best worked through as one group where we can say, when we complete those, we split the governance16:54
dhellmannan etherpad works for me, as long as it includes a list of all of the folks who should be agreeing and then an explicit ack from each of them somehow16:57
dhellmannthat's easier with gerrit, as zaneb points out, but we can make an etherpad work too16:58
cdentI left a comment on the patch asking what people want it to say, so we can at least move that part forward.17:01
cdentI wish that being earnest wasn't such a firestarter.17:02
scasi see the advantage of gerrit, which is why i followed up with an out-loud thought about a spec to ratify the resolution. it's more work for all, but it preserves the spirit of democracy17:05
melwittI agree on being earnest. I've been earnest that I want to prevent disruption to our ability to deliver enhancements for users and extracting code obviously disrupts it. but since there's never a "good" time to extract code, I've said OK, let's extract it now as a compromise to make some progress. and I say, let's agree on a set of work items to get done before we split governance and not maximally disrupt our ability to deliver for17:08
melwitt users. and then I'm told I'm unwilling to compromise and receive lots of fire upon me17:08
cdentmelwitt: I left a pretty direct question for you in my latest comment. I don't understand how changing governance makes us any less "one group". I'm not denying that people feel that way, I'm saying "I don't understad"17:08
cdentfrom my standpoint I don't think you're unwilling to compromise. I think people watching us are jumping to bigger conclusions than are really there17:09
scasin the information age, perceptions are larger than reality17:09
cdentyou're right: the extraction (already begun) is the bigger disruption to being able to deliver than any other potential change17:09
melwittcdent: you have stated yourself that you want to split groups so that placement can have its own priorities, independent from nova. and I'm saying, let's keep our priorities the same for at least some set of critical work items where close cooperation is needed17:10
cdentthat's long term melwitt, and for the most part that is so _nova_ can have its own priorties. I've felt for the the last year that nova has been too placement (server-side) focused17:10
melwittcdent: I totally agree that it's long term. and that should be when we split governance, is when we are ready for that, IMO17:11
cdentI want use to slow down the server-side and only deal with making the things people want to do with existing functionality (shared disk, nested rp, happen) for _all_ the projects17:11
cdentso you're concerned that the "all the projects" part will be detrimental to nova's goals? I disagree. I think nova will hugely benefit from a more diverse group of people (eventually) exercising placement. fewer bugs is the big one.17:12
edleafeWhat I don't understand is that if the placement cores are the nova cores, how there could be any divergence of priorities17:13
melwittI understand that, but currently we are in the position where server side features have _never_ been used before (NRPs) and I think first-ever integration should be done while we are one group. it will likely need fixes on the server side, based on previous experiences we've had17:13
cdentmost of the placement-side functionality for pending stuff is in place (as matt has pointed out many times)17:13
*** ricolin has quit IRC17:14
cdentI guess we'll just have to disagree on "while we are one group". I feel like we always will be but that if you feel like we won't be when governance changes (because, apparently, that will change priorities) then we aren't one group now17:14
melwittedleafe: because that's the point of having separate governance. it means you are an independent group with the ability to have independent priorities. I think it's premature given the work we're still in the middle of17:14
scaswhat i'm curious about is what is the urgency on going through the motions? to put a firm-yet-malleable date on the actual motions, seems totally reasonable to me, without doing things so close to a release. this is just my peanut gallery interpretation, but stein is a longer cycle17:16
melwittcdent: maybe, but it's a big step that we can't come back from, if we take it. I'd rather we just sit down and agree to some set of work items to get done before we call it. we will split the governance, I would like it to be based on a real work milestone17:16
edleafemelwitt: I would agree if we started with a completely different team. The idea of making all nova cores as cores in placement is so that while those critical pieces are in play, the behavior will be the same either way. Over time, though, the number of nova cores actively involved in placement will diminish, and new people drawn to the project will become engaged, and possibly merit core status17:16
cdentmelwitt: do you agree with jay and matt that this is a people problem? If not, what are they talking about that you disagree with?17:17
melwittedleafe: I understand where you're coming from, but I still think it's premature. we've only just started the code extraction and we have important work to do that I think makes most sense while we are still one group, before we split17:18
*** annabelleB has quit IRC17:19
melwittcdent: I don't know, I've been focused on the work we need to get done, the biggest one being NRPs integration. I'm doing my best to ensure that happens as smoothly as possible, and I think being one group under compute is the smoothest path for it17:20
melwittideally, we wouldn't be extracting code in the middle of it, but I am trying to get where you're coming from to make some progress there, so we're doing it17:21
* cdent nods17:21
cdentI'm grateful for that.17:21
* leakypipes will have to remember the term "firm-yet-malleable"17:23
melwittI'd like for us all to have a serious discussion about splitting the governance and not make arbitrary dates for a cutover. I hope, as a group, we can agree one some minimal set of work items to do and then we split it after that17:23
cdentBut I'd like to reiterate: I'm just trying to do my job. This is a thing we'd say we'd do. I've been working on it for going on 2.5 years. Had I my druthers we never would have started in nova in the first place, but we did, and that was okay. My efforts these past couple of weeks have just been trying to bring all the necessary people together to make it happen. It wasn't suppose to be a cluster fuck, and I'm still not s17:23
cdentwhy it has been.17:23
melwittI too, am just trying to do my job17:24
scasagreeing past one another: a time-honored technology tradition17:24
cdentmelwitt: yeah, and I really do appreciate that. I sometimes feel like we're caught in the crossfire of something that's going on where we can't quite see17:25
elbragstadi can relate to the concern about things taking longer even involving multiple groups or even just repositories (this is something we deal with quite a bit in keystone)17:26
cdentI'm sorry, I have to go, will catch up later17:28
melwittI think we've pretty much wrapped up here for now. I'd like to get back to work too o/17:30
*** jamesmcarthur has quit IRC17:30
*** jamesmcarthur has joined #openstack-tc17:34
*** annabelleB has joined #openstack-tc17:37
*** jamesmcarthur has quit IRC17:45
*** mriedem_away is now known as mriedem17:50
*** annabelleB has quit IRC17:58
*** dtantsur is now known as dtantsur|afk17:59
* dims catches up18:02
*** annabelleB has joined #openstack-tc18:04
*** annabelleB has quit IRC18:30
dimsdoes FNTECH have one of the throwable microphones?18:35
dimswould be handy when we get everyone in a room and have to pass it around (doubles as a talking stick)18:35
leakypipesdims: heh.18:37
smcginnisBased on the ups and downs here, I'm not sure throwing things is a good idea. ;)18:37
dimshahahaha smcginnis18:41
dimssmcginnis : when i was chaperoning some 4th graders, i threw a clementine to my son (during lunch, not too far!) and got yelled at by the teacher-in-charge!18:42
*** annabelleB has joined #openstack-tc18:46
smcginnisdims: Hah, naughty naughty.18:47
dimskids still remind me to this day :)18:47
zanebdims: lol18:48
dimsi clearly don't learn my lessons :)18:49
*** tosky has quit IRC18:52
*** openstackstatus has quit IRC18:58
*** annabelleB has quit IRC19:32
*** e0ne has joined #openstack-tc19:36
*** openstackstatus has joined #openstack-tc19:39
*** ChanServ sets mode: +v openstackstatus19:39
*** openstackstatus has quit IRC19:55
*** openstackstatus has joined #openstack-tc19:58
*** ChanServ sets mode: +v openstackstatus19:58
cdentgoodnight20:02
*** cdent has quit IRC20:02
*** e0ne has quit IRC20:06
*** openstackstatus has quit IRC20:11
*** openstackstatus has joined #openstack-tc20:12
*** ChanServ sets mode: +v openstackstatus20:12
*** openstackstatus has quit IRC20:36
*** openstackstatus has joined #openstack-tc20:38
*** ChanServ sets mode: +v openstackstatus20:38
*** harlowja has joined #openstack-tc20:46
*** annabelleB has joined #openstack-tc20:55
*** e0ne has joined #openstack-tc20:56
mnaserIn regards to having a discussion, I drafted up an email about this subject and I agree we all just need to sit and discuss this.20:58
*** cmurphy|vacation is now known as cmurphy20:58
*** e0ne has quit IRC21:00
jbrycedims: We've tried those throwable mics before with limited success. I'll see if they still have one lying around21:00
dimsthanks jbryce !21:01
*** jamesmcarthur has joined #openstack-tc21:44
mriedemplease no mics21:59
mriedemmics are always a pain in the ass at these things21:59
mriedemif you want to be part of the discussion, speak up and/or sit near the discussion21:59
*** annabelleB has quit IRC22:00
mriedemi think we've consciously tried to spread out the big mouths at the ptg in recent times to try and avoid side discussion22:01
*** elbragstad has quit IRC22:02
*** EvilienM is now known as EmilienM22:04
*** tosky has joined #openstack-tc22:09
*** annabelleB has joined #openstack-tc22:21
*** harlowja has quit IRC22:24
*** mriedem has quit IRC22:32
*** zaneb has quit IRC22:48
*** zaneb has joined #openstack-tc22:48
*** annabelleB has quit IRC22:51
*** annabelleB has joined #openstack-tc22:58
*** jamesmcarthur has quit IRC23:01
*** jamesmcarthur has joined #openstack-tc23:10
*** tosky has quit IRC23:14
*** jamesmcarthur has quit IRC23:15
*** annabelleB has quit IRC23:18
mrhillsmanlol23:23
fungiseating charts!23:24
*** jamesmcarthur has joined #openstack-tc23:31
*** jamesmcarthur has quit IRC23:40
*** jamesmcarthur has joined #openstack-tc23:53
*** jamesmcarthur has quit IRC23:57
*** jamesmcarthur has joined #openstack-tc23:58
*** jamesmcarthur has joined #openstack-tc23:58

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