Thursday, 2022-06-02

yoctozeptohrw: ubuntu boots, cirros does not, both use the same kernel -> likely the bootloader is the difference07:00
hrwyoctozepto: nope08:16
yoctozeptoplease elaborate08:17
hrwyoctozepto: cirros uses 18.04 kernels 08:17
yoctozeptooh! roger that08:17
yoctozeptoso ubuntu 18.04 does not boot either then?08:17
hrwyoctozepto: and the problem is our use of 'max' cpu model which changes from qemu version to version08:17
yoctozeptoack, I see08:18
hrwso vote for https://review.opendev.org/c/openstack/kolla-ansible/+/844321 and it will work again08:18
yoctozeptoapproved08:19
hrwcool08:19
yoctozeptoI did not see it because it was marked WIP08:19
fricklerhrw: fwiw I tried with a cirros image built with jammy kernel, that didn't boot either08:19
yoctozeptohmm08:19
yoctozeptoso the bootloader08:20
hrwyoctozepto: no.08:20
yoctozepto:D08:20
yoctozeptoI'm not following08:20
hrwfrickler: Debian 11 does not boot. Debian 11 + backports kernel does08:20
hrwthe problem is cpu model not kernel/bootloader/etc08:20
hrwQEMU 7.0 got support for ARM Cortex-A76 and Neoverse N1 cpu cores. which are more advanced than Cortex-A72 qemu knew before08:21
fricklerbut if cpu model is broken, why do some images still boot? I'd like to build a cirros image that works with max08:21
guesswhatGuys? Why is octavia_network_type: "tenant" ( https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavia.html ) not reliable for production ?08:22
hrwso amount of features of 'max' cpu increased. still it is virtual cpu which has all qemu supported arm cpu features but does not look like any existing one08:22
hrwI prefer to not spend time getting max working again as this is not something you use in real environments08:23
hrwI checked the issue, reported it upstream and provided fix for our project.08:24
fricklerhrw: hmm, o.k., I guess that that's a valid argument. so you would consider using a72 a permanent solution? until maybe upstream fixes something?08:24
hrwand have some patches to k-a in a queue08:24
hrwfrickler: a72 ftw. it is covering probably 90% of arm market, nearly all arm servers and most of cloud offering08:25
hrwespecially when we use distro provided firmware/kernels which may not cover latest-greatest08:26
yoctozeptoalso, it does not really matter for k-a - we are not responsible for fixing qemu on aarch64; our job is done as it is08:26
hrwyep08:26
hrwsorting some of qemu things is my part of my other hat08:27
guesswhatmgoddard Question, Why is ctavia_network_type: "tenant" not reliable for production ? ( https://github.com/openstack/kolla-ansible/blame/aad331069def7faf09b046c95d9dca827a7bede2/doc/source/reference/networking/octavia.rst#L400 ) Thanks08:32
mnasiadkaguesswhat: because it's relying on systemd units that configure the interface, which might fail - use on your own risk08:38
mnasiadka(or something else in OVS might fail - because these are basically OVSPorts)08:39
guesswhatmnasiadka: It fails for me, at least LBs are in Pending Upgrade or Error state after reboot, I tried to add Restart=on-failure to octavia-interface.service, but it randomly fails ofc...08:40
guesswhatWhats the other solution ? Everything includes OVSPorts, isnt?08:40
mnasiadkawell, I just meant this solution does OVS components outside of Neutron08:41
kevko\o/09:11
kevkomorning 09:11
hrwmnasiadka, kevko: https://review.opendev.org/c/openstack/kolla/+/844311 - please review09:26
hrwI am open for suggestions - especially for better argument name09:26
kevkogoing to09:27
guesswhatmnasiadka: and does exist some other solution for kolla? or its  octavia_network_type: "tenant" or nothing, cuz it can not work with default install  octavia_network_type: "provider" by default09:32
mnasiadkaguesswhat: and why it cannot?09:33
guesswhatby default kolla creates vxlan lb-mgmt-net, octavia worker and healthcheck can not reach this network..09:34
opendevreviewMerged openstack/kolla-ansible master: Switch to Cortex-A72 cpu on AArch64  https://review.opendev.org/c/openstack/kolla-ansible/+/84432109:36
kevkoguesswhat: are u sure ? 09:39
yoctozeptoyay, aarch unbroken09:40
yoctozeptonow time to backport09:40
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/yoga: Switch to Cortex-A72 cpu on AArch64  https://review.opendev.org/c/openstack/kolla-ansible/+/84438409:40
opendevreviewMarcin Juszkiewicz proposed openstack/kolla-ansible stable/yoga: Switch to Cortex-A72 cpu on AArch64  https://review.opendev.org/c/openstack/kolla-ansible/+/84438409:40
opendevreviewMarcin Juszkiewicz proposed openstack/kolla-ansible stable/wallaby: Switch to Cortex-A72 cpu on AArch64  https://review.opendev.org/c/openstack/kolla-ansible/+/84438509:41
hrwyoctozepto: GMTA ;D09:41
yoctozeptooh well09:41
yoctozeptothough we don't need it before yoga09:41
guesswhatkevko: https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/octavia/tasks/prepare.yml#L105-L107 its ommited if not specified, that means fallback to vxlan thus there is no chance that worker and healtcheck running on the management network could reach the lb-mgmt-net , correct?09:42
guesswhatmnasiadka ^09:42
yoctozeptoguessing we can merge for consistency09:42
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/xena: Switch to Cortex-A72 cpu on AArch64  https://review.opendev.org/c/openstack/kolla-ansible/+/84438609:42
hrwyoctozepto: need or not it is better to not use max09:43
* hrw -> updating patch09:43
mnasiadkaguesswhat: so just set it properly in octavia_amp_network dict?09:46
opendevreviewMarcin Juszkiewicz proposed openstack/kolla master: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84431109:47
guesswhatmnasiadka: what should I set there? it will work only for another physnet ( not for management network ) and it has to be a flat, external network ... , otherwise one must use ports, veth pairs  + bridge or routing with router...  Octavia is quite confusing in kolla, I would like to see working example, as docs is not helpful in this case..09:51
yoctozeptohrw: agreed09:51
hrwlong time since my simple patch got so many comments09:53
opendevreviewMarcin Juszkiewicz proposed openstack/kolla master: doc: get rid of remainders of binary images  https://review.opendev.org/c/openstack/kolla/+/84441110:04
opendevreviewMerged openstack/kolla-ansible master: Add support for custom alert notification templates  https://review.opendev.org/c/openstack/kolla-ansible/+/84210010:05
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Remove configuration related to api_workers  https://review.opendev.org/c/openstack/kolla-ansible/+/84313010:09
opendevreviewBartosz Bezak proposed openstack/kolla-ansible stable/xena: designate: allow designate_ns_record to be a list  https://review.opendev.org/c/openstack/kolla-ansible/+/84441611:03
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Remove nova related config from placement  https://review.opendev.org/c/openstack/kolla-ansible/+/84442011:26
opendevreviewBartosz Bezak proposed openstack/kolla-ansible stable/xena: designate: allow designate_ns_record to be a list  https://review.opendev.org/c/openstack/kolla-ansible/+/84441611:41
opendevreviewMerged openstack/kolla-ansible master: Split haproxy and keepalived restarts  https://review.opendev.org/c/openstack/kolla-ansible/+/83893011:45
opendevreviewBartosz Bezak proposed openstack/kolla-ansible stable/wallaby: designate: allow designate_ns_record to be a list  https://review.opendev.org/c/openstack/kolla-ansible/+/84442512:00
opendevreviewBartosz Bezak proposed openstack/kolla-ansible stable/wallaby: designate: allow designate_ns_record to be a list  https://review.opendev.org/c/openstack/kolla-ansible/+/84442512:02
bhreddyHi All, I am facing issue while using merge_configs module. I am merging api-paste.ini in nova, neutron and other services, the issue is the colon ":" is getting replaced with equals to "=" in target container 12:10
bhreddyfor example, In the nova api-paste.ini template "/: meta" changed as "/ = meta" in container12:12
kevkobhreddy: did you fill a bug somewhere ? 12:23
fricklermnasiadka: yoctozepto: one question you didn't answer regarding stable releases: should I include kayobe and/or ansible-collection-kolla?12:24
fricklero.k., ansible-collection-kolla doesn't have updates yet, so will skip that anyway for now12:26
bhreddyno I didn't file any bug12:28
bhreddyI thought there will be extra quotes or slashes we can use to retain colon12:29
bhreddyI tried like {{ ":" }}  and {{ ':'}} and backslash followed by colon...nothing helped me12:29
fricklerincluded kayobe now, let me know if I should drop it. https://review.opendev.org/c/openstack/releases/+/844438 Tag monthly kolla stable releases12:32
SvenKieskeI got a question regarding https://review.opendev.org/c/openstack/kolla-ansible/+/802304 (allow designate_ns_record to be a list): is it already possible to define multiple different dns backend pools via kolla-ansible?12:41
opendevreviewMerged openstack/kolla master: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84431112:45
opendevreviewMerged openstack/kolla master: doc: get rid of remainders of binary images  https://review.opendev.org/c/openstack/kolla/+/84441112:45
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Add proxysql support for database  https://review.opendev.org/c/openstack/kolla-ansible/+/77021512:52
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Edit services roles to support database sharding  https://review.opendev.org/c/openstack/kolla-ansible/+/77021612:52
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: [CI] Test ProxySQL with shards in the nova cells scenario  https://review.opendev.org/c/openstack/kolla-ansible/+/77062112:52
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: [DNM] Trigger cells job  https://review.opendev.org/c/openstack/kolla-ansible/+/83891612:52
opendevreviewPierre Riteau proposed openstack/kayobe stable/wallaby: Use net_mask filter instead of ansible's ipaddr  https://review.opendev.org/c/openstack/kayobe/+/84438713:12
opendevreviewPierre Riteau proposed openstack/kayobe stable/victoria: Use net_mask filter instead of ansible's ipaddr  https://review.opendev.org/c/openstack/kayobe/+/84438813:12
opendevreviewMaksim Malchuk proposed openstack/kolla stable/yoga: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84445513:29
opendevreviewMaksim Malchuk proposed openstack/kolla stable/xena: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84445613:30
opendevreviewMaksim Malchuk proposed openstack/kolla stable/wallaby: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84445713:30
opendevreviewMerged openstack/kolla-ansible master: Remove configuration related to api_workers  https://review.opendev.org/c/openstack/kolla-ansible/+/84313013:38
opendevreviewVerification of a change to openstack/kolla-ansible master failed: Remove nova related config from placement  https://review.opendev.org/c/openstack/kolla-ansible/+/84442013:38
opendevreviewPierre Riteau proposed openstack/kolla-ansible master: Increase openstack-exporter timeout to 45 seconds  https://review.opendev.org/c/openstack/kolla-ansible/+/84445913:55
opendevreviewPierre Riteau proposed openstack/kolla-ansible master: Increase openstack-exporter timeout to 45 seconds  https://review.opendev.org/c/openstack/kolla-ansible/+/84445913:57
mnasiadkafrickler: yes, include kayobe for now :)14:05
opendevreviewMaksim Malchuk proposed openstack/kolla stable/yoga: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84445514:16
opendevreviewMaksim Malchuk proposed openstack/kolla stable/wallaby: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84445714:17
opendevreviewMaksim Malchuk proposed openstack/kolla stable/xena: Allow to provide own repos.yaml file  https://review.opendev.org/c/openstack/kolla/+/84445614:18
SvenKieskeI got an architectural question, because I'm currently revisiting some internal work on kolla-ansible: Would it be an interesting usecase to provide a facility to further split networking? We are entertaining the idea of a separate logging/monitoring network (currently the internal api network is used for that)14:34
SvenKieskewe'd rather not only use this downstream and have to patch kolla-ansible into eternity, so I'd like to ask if there would be interest in providing templates to use a dedicated (virtual) logging network?14:35
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Remove nova related config from placement  https://review.opendev.org/c/openstack/kolla-ansible/+/84442014:36
hrwSvenKieske: I think that if it has a use and would come with documentation then should be fine15:42
opendevreviewVerification of a change to openstack/kolla-ansible stable/xena failed: designate: allow designate_ns_record to be a list  https://review.opendev.org/c/openstack/kolla-ansible/+/84441615:53
opendevreviewMerged openstack/kolla-ansible stable/wallaby: designate: allow designate_ns_record to be a list  https://review.opendev.org/c/openstack/kolla-ansible/+/84442518:10
guesswhatCan I add interface to br-int somehow automatically via ansible parameter?19:36
guesswhatkevko ping20:01
guesswhat@kevko20:26
opendevreviewMerged openstack/kolla-ansible stable/xena: designate: allow designate_ns_record to be a list  https://review.opendev.org/c/openstack/kolla-ansible/+/84441620:34

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