Monday, 2025-07-14

jrossero/ morning08:43
noonedeadpunkgood morning08:43
noonedeadpunkheh :)08:43
jrosserhah08:43
opendevreviewJonathan Rosser proposed openstack/ansible-role-pki master: Allow certificates to be installed by specifying them by name  https://review.opendev.org/c/openstack/ansible-role-pki/+/95423908:49
noonedeadpunkso I think there're some first results of azimuth driver for capi, and was able to spawn k8s 1.33 for it with our already deployed control cluster08:53
noonedeadpunkthus there's a chance of just do driver selection thing with telatively minor modifications08:54
jrosserdo we need to factor out the k8s control plane parts08:54
jrosseras that would be common08:54
noonedeadpunkyeah08:54
jrosserhow do you want to handle that, as for any variety of magnum in the future we will need a k8s in the infra nodes08:55
jrosserso that might be more "core OSA" than any of the drivers is08:55
noonedeadpunkthough it would highly likely be a fork of ansible-collection-kubernetes08:55
noonedeadpunkyeah, I was about to ask the same question :)08:55
noonedeadpunkI don't know yet how to handle that08:56
noonedeadpunkI think I would start from elaborating on what we already have in ops repo08:58
noonedeadpunkand then stage things out somewhere08:58
noonedeadpunkbut then a question would be what to do with driver specific things09:00
jrosserthere is a whole pile of complexity with integrating the stuff in the ops repo into (for example) an AIO09:00
jrosserits super expert level really09:00
noonedeadpunkyeah, right, and we probably can phase this things out for sure09:00
noonedeadpunkas given it's compatible - make sense to get it into core indeed09:01
jrosserso for example, putting drivers aside, we could add a playbook and conf.d/env.d into the main repos very simply kind of now09:01
jrosserdifferent question then would be the k8s/containers collection which we have forks of for ~years now09:02
noonedeadpunkso about playbooks - I'm looking through https://opendev.org/openstack/openstack-ansible-ops/src/branch/master/mcapi_vexxhost/playbooks and it looks it's somehow 50/5009:02
noonedeadpunkyou mean that, right? https://opendev.org/openstack/openstack-ansible-ops/src/branch/master/mcapi_vexxhost/playbooks/files/openstack_deploy/user-collection-requirements.yml#L2-L509:03
jrosseryes09:03
jrosserfor playbooks its mainly this https://opendev.org/openstack/openstack-ansible-ops/src/branch/master/mcapi_vexxhost/playbooks/k8s_install.yml#L16-L1709:04
noonedeadpunkwell, I think we have several options here, given I lost any hope about merging anything to it09:04
jrossermnaser: ^ reality is starting to really bite here :(09:05
noonedeadpunkbut we can be adding this to the os_magnum as well? https://opendev.org/openstack/openstack-ansible-ops/src/branch/master/mcapi_vexxhost/playbooks/mcapi_magnum_integration.yml09:05
jrosserwe can, for sure09:05
jrosseri guess the original question was kind of philosophical one about how we support out of tree drivers09:05
jrosserbut i'm not sure tbh how "in tree" the azimuth one is09:06
noonedeadpunkwell, it was mainly as I wanted to have some "universal" way for different drivers. and had no clue about any of them at a time09:06
noonedeadpunkat least it seems to be a bit better maintained atm, as missing 2 major k8s versions is kinda sucks...09:07
noonedeadpunkalso, given that I saw 1.31 even being spawned with heat driver (with some changes ofc009:08
noonedeadpunkanyway09:08
jrosserwell we can do it in pieces09:08
jrosserport 1/2 of whats in the ops repo to os_magnum, and 1/2 to plugins repo/main repo09:09
noonedeadpunkI kinda don't want to go into "in-tree" topic, as it doesn't matter. I'm more about having a way to pick the poison more naturally indeed09:09
noonedeadpunkyeah09:09
jrossersure09:09
noonedeadpunkbut I also think it might make sense to add second one to ops first, to see the full picture/scope?09:09
noonedeadpunk*second driver09:09
noonedeadpunkdunno though09:10
jrosseri think the choice there would be if we factor out the control plane k8s or not, and re-use it09:10
jrosserwell, actually it could probably be reused now as mcapi_vexxhost is a collection, so the control plane parts may be usable independantly anyway09:11
noonedeadpunkyes, right. and for that we need to decide what to do with ansible-collection-kubernetes09:11
noonedeadpunkyeah09:11
noonedeadpunkI was thinking about forking it more permanently and encompassing all fixes we need for it to be universal for both drivers09:12
noonedeadpunknot sure if do that into a github space or pull it to opendev09:12
noonedeadpunkprobably pulling to opendev is not really an option, as from what I can tell, it seems to be GPL 3.0 license: https://github.com/jrosser/ansible-collection-kubernetes/blob/main/galaxy.yml#L8-L909:17
noonedeadpunkweirdly though, license is not included in-tree....09:17
noonedeadpunkbut then in tasks it's apache 2.0: https://github.com/jrosser/ansible-collection-kubernetes/blob/main/roles/cluster_api/tasks/patch.yml#L709:18
noonedeadpunkI wonder if we should move proxy role just as a task to os_magnum and include it conditionally based on selected driver09:23
noonedeadpunkhttps://opendev.org/openstack/openstack-ansible-ops/src/branch/master/mcapi_vexxhost/roles/proxy/tasks/main.yml09:23
noonedeadpunkoh, we can't as it's targeting different group of hosts....09:23
noonedeadpunkanyway, I would be doing that all stuff in a "free" time09:25
noonedeadpunkbut kinda eager to complete and finally sort out capi drivers this cycle09:39
jrosseris anyone else using gerrit in a dark mode desktop14:15
jrosserthe in browser editor is almost unusable for me because the syntax hightlighting is picking colors not really readable on a dark background14:16
noonedeadpunkI'm using in white mode14:18
noonedeadpunkor well, it says "auto"14:18
jrosserfeels like the background changes to black but does not choose an alternative syntax highlighting pallete14:20
noonedeadpunkI think it works for me?14:21
opendevreviewJonathan Rosser proposed openstack/ansible-role-pki master: Generate ca_bundle during cert creation for standalone backend  https://review.opendev.org/c/openstack/ansible-role-pki/+/95462814:21
noonedeadpunkit's a bit toxic to my taste...14:22
noonedeadpunkhttps://ibb.co/XxTGDs8814:22
jrosserah hmmm https://pasteboard.co/bSizYwylwcDz.png14:23
noonedeadpunkok, that is not how I see it for sure14:24
opendevreviewJonathan Rosser proposed openstack/ansible-role-pki master: Generate ca_bundle during cert creation for standalone backend  https://review.opendev.org/c/openstack/ansible-role-pki/+/95462814:48
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Add debian trixie job definitions  https://review.opendev.org/c/openstack/openstack-ansible/+/95461615:45
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Add debian trixie job definitions  https://review.opendev.org/c/openstack/openstack-ansible/+/95461616:02
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-plugins master: Add debian trixie as a supported platform  https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/95497616:50
jrosserwe should probably set `openstack.osa` collection as installing from master branch during development, theres a surprise waiting in a-c-r which doesnt do that16:51
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Use the master branch of the openstack.osa collection for dev work  https://review.opendev.org/c/openstack/openstack-ansible/+/95497916:58
noonedeadpunkah, yes, my bad, sorry17:02
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-lxc_hosts master: Fix sync of /etc/apt/mirrors/ to container base image.  https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/95498017:04
jrosseransible-hardning fail on py3.13 https://docs.python.org/3/library/spwd.html17:12
noonedeadpunkoh, we have a module there17:15
noonedeadpunkdoesn't look like python-pam supports it either17:16
jrosseri found an approach like this https://github.com/saltstack/salt/pull/67788/commits/8a8fc0814264364de2928aeb1207226d18b6f2f817:22
jrosserwhich is kind of gross17:22
noonedeadpunkdoes not look too complex though....17:24
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-haproxy_server master: Always install netcat-openbsd on debian  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/95498517:26
noonedeadpunkwe have quite some things depending on this module17:26
noonedeadpunkwhich kinda make sense as well17:26
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-memcached_server master: Always install netcat-openbsd on debian  https://review.opendev.org/c/openstack/openstack-ansible-memcached_server/+/95498617:31
jrosserso i get as far as galera with really only small changes on trixie17:33
jrosserunsurprisingly there is no repo for that17:33
noonedeadpunkwell, I think we can do same as for EL10 now there?17:48
NeilHanlonnoonedeadpunk: so.. i forgot to update you last week, apologies.20:01
NeilHanlonsystemd-networkd can be grabbed from EPEL for EL9 and EL10. it's in the `systemd-extras` package: https://koji.fedoraproject.org/koji/buildinfo?buildID=220070020:01

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