Friday, 2017-12-15

dmsimardharlowja: I think even cdent's summary is going to need a tl;dr00:57
*** liujiong has joined #openstack-tc01:23
*** liujiong has quit IRC01:53
*** liujiong has joined #openstack-tc01:54
*** kumarmn has joined #openstack-tc01:56
*** marst has quit IRC01:59
*** mriedem has quit IRC02:11
*** kumarmn has quit IRC02:31
*** kumarmn has joined #openstack-tc02:32
*** kumarmn has quit IRC02:36
*** liujiong has quit IRC02:40
*** harlowja has joined #openstack-tc02:41
*** harlowja has quit IRC02:42
*** harlowja has joined #openstack-tc02:43
*** harlowja has quit IRC03:15
*** liujiong has joined #openstack-tc03:34
*** kumarmn has joined #openstack-tc04:27
*** harlowja has joined #openstack-tc04:36
*** harlowja has quit IRC04:45
*** kumarmn has quit IRC05:05
*** kumarmn has joined #openstack-tc05:06
*** kumarmn has quit IRC05:11
*** rosmaita has quit IRC05:14
*** harlowja has joined #openstack-tc05:21
*** harlowja has quit IRC05:22
*** harlowja has joined #openstack-tc05:24
*** harlowja has quit IRC05:29
*** harlowja has joined #openstack-tc05:38
*** harlowja has quit IRC06:32
*** jpich has joined #openstack-tc08:54
openstackgerritMerged openstack/governance master: Update policy goal for cloudkitty  https://review.openstack.org/52317409:25
openstackgerritMerged openstack/governance master: Add an openstack/self-healing-sig repository  https://review.openstack.org/52532809:33
openstackgerritMerged openstack/governance master: Added octavia queens tempest plugin planning.  https://review.openstack.org/52576809:33
openstackgerritMerged openstack/governance master: Python 35 congress completion artifact  https://review.openstack.org/52624709:33
openstackgerritMerged openstack/governance master: Mark the completion of tempest plugin split goal for murano team  https://review.openstack.org/52625009:33
openstackgerritMerged openstack/governance master: add "champions and stewards" as a top-5 help wanted area  https://review.openstack.org/51065609:33
openstackgerritThierry Carrez proposed openstack/governance master: Rename 'top-5 help wanted' to 'help most needed'  https://review.openstack.org/52061909:40
openstackgerritThierry Carrez proposed openstack/governance master: add redirect for renamed top-5-list file  https://review.openstack.org/52713809:40
openstackgerritMerged openstack/governance master: Rename 'top-5 help wanted' to 'help most needed'  https://review.openstack.org/52061909:53
openstackgerritMerged openstack/governance master: add redirect for renamed top-5-list file  https://review.openstack.org/52713809:55
*** kumarmn has joined #openstack-tc10:06
*** liujiong has quit IRC10:09
*** kumarmn has quit IRC10:11
*** dtantsur|afk is now known as dtantsur11:38
*** zaneb has quit IRC12:33
*** rosmaita has joined #openstack-tc12:47
*** cdent has joined #openstack-tc13:10
*** flwang has quit IRC13:22
*** flwang has joined #openstack-tc13:23
*** edleafe is now known as figleaf13:38
*** mriedem has joined #openstack-tc13:51
ttxdims: was there recent progress on the LTS discussion ? As far as I can tell activity on that etherpad stalled... What's the current status ? Anything I can do to help ?14:10
dimswaiting for a few things ttx 1) need to catch up with doug to see if there was some consensus in downstream redhat 2) waiting on chris price from ericsson 3) waiting on kandan from at&t as well. hoping to get all these come january. So let's wait a bit. i really want to get things going before we reach Dublin so we can get started in Dublin14:13
dimssounds like a plan?14:13
dimsHuawei downstream is not particularly interested ...14:14
dimsi talked to kandan and chris in kubecon14:14
ttxdims: sounds good14:16
ttxjust wanted to make sure that was not stalled, you seem to have it under control14:16
*** kumarmn has joined #openstack-tc14:18
dimsyep, will definitely ping you and we can get things going14:20
*** openstackgerrit has quit IRC14:48
*** kumarmn_ has joined #openstack-tc14:55
*** kumarmn has quit IRC14:57
*** marst has joined #openstack-tc14:59
*** kumarmn has joined #openstack-tc15:07
*** kumarmn_ has quit IRC15:09
*** harlowja has joined #openstack-tc15:11
*** harlowja has quit IRC15:13
*** openstackgerrit has joined #openstack-tc15:24
openstackgerritDai Dang Van proposed openstack/governance master: Update policy goal for watcher  https://review.openstack.org/52729915:24
fungii have to wonder if stuff like http://lists.openstack.org/pipermail/openstack-dev/2017-December/125636.html isn't reinforcing the lack of tripleo contributor affiliation diversity... "a way to reproduce upstream jobs, in your personal RDO cloud tenant, making easy to developers to debug and reproduce their code."15:37
fungidoes rdo give personal tenants to any developer who wants to contribute to tripleo?15:38
fungimwhahaha: ^ maybe you know? is rdo cloud open to everyone, or just employees of some companies?15:39
fungiif anyone can request a personal rdo cloud tenant, i think that's really cool15:40
cdentEmilienM might know something about all that ^15:44
openstackgerritGraham Hayes proposed openstack/governance master: Add assert:supports-accessible-upgrade to designate  https://review.openstack.org/52831515:45
EmilienMi'm in mtg, brb15:46
fungihttps://www.rdoproject.org/blog/2017/11/upcoming-changes-to-test-day/ and https://etherpad.openstack.org/p/rdo-queens-m2-cloud seem to imply that it's open to anyone who wants to help15:57
fungii wonder if that could have been more widely announced. it's a pretty awesome move enabling more involvement on the rdo team's part15:59
pabelangerfungi: yah, I think they are onetime account for testing days, but IIRC anybody is free to sign up to help16:05
fungiam i correct in assuming that's what arxcruz meant by "your personal RDO cloud tenant"?16:06
fungior is this something separate?16:06
pabelangerI am not sure about that, I'll defer to mwhahaha and EmilienM16:07
pabelangerhowever, I have an account on RDOcloud, mostly because I asked on an internal process for it16:07
pabelangerI am unsure if there is an external process outside of test days16:07
EmilienMok I'm back16:07
EmilienMfungi: to be honest, 1) I don't know the answer if yes/no anyone can get access to RDO Cloud and 2) I agree it doesn't encourage diversity if it's not the case16:08
EmilienMbut I never saw any rejection when someone asked for help or resources16:09
EmilienMRDO Cloud has been created for all developers working on OpenStack16:09
EmilienMI can't imagine them refusing you an account16:09
fungiEmilienM: sounds pretty cool then. is there a published process for signing up?16:10
EmilienMnow, what the TripleO CI team is a tool to reproduce CI jobs, not only in RDO Cloud but in any OpenStack cloud16:10
EmilienMbut the TripleO CI team is using RDO Cloud. I hope that makes the thread more clear16:10
fungiokay, so it was misleading phrasing in the sprint summary implying that it would only work in rdo cloud tenants?16:11
EmilienMfungi: let me ask on #rdo16:11
EmilienMfungi: yes it was16:11
EmilienMfungi: for example, I have my own servers and I run tripleo on them. I don't need RDO Cloud16:11
EmilienMfungi: the tooling isn't made for RDO Cloud. It's just tested on it16:11
* persia sees two separate issues a) RDO signup process is maybe not widely enough publicised (making the message disclusive, even if it is a general resource) and b) use of the phrase "personal RDO tenant" when the meaning was "personal OpenStack tenant".16:11
EmilienMI asked apevec on #rdo16:12
EmilienMfungi: I sent a message to Alan Pevec and give him the IRC history, so we can follow up16:13
fungiappreciated. i wasn't the only person who, upon reading that sprint summary, thought it implied that it ignored the possibility that non-red-hat employees might also be (interested in becoming) tripleo developers16:13
EmilienMfungi: I'll reply to the thread. I agree with you we need to be more inclusive16:14
fungithanks!16:14
dmsimardfungi: I'm the one who came up with the idea for the cloud environment for the RDO test day, I explain the context here: https://dmsimard.com/2017/11/29/come-try-a-real-openstack-queens-deployment/16:17
dmsimardfungi: It was as widely announced as we could, and was definitely open to anyone -- I even posted to openstack-operators (but though openstack-dev would not have been appropriate)16:17
dmsimards/though/thought/16:18
dmsimardIf we're happy with the way things turned out -- and I think we've been relatively successful, we want to repeat the experiment with different projects -- for example the next milestone test day could be a test cloud driven by kolla and the kolla cores would be involved in deploying the cloud and operating/troubleshooting it for the duration of the test days16:19
dmsimardThe general idea being to test OpenStack (as packaged by RDO, which is vanilla and equivalent to master branches) while providing the opportunity for deployment projects to get real user feedback -- sometimes we'll find issues in the deployment project, sometimes we'll find issues in the different projects (nova, neutron, etc.) and we'll collaborate with users and contributors to file bugs/fix them16:21
dmsimardWe meant to collaborate with a hosting provider for the duration of the event but it was too short notice so we're paying this one out of our pocket16:22
fungiand that used tenants in rdo cloud?16:23
fungineat16:23
dmsimardNo, the test day is a standalone deployment by Packstack on an OnMetal node in RAX16:23
fungiahh, okay so unrelated to the tripleo-quickstart sprint arxcruz posted about16:24
dmsimardyeah, I was about to get to RDO cloud but I saw there was also a discussion regarding test day so I addressed that one first16:24
EmilienMdmsimard: I replied to the thread, feel free to comment16:27
fungithanks EmilienM and dmsimard!16:28
dmsimardRDO cloud is a TripleO deployment -- I would say the purpose is two-fold. First it is to dogfood TripleO with a tight feedback loop between the team operating the cloud and engineering with a clear and purposeful boundary between the two -- the team operating that cloud is in another organization within Red Hat.16:28
dmsimardby dogfood, I guess I forgot to mention that implicitely includes RDO16:29
dmsimardAnd then, the second purpose is to provide development and CI resources for RDO and TripleO contributors16:29
EmilienMfungi: also, jpich just told me that RDO Cloud is "at/over capacity already"16:29
fungiwow, popular!16:29
dmsimardI don't believe we would turn down a request to have access to the cloud if it would help a contributor from outside Red Hat16:30
dmsimardJust like for the test day we have had people from the CERN or other organizations16:30
fungiwell, regardless EmilienM's reply clears it up for me. arxcruz wrongly implied that the goal only enabled reproducing jobs in rdo cloud tenants16:31
dmsimardfungi: I'll summarize on the thread, hope that clarifies things16:31
fungithanks again!16:32
cdentmriedem: you're doing a great job of stepping back from that thread...16:54
mriedemcdent: i'm doing an even better job of documenting my results for my yearly eval16:55
mriedembeen working on that since 2 hours ago16:55
mriedemwc = 016:55
cdentwoot!16:55
cdent"Did a lot of good shit for openstack"16:56
cdentdone16:56
mriedemi'm just extremely frustrated by the sweeping generalization16:56
mriedemnobody gives a shit about stable branches upstream16:56
mriedemnova isn't working on what matters16:56
mriedemnova's api is completely unstable16:56
cdentI'm hoping dtroyer will clarify, because I'm pretty sure that's not what he meant16:57
mriedempeople been talkin, and i won't name names or projects, but you know, people been talkin, and let's flip the table16:57
mriedemalright, back to eval16:58
dtroyermriedem: I'm in meeting hell and that probably wasn't the best time to send that message, but it totally isn't directed at you or the Nova team specifically, more at the overall culture here16:59
*** jpich has quit IRC17:02
mriedemif it was directed at openstack overall, that is clearly not obvious17:04
*** dtantsur is now known as dtantsur|afk17:05
dtroyerfair enough, and again in retrospect I shouldn't have sent it when I can't follow up in a timely manner.  My frustration is with our (TC, OpenStack leadership, board, etc) apparent inability to actually address things17:08
dtroyerand yes, that is another sweeping generalization that I don't have time to back up right now, but that's the focus of my thinking17:09
cdentdtroyer: how much of that do you think stems from an unwillingness to do something akin to root cause analysis?17:09
dtroyercdent: I wish it were that simple, I think the root cause is more a prevalent  "looking out for #1" where "#1" is not the commons.  there are always exceptions of course17:10
cdentI was hoping you weren't going to say that :( :)17:11
persiaOne of the stranger effects I notice as I travel is that in places with few natural resources (including those depleted or damaged), maintenance of the commons is essential to survival, leading to apparent external wealth (parts of germany (especially those devastated previously), Singapore, Japan, Doha, etc.  In places with abundant resources, sometimes there are no functional commons, and no apparent wealth.17:14
persiaI suspect there's a way to apply that same model to software, although I haven't found the right words for it.17:14
*** kumarmn has quit IRC17:18
cdenthuh, members of the UC don't seem impressed by ttx's informal model for how to do sig governance...17:27
mugsiecdent: we need another good bikeshed17:28
cdentso soon!17:29
mugsiethis does remind me of academic governance a little bit :)17:29
* mugsie once sat in a meeting, working out an agenda for a meeting, that would plan who would be in a steering group, which would plan a review meeting, which would send a report to the people in the original meeting17:31
cdentyou must be so proud17:31
mugsiea little bit of me died that day17:32
*** lukebrowning has joined #openstack-tc17:33
ttxcdent: any particular mention?17:42
ttxcdent: re. SIG governance17:42
ttxI might have missed it17:43
cdentttx: on the user-committee list17:43
ttxheh, I'll let Melvin defend it, since he co-authored it17:43
*** lukebrowning_ has joined #openstack-tc17:55
*** lukebrowning has quit IRC17:58
*** lukebrowning_ has quit IRC18:24
*** kumarmn has joined #openstack-tc18:38
*** mriedem has quit IRC18:51
*** kumarmn has quit IRC18:51
*** kumarmn has joined #openstack-tc19:01
*** lukebrowning has joined #openstack-tc19:02
*** kumarmn has quit IRC19:17
*** kumarmn has joined #openstack-tc19:19
*** kumarmn has quit IRC19:24
*** kumarmn has joined #openstack-tc19:25
*** kumarmn has quit IRC19:29
*** kumarmn has joined #openstack-tc19:30
*** kumarmn has quit IRC19:34
*** kumarmn has joined #openstack-tc19:38
*** kumarmn has quit IRC19:42
*** kumarmn has joined #openstack-tc19:42
*** kumarmn has quit IRC19:47
*** lukebrowning has quit IRC20:36
*** lukebrowning_ has joined #openstack-tc20:39
*** lukebrowning_ has quit IRC20:45
*** lukebrowning has joined #openstack-tc20:46
*** openstackgerrit has quit IRC20:48
*** lukebrowning has quit IRC20:52
*** lukebrowning has joined #openstack-tc20:53
*** lukebrowning has quit IRC20:58
*** lukebrowning has joined #openstack-tc21:00
*** lukebrowning has quit IRC21:05
*** lukebrowning has joined #openstack-tc21:06
*** lukebrowning has quit IRC21:11
*** lukebrowning has joined #openstack-tc21:13
*** lukebrowning has quit IRC21:18
*** lukebrowning has joined #openstack-tc21:19
*** lukebrowning has quit IRC21:23
*** lukebrowning has joined #openstack-tc21:25
*** lukebrowning has quit IRC21:30
*** lukebrowning has joined #openstack-tc21:31
*** lukebrowning has quit IRC21:36
*** lukebrowning has joined #openstack-tc21:38
*** lukebrowning has quit IRC21:42
*** lukebrowning has joined #openstack-tc21:44
*** kumarmn has joined #openstack-tc21:44
*** lukebrowning has quit IRC21:49
*** mriedem has joined #openstack-tc22:07
fungii think i got it straightened out. people talking past one another22:07
*** lukebrowning has joined #openstack-tc22:12
*** lukebrowning has quit IRC22:17
*** lukebrowning has joined #openstack-tc22:19
*** lukebrowning has quit IRC22:23
*** lukebrowning has joined #openstack-tc22:25
*** lukebrowning has quit IRC22:30
*** lukebrowning has joined #openstack-tc22:31
*** marst has quit IRC22:32
*** cdent has quit IRC22:34
*** lukebrowning has quit IRC22:36
*** lukebrowning has joined #openstack-tc22:37
*** lukebrowning has quit IRC22:42
*** lukebrowning has joined #openstack-tc22:44
*** kumarmn has quit IRC22:46
*** kumarmn has joined #openstack-tc22:46
*** lukebrowning has quit IRC22:49
*** lukebrowning has joined #openstack-tc22:50
*** kumarmn has quit IRC22:51
*** kumarmn has joined #openstack-tc22:51
*** kumarmn has quit IRC22:55
*** lukebrowning has quit IRC22:55
*** kumarmn has joined #openstack-tc22:55
*** lukebrowning has joined #openstack-tc22:56
*** kumarmn has quit IRC23:00
*** lukebrowning has quit IRC23:01
*** lukebrowning has joined #openstack-tc23:02
*** lukebrowning has quit IRC23:07
*** lukebrowning has joined #openstack-tc23:09
*** kumarmn has joined #openstack-tc23:10
*** lukebrowning has quit IRC23:13
*** lukebrowning has joined #openstack-tc23:15
*** lukebrowning has quit IRC23:19
*** lukebrowning has joined #openstack-tc23:21
*** lukebrowning has quit IRC23:26
*** lukebrowning has joined #openstack-tc23:28
*** lukebrowning has quit IRC23:32
*** lukebrowning has joined #openstack-tc23:34
*** lukebrowning has quit IRC23:39
*** lukebrowning has joined #openstack-tc23:40
*** mriedem has quit IRC23:46
*** lukebrowning has quit IRC23:49
*** lukebrowning has joined #openstack-tc23:51
*** lukebrowning has quit IRC23:56
*** lukebrowning has joined #openstack-tc23:57

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