Friday, 2020-12-18

*** diablo_rojo has quit IRC00:05
*** timburke has quit IRC01:41
*** timburke_ has joined #openstack-tc01:41
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-tc05:33
*** lpetrut has joined #openstack-tc05:50
*** lpetrut has quit IRC05:54
openstackgerritPranali Deore proposed openstack/governance master: Add glance-tempest-plugin to Glance  https://review.opendev.org/c/openstack/governance/+/76766606:22
*** lpetrut has joined #openstack-tc06:28
*** lpetrut has quit IRC06:30
*** slaweq has joined #openstack-tc07:42
*** dklyle has quit IRC07:57
*** ralonsoh has joined #openstack-tc08:02
*** andrewbonney has joined #openstack-tc08:15
*** rpittau|afk is now known as rpittau08:30
*** e0ne has joined #openstack-tc08:34
*** e0ne has quit IRC08:41
*** slaweq has quit IRC09:16
*** slaweq has joined #openstack-tc09:18
*** slaweq has quit IRC09:20
*** slaweq has joined #openstack-tc09:24
ttxfungi: all names had some level of issues, but Xena was deemed "safe enough".10:12
openstackgerritPranali Deore proposed openstack/governance master: Add glance-tempest-plugin to Glance  https://review.opendev.org/c/openstack/governance/+/76766610:42
*** slaweq has quit IRC10:51
*** slaweq has joined #openstack-tc10:55
*** e0ne has joined #openstack-tc12:01
*** tosky has joined #openstack-tc12:58
ttxmnaser: with AJaeger no longer helping as much on OpenStack project-config reviews, project-config-core is down to you alone. I think it's time to put out a call for new members into support the "openstack consumer"  side of our infrastructure13:15
ttxWith the remaining infra-root focusing on the opendev side (providing the services to all projects), we need new blood on the openstack side13:16
zbr|rover:(13:27
mnaserttx: ah, I think I am also not that great at reviewing. More of an “review on demand” sort of thing13:29
zbr|rovermnaser: as I said in the past, i am interested to help in the infra area.13:35
mnaserzbr|rover: thank you, i'm still unsure as to who manages project-config-core now13:40
mnaseri dont think we got much opendev-y governance done so is it up to me to add new members?  is it up to tact chair? is it up to opendev who mostly occupy project-config-core?13:40
* mnaser shrug13:40
*** e0ne has quit IRC14:09
*** e0ne has joined #openstack-tc14:09
ttxmnaser: That's what I meant by "openstack needs to start owning that side"14:11
ttxIt was a single group, but now that the opendev core services are used by multiple projects, operations of the services needs to be separated from configuration/usage of the services14:12
ttxThe former is opendev/centralized. The latter is project-specific14:12
ttxThe latter involves owning the OpenStack gerrit projects, OpenStack Zuul jobs, and debugging when "CI fails"14:14
ttxzbr|rover: which infra area makes most sense for you to be involved in? Core opendev operations, or OpenStack's consumption of those?14:15
ttxI feel like today if we/openstack own more of the latter, that will free up time for infra-root to focus on the former14:16
ttxAndreas's crazy review activity made it possible to ignore the issue until today, but now it's urgent14:17
ttxalthough project-config is likely still a shared property14:19
zbr|roveri was referring to opendev operations, but my impression is that decoupling may not be complete ever14:19
zbr|roverconfig changes do impact operations and can bring services down, sometimes changes that look genuine can do this.14:20
ttxsure it still requires lots of communications. But at least the core group no longer needs to know by heart all the job structure for all the projects14:22
ttxif they are "owned" by some other group14:22
ttxAlso I'm pretty sure that if a project-level config change can bring a service down, that's bug that should ultimately be fixed14:23
mnaseri think the focus of what ttx is talking about is specifically things like openstack/project-config14:33
mnaserlike adding a project to zuul/gerrit, etc14:33
ttxyes that and generally knowing the openstack zuul jobs structure / templates /etc. to be able to serve as first line of debugging and help14:35
*** iurygregory has joined #openstack-tc14:38
zbr|rovermnaser: i guess that giving more access to project-config is more accessible, but at the same time i think that anyone that gets core permissions to project-config should be fully trained to debug issues with the runnings services (read only access), so they can debug if needed.14:40
mnaserttx, zbr|rover: i guess this is worth adding as a discussion item for next weekly tc discussion15:00
fungiif it helps inform the situation, andreas did not have (nor want) root access to any running services15:00
mnaserfungi: right, yeah, i think we're mixing infra-root and infra-core a tad bit here15:01
fungibut managed to review massive amounts of project-config change activity15:01
fungii was responding to zbr|rover's suggestion that anyone with config core reviewer access needs access to the servers where that configuration is deployed15:01
*** e0ne_ has joined #openstack-tc15:02
fungiwe try to make those things debuggable without access to the servers for the most part15:02
zbr|roverfungi: not root, just ability to access logs.15:02
fungion rare occasions where it doesn't work as expected, it's fine to reach out to a smaller group of people with root access to dig in logs which may have lots of sensitive data, credentials, pii, et cetera15:03
*** e0ne has quit IRC15:05
ttxIf anything, that puts us in a virtuous circle of fixing those corner cases. Like if a project-level config change crashes servers. The more that separation works (project consumption vs. root services), the better15:05
zbr|roverttx: i think nobody argues against separation.15:19
fungias for who gets added to project-config-core that's probably technically my responsibility as tact sig chair, though i would consult with clarkb since it's sort of shared jurisdiction with opendev at the moment (the central opendev content of that repo is planned to move to the opendev/project-config repo eventually leaving just openstack-specific configuration in openstack/project-config, but that15:23
fungitransition will be fiddly)15:23
fungiit's not just that repo though, a lot of openstack-specific job configuration also resides in openstack/openstack-zuul-jobs15:28
gmannI can surly help on jobs side though I am not so familiar on other infra activities.15:31
*** rpittau is now known as rpittau|afk15:38
*** dklyle has joined #openstack-tc15:48
fungithat would help for sure. the bulk of the activity there is split between changes to central trusted job definition/instantiation, and changes creating new projects15:59
*** gibi is now known as gibi_pto16:35
*** chandankumar is now known as raukadah16:53
*** e0ne_ has quit IRC17:54
*** ralonsoh has quit IRC17:57
*** andrewbonney has quit IRC18:33
*** e0ne has joined #openstack-tc19:36
*** e0ne has quit IRC20:10
*** e0ne has joined #openstack-tc20:22
*** e0ne has quit IRC20:40
*** slaweq has quit IRC20:54
*** e0ne has joined #openstack-tc21:36
*** e0ne has quit IRC21:41
*** dklyle has quit IRC23:50

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!