Tuesday, 2021-11-09

opendevreviewMerged openstack/openstack-ansible stable/victoria: Bump OpenStack-Ansible Victoria  https://review.opendev.org/c/openstack/openstack-ansible/+/81533600:00
kleiniI notice growing queues in vhosts /nova and /neutron named notifications_designate.info and notifications_designate.error. How do I find the consumers of these queues?07:33
*** sshnaidm is now known as sshnaidm|afk07:45
noonedeadpunkkleini: if you don't have designate deloyed - there's no consumers for these07:45
noonedeadpunkin prior releases we had a bug that designate notifications were pushed even when designate was not deployed07:46
noonedeadpunkmaybe you're hitting that07:46
noonedeadpunkoh, well, for neutron this patch is present for ages actually07:48
noonedeadpunkbut anyway, the idea is that if designate is defined in inventory, (nova|neutron)_designate_enabled are renderred as true, and then in nova/neutron.conf under oslo_messaging_notifications topic is set to notifications_designate 07:50
noonedeadpunkthis is needed for designate to create records to get  resolvable hostnames or be able to provide records for floating ips iirc07:51
kleiniI have designate deployed. So it is not consuming those queues.07:52
opendevreviewJames Gibson proposed openstack/openstack-ansible master: Add playbook to generate any user defined certificates  https://review.opendev.org/c/openstack/openstack-ansible/+/81652208:23
*** sshnaidm|afk is now known as sshnaidm09:40
opendevreviewJames Gibson proposed openstack/openstack-ansible-os_nova master: Enable TLS for live migrations  https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/81522409:41
noonedeadpunkkleini: oh, yeah, I guess we missed defining that https://opendev.org/openstack/openstack-ansible-os_designate/src/branch/master/templates/designate.conf.j2#L40910:51
noonedeadpunk:(10:51
kleiniHmm, same for Nova. Will write the issue down in my TODO list and provide a patch, once it works for me.11:03
kleininoonedeadpunk: thanks for the pointer11:03
noonedeadpunkI guess the tricky thing there is that you might require domain_id11:05
kleinihttps://docs.openstack.org/designate/victoria/admin/samples/config.html designate configuration reference tells me, there should be zone_ids and not domain_ids. this makes more sense for me.11:28
noonedeadpunkyeah. I think we jsut haven't updated it for ages since it's commented out and has no effect11:46
noonedeadpunkand everybody just uses overrides there11:46
noonedeadpunkbut I believe we should be smarter there11:46
noonedeadpunkI just don't have designate in prod now so I wasn't digging into it lately11:46
kleinihttps://paste.opendev.org/show/810867/ <- this is, what I have configured now, but designate-sink is still not reading those queues11:53
noonedeadpunkkleini: I think also vhost should be provided at least?12:17
noonedeadpunkbecause nova/neutron puts notification inside their vhosts12:17
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Remove note about metal/horizon compatability  https://review.opendev.org/c/openstack/openstack-ansible/+/77157312:23
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Remove note about metal/horizon compatability  https://review.opendev.org/c/openstack/openstack-ansible/+/77157312:23
kleininoonedeadpunk: How do I provide the vhost?12:30
noonedeadpunkthat is damn good question....12:37
noonedeadpunkso eventually that's the code https://opendev.org/openstack/designate/src/branch/master/designate/notification_handler/neutron.py but it does not have any connection details12:40
noonedeadpunkI wonder how designate folks see this working...12:41
noonedeadpunkAs I actually thought it to be like implemented in ceilometer12:41
noonedeadpunkwhen ceilometer connects to other services with explicitly provided details12:42
noonedeadpunkAnd how designate aims to work if, let's say, neutron uses standalone rabbitmq cluster...12:42
noonedeadpunkso feels like these are things to ask a designate team... not sure how active they are though12:43
noonedeadpunkhm, so eventually, for notification for designate we need to provide quite different connection. ie set `nova_oslomsg_notify_vhost: /designate`12:47
noonedeadpunkkleini: oh, I guess this addresses the thing https://specs.openstack.org/openstack/oslo-specs/specs/victoria/support-transports-per-oslo-notifications.html12:49
kleiniSo, this needs to be changed on the Nova and Neutron side?12:50
noonedeadpunkyeah12:50
noonedeadpunkand that is not _that_ straightforward tbh12:51
kleiniAs I don't really need these notifications. I will disable them in Nova and Neutron for now.12:56
opendevreviewMerged openstack/openstack-ansible-os_tempest stable/ussuri: Pin neutron-tempest-plugin to v1.6.0  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/81563113:22
opendevreviewJonathan Rosser proposed openstack/ansible-role-python_venv_build stable/train: Set centos-7 jobs to non voting  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81721914:08
opendevreviewJonathan Rosser proposed openstack/ansible-role-python_venv_build stable/train: Workaround distro provided pip having old CA certs on centos-7  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81647314:09
johnsomnoonedeadpunk kleini Designate doesn’t used rabbit for integration with nova/neutron anymore. Neutron now talks directly to the designate API.14:10
noonedeadpunkoh....14:11
noonedeadpunkthen we need to do some clean-up14:12
noonedeadpunkdidn't know that14:12
johnsomdesignate-sink is there for backward compatibility for one services using it14:12
opendevreviewJonathan Rosser proposed openstack/ansible-role-python_venv_build stable/train: Revert "Set centos-7 jobs to non voting"  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81722114:15
opendevreviewJonathan Rosser proposed openstack/ansible-role-python_venv_build stable/train: Revert "Set centos-7 jobs to non voting"  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81722114:15
noonedeadpunkjohnsom: and how nova is acknoledged that designate is here? As I can't find any config option for nova. I see extension for neutron though14:25
noonedeadpunkor it just auto discovers from catalog?14:26
noonedeadpunkas I'd expect to have some section with auth to it...14:27
opendevreviewJames Gibson proposed openstack/openstack-ansible-os_nova master: Enable TLS for VNC from novncproxy to compute hosts  https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/81722214:39
opendevreviewJames Gibson proposed openstack/openstack-ansible-os_nova master: Enable TLS for VNC from novncproxy to compute hosts  https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/81722214:42
opendevreviewAleksandr proposed openstack/openstack-ansible master: Avoiding of setup of Vault on containers hosts (Vault role support)  https://review.opendev.org/c/openstack/openstack-ansible/+/80078714:47
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Add Vault role support  https://review.opendev.org/c/openstack/openstack-ansible/+/80078714:55
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-vault master: Initial commit to Vault role  https://review.opendev.org/c/openstack/ansible-role-vault/+/80079214:58
noonedeadpunk#startmeeting openstack_ansible_meeting15:00
opendevmeetMeeting started Tue Nov  9 15:00:28 2021 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'openstack_ansible_meeting'15:00
noonedeadpunk#topic rollcall15:00
noonedeadpunko/15:00
admin1o/15:00
jrosser_o/ hello15:01
damiandabrowski[m]hey!15:01
noonedeadpunkI almost failed again with sumer time hehe15:01
mgariepyhoo. early !15:03
noonedeadpunk#topic office hours15:04
noonedeadpunkI don't think we have any recent bugs, so jumping directly here15:04
noonedeadpunkI saw really great work regarding tls encryption for nova15:04
noonedeadpunkand even for VNC encryption - that's awesome15:05
jrosser_not related directly to OSA but we are seeing leaking fd in nova-compute after wallaby upgrade15:05
noonedeadpunkI fully failed my part due to internal stuff that I couldn't put away...15:05
noonedeadpunkoh15:05
noonedeadpunkwow, you already upgraded!15:06
jrosser_in case anyone else finds the same thing it looks like this https://bugs.launchpad.net/oslo.messaging/+bug/194996415:06
* noonedeadpunk subscribed15:07
noonedeadpunkinteresting15:07
jrosser_and yes for nova TLS i think the patches are really close15:07
jrosser_we have it deployed in multinode lab15:07
noonedeadpunkmay I dare to ask if you tested live migrations?15:07
jrosser_it would be great to get more testing of this, in particular as it takes ansible hostname and nodename facts and uses them in the certificate15:08
jrosser_and i think there are differences in the way people name their hosts, like fqdn or not15:08
noonedeadpunkYeah, we have ppl who can test this I believe15:08
jrosser_and this may interact with DNS blah blah and cause the cert verification to fail15:08
noonedeadpunkAt least I got several requests to notify about having first beta of X for test15:08
jrosser_we are currently testing internal VIP = https with cert from PKI role, and nova TLS15:09
noonedeadpunkand, we have mixed scenario of naming hosts in our sandbox :D15:09
jrosser_migration looks good i think, was just trying to get james here in IRC15:09
noonedeadpunkso that might be interesting15:09
jrosser_we were discussing what needs doing next here earlier today15:10
jrosser_and there is cleanup of the nova SSH keys15:10
noonedeadpunkoh, so you also implemented tls ssh auth there?15:10
jrosser_and also that we decide (?) that TLS is the only supported nova migration from now?15:10
jrosser_well, i think now that there is no need for those keys at all15:11
jrosser_unless i misunderstand how its working15:11
noonedeadpunkactually it might be that, yes15:11
noonedeadpunksince we set client certs there anyway15:11
* jrosser_ waves to JamesGibo 15:11
jrosser_james has done all this excellent work on nova TLS15:12
noonedeadpunkanswering on if it's the only supported migration - I think yes15:12
noonedeadpunkAt least I don't see other reall non-deprecated options15:12
opendevreviewMerged openstack/ansible-role-python_venv_build stable/ussuri: Set centos-7 jobs to non voting  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81631615:13
noonedeadpunkWe might keep it for another release just in case though15:13
jrosser_removing all the code for nova SSH keys would be great, but we can leave that for Y if we want to15:13
noonedeadpunkI think we should default to TLS now, with easy option for fallback15:14
jrosser_it does kind of have to be all one way or the other, i think15:14
jrosser_you can't have a mixed config across the compute nodes15:14
noonedeadpunkyeah, it can't be both15:14
jrosser_is there anything else that we want to complete TLS/PKI wise for the X release?15:15
noonedeadpunkWell we talked about memcached 15:16
noonedeadpunkBut it's not a requirement for sure15:16
jrosser_we did discuss a little about how to start transitioning the backend services to https, but that looks really quite "interesting" problem15:16
jrosser_like how to do it without a huge downtime15:16
noonedeadpunkOh, yes, that's interesting... I guess you can't have mix of backends?15:17
noonedeadpunkin terms of http/https15:18
mgariepyif the services listen both http and https, can we configure backend with both scheme in haproxy and confirm it work on https ?15:18
mgariepyor we need to move 1 backend at the time in haproxy over https..15:18
jrosser_it's not clear really15:19
jrosser_as the haproxy play runs kind of first for all the services15:19
JamesGiboHi, just caught up with meeting via irclogs!15:19
mgariepywhy couldn't we have multiple time the backends in the haproxy backend list ?15:19
noonedeadpunksame host/same port?15:19
mgariepyit will be on a different port anyway. 15:19
noonedeadpunkbut port for services is the same15:20
mgariepyho.. yep .. :/15:20
noonedeadpunkI _think_ we can manage backends during runtime15:20
noonedeadpunkthe same way we put them to maint?15:20
jrosser_right so anyway - reason i bring this up is its quite a complex problem15:21
noonedeadpunknah, module supports only enable/disable/drain I guess15:21
jrosser_and we need to start thinking about it even if theres no answer right now15:21
spateljrosser_ that rabbitMQ bug is interesting.. i haven't seen any behavior yet. 15:21
mgariepycan we have 2 pools of backends ?15:22
noonedeadpunkWell, at least I'm think that you can pass to haproxy socket to drop a specific backend or add another one15:23
noonedeadpunkSo even if there's no ansible module ready for that - that is not impossible15:23
jrosser_the awkward part is that when all this is completed you want the https backend to be on the same well known port numbers as the http one used to be15:24
noonedeadpunkAnd we can write config after all services are reloaded. or actually trigger haproxy role for migration in each playbook, which would be pretty nasty I guess.15:24
jrosser_so it feels like there are multiple phases involved15:25
noonedeadpunkyeah15:25
jrosser_ok well maybe most important is testing the nova TLS stuff15:26
noonedeadpunkI suggest merge it to be able to test easily15:26
noonedeadpunkwe can patch if afterwards anytime15:26
jrosser_JamesGibo: we've tested migration is working? :)15:27
JamesGiboYeah, it is working for us15:27
JamesGiboUsing the HAproxy API to manage the backends is an intressting idea, i will have a think about that15:29
jrosser_noonedeadpunk: how much of the hashicorp vault stuff would you like to get done for X?15:30
jrosser_maybe we should start an etherpad with todo/patch links15:31
noonedeadpunkpersonally I don't care _that_ much:) 15:31
noonedeadpunkas I don't have time for it at all. But folks eager to push stuff15:32
noonedeadpunkit's tough given their awareness of the project overall15:32
noonedeadpunkI think we can merge vault role and hopefully agree on "concept" patch15:33
noonedeadpunkand we can iterate on the vault to add internal storage and safe tokens storage then we have now15:34
opendevreviewMerged openstack/ansible-role-python_venv_build stable/ussuri: Workaround distro provided pip having old CA certs on centos-7  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81631715:34
noonedeadpunkbut at least not to get overwhelmed with depends-on there15:34
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-python_venv_build stable/ussuri: Revert "Set centos-7 jobs to non voting"  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81725015:35
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-python_venv_build stable/ussuri: Revert "Set centos-7 jobs to non voting"  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81725015:35
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-python_venv_build stable/ussuri: Revert "Set centos-7 jobs to non voting"  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/81725015:36
noonedeadpunkI think more important is to fix zun15:36
* jrosser_ looks for andrewbonney 15:36
noonedeadpunkas I haven't return to it. And the question is in libcyrur that's they don't build for deb15:37
andrewbonneyDidn't realise it was broken. I'll take a look tomorrow15:37
noonedeadpunkso options were either snap (fewwww) or build from source15:37
jrosser_this is no deb for focal, or just new version theres no deb at all?15:37
noonedeadpunkno versions for deb at all15:37
noonedeadpunk*new15:37
noonedeadpunkwell eventually we relied opensuse repo for deb which was a bit naive but worked15:38
noonedeadpunkoh, wait, I guess it was not kuryr but kata...15:39
noonedeadpunkyes, it was kata...15:40
noonedeadpunkso whole 2.0 version is not available for deb15:40
noonedeadpunkand to be specific - way was broken for debian only15:42
noonedeadpunkso we might set it as nv now I guess15:43
andrewbonneykata isn't required for zun to work, so in the worst case it could be disabled, but it would be nice to fix it15:43
noonedeadpunkbut we still need to find the way to move forward15:43
noonedeadpunkAlso, I asked damiandabrowski[m] to be another pair of eyes for https://etherpad.opendev.org/p/db_pool_calculations and help out with landing patches15:45
noonedeadpunkWould be great if we can get new numbers soon15:46
noonedeadpunkok, awesome, thanks everyone for joining! 15:47
johnsomnoonedeadpunk I didn't want to bug you during the meeting, but DNS records are really only tied to neutron ports/fips/etc. so neutron handles interacting with designate on behalf of nova during the port plugs. There is no longer a direct link from nova to designate.15:56
noonedeadpunkaha, fair enough15:58
noonedeadpunkI just had some recallings that nova-metadata was pushing for sink or smth like that15:59
noonedeadpunkbut yes, I agree that makes sense15:59
noonedeadpunk#endmeeting15:59
opendevmeetMeeting ended Tue Nov  9 15:59:49 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
opendevmeetMinutes:        https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-11-09-15.00.html15:59
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-11-09-15.00.txt15:59
opendevmeetLog:            https://meetings.opendev.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-11-09-15.00.log.html15:59
damiandabrowski[m]yeah, i will look at db_pool_calculations hopefully this week16:00
mgariepythe number of worker per service seems to be on the low side for some services like neutron16:05
mgariepykeystone also.16:09
mgariepyon a smallish cloud with ~100 compute nodes i'm at ~900 connections 16:16
noonedeadpunkwell yes16:16
mgariepyand it's with minimal services16:16
noonedeadpunkand 90% of them are just sleeping16:17
noonedeadpunkand never used16:17
mgariepyi would say 99.5 but yes.16:17
mgariepyso we should lower the thread per service then ?16:17
noonedeadpunkThe idea was to low max_pool_size16:18
noonedeadpunkand instead increase db_max_overflow16:18
noonedeadpunkbecause overflow steps in when pool_size is not enough16:19
noonedeadpunkand pool_size always fully used16:19
noonedeadpunkie https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/78659216:20
mgariepyha ok.16:21
spatelnoonedeadpunk around?16:57
noonedeadpunkyep16:59
opendevreviewMerged openstack/openstack-ansible stable/ussuri: Fetch upper constraints file with curl rather than allow pip to download it  https://review.opendev.org/c/openstack/openstack-ansible/+/81563218:10
spatelnoonedeadpunk :) are you around 20:02
spatelif you don't tag me i won't able to see notification.. :(20:02
spatelanyway its late for you so will talk tomorrow20:02

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