Tuesday, 2023-03-21

jrossergood morning08:13
jrosserseems we are a bit stuck on merging things08:13
jrosserbut this https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/87766508:13
jrosserand https://review.opendev.org/c/openstack/openstack-ansible-os_swift/+/87753408:14
jrossercould use another look08:14
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-rabbitmq_server stable/zed: Do not use 'always' tag in inappropriate places  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/87801508:21
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-rabbitmq_server stable/yoga: Do not use 'always' tag in inappropriate places  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/87801608:21
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-rabbitmq_server stable/xena: Do not use 'always' tag in inappropriate places  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/87801708:21
noonedeadpunkmornings08:59
ThiagoCMCMorning! =P09:00
noonedeadpunkyeah, things with reviews are bad indeed since both Damian and Andrew are out for a while...09:20
noonedeadpunkBut I've finally managed to deploy a compute! I needed roughly 3 weeks for that :D09:39
jrosserwow!09:40
jrosserwas that some unusual situation?09:40
noonedeadpunkWell. I dropped around 70% of manual for compute deployment as a reuslt09:41
noonedeadpunk(internal one)09:41
noonedeadpunkSo a new collection, couple of new roles, huge refactoring...09:41
noonedeadpunkIncluding zuul with required projects and dummy CI09:41
noonedeadpunkSo mainly trying to adopt gitops rails to ansible09:42
noonedeadpunkBut it's still not perfect and there's room for improvement...09:43
noonedeadpunkI think next step that it's not done - is fetching and parsing diff for the last change, so that zuul could run this add-compute.sh command and supplying it with compute names from the last diff. And actually undesrtanding that diff did add compute and not removed it, for example09:50
jrosseri have been trying the ceph read and write caches10:01
noonedeadpunkany luck with these?10:43
jrosseri have them both working, by seeing that there is stuff in the drives for both10:43
jrosserbut coming up with a convincing benchmark is not so obvious10:43
noonedeadpunkoh, sweet, given there're barely docs even configuring is quite a challange I assume10:46
jrosserthe parent read cache is pretty undocumented and no-one on the internet describes using it10:49
jrosserso configuration was complete mystery but actually simple in the end, needing umask=002 and setting the daemon to run with user=ceph group=libvirt-qemu otherwise it was all just permission denied type errors10:50
jrosserneeded a ton of `strace` to figure out what was failing though :/10:50
noonedeadpunkdoh... Yeah, I'd likely just gave up there....10:59
jrossernoonedeadpunk: what do you think about this https://github.com/openstack/openstack-ansible-os_nova/blob/master/defaults/main.yml#L25112:36
jrossershould it be something like12:36
jrosser`"{{ (openstack_service_publicuri_proto | default('http')) | ternary('ws', 'wss') }}"`12:37
jrosserbecuase certainly at the moment 'ws' is wrong 12:37
noonedeadpunkI'm not sure I did use serialconsole - I assume it's for ironic?12:39
noonedeadpunkBut I think I'd do some mapping maybe to say that http is ws, https is wss...12:41
noonedeadpunkrather then use ternary, as it would be like "{{ (openstack_service_publicuri_proto | default('http') == 'http') | ternary('ws', 'wss') }}"12:42
noonedeadpunkuh, closing bracket in the wrong place12:42
jrosseroh hrrm yes i just typo that12:42
jrosserwell also we have an odd situation with consoles12:43
jrosserarm hosts are serial console12:43
jrosserand in my deployment that is only working because by luck i have ironic deployed as well12:43
jrosserwhich enables the serial console proxies12:43
jrosserfor a mixed deployment of x86 and arm today i think consoles are broken, as nova_console_type can only be one thing when deploying the console proxy and setting up haproxy12:44
jrosseri am not totally sure what to do about this - other than `nova_console_type` currently controls too many things which are not always the same12:46
noonedeadpunkyeah.  I recall that but didn't have chance to look what can be done there12:46
noonedeadpunkand to be frank I'm not aware about all possible options that are present12:46
jrosseri was wondering if we should just install the console proxies unconditionally - i.e simplifly12:46
jrosseri need to think about it more really12:47
noonedeadpunkany reason why we can't convert it to the list?12:48
jrosserwell ultimately it's a role default for os_nova https://github.com/openstack/openstack-ansible-os_nova/blob/master/defaults/main.yml#L28612:49
jrosserthat specifies the console type for each host/group/whatever12:49
jrosserso that cant really be changed12:49
jrosserit's basically a mistake to use that var to drive haproxy or the console proxy deployment12:50
jrosserbecasue it can and will vary by host12:50
noonedeadpunkso for haproxy we basically need to have another one which will be constructed based on hostvars for all hosts in some groups?12:51
jrosserright - or even just a list of all enabled types12:51
noonedeadpunkWell, yeah, but you think to define it manually?12:52
noonedeadpunkor try to calculate?12:52
jrossernot sure tbh12:52
jrosserfeels like getting near needing all facts for all hosts to be valid in order to calculate it12:53
noonedeadpunkset default to one element that would be nova_console_type?12:53
jrosser^ yes something like this12:53
jrosser`{{ ([ nova_console_type ] + [ ironic_console_type ]) | unique }}"`12:54
jrossermaybe like that12:54
jrosserthat wouldnt automatically cover a mixed x86/arm deployment though, but maybe thats a valid case for an override anyway12:54
noonedeadpunkI'm quite confused about having nova_ironic_console_type and ironic_console_type as fully independant things12:55
noonedeadpunkand also - should be reject `disabled` then?12:56
noonedeadpunkor what are we gonna do with it....12:56
jrosserhah yes12:56
noonedeadpunkand we're also comparing nova_console_type to ironic_console_type 12:57
noonedeadpunkhttps://opendev.org/openstack/openstack-ansible/src/branch/master/inventory/group_vars/haproxy/haproxy.yml#L40312:57
noonedeadpunkso these should be mappings then or smth... ugh12:57
jrosserright becasue there is horrible logic if they are same or different12:58
jrosserdue to the bad definition of the existing vars12:58
noonedeadpunkaha, ok, so that's what we're trying to get rid of12:58
jrossersome of it, yes12:58
jrosserit's like independant things12:59
jrosser(compute nodes may have different nova_console_type) + (console proxy for each enabled type must be deployed) + (ironic might use serial consoles) + (correct haproxy parts need deploying depending on all this)12:59
noonedeadpunkso you can have a mix of spice + novnc ?13:17
noonedeadpunkOr it's jsut about novnc or spic + serial for arm?13:17
jrosseri would think you can do that if you really wanted to13:17
admin1using haproxy_frontend_raw: , if i manually do   backends like nova.domain.com, keystone.domain.com etc, do i just put   keystone.domain.com in keystone_service_publicuri ? 13:35
admin1without http or https or the port right .. just confirming 13:36
admin1hmm.. will deploy an aio and test13:39
admin1have to manually do  service.domain.com -> service-back 13:40
noonedeadpunkyeah I don't think we have straight way of doing that as of today14:16
jrossershould be something for next cycle - we can do this nicely with the haproxy maps in future14:18
noonedeadpunk++14:24
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Convert haproxy_security_headers_csp to a multiline string  https://review.opendev.org/c/openstack/openstack-ansible/+/87808214:41
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Define individual haproxy serices for each console type  https://review.opendev.org/c/openstack/openstack-ansible/+/87808314:41
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Define individual haproxy services for each console type  https://review.opendev.org/c/openstack/openstack-ansible/+/87808314:42
jrossernoonedeadpunk: ^ this should leave the existing behavour the same but make it easier to refactor for multiple console types14:42
jrosserok and also this is the root cause of the existence of `nova_ironic_console_type` https://opendev.org/openstack/openstack-ansible-os_nova/src/branch/master/defaults/main.yml#L512-L52514:48
jrossercurrently we have a group `nova_console` and also `ironic_console` - and the only point of `ironic_console` is to deploy more nova_serial_console services14:49
jrosserand those get installed in the `ironic_compute` container, rather than where the normal nova console proxies would go /o\14:49
jrosserthere is another possible simplification, which would be to get rid entirely of `ironic_console` group and just use the regular nova console proxies instead of something special for ironic (which aren't special at all, it's just another 3 nova-serialproxy processes running)14:51
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Define individual haproxy services for each console type  https://review.opendev.org/c/openstack/openstack-ansible/+/87808315:01
noonedeadpunk#startmeeting openstack_ansible_meeting15:03
opendevmeetMeeting started Tue Mar 21 15:03:02 2023 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
opendevmeetThe meeting name has been set to 'openstack_ansible_meeting'15:03
noonedeadpunk#topic rollcall 15:03
noonedeadpunko/15:03
NeilHanlono/15:03
admin1o/15:03
jrossero/ hello15:05
noonedeadpunk#topic office hours15:05
noonedeadpunkI messed up this week and haven't done what I've promised I will do - talking about sending ML regarding PTG and working on haproxy15:06
noonedeadpunkAnd releases :(15:06
noonedeadpunkWill cover all my debt till EOD15:06
noonedeadpunkRegarding PTG. Last week during TC meeting it was proposed for projects to have operators hours as previous year15:07
noonedeadpunkTo be frank for me that decision has come too late thus I'm not sure if we should have one or not15:08
noonedeadpunkwdyt?15:09
jrosserare they well attended?15:09
noonedeadpunkwell, were mixed feedback from last one15:10
noonedeadpunk*was15:10
jrosserwell - i don't know15:13
noonedeadpunkiirc there were couple of unique nicnames in zoom last year for us15:13
jrosserwell we should do it15:14
noonedeadpunkIn my report I've sent I've mentioned that around 50% were new ppl on operator hours comparing to PTG15:15
noonedeadpunkBut given we were 12 ppl, so around 50% could mean 4-5 new folks15:15
noonedeadpunkok. then let's do it :) what time we want to schedule that?15:15
noonedeadpunkI assume wednesday?15:16
jrosserthats ok for me15:16
NeilHanlonI'll try to get a few folks to join that might be interested from Rocky15:17
noonedeadpunklike... 17 utc? least occupied slot in terms of intersection15:17
jrosserthis is next week right?15:17
noonedeadpunkYup15:18
NeilHanlongood w/ me15:18
noonedeadpunkAwesome NeilHanlon, that would be great15:18
* noonedeadpunk still regrets we didn't catched up on FOSDEM for some beer15:18
NeilHanlonme too :( that weekend was so crazy15:18
noonedeadpunkOk, then I'll book an operator hours slot and will include that in email15:19
noonedeadpunkWhere are we with haproxy topic?15:23
noonedeadpunkSince Damian is not around for next couple of weeks (hopefully), I'm going to pick up his part15:23
jrosserpretty stalled i think15:24
jrosserlooking at the topmost-ish patch there is a bit of a mess in the stack https://review.opendev.org/c/openstack/openstack-ansible/+/87118915:25
jrosserthis is just needing a extra section in the releasenote https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/87118815:29
noonedeadpunkaha, but at least we've merged stepca15:29
noonedeadpunkand have votes for map files15:29
* NeilHanlon has minor edits for his writings because of StepCA... but that's not a "problem"15:30
jrosserwell we can maybe try to move things on a bit there after the meeting?15:30
noonedeadpunkWell, thinking about extra section, I think maybe it's not needed after all...15:30
noonedeadpunkbecause we're keeping old behaviour for now...15:32
noonedeadpunkso deprecation might be enough...15:32
jrosseri wonder also if we should consider the scope for this cycle15:32
noonedeadpunkyeah, we totally should15:33
jrosserlike if we don't want a huge rush we could push TLS backends to next cycle15:33
noonedeadpunkExcept of this haproxy thing I really want to fix systemd_service bug, as it's nasty...15:33
jrosserfeels like we could land the current haproxy changes and also address the large amount of unmerged stuff15:33
noonedeadpunkWell, we're going to have a deployment where internal TLS is going to be an acceptance criteria...15:34
noonedeadpunkI'm not sure how good reason is that to land TLS though...15:34
jrosseri wonder how close we are with a big set of overrides to enable15:35
noonedeadpunkLikely we can use local forks with backports for that...15:35
jrossercertainly for haproxy, not the roles though i guess15:35
jrosseralso nasty is the adding a compute node bug15:37
noonedeadpunkI haven't hit that on Xena though15:37
jrosserstuarts workaround was to run the playbook with no --limit until it gathered facts from all the compute nodes, CTRL-C at that point and re-run with the limit15:37
jrosserand you're sure you don't have facts for the * other compute nodes?15:38
noonedeadpunkWell. I've added https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks/common-tasks/gather-hardware-facts.yml as a standalone playbook to the local collection...15:38
noonedeadpunkI _think_ I don't but I will double-check that tomorrow15:38
jrosseri think there was someone else also comment on the bug about having the same thing15:39
noonedeadpunkyup15:39
noonedeadpunkalso on Zed jsut in case15:39
jrosserhmm ok15:39
noonedeadpunkbut well. I;ve jsut realized we're having `echo` in front of command for all these years... 15:40
noonedeadpunkin add-compute.sh15:40
noonedeadpunkSo it didn't look like being used at all15:40
noonedeadpunkbut yes, it's quite nasty15:41
noonedeadpunkAnd yeah, I'd try to scope bug fixing mostly this release. 15:42
noonedeadpunkEventually, we also need to add n-2 upgrades. It's not a hard requirement this time, but highly appreciated practise15:42
* jrosser looks at current upgrade jobs....15:43
jrosserwhy do we bother running the centos ones :)15:43
noonedeadpunkwell, they're passing, aren;'t they?15:45
noonedeadpunkNV but green15:45
noonedeadpunkI think we'd need to add some logic to or extra option to run-upgrade.sh15:46
noonedeadpunkas it's not flexible at all about source/target releases15:46
jrosseractually the failing ones are distro upgrade jobs15:46
jrosserand we don't run any regular non upgrade distro jobs alongside those15:47
noonedeadpunkwell. distro for ubuntu was passing lately...15:47
noonedeadpunkas well as for centos15:47
jrosseri was looking here https://review.opendev.org/c/openstack/openstack-ansible/+/87781315:47
NeilHanloni've been meaning to look at distro jobs for rocky soon15:47
* NeilHanlon makes a note15:47
noonedeadpunk`'ansible_os_family' is undefined`15:47
noonedeadpunkWell, it's caused by quite recent change15:48
jrossermy fault :)15:48
noonedeadpunkI'm trying to keep an eye on distro from time to time15:48
jrosserNeilHanlon: it should be a case of adding a correctly formed job name to the stuff in zuul.d and it should run one15:49
jrosserso really small effort to see how far it does/doesnt get15:49
noonedeadpunkGiven how we're critisized for using u-c - having distro as argument why osa is still good is quite handy15:49
jrosserhmm yes well i do notice those comments too15:49
noonedeadpunkI still see using packages as a nightmare deployment15:50
jrosserbut thats a univeral problem for all community deployment tools that dont have a huge army of QA people keeping packages updated15:50
noonedeadpunkyeah, so then you should rely on your distro and unattended-upgrades...15:51
noonedeadpunk(no)15:51
noonedeadpunkeventually one more thing that raised couple of times - if we want to make some migration guide from tripleo to have a good picture and hopefully get more users/maintainers for rhel distros15:52
noonedeadpunkThat could be quite profitable but I struggle having even very humble estimate of time for that...15:53
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Fix openstack client installs for 'distro' method  https://review.opendev.org/c/openstack/openstack-ansible/+/87811415:54
NeilHanlonnoonedeadpunk: i'll take a stab at that.. might have a coworker who would be interested15:57
noonedeadpunkoh rly?15:57
NeilHanlonhave a few technical sales people who like writing :P 15:57
NeilHanlonwhen do 'experimental' jobs run? i see a rocky distro metal job configured right now15:58
noonedeadpunkBecause eventually transfer to osa might be more straightforward as we're having distro path, which is same rdo. 15:58
noonedeadpunkNeilHanlon: you need to comment on some change `check experimental`15:59
NeilHanlonah.. i will move to check then for 'fun' :) 15:59
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Add rockylinux-9 distro metal job to check pipeline  https://review.opendev.org/c/openstack/openstack-ansible/+/87811516:00
NeilHanlondarn you beat me to it :P 16:00
jrosseroh!16:00
NeilHanlonno worries.. afk for a bit anyways :) 16:01
noonedeadpunkyeah, that would work as well :D16:01
jrosseri wonder why we have check pipeline on those jobs but not gate16:01
jrosserthat is odd16:01
noonedeadpunkMaybe we should actually replace distro job with rocky - as we've agreed some time ago to make more focus on rocky comparing to c9s16:01
NeilHanlon#yolo ... yolo16:01
noonedeadpunkbut never had time to follow up on that16:02
jrosserhopefully that would be pretty easy, and bring some more stability16:02
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Add rockylinux-9 distro metal job to check pipeline  https://review.opendev.org/c/openstack/openstack-ansible/+/87811516:03
noonedeadpunkyeah, or at least ways to fix will be around faster :)16:03
noonedeadpunk#endmeeting16:03
opendevmeetMeeting ended Tue Mar 21 16:03:48 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:03
opendevmeetMinutes:        https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-03-21-15.03.html16:03
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-03-21-15.03.txt16:03
opendevmeetLog:            https://meetings.opendev.org/meetings/openstack_ansible_meeting/2023/openstack_ansible_meeting.2023-03-21-15.03.log.html16:03
jrossernoonedeadpunk: if you like we can run through the haproxy stuff a bit?16:04
noonedeadpunkGive me 2-3 mins to push release patches 16:04
jrossermaybe it's all ok - just shout if you want to discuss any of it16:04
noonedeadpunkyup, done with releases16:08
noonedeadpunkWell, it's hard to tell if it's ok or not, as I was trying not to dig too deep and offload this thing and just review once it's done...16:08
noonedeadpunkI think I'm kind of clear with scope of what needs to be done at least to split haproxy config into parts16:10
noonedeadpunkbut I kind of missed your discussion about rebasing and reworking some bits to respect maps16:11
noonedeadpunkAnd what excatly should be simplified with them16:12
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Convert haproxy_security_headers_csp to a multiline string  https://review.opendev.org/c/openstack/openstack-ansible/+/87808216:16
jrossernoonedeadpunk: i think that was this one https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/87118816:17
jrosserso now looking at the comment we can probably merge that16:18
jrosseras it provides forward<>backward compatbility with old and new service data formats16:18
noonedeadpunkI've changed it to be only related to the var format change16:18
noonedeadpunkyeah16:18
jrosserthen i think this should be removed from the stack / abandoned https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/87577916:20
noonedeadpunkare you sure about that?16:21
jrossernope :)16:21
jrosseri keep confusing that one with the "temporary" stuff16:21
noonedeadpunkat very least it solves issue with triggering pki handlers16:21
noonedeadpunkI think that temporary stuff has been already abandoned16:22
noonedeadpunkat least I don't see it16:22
jrosserhmm 875779 is actually two completely distinct changes16:23
noonedeadpunkThis one? https://review.opendev.org/c/openstack/openstack-ansible/+/87232816:23
jrosserone to use the custom named handler for PKI role16:23
jrosserand the other to add the extra tasks file for calling with tasks_from:16:23
noonedeadpunkOk, let me fix that then16:23
jrosserthe subtle one is the PKI one and that really deserves it's own commit message to explain, so yeah16:24
noonedeadpunkyeah, fair16:24
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server master: Provide custom handler name to PKI role  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/87577916:27
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server master: Add tasks to configure external services only  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/87813116:31
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server master: Provide custom handler name to PKI role  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/87577916:31
admin1jrosser, noonedeadpunk, does this look ok ? https://gist.githubusercontent.com/a1git/eafad4f7234bd5972cdcaa7a315f9eba/raw/1f657028d28063e3abf9b9391b18e93031aba7c9/gistfile1.txt18:13
noonedeadpunkhave no idea18:15
noonedeadpunknever tried to do that18:15
admin1:D18:15
admin1i will run and report 18:15
admin1my guess is it will work, but will add 1 more line on the publcuri 18:16
admin1which when it works, i have to manually delete the older ones18:16
admin1i am missing console there18:16
jrossernot sure you need placement externally?18:16
admin1openstack endpoint list | grep public   shows placement as well 18:16
admin1when you login to horzon and click api access, that is shown 18:17
admin1so not sure how its used 18:17
jrosserwell anyway, it looks reasonable what you have..... interesting to know if it works18:18
admin1will report success in a bit :D18:18
jrosserjust rememeber you are replaceing what is already here https://opendev.org/openstack/openstack-ansible/src/branch/stable/zed/inventory/group_vars/haproxy/haproxy.yml#L24018:19
admin1haproxy playbook runs, but does not add any entries 18:23
admin1error detected while parsing switching rule : no such ACL : 'cloud_keystone' ... 18:28
admin1i will continue on this 18:28
admin1this is someone i want to have 18:28
admin1all public endpoints on 443 so that it works from even restrictive firewalls where 80/443 is allowed18:29
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Convert haproxy_security_headers_csp to a multiline string  https://review.opendev.org/c/openstack/openstack-ansible/+/87808218:29
opendevreviewMerged openstack/openstack-ansible-haproxy_server master: Simplify haproxy_service_configs structure  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/87118818:33
admin1keystone seems to have worked :) 18:35
admin1doing the rest 18:35
admin1it did an inplace update of the public url in the database18:35
jrosserNeilHanlon: \o/ https://zuul.opendev.org/t/openstack/build/0ad0606489ad4bed9d935cd2607fc2e418:47
NeilHanlon🥳18:47
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Define individual haproxy services for each console type  https://review.opendev.org/c/openstack/openstack-ansible/+/87808318:59
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_ironic master: Remove deprecated support for cisco ucs and cims ironic drivers.  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/87760619:00
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_ironic master: Install socat and configure ipmtool-socat console interface  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/87761819:00
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_ironic master: Rename idrac interfaces to idrac-wsman  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/87762719:00
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_ironic master: Enable raid interface implementations for ironic hardware drivers  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/87762819:00
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_ironic master: Add a no_driver ironic driver type  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/87762919:00
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_ironic master: Update IPA version for 2023.1 release of Ironic  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/87753819:01
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_ironic master: Install socat and configure ipmtool-socat console interface  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/87747919:01
admin1i had to change the endpoint for barbican, placement and magnum manually .. but the rest are all working fine :) 19:36
admin1wil do a complete check again to iron out any bugs 19:36
admin1figured out why ..  those services have   _service_publicurl  and rest have  publicuri     uri vs url 19:41
admin1only thing left is the console link 19:47
admin1as it does not have a backend 19:48
jrosserit should do....19:48
jrosserlike this https://zuul.opendev.org/t/openstack/build/0ad0606489ad4bed9d935cd2607fc2e4/log/logs/etc/host/haproxy/conf.d/nova_console.txt19:49
admin1there is a variable nova_serialconsoleproxy_base_url  .but in the config it also has a port 6080 19:52
admin1will try to override only nova_serialconsoleproxy_base_url first and see what it gives 19:52
admin1i put nova_novncproxy_base_uri: https://console.domain.net  and it  is what is set, and the actual url is https://console.domain.net/vnc_lite.html?path=%3Ftoken%3D780ac59b-4254-474a-b10b-9548676b3066&*** . .but does not work 20:06
admin1i think the 6080 has to be somewhere 20:06
admin1manually adding 6080 there works 20:06
admin1my mistake .ran only nova and not haproxy :) 20:11
admin1running20:11
admin1i think it will work . and then this is completely on https:// 20:11
admin1without any ports20:11
admin1it worked :D 20:11
admin1jrosser, noonedeadpunk  .. in case you guys want to replicate  https://gist.githubusercontent.com/a1git/2ed8f628a60c61bfe6e1249dce05ba8e/raw/798b8ab9322a0a9501a43481e86a0471346afbf7/gistfile1.txt20:14
admin1all ports are gone  .. 20:14
admin1this is how the endpoints look :  https://gist.githubusercontent.com/a1git/092e7efecf5fed1ae4c36c3c1e4384ce/raw/57cb4c088a83c5aa0cf4f78def771c661645a825/gistfile1.txt    20:16
jrosserwhat did you have to do for the console?20:17
admin1nothing ..  i only ran nova and checked, but had forgotton to run haproxy playbook20:20
admin1so nova updated with console, but the haproxy entry was missing20:20
admin1the setting pasted works .. and there is no extra step 20:20
admin1setup haproxy, followed by setup-openstack .. i did not checked if there were any tags that will only update/target the endpoint creation20:21
admin124(last)  -> 25(last) fails on installing rabbitmq  .. erlang-base-hipe  21:08
admin1i think a fix was out and already backported21:08
admin1upgrade to 25.3.0 error on setup-infra -> https://gist.githubusercontent.com/a1git/3d30ce247ca56afb96a92cb4fcd11f60/raw/ddc56964328251a376621a5e6248d62529707b2d/gistfile1.txt21:29

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