Friday, 2018-07-27

*** david-lyle has joined #openstack-tc00:03
*** harlowja has joined #openstack-tc00:05
*** dklyle has quit IRC00:06
*** dklyle has joined #openstack-tc00:12
*** dklyle_ has joined #openstack-tc00:14
*** david-lyle has quit IRC00:14
*** dklyle has quit IRC00:17
*** harlowja has quit IRC01:17
*** ricolin has joined #openstack-tc01:45
*** dklyle has joined #openstack-tc01:49
*** dklyle_ has quit IRC01:50
*** david-lyle has joined #openstack-tc02:01
*** dklyle has quit IRC02:02
*** david-lyle has quit IRC02:03
*** dklyle_ has joined #openstack-tc02:04
*** rosmaita has quit IRC02:55
*** diablo_rojo has quit IRC03:58
*** mriedem has quit IRC04:04
*** diablo_rojo has joined #openstack-tc04:46
*** diablo_rojo has quit IRC05:01
*** diablo_rojo has joined #openstack-tc05:46
*** dtantsur|afk is now known as dtantsur07:21
*** kfox1111 has quit IRC07:36
*** dtantsur is now known as dtantsur|bbl08:00
*** jpich has joined #openstack-tc08:06
*** bauzas is now known as PapaOurs08:19
*** e0ne has joined #openstack-tc08:22
*** diablo_rojo has quit IRC08:22
*** jaosorior has quit IRC08:38
*** jaosorior has joined #openstack-tc08:58
*** cdent has joined #openstack-tc09:18
*** jaosorior has quit IRC09:49
*** johnthetubaguy has quit IRC09:52
*** cdent has quit IRC10:27
*** dtantsur|bbl is now known as dtantsur10:49
*** cdent has joined #openstack-tc11:28
*** edmondsw has joined #openstack-tc12:17
*** johnthetubaguy has joined #openstack-tc12:17
fungiwhy have i never heard of https://www.loomio.org/ until now?12:28
fungihttps://github.com/loomio/loomio is the source code12:30
fungian interesting alternative to traditional rigid survey models, at least12:32
*** diablo_rojo has joined #openstack-tc12:33
*** mriedem has joined #openstack-tc12:35
smcginnisfungi: Cool, I never heard of that either.12:47
scaswe're part of the 10,000!12:49
scasi, too, have never heard of that12:49
scasobligatory: https://xkcd.com/1053/12:49
smcginnisheh12:52
scasi'm not going to like it, you're not going to like it, but my gut says i'll be self-approving chef changes until such time i can recruit someone else to review12:55
smcginnisDesperate times...12:57
scasin the past, conversations have come up, at least before kubernetes ate the core team, about moving the cookbooks to github. my gut feeling also says that that would be worse off than staying within the current model and 'just making it work'13:02
cdentscas: was the theory there that moving to github would make the cookbooks more visible to random people who want a drive-by interaction rather than the current model?13:03
smcginnisscas: Do you see any chance of moving that leading to potentially more casual contributors?13:03
smcginnisHah, what cdent saud.13:03
smcginnis*said13:03
scascdent: smcginnis: the theory being that ramping up on contributing with the openstack space elicited too much friction, not to mention learning chef openstack's nuances13:04
scasit's very purpose-built stuff. bringing it in to the openstack space years ago made sense because it would have been seen as just another random fork of cookbooks13:04
scasin fact, it was seen as just another random fork, until the big tent notion came about13:05
smcginnisI could see having it here would make it more official.13:05
scasmoving to the github model would place a significant amount of burden on maintainers, as instead of one place for filing regressions or soliciting feedback, i suddenly have 16 repos all with issues and prs of their own13:06
scasi have a singular view within openstack, so it's easier, for me, to wrangle all of the repos at once13:07
scasi've simply failed to show others how that can be13:07
scasto enact any significant change, one can't just grab one repo and hack on it13:08
scasas far as it attracting more casual contributors, github feels like more of a death knell than me whinging for a bit, then going back to working on docs or integration efforts13:11
scasi've had similar conversations within sous-chefs, which lives entirely on github. they have a decent model, but the platform of choice is a shifting sand13:12
smcginnisscas: Yeah, I would be a little worried that it might enable a few casual contributors at the expense of long term project health.13:12
scasit's not talked about often, but chef still enjoys a silent userbase13:15
scasi like for those users to be happy, even if they don't dedicate resources. it's stockholm syndrome from running my own b2b companies13:15
smcginnis:)13:16
cdentbbl13:16
*** cdent has quit IRC13:16
scasaside from 'Other Tool' having more deployment share, chef sits at the #3 deployment choice in the openstack space. as far as i can tell, they're mostly in production13:19
scasthere's somewhat of a motivator to keep that momentum going, however protracted it may be13:19
scasparticularly since the percentage increased by 1% from survey to survey13:20
scasthat could be an artifact of a shrinking segment, but, still, numbers are numbers13:20
smcginnisscas: I wonder if doing a superuser article might be a way to attract attention to the project.13:29
scascould be. every could of years, someone has put on a presentation or a superuser talk13:29
scass/could/couple/13:29
*** rosmaita has joined #openstack-tc13:30
scasi intended to present at vancouver with onboarding and an update. an unfortunate set of circumstances precluded me from being there13:30
scasat this point, i can see the next chance to present to the purpose-built crowd being the T summit, unless there are onboarding/updates happening at berlin and i happen to make it13:32
scassuperuser would be the next best thing, so i can show what we've done. a lot of work has gone into the 'just give me openstack' experience13:36
scasallinone may be the best supported scenario, which comes just shy of melting a macbook pro13:36
scasthat, and getting docs.o.o presence to better flesh out the choices that do exist13:38
scasi'll probably want to do a superuser article after the gerrit downtime and i can rewrite my docs to make them actually publishable13:45
TheJuliascas: Perhaps projects which you consume or support (in terms of install/config) could mention the that level of support in order to kind of an indirect interest?13:45
TheJuliaLike, if there is ironic support, I would happily dedicate a slide or two13:46
TheJulia(during the ironic project update that is)13:46
scasused to be, but we couldn't maintain it even at low numbers13:47
scasthere's a cookbook, but it needs to be refactored by an order of magnitude13:47
scasthere are several of those13:47
scas'core' is fairly well supported except swift13:48
scasin 3 years, we had maybe 1 bug on swift13:49
scasthat was in the dark ages, when integration was fraught with error, before tempest. no way it was that stable then13:49
scasback then, there numbered nine cores13:50
TheJuliaIt might be worthwhile to reach out to some PTLs of core projects so they have visibility and can convey that?13:51
scasthat might be worthwhile. i think the value may be better conveyed if i do that after the gerrit downtime. html docs look better than my walls of text13:53
*** ianychoi has joined #openstack-tc13:56
scasa few days of solid coffee-addled coding would probably get other services supported. ENOTIME beholden, unfortunately13:58
*** ianychoi_ has quit IRC14:00
scasmy backlog includes resurrecting those 'unsupported' services14:00
*** annabelleB has joined #openstack-tc14:08
*** annabelleB has quit IRC14:11
TheJuliaENOTIME is a common thing sadly :(14:11
*** diablo_rojo has quit IRC14:22
*** cdent has joined #openstack-tc14:32
*** diablo_rojo has joined #openstack-tc14:46
scasmost projects are one or two code repositories at best. i surprise myself sometimes that i can wrangle something with the breadth and depth as chef openstack14:54
scaswith someone to review what i write, a superuser article may breathe a little on the embers that exist. it'll make more sense once i can give links to functional docs15:00
lbragstad_smcginnis: the deadline for completing community goals work is supposed to be rocky-3 yeah?15:03
lbragstad_https://releases.openstack.org/rocky/schedule.html15:03
smcginnislbragstad_: Yeah... sadness.15:04
lbragstad_ok - i assume we have to wait until Stein to implement that then? We were waiting on a massive refactor in order to implement the mutable config goal15:05
smcginnislbragstad_: Yeah, if keystone hasn't done that yet, with feature freeze you probably want to wait until Stein now.15:05
lbragstad_ack15:05
lbragstad_thansk smcginnis15:06
lbragstad_cc knikolla ^15:06
smcginnislbragstad_: Unless you think it would be minor and low risk to still get in, but at this point I would think waiting is good.15:06
scasspeaking of releases, the code told me it's time to release chef openstack. better late than never15:07
scasthat would give me that area of time to get with the program on the releases repo15:07
scasthere's no harm in waiting for the coordinated release to send it out, other than timing, and me getting a start on the next one sooner than later15:09
smcginnisscas: Hmm, looks like we've never done Chef OpenStack official releases?15:12
smcginnisscas: Usually deployment projects like chef follow the cycle-trailing model that gives some time after everything else wraps up to finalize things.15:12
smcginnisscas: Since they are also consumers of everything else, so there's usually time needed to adjust to any last minute changes.15:13
scascycle-trailing is generous ;)15:13
scasENOTIME beholden, it takes me (with someone else to review) roughly a six months to stabilize15:14
scasif i slam patches in as they pass tests, i can probably cut that time down, at the risk of stability. my compensation there is focusing on the integration story15:14
smcginnisscas: I think right now we just raised the trailing time from 2 weeks to 2 months. :)15:15
scasvery generous.15:16
smcginnisscas: But even with cycle-trailing, we do require at least two milestone releases during the cycle as checkpoints. So it would be too late to get chef added to rocky.15:16
*** e0ne has quit IRC15:16
smcginnisscas: But it would be good if we can shoot to get things going in stein.15:16
scassmcginnis: yep. i know.15:16
*** annabelleB has joined #openstack-tc15:16
scasi'm planning on short-ordering rocky support as soon as stable packages drop. the time, again, is usually waiting for reviews to happen. i'd like to get coordinated for stein15:17
smcginnisscas: Great. Let me know if/when you have time for getting things set up.15:17
smcginnisscas: Maybe getting as part of the official cycle deliverables could be another good step to get more visiblity for the project.15:18
scasthat's the idea. mitaka was painful, and it's been difficult to catch up15:18
scastaking a more 'benevolent dictator' approach is about the only way to get with the times15:19
scasesr definition, natch15:19
*** hongbin_ has joined #openstack-tc15:39
-openstackstatus- NOTICE: A zuul config error slipped through and caused a pile of job failures with retry_limit - a fix is being applied and should be back up in a few minutes15:40
*** ChanServ changes topic to "A zuul config error slipped through and caused a pile of job failures with retry_limit - a fix is being applied and should be back up in a few minutes"15:40
*** diablo_rojo has quit IRC15:42
*** jpich has quit IRC16:06
*** lbragstad_ is now known as lbragstad16:11
*** mriedem is now known as mriedem_away16:15
*** harlowja has joined #openstack-tc16:27
*** zaneb has quit IRC16:38
*** zaneb has joined #openstack-tc16:39
*** ricolin has quit IRC16:59
*** diablo_rojo has joined #openstack-tc17:00
*** dtantsur is now known as dtantsur|afk17:10
*** mriedem_away is now known as mriedem17:23
*** harlowja has quit IRC17:31
fungiwhen you have only one major contributor, it's a stretch to paint that as a "benevolent dictator" model. you could just as well say it's unanimous agreement of all regular contributors on all merged changes17:45
scasfair point. from being from the southern US, i have a certain... way with words17:57
scasif i pump the metaphor, it's akin to a silent dinner, where everyone nods in agreement at whatever i serve17:59
scasfurther to that metaphor, what i serve _is_ pretty tasty, if you're into that kind of metaphor18:00
*** mriedem1 has joined #openstack-tc18:14
*** mriedem has quit IRC18:14
*** harlowja has joined #openstack-tc18:15
*** diablo_rojo has quit IRC18:16
*** mriedem1 is now known as mriedem18:22
*** diablo_rojo has joined #openstack-tc18:45
fungiscas: wait, dinner or supper? we southerners differentiate those ;)19:01
*** jaypipes has joined #openstack-tc19:16
scasfungi: upscale dinner, given the type of user still using the first gen tooling19:31
scas$X required to dine, if you will19:31
*** annabelleB has quit IRC19:32
scassome do prefer the flavor palate of ansible these days, so the metaphor is starting to fall apart19:33
scasi see it as not having enough variety, being more on a rotation than a bespoke menu19:35
scasto flagellate the metaphor beyond value...19:36
scasthat may paint enough of a picture to see what i see, to some extent19:37
*** lbragstad_ has joined #openstack-tc19:40
*** lbragstad has quit IRC19:41
*** lbragstad_ is now known as lbragstad19:56
*** e0ne has joined #openstack-tc20:06
*** rosmaita has quit IRC20:11
*** e0ne has quit IRC20:22
*** dtruong_ has quit IRC20:23
*** dtruong_ has joined #openstack-tc20:26
*** annabelleB has joined #openstack-tc20:30
*** cdent has quit IRC20:46
*** david-lyle has joined #openstack-tc20:54
*** dklyle_ has quit IRC20:57
*** diablo_rojo has quit IRC20:58
*** edmondsw has quit IRC21:04
*** edmondsw has joined #openstack-tc21:05
*** edmondsw has quit IRC21:10
*** e0ne has joined #openstack-tc21:16
*** tellesnobrega has quit IRC21:31
*** tellesnobrega has joined #openstack-tc21:32
*** annabelleB has quit IRC21:39
*** annabelleB has joined #openstack-tc21:40
*** annabelleB has quit IRC21:50
*** e0ne has quit IRC22:00
*** annabelleB has joined #openstack-tc22:08
*** annabelleB has quit IRC22:21
*** annabelleB has joined #openstack-tc22:37
*** hongbin_ has quit IRC22:42
*** annabelleB has quit IRC22:54
*** harlowja has quit IRC23:09
*** diablo_rojo has joined #openstack-tc23:47
notmynameI assume http://logs.openstack.org/23/586723/1/check/openstack-tox-py35/e871dac/job-output.txt.gz#_2018-07-27_23_43_52_905606 is transient? on the elections repo23:50
notmynamehttps://review.openstack.org/#/c/586723/23:50
clarkbnotmyname: I think so, I can list pbr versions off thzt mirror from here23:54
notmynameclarkb: ok. I'll recheck it, but otherwise not worry about it during the weekend :-)23:56

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