Thursday, 2020-12-10

*** tosky has quit IRC00:02
*** ricolin has quit IRC01:35
*** openstackgerrit has quit IRC03:22
*** camelCaser has quit IRC04:59
*** camelCaser has joined #openstack-tc05:02
*** bauzas has quit IRC05:02
*** bauzas has joined #openstack-tc05:09
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-tc05:33
*** cloudnull has quit IRC05:56
*** cloudnull has joined #openstack-tc05:57
*** ShadowJonathan has quit IRC06:11
*** rpittau|afk has quit IRC06:11
*** mnaser has quit IRC06:11
*** ShadowJonathan has joined #openstack-tc06:11
*** mnaser has joined #openstack-tc06:11
*** rpittau|afk has joined #openstack-tc06:11
*** evrardjp has quit IRC06:49
*** evrardjp_ has joined #openstack-tc06:49
*** lpetrut has joined #openstack-tc07:00
*** slaweq has joined #openstack-tc07:17
*** ralonsoh has joined #openstack-tc07:25
*** dklyle has quit IRC07:37
*** rpittau|afk is now known as rpittau08:17
*** e0ne has joined #openstack-tc08:23
*** tosky has joined #openstack-tc08:47
*** akahat has joined #openstack-tc09:43
*** bhagyashris has joined #openstack-tc09:44
*** ralonsoh_ has joined #openstack-tc10:00
*** ralonsoh has quit IRC10:01
*** ralonsoh_ is now known as ralonsoh10:33
*** lxkong has quit IRC12:26
*** ricolin has joined #openstack-tc12:56
*** apevec has joined #openstack-tc13:27
apevecmnaser, hi, 1500 UTC meeting is in this channel?13:28
mnaserapevec: yes :)13:28
apevecI can speak about the centos stream topic if needed!13:28
apevecI wonder what is expected AI for TC on that topic?13:28
mnaserI should probably append that to my message.  apevec: oh thank you that would be useful13:28
*** slaweq has quit IRC13:29
mnaserI am not sure if we have anything actionable yet other than “here’s a change and how does it affect us”13:29
apevecon tech level I see few steps like adding it to AFS, check few ifs in devstack etc.13:29
apevecIIUC concern was about announced EOL for centos "classic" before 1yr wallaby support is over?13:30
mnaserapevec: something I expect to come up is the whole “tested distros” for openstack list but I also expect maybe some folks to bring up what this means for already released versions of openstack13:30
mnaserYeah that was one that was brought up13:30
apevecso I'd like to emphasize c8s will be the _same_ content as we would get in "classic" just continuously released13:30
apevecah yes, where is that list of "tested distros" maintained again?13:31
mnaserI guess tripleo will develop against cs8?13:31
mnaserLet me grab that for you13:31
mnaserhttps://governance.openstack.org/tc/reference/runtimes/victoria.html and we determine them using https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html13:32
apevecthanks!13:32
mnaserFrom what I understand things like Python versions won’t change in a stream so it’s not like it’s centos stream but centos stream *8*13:32
apevecyes13:33
mnaserso it’s not actually rolling entirely but rolling inside the major release so to speak13:33
apevecit can be even diffed, there c8s branch at git.centos.org13:33
*** slaweq has joined #openstack-tc13:33
apevecyeah rolling was unfortunate wording which everybody seems to interpreted as bad13:33
apevecbased on experience with real rolling distros I guess13:34
mnaseryeah it gave centos stream == Debian sid sort of vibe13:34
apevecit was corrected in centos blog but too late for Internets :)13:34
mnaserInternet loves to find something to be angry about :)13:34
toskyit's like using the latest from stable/ussuri instaed of the last x.y.z tarball for a certain project13:35
mnaserThat’s exactly how I understand it too13:35
apevectosky++ good analogy, thanks!13:35
apevecand what I heard there are some admins who plan to do that, maintain tagged yum repos with _exact_ set of X.Y rpms13:36
apevecall what RHEL folks said is that they will not that that part anymore13:37
mnaserI see. So if someone just wants to check all the RPMs in RHEL and build a repo out of them, everything should can be pulled out of stream13:37
apevecyes13:37
mnaserBarring some security patch that hasn’t been moved to cs8 yet13:37
apevecand the content is the same eventually, just delivered earlier13:38
apevecit's the same for c8 "classic"13:38
apevecwe cannot publish embargoed fix13:38
apevecand it must go to rhel first b/c of SLA we have13:38
apevecbut it will be within hours in c8s branch13:39
mnaserA bit of a bummer that the 1:many model of discussion around cs8 built a lot of FUD. I appreciate you coming to clarify a lot of this stuff and hoping other rh community members reach out and do the same13:39
mnaser(In other communities)13:39
apevecnp, yes that's the hope13:39
apevecI mean, outrage and all was expected by our community managers, it will settle down once we get to the facts :)13:40
*** zbr has joined #openstack-tc13:58
*** diablo_rojo__ has joined #openstack-tc13:58
*** zbr has quit IRC14:05
*** zbr has joined #openstack-tc14:08
yoctozeptogmann: I will have a meeting till half past - I'd love it if you could postpone our topic till then, thanks14:16
yoctozeptoI mean, till 30th minute mark of the planned tc meeting14:16
noonedeadpunkapevec: well, even "classic" release of 8.3 got CI pretty broken for us14:29
noonedeadpunkbecause releasing kernel module renaming withing same minor kernel version kind of weird imo14:29
yoctozeptonoonedeadpunk: and renaming repos14:30
yoctozeptoand whatever14:30
noonedeadpunkand that, sure14:30
yoctozeptoand we also got docker 20.1014:30
yoctozeptoit is hell's rollecoaster this week14:30
yoctozepto:-)14:31
noonedeadpunkso it didn't only sounded like debian sid, but it already looks like debians sid even for classic version, which is not what everyone expected14:32
fungikeep your hands and arms inside th vehicle at all times14:32
funginoonedeadpunk: i wouldn't have equated it to sid, more like testing (the repository where candidates for the next stable release are assembled)14:33
fungipackages in sid (unstable) aren't guaranteed to make it into testing14:33
gmannyoctozepto: ack, sure.14:33
fungithey can have migration-blocking bugs filed against certain versions, or be missing some of their dependencies even14:34
fungii doubt that's expected with centos stream14:34
fungidebian testing is where package mostly land once they're "good enough to release"14:34
fungi(for the record, i run debian/unstable on most of my systems and find it remarkably stable)14:35
noonedeadpunkwell, with debian you can actually choose level which says that debian is has the way better model :)14:37
noonedeadpunkor you can jsut get some packaged from unstable/sid while sticking to stable14:38
*** tobberydberg has quit IRC14:38
fungisure, i mean on a lot of my systems i'm mixing testing, unstable, experimental, and packages i've patched/rebuilt locally14:38
*** tobberydberg has joined #openstack-tc14:39
funginot that i recommend doing that just for fun, but the security patching workflow during release freeze means that some fixes can land directly in testing/tpu without going through sid14:40
fungiso there are times where it makes some sense14:40
fungibut if you're going to be mixing suites or even just using sid without doing that, it's a good idea to get familiar with solving dependency problems, temporarily holding packages at specific versions, searching the bug tracker, paying attention to announced lib transitions, et cetera14:42
noonedeadpunkyeah, agree here14:42
fungiso like i say, not a problem i expect people using centos 8 stream to encounter14:43
*** mugsie has joined #openstack-tc14:44
noonedeadpunkwell, will see.14:45
noonedeadpunkI'm honestly more pessimistic here14:45
noonedeadpunk(mostly because of the 8.3 release)14:46
noonedeadpunkI find it as a great example of what may Centos become with Stream, but you even won't have a release notes to fix things afterwards and see what has been changed14:47
noonedeadpunkBecause now they are referencing to the point releases in notes, which won't be the case I guess?14:49
fungiit seems likely to end up similar to debian/testing or opensuse/tumbleweed, packages would need to meet certain quality level not just a dumping ground for things which might be releaseable in rhel14:49
apevecno, it will not be a dumping ground, it is still the same rhel process for better or worse14:51
apevecand 8.3 example shows that no QA is 100%14:51
apevecStream give us opportunity to check updates one by one14:51
apevecI can tell you that RHEL CI is serious, and we (RDO team) are working with them to get Zuul support within Fedora CI14:52
apevecthe same test infra for publicly contributed test cases will be used14:52
apevecad alert: https://fedoraproject.org/wiki/Zuul-based-ci is what fbo & team have been working on14:53
apevecStream will allow to propose tests for openstack use-cases14:53
*** marios|rover has joined #openstack-tc14:55
apevecnoonedeadpunk, re. release notes - RHEL relnotes will apply, I don't think centos ever had their own?14:57
*** weshay|ruck has joined #openstack-tc14:57
*** pojadhav has joined #openstack-tc14:57
apevecso we'll have Stream topic at :30 ?14:57
gmannapevec: yeah in 2nd half of the meeting14:59
apevecack14:59
jungleboyjo/15:00
ricolino/15:01
mnasertechnical difficulties this morning oops15:01
mnaser#startmeeting tc15:01
openstackMeeting started Thu Dec 10 15:01:55 2020 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: tc)"15:01
openstackThe meeting name has been set to 'tc'15:01
mnaser#topic rollcall15:02
*** openstack changes topic to "rollcall (Meeting topic: tc)"15:02
gmanno/15:02
ricolino/15:02
diablo_rojo__o/15:02
mnasero/15:02
mugsieo/15:02
mnaser#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee15:02
mnaseri count 4 names and an (on time) jungleboyj making it 515:03
*** rlandy has joined #openstack-tc15:03
jungleboyj:-)15:03
mnaser#topic Follow up on past action items15:03
*** openstack changes topic to "Follow up on past action items (Meeting topic: tc)"15:03
jungleboyjDidn't have to get the kids to school today.15:03
mnaser#link http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-03-15.00.html15:03
jungleboyjCan't wait until Ian can drive himself.15:03
mnaserhaha :)15:03
mnasermnaser change all reference of meeting time to go towards eavesdrop for single source of truth <= i've removed all references (or as much as i can) and relinked them to eavesdrop15:04
mnaserthat way, we won't have any confusion if we play in the time for the future15:04
mnaserif anyone sees any, i'd appreciate fixing them (or sending them my way!)15:04
jungleboyj++15:04
mnasermnaser remove openstacksdk discussions for future meetings <= done15:04
mnasermnaser send email to ML to find volunteers to help drive goal selection <= that's a TODO on me.  i will draft up and send the email out today.15:05
mnaser#action mnaser send email to ML to find volunteers to help drive goal selection15:05
gmann+1.15:05
mnaserfor follow up :)15:05
mnasernext up, gmann complete retirement of searchlight & qinling15:05
gmannthat is close, repo cleanup and governance patches are merged15:06
mnasernice.  any project-config patches left at this point or?15:06
gmannI left with few dependencies one left which are up and under review15:06
akahato/15:06
gmannno project config patch left15:06
gmann#link https://review.opendev.org/q/topic:%22retire-searchlight%22+status:open15:06
gmann#link https://review.opendev.org/q/topic:%22retire-qinling%22+status:open15:06
gmannone system config is there if you can have look.15:07
mnaserok awesome, i don't have infra-root but maybe we can ask clarkb or fungi nicely :P15:07
*** e0ne has quit IRC15:07
gmanni see will ping them15:07
mnasergmann: do you think we should keep it as an action item for next time to track or you feel like it should be marked as 'done' ?15:07
gmannmnaser: we do not need as governance patch is merged only thing is projects need to merge the already up patches for usage ermoval15:08
gmannremoval15:08
*** e0ne has joined #openstack-tc15:08
mnaserack, do you want us to track progress as an action item for next week just to see if we can help you drive this or feel its fine?15:09
fungii'll take a look at the system-config change now15:09
gmannmnaser: either way is fine, tracking with AI will be more clear.15:09
mnaseri agree :)15:09
gmannfungi: thanks, these two https://review.opendev.org/c/opendev/system-config/+/764573 https://review.opendev.org/c/opendev/system-config/+/76455315:09
mnaser#action gmann complete retirement of searchlight & qinling15:09
mnaserso many diablo_rojo's in here :P15:10
diablo_rojo__I am behind in my retirement of karbor, but I should have some patches up in the next couple days15:10
diablo_rojo__Lol sorry15:10
diablo_rojo__So many laptops15:10
mnaserok awesome, no worries, i'll keep it as an AI to track15:10
diablo_rojo__Yes please :)15:10
mnaser#action diablo_rojo complete retirement of karbor15:10
mnaserand finally mnaser remove project retirement from agenda -- that's gone to clean up the agenda now15:10
mnaser#topic W cycle goal selection start15:11
*** openstack changes topic to "W cycle goal selection start (Meeting topic: tc)"15:11
gmannWe should change this to X cycle goal15:11
mnaservery much so, lol15:11
diablo_rojo__Agreed lol15:11
mnaser#undo15:11
openstackRemoving item from minutes: #topic W cycle goal selection start15:11
mnaser#topic X cycle goal selection start15:11
*** openstack changes topic to "X cycle goal selection start (Meeting topic: tc)"15:11
mnaserso -- it's a bit on me having not sent the email to seek volunteers for this15:12
gmannyeah,15:12
mnaserthe action item is still there and i'll send that out today, but does it make sense to keep it as an open discussion item to track the progoress (i think it makes more sense than action items)15:12
gmannalso there is nothing in proposed directory so it may take time15:12
gmannSecure RBAC also not yet ready to be community goal.15:12
mugsieyeah, and the etherpad doesn't have a huge selection of ... achivable goals :/15:13
gmanntrue15:13
mugsie#link https://etherpad.opendev.org/p/community-goals15:13
mnaseri think perhaps a small reminder that we don't have to do a community goal for every release.  and maybe it makes sense for us to say .. im sure our contributors are tired, and even more since covid15:13
mnaserso maybe skipping a community goal for sanity and letting our developers push time towards a feature they want to drive or something that they might _enjoy_ doing a bit more than say, privsep ;)15:14
mugsieyeah.15:14
mnaser(disclaimer: i think privsep is great but maybe not the most exciting thing to work on)15:14
mugsieor we tried a "stablisation" cycle in the past, that might be a good breather goal?15:14
gmannyeah, that is totally fine.15:14
jungleboyjGiven how burned out everyone seems to be mnaser 's idea isn't bad.15:14
ricolinmugsie, that will make a fine goal indeed15:15
fungicycle goal: try not to make things worse ;)15:15
mnasermugsie: that's pretty neat, i mean, we can just leave it open and ask folks to update the proposed goal page with something they worked on15:15
mugsieI like that :)15:15
gmann+1. goal can be 'spend goal-work time with your family and firend' :)15:15
mnaserso that its sort-of a show-and-tell "hey we FINALLY got around doing X"15:15
mnaserkinda thinking of thinking the community goal this time around maybe being your '20% time'15:16
mnaserand if that doesn't produce anything, that's also fine.  times are hard :<15:16
gmannand this can encourage teams to do more progress on OSC and RBAC stuff too15:16
mnaserperhaps we can link out to the popup teams and the goals that are not selected15:17
gmannotherwise popup teams does not get much attentions from projects side15:17
gmannmnaser: +115:17
mnaserand say that you could totally help with that15:17
gmannyeah good idea.15:17
mnaserthis is an awesome idea i think15:18
mugsie+10015:18
mnaseri will try to summarize some of these ideas, being like either: 1. use this time to rest and relax, no need to do something, 2. use this time to finish up this really cool thing you've been trying to find time to, and share with us to recognize or 3. check out these existing goals / popup teams that might interest you if you want to invest time in something different/new15:19
mnaser(all 3 can be what the stabilize 'goal' is)15:19
mnaserhow do we feel about above ^ before i blast to ML? :)15:20
jungleboyjI like it.15:21
gmann+1, one suggestion to move popup team one as 1st :)15:21
jungleboyj+115:21
mugsiesounds great to me15:21
ricolinmnaser, assume we will keep collecting new idea for goals along side with these three idea?15:21
mugsie(in any order :D )15:21
mnaserof course15:22
mnaserthat's a good addition15:22
ricolinmnaser, super:)15:22
mnaserok so after all my not sending that email was a 'happy accident'15:22
mnaser:P15:22
mnaserok, moving onto next15:22
mnaser#topic Audit and clean-up tags (gmann)15:22
*** openstack changes topic to "Audit and clean-up tags (gmann) (Meeting topic: tc)"15:22
jungleboyjSometimes things happen for a reason.  :-)15:22
gmannwe can remove the zero upgrade one as it is merged.15:23
mnaser#topic Audit and clean-up tags (gmann)15:23
*** openstack changes topic to "Audit and clean-up tags (gmann) (Meeting topic: tc)"15:23
mnaser#undo15:23
openstackRemoving item from minutes: #topic Audit and clean-up tags (gmann)15:23
gmannfor API tag, doc patch is merged. thanks mugsie for pushing that. I will start the ML to encourage projects to start apply for that tag15:23
gmannmnaser: may be we can track only API one for now to know how projects are progressing on this15:24
gmannI am sure manila is interested, may be gouthamr will raise patch soon15:24
gouthamr+115:24
mnaserok so should we keep this action to discuss on progress of getting projects in15:25
mnaseror split it out to action items?15:25
gmannI think action is fine to know how many projects want/do not want and what next we can do on this tag15:25
mnasergmann: maybe an action item is announcing the tag and seeing if projecst have interest in 'applying' ?15:26
*** dklyle has joined #openstack-tc15:27
gmannmnaser:  I will say to keep 'Audit and clean-up tags' only and we will have each tag one by one to audit carefully15:27
gmannso that we cover each tag this time15:27
mnasersounds good15:27
mnaserok, trying to be mindful of our time15:27
mnasermaybe we can flush this quickly15:27
mnaser#topic X cycle release name vote recording (gmann)15:27
*** openstack changes topic to "X cycle release name vote recording (gmann) (Meeting topic: tc)"15:27
mnasersmcginnis: happen to be around? do you see access to the results or we have to disclose?15:27
mnaser(implying that i would .. remember mine)15:28
jungleboyj:-)15:28
gmann:)15:28
jungleboyjIt would be good if we had the results as I don't totally remember my vote.15:28
mugsie#link https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e6e96070af39fe715:29
ricolinwe do have the result link15:29
gmanndoes organizer get the vote results may be fungi knows?15:29
ricolin^^^15:29
mnaserthat's what i'm curious about15:29
mugsie(the CIVS email has the link to the results page)15:30
gmannmugsie: ricolin yeah but it does not have individual vote results15:30
fungicivs doesn't provide individual voter choices unless you set that option when creating the poll, otherwise votes are anonymous15:30
gmannohk15:30
mnaserahhh, ok, so we really need to remember our choices15:30
gmannand only for 6 votes as more vote now can alter the result :)15:30
mnaserok well, we're at 10:30 and a bunch of community members are looking forward for another discussion, so id like to be mindful of time15:31
jungleboyjI am pretty sure I was Xenoblast, Xenomorpth and Xenith15:31
mnaserwe can keep this for next week or discussion async over ML or IRC15:31
gmannsure15:31
mnaser#topic CentOS 8 releases are discontinued / switch to CentOS 8 Stream (gmann/yoctozepto)15:31
*** openstack changes topic to "CentOS 8 releases are discontinued / switch to CentOS 8 Stream (gmann/yoctozepto) (Meeting topic: tc)"15:31
mnaserall yours ^, also  we have apevec from the RDO community who can help inform/explain things too15:31
apevecactually, I didn't propose the topic :)15:32
apevecI think it was from Kolla ?15:32
apevecI can explain what Stream is15:32
gmannyoctozepto started this in QA office hour this week15:32
gmannalso we are adding job in devstack also which need more work #link https://review.opendev.org/c/openstack/devstack/+/75912215:32
apevecbasically the same content as in centos8 just delivered earlier15:33
gmannapevec: +1, that will be helpful, go head15:33
gmannahead15:33
apevecso atm no need to change15:33
mugsieso, does this mean for stable branches we should remove stream?15:33
apevecso tl;dr the same RHEL process applies15:33
apeveconly what is planned to be release will get to Stream15:33
mugsieas stream could update under us, and cause a ton of changes to fix the gate?15:33
apevecmugsie, atm we don't think we have 8-stream in AFS15:34
mnasermugsie: as i understand it, stream is not exactly a rolling distro15:34
apevecmugsie, centos updates under us e.g. right now15:34
mnaserso it's like how we said we support centos 8 but centos 8 and 8.1 and 8.2 and 8.3 are different15:34
mnaserwe never really said 'we support centos 8.X'15:34
apevecyeah rolling might have different implications,15:34
mugsiewe pin to a minor version of centos (wel we did for centos 7.x)15:34
apevecwhere we pin it?15:34
mnaseroh really? TIL, i thought we were always testing against latest centos minor (i remember the painful breakages when upgrades happen)15:35
mnaserat least in our OSA times :P15:35
mnaserat least nodepool builds latest AFAIK15:35
* yoctozepto still in another meeting, give him 5 mins15:35
apevecin AFS we have just 815:35
apeveci.e. latest15:35
apevecfungi, please remind me where is AFS content defined?15:35
fungialso the images we build for ci nodes in opendev just use whatever the latest 8.x is at the time15:35
apevecright15:36
apevecand we are getting now all 8.3 updates in bulk15:36
apevecwhich are breaking things15:36
apevecask weshay|ruck  ;)15:36
weshay|ruck:)15:36
marios|rover:(15:36
weshay|rucktru story15:36
gmanntesting runtime also just talk about 7/8 which mean whatever latest .x is can be run #link https://governance.openstack.org/tc/reference/runtimes/ussuri.html15:37
apevecso getting single updates could be better for us in CI15:37
apevecthanks for the link15:37
mugsieoh, we did move to the "latest CentOS Major"15:37
zbrswitching to stream makes sense IMHO, i already did this locally ~6 month ago.15:37
apevecyeah so CentOS 8 can stay, with 8 Stream repos enabled until 202415:37
mnaseri assume for those targeting centos, life will be easier as it'll be small bumps rather than one big blow at once15:37
*** mgariepy has joined #openstack-tc15:37
fungi#link https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/mirror-update/files/centos-mirror-update mirror script for centos15:37
fungiapevec: ^15:37
apevecthanks fungi++15:38
mnaserso rather than one big change on release day, it's a small delta over time..15:38
apevecoh wait only 7 ?15:38
apevecah nm, I'm blind15:38
mnaser:P\15:38
fungiapevec: separate sections for 7 and 8 yeah15:39
apevecyep, I see now15:39
apevecso yes, mirror.dal10.us.leaseweb.net/centos/8/15:39
mnaseri think right now from an openstack pov, tripleo will probably continue to give us the signal of 'openstack can run on this stack' in terms of qemu/libvirt/etc as it always has15:39
mugsieOK, so it will me RHEL will have to deal with any incompatibilities when building packages for RHEL, but we just keep using CentOS 8 stream, which should stay the same major version for the life cycle of that OpenStack release15:39
apevecwe'll need to add http://mirror.dal10.us.leaseweb.net/centos/8-stream/15:39
mnaseryoctozepto and gmann from what i see are working on the devstack improvements to be able to run on it15:39
mugsieand stream major versions will have a longer life cycle than our releases anyway, so we should be OK?15:40
apevecyes Stream will be 5 years15:40
zbranyone working on a change to add 8-stream? I can do it.15:40
mnasermugsie: i think given RHEL's upstream dev happening inside tripleo (and targetting stream?), i can imagine that they'll want to get things landed inside of stream so rhel works15:40
apeveczbr, not change, add15:40
gmanndo we need to change in stable branch also or keep centos8?15:40
apevecif we have space15:40
apevecso we don't break current assumption about repo paths15:41
zbryeah, that was the idea.15:41
gmannso add from wallaby onwards ?15:41
zbrwe can think as "8-stream" as some kind of 9-ish.15:41
mugsiegmann: thats a good call. doe we have any stable branches that will be supported past Dec 2021?15:41
mnaseri think ussuri might be affected, lets check15:42
gmannmugsie: yeah at least Victoria. and ussuri on Extended maintance15:42
mnaser#link https://releases.openstack.org/15:42
apevecI think TripleO will want Train, weshay|ruck marios|rover ?15:42
marios|roverapevec: yes15:42
* yoctozepto is here15:42
mugsievictoria is going to be impacted, ussari in EM is less of a worry15:42
gmannwe need to care for both Victoria and Ussuri15:42
yoctozeptoI see you are progressing as planned :-)15:43
yoctozeptogmann: ++15:43
fungithe bulk of the upstream jobs run on ubuntu anyway, so if we end up needing to drop centos-8 jobs from some em branches that doesn't seem like the end of the world15:43
fungior convert them to use stream15:43
yoctozeptoKolla is going to switch to stream if nothing changes in the first month of 202115:43
jungleboyjfungi:  ++15:43
mugsieyeah. converting victoria to stream may be a good idea. I would just leave ussari as is, and turn off centos next december15:43
fungii mean, think about it, the packages landing in stream would have also filtered into centos 8 point releases under the old model and caused the same disruption for jobs running on those branches either way15:43
yoctozeptowe still expect the situation might change15:43
apevecfungi, exactly15:44
apevecyoctozepto, in what way would it change?15:44
gmannand we can leave decision for Ussuri later if EM team want to move it to Unmaintained or fine with dropping centos815:44
mnaseras i understand it this morning, centos stream 8 is pretty much RHEL 8.LATEST + delta until 8.LATEST+115:45
fungiso it's business as usual. em branches are either fixed so jobs can continue running, or we drop those jobs if the work to fix them is greater than the benefit they provide us15:45
apevecmnaser, correct, it candidate builds for .LATEST+115:45
gmanngrenade jobs are on ubuntu so we do not need to worry for ussuri updates for victoria grenade testing15:45
apeveci.e. now in c8s you see what will be released as 8.415:45
yoctozeptoapevec: well, we never know whether this decision is not reverted based on pressure15:45
yoctozeptoplus also independent projects doing rebuilds15:45
apevecyoctozepto, I can tell you for sure it is not going to be reverted15:45
apevecand there are already other rebuilds15:46
apevecjust not sure how viable they would be15:46
apevecagain, c8s == same content just earlier15:46
fungie.g. rockylinux15:46
apevecfungi, is README.md :)15:46
mnaserthe way i see it is: other rebuilds are there to welcome to bring patches to add support15:46
apevecbut yeah we'll see15:46
fungiapevec: yup! plus some vapor15:46
mnaserbut as of now, we need to seek a route moving forward for centos at least15:47
gmannyeah15:47
mugsiethereis some things I suspect will stick around like https://blog.cloudlinux.com/announcing-open-sourced-community-driven-rhel-fork-by-cloudlinux15:47
mnasercloudlinux has been around for ages as a rhel derivative15:47
apevecyes there are clones and that's fine15:47
fungialso scientific linux may end up doing a c8 update eventually15:47
apeveccXs will be still real thing15:48
mnaserto be honest, i feel like folks who are interacting with rhel/centos inside our upstream seem to have a pretty good grisp on the best solution moving forward15:48
apevecesp with next 9 cycle15:48
mnaserso from a tc pov, it looks like supportability is not disappearing for the platform15:48
mnaserand given rh's interest in maintaining older releases, they'll fix what needs to be done from a distro pov15:48
apevecweshay|ruck, marios|rover ^ go fix it :)15:49
marios|rover;)15:49
jungleboyjmnaser:  ++15:49
apevecbut yes, we are around15:49
mnaserand i already see mobilised action and planning from their part there15:49
gmann+1, there are much overlap between these two community in term of contributors.15:49
mnaseri think it's important to have had this discussion, i learned a lot about it, but i dont think there is anything immediate from the tc in terms of actionable15:50
yoctozeptoapevec: aye; we are more generally fine with stream15:50
yoctozeptojust our users seem very upset15:50
* noonedeadpunk was away and missed the party :(15:50
yoctozeptonoonedeadpunk: the party is pending15:50
fungiother than to simply be aware that some stable branches may need to switch jobs to a "different" node type15:50
fungi(which isn't really all that different)15:50
marios|roverfor ci it makes a lot of sense, unless you're ci'ing for RHEL builds which isn't the case here15:50
apevechope we'll get IRL party in 2022 Summit at least!15:51
jrosser^ exactly this - OSA also has end users who have just migrated 7>8 and are really worried15:51
yoctozeptoapevec: ++15:51
marios|roveri.e. we get the latest stuff earlier rather than all at once15:51
mnasertosky put it this morning in a very neat way, which was: centos 8 stream is stable/ussuri, and rhel 8.x is the tagged release15:51
mugsiemarios|rover: well, CI for RHEL is the reason we do have centos15:51
yoctozeptojrosser: exactly my words you mean?15:51
jrosserthis is not just about CI jobs but also the message we give out from projects like Kolla and OSA to our users, quite apart from RH customers15:51
apevecjrosser, users can still consume stream15:52
mugsieI do worry abnot people being able to install openstack on rhel without using the RHOP tools15:52
apevecthey just might to keep a snapshot15:52
yoctozeptoapevec: users don't want stream :D15:52
apevecif they're concerned about the rate of change15:52
yoctozeptothat's what they said15:52
yoctozeptothey are concerned about multiple things15:52
apevecyoctozepto, want / need is different :)15:52
fungipreviously the risk was that because centos lagged rhel we might not be testing against new behaviors in rhel which hadn't trickled into centos yet. the problem will simply get reversed, we may wind up testing against new features in centos-stream which haven't made it into rhel yet15:52
mnaseryeah.  i can see a point where releasing something to support centos 8 stream.. its probably very different over time15:52
mugsieas not all projects are in RHOSP, and people *do* sideload them into installs15:52
yoctozeptoapevec: they need a stable, reliable distro; and they feel like it has been discontinued15:53
apevecfungi, there is and will be more RHEL CI15:53
marios|roverfungi: s/may/will get new features that didn't make into rhel yet15:53
mnaserso a release from 1 year ago of OSA that says "supports centos 8 stream" might not actually support it 1 year later since changes15:53
apevecyoctozepto, let's take that offline, but it is not15:53
apevecagain same content15:53
yoctozeptoapevec: you don't have to persuade me15:53
mnaserbut, in defense of centos in this case15:53
mnaseri don't think any distro15:53
mnaserwas promising like15:53
yoctozeptoapevec: I am running stream15:53
apevecnothing would show up in c8s unless it is planned for .Y+115:53
mnaserOSA train ONLY runs against rhel 8.215:54
mnasers/rhel/centos/15:54
mnaserwe were always very much OSA train runs against centos 8<end>15:54
*** tdasilva_ has joined #openstack-tc15:54
mnaseri don't know of any community project that's actually "pinning" to point release of centos for what it's worth15:54
fungidoing so would be a terrible idea anyway15:54
noonedeadpunkIt's just the matter that it's hard and resourcefull to maintain thing that changes too fast15:55
noonedeadpunklike it was with Suse15:55
mugsieI know projects that say x version works on centos/rhel y.z15:55
fungibecause those point releases of centos don't get security support for the same duration as our stable branches15:55
mnasernoonedeadpunk: thing is, suse was a rolling distro15:55
*** tdasilva has quit IRC15:55
yoctozeptomnaser: openhpc15:55
noonedeadpunkand in case users don't like it and don't wont it in prod it is useless effort moreover15:55
yoctozeptoand I believe some others also do pin15:55
yoctozeptokolla never did15:55
mnaseri think we were deploying against the rolling version of suse at the time15:55
fungithe centos/rhel model has for a long time been that if you want security support you need to fairly quickly update to the next minor release in the series15:56
yoctozeptoit bit us but we can live with that15:56
mnaseryoctozepto: TIL!15:56
yoctozeptoubuntu also bit us, not seeing much difference15:56
gmann5 min remaining for meeting15:56
*** thiago__ has joined #openstack-tc15:56
noonedeadpunkmnaser: well changes between suse 15.1 and 15.2 were not bigger then for centos 8.2 -> 8.3 where repos got renamed...15:56
gmannso two things for us ? 1. move all centos8 josb to centos8-stream for master as well as stable/Victoria (leave stable/ussuri for now) + 2. update wallaby and Victoria testing runtime doc too15:56
mnasernoonedeadpunk: i think there was no shortage of packages being renamed inside suse at the time15:56
mnaser:P15:56
mugsiegmann: ++15:57
*** admin0 has joined #openstack-tc15:57
yoctozeptoif centos stream rolls more like ubuntu lts now, I will not see a difference15:57
mnasergmann: ok, that's pretty good and i trust your QA-team hat :)15:57
noonedeadpunk+115:57
*** lpetrut has quit IRC15:57
*** andrewbonney has joined #openstack-tc15:57
yoctozepto++15:57
mnaserapevec: i can maybe throw a suggestion for some sort of office hour / ama something like that to explain and talk through these15:57
apevecsure, we can do that15:58
mnaseri know that might be quite stressful with a lot of opinions going out but today's discussion was helpful15:58
apevechere in TC channel?15:58
mnaseri'm happy to host it here15:58
jungleboyjmnaser: ++15:58
gmannok. once we get devstack job working then we can ask teams to start migrating it. I will push testing runtime doc update15:58
noonedeadpunkgmann: so it will mean that CI has images for both stream and non-strem, right?15:58
mnaserand we can ask the deployment projects to be around for that and it will be very useful i think15:58
apevecyes let keep both for now15:58
gmannnoonedeadpunk: only stream as those stable release CI continue after dec 2021 also15:59
mnaser#action mnaser work to find time for community deployment projects + centos/rdo team15:59
*** tdasilva_ has quit IRC15:59
gmannapevec: in that case we need to remove it again15:59
apevecyes but only in Dec ?15:59
mnaser(i need to close out at 11, i will end the meeting, but i think we can continue the discussion here)16:00
noonedeadpunkYeah, I'd rather live with stable Centos until next release in CI while adding Stream as NV jobs16:00
gmannyeah we can continue after meeting too16:00
mnaser(another meeting :<)16:00
noonedeadpunkto see how it's going16:00
mnaser#endmeeting16:00
*** openstack changes topic to "OpenStack Technical Committee office hours: Tuesdays at 09:00 UTC, Wednesdays at 01:00 UTC, and Thursdays at 15:00 UTC | https://governance.openstack.org/tc/ | channel logs http://eavesdrop.openstack.org/irclogs/%23openstack-tc/"16:00
openstackMeeting ended Thu Dec 10 16:00:31 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-10-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-10-15.01.txt16:00
mnasernoonedeadpunk: that's a good proposal too16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-12-10-15.01.log.html16:00
*** tdasilva_ has joined #openstack-tc16:00
mnasernoonedeadpunk, jrosser, yoctozepto, apevec, weshay|ruck: i'll reach out to find a reasonable time for y'all and reach out to other projects that might be affected soon :)16:01
jrossermnaser: thanks!16:02
*** guilhermesp has joined #openstack-tc16:02
apevecthanks all!16:02
noonedeadpunkmuch appreciated :)16:02
weshay|ruckmnaser++16:02
fungiworth noting, ubuntu lts versions don't entirely "roll" they do at least mark point releases within them over time as well16:02
yoctozeptomnaser: thanks16:02
jrossernormally in a community deployment project we'd try to have a transition release supporting both operating system release N and N+116:03
*** thiago__ has quit IRC16:03
yoctozeptofungi: yeah, but having ubuntu lts installed and updating it is closer to having centos stream than centos point releases16:03
jrosseri'm not really sure how thats going to happen here16:03
mnaserjrosser: i think changing to stream is just changing the repo name16:03
yoctozeptobut yeah, somewhere inbetween indeed16:03
mnaserand update16:03
yoctozepto++16:03
fungijrosser: that's what we would do between centos 8 and centos 9, but not between centos 8.2 and centos 8.stream16:04
*** zbr has quit IRC16:04
noonedeadpunkyeah, just main concern for me with stream now is to see how often it is going to be broken16:04
gmannyeah with major version only16:04
gmannnoonedeadpunk: ah that is good point16:04
noonedeadpunkand so it does not block our work as for now at least16:04
fungijrosser: we didn't do a coordinated overlapping transition from centos 8.1 to 8.2 for example16:05
gmannso let's try it on master for another 3-6 month and then take call for victoria16:05
apevecnoonedeadpunk, yes, there are no guarantees TBH, no QA is 100%16:05
apevecbut with Stream will be able to hook up more public CI16:05
mnasercentos 8.2 to 8.3 broke just as much, but i guess "bigger less breakages" vs "smaller more breakages" might be the balance16:05
noonedeadpunkapevec: I was thinking more about merging of breaking changes16:05
gmannadding stream as non-voting on master to check stability and then move it to voting + remove centos8 ?16:05
jrosserfungi: no indeed, but bionic->focal would be one of those, and there certainly seems to be a perception (possibly incorrect) that c8 -> c8s is a similar step16:05
noonedeadpunkyeah exactly mnaser16:05
jrosseri think thats a comms/marketing issue hearing stuff here today though16:06
fungijrosser: we equate centos 8 to ubuntu focal or opensuse 1516:06
apevecnoonedeadpunk, TBH it's culture thing, package maintainers even in Fedora are not used to PR in Pagure16:06
*** zbr has joined #openstack-tc16:06
apevecwe do have Fedora Zuul CI and some maintainers are very happy with it16:06
apevecand use it before merging16:06
yoctozeptonoonedeadpunk: I understood stream is going to move in the redhat pipeline so that it is stabler than it used to be16:07
yoctozeptoapevec is that right16:07
apevecthe same testing infra will apply in c9s16:07
apevecso future is bright!16:07
*** zbr has quit IRC16:07
noonedeadpunkI think the point here is what are they testing. As with change you usually do change test to fit new behaviour16:07
yoctozeptoit always is; the tunnel has light at its end16:07
apevecyoctozepto, yes, RHEL CI has good plans16:08
noonedeadpunkbut you also need to adjust tooling behind this upgrade to fit new behaviour16:08
yoctozeptoapevec: hopefully they will be realised to their full extent!16:08
*** zbr has joined #openstack-tc16:08
* gmann need to move to nova meeting16:08
zbrto enable mirroring on 8-stream I added https://review.opendev.org/c/opendev/system-config/+/76649916:10
apevecthanks zbr16:17
smcginnismnaser: Just confirming - I did not check the box when setting up the polling, so I do not have access to full details of votes.16:18
smcginnisI think the intent with that part of the process was to make sure the community could find out which TC members voted for a name.16:18
smcginnisPresumably to know whether or not to reelect them next time if they were not happy with the results. :)16:19
smcginnisSo I think we can maybe have TC members just state which names they voted for, even if they don't recall how they ranked them?16:20
fungiaccountability from elected officials? what is this, a functional government?16:20
fungi;)16:20
smcginnisNot sure. I did mess that up, so if the TC feels we should correct the problem, I'm fine setting up a new poll and starting over.16:20
smcginnisNot that I'm proposing we do that (or that I particularly want to do that) but not sure how else to fix things if it's felt that is a problem.16:21
mnasersmcginnis: first off, thank you for just taking the time to _actually_ work through getting this done16:23
*** zbr has quit IRC16:24
mnaserso honestly, that's already a lot that i personally appreciate that you're driving16:24
mnaserwith regards to a resolution -- i'm not too sure, i suspect that we didn't even get enough votes because of the holidays :x16:26
mnaserso i am wondering if it might make sense to run it again (with the right options), a bit later when more tc members are not out for vacation/holidays -- that way we can actually get a proper response16:26
*** zbr has joined #openstack-tc16:27
*** e0ne has quit IRC16:28
*** zbr has quit IRC16:29
smcginnisWe could. The foundation has already started the vetting process though. If we decide to do a do-over, I should let them know ASAP to stop.16:29
*** zbr has joined #openstack-tc16:30
smcginnisOn the other hand, the dates were published awhile ago, so even for the folks taking vacation, it should have been no surprise that this was taking place.16:30
mnasersmcginnis: ah i didn't know it was that far in, ok, well, i mean i think most of us might be able to remember our top choices16:32
mnaserbut maybe not the ranking accurately16:32
mnaserso maybe just a fair 'hey these were my preferences at the time' and trust that we're all humans and any errors are not bc lack of transparency but .. memory :)16:32
smcginnisI think (hope) that would be enough.16:33
smcginnisThe rough ETA was we should have final all-clear by next week.16:33
smcginnisI gave them the link to results, but only pointed out the first two names.16:33
smcginnisThere were really three in third place, so I think if it comes to that, then we can do another poll as a tie breaker.16:34
mnaserthat's fair16:35
jungleboyjsmcginnis:  ++ That sounds like a fair plan.16:35
mnasersmcginnis: i can send an email to ML explaining (or maybe you already did, or perhaps you can) and then TC members can reply to that thread recording what they voted to what they best recall16:35
smcginnisI can send that now. Good to be transparent there.16:36
* jungleboyj has nothing to hide! :-)16:36
mnaserand then we'll just keep that next to the poll results which i think we post inside the governance change when we add the new name16:36
smcginnisSounds like a plan.16:36
mnaserlink to an ML thread is probably easier kept than eavesdrop16:36
mnaserok, thank you so much.  perhaps shoot if you could shoot a message once that's out so those who have more eyes on IRC can check it out too16:37
smcginnisDrafting now...16:37
*** zbr has quit IRC16:46
*** zbr has joined #openstack-tc16:49
smcginnisOK, sent.16:53
*** zbr has joined #openstack-tc16:55
*** marios|rover has quit IRC17:12
*** zbr has quit IRC17:21
*** zbr has joined #openstack-tc17:24
*** zbr has quit IRC17:35
*** zbr has joined #openstack-tc17:37
*** zbr has quit IRC17:55
*** zbr has joined #openstack-tc17:57
*** zbr5 has joined #openstack-tc17:57
*** zbr5 has quit IRC17:58
*** zbr has quit IRC17:58
*** zbr has joined #openstack-tc17:59
*** rpittau is now known as rpittau|afk18:04
jungleboyjsmcginnis:  Thank you!18:07
*** apevec has quit IRC18:23
spotzI hope you're happy jungleboyj! I've got the song stuck in my head!18:26
jungleboyjSorry.  Seriously, that was why I couldn't do it.18:27
*** andrewbonney has quit IRC20:05
*** tdasilva_ has quit IRC20:37
*** tdasilva_ has joined #openstack-tc20:39
*** lxkong has joined #openstack-tc21:02
zaneb+1 for this plan: <mnaser> so maybe just a fair 'hey these were my preferences at the time' and trust that we're all humans and any errors are not bc lack of transparency but .. memory :)21:11
*** slaweq has quit IRC21:16
gmannmnaser: this is +w but not merged yet due to depends-on but for bringing back the retired repo we need to remove these from legacy file too - https://review.opendev.org/c/openstack/governance/+/76580022:10
mnaserah good catch, it was gonna probably break then .. i think22:11
gmannyeah.I think we should extend the script to check if any repo exist in both file.22:12
*** thiago__ has joined #openstack-tc22:30
*** tdasilva_ has quit IRC22:32
*** thiago__ has quit IRC22:45
*** tdasilva_ has joined #openstack-tc22:45
*** smcginnis has quit IRC23:16
*** smcginnis has joined #openstack-tc23:42
*** smcginnis has quit IRC23:49
*** tosky has quit IRC23:53

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