Friday, 2021-03-12

*** jamesmcarthur has joined #openstack-tc00:16
*** jamesmcarthur has quit IRC00:20
*** jamesmcarthur has joined #openstack-tc00:20
*** cloudnull has quit IRC00:27
*** cloudnull has joined #openstack-tc00:27
*** tosky has quit IRC00:51
*** vishalmanchanda has joined #openstack-tc03:27
*** ianychoi_ has joined #openstack-tc03:27
*** ianychoi__ has quit IRC03:30
*** jamesmcarthur has quit IRC04:33
*** jamesmcarthur has joined #openstack-tc04:44
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-tc05:33
*** ralonsoh has joined #openstack-tc06:18
openstackgerrit王昊 proposed openstack/election master: Late candidacy for Zaqar PTL position of Xena Cycle  https://review.opendev.org/c/openstack/election/+/78015006:25
*** diablo_rojo has quit IRC06:36
*** jamesmcarthur has quit IRC06:58
*** jamesmcarthur has joined #openstack-tc06:59
*** jamesmcarthur has quit IRC07:05
*** slaweq has joined #openstack-tc07:11
*** jaosorior has quit IRC07:13
*** jamesmcarthur has joined #openstack-tc07:29
*** e0ne has joined #openstack-tc07:34
*** e0ne has quit IRC07:35
*** belmoreira has joined #openstack-tc07:44
*** dklyle has quit IRC07:47
yoctozeptozaqar moved to late08:02
yoctozeptobetter and better every day :-)08:02
yoctozepto2 projects left - they consider dpl08:03
*** e0ne has joined #openstack-tc08:15
*** e0ne has quit IRC08:17
*** ianychoi_ has quit IRC08:32
*** andrewbonney has joined #openstack-tc08:33
*** jamesmcarthur has quit IRC08:40
*** tosky has joined #openstack-tc08:51
*** jamesmcarthur has joined #openstack-tc08:55
*** jamesmcarthur has quit IRC09:02
*** jamesmcarthur has joined #openstack-tc09:34
*** jamesmcarthur has quit IRC09:43
openstackgerritAurelien Lourot proposed openstack/governance master: Add Magnum charm to OpenStack charms  https://review.opendev.org/c/openstack/governance/+/78021209:53
*** jamesmcarthur has joined #openstack-tc09:56
*** jamesmcarthur has quit IRC10:01
*** jamesmcarthur has joined #openstack-tc10:32
*** smcginnis has joined #openstack-tc10:38
*** jamesmcarthur has quit IRC10:39
*** jamesmcarthur has joined #openstack-tc10:56
*** bodgix has quit IRC10:59
*** bodgix_ has joined #openstack-tc10:59
*** slaweq has quit IRC11:00
*** jamesmcarthur has quit IRC11:01
*** slaweq has joined #openstack-tc11:02
*** smcginnis has quit IRC12:28
*** tkajinam has quit IRC12:54
*** jamesmcarthur has joined #openstack-tc12:57
*** smcginnis has joined #openstack-tc13:05
*** jamesmcarthur has quit IRC13:06
*** smcginnis has quit IRC13:52
jungleboyjyoctozepto: ++  That is good news.13:54
jungleboyjUnderstandable that people are running behind.  Lot going on everywhere right now.13:55
fungiso far the late volunteers can be found at https://review.opendev.org/q/project:openstack/election+is:open+label:code-review=-213:59
*** e0ne has joined #openstack-tc14:11
*** rosmaita has joined #openstack-tc14:28
*** smcginnis has joined #openstack-tc14:28
rosmaitaanyone around to talk about requirements updates?14:28
*** lpetrut has joined #openstack-tc14:35
*** e0ne has quit IRC14:46
fungiin what context?14:49
* fungi has not caught up on e-mail this morning, so apologies if it's in there somewhere14:50
rosmaitafungi: no, not in email14:51
rosmaitajust had a discussion with hberaud in #openstack-cinder14:51
rosmaitaso my short term question is answered14:51
fungiahh, okay cool14:51
rosmaitamore general question is that i updated the requirements for os-brick for last week's release, and got some negative feedback14:52
rosmaitahttp://lists.openstack.org/pipermail/openstack-discuss/2021-March/020899.html14:52
rosmaitaeharney noticed that by updating eventlet in os-brick, that means consumers of the brick library (looking at nova) will have to use 0.30.1 too)14:53
rosmaitawhich they probably are in the gates14:53
rosmaitabut still, it might be better to have some coordination on this14:53
rosmaitaalso about that email, eharney suggested that maybe in requirements we only specify x.y.0 versions as minimums when doing general updates, and only specify a patch version when the patched version is known to be needed14:53
rosmaitawhich seems reasonable14:53
rosmaitaso i guess this is really a request for the TC to come up with a clear policy14:53
fungii think the concern there is that increasing your listed minimums even if you don't have reason to believe it's necessary isa knee-jerk reaction to not testing them any longer14:53
rosmaitayeah, i can see that, but just running unit tests doesn't seem to be much validation14:54
rosmaitawe14:54
fungior in order to simplify testing of them14:54
rosmaita'd have to run complete integration gates with the l-c, i would think14:54
fungithe counterargument is that distribution package maintainers are going to need to do their own testing either way to confirm whether the versions of dependencies they ship will work, regardless of whether they're older or newer than what our projects claim to support14:55
rosmaitayeah, that was what i took away from the discussion in february14:57
rosmaitathis one: http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020556.html14:58
rosmaitabut i was starting to wonder whether i had misread the thread14:59
gmannyeah, we cannot test it in integration way i mean if we have to do it will be large effort.14:59
fungiwell, the thread didn't say projects should increase their minimums any differently than they've done in the past, but i suppose it didn't say they can't either14:59
rosmaitagmann: btw, left a comment for you on https://review.opendev.org/c/openstack/cinder/+/77416315:00
gmannrosmaita: ack,15:00
rosmaitagmann: no rush, just before RC-time :)15:00
gmannthere are lot of things from distro side we would not be able to tests at upstream15:01
gmannrosmaita: we discussed it in yesterday TC meeting also and will continue in next TC meeting too15:01
rosmaitai didn't realize that!15:01
rosmaitawill have to look15:01
gmannand find what all we can do (which is what we have proposed in ML) and how to document those15:01
rosmaitai have a conflict for TC thursday meeting, so i don't attend very often15:02
rosmaitai didn't realize that the discussion was still continuing15:02
gmannrosmaita: http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-03-11-15.00.log.html#l-12615:02
rosmaitathanks15:03
gmannrosmaita: anyways I will ping you when we continue it15:03
rosmaitagmann: ty15:03
*** jamesmcarthur has joined #openstack-tc15:04
fungirosmaita: to be clear, we didn't really discuss projects updating their requirements minimums, just whether the tc should be implementing a lower bounds testing policy of any kind and if so, what it should include15:07
rosmaitafungi: right, it would be helpful to get some guidance about updating the minima15:07
fungimy concern is that the cure (tc enshrining lower bounds management and testing policy) could be worse than the disease (letting projects decide for themselves how they want to handle it)15:09
*** jamesmcarthur has quit IRC15:09
gmannif we have l-c file lower bound mismatch with requirements.txt then requirement check fail so we have to sync requirements min if we tests l-c15:09
rosmaitai am ok with letting each project decide15:09
rosmaitajust want to make sure i am not being too aggressive and causing problems for other people15:10
fungithe lower bounds in each project's requirements.txt and test-requirements.txt files  have to be at least as low as the lower bounds in the global-requirements.txt, yes15:10
fungipretty sure we already test that15:10
fungibut it would be good to double-check that's still the case15:11
gmannthere is no lower bound in global-requirements.txt anymore15:11
gmanneverything else other than lower-constraints job are tested with upper bound in upper-constraints.txt15:12
gmannchallenge in "letting projects decide" is, we will be leaving Debian use case of lower bound uncomplete, when many or few project start removing the loer bound testing and some keep.15:13
fungioh, yep i see the lower bounds got removed from global-requirements.txt, now it just has inclusions15:13
gmannwe should either do it in all projects or say we do not do and if any project does that is just extra things from them15:14
gmannyeah15:14
gmanni mean "as openstack upstream we do not provide lower bound" or "as openstack upstream we provide lower bound consistently for all project we release"15:15
fungioh, yep, looks like i missed that the lower bounds were stripped out of global-requirements.txt after queens. i guess that was because we decided it was too hard to test that the lower bounds in each project were at least as inclusive?15:16
gmannyeah. in queens or so15:16
*** lpetrut has quit IRC15:16
fungianyway, honestly, i think i'd be okay saying that openstack can't make any guarantees about lower bounds without thorough integration testing with them, and as that's not feasible, we just publish lists of the package versions we tested with and expect distribution package maintainers to perform their own testing if they want to ship different versions of dependencies than we tested (which is inevitable15:17
fungianyway)15:17
openstackgerritGhanshyam proposed openstack/governance master: Appoint Hao Wang as Zaqar PTL  https://review.opendev.org/c/openstack/governance/+/78027915:20
*** jamesmcarthur has joined #openstack-tc15:22
*** jamesmcarthur has quit IRC15:28
*** jamesmcarthur has joined #openstack-tc15:40
*** jamesmcarthur has quit IRC15:47
*** e0ne has joined #openstack-tc15:53
*** dklyle has joined #openstack-tc15:59
*** jamesmcarthur has joined #openstack-tc15:59
*** e0ne has quit IRC16:00
*** jamesmcarthur has quit IRC16:06
*** jamesmcarthur has joined #openstack-tc16:20
*** timburke has joined #openstack-tc16:21
*** e0ne has joined #openstack-tc16:22
*** jamesmcarthur has quit IRC16:25
*** jamesmcarthur has joined #openstack-tc16:37
*** e0ne has quit IRC16:39
*** belmoreira has quit IRC16:40
*** jamesmcarthur has quit IRC16:43
*** jamesmcarthur has joined #openstack-tc16:57
*** e0ne has joined #openstack-tc16:59
*** jamesmcarthur has quit IRC17:02
*** jamesmcarthur has joined #openstack-tc17:11
*** e0ne has quit IRC17:14
*** vishalmanchanda has quit IRC17:26
*** e0ne has joined #openstack-tc17:27
*** ralonsoh has quit IRC17:55
*** timburke_ has joined #openstack-tc18:18
*** timburke has quit IRC18:21
*** smcginnis has quit IRC18:25
*** smcginnis has joined #openstack-tc18:30
*** andrewbonney has quit IRC18:54
*** e0ne has quit IRC19:04
*** jamesmcarthur has quit IRC19:11
*** jamesmcarthur has joined #openstack-tc19:16
*** timburke_ has quit IRC19:29
*** timburke__ has joined #openstack-tc19:29
*** e0ne has joined #openstack-tc19:34
*** jamesmcarthur has quit IRC19:39
*** jamesmcarthur has joined #openstack-tc19:39
*** belmoreira has joined #openstack-tc19:41
*** jamesmcarthur has quit IRC20:41
*** belmoreira has quit IRC20:54
*** e0ne has quit IRC20:59
*** smcginnis has quit IRC21:38
*** smcginnis has joined #openstack-tc21:44
*** jamesmcarthur has joined #openstack-tc21:48
*** smcginnis has quit IRC21:53
*** jamesmcarthur has quit IRC22:04
*** jamesmcarthur has joined #openstack-tc22:07
*** jamesmcarthur has quit IRC22:48
*** jamesmcarthur has joined #openstack-tc23:00
*** jamesmcarthur has quit IRC23:13
*** jamesmcarthur has joined #openstack-tc23:14
*** jamesmcarthur has quit IRC23:19
*** jamesmcarthur has joined #openstack-tc23:29
*** jamesmcarthur has quit IRC23:32
*** jamesmcarthur has joined #openstack-tc23:36
*** jamesmcarthur has quit IRC23:45
*** jamesmcarthur has joined #openstack-tc23:47
*** jamesmcarthur has quit IRC23:58
*** jamesmcarthur has joined #openstack-tc23:59

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