Thursday, 2023-02-23

gmanntc-members: need one more review on the election results https://review.opendev.org/c/openstack/governance/+/87404201:59
JayFgmann: lgtm02:11
gmannJayF: thanks 02:17
opendevreviewMerged openstack/governance master: Update with 2023.2 Election results.  https://review.opendev.org/c/openstack/governance/+/87404202:35
gmann^^ Welcome jamespage for newly elected TC and all the returning tc-members (knikolla[m] spotz slaweq rosmaita ) for continuing the next term02:36
gmannand thanks arne_wiebalck for all your work and contribution in TC02:37
gmannjamespage: I have shared the TC onboarding email to you but in case you have any query, feel free to ping us in this channel02:37
jamespagegmann: thanks :) on my read list this AM08:25
ralonsohgmann, hello! qq: should I start sending the mail to the pypi mantainers?09:24
ralonsoh--> https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup-email-template09:24
ralonsohI'm not sure if that was decided or not (sorry)09:24
bauzasnoonedeadpunk: I didn't really wanted to formalize One WSGI server to Rule them All you know10:13
bauzasnoonedeadpunk: but my point is, we have devstack that runs it heavily10:13
bauzasand the uswsgi migration we had in the past is still in ringing in my brain10:13
bauzasso we should somehow do kind of an audit from a cross-project pov and see what needs to be done if any10:14
noonedeadpunkbauzas: the thing is, that users tend to pick software stack that is used in devstack as source of truth10:14
bauzas-ish but I don't disagree10:14
bauzasthe wsgi stack is somehow a prescriber I agree10:14
bauzasgunicorn seems indeed a good competitor, but before rushing into a conclusion, I'd just hope that we would arrive to some agreement before10:15
noonedeadpunkBut yes, uwsgi migration was not really neat and it still having it's issues in some projects10:15
bauzaswhich can be :10:15
bauzas1/ say this isn't a problem and leave as it is10:16
noonedeadpunkAnd yeah, I'm not sure why uwsgi was picked at the first place as it always had awful performance10:16
bauzas2/ consider uswgi critical to the projects and then take the maintainance burden on our shoulders10:16
bauzas3/ identify some other competitor where benefits overweight the migration and then do a migration plan 10:17
bauzasI don't know yet which of the three options seems the best :)10:17
noonedeadpunkEventually, I assume that most of services that are run with uwsgi should not be an issue to migrate, as it's kind of standard?10:18
bauzasso the goal I was referring to was the cross-project effort of talking to each others and do the decision :;)10:18
noonedeadpunkI don't like second for sure :)10:18
bauzaswe had precedents of projects we took under our umbrella10:18
noonedeadpunkBut yeah, I totally agree with you here10:18
noonedeadpunkWell, I'm not feeling we have resources for that?10:19
noonedeadpunkI might be wrong though10:19
bauzasgood call10:19
bauzaswhich can't be answered until we have this epiphanic brainstorm 10:19
noonedeadpunkWhich is likely more a PTG thing10:20
noonedeadpunkWe likely can easily postpone that even to in-person PTG10:20
noonedeadpunkuwsgi is in this state for a year already and they had even a bugfix release during that period10:21
noonedeadpunkSo it's not really urgent thing, but I'd prefer coming out with plan at least of what we're gonna do10:21
bauzasand we are on a non-slurp release, remember ;)10:22
noonedeadpunkAs for deployment projects or packagers it would be tricky to do last minute changes10:22
bauzasthat's a lovely timing for a preparatory work, not a migration10:22
bauzasdespite I don't know how much of the slurpriness is tied devstack10:22
noonedeadpunkTo be frank I still need couple of minutes to think when changes should be made not to ruin everything10:23
opendevreviewDmitriy Rabotyagov proposed openstack/governance master: Exclusive management of projects by openstackci  https://review.opendev.org/c/openstack/governance/+/87478710:58
coreycbhello tc, I have a question on stable branch naming for 2023.1 antelope. would a deployment project such as the charms be required to switch to stable/2023.1 or could the project stick with stable/antelope if they chose to?16:05
fungii can't speak to tc policy, but zuul looks for matching branch names across projects when integrating them in jobs, so for example constraints lists from the requirements repo won't be applied correctly without some additional manual mapping in job definitions16:16
coreycbfungi: that's a good point, thanks for sharing16:17
gmanncoreycb: we need to be consistent across all the OpenStack projects with stable/2023.1. Not just from zuul perspective but also user/developers and many other tooling also.18:25
gmannralonsoh: yes please. QA team has done that and finish the cleanup. 18:26
coreycbgmann: ok, I'll relay this back to the rest of the tam. thanks for getting back to me.18:30
gmann+1. thanks 18:31
opendevreviewMerged openstack/governance master: Define 2023 upstream investment opportunities  https://review.opendev.org/c/openstack/governance/+/87223319:05
opendevreviewGhanshyam proposed openstack/governance master: Adding mailto link in upstream opportunities doc  https://review.opendev.org/c/openstack/governance/+/87496822:55
opendevreviewGhanshyam proposed openstack/governance master: Appoint Liu as Senlin PTL  https://review.opendev.org/c/openstack/governance/+/87496923:10
opendevreviewIan Y. Choi proposed openstack/election master: Bobcat Election Results (TC/PTL)  https://review.opendev.org/c/openstack/election/+/87497023:19
opendevreviewGhanshyam proposed openstack/governance master: Appoint Felipe Reyes as OpenStack_Charms PTL  https://review.opendev.org/c/openstack/governance/+/87497123:20

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