Wednesday, 2025-05-21

opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: CI: Bump mariadb_monitor_ping_timeout to max  https://review.opendev.org/c/openstack/kolla-ansible/+/95043405:14
opendevreviewMichal Nasiadka proposed openstack/kolla master: WIP: Move to CentOS Stream 10  https://review.opendev.org/c/openstack/kolla/+/95039205:25
kevkomnasiadka: if you trying to tune proxysql somehow in CI when container is down during the mariadb upgrade ...I am afraid that it's impossible ..because there are another mechanisms which are checking availability of node ...not only ping 07:50
mnasiadkaNo, it's not the case - many times we just have constrained CI and networking/CPU/whatever causes issues - bumping up ping values is helping07:51
mnasiadkabut it seems our multinode is not only suffering from that...07:51
mnasiadka(sometimes proxysql, sometimes rabbitmq, sometimes something else)07:51
mnasiadkatrying to get to a stable state with these jobs07:51
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: CI: Bump mariadb_monitor_ping_timeout to max  https://review.opendev.org/c/openstack/kolla-ansible/+/95043407:52
kevkoAh, I don't think proxysql issue is problem in multinode ... (But I can't say if it is not only in CI) ....but we have production multinodes clusters ..without problems for years now with proxysql ...07:53
kevkomnasiadka: so it will be something different 07:53
kevkoI would say ..07:53
mnasiadkayeah, that only happens in CI - you're not running controllers on 8GB RAM VMs with oversubscribed everything07:53
mnasiadkaand lousy network07:53
kevkomnasiadka: I have 16 :) on my tests 07:58
kevkomnasiadka how much CPUs have nodes with 16 ? 07:58
mnasiadkawe don't have 16GB nodes, at least not yet.07:58
kevkoAh, sorry I meant 8 - how many CPUs ? 08:00
mnasiadka808:22
frickleror sometimes 4, but modern, fast ones08:35
mnasiadkawe could try switching multinode jobs to nested-virt labels - we would then get the modern ones - let me try08:43
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: DNM: Test multinode on nested virt labels  https://review.opendev.org/c/openstack/kolla-ansible/+/95049208:45
kevkomnasiadka: well, I think the issue is too much RAM against CPU 09:18
kevkomnasiadka: i think it should be 1/4 2/8 4/16 09:19
kevkofrickler: can I ask you for review please ? https://review.opendev.org/c/openstack/kolla-ansible/+/949812 second +2 09:21
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: DNM: Test multinode on nested virt labels  https://review.opendev.org/c/openstack/kolla-ansible/+/95049209:23
kevkomnasiadka: where I can see nodesets ( or labels ) ? To check ram/cpu  09:27
mnasiadkaYou can't, these are only flavor names on respective clouds - which sometimes have these values in the name, and sometimes not09:28
mnasiadkaAnd I don't think we can influence anything09:28
mnasiadkaWith new Zuul-launcher instead of nodepool there will be some more options with 16G of RAM09:28
mnasiadkaBut frickler is closer to these definitions ;-)09:28
kevkoi think you need 1/4 CPU/RAM 09:29
kevkoideally 4/1609:30
kevkoI would try 2/8 for example 09:31
kevkoah, ok i found it in openstack infra repo09:36
kevkois it 8vcpu and 8gb ram ? :D https://786b6091616ef4dbd1b1-3bbb48847b672b5467267c1efe6f2622.ssl.cf1.rackcdn.com/openstack/14193b183f33422c8d68f3e68371fdb1/primary/logs/facts.json09:39
kevkowe need v3-standard-2 or v3-standard-4 got from vexxhost https://vexxhost.com/pricing/09:48
kevkobut there is only https://paste.openstack.org/show/bPcuLkuV6IyOfS5qagOv/  v3-standard-8 :( in project-config repo 09:49
kevkomnasiadka: you've set it to v3-standard-8 ...so it should be stable as it is 8/32 09:52
kevkobut still...i think 2/8 can be enough 09:52
kevkomnasiadka: How do you actually estimate whether it's OK? 09:54
kevkobbezak: can I ask for review please :) ? https://review.opendev.org/c/openstack/kolla-ansible/+/94981209:56
bbezaksure, you can ask! :)09:57
bbezaklet me see09:57
kevkobbezak: thank you 09:59
kevkobbezak: it's nice patch i think ... and with ubuntu 24.04 useful as I can bootstrap and create venv with k-a10:00
kevkomnasiadka: btw, is it hard to ask for 4/16 flavor or 2/8  ? 10:11
kevkomnasiadka: it's really better than 8/8 ...10:11
opendevreviewPierre Riteau proposed openstack/kayobe master: Revert "[release] Use OpenStack 2025.1 release"  https://review.opendev.org/c/openstack/kayobe/+/95051210:14
mnasiadkakevko: I see you don't understand - ask every company delivering resources for adding a flavor? I guess so :)10:20
mnasiadkaAnd I doubt it would change anything10:20
opendevreviewPierre Riteau proposed openstack/kayobe master: CI: Remove openstack-tox-py39 override  https://review.opendev.org/c/openstack/kayobe/+/95051710:24
opendevreviewPierre Riteau proposed openstack/kolla-ansible master: CI: Use openstack-python3-jobs template  https://review.opendev.org/c/openstack/kolla-ansible/+/95051910:36
kevkomnasiadka: of course I understand :) 10:39
kevkomnasiadka: michalarbet@pixla:/tmp/project-config$10:40
kevkogrep -Ri nested-virt-debian-bookworm | awk -F ':' '{print $1}' | sort | uniq | sort | xargs grep -Ri providers: -A10 | grep cloud:10:40
kevkonodepool/nl05.opendev.org.yaml-    cloud: rax10:40
kevkonodepool/nl06.opendev.org.yaml-    cloud: openmetal10:40
kevkonodepool/nl07.opendev.org.yaml-    cloud: vexxhost10:40
kevkonodepool/nl08.opendev.org.yaml-    cloud: ovh10:40
kevkomnasiadka: I just thought it might be in their interest to provide fewer resources, and at the same time we would have the correct CPU/RAM ratio :) … the wolf would be full and the sheep intact …10:41
kevkomnasiadka: btw, I've been thinking about our eternal struggle with RabbitMQ, rate limiting, Cloudsmith APT... versions... etc...11:11
kevkomnasiadka: What about downloading Erlang as one big package, downloading RabbitMQ as one big package, and just installing those two packages?11:11
kevkomnasiadka: I mean Instead of using the APT repo? https://www.erlang-solutions.com/downloads-2/# and also https://github.com/rabbitmq/rabbitmq-server/releases for rabbitmq11:12
mnasiadkaand get more issues with github rate limits?11:12
mnasiadkaLet's not break something that works today ;)11:13
kevkomnasiadka: does github have also some rate limits ? :) 11:15
mnasiadkawho doesn't :)11:15
kevkomnasiadka: and include deb into git  ? :D 11:16
kevkomnasiadka: or rpm ? 11:16
kevkobad idea i know ... but ? :D 11:17
kevko60 mb + 30mb :D 11:17
kevkojust asking 11:17
mnasiadkaLet's just leave it, there's a lot of other things we need to do this cycle ;)11:23
opendevreviewPierre Riteau proposed openstack/kayobe master: CI: Update command to match allowlist_externals  https://review.opendev.org/c/openstack/kayobe/+/95052811:32
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use Epoxy extrepo release  https://review.opendev.org/c/openstack/kolla/+/95053011:50
kevkohaha ... we should build against bookworm backport epoxy not dalmatian :D 11:51
kevkomnasiadka frickler bbezak https://review.opendev.org/c/openstack/kolla/+/95053011:51
mnasiadkakevko: https://review.opendev.org/c/openstack/kolla/+/94975211:52
kevkomnasiadka: ahaaaa, thanks 11:57
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use bookworkm suite for rabbitmq APT repo  https://review.opendev.org/c/openstack/kolla/+/95053111:57
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use Epoxy extrepo  https://review.opendev.org/c/openstack/kolla/+/94975212:02
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use bookworkm suite for rabbitmq APT repo  https://review.opendev.org/c/openstack/kolla/+/95053112:02
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use bookworkm suite for rabbitmq APT repo  https://review.opendev.org/c/openstack/kolla/+/95053112:08
opendevreviewMerged openstack/ansible-collection-kolla master: Improve virtualenv handling and pip installation for SDK roles  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/94976712:14
opendevreviewMerged openstack/kolla-ansible master: Standardize Python interpreter handling  https://review.opendev.org/c/openstack/kolla-ansible/+/94981212:14
opendevreviewMichal Arbet proposed openstack/kolla master: Fix mock_open() expectations for Python 3.13+  https://review.opendev.org/c/openstack/kolla/+/95053312:29
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use Epoxy extrepo  https://review.opendev.org/c/openstack/kolla/+/94975212:30
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use bookworkm suite for rabbitmq APT repo  https://review.opendev.org/c/openstack/kolla/+/95053112:30
opendevreviewAmir Hossein Ahmadi proposed openstack/kolla master: swift: Reintroduce support for Swift deployment  https://review.opendev.org/c/openstack/kolla/+/95053412:33
opendevreviewAmir Hossein Ahmadi proposed openstack/kolla master: swift: Reintroduce support for Swift deployment  https://review.opendev.org/c/openstack/kolla/+/95053412:34
opendevreviewMichal Arbet proposed openstack/kolla-ansible stable/2025.1: [CI] Fix bootstrap testing  https://review.opendev.org/c/openstack/kolla-ansible/+/95029512:38
opendevreviewMichal Arbet proposed openstack/kolla-ansible stable/2025.1: Standardize Python interpreter handling  https://review.opendev.org/c/openstack/kolla-ansible/+/94981312:38
opendevreviewMichal Arbet proposed openstack/kolla-ansible stable/2025.1: [CI] Enable virtualenv testing for Debian/Ubuntu  https://review.opendev.org/c/openstack/kolla-ansible/+/95040512:38
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use bookworkm suite for rabbitmq APT repo  https://review.opendev.org/c/openstack/kolla/+/95053112:52
msalariamir58118: Did you get a response to your email sent to the core team?12:56
kevkomnasiadka: haha, today I am fixing the stuff and then I am noticing that I have a merge conflict and when I open ..it's the same fix from you :D :D :D ^^ 3.13 python 12:58
mnasiadkalol12:59
amir58118-2msalari: Unfortunately, no. i sent an email to Dr. Harbott , but i haven't recieved a responce, yet.12:59
mnasiadkaJust a small reminder - there's no regular IRC meeting today - we're meeting at https://meetpad.opendev.org/kolla-flamingo-ptg for a PTG recap13:00
opendevreviewMichal Arbet proposed openstack/kolla master: Fix mock_open() expectations for Python 3.13+  https://review.opendev.org/c/openstack/kolla/+/95039813:01
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use Epoxy extrepo  https://review.opendev.org/c/openstack/kolla/+/94975213:01
opendevreviewMichal Arbet proposed openstack/kolla master: debian: Use bookworkm suite for rabbitmq APT repo  https://review.opendev.org/c/openstack/kolla/+/95053113:01
kevkohh, thanks 13:01
fricklermsalari: amir58118-2: is there anything that cannot be discussed in public? I personally have zero interest in swift at all13:22
kevkomnasiadka:  I took the liberty of changing the commit message and adding more information here in your patch -> https://review.opendev.org/c/openstack/kolla/+/950398/5 13:37
amir58118-2frickler: that's totally fine, if the door is open for us to take over maintenance, we're happy to take full responsibility for developing and supporting swift in kolla.13:45
amir58118-2we think there’s still a valid use case for Swift in containerized environments, especially for operators who rely on Kolla and don’t have alternative deployment methods in place13:45
amir58118-2we believe the existing issues with Swift in Kolla can be addressed, and we’re fully committed to doing the work.13:48
kevkoamir58118-2: I would say that drop of swift will be good start, and you can send new master patches for review ..including tests ...and if it will be done in current cycle ...flammingo will be with your pure new swift, right ? 13:51
amir58118-3The only technical issue raised so far has been the incompatibility between HAProxy and the Swift proxy server. I can say we have a solution for that — we can use nginx or traefik as the load balancer for Swift to avoid interfering with the rest of the OpenStack deployment.13:52
frickleras long as there isn't broader interest in swift, I would suggest for you to maintain it in a downstream fork13:53
msalarikevko: That would be great. But naturally, we'll need some guidance along the way as we prepare the patch. What worries me is the statement that there's no interest in Swift — it makes me concerned that our efforts might end up being in vain.13:54
msalarifrickler: Are the technical reasons behind the lack of interest in Swift not something that can be shared? Is it just because there were serious issues with it in the past?13:55
fricklerwell to me ceph is the better solution, so swift is kind of useless13:57
msalarifrickler: So, does the fact that you dont like swift means that if we propose Swift role (modernized and without problems) from scratch and propose it, you won’t even review it?14:04
kevkofrickler: ceph is always better ...BUT ...every user is different ..for example swift is much benevolent with HW ...14:05
msalarikevko: and swift is better for multi-region data centers. swift is eventual consistent and ceph is strong consistent. use cases are different14:06
kevkoin overall Swift is less demanding on CPU and hardware than Ceph , simple replcation , plain disk files , run well on older HW or lowend ... 14:06
kevkoi am not saying that we are using it ...just wondering about pros/cons 14:07
msalariEventual consistency of swift gets better availability in network partition conditions and in multi-region clusters14:07
kevkoyep 14:07
amir58118-2+114:07
kevkoi will review ..from scratch ... but i am only one it looks like :D 14:07
mnasiadkaIt's not about that we dislike Swift, it's about why Kolla should support deploying Swift.14:08
kevkoas kolla is orchestration project for openstack projects which swift is still part of ? :) I would say 14:08
kevkoand still usable ...not like freezer or panko or watcher or those craps 14:08
mnasiadkaFor Swift to be sustainable and performant in Kolla - it would need to have support for another load balancer than the API HAProxy14:08
msalarikevko: frickler: I just need a clear answer to this question: if we invest time in redesigning Swift support for Kolla Ansible, will you consider it? I need this to define our company’s OKRs for this quarter.14:09
msalarimnasiadka: exact. our plan is right this14:09
kevko+114:10
amir58118-2mnasiadka: exactly, As mentioned earlier, I did point that out — and we already have a working solution using nginx or traefik instead of HAProxy for Swift.14:10
fricklerright, I won't spend time reviewing it, just like I don't for other topics like LE or rocky14:10
mnasiadkaWell, I would prefer it being second haproxy - we would need to build nginx/traefik in Kolla and there's no sane reason for doing that.14:11
amir58118-2mnasiadka: That's fair — using a second HAProxy is totally doable for us as well. if a second HAProxy instance is more aligned with Kolla's direction, we're happy to adapt to that.14:13
mnasiadkaamir58118-2, msalari: I can't promise it will  be merged as I can't promise I'll have time to review it - but if kevko is happy to guide you to success - then you can try.14:13
amir58118-2Thanks, that’s all we needed.14:13
amir58118-2Kevko: thanks for being the Yoda of our Swift mission =)14:15
msalarikevko: Are you going to give us a more encouraging answer?14:18
kevkoamir58118-2: Only what I believe is right, I do. The path of open source, this is.14:19
msalarikevko: sorry. just ignore my last message. thank you for support14:24
kevkoamir58118-2 msalari : Look, I personally don't need Swift support right now, but who knows – maybe in the future I will, if one of our clients requests it. For this reason, I’ll do the review for you and help guide you. I imagine Swift as being separate from OpenStack services. Maybe we can use the HAProxy role and introduce a second VIP, or14:24
kevkoset up Nginx/Traefik as mnasiadka suggested. Swift shouldn't affect the current services and should be installable using Kolla. If you add me as a reviewer, I’ll definitely keep an eye on it. That said, the policy requires two +2 votes... and I’m just one14:24
kevkoamir58118-2 msalari: I just want to see new patches, with tests ...from scratch ...14:25
amir58118-2kevko: Thanks a lot for your support. We’re actively working on the patch for Swift and making sure it meets all requirements, including tests. We’ll share the updates with you as soon as it’s ready for review.14:29
amir58118-2You can count on us for other Kolla-related matters as well. thanks to everyone.14:31
kevkoamir58118-2: do you have some work in progress patches now ? 14:32
amir58118-2yes14:33
amir58118-2https://review.opendev.org/c/openstack/kolla-ansible/+/94579114:33
amir58118-2https://review.opendev.org/c/openstack/kolla/+/95053414:33
amir58118-2Our goal is to reintroduce swift role from scratch.14:35
amir58118-2Therefore, we may submit a new patch specifically for Kolla-Ansible.14:36
PrzemekKIf You could look at changes/bugs from Piotr https://review.opendev.org/q/project:openstack/kolla-ansible https://bugs.launchpad.net/kolla-ansible/+bugs?orderby=-id&start=0 . Finally we upgraded first enviroment to 2025.114:38
kevkoPrzemekK: done 15:05
kevkomnasiadka bbezak: now backport 2025.1 please ? https://review.opendev.org/c/openstack/kolla-ansible/+/94981315:06
kevkowhole stack of course .. 15:09
kevkoso I can remove venv creation from Zuul CI in next patch and we have working auto venv creation 15:09
opendevreviewPiotr Milewski proposed openstack/kolla-ansible master: Fix missing vendoradata.json file for nova-metadata  https://review.opendev.org/c/openstack/kolla-ansible/+/95040615:19
opendevreviewPiotr Milewski proposed openstack/kolla-ansible master: Unnecessary comma in kolla-tolbox configuration - external rabbitmq  https://review.opendev.org/c/openstack/kolla-ansible/+/95031115:29
PrzemekK@kevko <3 15:46
*** darmach0 is now known as darmach17:27
-opendevstatus- NOTICE: Gerrit is being updated to the latest 3.10 bugfix release as part of early prep work for an eventual 3.11 upgrade. Gerrit will be offline momentarily while it restarts on the new version.17:34
opendevreviewVerification of a change to openstack/kolla-ansible master failed: CI: Use openstack-python3-jobs template  https://review.opendev.org/c/openstack/kolla-ansible/+/95051917:44
opendevreviewMerged openstack/kolla-ansible stable/2024.1: Pins ansible.utils in 2024.1 branch  https://review.opendev.org/c/openstack/kolla-ansible/+/94846220:07
opendevreviewVerification of a change to openstack/kolla-ansible master failed: CI: Use openstack-python3-jobs template  https://review.opendev.org/c/openstack/kolla-ansible/+/95051920:15
opendevreviewMerged openstack/kolla-ansible master: Unnecessary comma in kolla-tolbox configuration - external rabbitmq  https://review.opendev.org/c/openstack/kolla-ansible/+/95031121:20
opendevreviewMerged openstack/kolla-ansible master: CI: Use openstack-python3-jobs template  https://review.opendev.org/c/openstack/kolla-ansible/+/95051922:40

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